Network Management

Description

In the 3GPP context, Network Management (NM) refers to the comprehensive framework of standardized functionalities and interfaces used to manage 3GPP-defined systems, including the Core Network (CN), Radio Access Network (RAN), and User Equipment (UE). It is not a single center but a layered architecture and a set of processes defined across numerous technical specifications (TS), primarily in the 28-series (Management and Orchestration), 32-series (Telecommunication management), and others. The NM framework is based on the FCAPS model (Fault, Configuration, Accounting, Performance, and Security Management) and the Telecommunications Management Network (TMN) layered model.

The architecture typically involves several logical layers: Network Element (NE) layer, Element Management (EM) layer, and Network Management (NM) layer. The NM layer provides an end-to-end view of the network and manages multiple sub-networks or domains. It communicates with the Element Management Systems (EMS) below it using standardized interfaces, most notably the Itf-N (Northbound Interface) defined using XML-based protocols. Key management functions include performance monitoring (collecting counters and measurements for KPIs), fault management (alarm surveillance and root cause analysis), configuration management (software handling, provisioning), and lifecycle management of network services and slices.

NM works through a set of standardized Information Service (IS) models, which define the managed objects, their attributes, and the notifications they can emit. Managers (NM systems) and Agents (EM systems or NEs) exchange information using protocols like CORBA/IDL in earlier releases and moving towards RESTful APIs and YANG data models in later releases (e.g., for 5G network resource model). The specifications detail everything from requirements (32.1xx series) to protocol-specific mappings (32.3xx and 32.6xx series). This extensive standardization ensures that an operator can integrate management systems from different vendors to manage a heterogeneous network infrastructure.

Purpose & Motivation

The primary purpose of standardizing Network Management in 3GPP is to enable the operational feasibility of multi-vendor mobile networks. Without common management interfaces and information models, each network element vendor would provide proprietary management systems, forcing operators to use dozens of different tools to run their networks. This would be enormously costly, inefficient, and error-prone. Standardized NM solves this by defining how management information is modeled and communicated, allowing for integrated, higher-level operational support systems (OSS).

Historically, management standardization evolved from the ITU-T TMN framework. 3GPP adopted and extended these principles for mobile networks starting from 3G (Release 99/4). The initial focus was on managing the circuit-switched core and radio network. As networks grew more complex with the introduction of IP-based cores (IMS, EPC), packet-switched services, and later virtualized network functions, the NM framework had to evolve dramatically. It addresses the limitations of siloed, vendor-locked management by providing a common language and set of interactions for fault monitoring, performance assurance, software updates, and configuration—critical for maintaining service quality, reducing operational expenditure (OPEX), and enabling new operational paradigms like self-organizing networks (SON) and automated lifecycle management for network slicing in 5G.