Tech-invite  3GPPspace  IETF RFCs  SIP
Quick  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.2 Application-to-Point Message delivery procedures  8.7.2.1 From Application Server to MSGin5G UE  8.7.2.2 From Application Server to Legacy 3GPP UE  8.7.2.3 From Application Server to Non-3GPP UE 
...

 

8.7.2  Application-to-Point Message delivery procedures  p. 88

8.7.2.1  From Application Server to MSGin5G UE  p. 88

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 a secured communication with the MSGin5G Server
Copy of original 3GPP image for 3GPP TS 23.554, Fig. 8.7.2.1-1: Message delivery from Application Server to MSGin5G UE
Figure 8.7.2.1-1: Message delivery from Application Server to MSGin5G UE
(⇒ copy of original 3GPP image)
Up
Step 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:
  1. The API request includes Originating AS Service ID, Recipient UE Service ID and Message ID information elements in 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 MSGin5G UE.
Step 2.
The MSGin5G Server sends MSGin5G message request to MSGin5G Client as specified in clause 8.3.3.
Step 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.
Step 4.
The MSGin5G Server sends the message delivery status report to the Application Server as specified in clause 8.3.5
Up

8.7.2.2  From Application Server to Legacy 3GPP UE  p. 89

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 a secured communication with the MSGin5G Server
  2. The Legacy 3GPP Message Client in Legacy 3GPP UE has registered with the MSGin5G Server via the Legacy 3GPP Message Gateway.
  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.
Copy of original 3GPP image for 3GPP TS 23.554, Fig. 8.7.2.2-1: Application Server to Legacy 3GPP UE messaging
Figure 8.7.2.2-1: Application Server to Legacy 3GPP UE messaging
(⇒ copy of original 3GPP image)
Up
Step 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:
  1. The API Request includes Originating AS Service ID, Recipient UE Service ID and Message ID information elements in Table 8.3.2-1, and may include Delivery status required, Application ID, Payload, Priority type information elements from Table 8.3.2-1.
Step 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
Step 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.
Step 4-7.
Same with step 4-7 in clause 8.7.1.2
Step 8.
The Legacy 3GPP Message Gateway sends the MSGin5G message delivery status report to the MSGin5G Server as specified in clause 8.3.4.
Up

8.7.2.3  From Application Server to Non-3GPP UE  p. 91

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 Client in Non-3GPP UE has registered with the MSGin5G Server via the Non-3GPP Message Gateway.
  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.
Copy of original 3GPP image for 3GPP TS 23.554, Fig. 8.7.2.3-1: Application Server to Non-3GPP UE messaging
Figure 8.7.2.3-1: Application Server to Non-3GPP UE messaging
(⇒ copy of original 3GPP image)
Up
Step 1.
The Application Serve sends an API Request to MSGin5G Server for sending MSGin5G message as specified in 8.3.2 with the following clarifications:
  1. The API Request includes Originating AS Service ID, Recipient UE Service ID and Message ID information elements in Table 8.3.2-1, and may include Delivery status required, Application ID, Payload, Priority type information elements from Table 8.3.2-1.
Step 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.
Step 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.
Step 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.
Step 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.
Up

Up   Top   ToC