Menu
Latest
12 meetings · Prague, Jeju · 12–16 Oct
Reports
RAN1#126-bis · SA2#177

Glossary term · Core Network

NEF

Network Exposure Function

Core Network →

NEF is the 5G core network function that securely exposes network capabilities and events to authorized third parties, acting as a controlled gateway between external APIs and internal 3GPP protocols.

Introduced
Rel-15
Where
Core Network › 5G Core
Specifications
87 specs
Also in
Services
NEF Description Purpose What changed Family Neighbours Detected Changes Specifications

Description

The Network Exposure Function (NEF) is a central component within the 5G Service-Based Architecture (SBA) of the 5G Core (5GC). It serves as the standardized, secure, and policy-controlled entry point for external Application Functions (AFs) to interact with the 3GPP network. Architecturally, the NEF is a network function (NF) that communicates with other core NFs (like the Policy Control Function (PCF), Unified Data Management (UDM), and Network Repository Function (NRF)) via standardized service-based interfaces (e.g., Nnef). Its primary role is to mediate between external, non-3GPP application layer protocols (typically RESTful APIs based on HTTP/JSON) and the internal 3GPP-specific service-based interfaces (e.g., using JSON over HTTP/2). This involves API translation, protocol conversion, and ensuring that external requests are properly authorized, authenticated, and compliant with network policies.

Functionally, the NEF provides two main capabilities: exposure and storage. For exposure, it offers a northbound API (often defined in 3GPP TS 29.522) that allows AFs to request network services, such as influencing traffic routing (e.g., via the Network Slice Selection Assistance Information (NSSAI)), subscribing to network events (like UE location changes, connectivity status, or communication failure), and accessing network analytics. The NEF validates these requests against subscriber profiles and network policies enforced by the PCF. For storage, the NEF can securely store structured data received from an AF as "application data" in the Unified Data Repository (UDR) for later use by other network functions, acting as a structured data gateway.

Internally, the NEF works by receiving an API request from an AF, authenticating and authorizing the AF (often in conjunction with the Network Repository Function (NRF) and Security Edge Protection Proxy (SEPP)), and then translating that request into the appropriate service-based interface operation towards the relevant internal NF. For example, an AF request to monitor a UE's reachability status would be translated by the NEF into a subscription request to the Access and Mobility Management Function (AMF). The NEF then acts as a proxy, forwarding relevant notifications from the AMF back to the AF. This abstraction shields the internal 3GPP network from direct external access, providing a layer of security, stability, and control while enabling rich service capabilities.

Purpose & Motivation

The NEF was created to address the fundamental challenge of "walled garden" networks in previous generations (2G/3G/4G), where network capabilities were largely inaccessible to external entities, stifling innovation and service differentiation. In 4G EPC, limited exposure was provided via the Service Capability Exposure Function (SCEF), but it was often complex and not fully standardized for all capabilities. The 5G vision of enabling vertical industries (e.g., automotive, IoT, manufacturing) and new business models required a more robust, scalable, and programmable exposure framework.

Its primary purpose is to solve the problem of secure and controlled network openness. It allows Mobile Network Operators (MNOs) to monetize their network assets by offering capabilities like QoS control, location services, and network status information to enterprise partners and third-party developers through well-defined APIs. This enables the creation of tailored services such as enhanced mobile broadband with guaranteed bitrates for video providers, low-latency communication for cloud gaming, or reliable connectivity slices for industrial IoT. Furthermore, the NEF addresses security and privacy concerns by centralizing all external interactions, ensuring that exposure is governed by operator-defined policies, user consent (where applicable), and regulatory requirements, preventing unauthorized access to sensitive network data and control functions.

What changed in its specifications

The latest release-to-release comparison of specifications that define NEF. Each summary describes the whole specification, not only this term.

TR 21.905Rel-17 → Rel-18

Rel-18 brings only minor changes to TS 21.905: 0 clauses changed, with no change attributed to a release feature.

Full comparison in TR 21.905 →
TS 23.222Rel-18 → Rel-19

Rel-19 adds CAPIF Phase 3 procedures for unpublishing service APIs between interconnected core functions, revoking API invoker and resource owner authorization, open discovery of service APIs, and UE-hosted API invoker access to resources owned by other UEs.

Full comparison in TS 23.222 →

Architecture

Where it sits in the network

Technology family

Network exposure and analytics · Core Network

  1. Rel-11 SCS/AS
  2. Rel-13 IWK-SCEF, SCEF
  3. Rel-15 CAPIF, NEF, NWDAF
  4. Rel-16 SCEF+NEF
  5. Rel-17 ADRF, AnLF, DCCF, L-NEF, MDAF, MFAF, MTLF
  6. Rel-18 RE-NWDAF
  • NEF counterpart in another generation: SCEF
    “In order to support interworking with EPC, the NEF is integrated with SCEF as a combined SCEF+NEF node for network exposure as defined in clause 5.17.5 of TS 23.501 [2].” TS 23.502
  • NEF used together with CAPIF
    “When an NEF is used for external exposure, the CAPIF may be supported. When CAPIF is supported, an NEF that is used for external exposure supports the CAPIF API provider domain functions.” TS 23.501
  • NEF extended by L-NEF
    “Redirecting the AF to a more suitable NEF/L-NEF e.g. when serving an AF request for local information exposure and detecting there is a more appropriate NEF instance to serve the AF's request.” TS 23.501
  • NEF extended by SCEF+NEF
    “In order to support interworking with EPC, the NEF is integrated with SCEF as a combined SCEF+NEF node for network exposure as defined in clause 5.17.5 of TS 23.501 [2].” TS 23.502

Members and relations were proposed independently by several models and kept only where at least two agree; quotes are verified verbatim against the specifications. Release = first approved version of the defining specification.

Release Timeline

Detected Changes Across Releases

verified against 3GPP sources

Documented changes in 6 releases, each verified against the text of 3GPP specifications or approved change requests and shown with the exact wording. The release timeline above shows the same releases. A release without an entry has no documented change for this term.

Rel-15 introduced

The NEF is specified for the first time in Rel-15, with its architecture, exposure and translation functions, PFD function, UDR storage, and the Northbound API towards the AF.

  • “The NEF shall securely expose network capabilities and events provided by 3GPP NFs to AF.” TS 29.522 v15.9.0
  • “The NEF shall be able to translate the information received from the AF to the one sent to internal 3GPP NFs, and vice versa.” TS 29.522 v15.9.0
  • “NEF stores/retrieves information as structured data using a standardized interface (Nudr) to the Unified Data Repository (UDR).” TS 23.501 v15.13.0
Rel-16 specification text

In Rel-16 the NEF gained new roles and procedures: Nnef_EventExposure service, SCEF+NEF combined node, NWDAF analytics exposure, location exposure via GMLC/AMF, and SMS delivery as MTC-IWF.

  • “the NEF shall create a new "Individual Event Exposure Subscription" resource, store the subscription and send an HTTP "201 Created" response” TS 29.591 v16.7.0
  • “An NEF may support exposure of NWDAF analytics as specified in TS 23.288 [86].” TS 23.501 v16.20.0
  • “The NEF supports interactions towards the CHF, as defined in TS 32.254 [123].” TS 23.501 v16.20.0
Rel-17 specification text

In Rel-17 the NEF gained new exposure capabilities, including time synchronization exposure, EAS Deployment information, AF-specific UE ID, NSACF event exposure, and local NEF discovery and selection.

  • “The NEF may support the time synchronization exposure function to the AF.” TS 29.522 v17.18.0
  • “The NEF may provide means for the AF to provide the EAS Deployment information.” TS 29.522 v17.18.0
  • “An NEF may support exposure of event based notifications and reports for NSACF as specified in clause 5.15.11.” TS 23.501 v17.15.0
Rel-18 1 CR

NEF gained new Rel-18 functionality, including member UE selection assistance for AI/ML, NSACF-based network slice status exposure, HR-SBO determination and traffic influence data subscription handling.

  • “The Member UE selection assistance functionality shall be hosted by NEF and the features of the Member UE selection assistance functionality hosted by the NEF include” TS 23.501 v18.12.0
  • “the NEF shall then further interact with the concerned NSACF(s) to create or update the associated subscription(s) to notifications” TS 29.522 v18.13.0
  • NEF capability for the new AIML service TS 23.501CR4408
Rel-19 1 CR

NEF gained new roles and procedures in Rel-19, including interaction with the EIF for energy exposure, MSISDN verification via Nnef_UEId, and new VFL training event subscription handling.

  • “the NEF shall then further interact with the EIF to create or update the associated subscription(s) to notifications by invoking the Nneif_EventExposure_Subscribe service operation” TS 29.522 v19.7.0
  • “The NEF may also provide MSISDN verification (via Nnef_UEId service) to an authenticated and authorized AF” TS 23.501 v19.9.0
  • KI#1.2: Adding a new NEF service operations for USS TS 23.256CR0128
Rel-20 1 CR

NEF behaviour was extended in Rel-20, including energy-saving functionality, application ranking reporting, QoS monitoring unavailability cause handling, and new interactions with the EIF, PCF and UDM.

  • “When the NEF receives the notification from the PCF about the indication that the energy saving operations are applied” TS 29.522 v20.1.0
  • “the NEF shall indicate in an HTTP "403 Forbidden" response message the cause for the rejection” TS 29.522 v20.1.0
  • NEF functionality update to support network energy saving TS 23.501CR6587

Defining Specifications

3GPP specifications that define or reference NEF, with the latest known release. Sourced from the 3GPP document catalog — see methodology.

SpecificationTitleRelease
TR 21.905 vj20 3GPP Terminology and Definitions Rel-19 read
TS 23.222 vk10 Common API Framework (CAPIF) Rel-20 read
TS 23.434 vk10 Service Enabler Architecture Layer (SEAL) for Verticals Rel-20 read
TS 23.435 vk00 Network Slice Capability Enablement (NSCE) Architecture Rel-20 read
TS 23.482 vk30 AI/ML Enablement for Verticals Rel-20 read
TS 23.501 vk30 5G System Architecture Rel-20 read
TS 23.527 vk00 5G Restoration Procedures for N4 Interface Rel-20 read
TS 23.558 vk30 Enabling Edge Applications Rel-20 read
TS 23.700 vk10 AI/ML Application Layer Support Phase 2 Rel-20 read
TR 23.745 vh00 Study on App Layer Support for Factories of the Future in 5G Rel-17 read
TR 23.758 vh00 Study on Edge Application Architecture Rel-17 read
TR 23.764 vh10 Study on V2X Application Layer Enhancements Rel-17 read
TS 24.229 vk10 IMS SIP/SDP Call Control Protocol Rel-20 read
TS 24.542 vj00 SEAL Notification Management Protocol Rel-19 read
TS 26.501 vk00 5G Media Streaming Architecture Rel-20 read
TS 26.502 vj60 5G Multicast-Broadcast User Services Rel-19 read
TS 26.510 vj20 5G Media Streaming and Real-Time Communication APIs Rel-19 read
TS 26.512 vj30 5G Media Streaming Protocols and APIs Rel-19 read
TS 26.517 vj30 5G MBS User Service Protocols Rel-19 read
TS 26.531 vj00 Data Collection & Reporting Architecture for 5G Rel-19 read
TS 26.532 vj10 Data Collection and Reporting API Specification Rel-19 read
TS 26.567 vj20 IMS-Based Split Rendering Rel-19 read
TS 26.802 vk00 5G Media Streaming Multicast Enhancements Rel-20 read
TR 26.803 vh00 5G Media Streaming Extensions for Edge Processing Rel-17 read
TS 26.804 vk10 5G Media Delivery Architecture Extensions Rel-20 read
TR 26.806 vi00 Technical Report on Smartly Tethering AR Glasses Rel-18 read
TS 26.891 vg00 Media Distribution Services in 5G System Rel-16 read
TR 26.919 vj00 Study on 5G Conversational Media Handling Rel-19 read
TR 26.928 vj00 Study on eXtended Reality (XR) in 5G Rel-19 read
TS 26.942 vk00 Sustainable Media Metrics and Architectural Impacts for 5G Rel-20 read
TS 28.802 vf00 Management Study for 5G Network Architecture Rel-15 read
TR 28.816 vh00 Charging for 5G Cellular IoT Rel-17 read
TR 28.833 vi01 Technical Report on 5G LAN-type Service Management Rel-18 read
TR 28.843 vi10 Technical Report on Charging Aspects for Vertical Scenarios Rel-18 read
TS 28.849 vj10 CAPIF Phase2 Charging Study Rel-19 read
TS 28.851 vj10 Charging for Next Gen Real Time Communication Phase 2 Rel-19 read
TS 28.879 vj10 OAM for Service Management Exposure Study Rel-19 read
TS 29.122 vk10 T8 SCEF Service Exposure APIs Rel-20 read
TS 29.175 vk10 Nimsas Service Based Interface for IMS AS Rel-20 read
TS 29.255 vk00 UAS-specific NAF Service Based Interface Rel-20 read
TS 29.503 vk10 UDM Service Based Interface Rel-20 read
TS 29.504 vk10 Nudr Unified Data Repository Services Rel-20 read
TS 29.508 vk10 Session Management Event Exposure Service Rel-20 read
TS 29.512 vk10 Session Management Policy Control Service Stage 3 Rel-20 read
TS 29.513 vk10 5G PCC Signalling Flows Rel-20 read
TS 29.514 vk10 Policy Authorization Service Rel-20 read
TS 29.515 vk10 Ngmlc Location Services API Rel-20 read
TS 29.517 vk10 AF Event Exposure Service Rel-20 read
TS 29.518 vk10 AMF Service Based Interface Rel-20 read
TS 29.519 vk10 5G UDR Policy and Application Data Services Rel-20 read
TS 29.520 vk10 5G NWDAF Services Rel-20 read
TS 29.521 vk10 Binding Support Management Service Rel-20 read
TS 29.522 vk10 NEF Northbound Interface Rel-20 read
TS 29.523 vk10 Policy Control Event Exposure Service Rel-20 read
TS 29.530 vk10 5G AF AI/ML Services Rel-20 read
TS 29.532 vk00 Nmbsmf Service Based Interface Specification Rel-20 read
TS 29.534 vk00 5G Access and Mobility Policy Authorization Rel-20 read
TS 29.535 vk10 AAnF Service Based Interface Rel-20 read
TS 29.536 vk10 Nnsacf Network Slice Admission Control Rel-20 read
TS 29.541 vk00 NEF South-Bound Interfaces for NIDD and SMS Rel-20 read
TS 29.542 vk00 Nsmf NIDD Service API (TS 29.542) Rel-20 read
TS 29.543 vk10 Data Transfer Policy Control Services Rel-20 read
TS 29.551 vk00 3GPP TS 29551 vk00: PFD Management Service Specification Rel-20 read
TS 29.552 vk10 5G Network Data Analytics Procedures Rel-20 read
TS 29.554 vk10 BDT Policy Control Service Rel-20 read
TS 29.558 vk00 Edge Application Enablement APIs Rel-20 read
TS 29.562 vk10 HSS Nhss Services for IMS and GBA Rel-20 read
TS 29.564 vk10 Nupf Service Based Interface Rel-20 read
TS 29.574 vk10 DCCF Service Based Interface Rel-20 read
TS 29.575 vk10 ADRF Service Based Interface Rel-20 read
TS 29.576 vk10 MFAF Service Based Interface Rel-20 read
TS 29.581 vk00 Nmbstf Service Based Interface Stage 3 Rel-20 read
TS 29.591 vk10 NEF Southbound Services Rel-20 read
TS 29.675 vj20 Nucmf Service Based Interface Protocol Rel-19 read
TS 29.889 vj10 Study on UPF data collection for AI/ML Rel-19 read
TS 29.890 vg00 CT3 5G System Technical Report Rel-16 read
TS 32.254 vk00 3GPP TS 32.254: Charging for Northbound APIs Rel-20 read
TS 32.255 vk30 5G Data Connectivity Converged Charging Rel-20 read
TS 32.819 v800 Element Management Layer OS Functions Rel-8 read
TS 32.899 vf10 5G Charging Architecture Study Rel-15 read
TS 33.127 vj80 Lawful Interception Architecture Rel-19 read
TS 33.519 vk10 NEF Security Assurance Requirements and Tests Rel-20 read
TS 33.535 vj00 5G AKMA: Authentication and Key Management for Apps Rel-19 read
TR 33.739 vi10 Study on security enhancement of support for Rel-18 read
TS 33.749 vj00 Study on security aspects of edge computing enhancement Rel-19 read
TS 33.835 vg10 Study on authentication and key management for apps Rel-16 read
TR 33.882 vi01 Technical Report on 5G Security for Personal IoT Networks Rel-18 read