Description
Network Control Mode (NC) is a fundamental operational concept within 3GPP's management framework, particularly central to Self-Organizing Network (SON) functionalities. It defines the degree of automation and the locus of control for network management and optimization tasks. The mode is typically configured on a per-network-element (e.g., gNB, eNB) or per-SON-function basis and dictates whether decisions are made by the network element itself (distributed SON), by a central management system (centralized SON), or through a hybrid approach. The three primary modes are NC0, NC1, and NC2, each representing a different balance between human operator oversight and machine-driven automation.
NC0, or Manual Mode, represents the traditional network management approach. In this mode, all configuration, optimization, and fault recovery actions are manually planned and executed by network operators via the Operations, Administration, and Maintenance (OAM) system. The network element operates strictly according to its static configuration and provides performance measurements to the OAM system, but it does not initiate any autonomous changes. This mode offers maximum control and predictability but is slow to react to dynamic network conditions and scales poorly with large, dense networks.
NC1, or Assisted Mode, introduces a level of automation while retaining central oversight. In this hybrid mode, the network element (distributed SON) or a dedicated SON server (centralized SON) can analyze performance data and generate recommendations for configuration changes. However, these recommendations are not automatically applied. Instead, they are presented to the network operator via the OAM system for review and manual approval. This allows operators to leverage the data-processing capabilities of SON algorithms while maintaining a human-in-the-loop for validation, especially for critical changes that could impact service.
NC2, or Full Automatic Mode, represents the highest level of automation. Here, the SON function (whether distributed in the node or centralized) is granted the authority to autonomously analyze network conditions, make optimization decisions, and directly apply the necessary configuration changes to the network element without requiring prior human approval. This enables real-time or near-real-time adaptation to traffic fluctuations, interference, failures, and the integration of new cells. NC2 is essential for realizing the full benefits of SON, such as rapid self-healing and continuous optimization, but it requires robust, thoroughly tested algorithms and comprehensive policy frameworks to prevent unstable or undesirable network behavior.
Purpose & Motivation
The Network Control Mode concept was created to provide a structured and graduated pathway for operators to introduce automation into their networks, specifically through SON features defined from 3GPP Release 8 onwards. Prior to SON, network rollout, optimization, and maintenance were entirely manual processes, which became prohibitively expensive, slow, and error-prone as networks grew in size and complexity with the advent of LTE and heterogeneous deployments involving macro cells, small cells, and different frequency bands.
The primary problem NC modes solve is the "trust gap" in network automation. Moving from a fully manual model to a fully autonomous one is a significant operational and cultural shift for operators. The NC0, NC1, NC2 hierarchy provides a risk-managed migration path. Operators can start with NC1 (Assisted Mode) for non-critical optimization functions, allowing their teams to build confidence in the SON algorithms by reviewing recommendations before they are applied. Once the algorithms are proven reliable under various conditions, operators can transition specific functions to NC2 (Full Automatic) to achieve operational efficiency gains and faster response times.
Furthermore, NC modes allow for flexibility based on the criticality of the network function and the operator's operational philosophy. For example, an operator might run Mobility Load Balancing in NC2 mode for rapid reaction to congestion but run Physical Cell ID conflict resolution in NC1 mode to ensure manual oversight of a fundamental radio parameter. The concept also facilitates multi-vendor interoperability in SON, as it defines clear interfaces and responsibilities between the network element (which executes the changes) and the management system (which may authorize them), depending on the configured mode. This structured approach to control delegation is a cornerstone of modern, software-defined, and autonomous mobile network management.
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (2 CRs across 2 releases). Complements the general historical overview above with the evidence-based evolution of this function.
Studied in Rel-8, normative work from Rel-15.
In Release 15, the NC function was introduced to enable a new Network Control Mode for UE Power Saving. This mode allows the network to configure and control specific UE power saving settings and behaviors. The introduction involved defining new procedures and capabilities for this control mechanism within the relevant 3GPP specifications.
- Approved by plenary – Rel-15 spec under change control TS 38.113
In Release 16, the standardization of the Network Control mode (NC) for NR-U was introduced. This included the definition of new UE procedures, such as the initiation and termination of the Network Control mode, and specified the required interactions with the network. Furthermore, enhancements were made to the Radio Resource Management and mobility procedures to fully support the NC mode of operation.
- Approved by plenary – Rel-16 spec under change control TS 38.175
Explore further
Broader topics and technologies where NC plays a role.
Defining Specifications
3GPP specifications that define or reference NC, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 32.303 v900 | Notification IRP CORBA Solution Set | Rel-9 |
| TS 32.306 vj00 | Configuration Management Notification IRP Solution Set | Rel-19 |
| TS 32.373 v1900 | IRP Security Services CORBA Solution | Rel-9 |
| TS 32.376 vj00 | Security services for IRP Solution Set | Rel-19 |
| TS 38.113 vj00 | NR Base Station EMC Specification | Rel-19 |
| TS 38.175 vj00 | EMC for NR IAB Nodes | Rel-19 |
| TR 38.903 vj00 | Test Tolerances & Measurement Uncertainties | Rel-19 |
| TR 44.901 vj00 | Extended NACC for External Cell Change | Rel-19 |