Description
The Telecommunications Management Network (TMN) is a conceptual framework standardized by the ITU-T in recommendation M.3010. It is not a physical network but a logically separate, overarching architecture that interfaces with the telecommunications network it manages. The core principle of TMN is to provide organized, structured, and standardized ways to achieve the interoperability and automated management of heterogeneous network elements (NEs) and network systems. Its architecture is built upon a layered model comprising four logical layers: Business Management Layer (BML), Service Management Layer (SML), Network Management Layer (NML), and Element Management Layer (EML), with the Network Element Layer (NEL) representing the actual managed resources.
TMN defines key functional areas, encapsulated in the FCAPS model: Fault Management (detection, isolation, correction), Configuration Management (provisioning, status control), Accounting Management (usage metering and charging), Performance Management (quality and traffic data collection), and Security Management (access control, integrity). Communication between management systems and network elements occurs across standardized interfaces, primarily the Q3 interface which uses the Common Management Information Protocol (CMIP) over OSI stacks, and the simpler Qx interface. Information is modeled using the Guidelines for the Definition of Managed Objects (GDMO) and Abstract Syntax Notation One (ASN.1), allowing for a common understanding of managed resources.
Within 3GPP, TMN principles and models form the historical foundation for the Operations, Administration, and Maintenance (OAM) framework and the Designated for the Management (Itf-N) reference points. While 3GPP systems have evolved to use more modern protocols like SNMP and NETCONF/YANG, the TMN concepts of management layers, functional separation, and standardized information exchange remain deeply influential. It enables the integration of Network Management Systems (NMS) and Operations Support Systems (OSS) to automate tasks like service provisioning, performance monitoring, and fault correlation across the entire 3GPP network domain, from radio access to core.
Purpose & Motivation
TMN was created to solve the critical problem of operational complexity and cost in multi-vendor telecommunications networks. Before its standardization, each equipment vendor provided proprietary management systems with unique interfaces, forcing network operators to manage a 'islands of management' scenario. This led to high integration costs, manual processes, inability to automate end-to-end service provisioning, and difficulties in correlating faults across different network domains. The TMN framework provided a universal 'blueprint' for interoperable management.
Its adoption by 3GPP, starting in early releases, was motivated by the need to manage complex, layered mobile networks comprising radio, switching, and service platforms from multiple suppliers. TMN's layered architecture (BML, SML, NML, EML) perfectly mapped to the organizational and functional separation within a telecom operator, separating business and service logic from network and element-specific technical management. By standardizing the information models (via GDMO) and communication protocols (CMIP/CMIS over Q3), it aimed to allow an operator's OSS to manage network elements from different vendors through a single, consistent interface, thereby reducing operational expenditure (OPEX) and enabling faster service deployment.
Classification
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (13 CRs across 6 releases). Complements the general historical overview above with the evidence-based evolution of this function.
Studied in Rel-4, normative work from Rel-15.
In Release 15, the TMN (Telecommunications Management Network) function was updated to introduce new Network Resource Management (NRM) definitions for managing EN-DC and 5G interworking, alongside the addition of new management functions and entities. Furthermore, a missing NRM fragment was added specifically to support network performance management capabilities, enhancing the overall management framework for the new 5G network architecture.
In Release 16, a specific enhancement for the TMN function was the correction of the notification support table for the ManagedElement and ManagementNode entities. This update ensured the management system accurately reflected the notification capabilities of these core network resources. The change refined the data handling for network resource management and access control management within the standardized protocols for operation, administration, and maintenance.
- Correct notification support table for ManagedElement and ManagementNode TS 28.622CR0097
In Release 17, the TMN function introduced new stage 2 definitions for file management and for management data collection and discovery. These enhancements expanded the standardized framework for administering network operations, including the handling of security management data and network resource management data. The updates also incorporated refinements to attribute properties for the Management Data Collection information object class.
In Release 18, the enhancements to the Telecommunications Management Network (TMN) function specifically refined the ManagementDataCollection capability. The primary new feature introduced was the ability to request management data on a per-PLMN basis, providing more granular network management. Additionally, corrections were made to the description and definition of the ManagementDataCollection Information Object Class (IOC) to ensure clarity and accuracy in the specification.
In Release 19, the TMN function was enhanced with new enumeration values for management capabilities specifically related to data management. Furthermore, the release provided clarifications on the handling and specifications for historical management data. These updates refined the data management framework within the telecommunications management network.
In Release 20, the primary update for the TMN function was the addition of new enumerated values to represent management capabilities that were missing from the previous Release 19. This enhancement, documented in a Change Request to TS 28.622, specifically addressed the need to define these missing capabilities within the standardized framework for operation, administration, and maintenance.
- Rel-20 CR TS 28.622 Add Enum values for missing R19 management capabilities TS 28.622CR0598
Explore further
Broader topics and technologies where TMN plays a role.
Defining Specifications
3GPP specifications that define or reference TMN, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 21.133 v1400 | 3G Security Requirements | Rel-5 |
| TR 21.905 vj00 | 3GPP Technical Terms and Definitions | Rel-19 |
| TR 26.937 vj00 | 3GPP PSS Characterization | Rel-19 |
| TS 28.622 vk20 | Telecommunication Management; Generic NRM Information Service | Rel-20 |
| TS 28.632 vj00 | Inventory Management NRM Integration Reference Point | Rel-19 |
| TS 28.702 vj00 | Core Network NRM IRP Information Service | Rel-19 |
| TS 28.705 vj00 | IMS NRM IRP Information Service | Rel-19 |
| TS 28.708 vj00 | EPC NRM Integration Reference Point Information Service | Rel-19 |
| TS 29.816 va00 | PCRF Failure & Restoration Study | Rel-10 |
| TS 32.101 vj00 | Management principles and high-level requirements | Rel-19 |
| TS 32.102 vj00 | Telecom Management Physical Architecture Framework | Rel-19 |
| TS 32.111 vj00 | Fault Management Requirements | Rel-19 |
| TS 32.141 vj00 | Subscription Management (SuM) Architecture | Rel-19 |
| TS 32.300 vj00 | 3GPP Network Resource Naming Convention | Rel-19 |
| TS 32.306 vj00 | Configuration Management Notification IRP Solution Set | Rel-19 |
| TS 32.371 vj00 | Security Management Concept & Requirements | Rel-19 |
| TS 32.372 vj00 | Security Service for IRP Information Service | Rel-19 |
| TS 32.401 vj00 | Performance Management Concept & Requirements | Rel-19 |
| TS 32.602 vj00 | Basic Configuration Management IRP Information Service | Rel-19 |
| TS 32.622 vb10 | Generic Network Resources IRP NRM | Rel-11 |
| TS 32.632 vb00 | Core Network Resources IRP: Network Resource Model | Rel-11 |
| TS 32.642 vb50 | UTRAN Network Resource Model for Configuration Management | Rel-11 |
| TS 32.652 vc00 | GERAN Network Resources NRM for Configuration Management | Rel-12 |
| TS 32.662 vj00 | Configuration Management (CM); Kernel CM IRP | Rel-19 |
| TS 32.690 vj00 | Inventory Management IRP Requirements | Rel-19 |
| TS 32.692 vb00 | Inventory Management NRM IRP Specification | Rel-11 |
| TS 32.712 vb10 | Transport Network Interface NRM for CM | Rel-11 |
| TS 32.722 vb00 | Repeater NRM IRP: Network Resource Model | Rel-11 |
| TS 32.732 vb00 | IMS Network Resource Model IRP: Information Service | Rel-11 |
| TS 32.752 vb01 | EPC NRM IRP Information Service | Rel-11 |
| TS 32.819 v800 | Element Management Layer OS Functions | Rel-8 |
| TS 32.859 vc10 | Alarm Management Quality Improvement Study | Rel-12 |
| TS 52.021 vj00 | GSM A-bis Interface Network Management | Rel-19 |
| TS 52.402 vj00 | GSM Performance Management Measurements | Rel-19 |