Since March 2025, O-RAN ALLIANCE (O-RAN) Work Groups and Focus Groups published 60 technical documents, bringing the total to 134 titles in current version and 830 documents overall. Four documents represent new titles.
O-RAN specifications set the foundation for open, intelligent, virtualized, and interoperable Radio Access Networks (RAN). They describe different functions and interfaces of the O-RAN Architecture (Figure 1). O-RAN Work Groups (WG) and Focus Groups (FG), each covering different part of the solution, keep strong momentum in the specification development.
All O-RAN technical documents are available on our website at www.o-ran.org/specifications.
New specification of general aspects and principles for the interface between DUs (D2 interface).
C-plane – fundamental control signaling (D2 setup, UE add./mod./del., etc.) are specified.
U-plane – procedure on transferring user data between O-DUs are specified.
Synchronization/Transport – specified that existing WG9 requirements and specifications can fulfill the requirement for D2.
This initial release introduces analysis and service-level recommendations for detection and avoidance of A1 policy conflict.
This technical report contains considerations and recommendations related to partial enforcement of A1 policies.
This technical report (TR) contains a study of continuous security monitoring which was spun off from the zero trust architecture study item.
This first version of the TR focusses on topics towards the agreed scope which encompasses the study of the definition of security related data to be monitored and collected from O-RAN architecture elements and non O-RAN architecture elements that contribute to monitoring various security related attacks.
This version contains key issues for various security threats which ascertain whether we need to collect security related data or not. The solutions in this version of the document further cover a few key issues that dictate which data needs to be potentially defined for collection. The recommendations at this point in time are a place holder to be extended in later versions towards normative requirements and controls.
The SMO Intents-driven Management study (TR) introduces the exposure of the SMO services in a simplified form, RAN management via intents, to address the wide range of their applicability. This includes the various interactions within SMO management loops (closed, open), serving as a simplified method for management exposure of RAN services both externally and internally to other management or business systems. This version includes a discussion and use cases regarding conflict in intent requirements and resulting conflicting actions. Furthermore, editorial updates and text improvements were included in the document.
The O-RAN Architecture Description document specifies the overall architecture of O-RAN. It describes all O-RAN architecture elements and relevant interfaces that connect them. This version adds a new D2 interface - an inter-O-DU interface for carrier aggregation - to the O-RAN architecture. It elucidates the SMOS (SMO Services) Communication and R1 services. Finally, it updates the format to align with the ODR (O-RAN Document Drafting Rules).
This document describes O-RAN slicing related use cases, requirements and architecture. Along with requirements and a reference slicing architecture, slicing related impact to O-RAN functions and interfaces is also captured. This version of O-RAN Slicing Architecture Technical Specification includes minor updates to address ETSI PAS comments and editorial corrections.
This document describes potential O-RAN use cases at a very high level, emphasizing how the use case is enabled by the O-RAN architecture along with basic input data expectations and resulting actions. This version of O-RAN Use Cases Analysis Report includes updates to a use case (“Interference Optimization”), 3GPP Release-18 upgrades, ETSI PAS resolutions, and some editorial corrections.
This document describes selected O-RAN use cases in further details to facilitate relevant O-RAN Work Groups to define requirements for associated O-RAN functions and interfaces. This version of O-RAN Use Cases Detailed Specification Report includes new sub use case additions to Shared O-RU use case, 3GPP Release-18 upgrades, ETSI PAS resolutions, and some editorial corrections.
This document specifies the general aspects and principles of the A1 interface. This version brings updated A1 ML related procedures.
This document describes use cases for the O-RAN A1 interface. This version brings use case for AI/ML model training job status with Non-RT RIC as A1-ML Consumer.
This specification defines the data types for A1 Policies and A1 Enrichment Information in a reusable and extensible way. It allows new policy types to be created independently of the generic application protocol parts. This version brings editorial enhancement.
The O-RAN R1GAP Specification summarizes the R1 interface specification objectives and specifies the principles and procedures related to the O-RAN R1 interface. The Specification is updated the data subscription and data request to include the data request/subscription status and deprecated Heartbeat service as part of Service management and exposure service.
This document describes use cases and requirements for the O-RAN R1 interface. The Specification is updated the new use cases related to AI/ML model training capability registration and data job status.
This document describes transport protocols for the O-RAN R1 interface services. Migrated the specification to new TS template and updated the Kafka Security requirements.
This document contains a realization for the procedures identified in O-RAN R1 interface: General Aspects and Principles. The specification is updated with the Bootstrap API, RAN OAM CM API’s, RAN OAM FM API’s, Added new API’s for Configuration schema information API, AI/ML Model deployment API, AI/Ml model retrieve API, Updates to AI/ML model registration API, AI/Ml model discovery API and AI/ML model training API.
This document specifies the Type Definitions for R1 Services. It is part of a TS-family covering the R1 interface specifications. The specification is updated by adding an example of RAN OAM Trace Metrics configuration.
This document specifies test cases for conformance testing and interoperability testing of the rApps and R1 services over R1 interface. The Specification is published with Conformance test of rApp and Non-RT RIC as DUT for DME, A1 policy management and Service management and exposure.
This initial release introduces analysis and service-level recommendations for detection and avoidance of A1 policy conflict.
This document describes O-RAN WG2 Non-RT RIC use cases in detail including the required datasets, the flows, and the interactions within and outside of Non-RT RIC with other O-RAN components. As a result of the use case analysis, this specification captures the requirements imposed by these use cases on the Non-RT RIC architecture, A1 and R1 interfaces as well. This version of the specification includes addition of a new Energy Savings sub use case (time domain cell DTX/DRX optimization), 3GPP Release 18 upgrades and editorial corrections
This technical report contains considerations and recommendations related to partial enforcement of A1 policies.
This document provides the technical specification for the Non-Real-Time RAN Intelligent Controller (Non-RT RIC) architecture.
This document specifies the E2 Service Model (E2SM) for UE and Cell level services over E2 interface. This version of E2SM-RC includes support for Uplink Power Control feature.
This document specifies the E2 Service Model (E2SM) for exposing services related to node and cell-level configuration and control over the E2 interface. This version of the E2SM-CCC specification introduces the O-PRBBlankingPolicy for cell-level PRB Blanking configuration and control, along with corrections to the JSON Schema.
This document specifies the control plane, user plane and synchronization plane protocols used over the fronthaul interface. The summary of updates for this version is below:
This specification defines the Management Plane for the O-RAN Open Fronthaul based on the selected lower-layer split point as defined within the Open Fronthaul Control Plane, User Plane and Synchronization Plane specification. The summary of updates for this version is below.
This document defines tests that validate the conformance to the protocols defined for the Lower Layer Split Option 7.2x interface between the O-RU and the O-DU. This version brings:
This document specifies the interoperability testing (IOT) for O-DU and O-RU from different vendors connected using the O-RAN fronthaul (FH) interface. This version brings:
The scope of C-Plane profile spec is to further clarify (i.e. profile) for each RAN node the expected behavior (still within the scope of the 3GPP specifications). E.g., Usage of IEs for each use case, general behavior of each node, etc. C-Plane profile spec contains profiles of X2/F1/Xn C-Plane procedure for EN-DC use cases, NR-SA use cases and NR-DC use cases. This version brings:
The scope of WG5 IOT spec is to specify interoperability tests for RAN Node from different vendors implemented in accordance to the WG5 C-plane and U-plane profiles in the specification WG5.C.1. and WG5.U.0, respectively. 11 new test cases for C-plane profile are captured in this version.
New specification to specify general aspects and principles for the interface between DUs (D2 interface).
C-plane – fundamental control signaling (D2 setup, UE add./mod./del., etc.) are specified.
U-plane – procedure on transferring user data between O-DUs are specified.
Synchronization/Transport – specified that existing WG9 requirements and specifications can fulfill the requirement for D2.
This specification defines an O-RAN Application Services Descriptor (ASD) for potential use in application package. This version of the document adds a TOSCA based data model specification of the ASD. In addition it introduces several changes in the information model: it introduces a new ExecutableSwImage information element, semantics enhancement to the different version related properties in the ASD, semantic additions in the resourceMapping property and other smaller enhancements and corrections.
This document specifies a test specification for test and validation of the O-Cloud interfaces/APIs. This revision of the O-Cloud Interface Conformance Test Specification addresses critical corrections to ensure test cases rigorously validate O-Cloud interface compliance with defined API specifications. Without these updates, certain tests may produce false negatives even when applied to fully compliant O-Cloud implementations, undermining the accuracy and reliability of certification outcomes.
This TS specifies the O-RAN O-Cloud’s DMS interface protocol and data model based on the ETSI NFV solutions. This version of the document updates the versions of the three ETSI NFV SOL APIs for the management of NF Deployments profiled as “NF Deployment lifecycle service”, “NF Deployment fault service”, and “NF Deployment performance service” to the latest API versions published in the ETSI NFV Release 5 referenced documentation (v5.1.1). This version also includes a new example end-to-end procedure about healing to recover from failure of an NF Deployment (clause A.3.1) and additional description (see clause 2.5.1 and 3.2.6.3.2) to clarify the relation of the present O2DMS profile with regards to O-Cloud Node Clusters, resource groups and tenancy and the use of underlying resource managers for VM and container-based deployments.
The O-Cloud Information Model provides the logical model of information elements and their relationships.
This document provides O-Cloud IoT specification, and includes definition of the interoperability testing methodology and a set of tests for the O-Cloud Notification API. This is a minor release to update the references for WG6 Specifications, editorial changes and Change history table updates.
This specification outlines the deployment management services of the O2dms interface profile based on Kubernetes Native API for containerized NFs. This version of the document updates the supported use cases (instantiate, terminate, and heal) to align them to the NF Deployment level use cases.
This specification defines O-RAN O-Cloud IMS interface functions and protocols for the O-RAN O2 interface. This version of the document introduces support for the Provisioning API, and adds further PM related and probable causes support.
This document introduces different use cases for O-RAN orchestration of virtualized RAN and the interfaces used for management and orchestration, in particular the O1 interface between the service management and orchestration framework and the RAN managed functions and the O2 interface between the service management and orchestration framework and the O-Cloud Infrastructure Management Services/Deployment Management Services that controls resource assignment for Virtualized Network Functions. This version incorporates a number of corrections of terminologies, use case names and diagrams, and a new use case for Delete O-Cloud Node Cluster created using O-Cloud template.
This specification defines O-RAN O-Cloud hardware accelerator interface functions and protocols for the O-RAN AAL interface. This release added clarification on fault notifications from the AAL implementation to AAL Applications.
This document specifies how to accelerate the High-PHY functionality of an O-DU where the High-PHY Acceleration Function (AF) is hosted on an AAL-LPU that is assigned to the AAL Application that is part of the O-DU. This document also specifies a set of AAL Profiles and procedures for utilizing the AALI Common Management (AALI-C-Mgmt) and Application (AALI-C-App) interfaces to convey the information elements specified by the AAL Profiles. This version of the document introduces addition of weightForAverageFO parameter for channel estimation in PUSCH/PUCCH and support of fault notification in PDSCH, PDCCH and PUSCH.
This specification focuses on the Common API related to common aspects of accelerator abstraction from an administration and AAL Application perspective. This version of the document introduces requirements for fault notification and handling of those notifications.
This is the O-RAN WG7 Hardware Reference Design Specification for Indoor Picocell FR1 with Split Architecture Option 7-2 (V2). It describes one white box hardware reference design example for indoor deployments. In this version, section 2.3 is modified with an addition of “2.3.3 O-RU7-2 Hardware Components for SDR based Design”
This specification defines the O-CU and O-DU software architecture, functional blocks, and API definitions.
This specification defines interoperability test cases for O-CU and O-DU.
This document specifies management services for the O-RAN O1 interface and includes requirements, notifications and protocols. Summary of the changes since the previous version:
The O-RAN OAM Architecture identifies management services, functions and interfaces supported in O-RAN, including the interworking between SMO and O-RAN O-Cloud components. Requirements are derived from end-to-end OAM use cases, including the initial provisioning of O-RAN service across VNFs and PNFs and the collection of measurement data. Summary of the changes since the previous version:
The O-RAN Information Model and Data Models document specifies the Information Model and the Data Models that are foundational for O-RAN’s model-driven architecture and for the functions carried out over O-RAN interfaces. Summary of the changes since the previous version:
The present document specifies the Information Model and the Data Model for Network Resource Model (NRM) that are foundational for functions carried out over the O-RAN O1 interface. This version brings:
The present document specifies the O-RAN Performance Measurements (PMeas) for 5G networks that may be supported on the O1 Interface. This version brings:
This document specifies the Information Model used to support TE&IV services within the SMO. The TE&IV Information Models described in this document are structured using the concept of Namespaces. In addition, relevant sections in this document include information imported from existing standards and industry work that serve as a basis for O-RAN TE&IV. Summary of the changes from the previous version:
This document specifies the TE&IV Data Models used to support TE&IV services within the SMO.
Summary of changes from the previous version:
This document specifies the TE&IV APIs used to support TE&IV services within the SMO. Summary of the changes from the previous version:
The Fronthaul CUS-Plane Security Technical Report examines the security aspects of the CUS-Plane on the Open Fronthaul interface between the O-DU and O-RU. It identifies critical assets, key issues, threats, and potential risks, and proposes security requirements and solutions to effectively secure CUS-Plane traffic.
The version 04.00 of the technical report includes updates to three key management solutions for MACsec. Furthermore, it provides clarifications on the applicability of IEEE 802.1AE standards to various MACsec deployment scenarios. The report also updates potential security requirements on the S-Plane, and includes updates to the MACsec solution proposal using EDE-CC.
OAuth2.0 version 5.0 consists of 35 threats and vulnerabilities related to OAuth 2.0. Identified new security controls and provided new solutions on split the administration of the roles and permissions between the authorization server and resource server.
This Technical Specification contains security requirements and controls for O-RAN architecture element, O-RAN defined interfaces as well as transversal security requirements and controls for the O-RAN architecture.
The version 12.00 of the technical specification includes key updates such as: incorporation of ETSI and BSI corrections; new security requirements for AI/ML, SME, and SMOS communication; and MACsec for Shared O-RU. C-Plane and U-Plane authentication/authorization are aligned, MACsec EDE-CC requirements for TNE are clarified, and O-Cloud platform security and application package validation are further updated. The specification also includes updated O1/O2 security with refined O1 and O2 terms, new annexes mapping security requirements and controls, enhancements to Y1, Near-RT RIC, A1 security, SBOM, and certificate management, and the addition of eCPRI to common protocols, definitions, and Mapping Table D.2.
This technical report studies the applicability of a Zero Trust Architecture (ZTA) to the O-RAN Architecture. It identifies assets and security controls in pursuit of a ZTA while considering those already existing in WG11 specifications. The third version of the ZTA technical report completes the initial gap analysis comparing current security requirements and controls of O-RAN assets to the ZTA security guidelines derived from CISA’s Zero Trust Maturity Model. In this version, the gap analyses for SMO and Non-RT RIC were added along with analyses of transversal functions managed at a system-wide level and cross cutting capabilities.
This technical report considers security of O-RAN applications during their lifecycle phases of development, onboarding, and operation. O-RAN applications in the scope of the technical report include VNFs/CNFs as well as software for physical network functions. The report presents key issues developed from identified threats and proposes solutions in order to derive security requirements for technical specifications. The fourth version of the technical report updates key issues and solutions based on updated security threats, requirements, and controls.
This document provides security protocol specifications for an O-RAN compliant implementation. Version 12 incorporates ETSI corrections, and adds cryptographic operations related to random number generation. Additionally, a number of editorial corrections have been done for clarity, consistency and ODR conformance.
The O-RAN Security Threat Modeling and Risk Assessment Technical Report (TR) identifies critical assets and outlines potential security threats to the O-RAN system, along with guiding security principles to mitigate those risks. It also evaluates the likelihood and potential impact of each identified threat on the overall system.
The TR has now been updated to Version 6, introducing several significant enhancements over Version 5. This new version emphasizes alignment with ETSI comments, the addition of OAuth 2.0-related threats, and the refinement of multiple threat entries—including common threats and those related to Non-RT RIC, xApp, O-RU, physical, radio, and the E2 and Y1 interfaces—to ensure improved compliance with STRIDE. Additionally, the risk assessment matrix has been expanded to cover a broader range of threats.
This TR contains a study of continuous security monitoring which was spun off from the zero trust architecture study item.
This first version of the TR focusses on topics towards the agreed scope which encompasses the study of the definition of security related data to be monitored and collected from O-RAN architecture elements and non O-RAN architecture elements that contribute to monitoring various security related attacks.
This version contains key issues for various security threats which ascertain whether we need to collect security related data or not. The solutions in this version of the document further cover a few key issues that dictate which data needs to be potentially defined for collection. The recommendations at this point in time are a place holder to be extended in later versions towards normative requirements and controls.
These specifications validate the proper implementation of security requirements and protocols, emulate security attacks, and validate the effectiveness of security mitigation methods. Version 10 adds 2 security test cases for OAuth 2.0 in clause 6 as a result of splitting original combined test case. Test case for Unauthorised Rollback Prevention was also added to clause 18 about O-Cloud. Contents of DoS timeTransmitter LLS C4 test case was removed in clause 11. Many smaller editorial changes were incorporated in order to have same format of all test cases. Changes affected clauses 6, 7, 8, 11, 12, 13, 15, 16, 17, 18, 19, 20, 24 and 25.
This test specification is focused on validating the end-to-end system functionality, performance, and key features of the O-RAN system as a black box. The changes from previous version:
This document describes the certification and badging processes and associated detailed technical procedures for the Open Testing and Integration Centres (OTICs) and various other testing entities. Changes from previous version:
