Tech-invite  3GPPspace  IETFspace
21  22  23  24  25  26  27  28  29  31  32  33  34  35  36  37  38  4‑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.3 Non-MSGin5G UE Registration  8.2.4 Non-MSGin5G UE De-registration 
...

 

8.2.3  Non-MSGin5G UE Registration  p. 31

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 performs registration with the MSGin5G Server on behalf of the Non-3GPP UEs, based on the registration request from the Non-3GPP UE or on pre-provisioned information. After the procedure is complete, the Message Gateway may communicate the result to the UE to enable MSGin5G Services at the Non-3GPP UEs.
The signalling flow is illustrated in Figure 8.2.3-1.
Pre-conditions:
  1. The Message Gateway has been pre-provisioned with the MSGin5G Server address and UE Service ID for a Non-3GPP UE.
  2. Both the Non-3GPP UE and Message Gateway have been configured with the necessary credentials to enable authentication and Non-3GPP UE registration at the Message Gateway.
  3. A secured connection has been established between the Message Gateway and the MSGin5G Server.
Copy of original 3GPP image for 3GPP TS 23.554, Fig. 8.2.3-1: Non-MSGin5G UE registration
Figure 8.2.3-1: Non-MSGin5G UE registration
(⇒ copy of original 3GPP image)
Up
Step 1.
The Non-MSGin5G UE registers at the Message Gateway. Alternatively, the Non-MSGin5G UE registration information is configured at the Message Gateway. The Message Gateway, based on the registration request and pre-provisioned information, registers the UE with the MSGin5G Server, a corresponding UE Service ID and, if available, a Non-MSGin5G UE profile.
Information element Status Description
UE Service IDMUE service identifier assigned to the requesting Non-MSGin5G UE.
MGW Service IDMThe service identifier of the Message Gateway performing registration on behalf of a Non-MSGin5G UE
UE credential informationM The information needed to authenticate the UE. The authentication and authorization between MSGin5G client and MSGin5G Server are specified in Annex Y.2 of TS 33.501.
Non-MSGin5G UE ProfileOSet of parameters describing the Non-MSGin5G UE
> Non-MSGin5G UE Communication AvailabilityO Communication availability information for the Non-MSGin5G UE to receive messages. This IE informs the MSGin5G Server if the UE has a specific application-level schedule/periodicity to its MSGin5G communications, which may be used to determine whether and when MSGin5G communications are attempted. See Table 8.2.1-3.
Step 2.
The Message Gateway sends the Non-MSGin5G UE registration request to the MSGin5G Server. The request includes the information detailed in Table 8.2.3-1.
Step 3.
The MSGin5G Server authenticates the Message Gateway and authorises the Non-MSGin5G UE to receive the MSGin5G Service. The MSGin5G Server records the UE's availability for MSGin5G Service.
Step 4.
The MSGin5G Server returns the result of the registration in the Non-MSGin5G UE registration response message with the information detailed in Table 8.2.2-2.
Up

8.2.4  Non-MSGin5G UE De-registration  p. 33

The Message Gateway performs de-registration with the MSGin5G Server on behalf of the Non-MSGin5G UEs, in order to terminate services from the MSGin5G Server. After the procedure is complete, the Message Gateway communicates the result to the requesting UE.
The procedure assumes that the Non-MSGin5G UE is responsible for initiating the de-registration from the MSGin5G Server. The signaling flow for Non-MSGin5G UE de-registration is illustrated in Figure 8.2.4-1.
Pre-conditions:
  1. The Message Gateway successfully performed registration with the MSGin5G Server on behalf of the Non-MSGin5G UE.
Copy of original 3GPP image for 3GPP TS 23.554, Fig. 8.2.4-1: Non-MSGin5G UE de-registration
Figure 8.2.4-1: Non-MSGin5G UE de-registration
(⇒ copy of original 3GPP image)
Up
Step 1.
The Message Gateway determines to de-register the Non-MSGin5G UE with the MSGin5G Server.
Step 2.
The Message Gateway sends a Non-MSGin5G UE de-registration request to the MSGin5G Server that includes the UE Service ID associated with the Non-MSGin5G UE, as shown in Table 8.2.4-1.
Information element Status Description
UE Service IDMUE service identifier assigned to the Non-MSGin5G UE.
UE credential informationM The information needed to authenticate the UE. The authentication and authorization between MSGin5G client and MSGin5G Server are specified in Annex Y.2 of TS 33.501.
Step 3.
The MSGin5G Server validates the Non-MSGin5G UE de-registration request and verifies the security credentials. The MSGin5G Server deletes any applicable MSGin5G Client Profile information that it has stored.
Step 4.
The MSGin5G Server deletes any applicable information that it has stored and replies with a Non-MSGin5G UE de-registration response as shown in Table 8.2.4-2.
Information element Status Description
UE Service IDMUE service identifier assigned to the Non-MSGin5G UE.
De-registration resultMIndication if the de-registration is success or failure
Up

Up   Top   ToC