Content for TS 23.554 Word version: 18.2.0

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.4 Message Aggregation 8.4.1 General 8.4.2 Message Aggregation at MSGin5G Client 8.4.3 Message Aggregation at MSGin5G Server
...

8.4 Message Aggregation p. 61

8.4.1 General p. 61

Based on maximum segment size allowed to transmit over available transport, the MSGin5G Service can optimize communications by aggregating one or more messages towards the target.

The following pre-conditions apply for message aggregation:

The recipient UE(s) support an MSGin5G Client or the (Legacy-3GPP and non-3GPP) Message Gateway supports the MSGin5G Client capability.
The MSGin5G Client 1 and MSGin5G Client 2 are registered with the MSGin5G Server, or an Application Server has established a secured communication with the MSGin5G Server.

8.4.2 Message Aggregation at MSGin5G Client p. 61

Figure 8.4.2-1 shows the procedure for an MSGin5G Client aggregating Point-to-Point messages including a group of messages each carrying small amounts of data. All of the aggregated Point-to-Point messages are sent to a same recipient UE.

Copy of original 3GPP image for 3GPP TS 23.554, Fig. 8.4.2-1: MSGin5G UE aggregates messages towards target MSGin5G UE

Figure 8.4.2-1: MSGin5G UE aggregates messages towards target MSGin5G UE
(⇒ copy of original 3GPP image)

Figure 8.4.2-2 shows the procedure for an MSGin5G Client aggregating Point-to-Application messages each carrying small amounts of data All of the aggregated Point-to-Application messages are sent to a same Application Server.

Copy of original 3GPP image for 3GPP TS 23.554, Fig. 8.4.2-2: MSGin5G UE aggregates messages towards target Application Server

Figure 8.4.2-2: MSGin5G UE aggregates messages towards target Application Server
(⇒ copy of original 3GPP image)

The following procedure applies to the above Figure 8.4.2-1 and Figure 8.4.2-2 with the exception that step 7 only applies to Figure 8.4.2-1.

Step 1.

Application Client(s) on UE 1 initiates a request to the MSGin5G Client 1 to send a message to another target or to send a group message.

Step 2.

The MSGin5G Client 1 checks if aggregation is allowed for this message as per the service configuration, The MSGin5G Client 1 also checks the message data size, and the priority level to determine if the received message can be aggregated. For example, MSGin5G Client 1 finds that the messages have small payload size when compared to the maximum segment size that can be transmitted over available transport and are not high priority messages (i.e. the value of Priority type included in the message is not "High"), which could be sent as per scheduling policy towards a selected target.

Step 3.

The MSGin5G Client 1 aggregates multiple MSGin5G message requests intended for a selected target and sends the Aggregated message request as defined in Table 8.4.2-1 and Table 8.4.2-2 according to scheduling policy towards MSGin5G Server.

Table 8.4.2-1: Aggregated message request (MSGin5G Client to MSGin5G Server)

Information element	Status	Description
Originator UE Service ID	M	The service identity of the sending MSGin5G Client.
Recipient UE Service ID/AS Service ID (see NOTE)	M	The service identity of the receiving MSGin5G Client or the receiving Application Server.
Message ID	M	Unique identifier of the aggregated message
Security credentials	O	Security information required by the MSGin5G Server. This is a placeholder for SA3 security information.
Number of individual messages	M	Indicates total number of messages which are aggregated into single message
List of individual messages	M	Each element in this list contains information as specified in Table 8.3.2-1.
Store and forward flag	O	An indicator of whether store and forward services are requested for this aggregated message. If the value indicates that store and forward services are requested by the sender, the store and forward procedure in clause 8.3.6 applies. The forward services can be applied to the aggregated message only if all messages in this aggregated message can be store and forwarded.
Store and forward parameters	O	Parameters used by MSGin5G Server for providing store and forward services, as detailed in Table 8.3.2-2. This IE shall be included only if the value of the Store and forward flag IE indicates that store and forward services are requested. The MSGin5G store and forward procedure is detailed in clause 8.3.6.

Table 8.4.2-2: Individual message data

Information element	Status	Description
Individual Message ID	M	Unique identifier of this individual message.
Application ID	O	Identifies the application for which the payload is intended.
Delivery status required	O	Indicates if delivery acknowledgement from the recipient is requested.
Payload	M	Payload of the message
Priority type	O	Application priority level requested for this message as specified in Table 8.3.2-1 except that the value of this IE should not be High.

Step 4.

MSGin5G Server checks whether the MSGin5G Client 1 is authenticated and authorized to send Aggregated message request. If authenticated and authorized, the MSGin5G Server skips step 5.

Step 5.

If MSGin5G Client 1 is not authorized to send Aggregated message request, the Aggregated message request is not valid, or the message is stored for deferred delivery, the MSGin5G Server sends Aggregated message response to the MSGin5G Client 1. The information elements defined in Table 8.4.2-3 are included in the response.

Table 8.4.2-3: Aggregated message response (MSGin5G Server to MSGin5G Client)

Information element	Status	Description
Original MSGin5G Client ID	M	The identity of the MSGin5G Client sending the original message.
Message ID	M	Unique identifier of this message
Delivery Status	O	Indicates if delivery is a failure, or if the message is stored for deferred delivery.
Failure Cause	O	This IE contains the failure reason, e.g. the originator is not authorized to send a message request or one of the multiple messages aggregated has an issue, may be included in this IE.

Step 6.

If MSGin5G Client 1 is authorized to send Aggregated message request, the MSGin5G Server sends Aggregated message request towards the selected target MSGin5G Client(s) 2/ Application Server. If the aggregated message is sent to a recipient whose supported message segment size is smaller than the aggregated message, the MSGin5G Server should remove the last individual message in the List of individual messages element from the aggregated message until the aggregated message is smaller than the maximum segmentation size that can be transmitted over available transport. The MSGin5G messages removed from the aggregated message may be sent individually or aggregated again by the MSGin5G Server according to service configuration.

Step 7.

The MSGin5G Client 2 splits the received Aggregated message request into multiple individual MSGin5G message requests per application and sends them towards Application Client(s).

Step 8.

The Application Client(s)/ Application Server may initiate sending a message delivery status report, if requested in the original message that is received as in Step 7 (for MSGin5G UE) or Step 6 (for Application Server). MSGin5G Client 2/ Application Server sends the message delivery status report towards the Application Client(s) on UE 1 via MSGin5G Server and MSGin5G Client 1.

8.4.3 Message Aggregation at MSGin5G Server p. 68

Figure 8.4.3-1 shows the procedure for MSGin5G Server aggregating Application-to-Point messages each carrying small data targeted towards the target UE.

Copy of original 3GPP image for 3GPP TS 23.554, Fig. 8.4.3-1: MSGin5G Server aggregates messages towards target end point

Figure 8.4.3-1: MSGin5G Server aggregates messages towards target end point
(⇒ copy of original 3GPP image)

Step 1.

The Application Server initiates to send Application-to-Point message or a group message towards target UE(s) 1 and sends the request to MSGin5G Server and includes an indication that message aggregation is allowed for this message.

Step 2.

The MSGin5G Server checks the message data size and the priority level to determine if the received message can be aggregated. For example, MSGin5G Server finds that the messages have small payload size when compared to the maximum segment size that can be transmitted over available transport and are not high priority messages (i.e. the value of Priority type included in the message is not "High"), which could be sent as per scheduling policy towards a selected target.

Step 3.

The MSGin5G Server aggregates multiple MSGin5G message requests intended for the target UE and sends the Aggregated message request as defined in Table 8.4.3-1 and Table 8.4.2-2 according to scheduling policy towards the MSGin5G Client 1.

Table 8.4.3-1: Aggregated message request (MSGin5G Server to MSGin5G Client)

Information element	Status	Description
Originating AS Service ID	M	The service identity of the sending Application Server.
Recipient UE Service ID	M	The service identity of the receiving MSGin5G Client.
Message ID	M	Unique identifier of this message
Number of individual messages	M	Indicates total number of messages which are aggregated into single message
List of Individual messages	M	Each element in this list contains information as specified in Table 8.3.3-1

Step 4.

The MSGin5G Client 1 splits the received Aggregated message request into multiple individual MSGin5G message requests per application and sends towards Application Client(s) as notifications.