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.4.3 Message aggregation at MSGin5G Server p. 75
Figure 8.4.3-1 shows the procedure for the MSGin5G Server aggregating a set of Application-to-Point messages targeted to the same recipient UE, set of group messages for the same MSGin5G group, or a set of messages delivered based on Messaging Topic for the same Messaging Topic, or a set of messages broadcasted to the same Service Area, each carrying a small amount data targeted towards the same target MSGin5G UE(s).
Figure 8.4.3-1: MSGin5G Server aggregates messages towards target MSGin5G UE
(⇒ copy of original 3GPP image)
(⇒ copy of original 3GPP image)
Figure 8.4.3-2 shows the procedure for MSGin5G Server aggregating a set of Application-to-Point messages targeted to the same recipient UE, or a set of group messages for the same MSGin5G group, or a set of messages delivered based on Messaging Topic for the same Messaging Topic, or a set of messages broadcasted to the same Service Area, each carrying a small amount data targeted towards the same target Non-MSGin5G UE(s).
Figure 8.4.3-2: MSGin5G Server aggregates messages towards target Non-MSGin5G UE
(⇒ copy of original 3GPP image)
(⇒ copy of original 3GPP image)
Figure 8.4.3-3 shows the procedure for MSGin5G Server aggregating Broadcast messages, each carrying a small amount 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
(⇒ copy of original 3GPP image)
(⇒ copy of original 3GPP image)
The following procedure applies to the above Figure 8.4.3-1, Figure 8.4.3-2 and Figure 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.
Step 1.
The Application Server initiates to send a set of Application-to-Point messages targeted to the same recipient UE, or a set of group messages for the same MSGin5G group, or a set of messages delivered based on Messaging Topic for the same Messaging Topic, or a set of messages broadcasted to the same Service Area, and sends the request to MSGin5G Server. The MSGin5G Server executes the MSGin5G messages origination procedure for each message as specified in clause 8.3.2.
Step 2.
The MSGin5G Server checks the message data size and the priority level of each message to determine if these messages, targeted to the same service end-point and of the same message type (i.e., either a set of Application-to-Point messages targeted to the same recipient UE, a set of group messages for the same MSGin5G group, a set of messages delivered based on Messaging Topic for the same Messaging Topic or a set of messages broadcasted to the same Service Area,), can be aggregated. For example, the 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. The Aggregated message request contain the information elements as defined in Table 8.4.3-1 and Table 8.4.2-2. The MSGin5G Server delivers the Aggregated message request by using the MSGin5G messages termination procedure specified in clause 8.3.3.
| Information element | Status | Description |
|---|---|---|
| Originating AS Service ID | M | The service identity of the sending Application Server. |
| Recipient UE Service ID | O | The service identity of the receiving MSGin5G Client. This IE in Mandatory for all type of message request except the broadcast message. |
| Group Service ID (see NOTE) | O | The service identifier of the target MSGin5G Group. This IE should be present if the aggregated message is a set of group messages for the same MSGin5G group. |
| Messaging Topic (see NOTE) | O | Indicates which Messaging Topic this message is related to. This IE should be present if the aggregated message is a set of message delivered based on Messaging Topic for the same Messaging Topic. |
| Broadcast Area ID (see NOTE) | O | The identifier of the Service Area where the message needs to be broadcast. |
| 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.
|
||
Step 4a.
If the recipient of the aggregated message is MSGin5G UE, the MSGin5G Client 1 residing on the MSGin5G UE 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).
Step 4b.
If the recipient of the aggregated message is the 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.
Step 4c.
If the recipient of the aggregated message is a Broadcast Area, the Broadcast Message Gateway split the received aggregated message request into multiple individual MSGin5G message requests. The Broadcast Message Gateway may either broadcast each individual MSGin5G message request to the MSGin5G UEs in the Broadcast Area, or broadcast the content of each individual MSGin5G message request to the non-MSGin5G UEs in the Broadcast Area, via CBCF. The procedures on CBCF are specified in TS 23.041.
