Tech-invite  3GPPspace  IETF RFCs  SIP
index  N  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:  18.2.0

Top   Top   Up   Prev   Next
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.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. 94

8.7.4.1  General  p. 94

This clause introduces a group messaging procedure for MSGin5G Client and MSGin5G Server to send and receive Group message 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. 95

Figure 8.7.4.2-1 shows the MSGin5G Group messaging procedure in which MSGin5G Client (both IMS and non-IMS UE) 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.
  2. All participants in the MSGin5G Group may get the Group information i.e. the Group Service ID.
  3. The group consists of different types of UEs i.e. MSGin5G UE, Legacy 3GPP UE and Non-3GPP UE.
  4. 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.
The MSGin5G Client 1 sends a message to a group as specified in clause 8.3.2 with following clarifications:
  1. The MSGin5mG Message request includes Originating UE Service ID, Recipient Group Service ID and Message ID information elements from Table 8.3.2-1. The MSGin5G message request may include Delivery status required, Application ID, Payload and Priority type information elements from Table 8.3.2-1.
Step 2.
Upon receiving the MSGin5G message request to send the group message, the MSGin5G Server may send the message to the Application Server based on service ID present in the received MSGin5G message request (e.g. to log application specific message or for analytics). Otherwise go to step 4.
  1. Upon receiving the MSGin5G message request, the Application Server validates the message and if the message is not valid, the Application Server sends MSGin5G message response with delivery status set as Reject to the MSGin5G Server. Otherwise, go to step 3.
  2. The MSGin5G Server sends the MSGin5G message response with delivery status set as reject to the MSGin5G Client 1. The information elements defined in Table 8.3.2-3 are included in the response. Following procedures will be skipped.
Step 3.
The Application Server initiates to send message to all group members and sends the MSGin5G message request to the MSGin5G Server.
Step 4.
Upon receiving the MSGin5G message request, if the MSGin5G Server determines the MSGin5G Client-1 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 as specified in TS 23.434.
Step 5.
The MSGin5G Server sends the message to all participants of the group by their UE Service ID. The MSGin5G message request includes Originating UE 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.3.3, the message to:
  1. the MSGin5G UE,
  2. the Legacy 3GPP UE,
  3. the Non-3GPP UE.
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 message client 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. 96

Figure 8.7.4.3-1 shows the MSGin5G Group messaging procedure in which 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.
  2. The group consists of different types of UEs i.e. MSGin5G UE, Legacy 3GPP UE and Non-3GPP UE, they may receive group message from one Application Server.
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. the MSGin5G UE,
  2. the Legacy 3GPP UE,
  3. the Non-3GPP UE.
Step 4.
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 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