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

Glossary term · Management

OAM

Operations, Administration, and Maintenance

Management →

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.

Introduced
Rel-8
Where
Management
Specifications
53 specs
Also in
Core Network, Services, Radio Access Network, Security
OAM Description Purpose What changed Neighbours 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.

What changed in its specifications

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

TS 23.203Rel-16 → Rel-17

NB-IoT/eMTC support for Non-Terrestrial Networks: adds QCI characteristic for satellite access, note on GEO/LEO delays, and PCRF policy control for satellite PDN connections.

Full comparison in TS 23.203 →
TS 23.222Rel-18 → Rel-19

Rel-19 adds CAPIF Phase 3 procedures for unpublishing service APIs between interconnected core functions, revoking API invoker and resource owner authorization, open discovery of service APIs, and UE-hosted API invoker access to resources owned by other UEs.

Full comparison in TS 23.222 →

Release Timeline

Detected Changes Across Releases

from 3GPP Change Requests

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

Rel-16 2 changes
  • OAM requirements for 3rd party API providers TS 23.222CR0017
  • OAM as service consumer TS 29.520CR0047
Rel-18 2 changes
  • 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
  • Adding the OAM information as one input of policy decision TS 29.507CR0356

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 vk10 Policy and Charging Control Architecture Rel-20 read
TS 23.222 vk10 Common API Framework (CAPIF) Rel-20 read
TS 23.435 vk00 Network Slice Capability Enablement (NSCE) Architecture Rel-20 read
TS 23.436 vk20 Application Data Analytics Enablement Rel-20 read
TS 23.482 vk30 AI/ML Enablement for Verticals Rel-20 read
TS 23.503 vk30 5G Policy and Charging Control Framework Rel-20 read
TS 23.700 vk10 AI/ML Application Layer Support Phase 2 Rel-20 read
TS 23.791 vg20 NWDAF Data Collection & Analytics Framework Rel-16 read
TS 25.703 vc00 HNB Emergency Warning Area Study for UTRA Rel-12 read
TS 26.501 vk00 5G Media Streaming Architecture Rel-20 read
TS 26.510 vj20 5G Media Streaming and Real-Time Communication APIs Rel-19 read
TS 26.512 vj30 5G Media Streaming Protocols and APIs Rel-19 read
TS 26.804 vk10 5G Media Delivery Architecture Extensions Rel-20 read
TS 26.942 vk00 Sustainable Media Metrics and Architectural Impacts for 5G Rel-20 read
TS 28.627 vj00 SON Policy NRM IRP: Requirements Rel-19 read
TS 28.628 vj00 SON Policy NRM IRP Information Service Rel-19 read
TS 28.861 vg00 SON for 5G Networks Management Rel-16 read
TS 28.879 vj10 OAM for Service Management Exposure Study Rel-19 read
TS 29.333 vj00 MRFC-MRFP Mp Interface Protocol Rel-19 read
TS 29.412 v810 Control Procedures for Trunk Gateways in NGN Networks Rel-8 read
TS 29.507 vk10 Access and Mobility Policy Control Rel-20 read
TS 29.520 vk10 5G NWDAF Services Rel-20 read
TS 29.523 vk10 Policy Control Event Exposure Service Rel-20 read
TS 29.535 vk10 AAnF Service Based Interface Rel-20 read
TS 29.552 vk10 5G Network Data Analytics Procedures Rel-20 read
TR 29.835 vh10 Study on Port Allocation for 3GPP Interfaces Rel-17 read
TS 32.140 vj00 Subscription Management (SuM) requirements Rel-19 read
TS 32.141 vj00 Subscription Management (SuM) Architecture Rel-19 read
TS 32.521 vb10 SON Policy NRM IRP Requirements Rel-11 read
TS 32.522 vb70 SON Policy NRM IRP Information Service Rel-11 read
TS 32.541 vj00 SON Self-Healing Concepts and Requirements Rel-19 read
TS 32.571 vj00 HNB/HeNB Type 2 Interface Management Concepts Rel-19 read
TS 32.582 vj00 HNB Management Information Model for Type 1 Interface Rel-19 read
TS 32.592 vj00 HeNB OAM&P Information Model Rel-19 read
TS 32.593 vj00 HeNB OAM&P Procedure Flows for Type 1 Interface Rel-19 read
TS 32.594 vj00 Data definitions for HeNB to HeMS Type 1 interface Rel-19 read
TS 32.823 v900 Self-Healing in SON Study Rel-9 read
TS 32.826 va00 Study on Energy Savings Management in LTE/SAE Networks Rel-10 read
TS 32.827 va10 UE Management over Itf-N for MDT/SON Rel-10 read
TS 32.834 vb00 Inter-RAT Energy Saving Management Study Rel-11 read
TS 32.851 vc20 Network Sharing OAM Requirements Rel-12 read
TS 32.865 vf00 OAM Aspects of SON for AAS-Based Deployments Rel-15 read
TS 33.794 vj10 Study on Zero Trust Security Enablers for 5G Rel-19 read
TR 33.866 vh00 Security aspects of Network Automation enablers for 5GS Rel-17 read
TR 33.876 vi01 Technical Report on Certificate Management Rel-18 read
TR 33.916 vk00 Security Assurance Methodology (SECAM) Evaluation Process Rel-20 read
TR 33.926 vk20 Generic Network Product Security Assurance Rel-20 read
TR 33.927 vj00 Security Assurance for Virtualized Network Products Rel-19 read
TS 36.887 vc00 Energy Saving Enhancement for E-UTRAN Study Rel-12 read
TR 36.927 vj00 Network Energy Saving for E-UTRAN Rel-19 read
TS 37.320 vj40 MDT Overall Description (Stage 2) Rel-19 read
TS 37.834 vc00 WLAN/3GPP Radio Interworking Study Rel-12 read
TS 38.401 vj30 NG-RAN Architecture Description Rel-19 read