Content for TS 29.502 Word version: 18.5.0

1… 5… 5.2.2… 5.2.2.2.4… 5.2.2.3… 5.2.2.3.2… 5.2.2.3.3… 5.2.2.3.6… 5.2.2.3.8… 5.2.2.3.10… 5.2.2.3.17… 5.2.2.3.23… 5.2.2.4… 5.2.2.8… 5.2.2.8.2… 5.2.2.8.2.7… 5.2.2.8.2.12… 5.2.2.8.2.20… 5.2.2.8.3… 5.2.2.8.3.6… 5.2.2.9… 5.2.3… 6… 6.1.2… 6.1.3… 6.1.3.3… 6.1.3.5… 6.1.3.6… 6.1.3.7… 6.1.4… 6.1.6… 6.1.6.2… 6.1.6.2.5… 6.1.6.2.11… 6.1.6.2.18… 6.1.6.2.27… 6.1.6.2.40… 6.1.6.2.54… 6.1.6.2.65… 6.1.6.3… 6.1.6.4… 6.1.7… A… B… C…

B.1 Example of HTTP multipart message B.1.1 General B.1.2 Example HTTP multipart message with N1 SM Message binary data

B HTTP Multipart Messages p. 359

B.1 Example of HTTP multipart message p. 359

B.1.1 General p. 359

This clause provides a (partial) example of HTTP multipart message. The example does not aim to be a complete representation of the HTTP message, e.g. additional information or headers can be included.

This Annex is informative and the normative descriptions in this specification prevail over the description in this Annex if there is any difference.

B.1.2 Example HTTP multipart message with N1 SM Message binary data p. 359

POST /example.com/nsmf-pdusession/v1/sm-contexts HTTP/2
Content-Type: multipart/related; type="application/json"; boundary=----Boundary
Content-Length: xyz
------Boundary
Content-Type: application/json
{
    "supi": "imsi-<IMSI>",
    "pduSessionId": 235,
    "dnn": "<DNN>",
    "sNssai": {
      "sst": 0
    },
    "servingNfId": "<AMF Identifier>",
    "n1SmMsg": {
      "contentId": "n1msg"
    },
    "anType": "3GPP_ACCESS",
    "smContextStatusUri": "<URI>"
}
------Boundary
Content-Type: application/vnd.3gpp.5gnas
Content-Id: n1msg
{ … N1 SM Message binary data …}
------Boundary