name: NEF
full_form: Network Element Function block
context: Figure 5.5.4.4.2.1: Charging for Exposure with bulk subscription 1. NEF registers with the NRF for any newly registered NF along with its NF services. 2. When an NF instantiates, it registers itself along with the supported NF services with the NRF. 3. NRF acknowledges the registration. 4. NRF notifies the NEF with the newly registered NF along with the supported NF services. 5. NEF evaluates the NF and NF services supported against the pre-configured events within NEF. Based on that, NEF subscribes with the corresponding NF either for a single UE, group of UE(s) (e.g. identifying a certain type of UEs such as IoT UEs), any UE. NF acknowledges the subscription with the NEF. 6 - 7. When the event trigger happens, NF notifies the requested information towards NEF. NEF may store the information in the UDR. 8. Application registers with the NEF for a certain event identified by event filters. A. The NEF interacts with charging domain for the Nnef_EventExposure request from Application. 9 -
description: The Network Element Function (NEF) is a network function that registers with the NRF, evaluates NFs and their services, subscribes to events, and interacts with the charging domain for event exposure requests from applications.
explanation: Based on the context provided from 3GPP TS 32.899, section 5.5.4.4.2, NEF is classified as a Network Function due to its role in registering with NRF, evaluating NFs and their services, subscribing to events, and interacting with the charging domain for event exposure requests.
section_title: 5.5.4.4.2Procedure description
biotag_Context: O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,B-Network Function,O,O,O,O,B-Network Function,O,O,O,B-Network Function,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,B-Network Function,O,O,O,O,B-Network Function,O,O,B-Network Function,O,O,O,O,B-Network Function,O,O,O,O,B-Network Function,O,O,B-Network Function,O,O,B-Network Function,O,B-Network Function,O,O,O,O,O,O,O,O,O,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,O,B-Device,O,O,B-Technology,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,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,O,O
biotag_Description: O,B-Network Function,I-Network Function,O,O,O,O,O,O,O,O,O,O,O,O,B-Network,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O