8.7.2 Application-to-Point Message delivery procedures

23.5543GPPApplication architecture for MSGin5G ServiceRelease 18Stage 2TS

Tools: ARFCN - Frequency Conversion for 5G NR/LTE/UMTS/GSM

8.7.2.1 From Application Server to MSGin5G UE

Editor’s note: It is FFS whether and how NIDD can be chosen as alternative delivery mechanism in application -to-Point message delivery to MSGin5G UEs.

Figure 8.7.2.1-1 shows the message delivery procedure from Application Server to MSGin5G UE.

Pre-conditions:

1. The MSGin5G Client is registered with the MSGin5G Server.

2. The Application Server has established secured communication with the MSGin5G Server.

Figure 8.7.2.1-1 Message delivery from Application Server to MSGin5G UE

1. The Application Server sends API Request to MSGin5G Server for sending MSGin5G message as specified in clause 8.3.2 with the following clarifications:

a) The API request includes Originating AS Service ID, Recipient UE Service ID and Message ID information elements from Table 8.3.2-1, and may include Delivery status required, Application ID, Payload, Priority type information elements from Table 8.3.2-1.

b) Upon receiving the API Request for MSGin5G message delivery, the MSGin5G Server determines that the Application Server is allowed to send message to the MSGin5G UE.

2. The MSGin5G Server sends MSGin5G message request to MSGin5G Client as specified in clause 8.3.3.

3. If Delivery status required is included in the MSGin5G message request, MSGin5G Client 2 sends message delivery status report to the MSGin5G Server specified in clause 8.3.4.

4. The MSGin5G Server sends the message delivery status report to the Application Server as specified in clause 8.3.5

8.7.2.2 From Application Server to Legacy 3GPP UE

Figure 8.7.2.2-1 shows the message delivery procedure from Application Server to Legacy 3GPP UE.

Pre-conditions:

1. The Application Server has established secured communication with the MSGin5G Server.

2. The Legacy 3GPP Message Gateway has registered with the MSGin5G Server on behalf of the client in the Legacy 3GPP UE.

3. Legacy 3GPP Message Gateway is aware of the legacy 3GPP message client (i.e. SMS client) in Legacy 3GPP UE and provides the mapping to UE Service ID.

Figure 8.7.2.2-1: Application Server to Legacy 3GPP UE messaging

1. The Application Server sends an API Request to MSGin5G Server for sending MSGin5G message as specified in clause 8.3.2 with the following clarifications:

a) The API Request includes Originating AS Service ID, Recipient UE Service ID, and Message ID information elements from Table 8.3.2-1, and may include Delivery status required, Application ID, Payload, Priority type information elements from Table 8.3.2-1.

2. Upon receiving the API Request for MSGin5G message delivery, the MSGin5G Server determines that the Application Server is allowed to send message to the recipient UE.

3. The MSGin5G Server sends MSGin5G message request to the recipient based on the UE Service ID. The Legacy 3GPP Gateway receives the MSGin5G message request on behalf of the Legacy 3GPP UE as specified in clause 8.3.3.

4-7. Same with step 4-7 in clause 8.7.1.2

8. The Legacy 3GPP Message Gateway sends the MSGin5G message delivery status report to the MSGin5G Server as specified in clause 8.3.4.

8.7.2.3 From Application Server to Non-3GPP UE

Figure 8.7.2.3-1 shows the message delivery procedure from Application Server to Non-3GPP UE.

Pre-conditions:

1. The Application Server has established a secured communication with the MSGin5G Server.

2. The Non-3GPP Message Gateway has registered with the MSGin5G Server on behalf of the message client in the Non-3GPP UE.

3. Non-3GPP Message Gateway is aware of the non-3GPP message client in Non-3GPP UE and provides the mapping to UE Service ID.

Figure 8.7.2.3-1 Application Server to Non-3GPP UE messaging

1. The Application Server sends an API Request to MSGin5G Server for sending MSGin5G message as specified in 8.3.2 with the following clarifications:

a) The API Request includes Originating AS Service ID, Recipient UE Service ID and Message ID information elements from Table 8.3.2-1, and may include Delivery status required, Application ID, Payload, Priority type information elements from Table 8.3.2-1.

2. Upon receiving the API Request for MSGin5G message delivery, the MSGin5G Server determines that the Application Server is allowed to send message to the Non-3GPP UE.

3. The MSGin5G Server sends MSGin5G message request to the recipient based on the UE Service ID. The Non-3GPP Message Gateway receives the MSGin5G message request on behalf of the Non-3GPP UE as specified in clause 8.3.3.

4. The Non-3GPP Message Gateway translates the MSGin5G message to the Non-3GPP message and sends it to the Non-3GPP UE. This step is outside the scope of the current specification.

5-6. If message delivery status report is required, the Non-3GPP Message Gateway sends the MSGin5G message delivery status report to the MSGin5G Server as specified in clause 8.3.4, the MSGin5G Server sends the message delivery status report to the Application Server as specified in clause 8.3.5.