Section: 4.25.8 NEF Initiated SMF-NEF Connection Release procedure
Content: 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. Figure 4.25.8-1: NEF Initiated SMF-NEF Connection Release procedure on the AF request 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. 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. 3. The NEF notifies the deletion of the SM context information by invoking Nnef_SMContext_DeleteNotify Request toward the SMF. 4. The SMF acknowledges the notification by invoking Nnef_SMContext_DeleteNotify Response to the NEF. 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. Figure 4.25.8-2: NEF Initiated SMF-NEF Connection Release procedure on the NIDD Authorization Update 1. On NIDD Authorization Update by UDM, NEF may determine that it needs to release the corresponding SMF-NEF Connection. 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. 3. The SMF acknowledges the notification by invoking Nnef_SMContext_DeleteNotify Response to the NEF. 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).