8.2.9 Non-MSGin5G UE bulk de-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 may decide to use bulk registration procedure specified in this clause based on service policy. The procedure for Non-MSGin5G UE bulk registration is illustrated in figure 8.2.9-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 UEs, and may also been configured with Non-MSGin5G UEs’ Profile if available, to enable authentication and Non- MSGin5G UEs registration at the Message Server.

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

Figure 8.2.9-1: Non-MSGin5G UE bulk registration

1. The Message Gateway determines to perform Non-MSGin5G UE bulk registration.

NOTE: The conditions of whether the Non-MSGin5G UE bulk registration is used are implementation specific and out of the scope of the current specification.

2. The Message Gateway sends a Non-MSGin5G UE bulk registration request to the MSGin5G Server. The Information Elements specified in table 8.2.9-1 are included in the Non-MSGin5G UE bulk registration request.

Table 8.2.9-1: Non-MSGin5G UE bulk registration request

Information element	Status	Description
Number of individual MSGin5G UE registration requests	M	Indicates total number of Non-MSGin5G UE registration requests which are bulked in this Non-MSGin5G UE bulk registration request
List of individual Non-MSGin5G UE information	M	Each element in this list contains information as specified in Table 8.2.3-1.

3. Upon receiving the Non-MSGin5G UE bulk registration request, the MSGin5G Server processes each of the UE registration from the list individually as specified in clause 8.2.3, If the registration is successful, the MSGin5G Server stores every UE Service ID and associated Non-MSGin5G UE Profile information of bulk registered Non-MSGin5G UE respectively.

Editor’s note: Security aspects of Non-MSGin5G UE bulk registration is the responsibility of SA3.

4. The MSGin5G Server includes all corresponding MSGin5G UE registration responses in a Non-MSGin5G UE bulk registration response and sends it to Message Gateway. The Information Elements specified in table 8.2.9-2 are included in the Non-MSGin5G UE bulk registration response.

Table 8.2.9-2: MSGin5G UE bulk registration response

Information element	Status	Description
Number of individual Non-MSGin5G UE registration responses	M	Indicates total number of Non-MSGin5G UE registration responses which are bulked in this MSGin5G UE bulk registration response
List of individual Non-MSGin5G UE registration response	M	Each element in this list contains information as specified in Table 8.2.1-4.