Content for TS 23.554 Word version: 19.3.0
1…
4…
5…
5.3…
5.5…
6…
7…
8…
8.2…
8.2.7…
8.2.11
8.3…
8.3.5…
8.4…
8.4.3
8.5…
8.6…
8.7…
8.7.2…
8.7.3…
8.7.4…
8.7.5…
8.7.6…
8.8…
8.9…
8.10…
8.11…
9…
9.2…
10…
11…
8.2.7 MSGin5G UE bulk registration over MSGin5G-6 reference point
8.2.8 Constrained device with MSGin5G Client selecting MSGin5G Gateway UE
8.2.9 Non-MSGin5G UE bulk registration
8.2.10 Non-MSGin5G UE bulk de-registration
...
...
8.2.7 MSGin5G UE bulk registration over MSGin5G-6 reference point |R18| p. 40
When MSGin5G UE-1 and UE-2, which support an MSGin5G Client, perform registration via MSGin5G Gateway UE to contact the MSGin5G Server, the MSGin5G Gateway service functionality in the MSGin5G Gateway UE may decide to use bulk registration procedure specified in this clause based on the registration request sent from MSGin5G Clients in MSGin5G UE-1 and MSGin5G UE-2, if allowed by service policy. The procedure for MSGin5G UE bulk registration is illustrated in Figure 8.2.7-1.
Pre-conditions:
- The MSGin5G Gateway UE has registered to the MSGin5G Server successfully.
- MSGin5G UE-1 and MSGin5G UE-2 have discovered and selected an MSGin5G Gateway UE as specified in clause 8.2.8 and connected to the serving network via MSGin5G Gateway UE successfully.
- UE Service IDs and the MSGin5G Server addresses have been configured on the MSGin5G Gateway UE, MSGin5G UE-1 and MSGin5G UE-2. All these MSGin5G UEs are served by a same MSGin5G Server.
- Both the MSGin5G UEs and MSGin5G Server have been configured with the necessary credentials to enable authenticating one another.
Step 1.
The MSGin5G Client-1 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-1 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 degree | O | Indicates whether the registration request is urgent or not. |
| Wait time | O | Indicates the maximum wait time of the registration request allowed by the MSGin5G Client which sent the registration request before the bulk registration request is sent to the MSGin5G Server. |
Upon receiving the MSGin5G UE registration request, the MSGin5G Gateway Client checks whether this request can be queued for bulk-handling based on the service policy and the information included in the MSGin5G UE registration request, e.g. whether the MSGin5G UE registration request is urgent.
Step 3.
Based on step 2:
- if the MSGin5G UE registration request is urgent, MSGin5G Gateway Client may also include other registration requests; or
- if the MSGin5G UE registration request can be bulk-handled, MSGin5G Gateway Client sends a bulk registration notification to MSGin5G Client-1 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.
| Information element | Status | Description |
|---|---|---|
| UE Service ID | M | UE service identifier assigned to the requesting MSGin5G UE. |
| Expected registration time | O | The expected time when the bulk registration can be handled and the MSGin5G UE registration Response can be received. |
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 Gateway Client.
Step 5.
The MSGin5G Gateway Client sends the MSGin5G UE registration response to MSGin5G Client-1. The MSGin5G Client-1 handles the MSGin5G UE registration response as specified in clause 8.2.1 and skips all the remaining steps in the present clause.
Step 6.
MSGin5G Client-2 sends an MSGin5G UE registration request and the MSGin5G UE registration request is handed as in steps 2-5.
Step 7.
The MSGin5G Gateway Client finds that the conditions of sending a bulk registration request can be fulfilled, e.g.
Step 8.
- the registration request expiration time in the MSGin5G UE registration request sent from MSGin5G Client-1 or MSGin5G Client-2 is reached; or
- the periodic bulk registration interval is reached; or
- the maximum MSGin5G UE registration request number in a MSGin5G UE bulk registration request is reached.
The MSGin5G Gateway Client 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 |
|---|---|---|
| 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. |
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 individually as specified in clause 8.2.1.
Step 10.
The MSGin5G Server includes all corresponding MSGin5G UE registration responses in an MSGin5G UE bulk registration response and sends it to MSGin5G Gateway Client. The Information Elements specified in Table 8.2.7-4 are included in the 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. |
Step 11.
Upon receiving the MSGin5G UE bulk registration response, the MSGin5G Gateway Client splits the MSGin5G UE bulk registration response into multiple individual MSGin5G UE registration responses. Each individual MSGin5G UE registration response contains information as specified in Table 8.2.1-4.
Step 12.
MSGin5G Gateway Client sends the MSGin5G UE registration Response 1 to MSGin5G Client-1.
Step 13.
MSGin5G Gateway Client sends the MSGin5G UE registration Response 2 to MSGin5G Client-2.
8.2.8 Constrained device with MSGin5G Client selecting MSGin5G Gateway UE |R18| p. 43
The signalling flow for MSGin5G Client-2 in the MSGin5G UE-2 (which is a constrained device) to request other MSGin5G UEs supporting MSGin5G Gateway service functionality to provide their configuration is illustrated in Figure 8.2.8-1.
Pre-conditions:
- MSGin5G UE-2 is not able to communicate with MSGin5G Server directly;
- MSGin5G UE-2 has discovered nearby MSGin5G UEs using ProSe direct discovery procedure as specified in TS 23.304 and the 5G ProSe Direct Communication is established between MSGin5G UE-2 and nearby MSGin5G UE-1 and MSGin5G UE-3 as specified in TS 23.304.
- An MSGin5G UE-3 supports MSGin5G Gateway service functionality (i.e. MSGin5G UE-3 is an MSGin5G Gateway UE) and an MSGin5G UE-1 does not support MSGin5G Gateway service functionality (i.e. MSGin5G UE-1 is not an MSGin5G Gateway UE).
- The UE service ID has been pre-configured on the MSGin5G UE-2.
Step 1.
The MSGin5G Client-2 in MSGin5G UE-2 (which is a constrained UE) sends messages to all surrounding MSGin5G UEs (using ProSe Direction communication as specified in TS 23.304) to provide their gateway configuration if MSGin5G Gateway service functionality is supported by the MSGin5G UE, i.e. the MSGin5G UE is a MSGin5G Gateway UE. The request message includes information elements as specified in Table 8.2.8-1.
| Information element | Status | Description |
|---|---|---|
| Layer-2 ID | M | Layer-2 identity of UE-2. |
| UE service ID | M | UE service identifier of the UE-2. |
| MSGin5G UE ID | O | MSGin5G device identifier of the UE-2. |
| Required packet size | M | Maximum allowed packet size of the UE-2. |
Step 2.
Upon receiving the request from the MSGin5G Client of MSGin5G UE-2, the MSGin5G UE-3 supporting the MSGin5G Gateway service functionality sends the response for the gateway configuration. The response message includes information elements as specified in Table 8.2.8-2. The MSGin5G UE-1 does not support the MSGin5G Gateway service functionality and ignores the request for gateway UE configuration, i.e. should not send a corresponding response.
| Information element | Status | Description |
|---|---|---|
| Layer-2 ID | M | Layer-2 identity of UE-1. |
| UE service ID | M | UE service identifier of the UE-1. |
| MSGin5G UE ID | O | MSGin5G device identifier of the UE-1. |
| Allowed packet size | M | Maximum allowed packet size of the UE-2. |
Step 3.
Once MSGin5G UE has selected the MSGin5G Gateway UE, the MSGin5G UE indicates the selected MSGin5G Gateway UE by registering to use the gateway service. The signalling flow for MSGin5G Client in the MSGin5G UE (which is a constrained device) to register itself to use Gateway service of the MSGin5G Gateway UE is illustrated in Figure 8.2.8-2.
If the MSGin5G UE-2 receives responses from multiple different MSGin5G Gateway UEs, then the MSGin5G Client of the MSGin5G UE-2 selects an MSGin5G Gateway UE whose value of the Allowed packet size is equal or more than the value of the Required packet size of the MSGin5G UE-2. If the value of the Allowed packet size is less than the value of the Required packet size for all MSGin5G Gateway UE, then the MSGin5G Client of the MSGin5G UE-2 selects the MSGin5G Gateway UE with the maximum value of the Allowed packet size among all MSGin5G Gateway UEs and further sets the maximum allowed packet size of the constrained UE to the value of the Allowed packet size of the selected MSGin5G Gateway UE.
If the MSGin5G UE-2 receives responses from multiple MSGin5G Gateway UEs which serve different domains, the MSGin5G UE-2 shall select the MSGin5G Gateway UE that serves the same domain as the MSGin5G UE-2 does, based on the UE service ID.
Step 1.
Upon selecting the MSGin5G Gateway UE, the MSGin5G Client of the MSGin5G UE sends a Gateway registration request to register with the selected MSGin5G Gateway UE to request the use of gateway service. The request message includes the UE service ID and may include the MSGin5G UE ID of the MSGin5G UE (i.e. constrained UE) and the time till when constrained device is intended to use the gateway service from the selected MSGin5G Gateway UE. The information elements are specified in Table 8.2.8-3.
| Information element | Status | Description |
|---|---|---|
| UE service ID | M | UE service identifier of the MSGin5G UE. |
| MSGin5G UE ID | O | Unique identifier that represents the MSGin5G UE (i.e. the device identifier of the MSGin5G UE). |
| Time till | O | The time when constrained device is intended to use the gateway service. |
Step 2.
Upon receiving the request from the MSGin5G Client of the MSGin5G UE, the MSGin5G Gateway Client in MSGin5G Gateway UE checks whether the MSGin5G UE is authorized to use the gateway service or not.
Step 3.
The MSGin5G Gateway Client in MSGin5G Gateway UE sends the response message with the status of the registration. If the registration is successful, the response message includes parameters like the Accepted time till when the constrained device is allowed to use the gateway service from the selected MSGin5G Gateway UE. The information elements are specified in Table 8.2.8-4.
| Information element | Status | Description |
|---|---|---|
| UE Service ID | M | UE service identifier of the requesting MSGin5G UE. |
| Registration result | M | Indication if the registration is success or failure. |
| Accepted time till | O | Indicates the time when constrained device is allowed to use the gateway service if the constrained device was authorized succesfully. |
| Failure Cause | O | The reason for failure. This IE should be included if the Registration result is failure. |
8.2.9 Non-MSGin5G UE bulk registration |R18| p. 46
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:
- The Message Gateway has been pre-configured with the MSGin5G Server address.
- The Message Gateway has been configured with the necessary information as specified in clause 8.1.3. If the UE Service ID and Non-MSGin5G UE credentials have been configured and the Non-MSGin5G UEs' Profile is available, this pre-condition enables authentication and Non- MSGin5G UEs registration at the Message Server.
- A secured connection has been established between the Message Gateway and the MSGin5G Server.
Step 1.
The Message Gateway determines to perform Non-MSGin5G UE bulk registration.
Step 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.
| 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. |
Step 3.
Upon receiving the Non-MSGin5G UE bulk registration request, the MSGin5G Server processes each of the UE registrations from the list individually as specified in clause 8.2.3. For each individual Non-MSGin5G UE registration that successful, the MSGin5G Server stores that UE Service ID and associated Non-MSGin5G UE Profile information.
Step 4.
The MSGin5G Server includes all corresponding MSGin5G UE registration responses in a Non-MSGin5G UE bulk registration response and sends it to the Message Gateway. The Information Elements specified in Table 8.2.9-2 are included in the Non-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. |
8.2.10 Non-MSGin5G UE bulk de-registration |R18| p. 47
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:
- The Message Gateway successfully performed registration with the MSGin5G Server on behalf of a set of Non-MSGin5G UEs.
Step 1.
The Message Gateway determines to perform Non-MSGin5G UE bulk de-registration.
Step 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.
| 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. |
Step 3.
Upon receiving the request, the MSGin5G Server processes each of the UE de-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.
Step 4.
The MSGin5G Server replies with a Non-MSGin5G UE bulk de-registration response as shown in Table 8.2.10-2.
| 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. |
