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

Glossary term · Management

TM

Telecommunication Management

Management →

TM is the comprehensive 3GPP framework for managing all network aspects, providing standardized interfaces and procedures to monitor, control, and optimize resources and services.

Introduced
Rel-4
Where
Management
Specifications
33 specs
Also in
Radio Access Network
TM Description Purpose What changed Neighbours Specifications

Description

Telecommunication Management (TM) is the overarching 3GPP framework and set of specifications that define how mobile networks are operated, administered, and maintained. It encompasses the full FCAPS model—Fault, Configuration, Accounting, Performance, and Security management—applied to the entire network domain, including the Radio Access Network (RAN), Core Network (CN), and User Equipment (UE). The architecture is typically based on a manager-agent model, where Network Management Systems (NMSs) or Element Management Systems (EMSs) act as managers, and the individual network elements (NEs) like base stations and core nodes act as agents that are managed. Communication between managers and agents uses standardized interfaces, primarily the Itf-N (Northbound Interface) and proprietary or standardized southbound interfaces.

The framework operates through a set of well-defined management functions. Fault Management involves the continuous surveillance of the network to detect, isolate, and correct abnormal operations and failures, generating alarms and notifications. Configuration Management handles the installation, provisioning, and modification of network equipment and software, including the setup of network parameters and software upgrades. Performance Management involves the collection and analysis of statistical data related to the network's operation and traffic, such as call success rates, handover statistics, and throughput measurements, which are used for capacity planning and optimization.

Accounting Management (often tied to Charging) collects resource usage data for billing purposes. Security Management ensures the integrity, confidentiality, and availability of management data and operations. 3GPP specifies detailed Information Models for these functions, often using object-oriented paradigms where managed entities (like a cell or a network slice instance) are represented as Managed Objects with defined attributes, operations, and notifications. These models are frequently realized using protocols like SNMP or CORBA/CMIP in earlier releases, and increasingly moving towards NETCONF/YANG and RESTful APIs in modern implementations. The TM framework is essential for achieving automated, efficient, and multi-vendor interoperable network operations, which is critical for the scalability and reliability of large-scale mobile networks.

Purpose & Motivation

Telecommunication Management was created to solve the critical operational challenges arising from the complexity and multi-vendor nature of modern mobile networks. In the early days of cellular networks, management systems were largely proprietary, leading to vendor lock-in, high operational costs, and inefficiencies for operators running networks with equipment from multiple suppliers. There was no standardized way to monitor a Nokia base station and an Ericsson core node from a single management console. The purpose of standardizing TM within 3GPP was to define a unified framework that ensures interoperability, reduces operational complexity, and lowers costs.

Its creation was motivated by the need for scalable and automated operations. As networks grew from 2G to 3G and beyond, the number of network elements exploded, making manual configuration and troubleshooting impractical. The TM framework provides the blueprint for automated provisioning, bulk configuration, and centralized fault monitoring. It addresses the problem of integrating new network technologies and services—like IMS, LTE, and 5G—into existing operational support systems (OSS) by defining consistent management interfaces and information models. This allows operators to introduce new capabilities without having to build entirely new, siloed management systems.

Furthermore, TM standardizes the critical flow of performance and accounting data, which is the lifeblood for network optimization and business operations. Without standardized performance measurements, comparing the health of different parts of the network or different vendors' equipment is difficult. Standardized accounting data collection is equally vital for generating accurate billing records. In essence, TM exists to transform the telecommunications network from a collection of hardware boxes into a programmable, observable, and efficiently managed service delivery platform, enabling the quality of service and operational efficiency that subscribers and operators demand.

What changed in its specifications

The latest release-to-release comparison of specifications that define TM. Each summary describes the whole specification, not only this term.

TR 21.905Rel-17 → Rel-18

Rel-18 brings only minor changes to TS 21.905: 0 clauses changed, with no change attributed to a release feature.

Full comparison in TR 21.905 →
TS 25.322Rel-7 → Rel-8

Polling via POLL SUFI, flexible RLC PDU sizes in uplink, new primitive parameters for UM and AM, optional SN_Delivery configuration, altered SDU handling.

Full comparison in TS 25.322 →

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-4 Initial

Telecommunication Management was formally established as a key work area within 3GPP, building upon ITU-T TMN principles. The initial architecture defined core management concepts, the generic network resource model, and baseline requirements for managing UMTS networks, including the Circuit-Switched and Packet-Switched domains. It laid the groundwork for standardized fault, configuration, and performance management procedures.

Defining Specifications

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

SpecificationTitleRelease
TR 21.905 vj20 3GPP Terminology and Definitions Rel-19 read
TS 25.322 vj00 RLC Protocol Specification Rel-19 read
TS 25.331 vj01 UTRAN Radio Resource Control Protocol Rel-19 read
TR 25.912 vj00 Evolved UTRA and UTRAN Technical Report Rel-19 read
TS 28.701 vj00 Core Network NRM IRP Requirements Rel-19 read
TS 32.101 vj00 PLMN Management Principles and Requirements Rel-19 read
TS 32.102 vj00 Telecom Management Physical Architecture Framework Rel-19 read
TS 32.111 vj00 Fault Management Alarm IRP Solution Sets Rel-19 read
TS 32.301 vj00 Notification IRP Requirements Rel-19 read
TS 32.322 vj00 Test Management IRP Information Service Rel-19 read
TS 32.325 v900 Test Management IRP XML Definitions Rel-9 read
TS 32.326 vj00 Test Management IRP Solution Set Definitions Rel-19 read
TS 32.371 vj00 Security Management Concept & Requirements Rel-19 read
TS 32.600 vj00 3GPP Configuration Management Specification Rel-19 read
TS 32.601 vj00 Basic Configuration Management IRP Requirements Rel-19 read
TS 32.611 vj00 Bulk CM IRP Requirements Rel-19 read
TS 32.612 vj00 Bulk Configuration Management IRP: Information Service Rel-19 read
TS 32.621 vb00 Generic Network Resources IRP Requirements Rel-11 read
TS 32.631 vb00 Core Network Resources IRP Requirements Rel-11 read
TS 32.661 vj00 Kernel Configuration Management IRP Requirements Rel-19 read
TS 32.690 vj00 Inventory Management IRP Requirements Rel-19 read
TS 32.691 vb00 Inventory Management IRP Requirements Rel-11 read
TS 32.711 vb00 TN Interface NRM IRP Requirements Rel-11 read
TS 36.300 vj20 E-UTRAN Radio Interface Protocol Architecture Rel-19 read
TS 36.302 vj00 E-UTRA Physical Layer Services Rel-19 read
TS 36.322 vj00 E-UTRA Radio Link Control Protocol Specification Rel-19 read
TS 36.331 vj40 E-UTRA Radio Resource Control (RRC) Protocol Rel-19 read
TS 36.747 ve00 Enhanced CRS and SU-MIMO IM Performance Requirements Rel-14 read
TR 37.901 vf10 UE Application Layer Data Throughput Performance Rel-15 read
TS 38.322 vj30 NR Radio Link Control (RLC) Protocol Specification Rel-19 read
TS 38.331 vj40 NR Radio Resource Control (RRC) Rel-19 read
TR 38.833 vh00 NR Demodulation Performance Enhancement Rel-17 read
TR 38.878 vi40 Technical Report on Advanced Receiver for MU-MIMO Rel-18 read