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:  19.3.0

Top   Top   Up   Prev   Next
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 Registration  8.2.0 General  8.2.1 MSGin5G UE Registration  8.2.2 MSGin5G UE De-Registration  8.2.3 Non-MSGin5G UE Registration  8.2.4 Non-MSGin5G UE De-registration  8.2.5 Application Server Registration  8.2.6 Application Server De-registration 
...

 

8.2  Registration  p. 32

8.2.0  General |R18|  p. 32

Before a UE or an Application Server can use the MSGin5G Service it needs to register with the MSGin5G Server.
The procedures of MSGin5G UE registration/de-registration are specified in clause 8.2.1 and clause 8.8.2. The procedures also apply when the MSGin5G UE uses MSGin5G services by using another UE as relay.
The procedures of Non-MSGin5G UE registration/de-registration are specified in clause 8.2.3 and clause 8.8.4.
The procedures of Application Server registration/de-registration are specified in clause 8.2.5 and clause 8.8.6.
The MSGin5G Gateway UE may use bulk registration to register more than one of MSGin5G UEs at one time if allowed by the service policy. The bulk registration procedure is specified in clause 8.2.7. Before using bulk registration, the MSGin5G UE should select a MSGin5G Gateway as specified in clause 8.2.8. If a MSGin5G Gateway UE is selected by an MSGin5G UE, the MSGin5G UE should use bulk registration over MSGin5G-6 reference point specified in clause 8.2.7 instead of the MSGin5G UE registration procedure specified in clause 8.2.1. The corresponding procedure of MSGin5G UE bulk de-registration over MSGin5G-6 reference point is specified in clause 8.2.11.
The Message Gateway may also use bulk registration/de-registration to register more than one of Non-MSGin5G UE at one time with the MSGin5G Server. The procedures of Non-MSGin5G UE bulk registration and Non-MSGin5G UE bulk de-registration are specified in clause 8.2.9 and clause 8.2.10 respectively.
Up

8.2.1  MSGin5G UE Registration  p. 32

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. The MSGin5G UE has successfully completed the Configuration procedure; alternatively, a UE Service ID and the MSGin5G Server address have been pre-configured on the MSGin5G UE.
  3. Both the MSGin5G UE and MSGin5G Server have been configured with the necessary credentials to enable authenticating one another.
Reproduction of 3GPP TS 23.554, Fig. 8.2.1-1: MSGin5G Client registration
Figure 8.2.1-1: MSGin5G Client registration
Up
Step 1.
The MSGin5G UE sends an MSGin5G UE registration request to the MSGin5G Server. The request includes the UE Service ID and may include the MSGin5G Client Profile and Requested expiration time as detailed in Table 8.2.1-1.
Information element Status Description
UE Service IDMUE service identifier assigned to the requesting MSGin5G UE.
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. See Table 8.2.1-2. The MSGin5G Server uses the information in step 5 of clause 8.9.3.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. See Table 8.2.1-3.
> MSGin5G Client Supported MSGin5G segment sizeOThe maximum payload size of the MSGin5G message can be used by the MSGin5G Server to deliver message to this MSGin5G Client. The MSGin5G message sent to this MSGin5G Client should be segmented by the MSGin5G Server if the payload size of the message is bigger than this IE as specified in clause 8.5.
The value of this IE is decided by the MSGin5G Client, and is depended on the MSGin5G Client capabilities, e.g. computing capability or application processing time limitation.
If this IE is not included, the MSGin5G Server shall use the pre-configured global value (default value is 2048 bytes) within the MSGin5G service domain.
Requested expiration timeORequested expiration time for the registration.
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. The MSGin5G Server uses the information to determine whether Store and Forward procedure applies as specified in clause 8.3.6.
Step 2.
Upon receiving the request, the MSGin5G Server initiates authentication procedures with the MSGin5G Client and authorizes the MSGin5G Client. If the registration is successful, the MSGin5G Server stores the UE Service ID and associated MSGin5G Client Profile. The UE Service ID and associated MSGin5G Client Profile should be maintained on the MSGin5G Server until one of the following cases applies:
  1. the MSGin5G UE de-registers from the MSGin5G Server as specified in clause 8.2.2;
  2. the MSGin5G UE re-registered successfully with a different MSGin5G Client Profile; In this case, the MSGin5G Server shall store the UE Service ID and associated new MSGin5G Client Profile;
  3. the MSGin5G UE registration is expired; or
  4. the MSGin5G Server deletes the MSGin5G UE registration as required by the service provider.
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. The registration expiration time may be returned either as provided by the MSGin5G client in the registration request or determined by the MSGin5G Server based on local policy.
Information element Status Description
UE Service IDMUE service identifier of the requesting MSGin5G UE.
Registration resultMIndication if the registration is success or failure.
Registration expiration time (see NOTE 1)OIndicates the expiration time of the registration.
Failure Cause (see NOTE 2)OThe reason for failure.
NOTE 1:
This IE shall only be present when the Registration is Success.
NOTE 2:
This IE shall only be present when the Registration result is Failure.
Up

8.2.2  MSGin5G UE De-Registration  p. 35

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-condition:
  1. The MSGin5G UE is registered to the MSGin5G Server.
Reproduction of 3GPP TS 23.554, Fig. 8.2.2-1: MSGin5G UE de-registration
Figure 8.2.2-1: MSGin5G UE de-registration
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 MSGin5G UE.
Step 3.
The MSGin5G Server may initiate authentication procedures with the MSGin5G Client and authorizes the MSGin5G Client. If the MSGin5G Server has authorized the MSGin5G Client successfully it deletes any UE Service ID and associated MSGin5G Client Profile that it has stored.
Step 4.
The MSGin5G Server sends 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 of the MSGin5G UE.
De-registration resultMIndication if the de-registration is success or failure.
Failure CauseOThe reason for failure.
Up

8.2.3  Non-MSGin5G UE Registration  p. 36

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 MSGin5G UEs, based on pre-provisioned information when it receives a registration request from the Non MSGin5G UE, or gets the knowledge that the Non-MSGin5G UE is ready for the MSGin5G service. After the procedure is completed, the Message Gateway may communicate the result to the Non-MSGin5G UE to enable MSGin5G Services at the Non MSGin5G UE.
The signalling flow is illustrated in Figure 8.2.3-1.
Pre-conditions:
  1. The Message Gateway has been pre-configured with the MSGin5G Server address.
  2. 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 UE Profile is available, this pre-condition enables authentication and Non- MSGin5G UE registration at the Message Server.
  3. A secured connection has been established between the Message Gateway and the MSGin5G Server.
Reproduction of 3GPP TS 23.554, Fig. 8.2.3-1: Non-MSGin5G UE registration
Figure 8.2.3-1: Non-MSGin5G UE registration
Up
Step 1.
The Message Gateway sends the Non-MSGin5G UE registration request to the MSGin5G Server. The request includes the information pre-configured to the Message Gateway or provided by the Non-MSGin5G UE (e.g. in non-MSGin5G registration or bootstrapping procedures which are out of scope of the present specification) and detailed in Table 8.2.3-1.
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.
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 Non-MSGin5G 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.
Upon receiving the request, the MSGin5G Server initiates authentication procedures with the Message Gateway on behalf of the Non-MSGin5G Client and authorises the Non-MSGin5G UE to receive the MSGin5G Service. If the registration is successful, the MSGin5G Server stores the UE Service ID and associated Non-MSGin5G UE Profile. The UE Service ID and associated Non-MSGin5G UE Profile should be maintained on the MSGin5G Server until one of the following cases applies:
  1. the Non-MSGin5G UE de-registers from the MSGin5G Server as specified in clause 8.2.4;
  2. the Non-MSGin5G UE re-registered successfully with a different Non-MSGin5G UE Profile; In this case, the MSGin5G Server shall store the UE Service ID and associated new Non-MSGin5G UE Profile;
  3. the Non-MSGin5G UE registration is expired; or
  4. the MSGin5G Server deletes the Non-MSGin5G UE registration as required by the service provider.
Step 3.
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.1-4, to the Message Gateway.
Up

8.2.4  Non-MSGin5G UE De-registration  p. 37

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.
The procedure assumes that the Message Gateway is responsible for initiating the de-registration from the MSGin5G Server on behalf of the Non-MSGin5G UE. The signaling flow for Non-MSGin5G UE de-registration is illustrated in Figure 8.2.4-1.
Pre-condition:
  1. The Message Gateway successfully performed registration with the MSGin5G Server on behalf of the Non-MSGin5G UE.
Reproduction of 3GPP TS 23.554, Fig. 8.2.4-1: Non-MSGin5G UE de-registration
Figure 8.2.4-1: Non-MSGin5G UE de-registration
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.
Step 3.
Upon receiving the request, the MSGin5G Server may initiate authentication procedures with the Message Gateway on behalf of the Non-MSGin5G Client and authorizes the Message Gateway. If the MSGin5G Server has authorized the Message Gateway successfully, it deletes any UE Service ID and associated Non-MSGin5G UE Profile that it has stored.
Step 4.
The MSGin5G Server 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 of the Non-MSGin5G UE.
De-registration resultMIndication if the de-registration is success or failure.
Failure CauseOThe reason for failure.
Up

8.2.5  Application Server Registration  p. 38

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.
Pre-conditions:
  1. The Application Server has connected to the serving network successfully.
  2. An AS Service ID has been provisioned on the Application Server.
  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.
Reproduction of 3GPP TS 23.554, Fig. 8.2.5-1: Application Server registration
Figure 8.2.5-1: Application Server registration
Up
Step 1.
The Application Server sends an Application Server registration request to the MSGin5G Server. The request may include authorization information for the Application Server to register to the MSGin5G Server. The request shall include the AS Service ID and may include Application Profile information and Requested expiration time 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 may verify the security credentials.
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 and Expected MSGin5G group list as detailed in Table 9.1.2.3-1. The Application Profile should be maintained on the MSGin5G Server until one of the following cases applies:
  1. the Application Server de-registers from the MSGin5G Server as specified in clause 8.2.6;
  2. the Application Server re-registered successfully with a different Application Profile; In this case, the MSGin5G Server shall store the AS Service ID and associated new Application Profile;
  3. the Application Server registration is expired; or
  4. the MSGin5G Server deletes the Application Server registration as required by the service provider.
Up

8.2.6  Application Server De-registration  p. 39

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.
Reproduction of 3GPP TS 23.554, Fig. 8.2.6-1: Application Server de-registration
Figure 8.2.6-1: Application Server de-registration
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. If the MSGin5G Server has authorized the Application Server successfully, it deletes any AS Profile information and Expected MSGin5G group list that it has stored.
Step 4.
The MSGin5G Server replies with an Application Server de-registration response as detailed in Table 9.1.2.6-1.
Up

Up   Top   ToC