Tech-invite3GPPspaceIETF RFCsSIP
Quick21222324252627282931323334353637384‑5x

Content for  TS 23.554  Word version:  18.0.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  Usage of Network Capabilitiesp. 94

8.9.1  Generalp. 94

The present clause specifies the functionality leveraged by the MSGin5G Service via Core Network exposure.

8.9.2  UE reachability status monitoringp. 94

8.9.2.1  Generalp. 94

UE reachability status leverages the 3GPP network monitoring functionality exposed via T8/N33 reference point detailed in TS 23.502 and TS 29.522. How the MSGin5G Server determines whether and how (e.g., via request/response or subscription) to monitor the UE reachability using the 3GPP Network capabilities is implementation dependent.
Up

8.9.2.2  Proceduresp. 94

8.9.2.2.1  Request-responsep. 94
Figure 8.9.2.2.1-1 shows the procedure which may be used by the MSGin5G Server to make a request for UE reachability status information.
Pre-conditions:
  1. A UE hosts an MSGin5G Client.
  2. The MSGin5G Client registers with the MSGin5G Server and shares UE contact information.
  3. The MSGin5G Server determines to subscribe for monitoring of UE reachability events in the Core Network, e.g., that the UE is a sleepy node.
Copy of original 3GPP image for 3GPP TS 23.554, Fig. 8.9.2.2.1-1: MSGin5G reachability status request-response.
Up
Step 1.
The MSGin5G Server sends a one-time Monitoring Request to the 3GPP Network using SCEF/NEF capabilities.
The one-time Monitoring Request includes monitoring type set to UE_REACHABILITY, Maximum Number of Reports of 1 and does not include the Monitoring Duration IE.
Step 2.
The 3GPP network processes the monitoring request and determines the reachability status of the UE(s), as described in TS 29.122.
Step 3.
If the Monitoring Request is successfully processed, a monitoring response providing the UE(s) reachability status is sent to the MSGin5G Server. The response may include idle mode information e.g., active time granted to the UE, eDRX cycle length, periodic RAU/TAU timer, etc., depending on the parameters indicated in the request.
Up
8.9.2.2.2  Subscribep. 95
Figure 8.9.2.2.2-1 shows the procedure which may be used by the MSGin5G Server to subscribe for monitoring of UE reachability.
Pre-conditions:
  1. A UE hosts an MSGin5G Client.
  2. The MSGin5G Client registers with the MSGin5G Server and shares UE contact information.
  3. The MSGin5G Server determines to subscribe for monitoring of UE reachability events in the Core Network, e.g., that the UE is a sleepy node.
Copy of original 3GPP image for 3GPP TS 23.554, Fig. 8.9.2.2.2-1: MSGin5G reachability status subscribe.
Up
Step 1.
The MSGin5G Server sends a Monitoring Event Subscribe request to the 3GPP Network using existing SCEF/NEF capabilities.
The Monitoring Event Subscribe is a Monitoring Request with monitoring type set to UE_REACHABILITY , and either the Maximum Number of Reports greater than 1 or the Monitoring Duration IE are included.
Step 3.
The 3GPP network processes the Monitoring Event Subscribe request as described in TS 29.122.
Step 4.
If the Monitoring Event Subscribe Request is successfully processed, a response indicating the request was accepted is sent to the MSGin5G Server.
Up
8.9.2.2.3  Notifyp. 96
Figure 8.9.2.2.3-1 shows the procedure which may be for updating MSGin5G reachability status.
Pre-conditions:
  1. The MSGin5G Server has subscribed for reachability status monitoring for a UE or group of UEs.
  2. The monitored UE(s) transitions to Connected Mode, Idle Mode or eDRX paging occasion and the 3GPP Network Entities detects the change in UE reachability status.
Copy of original 3GPP image for 3GPP TS 23.554, Fig. 8.9.2.2.3-1: MSGin5G reachability status notify.
Up
Step 1.
Based on the reachability status change of a monitored UE(s), the 3GPP Network sends a Monitoring Notification message for UE reachability to the MSGin5G Server as specified in TS 29.122.
The notification may include idle mode information e.g., active time granted to the UE, eDRX cycle length, periodic RAU/TAU timer, etc., depending on the subscription.
Step 2.
After receiving a UE Reachability monitoring notification, the MSGin5G Server responds with an acknowledgement of the notification via SCEF/NEF.
Step 3.
The MSGin5G Server uses the information provided in the UE reachability monitoring event report to update its information on the UE's availability, e.g., MSGin5G Client Availability information. The MSGin5G Server may provide additional services based on reachability information, e.g., forward a stored message, etc.
Up
8.9.2.2.4  Unsubscribep. 97
Figure 8.9.2.2.4-1 shows the procedure which may be used by the MSGin5G Server to unsubscribe from monitoring of UE reachability.
Pre-conditions:
  1. The MSGin5G Server has subscribed for reachability status monitoring for a UE or group of UEs.
  2. Later, the MSGin5G Server determines to unsubscribe for monitoring of UE reachability events in the Core Network,
Copy of original 3GPP image for 3GPP TS 23.554, Fig. 8.9.2.2.4-1: MSGin5G reachability status unsubscribe.
Up
Step 1.
The MSGin5G Server sends a Monitoring event unsubscribe request to the 3GPP Network using existing SCEF/NEF capabilities.
Step 2.
The 3GPP network processes the Monitoring event unsubscribe request and deletes the subscription, as described in TS 29.122.
Step 3.
If the Monitoring event unsubscribe request is successfully processed, a response indicating the subscription was deleted is sent to the MSGin5G Server via SCEF/NEF.

8.9.2.3  Flowsp. 98

The following information flows are specified for UE reachability status monitoring:
  • UE Reachability monitoring request and response;
  • UE Reachability monitoring subscribe and unsubscribe
  • UE Reachability monitoring notify
All UE reachability monitoring interactions from MSGin5G Server (acting as SCS/AS) to SCEF/NEF occur over T8/N33 reference points capabilities detailed in TS 23.502 and TS 29.522. As specified in TS 29.522, clause 4.4.2, all UE Reachability monitoring procedures use APIs specified in TS 23.682, clause 5.6.1.4 and TS 29.122, clause 4.4.2.2.
Up

Up   Top   ToC