Support for GSM SMS TPDU in HTTP2 body
Description
In 5G the node SMSF node sends and receives SMS TPDU as part of multipart body(29.540). As mentioned in the 3GPP specification, example HTTP multipart message with SMS binary data:
POST /example.com/nsmsf-sms/v1/ue-contexts/{supi}/sendsms HTTP/2
Content-Type: multipart/related; boundary=----Boundary
Content-Length: xyz
------Boundary
Content-Type: application/json
{
"smsRecordId": "777c3edf-129f-486e-a3f8-c48e7b515605",
"smsPayload": {
"contentId": "sms"
},
"gpsi": "msisdn-8613915900000",
"pei": "imei-123456789012345",
"accessType": "3GPP_ACCESS",
"ueLocation": {
"nrLocation": {
"tai": {
"plmnId": {
"mcc": "46",
"mnc": "000"
},
"tac": "A01001",
"ncgi": {
"plmnId": {
"mcc": "46",
"mnc": "000"
},
"nrCellId": "225BD6007"
}
}
},
"ueTimeZone": "+08:00"
}
------Boundary
Content-Type: application/vnd.3gpp.sms
Content-Id: sms
{ … SMS Message binary data …}
------Boundary
The SMS Message binary data mentioned in this is GSM SMS TPDU.
vnd.3gpp.sms: Binary encoded payload, encoding SMS payload, as specified in 3GPP TS 23.040 [11] and 3GPP TS 24.011
[12].
Currently this is not being decoded in wireshark.
This should be similarly decoded as GSM-MAP SMS or AVP: SM-RP-UI(3301) as in OFR/TFR as per my knowledge.
Links / references / protocol specifications
Specifications mentioned for reference:
- 29.540: https://portal.3gpp.org/desktopmodules/Specifications/SpecificationDetails.aspx?specificationId=3344
- 23.040: https://portal.3gpp.org/desktopmodules/Specifications/SpecificationDetails.aspx?specificationId=747
- 24.011: https://portal.3gpp.org/desktopmodules/Specifications/SpecificationDetails.aspx?specificationId=1017
Sample capture
Sample trace attached. Please decode as HTTP2. sms_http_issue_trace.pcap
Edited by J93d