8.2.7 MSGin5G UE bulk registration over MSGin5G-6 reference point

23.5543GPPApplication architecture for MSGin5G ServiceRelease 18Stage 2TS

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

When constrained devices UE-2a and UE-2b, which support an MSGin5G Client, perform registration via MSGin5G UE-1 to contact the MSGin5G Server, the MSGin5G UE-1 may decide to use bulk registration procedure specified in this clause based on the registration request sent from MSGin5G Clients in MSGin5G UE-2a and MSGin5G UE-2b, if allowed by service policy. The procedure for MSGin5G UE bulk registration is illustrated in figure 8.2.7-1.

Pre-conditions:

1. The MSGin5G UE-1 has registered to the MSGin5G Server successfully.

2. MSGin5G UE-2a and MSGin5G UE-2b have discovered and selected MSGin5G UE-1 as the MSGin5G Proxy UE as specified in clause 8.2.8 and connected to the serving network via MSGin5G UE-1 successfully.

3. UE Service IDs and the MSGin5G Server addresses have been configured on the MSGin5G UE-1, MSGin5G UE-2a and MSGin5G UE-2b. All these MSGin5G UEs are served by a same MSGin5G Server.

4. Both the MSGin5G UEs and MSGin5G Server have been configured with the necessary credentials to enable authenticating one another.

Figure 8.2.7-1: MSGin5G Client bulk registration

1. The MSGin5G Client-2a sends an MSGin5G UE registration request to the MSGin5G Server as specified in clause 8.2.1, In addition to the Information Elements specified in table 8.2.1-1, the MSGin5G Client-2a may also add the Information Elements specified in table 8.2.7-1 in the MSGin5G UE registration request.

Table 8.2.7-1: MSGin5G UE registration request

Information element	Status	Description
Registration urgent degree	O	Indicates whether the registration request is urgent or not. If a MSGin5G UE registration request is indicated as urgent, the MSGin5G UE registration request cannot be bulk-handled.
Registration request expiration time	O	Indicates the maximum processing time of the registration request allowed by the MSGin5G Client-2.

2. Upon receiving the MSGin5G UE registration request, the MSGin5G Client-1 checks whether this request can be bulked based on the service policy and the information included in the MSGin5G UE registration request, e.g.

a) whether the MSGin5G UE registration request is urgent; or

b) whether bulk registration is supported by the MSGin5G service provider;

NOTE 1: Whether bulk registration is supported can be configured in the MSGin5G Client-1.

NOTE 2: The bulk registration conditions are specified by application provider or MSGin5G Service provider and are out of scope of this document.

3. Based on step 2:

a) if the MSGin5G UE registration request cannot be bulked, MSGin5G Client-1 forwards the registration request to MSGin5G Server; or

b) if the MSGin5G UE registration request can be bulked, MSGin5G Client-1 sends a bulk registration notification to MSGin5G Client-2 and caches/stores the MSGin5G UE registration request until the bulk registration conditions can be fulfilled. The Information Elements specified in table 8.2.7-2 are included in the bulk registration notification. The steps 4 and 5 are skipped.

Table 8.2.7-2: bulk registration notification

Information element	Status	Description
UE Service ID	M	UE service identifier assigned to the requesting MSGin5G UE-2.
Expected registration time	O	The expected time when the bulk registration can be handled and the MSGin5G UE registration Response can be received.

4. The MSGin5G Server handles the MSGin5G UE registration request as specified in clause 8.2.1 and sends the corresponding MSGin5G UE registration response to MSGin5G Client-2a.

5. The MSGin5G Client-1 sends the MSGin5G UE registration response to MSGin5G Client-2a. The MSGin5G Client-2a handles the MSGin5G UE registration response as specified in clause 8.2.1 and skips all the remaining steps in this clause.

6. MSGin5G Client-2b sends an MSGin5G UE registration request and the MSGin5G UE registration request is handed as in steps 2-5.

7. The MSGin5G Client-1 finds that the conditions of sending a bulk registration request can be fulfilled, e.g.

a) the registration request expiration time in the MSGin5G UE registration request sent from MSGin5G Client-2a or MSGin5G Client-2b is reached; or

b) the periodic bulk registration interval is reached; or

c) the maximum MSGin5G UE registration request number in a MSGin5G UE bulk registration request is reached.

NOTE 3: The maximum registration time, periodic bulk registration interval and maximum MSGin5G UE registration request number are implementation specific and out of the scope of the current specification.

8. The MSGin5G Client-1 includes all cached/stored MSGin5G UE registration requests in an MSGin5G UE bulk registration request and sends it to the MSGin5G Server. The Information Elements specified in table 8.2.7-3 are included in the MSGin5G UE bulk registration request.

Table 8.2.7-3: MSGin5G UE bulk registration request

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

9. Upon receiving the MSGin5G UE bulk registration request, the MSGin5G Server splits the MSGin5G UE bulk registration request, executes the authentication, authorization and registration procedures for each MSGin5G Client-2 individually as specified in clause 8.2.1.

Editor’s note: Security aspects of bulk registrationis the responsibility of SA3.

10. The MSGin5G Server includes all corresponding MSGin5G UE registration responses in an MSGin5G UE bulk registration response and sends it to MSGin5G Client-1. The Information Elements specified in table 8.2.7-4 are included in the MSGin5G UE bulk registration response.

Table 8.2.7-4: MSGin5G UE bulk registration response

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

11. Upon receiving the MSGin5G UE bulk registration response, the MSGin5G Client-1 splits the MSGin5G UE bulk registration response into multiple individual MSGin5G UE registration response, each individual MSGin5G UE registration response contains information as specified in Table 8.2.1-4.

12. MSGin5G Client-1 sends the MSGin5G UE registration Response 2a to MSGin5G Client-2a.

13. MSGin5G Client-1 sends the MSGin5G UE registration Response 2b to MSGin5G Client-2b.