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

Glossary term · Management

NF Deployment instance

Network Function Deployment Instance

Management →

NF Deployment instance is a concrete, running realization created from an NF Deployment template, with its own identity, state, and lifecycle within the 3GPP management system.

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

Description

NF Deployment instance is a Release 20 management concept defined in 3GPP TS 28.531 and TS 28.533. It is defined simply as a particular instance of an NF Deployment. The distinction mirrors the classic template-versus-instance pattern in cloud and orchestration systems: an NF Deployment describes the deployable software and its characteristics, while an NF Deployment instance is a specific, running occurrence of that deployment with its own identity, configuration, and operational state.

In the management architecture, the NF Deployment instance is the object that the management system actually creates, monitors, and controls. When an operator or an automation function requests deployment of a network function, the management services in TS 28.531 instantiate the NF Deployment, producing one or more NF Deployment instances. Each instance is associated with allocated virtualized resources, a configuration, and a lifecycle state (for example, instantiating, running, scaling, or terminating). The instance is the anchor point for management operations such as modification, scaling, healing, and deletion.

The instance concept is essential for supporting multiple simultaneous deployments of the same software. For example, an NF Deployment might be instantiated many times to serve different network slices, different geographical regions, or different capacity tiers. Each of these is a distinct NF Deployment instance, allowing independent lifecycle management, fault isolation, and performance monitoring. This is particularly important in network slicing, where slice-specific instances must be created and torn down without affecting other slices.

Because the instance is a managed object, it carries attributes and associations defined by the information model in TS 28.531 and the architecture in TS 28.533. These include references to the parent NF Deployment, the realized network function(s), the allocated resource instances, and any associated measurement or alarm objects. Management services expose operations to query and modify these attributes, enabling closed-loop automation. For example, a performance measurement crossing a threshold can trigger a scaling operation on a specific NF Deployment instance rather than on the deployment template.

The NF Deployment instance also supports traceability and accountability. Each instance has a unique identity within the management system, so operators can track which software version, configuration, and resource set is running at any given time. This is valuable for troubleshooting, auditing, and compliance. In multi-vendor environments, the instance identity allows coordination between the 3GPP management system and the underlying MANO or cloud platform, which may use its own identifiers for the same running software.

Overall, the NF Deployment instance is the operational workhorse of NF lifecycle management in Release 20. It transforms the abstract NF Deployment into concrete, manageable entities that can be automated, observed, and controlled at scale, which is a prerequisite for the highly dynamic, slice-based, cloud-native networks envisioned for 5G-Advanced and 6G.

Purpose & Motivation

The NF Deployment instance exists to provide a concrete, identifiable object for each running occurrence of deployed NF software. Without it, the management system could only refer to the deployment as an abstract template, making it impossible to independently manage multiple simultaneous deployments of the same software. This matters because modern networks routinely run many copies of the same NF for different slices, regions, or capacity needs, and each copy must be scaled, healed, and monitored separately.

The instance concept also enables precise association of management data. Alarms, performance measurements, configuration changes, and lifecycle operations must be tied to a specific running entity, not to a generic deployment description. By defining the instance as a first-class managed object, 3GPP ensures that these associations are standardized and interoperable across vendors and management systems.

Historically, this follows the well-established pattern in cloud orchestration where templates are instantiated into running resources. 3GPP adopted this pattern in Release 20 to align its management framework with cloud-native practices, addressing the limitations of earlier models that treated NFs as monolithic, statically provisioned nodes. The NF Deployment instance thus provides the granularity and traceability needed for automated, slice-aware operations.

What changed in its specifications

The latest release-to-release comparison of specifications that define NF Deployment instance. 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 in TS 28.531 and TS 28.533 as a particular instance of an NF Deployment, establishing the template-versus-instance distinction needed for managing multiple concurrent deployments of virtualized NF software.

Defining Specifications

3GPP specifications that define or reference NF Deployment instance, 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