Content for TS 29.538 Word version: 18.6.1
1 Scope
2 References
3 Definitions of terms, symbols and abbreviations
3.1 Terms
3.2 Symbols
3.3 Abbreviations
4 Overview
...
...
1 Scope p. 11
The present document specified the Application Programming Interface (API) for enabling the MSGin5G Service over MSGin5G-2/3/4/7/8 interfaces. The application layer architecture, functional requirements, procedures and information flows necessary for MSGin5G Service are contained in TS 23.554. The requirements for MSGin5G are specified in TS 22.262.
2 References p. 11
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.554: "Application architecture for MSGin5G Service".
[3]
TS 22.262: "Message Service within the 5G System".
[4]
TS 29.500: "5G System; Technical Realization of Service Based Architecture; Stage 3".
[5]
TS 29.571: "5G System; Common Data Types for Service Based Interfaces Stage 3".
[6]
OpenAPI: "OpenAPI Specification Version 3.0.0", https://spec.openapis.org/oas/v3.0.0 .
[7]
TS 23.222: "Functional architecture and information flows to support Common API Framework for 3GPP Northbound APIs; Stage 2".
[8]
TS 29.222: "Common API Framework for 3GPP Northbound APIs; Stage 3".
[9]
TS 29.501: "5G System; Principles and Guidelines for Services Definition; Stage 3".
[10]
RFC 9112: "HTTP/1.1".
[11]
RFC 9110: "HTTP Semantics"
[12] Void.
[13] Void.
[14]
RFC 9111: Caching".
[15] Void
[16]
RFC 9113: HTTP/2".
[17]
RFC 8259: "The JavaScript Object Notation (JSON) Data Interchange Format".
[18]
TR 21.900: "Technical Specification Group working methods".
[19]
TR 33.862: "Study on security aspects of the Message Service for MIoT over the 5G System (MSGin5G)".
[20]
TS 33.501: "Security architecture and procedures for 5G system".
[21]
RFC 6749: "The OAuth 2.0 Authorization Framework".
[22]
TS 33.122: "Security Aspects of Common API Framework for 3GPP Northbound APIs".
[23]
TS 29.522: "5G System; Network Exposure Function Northbound APIs; Stage 3".
[24]
TS 29.122: "T8 reference point for northbound APIs".
3 Definitions of terms, symbols and abbreviations p. 12
3.1 Terms p. 12
For the purposes of the present document, the terms 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.
For the purposes of the present document, the following terms and its definitions given in TS 23.554 shall apply:
MSGin5G Service
MSGin5G message
MSGin5G UE
MSGin5G Group
MSGin5G Client
MSGin5G Server
Legacy 3GPP Message Gateway
Non-3GPP Message Gateway
Broadcast Message Gateway
Legacy 3GPP UE
Non-3GPP UE
Point-to-Point messaging
Point-to-Application messaging
Application-to-Point messaging
Group messaging
Broadcast messaging
Messaging Topic
Message Gateway
Broadcast Area
3.2 Symbols p. 12
For the purposes of the present document, the following symbols apply:
3.3 Abbreviations p. 12
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.
AS
Application Server
BC
Broadcast
BMG
Broadcast Message Gateway
CAPIF
Common API Framework
L3G
Legacy 3GPP Message Gateway
N3G
Non-3GPP Message Gateway
4 Overview p. 13
The MSGin5G Service is designed and optimized for massive IoT device communication including thing-to-thing communication and person-to-thing communication and provides messaging capability in 5GS with messaging communication models including Point-to-Point, Application-to-Point/Point-to-Application, Group and Broadcast messaging.
3GPP TS 23.554 has specified the application layer architecture, architectural requirements, procedures, information flows and some APIs, in order to support the MSGin5G Service. Various features are defined to ensure the efficient use and deployment of MSGin5G Service, including configuration, registration, message delivery, message aggregation, segmentation and reassembly, topic messaging.
The present document specifies MSGin5G Services offered by MSGin5G Servers and MSGin5G Gateway, and APIs in detail, needed over MSGin5G-2/3/4/7/8 interfaces for interworking between MSGin5G Server and Legacy 3GPP UE, Non-3GPP UE, Broadcast Message Gateway or Application Server, with following functionalities need to be supported:
- Server-side functionality with the sending and receiving of messages to/from Application Servers and/or other MSGin5G Service endpoints on other UEs, provided by MSGin5G Server.
- Interconnecting two different messaging delivery mechanisms and assure the message integrity between different message delivery mechanisms, provided by Message Gateway.
