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.7.4 MSGin5G Group messaging  8.7.4.1 General  8.7.4.2 Message delivery from UE to group  8.7.4.3 Message delivery procedure from Application Server to group 
...

 

8.7.4  MSGin5G Group messaging  p. 102

8.7.4.1  General  p. 102

This clause introduces a group messaging procedure for MSGin5G Client and MSGin5G Server to send and receive Group messages after a group is created. In this procedure, the group creation and membership management are handled by group management function specified in TS 23.434.

8.7.4.2  Message delivery from UE to group  p. 102

Figure 8.7.4.2-1 shows the MSGin5G Group messaging procedure in which MSGin5G Client or Application Server sends a message to a group. One or multiple Controlling AS may be present in this group. The Controlling AS is not considered as a participant of this group.
Pre-conditions:
  1. An MSGin5G Group is created by following group management SEAL service procedures as specified in TS 23.434.
  2. All participants in the MSGin5G Group may get the Group information i.e. the Group Service ID.
  3. The MSGin5G Server has a copy of the group profile with all the group members by using Group information query specified in TS 23.434.
Copy of original 3GPP image for 3GPP TS 23.554, Fig. 8.7.4.2-1: Group messaging in MSGin5G Service
Figure 8.7.4.2-1: Group messaging in MSGin5G Service
(⇒ copy of original 3GPP image)
Up
Step 1.
A MSGin5G message request is sent to a group as specified in clause 8.3.2. This MSGin5G message request includes the information elements from Table 8.3.2-1. This message may be sent by:
  1. The MSGin5G Client-1; or
  2. The Application Server-1.
Step 2.
Upon receiving the MSGin5G message request to send the group message:
  1. if the MSGin5G Client-1 or Application Server-1 is authorized to send the group message, step 3 is to be processed by the MSGin5G Server;
  2. otherwise the MSGin5G Server sends MSGin5G message response with delivery status set as Reject to the MSGin5G Client-1 or the Application Server-1, i.e. the message is rejected by the MSGin5G service, as specified in clause 8.3.2.
Step 3.
The MSGin5G Server checks the whether one or multiple Controlling present in this MSGin5G group by checking the stored Expected MSGin5G group list to be controlled included in the Application Server registration,
  1. if a Controlling AS(s) is present, the MSGin5G Server sends the message to the Controlling AS (e.g. to log application specific message or for analytics) based on Group service ID present in the received MSGin5G message request , i.e. this group is included in one or multiple Application Server's Expected MSGin5G group list to be controlled , and holds the message on MSGin5G Server until the Controlling AS agreed to send this message, i.e. after step 4
    1. Upon receiving the MSGin5G message request, the Controlling ASApplication Server checks whether the message is allowed to be sent based on the application specific logic. If the message is not allowed to be sent, the Controlling AS sends MSGin5G message response with delivery status set as Reject to the MSGin5G Server.
      The MSGin5G Server sends the MSGin5G message response with delivery status set as reject to the MSGin5G Client-1, or to the Application Server-1 as specified in clause 8.3.2. The information elements defined in Table 8.3.2-3 are included in the response. Following procedures will be skipped, i.e. the message is rejected by the application.
    2. Otherwise, go to step 4.
  2. if a Controlling AS(s) is not present, the MSGin5G Server skips step 4 and continues the procedure from step 5.
Step 4.
The Controlling AS finishes to process the application specific logic of the message, e.g. log application specific message, or analyzes the information in the message, and sends the MSGin5G message request back to the MSGin5G Server based on different application specific logic of the Controlling AS.
Step 5.
The MSGin5G Server resolves the group ID to determine the members of that group, based on the information from the group management server as specified in TS 23.434. The MSGin5G Server sends the message to all participants of the group by their UE Service ID. The MSGin5G message request includes the information elements from Table 8.3.3-1. The MSGin5G Server routes, using the procedures in clause 8.3.3, the message to:
  1. a MSGin5G UE;
  2. a Legacy 3GPP UE;
  3. a Non-3GPP UE ; or
  4. an Application Server.
Step 6.
Upon receiving the group message, if message delivery status report is requested and if supported by target message client, the MSGin5G Client or Legacy 3GPP UE or Non-3GPP UE or Application Server sends the message delivery status report to originator MSGin5G Client 1 as specified in clause 8.2.4 and 8.3.5.
Up

8.7.4.3  Message delivery procedure from Application Server to group  p. 104

Figure 8.7.4.3-1 shows the MSGin5G Group messaging procedure in which the Application Server sends a message to a group.
Pre-conditions:
  1. An MSGin5G Group is created by following group management SEAL service procedures as specified in TS 23.434.
Copy of original 3GPP image for 3GPP TS 23.554, Fig. 8.7.4.3-1: Group messaging in MSGin5G Service
Figure 8.7.4.3-1: Group messaging in MSGin5G Service
(⇒ copy of original 3GPP image)
Up
Step 1.
The Application Server sends a message to a group as specified in clause 8.3.2.
Step 2.
Upon receiving the MSGin5G message request, if the AS is authorized to send the group message, the MSGin5G Server resolves the group ID to determine the members of that group, based on the information from the group management server specified in TS 23.434.
Step 3.
The MSGin5G Server sends the message to all participants of the group based on UE Service ID. The MSGin5G message Request includes Originating AS Service ID, Recipient Group ID, Recipient UE Service ID, Message ID, Payload information elements from Table 8.3.3-1. The MSGin5G message Request may include Delivery Status Required, Application ID and Priority Type information elements from Table 8.3.3-1. The MSGin5G Server routes, using the procedures in clause 8.7.2, the message to:
  1. a MSGin5G UE,
  2. a Legacy 3GPP UE,
  3. a Non-3GPP UE.
Step 4.
Upon receiving the group message, if message delivery status report is requested and if supported by the target message client, the MSGin5G Client or Legacy 3GPP UE or Non-3GPP message client sends the message delivery status report to originator Application Server as specified in clause 8.3.4 and 8.3.5.
Up

Up   Top   ToC