NGCOR

Next Generation Converged Operations Requirements

Management →
Introduced in Rel-12

NGCOR is the 3GPP framework defining operational requirements for converged, automated network management across multi-vendor and multi-technology systems like 5G to reduce cost and complexity.

Category
Management
Introduced
Rel-12
Where
Management
Specifications
3 specs
NGCOR Description Purpose Related Classification Detected Changes Specifications

Description

NGCOR, or Next Generation Converged Operations Requirements, is a comprehensive framework developed within 3GPP to define the operational requirements for managing modern, converged telecommunications networks. It specifically addresses the challenges of operating networks that integrate multiple Radio Access Technologies (RATs), such as 4G LTE and 5G NR, and potentially non-3GPP access, under a unified management system. The framework is detailed across several Technical Specifications (TS), including TS 28.390 (requirements), TS 32.130 (telecom management principles), and TS 32.851 (management services). Its primary goal is to enable seamless, automated, and efficient network operations and maintenance (O&M) in a heterogeneous environment.

The architecture of NGCOR is centered on principles of convergence, automation, and abstraction. It defines a set of management services and northbound interfaces that allow for a unified view and control of network resources, regardless of the underlying technology. This involves standardizing data models, fault management, performance management, configuration management, and lifecycle management procedures. Key components include the Management Function (MF) and the Network Resource Model (NRM), which provide an abstracted representation of physical and virtual network functions. NGCOR ensures that operational support systems (OSS) can manage network slices, virtualized network functions (VNFs), and physical network functions (PNFs) through common interfaces and data exchange formats.

In practice, NGCOR works by establishing a common set of requirements that vendors and operators must adhere to for network management interfaces and capabilities. It enables multi-domain management, allowing an operator to manage both the Evolved Packet Core (EPC) and the 5G Core (5GC) from a single OSS platform. The framework supports closed-loop automation, where the management system can automatically detect anomalies, analyze performance data, and execute corrective actions (e.g., scaling resources, reconfiguring parameters) without human intervention. This is crucial for supporting dynamic network slicing, where each slice may have unique performance and service level agreement (SLA) requirements that must be continuously monitored and assured.

NGCOR's role in the network is foundational for achieving operational efficiency and agility in the 5G era. By providing standardized requirements, it reduces integration costs and complexity when deploying equipment from different vendors. It facilitates the transition to cloud-native network architectures by defining how virtualized and containerized network functions should be managed. Furthermore, it underpins the realization of zero-touch network and service management (ZSM), a key objective for future networks where manual operations are minimized. In essence, NGCOR is the blueprint that ensures the management plane can keep pace with the innovation and complexity introduced in the data and control planes of next-generation networks.

Purpose & Motivation

NGCOR was created to address the escalating operational complexity and cost associated with managing multi-vendor, multi-technology networks. Prior to its definition, network management was often siloed, with separate OSS systems for different network domains (e.g., radio, transport, core) and technologies (2G, 3G, 4G). This led to high integration costs, inefficient processes, and an inability to rapidly deploy and assure new services. The advent of 5G, with its promises of network slicing, ultra-reliable low-latency communication (URLLC), and massive machine-type communication (mMTC), made these legacy operational models untenable.

The historical context for NGCOR is the industry's shift towards software-defined networking (SDN) and network function virtualization (NFV). While these technologies introduced flexibility, they also created new management challenges for virtualized resources and service chains. NGCOR provides the necessary operational requirements to harness this flexibility. It solves the problem of fragmented management by defining a converged framework that abstracts technological specifics, allowing operators to manage their entire network estate through common principles and interfaces.

Ultimately, the motivation for NGCOR is to enable scalable, automated, and cost-effective operations. It addresses the limitations of previous approaches that were reactive, manual, and technology-specific. By standardizing operational requirements, NGCOR lays the groundwork for autonomous networks, reduces time-to-market for new services, and ensures that operational capabilities evolve in lockstep with the advanced features offered by 5G and beyond networks.

Classification

Part ofOSS
Related approachesNRM5GC

Detected Changes Across Releases

from 3GPP Change Requests

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

Studied in Rel-12, normative work from Rel-17.

Rel-17 7 changes

In Release 17, the NGCOR function was updated with new business requirements and use cases to support advanced NG-RAN sharing scenarios. These additions specifically include requirements for mixed NG-RAN sharing, individual management of shared elements, and radio resources partitioning between Public Land Mobile Network (PLMN) operators. Furthermore, the release provided a solution description for managing shared NG-RAN Network Elements in a Multi-Operator Core Network (MOCN) scenario and performed a cleanup of concept and business-level requirements.

  • Update the business requirements to support NG-RAN sharing TS 32.130CR0006
  • Update business requirements to applicable for SBMA TS 32.130CR0009
  • Add mixed NG-RAN sharing use case and requirements TS 32.130CR0013
  • Add NG-RAN sharing individual management use case and requirements TS 32.130CR0014
  • Add missing use case and requirements for radio resources partitioning between POPs TS 32.130CR0018
  • Solution description for the requirements for the management of the shared NG-RAN NE(s) in MOCN network sharing scenario TS 32.130CR0019

+ 1 more changes

Rel-18 2 changes

In Release 18, the NGCOR function was updated with new requirements for managing the NG-RAN MOCN network sharing scenario. Specifically, these additions addressed the operational needs for scenarios where multiple Cell Identities are broadcast within the shared radio access network. The updates ensure the identified IRP solution subset satisfies these new requirement statements for converged operations.

  • Add new requirements for management support for NG-RAN MOCN network sharing scenario TS 32.130CR0024
  • Rel-18 CR TS 32.130 Add requirements for NG-RAN MOCN network sharing scenario with multiple Cell Identity broadcast TS 32.130CR0026
Rel-19 7 changes

In Release 19, the NGCOR function introduced new, specific management requirements for Indirect Network Sharing (INS), including requirements for RAN and CN management, PLMN-granularity performance measurements, and dedicated management workflows. The release also added access requirements for managing shared NG-RAN and worked to separate business-level from specification-level requirements. Furthermore, the existing framework of Solution Profiles was used to categorize these new requirements for the management support of the INS scenario.

  • Rel-19 CR TS 32.130 Add access requirements for management of shared NG-RAN TS 32.130CR0040
  • Rel-19 CR TS 32.130 Add requirements for RAN and CN Management of Indirect of Network Sharing TS 32.130CR0041
  • Rel-19 CR TS 32.130 Add requirements for Management of Indirect of Network Sharing TS 32.130CR0043
  • Rel-19 CR TS 32.130 Add PLMN granularity performance measurement requirements for Indirect Network Sharing TS 32.130CR0052
  • Rel-19 CR TS 32.130 Add management workflows for requirements for management of INS TS 32.130CR0055
  • Rel-19 CR TS 32.130 Separate business-level requirements from specification-level requirements TS 32.130CR0048

+ 1 more changes

Explore further

Broader topics and technologies where NGCOR plays a role.

Defining Specifications

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

SpecificationTitleRelease
TS 28.390 vj00 Solution Profiles for Interface IRPs Rel-19
TS 32.130 vj20 Network Sharing OAM&P Requirements Rel-19
TS 32.851 vc20 Network Sharing OAM Requirements Rel-12