The present document specifies the functional architecture, procedures, information flows and APIs for MSGin5G Service. MSGin5G Service provides messaging communication capability in 5GS especially for Massive Internet of Things (MIoT).
MSGin5G Service includes the following message communication models:
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.
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.
MSGin5G message delivery that is originated at an Application Server in the network and terminated at a UE.
an area consisting of one or more cells where the broadcast message is delivered.
A MSGin5G message delivery that is delivered to UEs in a Broadcast Area.
Broadcast Message Gateway:
the entity in MSGin5G Service to support delivery Broadcast messages to Legacy 3GPP UEs, Non-3GPP UEs and MSGin5G UEs.
a UE (with or without MSGin5G client) which may not have capability to connect to the 3GPP network.
message delivery that is originated at a UE or an Application Server and is terminated at all members of the group (a group member can be of type UE, Legacy 3GPP UE or Non-3GPP UE).
Legacy 3GPP Message Gateway:
the entity in MSGin5G Service to support interworking with Legacy 3GPP UEs.
Legacy 3GPP UE:
the UE that supports legacy 3GPP message sending and receiving (e.g. SMS, NIDD, etc) in MSGin5G Service.
the client that enables MSGin5G message sending and receiving.
general terminology for Legacy 3GPP Message Gateway or Non-3GPP Message Gateway.
MSGin5G Gateway UE:
an MSGin5G UE which constructs and sends MSGin5G message upon receiving request along with required application specific data from the application client on the Constrained UE (without MSGin5G client). The same MSGin5G UE can also deliver the received MSGin5G message towards the target application client on the Constrained UE (without MSGin5G client).
the group of UEs which members may be MSGin5G UE, Legacy 3GPP UE and Non-3GPP UE.
the message defined in the present specification that is exchanged between the MSGin5G Service endpoints under the MSGin5G Service.
MSGin5G Proxy UE:
an MSGin5G UE which constructs and sends MSGin5G message upon receiving MSGin5G message from the MSGin5G Client on the Constrained UE. The same MSGin5G UE can also deliver the received MSGin5G message towards the target MSGin5G Client on the Constrained UE.
MSGin5G Relay UE:
an MSGin5G UE which receives MSGin5G message from Constrained UE (with MSGin5G client) and forwards it to the MSGin5G server and vice-versa.
A server in MSGin5G Service that receives and delivers MSGin5G messages among MSGin5G Service endpoints.
an MNO message service using the 5G System that enables Point- to-Point, Application-to-Point, Point-to-Application, Group and Broadcast message delivery for thing-to-thing communication and person-to-thing communication.
an identifier for a topic to which a UE or an Application Server can subscribe to in order to receive messages that are characterized by a Message Topic.
the UE that uses MSGin5G Client in MSGin5G Service.
Non-3GPP Message Gateway:
the entity in MSGin5G Service to support interworking with Non-3GPP UEs.
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.