Tech-invite  3GPPspace  IETF RFCs  SIP
index  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.11 Constrained devices in MSGin5G Service  8.11.1 General  8.11.2 Constrained device registration to use gateway UE  8.11.3 Constrained device Deregistration from using gateway UE  8.11.4 Constrained device sending message using Gateway UE  8.11.5 Constrained device receiving message via Gateway UE 
...

 

8.11  Constrained devices in MSGin5G Service  p. 117

8.11.1  General  p. 117

This clause specifies the procedures for the constrained device UE-2 which does not support an MSGin5G Client to perform registration to use MSGin5G UE-1 as gateway UE and to send messages and receive messages using MSGin5G UE-1 which is acting as a gateway UE for the UE-2. The communications between MSGin5G UE-1 and UE-2 is over MSGin5G-5 reference point.
Up

8.11.2  Constrained device registration to use gateway UE  p. 118

The signalling flow for registration of Application Client-2 on the UE-2 (which is a Constrained UE) with MSGin5G Client-1 on MSGin5G UE-1 to use it as a gateway UE is illustrated in Figure 8.11.2-1.
Pre-conditions:
  1. The MSGin5G UE-1 is configured with information to recognize and authorize UE-2.
  2. The UE-2 is a Constrained UE and does not have access network connection to connect with the MSGin5G Server.
  3. The UE-2 has discovered MSGin5G UE-1 is having connectivity to the MSGin5G Server and offers gateway UE functionality.
  4. The UE-2 is using NR-PC5 to communicate with MSGin5G UE-1.
Copy of original 3GPP image for 3GPP TS 23.554, Fig. 8.11.2-1: Registration of application client on UE-2 with MSGin5G Client-1 to use gateway UE functionality
Figure 8.11.2-1: Registration of application client on UE-2 with MSGin5G Client-1 to use gateway UE functionality
(⇒ copy of original 3GPP image)
Up
Step 1.
An Application Client-2 on the UE-2 registers with MSGin5G Client-1 in MSGin5G UE-1 to request MSGin5G Client-1 to act as a gateway UE. The request message includes information elements as specified in Table 8.11.2-1.
Information element Status Description
Layer-2 IDMLayer-2 identity of UE-2
Application IDMApplication ID of the application client on UE-2
Credential informationMUE-2 credential information
Step 2.
Upon receiving the request from the Application Client-2, the MSGin5G Client-1 authorizes the Application Client-2 on UE-2 to use gateway functionality and MSGin5G Client-1 stores the mapping between Application ID and Layer-2 ID of the UE-2.
Step 3.
The MSGin5G Client-1 sends response to the Application Client-2. The response message includes information elements as specified in Table 8.11.2-2.
Information element Status Description
ResultMIndicates success or failure of the request
Registration IDOIdentifies registration. This IE is included only if Result IE is set to success.
Failure reasonOIndicates failure reason. This IE is included only if Result IE is set to failure.
Up

8.11.3  Constrained device Deregistration from using gateway UE  p. 119

The signalling flow for deregistration of Application Client-2 on the UE-2 (which is a Constrained UE) with MSGin5G Client-1 to discontinue use of gateway UE functionality is illustrated in Figure 8.11.3-1.
Pre-conditions:
  1. The UE-2 is a Constrained UE and is successfully registered with MSGin5G UE-1 acting as a gateway UE.
Copy of original 3GPP image for 3GPP TS 23.554, Fig. 8.11.3-1: Deregistration of Application Client on UE-2 with MSGin5G Client-1 on MSGin5G UE-1 to discontinue use of gateway UE functionality
Figure 8.11.3-1: Deregistration of Application Client on UE-2 with MSGin5G Client-1 on MSGin5G UE-1 to discontinue use of gateway UE functionality
(⇒ copy of original 3GPP image)
Up
Step 1.
An Application Client-2 on the UE-2 deregisters with MSGin5G Client-1 in MSGin5G UE-1 to discontinue usage of gateway UE functionality of MSGin5G UE-1. The request message includes information elements as specified in Table 8.11.3-1.
Information element Status Description
Registration IDMIdentifies the registration
Step 2.
Upon receiving the request from the Application Client-2, the MSGin5G Client-1 removes the mapping between Application ID and Layer-2 ID of the UE-2. The MSGin5G Client-1 sends response to the Application Client-2 on UE-2. The response message includes information elements as specified in Table 8.11.2-2.
Up

8.11.4  Constrained device sending message using Gateway UE  p. 119

The signalling flow for the Application Client-2 on the UE-2 (which is a Constrained UE) to send message using gateway UE functionality on MSGin5G UE-1 is illustrated in Figure 8.11.4-1.
Pre-conditions:
  1. The MSGin5G UE-1 is connected to an access network that provides connectivity to the MSGin5G Server.
  2. The UE-2 is Constrained UE and is successfully registered with MSGin5G UE-1 acting as a gateway UE.
Copy of original 3GPP image for 3GPP TS 23.554, Fig. 8.11.4-1: Application Client-2 on UE-2 sends message using gateway UE functionality on MSGin5G UE-1
Figure 8.11.4-1: Application Client-2 on UE-2 sends message using gateway UE functionality on MSGin5G UE-1
(⇒ copy of original 3GPP image)
Up
Step 1.
An Application Client-2 on the UE-2 sends a request to send MSGin5G message to the MSGin5G Client-1. The information elements defined in Table 8.11.4-1 are included in the message.
Information element Status Description
Recipient addressOIndicates details of the recipient. This IE is mandatory to initiate Point-to-Point messaging and Point-to-Application messaging.
Recipient Group addressOIndicates target group.
This IE is mandatory to initiate Group messaging.
Application IDOIdentifies the application(s) for which the payload is intended.
PayloadMPayload of the message.
MSGin5G Server/Client is unaware of the content.
Delivery status requiredOIndicates whether delivery status is required or not
Step 2.
Upon receiving the request from the Application Client-2 in UE-2, the MSGin5G Client-1 constructs the related IEs specified in Table 8.3.2-1 and sends Point-to-Point Message, Point-to-Application Message or Group Message based on these Ies.
  1. if the size of the received message exceeds the maximum allowed packet size, the MSGin5G Client-1 sends the message as specified in clause 8.5; and
  2. If the size of the received message does not exceed the maximum allowed packet size, the MSGin5G Client-1 sends the message as specified in clause 8.7.
Step 3.
The MSGin5G Client-1 sends response to send MSGin5G message to Application Client-2 on UE-2. The response message includes information elements as specified in Table 8.11.4-2.
Information element Status Description
ResultMIndicates success or failure of the request
Failure reasonOIndicates failure reason. This IE is included only if Result IE is set to failure.
Step 4.
If delivery status is requested while sending the message in step 1, the MSGin5G Client-1 may receive MSGin5G message delivery status report from the MSGin5G Server.
Step 5.
Upon receiving the MSGin5G message delivery status report, the MSGin5G Client-1 sends the message delivery status report to the Application Client-2 on UE-2. The message delivery status report includes information elements as specified in Table 8.11.4-3.
Information element Status Description
Delivery statusMIndicates delivery status
Up

8.11.5  Constrained device receiving message via Gateway UE  p. 122

The signalling flow for Application Client-2 on the UE-2 (which is Constrained UE) to receive message (Group message, Point-to-Point message or Application-to-Point message) using gateway UE functionality on MSGin5G UE-1 is illustrated in Figure 8.11.5-1.
Pre-conditions:
  1. The MSGin5G UE-1 is connected to an access network that provides connectivity to the MSGin5G Server.
  2. The UE-2 is Constrained UE and is successfully registered with MSGin5G UE-1 acting as a gateway UE.
Copy of original 3GPP image for 3GPP TS 23.554, Fig. 8.11.5-1: UE-2 receives message using gateway UE functionality on MSGin5G UE-1
Figure 8.11.5-1: UE-2 receives message using gateway UE functionality on MSGin5G UE-1
(⇒ copy of original 3GPP image)
Up
Step 1.
The MSGin5G Client-1 receives either a Group message or a Point-to-Point message or Application-to-Point message as specified in clause 8.2.3 for the Application Client-2 on UE-2 for which the MSGin5G Client-1 is acting as Gateway UE. The MSGin5G Client-1 performs reassembly if the received message is segmented. The MSGin5G Client-1 may also perform segment recovery procedure as specified in clause 8.4.6 to recover missing segments.
Step 2.
Upon successfully receiving a message for the Application Client-2 on UE-2, the MSGin5G Client-1 sends message received request to Application Client-2 based on Application ID on the UE-2. The request includes information elements as specified in Table 8.11.5-1.
Information element Status Description
Originator addressOIndicates details of the originator. This IE is mandatory for Point-to-Point messaging and Application-to-Point messaging.
Group Service addressOIndicates group for which the message is received.
This IE is mandatory for Group Message.
PayloadMPayload of the message.
MSGin5G Server/Client is unaware of the content.
Delivery status requiredOIndicates whether delivery status is required or not
Priority typeO Application priority level requested for this message as specified in Table 8.3.2-1.
Step 3.
Upon successfully receiving the message, the Application Client-2 on UE-2 sends the message received response to the MSGin5G Client-1.
Step 4.
If delivery status is requested in the received message, the Application Client-2 on UE-2 sends message delivery status to the MSGin5G Client-1.
Step 5.
Upon receiving the delivery status, the MSGin5G Client-1 sends message delivery status report to the MSGin5G Server.
Up

Up   Top   ToC