B.2 Example HTTP multipart message with SMS binary data

29.5773GPP5G SystemIP Short Message Gateway and SMS Router For Short Message ServicesRelease 18Stage 3TS

Example HTTP multipart message with SMS binary data:

POST /example.com/nipsmgw-smservice/v1/mt-sm-infos/{gpsi}/sendsms HTTP/2

Content-Type: multipart/related; boundary=—-Boundary

Content-Length: xyz

——Boundary

Content-Type: application/json

{

"smsPayload": {

"contentId": "sms"

},

}

——Boundary

Content-Type: application/vnd.3gpp.sms

Content-Id: sms

{ … SMS Message binary data …}

——Boundary

The JSON part of the HTTP POST message includes an attribute named "smsPayload" which refers to RefToBinaryData structure. The "contentId" of RefToBinaryData is encoded as a string and used to reference the value of the Content-ID header field of the binary body part.

Annex C (informative):
Change history

Change history

Date

Meeting

TDoc

CR

Rev

Cat

Subject/Comment

New version

2022-04

CT4#109e

C4-222401

TS skeleton

0.0.0

2022-04

CT4#109e

C4-222341

Implementation of pCRs agreed at CT4#109e: C4-222279, C4-222280, C4-222283, C4-222398, C4-222399, C4-222402, C4-222403

0.1.0

2022-05

CT4#110e

C4-223450

Implementation of pCRs agreed at CT4#110e: C4-223220, C4-223222, C4-223353

0.2.0

2022-06

CT#96

CP-221078

TS presented for information and approval

1.0.0

2022-06

CT#96

CP-221078

TS approved at CT#96

17.0.0

2022-09

CT#97e

CP-222027

0001

F

Alignment on the service name used with template

17.1.0

2022-09

CT#97e

CP-222027

0002

F

Editorial corrections

17.1.0

2022-09

CT#97e

CP-222027

0003

F

Update on the content type for OpenAPI

17.1.0

2022-09

CT#97e

CP-222058

0004

F

29.577 Rel-17 API version and External doc update

17.1.0

2022-12

CT#98e

CP-223028

0005

1

F

Missing Mandatory Status Codes in OpenAPI

18.0.0

2022-12

CT#98e

CP-223033

0006

F

29.577 Rel-18 API version and External doc update

18.0.0