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 E2E Message delivery procedures  8.7.1 Point-to-Point Message delivery procedures  8.7.1.1 From MSGin5G UE to MSGin5G UE  8.7.1.2 From MSGin5G UE to Legacy 3GPP UE  8.7.1.3 From MSGin5G UE to Non-3GPP UE  8.7.1.4 From Legacy 3GPP UE to MSGin5G UE  8.7.1.5 From Non-3GPP UE to MSGin5G UE 
...

 

8.7  E2E Message delivery procedures  p. 90

8.7.1  Point-to-Point Message delivery procedures  p. 90

8.7.1.1  From MSGin5G UE to MSGin5G UE  p. 90

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

8.7.1.2  From MSGin5G UE to Legacy 3GPP UE  p. 91

Figure 8.7.1.2-1 shows the message delivery procedure from MSGin5G UE to Legacy 3GPP UE.
Pre-conditions:
  1. MSGin5G Client in MSGin5G UE has registered with the MSGin5G Server and the Message Gateway has registered with the MSGin5G Server on behalf of the Legacy 3GPP UE.
  2. Legacy 3GPP Message Gateway is aware of the UE Service ID of Legacy 3GPP UE and maintains the mapping to IDs used in the legacy network.
Copy of original 3GPP image for 3GPP TS 23.554, Fig. 8.7.1.2-1: Message delivery from MSGin5G UE to Legacy 3GPP UE
Figure 8.7.1.2-1: Message delivery from MSGin5G UE to Legacy 3GPP UE
(⇒ 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 following clarifications:
  1. The MSGin5G message request includes Originating UE 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 MSGin5G message request, the MSGin5G Server determines if the MSGin5G Client is authorized to send a message to the recipient UE.
Step 3.
The MSGin5G Server forwards the 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 8.3.3.
Step 4.
The Legacy 3GPP Message Gateway determines which legacy 3GPP message delivery mechanism (e.g. SMS, NIDD, Device triggering) will be used based on Legacy 3GPP UE capability, the UE communication status, and the MSGin5G Service configuration. When selected, the Legacy 3GPP Message Gateway maps the UE Service ID to the corresponding identifier. For example (not an exhaustive list):
  1. if the Legacy 3GPP Message Gateway selected the device triggering delivery mechanism, it maps the UE Service ID to MSISDN and Application port ID
  2. if the Legacy 3GPP Message Gateway selected the NIDD delivery mechanism, it maps the UE Service ID to External Identifier or MSISDN.
  3. if the Legacy 3GPP Message Gateway selected the SMS delivery mechanism, it maps the UE Service ID to MSISDN.
Step 5-7.
The Legacy 3GPP Message Gateway sends the payload of the MSGin5G message to the terminating Legacy 3GPP UE using the determined delivery mechanism. For example:
  1. For Device triggering delivery mechanism, the Legacy 3GPP Message Gateway interacts with the MTC-IWF/SCEF/NEF and maps the payload of the MSGin5G message to one or more Device Triggering requests. The MTC-IWF/SCEF/NEF interacts with SMS-SC for delivery to the UE and to receive the message delivery status report (see clause 5.2 of TS 23.682, clause 4.4.6 of TS 29.122 and clause 4.4.3 of TS 29.522)
  2. For NIDD delivery mechanism, the Legacy 3GPP Message Gateway may interact with the SCEF/NEF and maps the payload of the MSGin5G message to one or more NIDD submit request messages. The Reliable Data Service Configuration, Maximum Latency, Priority, PDN Connection Establishment Option settings are based on pre-configurations (see clause 5.13 of TS 23.682, clause 4.4.5.3 of TS 29.122 and clause 4.4.12.3 of TS 29.522). Alternatively, if tunnel parameters are provisioned in the Legacy 3GPP Message Gateway and UPF/P-GW the payload could be tunnelled via the UPF/P-GW (see clause 4.3.17.8.3.3 of TS 23.401, clause 5.6.10.3 of TS 23.501, clause 4.24 of TS 23.502);
  3. For SMS delivery mechanism, the Legacy 3GPP Message Gateway sends SMS to the Legacy 3GPP UE through the SMSC according to the procedure in TS 23.204 or the procedure in clause 4.13.3 of TS 23.502.
Step 8.
If Delivery status required is included in the MSGin5G message request, the Legacy 3GPP Message Gateway sends the MSGin5G message delivery status report to the MSGin5G Server as specified in clause 8.3.4 and then the MSGin5G Server sends the message delivery status report to the MSGin5G Client as specified in clause 8.3.5.
Up

8.7.1.3  From MSGin5G UE to Non-3GPP UE  p. 92

Figure 8.7.1.3-1 shows the message delivery procedure from MSGin5G UE to Non-3GPP UE.
Pre-conditions:
  1. MSGin5G Client in MSGin5G UE has registered with the MSGin5G Server and the Non-3GPP Message Gateway has registered with the MSGin5G Server on behalf of the Non-3GPP UE.
  2. 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.1.3-1: Message Delivery from MSGin5G UE to Non-3GPP UE
Figure 8.7.1.3-1: Message Delivery from MSGin5G UE to Non-3GPP UE
(⇒ copy of original 3GPP image)
Up
Step 1.
The Application Client in the MSGin5G UE triggers the MSGin5G Client to send an MSGin5G message request to the MSGin5G Server as specified in 8.3.2 with following clarifications:
  1. The MSGin5G message request includes Originating UE 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.
The MSGin5G Server determines if the MSGin5G Client is authorized to send a message to the recipient UE.
Step 3.
The MSGin5G Server forwards the 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.6.1.
Step 4.
The Non-3GPP Message Gateway translates the MSGin5G message to the Non-3GPP message with message delivery status report, if appropriate, requested and sends it to the Non-3GPP Message Client. This step is outside the scope of the present specification.
Step 5.
If message delivery status report is requested, 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 forwards the MSGin5G message delivery status report to the MSGin5G Client as specified in clause 8.3.5.
Up

8.7.1.4  From Legacy 3GPP UE to MSGin5G UE  p. 93

This procedure is used for message reply from Legacy 3GPP UE (e.g. SMS UE) to MSGin5G UE.
Figure 8.7.1.4-1 shows the response message delivery procedure from Legacy 3GPP UE (e.g. SMS UE) to MSGin5G UE.
Pre-conditions:
  1. MSGin5G Client in MSGin5G UE has registered with the MSGin5G Server and the Legacy 3GPP Message Gateway has registered with the MSGin5G Server on behalf of the Legacy 3GPP UE.
  2. The Legacy 3GPP UE received a message from the MSGin5G UE.
  3. The Legacy 3GPP Message Gateway is aware of the Legacy 3GPP UE and provides the mapping to UE Service ID.
  4. The Legacy 3GPP UE replies to the MSGin5G UE upon receiving the message from the MSGin5G UE.
  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.1.4-1: Legacy 3GPPs UE replies to MSGin5G UE
Figure 8.7.1.4-1: Legacy 3GPPs UE replies to MSGin5G UE
(⇒ 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 SMS message into MSGin5G message and 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 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 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 MSGin5G UE.
Step 3.
The MSGin5G Server forwards the MSGin5G message request to the target MSGin5G Client as specified in clause 8.3.3.
Step 4-6.
If the message delivery status report is requested, the MSGin5G Client in MSGin5G UE sends an MSGin5G message delivery status report to the MSGin5G Server as specified in clause 8.3.4, the MSGin5G Server sends the MSGin5G message delivery status report to the Legacy 3GPP Message Gateway specified in clause 8.3.5, the Legacy 3GPP Message Gateway translates the MSGin5G message delivery status report to a Legacy 3GPP message delivery status report and sends it to the Legacy 3GPP UE.
Up

8.7.1.5  From Non-3GPP UE to MSGin5G UE  p. 95

This procedure is used for message reply from Non-3GPP UE to MSGin5G UE.
Figure 8.7.1.5-1 shows the message delivery procedure from Non-3GPP UE to MSGin5G UE.
Pre-conditions:
  1. MSGin5G Client in MSGin5G UE has registered with the MSGin5G Server and the Non-3GPP Message Gateway has registered with the MSGin5G Server on behalf of the Non-3GPP UE.
  2. The Non-3GPP UE received a message from the MSGin5G UE.
  3. The Non-3GPP Message Gateway is aware of the Non-3GPP message client on the Non-3GPP UE and provides the mapping to UE Service ID.
  4. The Non-3GPP UE replies to the MSGin5G UE upon receiving the message from the MSGin5G UE.
  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.1.5-1: Non-3GPP UE replies to MSGin5G UE
Figure 8.7.1.5-1: Non-3GPP UE replies to MSGin5G UE
(⇒ 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 to MSGin5G message with message delivery status report requested and 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 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 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 MSGin5G UE.
Step 3.
The MSGin5G Server forwards the MSGin5G message request to the target MSGin5G Client as specified in clause 8.3.3.
Step 4.
If the message delivery status report is requested by the Non-3GPP UE, the MSGin5G Client in MSGin5G UE sends an MSGin5G message delivery status report to the MSGin5G Server specified in clause 8.3.4, the MSGin5G Server sends the MSGin5G message delivery status report to the Non-3GPP Message Gateway specified in clause 8.3.5, the Non-3GPP Message Gateway translates the MSGin5G message delivery status report to a Non-3GPP message delivery status report and sends it to the Non-3GPP UE.
Up

Up   Top   ToC