8.4 Message Aggregation
23.5543GPPApplication architecture for MSGin5G ServiceRelease 18Stage 2TS
8.4.1 General
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 same target. The target may be an UE, an Application Server, a Broadcast Area, an MSGin5G Group or a Messaging Topic.
The following pre-conditions apply for message aggregation:
1. The recipient UE(s) support an MSGin5G Client or the (Legacy-3GPP and non-3GPP) Message Gateway supports the MSGin5G Client capability.
2. 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
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 same recipient MSGin5G UE.
NOTE 1: Aggregation of multiple messages can also be done with the Application Client; in this case it is implementation specific and out of the scope of the current specification.
Figure 8.4.2-1: MSGin5G UE aggregates messages towards target MSGin5G UE
Figure 8.4.2-2 shows the procedure for an MSGin5G Client aggregating Point-to-AS messages each carrying small amounts of data All of the aggregated Point-to-AS messages are sent to same Application Server.
Figure 8.4.2-2: MSGin5G UE aggregates messages towards target Application Server
Figure 8.4.2-3 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 same recipient Non-MSGin5G UE.
Figure 8.4.2-3: MSGin5G UE aggregates messages towards target Non-MSGin5G UE
Figure 8.4.2-4 shows the procedure for an MSGin5G Client sends aggregated message to a MSGin5G group. All of the aggregated messages are sent to same MSGin5G Group.
Figure 8.4.2-4: MSGin5G UE sends aggregated messages towards target MSGin5G Group
Figure 8.4.2-5 shows the procedure for an MSGin5G Client sends aggregated message based on Messaging Topic. All of the aggregated messages includes the same Messaging Topic.
Figure 8.4.2-5: MSGin5G UE sends aggregated messages towards target MSGin5G Group
Figure 8.4.2-6 shows the procedure for an MSGin5G Client aggregating Broadcast messages including a group of messages each carrying small amounts of data. All of the aggregated Broadcast messages are sent to same Broadcast Area.
Figure 8.4.2-6: MSGin5G UE aggregates messages towards target Broadcast Area
The following procedure applies to the above figures 8.4.2-1 to 8.4.2-6 with the exception that:
a) step 4a only applies to figure 8.4.2-4
b) step 7a only applies to figure 8.4.2-1 and figure 8.4.2-4;
c) step 7b only applies to figure 8.4.2-3. and figure figure 8.4.2-4; .and
d) step 7c only applies to figure 8.4.2-6.
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.
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.
NOTE 2: MSGin5G Client 1 decides to continue aggregating messages until optimal use of segment size before sending message towards MSGin5G Server.
NOTE 3: The configuration of whether aggregation is allowed for MSGin5G messages and how the MSGin5G Client 1 uses information such as individual message priority, maximum time to wait, etc for aggregating and sending is out of scope of the present document.
NOTE 4: The maximum segment size that can be transmitted over available transport is configured to the MSGin5G Client 1 in the MSGin5G Service specific information IE as specified in Table 8.1.2-2.
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) |
O |
The service identity of the receiving MSGin5G Client or the receiving Application Server. |
|
Group Service ID (see NOTE) |
O |
The service identifier of the target MSGin5G Group. |
|
Messaging Topic (see NOTE) |
O |
Indicates which Messaging Topic this message is related to. |
|
Broadcast Area ID (see NOTE) |
O |
The service identifier of the Broadcast Area where the message needs to be broadcast. |
|
Message ID |
M |
Unique identifier of the aggregated 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.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. |
|
NOTE Only one of these IEs shall be included to represent the type of message request. |
||
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. |
NOTE 5: Total size of Aggregated message request is less than or equal to maximum segment size allowed to be transmitted over available transport.
4. MSGin5G Server checks whether the MSGin5G Client 1 is authorized to send Aggregated message request.
4b The MSGin5G Server performs the necessary message exchanging procedure with Application Server as per clause 8.7.4.2.
5. If MSGin5G Client 1 is not authorized to send Aggregated message request, the Aggregated message request is not valid, or if MSGin5G Client 1 is authorized but 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. |
6. If MSGin5G Client 1 is authorized to send Aggregated message request and the message is not stored for deferred delivery, the MSGin5G Server sends Aggregated message request towards the selected target as specified in clause 8.3.3. 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.
Editor’s note: The procedure to send an Aggregated message request which requires store and forward services is FFS.
7a. If the recipient of the aggregated message is MSGin5G UE 2, the MSGin5G Client 2 in the MSGin5G UE 2 splits the received Aggregated message request into multiple individual MSGin5G message requests. The content of each MSGin5G message is delivered to the recipient Application Client(s).
NOTE 6: The delivery between MSGin5G Client and Application Client is out of scope of the present document.
7b. If the recipient of the aggregated message is Message Gateway on behalf of Non-MSGin5G UE, the Message Gateway splits the received Aggregated message request into multiple individual MSGin5G message requests. The content of each MSGin5G message is delivered to the Non-MSGin5G UE via Non-MSGin5G message delivery.
NOTE 7: The Non-MSGin5Gmessage delivery is out of scope of this document.
7c. If the aggregated message needs to be delivered in the Broadcast Area, the Broadcast Message Gateway splits the received Aggregated message request into multiple individual MSGin5G message requests. The content of each MSGin5G message is delivered to the CBCF, and CBCF broadcasts the message as specified in 3GPP TS 23.041 [14].
8. The Application Client(s)/ Application Server/ Message Gateway may initiate sending a message delivery status report, if requested in the original message that is received as in Step 7 (for MSGin5G UE) and Non-MSGin5G UE or Step 6 (for Application Server). MSGin5G Client 2/ Application Server/ Message Gateway sends the message delivery status report towards the Application Client(s) on UE 1 via MSGin5G Server and MSGin5G Client 1.
NOTE 8: The message delivery status reports can also be aggregated into a single message.
8.4.3 Message Aggregation at MSGin5G Server
Figure 8.4.3-1 shows the procedure for MSGin5G Server aggregating Application-to-Point messages each, a group message, or Message delivery based on Messaging Topic, carrying small data targeted towards the target MSGin5G UE(s).
NOTE 1: Aggregation of multiple messages can also be done at the Application Server; in this case it is implementation specific and out of the scope of the current specification.
Figure 8.4.3-1: MSGin5G Server aggregates messages towards target MSGin5G UE
Figure 8.4.3-2 shows the procedure for MSGin5G Server aggregating Application-to-Point messages, a group message, or Message delivery based on Messaging Topic, each carrying small data targeted towards the target Non-MSGin5G UE(s).
Figure 8.4.3-2: MSGin5G Server aggregates messages towards target Non-MSGin5G UE
Figure 8.4.3-3 shows the procedure for MSGin5G Server aggregating Broadcast message, each carrying small data targeted towards the target Broadcast Area.
Figure 8.4.3-3: MSGin5G Server delivers aggregated message towards Non-MSGin5G UEs in the Broadcast Area
The following procedure applies to the above figures 8.4.3-1, 8.4.3-2 and 8.4.3-3 with the exception that step 4a only applies to figure 8.4.3-1, step 4b only applies to figure 8.4.3-2 and step 4c only applies to figure 8.4.3-3.
1. The Application Server initiates to send Application-to-Point message or a group message or Message delivery based on Messaging Topic and sends the request to MSGin5G Server as specified in clause 8.3.2.
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.
NOTE 2: MSGin5G Server decides to continue aggregating messages until optimal use of segment size before sending message towards MSGin5G Client 1.
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 (see NOTE) |
O |
The service identity of the receiving MSGin5G Client. |
|
Group Service ID |
||
|
(see NOTE) |
O |
The service identifier of the target MSGin5G Group. |
|
Messaging Topic (see NOTE) |
O |
Indicates which Messaging Topic this message is related to. |
|
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 |
|
NOTE: Only one of these IEs shall be included to represent the type of message request. |
||
NOTE 3: Total size of Aggregated message request is less than or equal to maximum segment size allowed to transmit over available transport.
4a. If the recipient of the aggregated message is MSGin5G UE, the MSGin5G Client 1 splits the received Aggregated message request into multiple individual MSGin5G message requests. The content of each MSGin5G message is delivered to the recipient Application Client(s) as notifications.
NOTE 4: The delivery between MSGin5G Client and Application Client is out of scope of the present document.
4b. If the recipient of the aggregated message is Message Gateway on behalf of Non-MSGin5G UE, the Message Gateway splits the received Aggregated message request into multiple individual MSGin5G message requests. The content of each MSGin5G message is delivered to the Non-MSGin5G UE via Non-MSGin5G message delivery.
NOTE 5: The Non-MSGin5Gmessage delivery is out of scope of this document.
NOTE 6: The MSGin5G Server may aggregate messages towards the target UE if it receives message from multiple MSGin5G UEs (instead of application server).
4c. If the recipient of the aggregated message is a Broadcast Area, the Broadcast Message Gateway delivers the content of each MSGin5G message in the aggregated message to the CBCF, and CBCF broadcasts the message as specified in 3GPP TS 23.041 [14].