8.7.4 MSGin5G Group messaging

23.5543GPPApplication architecture for MSGin5G ServiceRelease 18Stage 2TS

8.7.4.1 General

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 3GPP TS 23.434 [5].

8.7.4.2 Message delivery from UE to group

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.

Editor’s note: Solution for the group hosted on the legacy side where MSGin5G Client is one of the group members is FFS.

Pre-conditions:

1. An MSGin5G Group is created by following group management SEAL service procedures as specified in 3GPP TS 23.434 [5].

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 3GPP TS 23.434 [5].

Figure 8.7.4.2-1: Group messaging in MSGin5G Service

1. The MSGin5G Client 1 sends a message to a group as specified in clause 8.3.2 with following clarifications:

a) The MSGin5G 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.

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.

a) 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.

b) 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.

3. The Application Server initiates to send message to all group members and sends the MSGin5G message request to the MSGin5G Server.

Editor’s note: Whether to keep or correct step 2 or 3 is FFS.

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 3GPP TS 23.434 [5].

NOTE: If the originating UE is member of the group, the originating UE is not included as recipient of the group message.

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:

a) a MSGin5G UE,

b) a Legacy 3GPP UE,

c) a Non-3GPP UE.

NOTE: Steps 5 a), 5 b) and 5 c) can happen in parallel and in any order.

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

8.7.4.3 Message delivery procedure from Application Server to group

Figure 8.6.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 3GPP TS 23.434 [5].

Figure 8.7.4.3-1: Group messaging in MSGin5G Service

1. The Application Server sends a message to a group as specified in clause 8.3.2.

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 3GPP TS 23.434 [5].

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:

a) a MSGin5G UE,

b) a Legacy 3GPP UE,

c) a Non-3GPP UE.

NOTE: Steps 3 a), 3 b) and 3 c) can happen in parallel and in any order.

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.