OAM

Operations, Administration, and Maintenance

Management →
Introduced in Rel-8 Also in: Core Network, Services, Radio Access Network, Security

OAM is the set of processes, activities, tools, and standards used to operate, administer, and maintain a telecommunications network to ensure its reliability, performance, and service provisioning.

Category
Management
Introduced
Rel-8
Where
Management
Also touches
4 segments
Specifications
53 specs
OAM Description Purpose Detected Changes Specifications

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.

Detected Changes Across Releases

from 3GPP Change Requests

Specific changes extracted from the „Change history“ tables of 3GPP specifications (8 CRs across 4 releases). Complements the general historical overview above with the evidence-based evolution of this function.

Studied in Rel-8, normative work from Rel-16.

Rel-16 2 changes

In Release 16, the OAM function was extended to formally include requirements for managing third-party API providers. Furthermore, the concept of OAM itself acting as a service consumer was introduced, defining its role in consuming services from other network functions.

  • OAM requirements for 3rd party API providers TS 23.222CR0017
  • OAM as service consumer TS 29.520CR0047
Rel-17 2 changes

In Release 17, the OAM function for the 5G Media Streaming (5GMS) feature set saw essential maintenance updates. This work, conducted within the 5GMS Phase 3 (5GMS3) and TEI17 work item, focused on necessary corrections and refinements to ensure stability. The changes were general upkeep for the existing OAM framework rather than introducing major new procedures or interfaces.

  • [5GMS3, TEI17] Essential maintenance TS 26.512CR0037
  • [5GMS3, TEI17] Essential maintenance TS 26.512CR0054
Rel-18 3 changes

In Release 18, OAM enhancements included the introduction of preparation and maintenance procedures to support Federated Learning within the 5G Core network. Furthermore, corrections were made to existing OAM data collection procedures and to the OAM-based IP address allocation process for Integrated Access and Backhaul nodes.

  • Preparation and Maintenance Procedures for Federated Learning in 5GC TS 29.552CR0062
  • Corrections to data collection from OAM procedures TS 29.552CR0084
  • Correction on IP address allocation for IAB via OAM TS 38.401CR0345
Rel-19 1 change

In Release 19, a key enhancement for OAM was its integration into the policy framework. Specifically, OAM information was newly defined as a formal input for policy decisions. This allows network management data to directly influence and automate operational policies.

  • Adding the OAM information as one input of policy decision TS 29.507CR0356

Explore further

Broader topics and technologies where OAM plays a role.

Defining Specifications

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

SpecificationTitleRelease
TS 23.203 vj20 Policy and charging control architecture Rel-19
TS 23.222 vj80 Common API Framework for 3GPP Northbound APIs Rel-19
TS 23.435 vj30 Network Slice Capability Exposure Procedures Rel-19
TS 23.436 vk00 ADAEnabler Functional Architecture and Information Flows Rel-20
TS 23.482 vk00 AIML Enablement Service Architecture Rel-20
TS 23.503 vk00 5G Policy and Charging Control Framework Rel-20
TS 23.700 vk00 XR Services Application Enablement Layer Rel-20
TS 23.791 vg20 NWDAF Data Collection & Analytics Framework Rel-16
TS 25.703 vc00 HNB Emergency Warning Area Study for UTRA Rel-12
TS 26.501 vj30 5G Media Streaming (5GMS) Architecture Rel-19
TS 26.510 vj10 Media Delivery APIs for 5GMS and RTC Systems Rel-19
TS 26.512 vj10 5G Media Streaming Protocols & APIs Rel-19
TS 26.804 vj10 5G Media Streaming Extensions Study Rel-19
TR 26.942 vj00 Study on Media Energy Consumption Exposure & Evaluation Rel-19
TS 28.627 vj00 SON Policy NRM IRP: Requirements Rel-19
TS 28.628 vj00 SON Policy NRM IRP Information Service Rel-19
TS 28.861 vg00 SON for 5G Networks Management Rel-16
TS 28.879 vj10 OAM for Service Management Exposure Study Rel-19
TS 29.333 vj00 MRFC-MRFP Mp Interface Protocol Rel-19
TS 29.412 v1810 Trunking Gateway Control Procedures Rel-8
TS 29.507 vj40 5G Access & Mobility Policy Control Service Rel-19
TS 29.520 vj40 5G Network Data Analytics Services Stage 3 Rel-19
TS 29.523 vj20 5G Policy Control Event Exposure Service Rel-19
TS 29.535 vj40 5G AKMA Anchor Services Stage 3 Protocol Rel-19
TS 29.552 vj40 5G Network Data Analytics Signalling Flows Rel-19
TR 29.835 vh10 Study on Port Allocation for 3GPP Interfaces Rel-17
TS 32.140 vj00 Subscription Management (SuM) requirements Rel-19
TS 32.141 vj00 Subscription Management (SuM) Architecture Rel-19
TS 32.521 vb10 SON Policy NRM IRP Requirements Rel-11
TS 32.522 vb70 SON Policy NRM IRP Information Service Rel-11
TS 32.541 vj00 SON Self-Healing Concepts and Requirements Rel-19
TS 32.571 vj00 HNB/HeNB Type 2 Interface Management Concepts Rel-19
TS 32.582 vj00 HNB Management Information Model for Type 1 Interface Rel-19
TS 32.592 vj00 HeNB OAM&P Information Model Rel-19
TS 32.593 vj00 HeNB OAM&P Procedure Flows for Type 1 Interface Rel-19
TS 32.594 vj00 Data definitions for HeNB to HeMS Type 1 interface Rel-19
TS 32.823 v1900 Self-Organizing Networks Self-Healing Study Rel-9
TS 32.826 va00 Study on Energy Savings Management in LTE/SAE Networks Rel-10
TS 32.827 va10 UE Management over Itf-N for MDT/SON Rel-10
TS 32.834 vb00 Inter-RAT Energy Saving Management Study Rel-11
TS 32.851 vc20 Network Sharing OAM Requirements Rel-12
TS 32.865 vf00 OAM Aspects of SON for AAS-Based Deployments Rel-15
TS 33.794 vj10 Study on Zero Trust Security Enablers for 5G Rel-19
TR 33.866 vh00 Security aspects of Network Automation enablers for 5GS Rel-17
TR 33.876 vi01 Technical Report on Certificate Management Rel-18
TR 33.916 vj00 3GPP Security Assurance Methodology (SECAM) Rel-19
TR 33.926 vk00 Security Assurance Specification (SCAS) Rel-20
TR 33.927 vj00 Security Assurance for Virtualized Network Products Rel-19
TS 36.887 vc00 Energy Saving Enhancement for E-UTRAN Study Rel-12
TR 36.927 vj00 Network Energy Saving for E-UTRAN Rel-19
TS 37.320 vj00 Minimization of Drive Tests (MDT) Overview Rel-19
TS 37.834 vc00 WLAN/3GPP Radio Interworking Study Rel-12
TS 38.401 vj10 NG-RAN Architecture Specification Rel-19