MSGin5G message may be delivered between different PLMNs.
The procedure specified in
clause 8.7.5.2 applies to Point-to-Point message and Group message, and may also apply to Application-to-Point message and Point-to-Application message delivery if agreed by the business agreement between the PLMNs. The procedure specified in
clause 8.7.5.3 applies to Message delivery based on Messaging Topic.
Figure 8.7.5.2-1 shows message delivery between MSGin5G endpoints in different PLMNs, where Message Sender is registered in MSGin5G Server 1 and Message Receiver is registered in MSGin5G Server 2.
Pre-condition:
-
The Message Sender (e.g. MSGin5G Client 1 in MSGin5G UE 1) is registered to the MSGin5G Server 1 in one PLMN.
-
The Message Receiver (e.g. MSGin5G Client 2 in MSGin5G UE 2) is registered to the MSGin5G Server 2 in another PLMN.
-
MSGin5G Server 1 and MSGin5G Server 2 have established a secured connection.
Step 1.
The Message Sender sends an MSGin5G message request to MSGin5G Server 1 in PLMN 1 as specified in
clause 8.3.2.
Step 2.
The MSGin5G Server 1 analyses the target UE Service ID and determines that the message is targeted to the Message Receiver in PLMN 2, authenticates that the Message Sender is allowed to send a message to the Message Receiver, and then the MSGin5G Server 1 forwards the MSGin5G message request to MSGin5G Server 2 in PLMN 2.
Step 3.
MSGin5G Server 2 forwards the MSGin5G message request to the Message Receiver as specified in
clause 8.3.3.
Step 4-6.
If the message delivery status report is requested, the Message Receiver sends a message delivery status report to Message Sender as per procedure specified in
clause 8.3.4 and 8.3.5.
Figure 8.7.5.3-1 shows the inter-PLMN Message delivery based on Messaging Topic when MSGin5G Server 2 forwards the Messaging Topic subscription request from the MSGin5G UE/Application Server served by it to MSGin5G Server 1 as specified in
clause 8.8.4.
Pre-condition:
-
The Message Sender (e.g. an MSGin5G UE, a Message Gateway on behalf of a Non-MSGin5G UE or an Application Server) is registered to the MSGin5G Server 1 in PLMN 1.
-
The Message Receiver (e.g. an MSGin5G UE, a Message Gateway on behalf of a Non-MSGin5G UE or an Application Server) is registered to the MSGin5G Server 2 in PLMN 2.
-
MSGin5G Server 1 and MSGin5G Server 2 have established a secured connection.
-
MSGin5G Client or Application Server served by MSGin5G Server 2 has subscribed to a Messaging Topic with the MSGin5G Server 1 as specified in clause 8.8.4 via MSGin5G Server 2.
Step 1.
The Message Sender sends an MSGin5G message request (if the sender is an MSGin5G UE) or API request (if the sender is an Application Server or a Message Gateway on behalf of a Non-MSGin5G UE) to MSGin5G Server 1 in PLMN 1 as specified in
clause 8.3.2. A Messaging Topic is included in this request.
Step 2.
The MSGin5G Server 1 checks the subscription the Messaging Topic included in the inbound request and obtains the UE Service ID/AS Service ID of the Message Receiver. The MSGin5G Server 1 determines that the message with ths Messaging Topic is needed to be delivered to an MSGin5G UE/Application Server served by Message Server 2 in PLMN 2 based on the UE Service ID/AS Service ID of the Message Receiver. The MSGin5G Server 1 then sends the MSGin5G message to MSGin5G Server 2.
Step 3.
The MSGin5G Server 2 delivers the MSGin5G message request to Messager Receiver based on the UE Service ID/AS Service ID in the inbound message as specified in
clause 8.3.3.
Step 4-6.
If the message delivery status report is requested, the Message Receiver sends message delivery status report to Message Sender as per procedure specified in
clause 8.3.4 and
clause 8.3.5.
Figure 8.7.5.3-2 shows the inter-PLMN Message delivery to subscribing service endpoints based on Messaging Topic when MSGin5G Server 2 subscribe the Messaging Topic on behalf of all MSGin5G UEs/Application Servers served by it as specified in
clause 8.8.4.
Pre-condition:
-
The Message Sender (e.g. an MSGin5G UE, a Message Gateway on behalf of a Non-MSGin5G UE or an Application Server) is registered to the MSGin5G Server 1 in PLMN 1.
-
The Message Receiver (e.g. an MSGin5G UE, a Message Gateway on behalf of a Non-MSGin5G UE or an Application Server) is registered to the MSGin5G Server 2 in PLMN 2.
-
MSGin5G Server 1 and MSGin5G Server 2 have established a secured connection.
-
MSGin5G Server 2 subscribed to a Messaging Topic with the MSGin5G Server 1 as specified in clause 8.8.4. A Messaging Topic with the MSGin5G Server 2 address of the subscriber has been created on MSGin5G Server 1.
-
The MSGin5G Client or Application Server served by MSGin5G Server 2 subscribed to the Messaging Topic with the MSGin5G Server 2. A Messaging Topic with the UE Service ID/AS Service ID of the subscriber has been created on MSGin5G Server 2.
Step 1.
The Message Sender sends an MSGin5G message request (if the sender is an MSGin5G UE) or API request (if the sender is an Application Server or a Message Gateway) to MSGin5G Server 1 in PLMN 1 as specified in
clause 8.3.2. A Messaging Topic is included in this request.
Step 2.
The MSGin5G Server 1 checks the subscription the Messaging Topic included in the inbound request and obtains the MSGin5G Server 2 address. The MSGin5G Server 1 determines that the message with ths Messaging Topic is needed to be delivered to the Message Server 2 in PLMN 2 and sends the MSGin5G message to MSGin5G Server 2.
Step 3a.
The MSGin5G Server 2 checks the subscription the Messaging Topic included in the inbound request and obtains the UE Service ID/AS Service ID of the Message Receiver 1. The MSGin5G Server 2 delivers the MSGin5G message request to Messager Receiver 1 based on its UE Service ID/AS Service ID as specified in
clause 8.8.2.
Step 3b.
The MSGin5G Server 2 also delivers the MSGin5G message request to Messager Receiver 2 which subscribed this Messaging Topic as specified in
clause 8.8.2.
Step 4a-6a.
If the message delivery status report is requested, the Message Receiver 1 sends message delivery status report to Message Sender as per procedure specified in
clause 8.3.4 and
clause 8.3.5.
Step 4b-6b.
If the message delivery status report is requested, the Message Receiver 2 sends message delivery status report to Message Sender as per procedure specified in
clause 8.3.4 and
clause 8.3.5.