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.11 Application Client UE in MSGin5G Service 8.11.1 General 8.11.2 Application Client registration using MSGin5G Client 8.11.3 Application Client de-registration using MSGin5G Client 8.11.4 Application Client sending a message using MSGin5G Client 8.11.5 Application Client receiving message via MSGin5G Client on another UE
...

8.11 Application Client UE in MSGin5G Service p. 126

8.11.1 General p. 126

This clause specifies the procedures for an Application Client to perform Application Client registration, to send messages and receive messages using MSGin5G Client regardless whether the Application Client resides on UE-1 or UE-2. The communication between Application Client and MSGin5G Client is over MSGin5G-5 reference point.

8.11.2 Application Client registration using MSGin5G Client p. 126

The signalling flow for registration of Application Client with MSGin5G Client on MSGin5G UE-1 to use MSGin5G service is illustrated in Figure 8.11.2-1.

Pre-conditions:

The MSGin5G UE-1 is configured with information to recognize and authorize UE-2 if the Application Client resides on UE-2.
The Application Client has discovered or is configured that the MSGin5G Client resides on MSGin5G UE-1 and can provide the MSGin5G service capability to it.
If the Application Client resides on UE-2, 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 with MSGin5G Client on MSGin5G UE-1

Figure 8.11.2-1: Registration of Application Client with MSGin5G Client on MSGin5G UE-1
(⇒ copy of original 3GPP image)

Step 1.

An Application Client registers with MSGin5G Client-1 in MSGin5G UE-1 to use MSGin5G service. The request message includes information elements as specified in Table 8.11.2-1.

Table 8.11.2-1: Information elements for Registration to gateway UE request

Information element	Status	Description
Layer-2 ID (see NOTE)	O	Layer-2 identity of UE-2.
Application ID	M	Application ID of the application client.
Credential information (see NOTE)	O	UE-2 credential information.
NOTE: Only included when the application client resides on UE-2.

Step 2.

Upon receiving the request from the Application Client, the MSGin5G Client authorizes the Application Client for MSGin5G service. The MSGin5G Client assigns a Registration ID and stores the mapping of the Registration ID, Application ID and Layer-2 ID of the UE-2 if included.

Step 3.

The MSGin5G Client sends a response to the Application Client. The response message includes information elements as specified in Table 8.11.2-2.

Table 8.11.2-2: Information elements for Registration to gateway UE response

Information element	Status	Description
Result	M	Indicates success or failure of the request.
Registration ID	O	Identifies registration. This IE is included only if Result IE is set to success.
Failure reason	O	Indicates failure reason. This IE is included only if Result IE is set to failure.

8.11.3 Application Client de-registration using MSGin5G Client p. 127

The signalling flow for deregistration of Application Client with MSGin5G Client-1 on MSGin5G UE-1 is illustrated in Figure 8.11.3-1.

Pre-conditions:

The Application Client is successfully registered with MSGin5G Client on MSGin5G UE-1.

Copy of original 3GPP image for 3GPP TS 23.554, Fig. 8.11.3-1: Deregistration of Application Client with MSGin5G Client on MSGin5G UE-1

Figure 8.11.3-1: Deregistration of Application Client with MSGin5G Client on MSGin5G UE-1
(⇒ copy of original 3GPP image)

Step 1.

An Application Client deregisters with MSGin5G Client in MSGin5G UE-1 to discontinue usage of the MSGin5G Service. The request message includes information elements as specified in Table 8.11.3-1.

Table 8.11.3-1: Information elements for Deregistration to gateway UE request

Information element	Status	Description
Registration ID	M	Identifies the registration.
Credential information	O	UE-2 credential information.

Step 2.

Upon receiving the request from the Application Client, the MSGin5G Client removes the mapping of Registration ID, Application ID and Layer-2 ID of the UE-2 if included. The MSGin5G Client sends a response to the Application Client. The response message includes the information elements as specified in Table 8.11.3-2.

Table 8.11.3-2: Information elements for Deregistration to gateway UE response

Information element	Status	Description
Result	M	Indicates success or failure of the request.
Failure reason	O	Indicates failure reason. This IE is included only if the Result IE is set to failure.

8.11.4 Application Client sending a message using MSGin5G Client p. 128

The signalling flow for the Application Client to send a message using the MSGin5G Client on MSGin5G UE-1 is illustrated in Figure 8.11.4-1.

Pre-conditions:

The MSGin5G UE-1 is connected to an access network that provides connectivity to the MSGin5G Server.
The Application Client is successfully registered with MSGin5G UE-1 to use MSGin5G service.

Copy of original 3GPP image for 3GPP TS 23.554, Fig. 8.11.4-1: Application Client sends message using MSGin5G Client on MSGin5G UE-1

Figure 8.11.4-1: Application Client sends message using MSGin5G Client on MSGin5G UE-1
(⇒ copy of original 3GPP image)

Step 1.

An Application Client sends a request to send MSGin5G message to the MSGin5G Client. The information elements defined in Table 8.11.4-1 are included in the message.

Table 8.11.4-1: Information elements for Request to send MSGin5G message

Information element	Status	Description
Recipient UE Service ID or AS Service ID (see NOTE)	O	The service identity of the recipient. This IE is mandatory to initiate Point-to-Point messaging and Point-to-AS messaging.
Group Service ID (see NOTE)	O	The service identifier of the target MSGin5G Group. This IE is mandatory to initiate Group messaging.
Broadcast Area ID (see NOTE)	O	The service identifier of the Broadcast Service Area where the message needs to be broadcast. This IE is mandatory in the Broadcast Message.
Messaging Topic (see NOTE)	O	Indicates which Messaging Topic this message is related to. This IE is mandatory for a message distribution based on topic.
Application ID	O	Identifies the application(s) for which the payload is intended.
Payload	M	Payload of the message. MSGin5G Server/Client is unaware of the content.
Delivery status required	O	Indicates whether delivery status is required or not.
Priority type	O	Application priority level requested for this message as specified in Table 8.3.2-1.
NOTE: Only one occurrence shall be present of any of these IEs.

Step 2.

Upon receiving the request from the Application Client, the MSGin5G Client constructs an MSGin5G message with the related IEs specified in Table 8.3.2-1 and sends the MSGin5G message.

if the size of the received message exceeds the maximum allowed packet size, the MSGin5G Client sends the message as specified in clause 8.5; or
If the size of the received message does not exceed the maximum allowed packet size, the MSGin5G Client sends the message as specified in clause 8.7.; or
If the size of the received message does not exceed the maximum allowed packet size, the MSGin5G Client may apply message aggregation as specified in clause 8.4 before sending the message as specified in clause 8.7.

Step 3.

The MSGin5G Client sends a response to Application Client. The response message includes the information elements as specified in Table 8.11.4-2.

Table 8.11.4-2: Information elements for Response to send MSGin5G message

Information element	Status	Description
UE Service ID or AS Service ID or Group Service ID or Broadcast Area ID or Message Topic	M	The service identifier that the message is sent.
Result	M	Indicates success or failure of the request.
Failure reason	O	Indicates failure reason. This IE is included only if Result IE is set to failure.

Step 4.

If delivery status is requested in the message in step 1, the MSGin5G Client may receive MSGin5G message delivery status report from the MSGin5G Server.

Step 5.

Upon receiving the MSGin5G message delivery status report, the MSGin5G Client sends the message delivery status report to the Application Client. The message delivery status report includes information elements as specified in Table 8.11.4-3.

Table 8.11.4-3: Information elements for MSGin5G message delivery status

Information element	Status	Description
UE Service ID or AS Service ID	M	The service identifier that sends the message delivery status.
Delivery status	M	Indicates delivery status.

8.11.5 Application Client receiving message via MSGin5G Client on another UE p. 130

The signalling flow for an Application Client to receive a message using the MSGin5G Client on MSGin5G UE-1 is illustrated in Figure 8.11.5-1.

Pre-conditions:

The MSGin5G UE-1 is connected to an access network that provides connectivity to the MSGin5G Server.
The Application Client is successfully registered with MSGin5G UE-1 to use MSGin5G service.

Copy of original 3GPP image for 3GPP TS 23.554, Fig. 8.11.5-1: Application Client receives message using MSGin5G Client on MSGin5G UE-1

Figure 8.11.5-1: Application Client receives message using MSGin5G Client on MSGin5G UE-1
(⇒ copy of original 3GPP image)

Step 1.

The MSGin5G Client receives an MSGin5G message as specified in clause 8.3.3 for the Application Client. The MSGin5G Client performs reassembly if the received message is part of a segmented message and waits till the whole message is received. The MSGin5G Client may also perform the segment recovery procedure as specified in clause 8.5.4 to recover missing segments.

Step 2.

Upon successfully receiving a message for the Application Client, the MSGin5G Client sends a message received request to the Application Client based on the Application ID in the received message. The message includes information elements as specified in Table 8.11.5-1.

Table 8.11.5-1: Information elements for Message received request

Information element	Status	Description
Recipient UE Service ID/AS Service ID (see NOTE)	O	The service identifier of the originator. This IE is mandatory for Point-to-Point messaging and AS-to-Point messaging.
Group Service ID (see NOTE)	O	The service identifier of the MSGin5G Group. This IE is mandatory for Group Message.
Messaging Topic (see NOTE)	O	Indicates the Topic for which the message is received. This IE is mandatory for a Topic Message.
Payload	M	Payload of the message. MSGin5G Server/Client is unaware of the content.
Delivery status required	O	Indicates whether delivery status is required or not.
Priority type	O	Application priority level requested for this message as specified in Table 8.3.2-1.
NOTE: Only one occurrence shall be present of any of these IEs.

Step 3.

Upon successfully receiving the message, the Application Client sends the message received response to the MSGin5G Client.

Step 4.

If delivery status is requested in the received message, the Application Client sends the message delivery status to the MSGin5G Client.

Step 5.

Upon receiving the delivery status, the MSGin5G Client constructs the MSGin5G message delivery status report as specified in Table 8.3.4-1 and sends it to the MSGin5G Server.