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

Glossary term · Management

NF Deployment

Network Function Deployment

Management →

NF Deployment is a software deployment realizing part or all functionality of one or more virtualized 3GPP network functions, and the management abstraction linking NF software to the virtualized infrastructure hosting it.

Introduced
Rel-20
Where
Management
Specifications
2 specs
NF Deployment Description Purpose What changed Neighbours Specifications

Description

NF Deployment is a management-plane concept introduced in 3GPP Release 20 within the SA5 management and orchestration specifications (TS 28.531 and TS 28.533). It represents the software deployment used to realize a part of, or the full function of, one or multiple 3GPP network functions that are virtualized. In other words, it is the deployable unit of NF software that is instantiated on top of a virtualized infrastructure, and it forms the bridge between the abstract network function (as defined in the service-based architecture) and the concrete virtualized resources (VMs, containers, and their associated networking and storage) that execute it.

Architecturally, the NF Deployment sits within the management domain, typically managed by the Management and Orchestration (MANO) functions and the 3GPP management system. TS 28.531 defines the provisioning management services, including the lifecycle management of NF deployments, while TS 28.533 defines the management and orchestration architecture that places these deployments in context. An NF Deployment can realize a portion of an NF (for example, a single microservice or a scaling unit) or the complete NF, and a single deployment may realize functionality for multiple NFs. This flexibility reflects the trend toward cloud-native, disaggregated network functions where the mapping between software components and logical NFs is not necessarily one-to-one.

Operationally, an NF Deployment is created, modified, scaled, healed, and terminated through management operations. Its lifecycle is tied to the NF Deployment instance, which is the particular instantiation of the deployment. Management services expose operations to create an NF Deployment, query its status, update its attributes, and delete it. Because the deployment is virtualized, its resource requirements (compute, storage, network) are described declaratively, and the orchestration layer maps these onto the underlying virtualized infrastructure. This enables automated scaling and placement decisions driven by policy and performance measurements.

The concept matters because 5G and beyond networks are increasingly built from virtualized and cloud-native components. Traditional management models that treated an NF as a monolithic entity tied to dedicated hardware cannot express the granularity needed for microservice-based implementations, multi-vendor deployments, and dynamic scaling. NF Deployment provides the necessary abstraction to manage software independently from the logical NF it realizes, supporting scenarios where one NF is spread across multiple deployments or where one deployment serves multiple NFs.

In the broader network lifecycle, NF Deployment integrates with NF lifecycle management, network slicing, and closed-loop automation. It allows operators to describe intent (for example, deploy this NF with these capacity and latency requirements) and let the management system realize it through deployments. It also supports fault management and performance management by providing a concrete object against which alarms and measurements can be associated. As Release 20 work on management and orchestration matures, NF Deployment is expected to be a foundational object for intent-based, fully automated network operations.

Purpose & Motivation

NF Deployment exists to solve the mismatch between logical network functions and their virtualized software realizations. In earlier generations, a network function was effectively synonymous with a physical node, and management could treat it as a single manageable entity. With virtualization and cloud-native design, an NF may be composed of many software components, may share deployments with other NFs, and may be scaled or relocated dynamically. Without an explicit management object representing the deployment, operators and orchestration systems would have no standardized way to describe, instantiate, and manage these software units.

The concept also addresses multi-vendor and disaggregated deployments. When different vendors supply different parts of an NF, or when a single NF is realized by multiple deployments, a standardized deployment abstraction allows the management system to coordinate lifecycle operations across vendors. It supports the declarative description of resource and configuration requirements, enabling automation rather than manual, node-centric provisioning.

Finally, NF Deployment was motivated by the need for consistent lifecycle management in the SA5 management framework. By defining the deployment as a first-class object in TS 28.531 and TS 28.533, 3GPP provides a common vocabulary and set of services that can be used across network domains, supporting network slicing, closed-loop assurance, and intent-driven operations.

What changed in its specifications

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

TS 28.531Rel-18 → Rel-19

Rel-19 adds management of IAB nodes to TS 28.531. The new clauses cover IAB-node configuration, location information, configuration via notifications, and a procedure with a sequence diagram.

Full comparison in TS 28.531 →
TS 28.533Rel-18 → Rel-19

Rel-19 adds Annex A.11, an illustrative architecture reference model in which management functions produce and/or consume Management Services. It also defines internal and external MnS consumers by PLMN trust domain.

Full comparison in TS 28.533 →

Evolution Across Releases

An overview written from the defining specifications, not a verified change history. For the exact text, open the specifications listed below.

Rel-20 Initial

Introduced as a management concept in TS 28.531 and TS 28.533, defined as the software deployment used to realize a part of, or the full function of, one or multiple virtualized 3GPP network functions. This initial definition established the abstraction needed for cloud-native NF lifecycle management.

Defining Specifications

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

SpecificationTitleRelease
TS 28.531 vk10 5G Network Slice Provisioning Management Rel-20 read
TS 28.533 vk10 5G Management Architecture Framework Rel-20 read