Description
The Telecom Operations Map (TOM), later evolved into the Enhanced Telecom Operations Map (eTOM), is a comprehensive, process-oriented framework developed and maintained by the TM Forum and adopted by 3GPP for standardization references. It is not a software product but a conceptual model that describes all the business processes required by a service provider. The map categorizes these processes into a hierarchical structure, defining how they interact and what information they exchange. Its primary goal is to provide a common language and structure for designing and implementing Operations Support Systems (OSS) and Business Support Systems (BSS).
Architecturally, the TOM is organized into vertical and horizontal process groupings. The vertical groupings, or end-to-end processes, represent the core flows like Fulfillment, Assurance, and Billing (FAB). These span from customer-facing interactions down to network resource management. The horizontal groupings represent functional layers such as Customer Relationship Management (CRM), Service Management & Operations, and Resource Management & Operations (Network & IT). Each process in the map is defined with its inputs, outputs, triggers, and interactions with other processes. For implementation, the framework is complemented by shared information models, like the Shared Information/Data Model (SID), which standardizes the data entities (e.g., Customer, Service, Resource) that processes act upon.
How it works in practice is that telecom operators and their vendors use the TOM as a blueprint. When an operator wants to automate a new service provisioning flow, they refer to the TOM to identify the standard processes involved—such as "Order Handling," "Service Configuration," and "Resource Activation." They then design their OSS software and interfaces to align with these process definitions and data models. This alignment enables system integration and interoperability between different vendors' OSS components. Its role is foundational for achieving automated, efficient, and scalable operations, which is critical for managing complex modern networks like 5G and for enabling agile service delivery.
Purpose & Motivation
The Telecom Operations Map was created to address the critical industry problem of operational complexity and high costs associated with managing telecommunications networks. Before its widespread adoption, each telecom operator designed its operational processes and supporting IT systems in a proprietary, siloed manner. This led to severe challenges when integrating systems from different vendors, automating end-to-end service flows, and launching new services quickly. The lack of standardization resulted in lengthy integration projects, high operational expenditure (OPEX), and inflexible operations.
The TOM provides a standardized, industry-agreed framework that defines 'how' a telecom business should operate. It solves the problem of process fragmentation by offering a common reference model. This allows operators to streamline their operations, automate processes consistently, and more easily integrate multi-vendor environments. For vendors, it reduces the customization needed for each operator, lowering costs and accelerating deployment.
Historically, its development was motivated by the industry's shift towards competition and deregulation in the 1990s and 2000s. Operators needed to become more agile and cost-efficient. The TM Forum, with contributions from leading global operators and vendors, developed the TOM to meet this need. Its adoption into 3GPP specifications (e.g., for management architecture) provided a formal link between network technical standards and business operations, ensuring that network management interfaces could support these standardized operational processes.
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (91 CRs across 5 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 TO function introduced a standardized collection of specialist technical terms and definitions to ensure consistent terminology across 3GPP specifications. This included defining core system components like the 3GPP system, Access Stratum, and Base Station, as well as procedures such as Authentication and baseline capabilities for UE operation. The primary goal was to provide a unified reference to prevent inconsistent use of terminology and aid readers across multiple project documents.
- CR to TS 38.213 capturing the RAN1#92bis and RAN1#93 meeting agreements and aligning higher layer parameters with TS 38.331 TS 38.213CR0002
- CR to 38.213 capturing the RAN1#94 meeting agreements TS 38.213CR0005
- Combined CR of all essential corrections to 38.213 from RAN1#94bis and RAN1#95. TS 38.213CR0007
- Correction to dynamic HARQ codebook in NR TS 38.213CR0014
- Corrections to TS 38.213 TS 38.213CR0015
- Correction to last PUCCH resource set configuration TS 38.213CR0019
+ 14 more changes
In Release 16, the Telecom Operations Map (TO) function was updated to incorporate new procedures and corrections for network operations, including enhancements for SCell dormancy, sidelink communications, and NR-U 2-step RACH. The release introduced specific technical clarifications for handling HARQ-ACK feedback, uplink cancellation, and prioritization between uplink and sidelink transmissions. These updates ensured consistent terminology and operational procedures across the 3GPP system specifications.
- CR to 38.213 on RRC parameter alignment for SCell dormancy TS 38.213CR0133
- CR to 38.213 on BWP triggering via SCell dormancy indication TS 38.213CR0134
- CR to 38.213 on HARQ-ACK processing timeline for DCI format 1_1 with Scell dormancy indication without scheduling PDSCH TS 38.213CR0135
- Corrections related to sidelink physical layer procedures TS 38.213CR0145
- Corrections related to the sidelink slot index TS 38.213CR0154
- CR to 38.213 on NR-U 2-step RACH PO configuration TS 38.213CR0165
+ 19 more changes
In Release 17, the TO function incorporated changes related to extending NR operation to 71 GHz and included corrections for various technical procedures such as PDCCH monitoring, SSB availability for scheduling MBS, and UL prioritization related to SP-CSI. It also updated terminology, changing the abbreviation of "DN" from Destination Network to include both Data Network and Distinguished Name. Furthermore, the release provided corrections for Beam Failure Recovery within the unified TCI state framework and for UE capabilities regarding CA and DC.
- Introduction for extending NR operation to 71 GHz TS 38.213CR0271
- Corrections on extending NR operation to 71 GHz TS 38.213CR0291
- Corrections on extending NR operation to 71 GHz TS 38.213CR0320
- Corrections on the value of slot configuration period in TS 38.213 for the features extending NR operation to 71 GHz TS 38.213CR0335
- CR on PDCCH monitoring when overlapping with the rate matching pattern to TS 38.213 TS 38.213CR0383
- CR on SS0 availability for scheduling MBS to TS 38.213 TS 38.213CR0399
+ 17 more changes
In Release 18, the Telecom Operations Map (TO) function was updated to the Rel-18 version, as indicated by multiple MCC updates. The release also introduced specific operational corrections and enhancements, including those for Non-Terrestrial Networks (NTN) such as FR2-NTN inclusion and RACH-less handover procedures, alongside refinements to sidelink (SL) power control and reporting mechanisms.
- Corrections to the Pathloss RS in LTM TCI state TS 38.213CR0633
- Corrections to the beam of CFRA triggered by cell switch command in TS38.213 TS 38.213CR0644
- Correction on SSB to CG PUSCH mapping for NTN RACH-less handover TS 38.213CR0656
- Corrections to TS 38.213 on OLPC for SL PRS TS 38.213CR0657
- CR on FR2-NTN inclusion to TS 38.213 TS 38.213CR0658
- Corrections to SSB-RO association for LTM TS 38.213CR0691
+ 13 more changes
In Release 19, the primary update for the Telecom Operations Map function was a version update to the Rel-19 iteration, specifically for the Management Concept and Capabilities (MCC). This was accompanied by a correction to align RRC parameter names with the definitions in the 3GPP TS 38.331 specification, ensuring consistent terminology across documents.
Explore further
Broader topics and technologies where TO plays a role.
Defining Specifications
3GPP specifications that define or reference TO, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TR 21.905 vj00 | 3GPP Technical Terms and Definitions | Rel-19 |
| TS 23.018 vj00 | Basic call handling in 3GPP CS domain | Rel-19 |
| TS 32.321 vj00 | Test Management IRP: Requirements | Rel-19 |
| TS 32.322 vj00 | Test Management IRP Information Service | Rel-19 |
| TS 32.326 vj00 | Test Management IRP Solution Set Definitions | Rel-19 |
| TS 32.327 v1900 | Test Management IRP SOAP Solution Set | Rel-9 |
| TS 36.766 vf00 | LTE BS Interference Cancellation Receiver Study | Rel-15 |
| TS 38.213 vj10 | NR Physical Layer Control Procedures | Rel-19 |
| TR 38.812 vg00 | Study on NOMA for NR | Rel-16 |