name: NEF
full_form: Network Exposure Function
context: The IRI-POI in the NEF shall generate an xIRI containing an NEFPDUSessionRelease record when the IRI-POI present in the NEF detects that an unstructured PDU session using NEF related to the target UE needs to be released. The IRI-POI present in the NEF shall generate the xIRI for the following events: - NEF notifies the SMF that the SMF-NEF Connection for NIDD via NEF is no longer valid using Nnef_SMContext_DeleteNotify service operation when NEF receives a notification from the UDM that the NIDD authorization has ended. NEF releases the SM Context for NIDD on NEF as described in TS 29.541 [57] clause 5.2.2.4. This corresponds to NEF Initiated SMF-NEF Connection Release procedure. - NEF returns Nnef_SMContext_Delete Response towards SMF confirming release of the SMF-NEF session for the target UE. In this scenario, SMF releases the SM Context for NIDD on NEF as specified in TS 29.541 [57] clause 5.2.2.3). Table 7.7.2-3: NEFPDUSessionRelease record
description: The Network Exposure Function (NEF) is a network function that provides a means for the UE and the 5G core network to interact with each other, enabling the exposure of capabilities and events. It plays a crucial role in managing PDU sessions, handling SMF-NEF connections, and notifying the UDM about NIDD authorization.
explanation: The context explicitly mentions NEF as an entity that interacts with other network functions like SMF and UDM, performs specific operations such as generating xIRI containing NEFPDUSessionRelease records, and participates in procedures like NEF Initiated SMF-NEF Connection Release. This behavior aligns with the characteristics of a Network Function.
section_title: 7.7.2.1.4	PDU session release
biotag_Context: O,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,B-Connection,O,O,B-Network Function,O,O,O,O,B-Device,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,B-Network Function,O,O,O,O,O,B-Procedure,O,B-Network Function,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,B-Network Function,O,O,B-Procedure,O,O,O,B-Network Function,O,O,B-Service,O,O,B-Procedure,O,B-Network Function,O,O,O,B-Specification,O,O,O,O,O,O,O,B-Network Function,O,O,B-Miscellaneous,I-Miscellaneous,O,O,B-Network Function,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,B-Service,O,O,B-Procedure,O,B-Network Function,O,O,O,B-Specification,O,O,O,O,O,O,O,O
biotag_Description: O,B-Network Function,I-Network Function,I-Network Function,O,O,O,O,O,O,O,O,O,O,O,B-Device,O,O,B-Technology,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Connection,O,O,O,O,O,O,O,B-Network Function,O,B-Procedure,O