Tech-invite  3GPPspace  IETFspace
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:  19.3.0

Top   Top   Up   Prev   Next
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 Message Aggregation  8.4.1 General  8.4.2 Message Aggregation at MSGin5G Client 
...

 

8.4  Message Aggregation  p. 68

8.4.1  General  p. 68

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.
Up

8.4.2  Message Aggregation at MSGin5G Client  p. 68

Figure 8.4.2-1 shows the procedure for an MSGin5G Client aggregating a set of Point-to-Point messages each carrying small amounts of data. All of the Point-to-Point messages to be aggregated are targeted to the same 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)
Up
Figure 8.4.2-2 shows the procedure for an MSGin5G Client aggregating a set of Point-to-AS messages each carrying small amounts of data. All of the Point-to-AS messages to be aggregated are sent to 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)
Up
Figure 8.4.2-3 shows the procedure for an MSGin5G Client aggregating a set of Point-to-Point messages each carrying small amounts of data. All of the Point-to-Point messages to be aggregated are sent to same recipient Non-MSGin5G UE.
Copy of original 3GPP image for 3GPP TS 23.554, Fig. 8.4.2-3: MSGin5G UE aggregates messages towards target Non-MSGin5G UE
Figure 8.4.2-3: MSGin5G UE aggregates messages towards target Non-MSGin5G UE
(⇒ copy of original 3GPP image)
Up
Figure 8.4.2-4 shows the procedure for an MSGin5G Client sends aggregated message to a MSGin5G group. All of the messages to be aggregated are sent to same MSGin5G Group.
Copy of original 3GPP image for 3GPP TS 23.554, Fig. 8.4.2-4: MSGin5G UE sends aggregated messages towards target MSGin5G Group
Figure 8.4.2-4: MSGin5G UE sends aggregated messages towards target MSGin5G Group
(⇒ copy of original 3GPP image)
Up
Figure 8.4.2-5 shows the procedure for an MSGin5G Client sends aggregated message based on Messaging Topic. All the messages to be aggregated have the same Messaging Topic.
Copy of original 3GPP image for 3GPP TS 23.554, Fig. 8.4.2-5: MSGin5G UE sends aggregated messages towards target MSGin5G Group
Figure 8.4.2-5: MSGin5G UE sends aggregated messages towards target MSGin5G Group
(⇒ copy of original 3GPP image)
Up
Figure 8.4.2-6 shows the procedure for an MSGin5G Client aggregating a set of Broadcast messages each carrying small amounts of data. All of the Broadcast messages to be aggregated are sent to same Broadcast Area.
Copy of original 3GPP image for 3GPP TS 23.554, Fig. 8.4.2-6: MSGin5G UE aggregates messages towards target Broadcast Area
Figure 8.4.2-6: MSGin5G UE aggregates messages towards target Broadcast Area
(⇒ copy of original 3GPP image)
Up
The following procedure applies to the above Figure 8.4.2-1 to Figure 8.4.2-6 with the exception that:
  1. step 4a only applies to Figure 8.4.2-4
  2. step 7a only applies to Figure 8.4.2-1 and Figure 8.4.2-4;
  3. step 7b only applies to Figure 8.4.2-3 and Figure 8.4.2-4; and
  4. step 7c only applies to Figure 8.4.2-6.
Step 1.
Application Client(s) initiates a request to the MSGin5G Client 1 to send a message to another target. The target may be an MSGin5G UE, a Non-MSGin5G UE, an Application Server, a MSGin5G group, or a broadcast area. the Application Client(s) may also initiate a request to the MSGin5G Client 1 to send a message which is to be delivered based on Messaging Topic.
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 message has a small payload size when compared to the maximum segment size that can be transmitted over available transport and is not high priority message (i.e. the value of Priority type included in the message is not "High"), the MSGin5G Client 1 may aggregate this message. The MSGin5G Client 1 may continue aggregating messages until an optimal segment size is reached before sending the aggregated message. When the aggregation is finished, e.g. the optimal segment size is reached or other conditions such as waiting time configured by service provider is fulfilled, the MSGin5G Client sends the aggregated message 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 containing the information elements specified in Table 8.4.2-1 and Table 8.4.2-2 according to scheduling policy towards the MSGin5G Server.
Information element Status Description
Originator UE Service IDMThe service identity of the sending MSGin5G Client.
Recipient UE Service ID/AS Service ID
(see NOTE)		OThe service identity of the receiving MSGin5G Client or the receiving Application Server.
Group Service ID
(see NOTE)		OThe service identifier of the target MSGin5G Group.
Messaging Topic
(see NOTE)		OIndicates which Messaging Topic this message is related to.
Broadcast Area ID
(see NOTE)		OThe service identifier of the Broadcast Area where the message needs to be broadcast.
Message IDMUnique identifier of this aggregated message.
Number of individual messagesMIndicates total number of messages which are aggregated into this message.
List of individual messagesM Each element in this list contains information elements as specified in Table 8.4.2-2.
Store and forward flagOAn indicator of whether store and forward services are requested for this aggregated message. The store and 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 parametersO 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.
NOTE:
Only one of these IEs shall be included to represent the type of message request.
Information element Status Description
Individual Message IDMUnique identifier of this individual message.
Application IDOIdentifies the application for which the payload is intended.
Delivery status requiredOIndicates if delivery acknowledgement from the recipient is requested.
PayloadMPayload of the message.
Priority typeO 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 authorized to send the Aggregated message request.
Step 4a.
The MSGin5G Server performs the necessary message exchanging procedure with the Application Server as per clause 8.7.4.2.
Step 5.
The MSGin5G Server sends the Aggregated message response to the MSGin5G Client 1 in the cases listed below. The information elements defined in Table 8.4.2-3 shall be included in the response:
  1. MSGin5G Client 1 is not authorized to send Aggregated message request; or
  2. the Aggregated message request is not valid; or
  3. if MSGin5G Client 1 is authorized but the message is stored for deferred delivery.
Information element Status Description
Original MSGin5G Client IDMThe identity of the MSGin5G Client sending the original message.
Message IDMUnique identifier of the original aggregated message.
Delivery StatusOIndicates if delivery is a failure, or if the message is stored for deferred delivery.
Failure CauseOThis 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 an Aggregated message request, the MSGin5G Server sends the 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 segment 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 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).
Step 7b.
If the recipient of the aggregated message is a 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 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 Broadcast Message Gateway broadcasts each individual MSGin5G message request to the MSGin5G UEs in the Broadcast Area, or broadcasts 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.
Step 8.
The recipient MSGin5G Client/ Application Server/ Message Gateway may initiate sending a message delivery status report, if requested in the original message that is received as in Step 7a (for MSGin5G UE), step 7b (for Non-MSGin5G UE) or Step 6 (for Application Server). MSGin5G Client 2/ Application Server/ Message Gateway sends the message delivery status report towards the MSGin5G Client on MSGin5G UE 1 via MSGin5G Server.
Up

Up   Top   ToC