Tech-invite3GPPspaceIETF RFCsSIP
Quick21222324252627282931323334353637384‑5x

Content for  TS 23.554  Word version:  18.2.0

Top   Top   Up   Prev   Next
1…   4…   5…   5.5…   6…   7…   8…   8.2…   8.2.3…   8.2.5…   8.3…   8.3.4…   8.4…   8.5…   8.6…   8.7…   8.7.2…   8.7.3…   8.7.4…   8.7.5…   8.8…   8.9…   8.9.3…   8.10…   8.11…   9…   10…

 

8.2.5  Application Server Registrationp. 34

The signalling flow for Application Server registration is illustrated in Figure 8.2.5-1. Application Server may use the procedure in this clause to do registration. The procedure assumes that the Application Server is responsible for triggering registration to the MSGin5G Server in order to establish association with the MSGin5G Server to receive MSGin5G Service.
Pre-conditions:
  1. The Application Server has connected to the serving network successfully.
  2. An AS Service ID has been provisioned.
  3. The MSGin5G Server address has been provisioned on the Application Server.
  4. Both the Application Server and MSGin5G Server have been configured with the necessary credentials to enable authenticating one another.
Copy of original 3GPP image for 3GPP TS 23.554, Fig. 8.2.5-1: Application Server registration
Figure 8.2.5-1: Application Server registration
(⇒ copy of original 3GPP image)
Up
Step 1.
The Application Server sends an Application Server registration request to the MSGin5G Server. The request includes security credentials required for the Application Server to register to the MSGin5G Server. The request includes the AS Service ID and Application Server Profile information as detailed in Table 9.1.2.3-1.
Step 2.
Upon receiving the request, the MSGin5G Server validates the Application Server registration request and verifies the security credentials. The authentication and authorization between Application Server and MSGin5G Server are specified in Annex Y.4 of TS 33.501.
Step 3.
The MSGin5G Server sends an Application Server registration response to the Application Server, the response includes the information elements as specified in Table 9.1.2.4-1. If the registration is successful, the MSGin5G Server stores the AS Profile information as detailed in Table 9.1.2.3-1.
Up

8.2.6  Application Server De-registrationp. 34

By de-registering, the Application Server informs the MSGin5G Server that it wishes to terminate its association with the MSGin5G Server.
The procedure assumes that the Application Server is responsible for triggering the de-registration from the MSGin5G Server. The signalling flow for Application Server de-registration is illustrated in Figure 8.2.6-1.
Pre-conditions:
  1. The Application Server is registered to the MSGin5G Server.
Copy of original 3GPP image for 3GPP TS 23.554, Fig. 8.2.6-1: Application Server de-registration
Figure 8.2.6-1: Application Server de-registration
(⇒ copy of original 3GPP image)
Up
Step 1.
The Application Server determines to de-register from the MSGin5G Server.
Step 2.
The Application Server sends an Application Server de-registration request to the MSGin5G Server that includes the AS Service ID, as detailed in Table 9.1.2.5-1.
Step 3.
The MSGin5G Server validates the Application Server de-registration request and verifies the security credentials. The authentication and authorization between Application Server and MSGin5G Server are specified in Annex Y.4 of TS 33.501. The MSGin5G Server deletes any applicable AS Profile information that it has stored.
Step 4.
The MSGin5G Server replies an Application Server de-registration response as detailed in Table 9.1.2.6-1.
Up

8.2.7  MSGin5G UE bulk registration over MSGin5G-6 reference point |R18|p. 35

When constrained devices UE-2a and UE-2b which support an MSGin5G Client perform registration to use MSGin5G UE-1 to contact with 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 and connected to the serving network via MSGin5G UE-1 successfully.
  3. how constrained device decides whether to use MSGin5G Relay UE service or MSGin5G proxy UE service and how to discover them is FFS.
  4. 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.
  5. Both the MSGin5G UEs and MSGin5G Server have been configured with the necessary credentials to enable authenticating one another.
Copy of original 3GPP image for 3GPP TS 23.554, Fig. 8.2.7-1: MSGin5G Client bulk registration
Figure 8.2.7-1: MSGin5G Client bulk registration
(⇒ copy of original 3GPP image)
Up
Step 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.
Information element Status Description
Registration urgent degreeOIndicates whether the registration request is urgent or not. If a MSGin5G UE registration request is indicated as urgent, the MSGin5G UE registration request can not be bulked handled.
Registration request expiration timeOIndicates the maximum processing time of the registration request allowed by the MSGin5G Client-2.
Step 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.
  1. whether the MSGin5G UE registration request is urgent; or
  2. whether bulk registration is supported by the MSGin5G service provider;
Step 3.
Based on step 2:
  1. if the MSGin5G UE registration request can not be bulked, MSGin5G Client-1 sends the registration request to MSGin5G Server; or
  2. 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 step 4 and 5 are skipped.
Information element Status Description
UE Service IDMUE service identifier assigned to the requesting MSGin5G UE-2.
Expected registration timeOThe expected time when the bulk registration can be handled and the MSGin5G UE registration Response can be received.
Step 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.
Step 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.
Step 6.
MSGin5G Client-2b sends an MSGin5G UE registration request and the MSGin5G UE registration request is handed as in steps 2-5.
Step 7.
The MSGin5G Client-1 finds that the conditions of sending a bulk registration request can be fulfilled, e.g.
  1. the Registration request expiration time in the MSGin5G UE registration request sent from MSGin5G Client-2a or MSGin5G Client-2b is reached;
  2. the periodic bulk registration interval is reached;or
  3. the maximum MSGin5G UE registration request number in a MSGin5G UE bulk registration request is reached.
Step 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.
Information element Status Description
Bulk registration indicatorMIndicates that this request is a MSGin5G UE bulk registration request.
Number of individual MSGin5G UE registration requestsMIndicates total number of MSGin5G UE registration requests which are bulked in this MSGin5G UE bulk registration request
List of individual MSGin5G UE registration requestM Each element in this list contains information as specified in Table 8.2.1-1.
Step 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.
  • Security aspects of bulk registration depends on SA3 and is FFS
  • Step 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.
    Information element Status Description
    Bulk registration response indicatorMIndicates that this response is a MSGin5G UE bulk registration response.
    Number of individual MSGin5G UE registration responsesMIndicates total number of MSGin5G UE registration responses which are bulked in this MSGin5G UE bulk registration response
    List of individual MSGin5G UE registration responseMEach element in this list contains information as specified in Table 8.2.1-4.
    Step 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.
    Step 12.
    MSGin5G Client-1 sends the MSGin5G UE registration Response 2a to MSGin5G Client-2a.
    Step 13.
    MSGin5G Client-1 sends the MSGin5G UE registration Response 2b to MSGin5G Client-2b.
    Up

    8.2.8  Constrained device selecting MSGin5G Relay UE or MSGin5G Proxy UE |R18|p. 38

    8.2.9  Non-MSGin5G UE bulk de-registration |R18|p. 40

    8.2.10  Non-MSGin5G UE bulk de-registration |R18|p. 42


    Up   Top   ToC