8.2.3 Non-MSGin5G UE Registration

23.5543GPPApplication architecture for MSGin5G ServiceRelease 18Stage 2TS

Tools: ARFCN - Frequency Conversion for 5G NR/LTE/UMTS/GSM

Non-MSGin5G UEs (i.e., Legacy 3GPP UEs or Non-3GPP UEs) are connected to the MSGin5G Server through a Message Gateway. The Message Gateway performs registration with the MSGin5G Server on behalf of the Non MSGin5G UEs, based on pre-provisioned information when receives a registration request from the Non MSGin5G UE, or gets the knowledge of that Non-MSGin5G UE is ready for the MSGin5G service. After the procedure is completed, the Message Gateway may communicate the result to the Non-MSGin5G UE to enable MSGin5G Services at the Non MSGin5G UEs.

NOTE: The communication procedure between Non-MSGin5G UE and Message Gateway is out of scope of this document.

The signalling flow is illustrated in figure 8.2.3-1.

Pre-conditions:

1. The Message Gateway has been pre-configured with the MSGin5G Server address.

2. The Message Gateway has been configured with the necessary information as specified in clause 8.1.3, i.e. UE Service ID and credentials on behalf of Non- MSGin5G UE, and may also been configured with Non-MSGin5G UE Profile if available, to enable authentication and Non- MSGin5G UE registration at the Message Server.

3. A secured connection has been established between the Message Gateway and the MSGin5G Server.

Figure 8.2.3-1: Non-MSGin5G UE registration

1. The Message Gateway sends the Non-MSGin5G UE registration request to the MSGin5G Server. The request includes the information pre-configured to the Message Gateway or provided by the Non-MSGin5G UE (e.g. in a non-MSGin5G registration request) and detailed in Table 8.2.3-1.

Table 8.2.3-1: Non-MSGin5G UE registration request

Information element	Status	Description
UE Service ID	M	UE service identifier assigned to the requesting Non-MSGin5G UE.
MGW Service ID	M	The service identifier of the Message Gateway performing registration on behalf of a Non-MSGin5G UE
Non-MSGin5G UE Profile	O	Set of parameters describing the Non-MSGin5G UE
>Non-MSGin5G UE Communication Availability	O	Communication availability information for the Non-MSGin5G UE to receive messages. This IE informs the MSGin5G Server if the Non-MSGin5G UE has a specific application-level schedule/periodicity to its MSGin5G communications, which may be used to determine whether and when MSGin5G communications are attempted. See Table 8.2.1-3.

2. Upon receiving the request, the MSGin5G Server initiates authentication procedures with the Message Gateway on behalf of the Non-MSGin5G Client and authorises the Non-MSGin5G UE to receive the MSGin5G Service. If the registration is successful, the MSGin5G Server stores the UE Service ID and associated Non-MSGin5G UE Profile information.

NOTE: The authentication procedures in step 3 are built on top of the transport layer mechanism specified in Annex Y.2 of 3GPP TS 33.501 [16].

3. The MSGin5G Server returns the result of the registration in the Non-MSGin5G UE registration response message with the information detailed in table 8.2.1-4, to the Message Gateway.