Tech-invite3GPPspaceIETF RFCsSIP
Quick21222324252627282931323334353637384‑5x

Content for  TS 23.554  Word version:  18.0.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  Registrationp. 26

8.2.1  MSGin5G UE Registrationp. 26

The signalling flow for MSGin5G UE registration is illustrated in Figure 8.2.1-1. The procedure assumes that the MSGin5G UE is responsible for initiating registration to the MSGin5G Server in order to establish association with the MSGin5G Server to receive MSGin5G Services.
Pre-conditions:
  1. The MSGin5G UE has connected to the serving network successfully.
  2. A UE Service ID has been configured on the MSGin5G UE.
  3. The MSGin5G Server address has been provisioned on the MSGin5G UE.
  4. Both the MSGin5G UE 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.1-1: MSGin5G Client registration
Figure 8.2.1-1: MSGin5G Client registration
(⇒ copy of original 3GPP image)
Up
Step 1.
The MSGin5G UE sends an MSGin5G UE registration request to the MSGin5G Server. The request includes security credentials required for the MSGin5G Client to register to the MSGin5G Server. The request includes the UE Service ID and MSGin5G Client Profile information as detailed in Table 8.2.1-1.
Information element Status Description
UE Service IDMUE service identifier assigned to the requesting 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.
MSGin5G Client ProfileOSet of parameters describing the MSGin5G Client
> MSGin5G Client Triggering InformationO UE Identifier (i.e., MSISDN, external ID), port number(s) and associated protocol (e.g., SMS, NIDD, etc.) for device triggering. The MSGin5G Server uses the information in step 5 of clause 8.8.3. See Table 8.2.1-2.
> MSGin5G Client Communication AvailabilityO Communication availability information for the MSGin5G Client to receive MSGin5G messages. This IE informs the MSGin5G Server if the client has a specific application-level schedule/periodicity to its MSGin5G communications, which may be used in conjunction with UE reachability monitoring to determine whether and when MSGin5G communications are attempted. See Table 8.2.1-3.
> MSGin5G Client Supported Maximum MSGin5G segment sizeO The Maximum MSGin5G segment size can be used by the MSGin5G server to deliver message to the client served by it in its MSGin5G service domain. The MSGin5G message sent to the MSGin5G Client should be segmented by the MSGin5G Server serves the receiver if the message size is bigger than the MSGin5G Client Supported Maximum MSGin5G segment size. The value of this IE is decided by the MSGin5G Client, and is depended on the MSGin5G Client capabilities, e.g. supported transport, computing capability or application processing time limitation. If this IE is not included, the MSGin5G Server shall use the pre-configured global value within the MSGin5G service domain.
Information element Status Description
MSGin5G UE IDMIdentity of the UE hosting the MSGin5G Client (e.g., the External Identifier defined in TS 23.682, or an MSISDN)
MSGin5G Client PortsMList of port numbers that the MSGin5G Client listens on for device triggers from the MSGin5G Server. Also included with each port number is an associated protocol (e.g., SMS, NIDD, etc.).
Information element Status Description
Scheduled communication timeMTime when the UE becomes available for communication.
Communication duration timeMDuration time of periodic communication.
Periodic communication indicatorOIdentifies whether the client communicates periodically or not, e.g., on demand.
Periodic communication intervalOInterval Time of periodic communication. This IE is mandatory if the Periodic communication indicator indicates periodic communications.
Data size indicationOIndicates the expected data size to be exchanged during the communication duration.
Store and forward optionOIndicates opting out of store and forward services for incoming MSGin5G requests.
Step 2.
Upon receiving the request, the MSGin5G Server validates the registration request and verifies the security credentials.
Step 3.
The MSGin5G Server sends an MSGin5G UE registration response to the MSGin5G UE. The response includes the information elements as detailed in Table 8.2.1-4. If the registration is successful, the MSGin5G Server stores the UE Service ID and associated MSGin5G Client Profile information.
Information element Status Description
UE Service IDMUE service identifier assigned to the requesting MSGin5G UE.
Registration resultMIndication if the registration is success or failure
Failure CauseOThe reason for failure
Up

8.2.2  MSGin5G UE De-Registrationp. 29

By de-registering, the MSGin5G UE informs the MSGin5G Server that it wishes to terminate its association with the MSGin5G Server.
The procedure assumes that the MSGin5G UE is responsible for initiating the de-registration from the MSGin5G Server. The signalling flow for MSGin5G UE de-registration is illustrated in Figure 8.2.2-1.
Pre-conditions:
  1. The MSGin5G UE is registered to the MSGin5G Server.
Copy of original 3GPP image for 3GPP TS 23.554, Fig. 8.2.2-1: MSGin5G UE de-registration
Figure 8.2.2-1: MSGin5G UE de-registration
(⇒ copy of original 3GPP image)
Up
Step 1.
The MSGin5G UE determines to de-register from the MSGin5G Server.
Step 2.
The MSGin5G UE sends an MSGin5G UE de-registration request to the MSGin5G Server that includes the UE Service ID, as detailed in Table 8.2.2-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 MSGin5G UE de-registration request and verifies the security credentials. The MSGin5G Server deletes any applicable UE Service ID and associated MSGin5G Client Profile information that it has stored.
Step 4.
The MSGin5G Server an MSGin5G UE de-registration response as detailed in Table 8.2.2-2 to the MSGin5G UE.
Information element Status Description
UE Service IDMUE service identifier assigned to the non-SGin5G UE.
De-registration resultMIndication if the de-registration is success or failure
Failure CauseOThe reason for failure
Up

Up   Top   ToC