Tech-invite3GPPspaceIETF RFCsSIP
Quick21222324252627282931323334353637384‑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.9.3  MSGin5G device triggeringp. 113

8.9.3.1  Generalp. 113

MSGin5G device triggering is the means by which an Application Server sends an MSGin5G message and the 3GPP network device triggering capabilities exposed via T8 /N33 reference point are leveraged. For example, when an Application Server initiates an MSGin5G message request, but the target UE is not reachable, the MSGin5G Server may use the 3GPP network device triggering mechanism to wake up the device and provide the payload to the destination.

8.9.3.2  Procedurep. 114

Figure 8.9.3.2-1 shows the MSGin5G device triggering procedure.
Pre-conditions:
  1. A UE hosts an MSGin5G Client and/or Application Client which are supported by the MSGin5G Service.
  2. The MSGin5G Client registers with the MSGin5G Server.
  3. At a later time, the UE becomes unreachable by the MSGin5G Server.
Copy of original 3GPP image for 3GPP TS 23.554, Fig. 8.9.3.2-1: MSGin5G Triggering Procedure
Figure 8.9.3.2-1: MSGin5G Triggering Procedure
(⇒ copy of original 3GPP image)
Up
Step 1.
The Application Server sends an API request to the MSGin5G Server for sending an MSGin5G message, the API request includes the IEs as detailed in clause 9.1.2.1.
Step 2.
If the MSGin5G Server determines that the recipient MSGin5G Client is not reachable, it initiates a device trigger request via the SCEF/NEF as a result of the step 1 request.
To determine the reachability of the target UE, the MSGin5G Server may use the UE reachability status monitoring procedure in clause 8.9.2. The MSGin5G Server may also use availability information provided by the MSGin5G Client at registration in the MSGin5G Client Communication Availability IE, as detailed in Table 8.2.1-1.
Step 3.
The MSGin5G Server sends a request for Device Triggering via SCEF/NEF and determines the flow as detailed in clause 8.9.3.3.2. The Device Triggering request uses the UE Identifier, port number(s) and associated protocol information provided by the MSGin5G Client at registration in the MSGin5G Client Triggering Information IE.
The MSGin5G Server may use MSGin5G Client Communication Availability and/or pre-configured information to determine the timing of the Device Triggering request, e.g. the trigger may be sent to ensure that the target UE is reachable prior to resuming MSGin5G communications.
Step 4.
The MSGin5G Server receives a response from SCEF/NEF indicating the success or failure status of the request, as detailed in clause 8.9.3.3.
Step 5.
The device trigger is delivered to the target via SCEF/NEF and the Core Network. The targeted MSGin5G Client or Application Client receives the device trigger request. The targeted MSGin5G Client or Application Client parses the payload of the trigger request and determines the device trigger purpose. The target UE becomes reachable, and the MSGin5G Client or Application Client becomes available for further MSGin5G communications.
Step 6.
The MSGin5G Server receives a Device Triggering delivery status report from SCEF/NEF indicating the success of the delivery, as detailed in clause 8.9.3.3.
Step 7.
The MSGin5G Server send a Device Triggering delivery status report response to SCEF/NEF to acknowledge the delivery status report, as detailed in clause 8.9.3.3.
Step 8.
The MSGin5G Server responds to the request received in step 1.
Based on the trigger purpose derived from the payload, the targeted MSGin5G Client or Application Client performs the corresponding actions (e.g. establish access network connectivity, contact the Application Server etc).
Up

8.9.3.3  Flowsp. 115

The following information flows are specified for MSGin5G triggering:
  1. request for device triggering;
  2. response to device triggering;
  3. device triggering delivery report; and
  4. device triggering delivery report response.
All device triggering interactions from MSGin5G Server (acting as SCS/AS) to SCEF/NEF occur over T8/N33 reference points, using capabilities detailed in TS 23.502 and TS 29.522. As specified in TS 29.522, clause 4.4.3, all device triggering flows use APIs specified in TS 23.682, clause 5.17.1 and TS 29.122, clause 4.4.6.
Up

Up   Top   ToC