Tech-invite  3GPPspace  IETFspace
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:  19.3.0

Top   Top   Up   Prev   Next
1…   4…   5…   5.3…   5.5…   6…   7…   8…   8.2…   8.2.7…   8.2.11   8.3…   8.3.5…   8.4…   8.4.3   8.5…   8.6…   8.7…   8.7.2…   8.7.3…   8.7.4…   8.7.5…   8.7.6…   8.8…   8.9…   8.10…   8.11…   9…   9.2…   10…   11… 
8.7.3 Point-to-Application Message delivery procedures  8.7.3.1 From MSGin5G UE to Application Server  8.7.3.2 From Legacy 3GPP UE to Application Server  8.7.3.3 From Non-3GPP UE to Application Server 
...

 

8.7.3  Point-to-Application Message delivery procedures  p. 99

8.7.3.1  From MSGin5G UE to Application Server  p. 99

Figure 8.7.3.1-1 shows the message delivery procedure from MSGin5G UE to Application Server.
Pre-conditions:
  1. The Application Server and MSGin5G Client in MSGin5G UE have registered with the MSGin5G Server.
Copy of original 3GPP image for 3GPP TS 23.554, Fig. 8.7.3.1-1: Message delivery from MSGin5G UE to Application Server
Figure 8.7.3.1-1: Message delivery from MSGin5G UE to Application Server
(⇒ copy of original 3GPP image)
Up
Step 1.
The MSGin5G Client sends an MSGin5G message request to the MSGin5G Server as specified in clause 8.3.2 with the following clarifications:
  1. The MSGin5G message request includes Originating UE Service ID, Recipient AS 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 MSGin5G message request, the MSGin5G Server determines if the MSGin5G Client is allowed to send message to Application Server.
Step 2.
The MSGin5G Server forwards the MSGin5G message request to the Application Server as specified in clause 8.3.3.
Step 3-4.
If Delivery status required is included in the MSGin5G message request, the Application Server sends the message delivery status report to the MSGin5G Server as specified in clause 8.3.4, the MSGin5G Server sends the delivery status to MSGin5G Client as specified in clause 8.3.5.
Up

8.7.3.2  From Legacy 3GPP UE to Application Server  p. 100

This procedure is used for message reply from Non-3GPP UE to Application Server.
Figure 8.7.3.2-1 shows the message delivery procedure from Legacy 3GPP UE to Application Server.
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 message client in the Legacy 3GPP UE.
  3. The Legacy 3GPP UE received a message from the Application Server.
  4. The Legacy 3GPP Message Gateway is aware of the Legacy 3GPP Message client on the Legacy 3GPP UE and provides the mapping between its identifiers and UE Service ID.
  5. The Legacy 3GPP Message Gateway implementation supports storing a messaging transaction, i.e. mapping the message originating MSGin5G Service ID and the message delivered to the Legacy 3GPP UE, for an operator configured time period to allow if the Legacy 3GPP UE will send a response to the incoming message.
Copy of original 3GPP image for 3GPP TS 23.554, Fig. 8.7.3.2-1: Legacy 3GPP UE replies to Application Server
Figure 8.7.3.2-1: Legacy 3GPP UE replies to Application Server
(⇒ copy of original 3GPP image)
Up
Step 1.
The Legacy 3GPP UE sends a Legacy 3GPP message request to the Legacy 3GPP Message Gateway (e.g. through SMSC if SMS is used according the procedure in TS 23.204 or the procedure in clause 4.13.3 of TS 23.502).
Step 2.
The Legacy 3GPP Message Gateway translates the Legacy 3GPP message into an MSGin5G message and may include message delivery status report requested in the MSGin5G message. The Legacy 3GPP Message Gateway sends the MSGin5G message request to the MSGin5G Server as specified in clause 8.3.2 with the following clarifications:
  1. The MSGin5G message request includes Originating UE Service ID, Recipient AS Service ID and Message ID information elements from Table 8.3.2-1, and may include Delivery status required, and may include Application ID, Payload and Priority type information elements from Table 8.3.2-1.
  2. Upon receiving the MSGin5G message request, the MSGin5G Server determines if the Legacy 3GPP UE with its UE Service ID is allowed to send a message to the Application Server.
Step 3.
The MSGin5G Server forwards the MSGin5G message in API request to the Application Server as specified in clause 8.3.3.
Step 4-6.
If message delivery status report is requested, the Application Server sends the message delivery status report by API request to the MSGin5G Server as specified in clause 8.3.4, the MSGin5G Server forwards the message delivery status report to the Legacy 3GPP Message Gateway as specified in clause 8.3.5, the Legacy 3GPP Message Gateway translates the MSGin5G message delivery status report into a Legacy 3GPP message delivery status report and sends it to the Legacy 3GPP UE.
Up

8.7.3.3  From Non-3GPP UE to Application Server  p. 101

This procedure is used for message reply from Legacy 3GPP UE to Application Server.
Figure 8.7.3.3-1 shows the message delivery procedure from Non-3GPP UE to Application Server.
Pre-conditions:
  1. The Application Server has established 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. The Non-3GPP UE received a message from the Application Server.
  4. The Non-3GPP Message Gateway is aware of the Non-3GPP message client on the Non-3GPP UE and provides the mapping between its identifiers and UE Service ID.
  5. The Non-3GPP Message Gateway implementation supports storing a messaging transaction, i.e. mapping the message originating MSGin5G Service ID and the message delivered to the Non-3GPP UE, for an operator configured time period to allow if the Non-3GPP UE will send a response to the incoming message.
Copy of original 3GPP image for 3GPP TS 23.554, Fig. 8.7.3.3-1: Non-3GPP UE replies to Application Server
Figure 8.7.3.3-1: Non-3GPP UE replies to Application Server
(⇒ copy of original 3GPP image)
Up
Step 1.
The Non-3GPP UE sends a Non-3GPP message request to the Non-3GPP Message Gateway.
Step 2.
The Non-3GPP Message Gateway translates the Non-3GPP Message into an MSGin5G message and may include MSGin5G message delivery status report requested in the MSGin5G message. The Non-3GPP Message Gateway sends an MSGin5G message request to the MSGin5G Server as specified in clause 8.3.2 with the following clarifications:
  1. The MSGin5G message request includes Originating UE Service ID, Recipient AS 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 MSGin5G message request, the MSGin5G Server determines if the Non-3GPP UE with its UE Service ID is allowed to send a message to the Application Server.
Step 3.
The MSGin5G Server forwards the MSGin5G message in an API request to the Application Server as specified in clause 8.3.3.
Step 4-6.
If the delivery status is required, the Application Server sends a message delivery status report by API request to the MSGin5G Server as specified in clause 8.3.4, the MSGin5G Server sends the message delivery status report to the Non-3GPP Message Gateway as specified in clause 8.3.5, the Non-3GPP Message Gateway translates the MSGin5G message delivery status report into a Non-3GPP message delivery status report and sends it to the Non-3GPP UE.
Up

Up   Top   ToC