Description
Operations, Administration, and Maintenance (OAM) is a comprehensive framework for managing telecommunications networks, defined across numerous 3GPP specifications. It is not a single protocol but a collection of functions, interfaces, and procedures. The architecture is typically based on the Telecommunications Management Network (TMN) model and its evolution into the FCAPS model (Fault, Configuration, Accounting, Performance, Security). OAM functions are distributed across network elements (NEs), element management systems (EMSs), and network management systems (NMSs), communicating via standardized interfaces like Itf-N. Key components include the Network Resource Model (NRM), which provides an information framework for managed objects, and the Performance Management (PM) and Fault Management (FM) data collection and reporting mechanisms. Its role is to ensure the network operates efficiently, meets service level agreements (SLAs), and can be updated and repaired with minimal disruption. This involves continuous monitoring of Key Performance Indicators (KPIs), automated alarm generation and correlation for fault isolation, software and configuration management for network updates, and security management for access control and audit trails. In modern networks, OAM principles are extended to virtualized and cloud-native environments, managing virtualized network functions (VNFs) and cloud infrastructure alongside physical network functions (PNFs).
Purpose & Motivation
OAM exists to address the fundamental challenge of managing increasingly complex, heterogeneous, and large-scale telecommunications networks. Without standardized OAM, network operators would face immense difficulties in provisioning services, diagnosing faults, ensuring quality of service, and performing routine maintenance, leading to high operational costs and poor customer experience. Historically, proprietary management systems created vendor lock-in and interoperability issues. 3GPP standardized OAM to enable multi-vendor interoperability, automate operational tasks, and provide a unified view of the network. It solves problems like manual, error-prone configuration; slow fault detection and resolution; and lack of holistic performance visibility. The creation of comprehensive OAM standards was motivated by the need for operational efficiency, service assurance, and the ability to introduce new technologies (like 5G and network slicing) in a manageable way. It addresses the limitations of ad-hoc and non-standardized management approaches that were unsustainable for global, scalable mobile networks.
Key Features
- Standardized Fault Management (FM) for alarm surveillance, fault localization, and correction
- Comprehensive Performance Management (PM) for collection and analysis of Key Performance Indicators (KPIs)
- Configuration Management for software handling, inventory, and provisioning of network resources
- Accounting Management for tracking resource usage for billing and cost allocation
- Security Management functions including access control, security audit trails, and integrity checking
- Support for management of both traditional physical network functions and modern virtualized/cloud-native network functions
Evolution Across Releases
Introduced foundational OAM principles for the Evolved Packet System (EPS), including management architecture for the E-UTRAN and EPC. Established key performance measurement definitions and fault management procedures for the new LTE network, laying the groundwork for subsequent enhancements.
Defining Specifications
| Specification | Title |
|---|---|
| TS 23.203 | 3GPP TS 23.203 |
| TS 23.222 | 3GPP TS 23.222 |
| TS 23.435 | 3GPP TS 23.435 |
| TS 23.436 | 3GPP TS 23.436 |
| TS 23.482 | 3GPP TS 23.482 |
| TS 23.503 | 3GPP TS 23.503 |
| TS 23.700 | 3GPP TS 23.700 |
| TS 23.791 | 3GPP TS 23.791 |
| TS 25.703 | 3GPP TS 25.703 |
| TS 26.501 | 3GPP TS 26.501 |
| TS 26.510 | 3GPP TS 26.510 |
| TS 26.512 | 3GPP TS 26.512 |
| TS 26.804 | 3GPP TS 26.804 |
| TS 26.942 | 3GPP TS 26.942 |
| TS 28.627 | 3GPP TS 28.627 |
| TS 28.628 | 3GPP TS 28.628 |
| TS 28.861 | 3GPP TS 28.861 |
| TS 28.879 | 3GPP TS 28.879 |
| TS 29.333 | 3GPP TS 29.333 |
| TS 29.412 | 3GPP TS 29.412 |
| TS 29.507 | 3GPP TS 29.507 |
| TS 29.520 | 3GPP TS 29.520 |
| TS 29.523 | 3GPP TS 29.523 |
| TS 29.535 | 3GPP TS 29.535 |
| TS 29.552 | 3GPP TS 29.552 |
| TS 29.835 | 3GPP TS 29.835 |
| TS 32.140 | 3GPP TR 32.140 |
| TS 32.141 | 3GPP TR 32.141 |
| TS 32.521 | 3GPP TR 32.521 |
| TS 32.522 | 3GPP TR 32.522 |
| TS 32.541 | 3GPP TR 32.541 |
| TS 32.571 | 3GPP TR 32.571 |
| TS 32.582 | 3GPP TR 32.582 |
| TS 32.592 | 3GPP TR 32.592 |
| TS 32.593 | 3GPP TR 32.593 |
| TS 32.594 | 3GPP TR 32.594 |
| TS 32.823 | 3GPP TR 32.823 |
| TS 32.826 | 3GPP TR 32.826 |
| TS 32.827 | 3GPP TR 32.827 |
| TS 32.834 | 3GPP TR 32.834 |
| TS 32.851 | 3GPP TR 32.851 |
| TS 32.865 | 3GPP TR 32.865 |
| TS 33.794 | 3GPP TR 33.794 |
| TS 33.866 | 3GPP TR 33.866 |
| TS 33.876 | 3GPP TR 33.876 |
| TS 33.916 | 3GPP TR 33.916 |
| TS 33.926 | 3GPP TR 33.926 |
| TS 33.927 | 3GPP TR 33.927 |
| TS 36.887 | 3GPP TR 36.887 |
| TS 36.927 | 3GPP TR 36.927 |
| TS 37.320 | 3GPP TR 37.320 |
| TS 37.834 | 3GPP TR 37.834 |
| TS 38.401 | 3GPP TR 38.401 |