The signalling flow for MSGin5G UE registration is illustrated in Figure 8.2.1-1. The procedure assumes that the MSGin5G UE is responsible for initiating registration to the MSGin5G Server in order to establish association with the MSGin5G Server to receive MSGin5G Services.
The MSGin5G UE has connected to the serving network successfully.
A UE Service ID has been configured on the MSGin5G UE.
The MSGin5G Server address has been provisioned on the MSGin5G UE.
Both the MSGin5G UE and MSGin5G Server have been configured with the necessary credentials to enable authenticating one another.
The MSGin5G UE sends an MSGin5G UE registration request to the MSGin5G Server. The request includes security credentials required for the MSGin5G Client to register to the MSGin5G Server. The request includes the UE Service ID and MSGin5G Client Profile information as detailed in Table 8.2.1-1.
UE service identifier assigned to the requesting MSGin5G UE.
UE credential information
The information needed to authenticate the UE. The authentication and authorization between MSGin5G client and MSGin5G Server are specified in Annex Y.2 of TS 33.501.
MSGin5G Client Profile
Set of parameters describing the MSGin5G Client
> MSGin5G Client Triggering Information
UE Identifier (i.e., MSISDN, external ID), port number(s) and associated protocol (e.g., SMS, NIDD, etc.) for device triggering. The MSGin5G Server uses the information in step 5 of clause 8.8.3. See Table 8.2.1-2.
> MSGin5G Client Communication Availability
Communication availability information for the MSGin5G Client to receive MSGin5G messages. This IE informs the MSGin5G Server if the client has a specific application-level schedule/periodicity to its MSGin5G communications, which may be used in conjunction with UE reachability monitoring to determine whether and when MSGin5G communications are attempted. See Table 8.2.1-3.
> MSGin5G Client Supported Maximum MSGin5G segment size
The Maximum MSGin5G segment size can be used by the MSGin5G server to deliver message to the client served by it in its MSGin5G service domain. The MSGin5G message sent to the MSGin5G Client should be segmented by the MSGin5G Server serves the receiver if the message size is bigger than the MSGin5G Client Supported Maximum MSGin5G segment size.
The value of this IE is decided by the MSGin5G Client, and is depended on the MSGin5G Client capabilities, e.g. supported transport, computing capability or application processing time limitation.
If this IE is not included, the MSGin5G Server shall use the pre-configured global value within the MSGin5G service domain.
The MSGin5G Server sends an MSGin5G UE registration response to the MSGin5G UE. The response includes the information elements as detailed in Table 8.2.1-4. If the registration is successful, the MSGin5G Server stores the UE Service ID and associated MSGin5G Client Profile information.
By de-registering, the MSGin5G UE informs the MSGin5G Server that it wishes to terminate its association with the MSGin5G Server.
The procedure assumes that the MSGin5G UE is responsible for initiating the de-registration from the MSGin5G Server. The signalling flow for MSGin5G UE de-registration is illustrated in Figure 8.2.2-1.
The MSGin5G UE is registered to the MSGin5G Server.
The MSGin5G Server validates the MSGin5G UE de-registration request and verifies the security credentials. The MSGin5G Server deletes any applicable UE Service ID and associated MSGin5G Client Profile information that it has stored.