Content for TS 29.577 Word version: 18.4.0
1 Scope p. 8
The present document specifies the stage 3 protocol and data model for the Nipsmgw and Nrouter Service Based Interface. It provides stage 3 protocol definitions and message flows, and specifies the API for each service offered by the IP-SM-GW and SMS Router.
The 5G System stage 2 architecture and procedures are specified in TS 23.501 and TS 23.502.
The Technical Realization of the Service Based Architecture and the Principles and Guidelines for Services Definition are specified in TS 29.500 and TS 29.501.
The Stage 2 architecture, procedures and services to support service based short message service (SMS) in 5G system (5GS) is specified in TS 23.540.
2 References p. 8
The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
- For a specific reference, subsequent revisions do not apply.
- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
[1]
TR 21.905: "Vocabulary for 3GPP Specifications".
[2]
TS 23.501: "System Architecture for the 5G System; Stage 2".
[3]
TS 23.502: "Procedures for the 5G System; Stage 2".
[4]
TS 29.500: "5G System; Technical Realization of Service Based Architecture; Stage 3".
[5]
TS 29.501: "5G System; Principles and Guidelines for Services Definition; Stage 3".
[6]
OpenAPI: "OpenAPI Specification Version 3.0.0", https://spec.openapis.org/oas/v3.0.0 .
[7]
TR 21.900: "Technical Specification Group working methods".
[8]
TS 33.501: "Security architecture and procedures for 5G system".
[9]
RFC 6749: "The OAuth 2.0 Authorization Framework".
[10]
TS 29.510: "5G System; Network Function Repository Services; Stage 3".
[11]
RFC 9113: "HTTP/2".
[12]
RFC 8259: "The JavaScript Object Notation (JSON) Data Interchange Format".
[13]
RFC 9457: "Problem Details for HTTP APIs".
[14]
TS 23.540: "5G System; Technical realization of Service Based Short Message Service; Stage 2".
[15]
TS 29.571: "5G System; Common Data Types for Service Based Interfaces; Stage 3".
[16]
TS 23.040: "Technical realization of the Short Message Service (SMS)".
[17]
TS 24.011: "Point-to-Point (PP) Short Message Service (SMS) support on mobile radio interface".
[18]
RFC 2387: "The MIME Multipart/Related Content-type".
[19]
RFC 2045: "Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies".
3 Definitions and abbreviations p. 9
3.1 Definitions p. 9
For the purposes of the present document, the terms and definitions given in TR 21.905 and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905.
Gateway MSC For Short Message Service (SMS-GMSC):
function of an MSC capable of receiving a short message from an SC, interrogating an HLR/HSS/UDM for routing information and SMS info, and delivering the short message to the VMSC/SGSN/MME/SMSF of the recipient MS/UE.
IP-Short-Message-Gateway (IP-SM-GW):
function responsible for protocol interworking between the IP-based UE and the SC.
3.2 Abbreviations p. 9
For the purposes of the present document, the abbreviations given in TR 21.905 and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905.
IP-SM-GW
IP Short Message Gateway
SM MO
Short Message Mobile Originated
SM MT
Short Message Mobile Terminated
SMSF
Short Message Service Function
