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 specifications download portal.
Seven documents represent new titles:
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 slice subnet management procedures and some further editorial modifications for O-RAN ODR compliancy and ETSI PAS readiness.
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 additions to a use case (“Interference Optimization”) and some further editorial modifications for O-RAN ODR compliancy and ETSI PAS readiness.
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 and some further editorial modifications for O-RAN ODR compliancy and ETSI PAS readiness.
The communication and computing integrated networks study (TR) presents the use cases for integrated communication and computing in O-RAN. The potential solutions are studied for the identified use cases and key issues. The technical report also identifies the potential architecture impacts and requirements for support the integrated communication and computing in O-RAN.
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 further clarifies the “intent definition” and “intent removal” procedures and expands on the concept of “intent negotiation”.
SA-MVD TR discusses the importance of spectrum aggregation across different bands for enhanced user experience and efficient use of frequency resources. It highlights various deployment scenarios and evaluates different solutions for spectrum aggregation in multi-vendor RAN deployments, including Intra O-DU CA, Inter O-DU CA, and Dual Connectivity. The document also provides considerations for spectrum combinations, UE requirements, and solution evaluation criteria. Additionally, it outlines the requirements and architecture for a newly proposed Inter O-DU CA solution.
Decoupled SMO architecture study (TR) analyzed and identified the set of capabilities that the SMO has to offer and structured them in SMO Services (SMOSs) in a Service Based Architecture approach. A set of SMO Services have been defined and the analysis pointed towards next normative steps to be pursued after the study. The Decoupled SMO architecture TR was initiated to address the original problem statements (per Introduction section in the TR) and hence enables SMO deployments that are suitable for brownfield, greenfield and bluefield scenarios. The objective of this Technical Report is to propose a decoupled SMO architecture to enable standardized interoperability in multi-vendor SMO deployments. This version shows minimal “anchored” SMOSs to support a Non-RT RIC.
This document specifies the general aspects and principles of the A1 interface. This version brings general aspects of A1 ML model management service.
This document describes use cases for the O-RAN A1 interface. This version updates specification designator to R004.
This document specifies the application protocol of the A1 interface. This version updates specification designator to R004.
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 segmentation of JSON schemas. Adding attributes to Slice SLA target and Network energy saving policy types.
This document specifies test cases for conformance testing and interoperability testing of the Non-RT RIC and the Near-RT RIC over the A1 interface. This version brings editorial enhancements.
This document describes the transport protocol of the O-RAN A1 interface. This version brings Editorial enhancement of references. This version updates specification designator to R004.
The O-RAN R1GAP Specification summarizes the R1 interface specification objectives and specifies the principles and procedures related to the O-RAN R1 interface. In this release focus on enhancing the production capability for a DME type and added query procedure for subscription data in DME. Added AI/ML model inference service to AI/ML workflow. Updated the Service subscription procedures to add the update procedure in alignment with 3GPP CAPIF specifications.
This document specifies the Type Definitions for R1 Services. It is part of a TS-family covering the R1 interface specifications. This release addresses data type refactoring by updating the specification from data type to DME type.
This release introduces the first version of the R1 Test specifications that includes the conformance testing for rApps and SMO/Non-RT RIC framework, included one test procedure for SME-service registration test case.
This document provides the technical specification for the Non-Real-Time RAN Intelligent Controller (Non-RT RIC) architecture. This version includes enhancements to AI/ML workflow services, updates of R1 interface and R1 termination description, and editorial changes to comply with O-RAN drafting rules.
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 includes editorial changes for O-RAN Drafting Rules (ODR) compliancy.
This document contains a realization for the procedures identified in O-RAN R1 interface: General Aspects and Principles. This Version includes initial API for Bootstrap in SME, AI/ML registration, AI/ML discovery, AI/ML training in AI/ML workflow functions, Data offer API in DME, Update the existing A1 policy API in A1 Policy management services, and update of Data registration , Data discovery, Data subscription API’s refactoring to DME type, Uplifting all the API’s to align with 29.501 Design guidelines
This document describes use cases and requirements for the O-RAN R1 interface. This Version includes the Use cases of AI/ML model inference for AI/ML model training capability registration, Query for data subscription, AI/ML model inference and update the SME subscription use case.
This document details the functional and non-functional requirements on Near-RT RIC and E2 interface from the O-RAN use cases under study in O-RAN WG3. This version of WG3 Use Case Requirements specification includes enhancements for QoS based resource optimization and network energy saving use cases, and text improvements for O-RAN Drafting Rule (ODR) alignment.
This document (E2GAP) together with (E2AP) describes the general architecture of Near-RT RIC and the main functions and procedures supported over the E2 interface, and the E2 application protocol of Near-RT RIC. This version of the specification contains corrections and improvements for ETSI PAS.
This document (E2AP) together with (E2GAP) describes the general architecture of Near-RT RIC and the main functions and procedures supported over the E2 interface, and the E2 application protocol of Near-RT RIC. This version of the specification contains corrections and improvements for ETSI PAS.
This document serves as the overall framework for the set of specialized E2SMs, each of which is dedicated to a specific RAN function. This document also includes the common information elements used across the specialized E2SMs. This version of the specification contains corrections and improvements for ETSI PAS.
The document specifies the general aspects and principles ((incl. services, supported information types, protocol structure) of the Y1 interface, which connects the Near-RT RIC with an authorized Y1 consumer. This version contains editorial enhancements for O-RAN Drafting Rule (ODR) alignment.
The document specifies the application protocols (API definition, solution sets) of the Y1 services. This version contains editorial enhancements for O-RAN Drafting Rule (ODR) alignment.
The document specifies data types that are applicable on the Y1 interface. This version introduces new attributes for RAN Analytics Information and editorial enhancements for O-RAN Drafting Rule (ODR) alignment.
The present document is the first version of the technical report (TR) on the Conflict Mitigation functions in the Near-RT RIC. The scope is restricted to E2-related conflict mitigation between xApps. To achieve conflict-free multi-xApp operation in the Near-RT RIC, the TR discusses key issues that cover various types of conflict situations. The key issues also discuss technical considerations and open issue that the solutions may address. The TR provides solutions to the key issues containing brief evaluations and technical recommendations for further normative work on the topic.
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 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 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 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 modification of existing functionality: M-Plane IOT test for hybrid mode start-up made conditional on O-DU capability.
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. Main updates compared to previous version:
The scope of the O-RAN Study on O-Cloud Energy Savings is to investigate, review and further specify WG6 O-Cloud energy saving related use cases, requirements, and potential impact on the O-Cloud O2 interface, for example O2ims and O2dms. This version is adding an architecture option to the Energy Savings TR. Updates the “Use Case - 4” to select a specific Mode on an O-Cloud Node Cluster and
WG6 O-Cloud-Energy-Efficiency-Measurements.
This document specifies a test specification for test and validation of the O-Cloud interfaces/APIs. This version adds 2 API test cases for ETSI NFV Profile to catch up the latest ETSI NFV Profile spec which is released in March.
This document introduces and examines different scenarios and use cases for O-RAN deployments of Network Functionality into Cloud Platforms, O-RAN Cloudified NFs and O-RAN Physical NFs. This version of the document adds O-Cloud Networking Terminology Alignment and clarification of descriptions of Fronthaul Gateway and Fronthaul Multiplexer.
This specification defines O-RAN O-Cloud functions and protocols for the O-RAN O2 interface. This version brings several updates:
This specification defines O-RAN O-Cloud IMS interface functions and protocols for the O-RAN O2 interface. This version brings several updates:
The O-Cloud Information Model provides the logical model of information elements and their relationships. The updates against previous version:
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 brings several updates:
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 4 referenced documentation. This version also includes small corrections and bug fixes, such as corrections of missing references and clarification notes not anymore applicable.
This specification defines O-RAN O-Cloud hardware accelerator interface functions and protocols for the O-RAN AAL interface. This version of the document introduces the inline acceleration architecture earlier in section 4.1, aligning with the introduction and description of general acceleration architectures. The scope of the HAM identifier within the O-Cloud was defined with the addition of a new requirement. Lastly the update includes various editorial changes including update or figure numbers and a fix in the architecture diagram figure 4.2.2-1 typo from "O1 dms" to "O1".
This specification focuses on the Common API related to common aspects of accelerator abstraction from an administration and AAL Application perspective. In this version of the O-RAN Acceleration Abstraction Layer Common API specification several modifications and corrections were made to existing APIs to align with other specifications, add missing information and interface needs.
This is an AAL acceleration profile to allow an AAL DU application to offload computation of precoding and beam-forming weights for MU-MIMO to an accelerator.
This version of the document deleted few unused references and updated the to the latest O-RAN template addressing the copyright and licensing issues.
This specification details the AAL specification consisting of the description of the interface, information models and requirements to implement an AALi, for the AAL_PUSCH_FEC and AAL_PDSCH_FEC Profiles. This version of the document updated to the latest O-RAN specification template, along with updates to clarify the text in some sections of the document.
This specification describes the Architecture and Requirements for Indoor Picocell deployment scenarios as specified in O-RAN Deployment Scenarios and Base Station Classes For White Box Hardware. This version updates requirements on 4T4R and adds SuFG requirements in environmental sections.
Document describes functional procedures for reducing O-RU or O-RU+O-DU energy consumption, and defining related power KPIs. This version brings several updates:
This document specifies the Hardware Architecture and Requirement as required by deployment scenario and base station classes specification. The updates in the current version address the compliance requirements of O-RAN SuFG's circular economy guidelines for network equipment in O-RAN deployments by revising the EMC requirements for O-CU, O-DU, and O-RU to align with SuFG's circular economy outcomes.
This specification defines the O-CU and O-DU software architecture, functional blocks, and API definitions. This version updates O-CU and O-DU power management and NES E2 interactions.
This specification defines interoperability test cases for O-CU and O-DU. This version brings 5 new test cases including O-RU sharing, slice performance and ROHC profiles.
The document is intended to describe best practices for O-RAN transport Network Element (TNE) management interfaces. Phase 9 added the use cases for the coordinated interface between transport management and SMO in Annex E.
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:
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 since the previous version:
The present document specifies the O-RAN Performance Measurements (PMeas) for 5G networks that may be supported on the O1 Interface.
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.
The document leverages the existing content in various O-RAN specifications and specifies new use cases for Topology Exposure and Inventory Management. For each use case, the document describes the motivation, resources, processes involved and the data requirements. This version introduces a use case on handling cloud site outage using TE&IV Services.
O-RAN Security Requirements and Controls Specifications v10.0 has been updated to incorporate several key enhancements and clarifications. These updates include MACsec as a security control to protect both C-Plane and U-Plane messages. IEEE 1588 Authentication TLV has been included to secure S-Plane ANNOUNCE messages. LDAP has been designated as the preferred protocol for centralized user management. Additionally, shared O-RU security requirements have been updated, and new security requirements have been introduced to improve the least privilege of O1 NACM. Security controls have been added for the Near-RT RIC to validate data received from xApps through E2-related APIs. These updates also include the separation of non-atomic requirements, editorial changes to ensure conformity with ODR rules and compound O-RAN requirements have been split for better clarity. Furthermore, a mapping of threats to requirements has been added, along with a definition of sensitive data.
This document provides security protocol specifications for an O-RAN compliant implementation. Version 10 introduces LDAP for centralized O-RU user management, rewrites TLS and DTLS protocol clauses, adds an OAuth2.0 Access Token API with an Open API specification, and incorporates MACsec for enhanced data link layer security. Additionally, editorial references have been updated for clarity and consistency.
O-RAN Security Threat Modeling and Risk Assessment document identifies the various assets that are at risk, outlines the potential security threats that O-RAN system may face, along with security principles on how to mitigate these risks. The report then evaluates the likelihood and potential impact of the identified threats on the O-RAN system.
Version 4.00 of the O-RAN threat model introduces new threats related to centralized user management for the O-RU, time synchronization, and AI/ML. These threats have been mapped to corresponding vulnerabilities, assets, and security principles specific to O-RAN architecture. The risks associated with these threats have also been thoroughly assessed.
The O-Cloud security technical report analyzes the security of O-Cloud components and interfaces. It includes a risk assessment of the cloud deployment models (Private, Community, Public and Hybrid), identifies the assets that need to be protected, identifies potential security risks and vulnerabilities, and proposes recommendations and best practices for reducing risks and improving the security of O-Cloud. The identified assets, threats and recommendations are intended to be part of O-RAN security related specifications.
In the version 7.00, a few term definitions to align with WG6 specifications, O-Cloud Admission Control as a recommendation, Time synchronization related threat, O-Cloud asset ID changes are added.
The Fronthaul CUS-Plane security technical report examines various aspects of securing CUS-Plane on the Open Fronthaul interface between the O-DU and O-RU. In this study, the report identifies the critical assets that require protection within the CUS-Plane, details the key issues, threats emanating from the key issues and the potential risks involved.
The technical report has been updated to correct, modify the key issues related to S-Plane security. Specifically, it now includes considerations for implementing hop-by-hop MACsec to enhance CUS-Plane security. Additionally, the MACsec solution for securing Open Fronthaul has been expanded to support the three encryption modes and provide normative requirements to the Security Requirement Specifications.
Update to the SMO Security TR to include Decoupled SMO in its scope. Further security analysis of Decoupled SMO is pending for upcoming release trains.
Update to the Shared O-RU Security to include solution options for certificate chains in a multi-operator environment. Further analysis of the options will be performed in the Certificate Management WI.
This technical report provides the threat model and risk assessment for AI/ML in O-RAN. The report identifies threats and risks and recommends potential security controls to protect against those threats through safeguards or mitigations.
This version of the TR contains one additional threat analysis and several new security controls.
This document considers the security log management as far as it applies to entities defined in the O-RAN architecture.
Besides editorial changes more details were added to the solution details of solution #6.
This technical report is the result of a study on the use of centralized user management on the O-RU. The report contains identified key issues, threats and proposed mitigations.
In this version an update to the selection of protocols has been made where LDAP with StartTLS is selected as primary protocol.
This technical report studies the applicability of a Zero Trust Architecture (ZTA) to the O-RAN Architecture. The first version of the ZTA technical report identifies the applicability of NIST Zero Trust (ZT) tenets, defines assets, and outlines target security requirements based on CISA's ZeroTrust Maturity Model.
These specifications validate the proper implementation of security requirements and protocols, emulate security attacks, and validate the effectiveness of security mitigation methods. Several new changes requests were added in version 7.
Version 8 added several changes for O-Cloud testing, Application package and input validation. This version also rewrite some general tests from clause 6.
This technical report studies a comprehensive framework for certificate management across the O-RAN environment
OAuth2.0 Version 3.0 consists of additional security threats for OAuth2.0 related to access control, identified key issues and solutions for OAuth2.0.
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.
This version is adding requirements on confidentiality and unified file format on Summary Report and Test Report. Changes from previous version:
