8.2.10 Non-MSGin5G UE bulk de-registration
23.5543GPPApplication architecture for MSGin5G ServiceRelease 18Stage 2TS
The procedure assumes that the Message Gateway is responsible for initiating the bulk de-registration from the MSGin5G Server on behalf of the Non-MSGin5G UEs. The signaling flow for Non-MSGin5G UE bulk de-registration is illustrated in figure 8.2.10-1.
Pre-conditions:
1. The Message Gateway successfully performed registration with the MSGin5G Server on behalf of a set of Non-MSGin5G UEs.
Figure 8.2.10-1: Non-MSGin5G UE bulk de-registration
1. The Message Gateway determines to perform Non-MSGin5G UE bulk de-registration.
NOTE: The conditions of whether the Non-MSGin5G UEs can be bulked de-registered are implementation specific and out of the scope of the current specification.
2. The Message Gateway sends a Non-MSGin5G UE bulk de-registration request to the MSGin5G Server. The Information Elements specified in table 8.2.10-1 are included in the Non-MSGin5G UE bulk de-registration request.
Table 8.2.10y-1: Non-MSGin5G UE bulk de-registration request
|
Information element |
Status |
Description |
|
Number of individual MSGin5G UE de-registration requests |
M |
Indicates total number of Non-MSGin5G UE de-registration requests which are bulked in this Non-MSGin5G UE bulk de-registration request |
|
List of individual UE Service ID |
M |
Each element in this list contains a UE service identifier assigned to the Non-MSGin5G UE. |
3. Upon receiving the request, the MSGin5G Server processes each of the UE registration from the list individually as specified in clause 8.2.4. The MSGin5G Server deletes any applicable UE Service ID in the List of individual UE Service ID and associated MSGin5G Client Profile information that it has stored.
Editor’s note: Security aspect of Non-MSGin5G UE bulk de-registration is the responsibility of SA3.
4. The MSGin5G Server replies with a Non-MSGin5G UE bulk de-registration response as shown in table 8.2.10‑2.
Table 8.2.10-2: Non-MSGin5G UE bulk registration response
|
Information element |
Status |
Description |
|
Number of individual Non-MSGin5G UE de-registration responses |
M |
Indicates total number of Non-MSGin5G UE de-registration responses which are bulked in this Non-MSGin5G UE bulk de-registration response |
|
List of individual Non-MSGin5G UE de-registration response |
M |
Each element in this list contains information as specified in Table 8.2.4-2. |
8.2.11 MSGin5G UE bulk de-registration over MSGin5G-6 reference pointThe MSGin5G UE-1 may also decide to use bulk de-registration procedure specified in this clause based on the de-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 de-registration is illustrated in figure 8.2.11-1.
Pre-conditions:
1. The MSGin5G UE-1 has registered to the MSGin5G Server successfully.
2. MSGin5G UE-2a and MSGin5G UE-2b have registered to the MSGin5G Server via MSGin5G UE-1 successfully and MSGin5G UE-1 acts as MSGin5G Proxy UE as specified in clause 8.2.8.
Figure 8.2.11-1: MSGin5G UE bulk de-registration
1. The MSGin5G Client-2a sends an MSGin5G UE de-registration request to the MSGin5G Server as specified in clause 8.2.2, In addition to the Information Elements specified in table 8.2.2-1, the MSGin5G Client-2a may also add the Information Elements specified in table 8.2.11-1 in the MSGin5G UE de-registration request.
Table 8.2.11-1: MSGin5G UE de-registration request
|
Information element |
Status |
Description |
|
De-registration urgent degree |
O |
Indicates whether the de-registration request is urgent or not. If a MSGin5G UE de-registration request is indicated as urgent, the MSGin5G UE de-registration request cannot be bulk-handled. |
|
De-registration request expiration time |
O |
Indicates the maximum processing time of the de-registration request allowed by the MSGin5G Client-2. |
2. Upon receiving the MSGin5G UE de-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 de-registration request is urgent; or
b) whether bulk de-registration is supported by the MSGin5G service provider;
NOTE 1: Whether bulk de-registration is supported can be configured in the MSGin5G Client-1.
NOTE 2: The bulk de-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 de-registration request cannot be bulked, MSGin5G Client-1 forwards the de-registration request to MSGin5G Server; or
b) if the MSGin5G UE de-registration request can be bulked, MSGin5G Client-1 sends a bulk de-registration notification to MSGin5G Client-2 and caches/stores the MSGin5G UE de-registration request until the bulk de-registration conditions can be fulfilled. The Information Elements specified in table 8.2.11-2 are included in the bulk de-registration notification. The steps 4 and 5 are skipped.
Table 8.2.11-2: bulk de-registration notification
|
Information element |
Status |
Description |
|
UE Service ID |
M |
UE service identifier assigned to the requesting MSGin5G UE-2. |
|
Expected de-registration time |
O |
The expected time when the bulk de-registration can be handled and the MSGin5G UE de-registration response can be received. |
4. The MSGin5G Server handles the MSGin5G UE de-registration request as specified in clause 8.2.2 and sends the corresponding MSGin5G UE de-registration response to MSGin5G Client-2a.
5. The MSGin5G Client-1 sends the MSGin5G UE de-registration response to MSGin5G Client-2a. The MSGin5G Client-2a handles the MSGin5G UE de-registration response as specified in clause 8.2.2 and skips all the remaining steps in this clause.
6. MSGin5G Client-2b sends an MSGin5G UE de-registration request and the MSGin5G UE de-registration request is handed as in steps 2-5.
7. The MSGin5G Client-1 finds that the conditions of sending a bulk de-registration request can be fulfilled, e.g.
a) the de-registration request expiration time in the MSGin5G UE de-registration request sent from MSGin5G Client-2a or MSGin5G Client-2b is reached; or
b) the periodic bulk de-registration interval is reached; or
c) the maximum MSGin5G UE de-registration request number in a MSGin5G UE bulk de-registration request is reached.
NOTE 3: The maximum de-registration time, periodic bulk de-registration interval and maximum MSGin5G UE de-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 de-registration requests in an MSGin5G UE bulk de-registration request and sends it to the MSGin5G Server. The Information Elements specified in table 8.2.11-3 are included in the MSGin5G UE bulk de-registration request.
Table 8.2.11-3: MSGin5G UE bulk de-registration request
|
Information element |
Status |
Description |
|
Number of individual MSGin5G UE de-registration requests |
M |
Indicates total number of MSGin5G UE de-registration requests which are bulked in this MSGin5G UE bulk de-registration request |
|
List of individual MSGin5G UE de-registration request |
M |
Each element in this list contains information as specified in Table 8.2.2-1. |
9. Upon receiving the MSGin5G UE bulk de-registration request, the MSGin5G Server processes each of the MSGin5G UE de-registration from the list individually as specified in clause 8.2.2.
Editor’s note: Security aspects of MSGin5G UE bulk de-registration is the responsibility of SA3.
10. The MSGin5G Server includes all corresponding MSGin5G UE de-registration responses in an MSGin5G UE bulk de-registration response and sends it to MSGin5G Client-1. The Information Elements specified in table 8.2.11-4 are included in the MSGin5G UE bulk de-registration response.
Table 8.2.11-4: MSGin5G UE bulk de-registration response
|
Information element |
Status |
Description |
|
Number of individual MSGin5G UE de-registration responses |
M |
Indicates total number of MSGin5G UE de-registration responses which are bulked in this MSGin5G UE bulk de-registration response |
|
List of individual MSGin5G UE de-registration response |
M |
Each element in this list contains information as specified in Table 8.2.2-2 |
11. Upon receiving the MSGin5G UE bulk de-registration response, the MSGin5G Client-1 splits the MSGin5G UE bulk de-registration response into multiple individual MSGin5G UE de-registration response, each individual MSGin5G UE de-registration response contains information as specified in Table 8.2.2-2.
12. MSGin5G Client-1 sends the MSGin5G UE de-registration Response 2a to MSGin5G Client-2a.
13. MSGin5G Client-1 sends the MSGin5G UE de-registration Response 2b to MSGin5G Client-2b.