CNC

Centralized Network Configuration

Management →
Introduced in Rel-16 Also in: Services, Management

CNC is a 3GPP management framework for the centralized and automated configuration of network functions across multiple domains to reduce operational complexity.

Category
Management
Introduced
Rel-16
Where
Core Network › 5G Core
Also touches
2 segments
Specifications
8 specs
CNC Description Purpose Detected Changes Specifications

Description

Centralized Network Configuration (CNC) is a comprehensive management framework defined by 3GPP for centralized configuration of network functions across multiple administrative and technological domains. The architecture establishes a hierarchical model where a central CNC function coordinates with domain-specific management systems to ensure consistent configuration policies are applied throughout the network infrastructure. This framework operates through standardized interfaces that enable automated configuration provisioning, validation, and monitoring across heterogeneous network environments including RAN, core network, and transport segments.

The CNC framework employs a policy-driven approach where configuration policies are defined at a high abstraction level and then translated into domain-specific configuration commands. These policies can encompass various aspects including network slicing configurations, QoS parameters, security settings, and resource allocation parameters. The CNC function maintains a global view of network resources and their configurations, enabling it to optimize resource utilization and ensure configuration consistency across different network segments. This global perspective is particularly valuable for end-to-end service provisioning where configurations must be coordinated across multiple domains to meet service level agreements.

Key components of the CNC architecture include the CNC function itself, which serves as the central coordination point, and domain-specific management systems that implement the actual configuration changes within their respective domains. The framework defines standardized interfaces between these components, with the CNC function communicating with domain managers through the CNC-DM (Domain Manager) interface. Configuration data models are standardized to ensure interoperability between different vendors' implementations. The CNC function also interfaces with higher-level management systems such as network slice management functions and service orchestration platforms to receive configuration requirements and report on configuration status.

In operation, CNC follows a closed-loop automation approach where configuration changes are planned, deployed, validated, and monitored continuously. When a configuration change is required, the CNC function first validates the change against existing configurations and network policies to ensure compatibility and compliance. It then coordinates the deployment of the change across relevant domains, ensuring proper sequencing and timing to minimize service disruption. After deployment, the CNC function monitors the configuration's effectiveness and can trigger corrective actions if the actual network behavior deviates from expected outcomes. This automated lifecycle management significantly reduces manual intervention and configuration errors in complex network environments.

Purpose & Motivation

CNC was developed to address the growing complexity of network configuration management in 5G and beyond networks, where multiple technologies, vendors, and administrative domains must work together seamlessly. Traditional network configuration approaches relied heavily on manual, domain-specific configuration that was time-consuming, error-prone, and difficult to coordinate across different network segments. As networks evolved toward software-defined architectures and network slicing became a fundamental capability, the need for automated, centralized configuration management became critical to enable rapid service deployment and efficient resource utilization.

The creation of CNC was motivated by several key challenges in modern telecommunications networks. First, the introduction of network slicing required coordinated configuration across RAN, core, and transport domains to instantiate end-to-end network slices with specific performance characteristics. Without centralized coordination, slice configuration would require manual coordination between multiple domain managers, leading to long deployment times and potential configuration inconsistencies. Second, the increasing heterogeneity of network technologies (including 4G, 5G, and future 6G components) created interoperability challenges that could only be addressed through standardized configuration management interfaces.

CNC solves these problems by providing a standardized framework for centralized configuration management that abstracts the complexity of underlying network technologies. It enables network operators to define configuration policies at a service level and have those policies automatically translated into domain-specific configurations. This reduces operational overhead, minimizes configuration errors, and accelerates service deployment. The framework also supports multi-vendor environments by defining standardized interfaces and data models, allowing operators to manage heterogeneous network equipment through a single centralized interface rather than dealing with each vendor's proprietary management systems separately.

Detected Changes Across Releases

from 3GPP Change Requests

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

Rel-16 4 changes

In Release 16, the CNC function was introduced to provide centralized configuration management for vertical applications, specifically enabling the configuration of service-specific data. The release clarified CNC capabilities, including enhanced location management with procedures for location reporting configuration, configuration updates, and adaptive reporting, as well as the definition of the SEAL-X3 reference point for interaction between group and configuration management servers.

  • Update to location configuration procedure TS 23.434CR0015
  • Correct location trigger configuration TS 23.434CR0023
  • Clarification on CNC TS 24.519CR0009
  • Clarification on CNC TS 24.539CR0009
Rel-17 1 change

In Release 17, the new capability for the CNC function was the addition of VAL UE Information to the configuration management procedure. This enhancement allowed the SEAL's centralized configuration management service to configure and manage service-specific data applicable to vertical applications. It specifically enabled the group management server to retrieve this VAL service data from the configuration management server via the SEAL-X3 reference point.

  • add VAL UE Information to configuration management procedure TS 23.434CR0060
Rel-18 13 changes

In Release 18, the CNC function introduced new information flows for location reporting configuration updates and cancellations, and enhanced the BDT (Background Data Transfer) configuration with new and corrected API operations. It also added support for group configuration data subscription updates and unsubscription. Furthermore, it specified new adaptive location reporting procedures, allowing the SEAL LMS to propose configuration adjustments directly or suggestively to the VAL server.

  • Add information flow for location reporting configuration update TS 23.434CR0148
  • NRM BDT configuration TS 23.434CR0213
  • Add the information flow for “Location reporting configuration cancel request response” TS 23.434CR0170
  • NRM BDT configuration API TS 23.434CR0231
  • Missing request expiration time in BDT configuration request TS 23.434CR0265
  • Corrections for BDT configuration TS 23.434CR0272

+ 7 more changes

Rel-19 1 change

In Release 19, the CNC function within SEAL introduced support for adaptive location configuration and reporting. This enables the location management server to dynamically adjust location reporting configurations and propose these adaptive changes to the VAL server or client, with notification options for "DIRECT UPDATE" or "SUGGESTIVE UPDATE". These enhancements provide more flexible and efficient location management for vertical applications.

  • Support for adaptive location configuration and reporting TS 23.434CR0304
Rel-20 1 change

In Release 20, the CNC function introduced new capabilities for adaptive location reporting configuration and VAL service area configuration within the SEAL framework. Specifically, it added procedures for the location management server to propose adaptive configurations to a VAL server and to receive decisions on them, as well as mechanisms for a VAL server to configure a list of service area identifiers. These enhancements built upon the existing configuration management services for vertical applications.

  • Include power saving configuration within the NRM services for IoT devices TS 23.434CR0403

Explore further

Broader topics and technologies where CNC plays a role.

Defining Specifications

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

SpecificationTitleRelease
TS 23.434 vk00 Service Enabler Architecture for Verticals Rel-20
TR 23.745 vh00 Study on App Layer Support for Factories of the Future in 5G Rel-17
TS 24.519 vh10 TSN AF to DS-TT/NW-TT Protocol Aspects Rel-17
TS 24.539 vj30 NW-TT Protocol Aspects Rel-19
TR 28.839 vi10 Technical Report Rel-18
TS 29.585 vj00 TSN Interworking Protocol for 5G System Rel-19
TS 32.282 vi20 Charging management; Time Sensitive Networking Rel-18
TR 33.851 vh10 Security for Industrial IoT in 5G Rel-17