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.502  Word version:  19.1.0

Top   Top   Up   Prev   Next
1…   4.2.2.2.2   4.2.2.2.3…   4.2.2.3…   4.2.3…   4.2.3.3   4.2.4…   4.2.6   4.2.7…   4.2.9…   4.2.11…   4.2.11.5…   4.3…   4.3.2.2.2   4.3.2.2.3…   4.3.3…   4.3.3.3   4.3.4…   4.3.4.3   4.3.5…   4.3.5.2…   4.3.5.4…   4.3.5.6…   4.3.6…   4.4…   4.5…   4.9…   4.9.1.3…   4.9.2…   4.11…   4.11.1…   4.11.1.2.2   4.11.1.2.3   4.11.1.3…   4.11.1.3.3…   4.11.1.4…   4.11.1.5…   4.11.2…   4.11.3…   4.12…   4.12.6…   4.12a…   4.12b…   4.13…   4.13.4…   4.13.6…   4.14…   4.15…   4.15.3.2.5…   4.15.4…   4.15.6…   4.15.6.7…   4.15.6.13…   4.15.6.14…   4.15.9…   4.15.9.4…   4.15.13…   4.15.13.4…   4.16…   4.16.4…   4.16.8…   4.16.11…   4.16.14…   4.16.15…   4.17…   4.17.9…   4.18…   4.19…   4.22…   4.23…   4.23.7…   4.23.7.3.3   4.23.7.3.4…   4.23.9…   4.23.9.4…   4.23.11…   4.24…   4.25…   4.25.6…   4.26…   5…   5.2.3…   5.2.5…   5.2.6…   5.2.7…   5.2.8…   5.2.9…   5.2.12…   5.2.18…   A…   E…   F…   G   H… 
4.25.6 NIDD Authorization Update  4.25.7 SMF Initiated SMF-NEF Connection Release procedure  4.25.8 NEF Initiated SMF-NEF Connection Release procedure  4.25.9 NEF Anchored Group NIDD via NEF anchored unicast MT data 
...

 

4.25.6  NIDD Authorization Update  p. 671

Figure 4.25.6-1 illustrates the procedure for updating or revoking an existing NIDD Authorization.
The UDM may initiate the NIDD Authorization Update procedure with the NEF to send updated Authorization information to the NEF.
Reproduction of 3GPP TS 23.502, Fig. 4.25.6-1: NIDD Authorization Update procedure
Figure 4.25.6-1: NIDD Authorization Update procedure
Up
Step 0.
UDM provided a successful authorization for a NIDD configuration request as defined in clause 4.25.3. The NIDD authorization is modified in UDM (e.g. subscription withdrawal, DNN used for NIDD service is removed from the UE subscription) before expiration of the NIDD Duration previously authorized.
Step 1.
The UDM sends an NIDD Authorization Update information using Nudm_NIDDAuthorisation_UpdateNotify Request (SUPI, GPSI, S-NSSAI, DNN, Result, Cause, NIDD Duration) message to the NEF to update an user's NIDD authorization.
Step 2.
The NEF sends Nudm_NIDDAuthorisation_UpdateNotify Response message to the UDM to acknowledge the authorization update.
Step 3.
If the authorization is removed, the NEF should initiate the SMF-NEF Connection release procedure as specified in clause 4.25.8.
Step 4.
The NEF informs the AF that the user's authorisation status has changed by sending Nnef_NIDDConfiguration_UpdateNotify Request (GPSI, TLTRI, Result, Cause, NIDD Duration) message to the AF to update a user's NIDD authorization.
Step 5.
The AF responds to the NEF with Nnef_NIDDConfiguration_UpdateNotify Response message.
Up

4.25.7  SMF Initiated SMF-NEF Connection Release procedure  p. 672

When the PDU Session Release is initiated and if a NEF has been selected as anchor of the Control Plane CIoT 5GS Optimisation enabled PDU session which is Unstructured PDU Session Type as described in clause 4.3.4.2, then the SMF initiates a SMF-NEF Connection Release procedure towards the NEF corresponding to the "NEF ID" for that DNN / S-NSSAI Combination.
Reproduction of 3GPP TS 23.502, Fig. 4.25.7-1: SMF Initiated SMF-NEF Connection Release procedure
Figure 4.25.7-1: SMF Initiated SMF-NEF Connection Release procedure
Up
Step 1.
The SMF performs Step 1 of PDU Session Release Procedure as described in clause 4.3.4.2.
Step 2.
If a NEF has been selected as anchor of the Control Plane CIoT 5GS Optimisation enabled PDU session which is Unstructured PDU Session Type as described in clause 4.3.2.2, the SMF initiates the SMF-NEF Connection release for this PDU Session by sending Nnef_SMContext_Delete Request (User Identity, PDU Session ID, S-NSSAI, DNN, Release Cause) message to the NEF.
Step 3.
The NEF deletes the NEF PDU Session Context associated with the User Identity and the PDU session ID. The NEF sends Nnef_SMContext_Delete Response (Cause, [Small Data Control Rate Status], [APN Rate Control Status]) to the SMF confirming release of the SMF-NEF session for the UE. The NEF includes Small Data Rate Control Status if PDU Session used Small Data Rate Control.
Step 4.
Steps 3-15 of PDU Session Release Procedure as described in clause 4.3.4.2.
Up

4.25.8  NEF Initiated SMF-NEF Connection Release procedure  p. 672

NEF initiates a SMF-NEF connection release procedure in the following cases:
  • when a NIDD Authorization Update Request from the UDM indicates that the User is no longer authorized for NIDD, or
  • failure of AF or failure of AF connection, or
  • based on a request from the AF.
Figure 4.25.8-1 illustrates the NEF Initiated SMF-NEF Connection Release procedure based on a request from AF.
Reproduction of 3GPP TS 23.502, Fig. 4.25.8-1: NEF Initiated SMF-NEF Connection Release procedure on the AF request
Figure 4.25.8-1: NEF Initiated SMF-NEF Connection Release procedure on the AF request
Up
Step 1.
AF may indicate that a User's NIDD SMF-NEF connection is no longer needed by invoking Nnef_NIDDConfiguration_Delete Request (TLTRI) toward NEF.
Step 2.
The NEF deletes the NEF PDU session Context associated with the TLTRI and acknowledges the deletion of the NIDD configuration by invoking Nnef_NIDDConfiguration_Delete Response to the AF.
Step 3.
The NEF notifies the deletion of the SM context information by invoking Nnef_SMContext_DeleteNotify Request toward the SMF.
Step 4.
The SMF acknowledges the notification by invoking Nnef_SMContext_DeleteNotify Response to the NEF.
Step 5.
If the PDU session is not longer needed, the SMF performs steps 2-11 of PDU Session Release Procedure (see clause 4.3.4.2).
Figure 4.25.8-2 illustrates the NEF Initiated SMF-NEF Connection Release procedure based on the NIDD Authorization Update.
Reproduction of 3GPP TS 23.502, Fig. 4.25.8-2: NEF Initiated SMF-NEF Connection Release procedure on the NIDD Authorization Update
Figure 4.25.8-2: NEF Initiated SMF-NEF Connection Release procedure on the NIDD Authorization Update
Up
Step 1.
On NIDD Authorization Update by UDM, NEF may determine that it needs to release the corresponding SMF-NEF Connection.
Step 2.
The NEF deletes the corresponding NEF PDU session Context and notifies the deletion of the SM context information by invoking Nnef_SMContext_DeleteNotify Request toward the SMF.
Step 3.
The SMF acknowledges the notification by invoking Nnef_SMContext_DeleteNotify Response to the NEF.
Step 4.
If the PDU session is not longer needed, the SMF performs steps 2-11 of PDU Session Release Procedure (see clause 4.3.4.2).
Up

4.25.9  NEF Anchored Group NIDD via NEF anchored unicast MT data  p. 674

Figure 4.25.9-1 illustrates the procedure by which the AF can send a Group NIDD addressed to External Group Identifier. It is a pre-requisite assumption that the NEF has already resolved the mapping of External Group Identifier to individual SUPIs with the help of UDM during NIDD Configuration procedure as specified in clause 4.25.3. Standalone MT NIDD procedure specified in clause 4.25.5 is re-used by NEF to unicast the MT data to each UE.
Reproduction of 3GPP TS 23.502, Fig. 4.25.9-1: NEF Anchored Group NIDD via NEF anchored unicast data
Figure 4.25.9-1: NEF Anchored Group NIDD via NEF anchored unicast data
Up
Step 1.
If AF has already used the NIDD Configuration procedure of clause 4.25.3 to activate the NIDD service for a group of UEs and has unstructured data to send to the group identified by an External Group Identifier, the AF sends a Nnef_NIDD_Delivery Request (External Group Identifier, TLTRI, unstructured data, Reliable Data Service Configuration) message to the NEF. Reliable Data Service Configuration is an optional parameter that is used to configure the Reliable Data Service. When unstructured data is sent to an External Group Identifier, the AF shall not request acknowledgement in the Reliable Data Service Configuration.
Step 2.
Based on the existing NIDD configuration of the UE Group (see clause 4.25.3), the NEF sends a single Nnef_NIDD_Delivery Response to AF to acknowledge the acceptance of the Group NIDD delivery request in step 1.
Step 3.
The NEF uses the NEF anchored Mobile Terminated Data Transport procedure that is specified in steps 2-16 in clause 4.25.5 to send the same MT NIDD to each UE in the group.
Step 4.
After executing step 3 for all UEs in the group, the NEF sends aggregated response in Nnef_NIDD_GroupDeliveryNotify message. If some target UEs were not reachable due to UE power saving, then the NEF does not buffer the MT NIDD, but it may include indication on the expected reachability of those UEs in its response to AF in this step. If the delivery towards certain UE failed, the NEF may include the cause value.
Up

Up   Top   ToC