NRF

Network Resource Fulfilment

Management →
Introduced in Rel-15 Also in: Services

NRF is the 3GPP management function responsible for the automated provisioning, activation, and configuration of network resources and services within the MANO framework.

Category
Management
Introduced
Rel-15
Where
Core Network › 5G Core
Also touches
1 segments
Specifications
42 specs
NRF Description Purpose Related Classification Detected Changes Specifications

Description

Network Resource Fulfilment (NRF) is a critical management function within the 3GPP Management System, specifically defined in the Management and Orchestration (MANO) architecture for 5G networks. It operates within the Network Management (NM) and Element Management (EM) layers, interacting with the Network Functions (NFs) and physical/virtual resources. The NRF function is responsible for executing the workflows necessary to realize a service or network slice instance based on a provisioning request. This involves translating high-level service requirements (e.g., from a Communication Service Management Function - CSMF) into detailed, actionable configuration commands for the underlying network resources, including compute, storage, networking, and virtualized network functions (VNFs) or containerized network functions (CNFs).

Architecturally, NRF works in concert with other management functions like the Network Slice Subnet Management Function (NSSMF) and the Network Function Management Function (NFMF). When a network slice instance needs to be created, the NSSMF decomposes the slice requirements and invokes the NRF to fulfil the resources for each constituent subnet. The NRF interacts with resource-specific managers (e.g., Virtualized Infrastructure Manager - VIM, WAN Infrastructure Manager - WIM) and NF managers to allocate resources, instantiate software, configure parameters, and establish connectivity. It follows a defined fulfilment workflow that may include validation, reservation, activation, testing, and activation phases. The process is heavily reliant on descriptors and templates, such as Network Service Descriptors (NSD) and Virtual Network Function Descriptors (VNFD), which define the resource requirements and lifecycle scripts.

How it works involves a sequence of orchestrated steps. Upon receiving a fulfilment request, the NRF first performs admission control and checks resource availability against an inventory. It then triggers the resource managers to allocate the necessary virtual machines, containers, storage volumes, and network links. For network functions, it instructs the NFMF to instantiate the VNF/CNF using the appropriate package from a catalog. The NRF coordinates the configuration of these resources, ensuring that IP addresses, routing policies, security groups, and function-specific parameters are set according to the service blueprint. It monitors the fulfilment process, handling any errors through rollback procedures. Once all resources are provisioned and configured, the NRF updates the network inventory and notifies the requesting management function that the service or slice is ready for operation. This automation is key to supporting dynamic, on-demand network slicing and service deployment.

Purpose & Motivation

Network Resource Fulfilment was introduced to address the massive operational complexity of modern telecom networks, especially with the advent of 5G, network slicing, and cloud-native principles. Traditional network provisioning was largely manual, CLI-driven, and slow, making it impossible to meet the demands for rapid service innovation, elasticity, and customized slices for vertical industries. NRF automates this provisioning lifecycle, solving the problem of scaling network operations in a software-defined and virtualized environment.

Historically, each network element was configured independently. The move to Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) created a disaggregated, flexible infrastructure but also a management nightmare. The NRF, as part of the 3GPP's aligned management framework (building upon ETSI NFV MANO concepts), provides a standardized, vendor-agnostic interface and process for automating the end-to-end fulfilment of composite network services. It addresses the limitations of siloed, element-specific management systems that could not coordinate across compute, network, and application layers.

The creation of NRF was motivated by the business need for zero-touch service and slice management. Operators require the ability to deploy a new slice for an enterprise customer in minutes, not months. NRF enables this by providing the automated workflow engine that translates a customer-facing service order into technical reality. It is fundamental to achieving the 5G vision of network-as-a-service, allowing operators to efficiently utilize their pooled resources and rapidly respond to market opportunities while reducing operational expenditure and human error.

Architecture

In the Network Map

Classification

Part ofMANO
Specific typesSI

Release Timeline

Detected Changes Across Releases

from 3GPP Change Requests

Specific changes extracted from the „Change history“ tables of 3GPP specifications (89 CRs across 5 releases). Complements the general historical overview above with the evidence-based evolution of this function.

Rel-15 21 changes

In Release 15, the NRF (Network Repository Function) was newly introduced as a central repository for Network Function (NF) service registration and discovery, enabling NFs like the AMF and SMF to query the NRF to select appropriate peer NFs based on parameters like S-NSSAI and DNN. It also introduced support for hierarchical NRF deployments and roaming architectures, including the N27 reference point between NRFs in visited and home networks, to facilitate NF discovery across PLMN boundaries. Furthermore, the release specified capabilities for NF profile management, subscription handling, and notifications, allowing NFs to register their supported services and features, such as a UPF registering its NAT exposure capability.

+ 15 more changes

Rel-16 26 changes

In Release 16, the NRF's role was significantly expanded to support new discovery procedures and enhanced service registration. Key additions included enabling the discovery of functions like the P-CSCF, HSS, NSSF, and UCMF via the NRF, and introducing support for AF Available Data Registration. The release also defined new interactions, such as the N27 reference point for roaming between NRFs and mechanisms for NRF bootstrapping and intermediate forwarding.

  • NRF based P-CSCF discovery TS 23.501CR1035
  • Update NRF descriptions to support AF Available Data Registration as described in TS23.288 TS 23.501CR1406
  • HSS discovery via NRF TS 23.501CR1438
  • Update NRF descriptions to support AF Available Data Registration as described in TS23.288 TS 29.510CR0212
  • NRF Bootstrapping TS 29.510CR0251
  • UCMF Registration in NRF TS 29.510CR0253

+ 20 more changes

Rel-17 21 changes

In Release 17, the NRF saw enhancements for improved network function discovery and security, including support for NRF Sets and the Enhanced NF Discovery feature which can return altered priorities. It also introduced new capabilities for authorization, such as discovering whether OAuth2 is required for accessing NRF services and implementing resource-based authorization on NRF APIs. Furthermore, the NRF's role was expanded to support new functions like the NWDAF for analytics aggregation and the NSACF as a data source, and to accommodate specific network deployments like SNPNs and multicast/broadcast services (MBSF/MB-STF).

  • NRF supported features in Bootstrapping response TS 29.510CR0431
  • NWDAF aggregation capability registration in the NRF TS 29.510CR0505
  • NRF Content Encoding Information TS 29.510CR0518
  • Discovering whether Oauth2 authorization is required for accessing NRF services TS 29.510CR0581
  • SNPN impacts on NRF - DCS/CH identification TS 29.510CR0630
  • Returning NRF altered priorities when using the Enhanced NF Discovery feature TS 29.510CR0638

+ 15 more changes

Rel-18 14 changes

In Release 18, the NRF was enhanced with new registration and discovery services for Data Collection and Storage Function (DCSF), Model Repository Function (MRF), and Data Collection Management Function (DCMF). The release also introduced explicit support for Canary Testing via the NRF, added a new OAuth2 scope for its Management API, and defined procedures for Federated Learning and enhanced NWDAF discovery supporting ML model provisioning. Furthermore, it included updates for robustness interfaces and protocols, handling of NRF subscriptions in SNPN scenarios, and completed the LMF NF profile for registration.

  • Enhancement of NRF services to support DCSF registration and discovery TS 29.510CR0828
  • NRF service enhancement to support MRF registration and discovery TS 29.510CR0837
  • NRF service enhancement to support DCMF registration and discovery TS 29.510CR0844
  • Support for Canary Testing via NRF TS 29.510CR0852
  • Additional OAuth2 scope for the NRF Management API TS 29.510CR0863
  • Clarify NRF behavior upon receiving invalid client information in discovery request TS 29.510CR0996

+ 8 more changes

Rel-19 7 changes

In Release 19, the NRF (Network Repository Function) was enhanced to support the registration of an IMS Application Server (AS) and to indicate UPF capabilities, such as NAT information exposure functionality, within its NF profiles. Additionally, the release introduced new NRF discovery references and included corrections and expansions for services like Key Retrieval and the discovery of missing CHF instances.

  • Indicate the UPF capabilities in NRF TS 29.510CR1061
  • Support of IMS AS registration to NRF TS 29.510CR1103
  • Corrections to Key Retrieval from NRF TS 29.510CR1246
  • Rel-19 CR 32.255 Addition of NRF discovery reference TS 32.255CR0549
  • Rel-19 CR 32.256 Addition of NRF discovery reference TS 32.256CR0039
  • CR for 23.501 AIML_CN NRF services exposure TS 23.501CR6291

+ 1 more changes

Explore further

Broader topics and technologies where NRF plays a role.

Defining Specifications

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

SpecificationTitleRelease
TS 23.501 vk00 5G System Architecture Stage 2 Rel-20
TS 23.540 vj20 5G Service Based SMS Stage 2 Rel-19
TS 26.532 vj00 5G Data Collection and Reporting API Specification Rel-19
TS 26.567 vj00 IMS-based Split Rendering Rel-19
TS 26.804 vj10 5G Media Streaming Extensions Study Rel-19
TS 26.891 vg00 Media Distribution Services in 5G System Rel-16
TR 26.919 vj00 Study on 5G Conversational Media Handling Rel-19
TS 28.802 vf00 Management Study for 5G Network Architecture Rel-15
TR 28.840 vi10 Technical Report Rel-18
TS 29.503 vj50 UDM Service Based Interface Stage 3 Rel-19
TS 29.507 vj40 5G Access & Mobility Policy Control Service Rel-19
TS 29.508 vj40 5G Session Management Event Exposure Service Rel-19
TS 29.510 vj50 NRF Service Based Interface Protocol Rel-19
TS 29.512 vj40 5G Session Management Policy Control Service Rel-19
TS 29.513 vj40 5G PCC Signalling Flows & QoS Mapping Rel-19
TS 29.514 vj40 5G System; Policy Authorization Service; Stage 3 Rel-19
TS 29.515 vj50 Ngmlc Service Based Interface Protocol Rel-19
TS 29.518 vj50 AMF Service Based Interface Protocol Rel-19
TS 29.519 vj40 UDR Usage for Policy & Exposure Data Rel-19
TS 29.520 vj40 5G Network Data Analytics Services Stage 3 Rel-19
TS 29.521 vj40 5G Binding Support Management Service Stage 3 Rel-19
TS 29.523 vj20 5G Policy Control Event Exposure Service Rel-19
TS 29.525 vj40 5G UE Policy Control Service Stage 3 Rel-19
TS 29.551 vj30 5G PFD Management Service Stage 3 Rel-19
TS 29.552 vj40 5G Network Data Analytics Signalling Flows Rel-19
TS 29.554 vj10 5G Background Data Transfer Policy Control Service Rel-19
TS 29.562 vj40 HSS Services for IMS & GBA Interworking Rel-19
TS 29.574 vj40 5G Data Collection Coordination Services Stage 3 Rel-19
TS 29.575 vj40 5G Analytics Data Repository Services Stage 3 Rel-19
TS 29.576 vj40 5G Messaging Framework Adaptor Services Stage 3 Rel-19
TS 29.594 vj20 5G Spending Limit Control Service Stage 3 Rel-19
TR 29.829 vh10 SMS Service-Based Interfaces for 5G Core Rel-17
TS 32.255 vk10 Telecom Management; Charging for 5G Data Connectivity Rel-20
TS 32.256 vj40 5G Connection & Mobility Charging Spec Rel-19
TS 32.828 va00 Study on 3GPP-TMF NRM/SID Alignment Rel-10
TS 32.899 vf10 5G Charging Architecture Study Rel-15
TS 33.117 vk00 Catalogue of General Security Assurance Requirements Rel-20
TS 33.127 vj50 Lawful Interception Architecture and Functions Rel-19
TS 33.518 vk00 5G Security Assurance Specification (SCAS) for NRF Rel-20
TR 33.739 vi10 Study on security enhancement of support for Rel-18
TS 33.776 vj00 Study of ACME for 5G SBA Rel-19
TS 33.794 vj10 Study on Zero Trust Security Enablers for 5G Rel-19
Patrick Zandl

About the author: Patrick Zandl (b. 1974)

Telecommunications specialist, technology journalist (founder of the Mobil server), and developer who has been running since 2025 — the largest Czech-language resource on AI-assisted programming. Formerly Chief Wizard Architect at Prusa3D and head of development for Turris at CZ.NIC; currently a consultant and instructor on AI implementation in companies.