O-RAN testing, integration
and certification
O-RAN Global PlugFests
and Proofs of Concept
Resource from O-RAN EcoSystem Players
Next generation Open RAN research
Virtual exhibition of O-RAN implementations
Explore O-RAN
in the World
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) or Focus Groups (FG), each covering different part of the solution, keep strong momentum in specification development.
Since November 2023, O-RAN WGs and FGs published 69 technical documents, bringing the total to 112 titles in current version and 561 documents overall.
11 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 has further updates related to O-RAN Drafting Rules (ODR) compliance, ETSI Publicly Available Specification (PAS) review readiness, and also addresses review comments related to O-RAN architecture terminology alignment.
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 includes a new use case (“Interference Optimization”) and some minor 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 includes new sub use case additions to Shared O-RU use case and some minor editorial corrections.
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 clarifies that O-RAN Network Function (NF) has “O-RAN defined behaviors and interfaces” but “can also inherit and/or extend” a 3GPP NF. The “Cloudified NF” definition addressing deployment aspects is removed to keep the focus of this document on logical network view. The R1 interface and Near-RT RIC APIs are added to “Relevant Interfaces in O-RAN Architecture” clause. New text and figure are introduced to describe Service Based Architecture of Near-RT RIC. The Security Architecture clause is simplified by removing informative text and referring to relevant WG11 specifications. Finally, relevant clauses are updated to add testability, clarify that O-RAN does not conflict with 3GPP, and align with WG10 OAM architecture by representing O1 interface as an MnS (Management Service).
The objective of this Technical Report was to propose a decoupled SMO architecture to enable standardized interoperability in multi-vendor SMO deployments. Decoupled SMO 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 SMOSs 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 SMO Intent Management 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.
The external exposure allows external management and business entities to interact with the SMO by expressing their requirements and goals for RAN instances in a simplified manner, without needing to be aware of all the details of the RAN models and the various types of management and orchestration interfaces design. An example of such external management service can be an E2E Service Management (SM) system that is tasked to create and maintain a 5G service that includes access/RAN, core, transport and cloud services needed.
Internally, different SMOS producers (in the SMO framework, or rApps) can use intents to interact with each other for different RAN management related tasks.
Using intents would simplify the interactions and minimize dependencies between the consuming and producing entities of the management service, e.g., E2E SM entity, or a BSS, and the O-RAN SMO. The simplified approach of the SMO NBI, SMOS exposure and R1 using intent-based management is beneficial to address these needs. The TR outlines use cases, the relevant best-in-class industry work done on intents management and identifies the next steps for the normative work after the study.
This document specifies the general aspects and principles of the A1 interface. This version brings ETSI PAS related editorial enhancements and applying latest template.
This document describes use cases for the O-RAN A1 interface. This version brings editorial enhancement and applying latest template.
This document describes the transport protocol of the O-RAN A1 interface. This version brings ETSI PAS related editorial enhancements of references in clause 7.
This document specifies the application protocol of the A1 interface. This version brings ETSI PAS related editorial enhancement and applying latest template.
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 ETSI PAS related editorial enhancements and extended description of packet delay and packet loss attributes and UE identifier options for ScopeIdentifier. It also updates to the latest JSON schema draft.
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 ETSI PAS related editorial enhancements, applying latest template and updating test cases applicability.
This document provides the technical specification for the Non-Real-Time RAN Intelligent Controller (Non-RT RIC) architecture. The main updates for this version spec include:
This document describes use cases for the O-RAN A1 interface. The main updates for this version spec includes:
The O-RAN R1GAP Specification summarizes the R1 interface specification objectives and specifies the principles and procedures related to the O-RAN R1 interface. This version brings:
This document describes use cases and requirements for the O-RAN R1 interface. This version brings:
This document describes transport protocols for the O-RAN R1 interface services. Updated the specification to include minimum version of Kafka required on the Application layer.
This document contains a realization for the procedures identified in O-RAN R1 interface: General Aspects and Principles. This version brings:
This document specifies the Type Definitions for R1 Services. It is part of a TS-family covering the R1 interface specifications.
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 the specification adds the advanced sleep mode (ASM) use case as part of the energy saving WI and several ODR-related editorial changes.
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 adds Subscription audit procedure to request a list of currently active RIC subscriptions on the E2 Node.
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 adds Subscription audit procedure to request a list of currently active RIC subscriptions on the E2 Node.
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 includes “partial UE ID” data structure to be used with, e.g., RIC Query.
This document specifies the capabilities exposed over E2 interface to enable efficient control of RAN, including radio bear control, radio access control, connected mode mobility, etc. This version of the document completes Control Style 8, adds use of UE identifiers for RIC query as well as clarifications on RAN function definition and UE ID.
This document aims at exposing configuration and control related processes on a cell-level basis. This version of the document adds Energy saving report and control for cell/carrier switch on/off functionality.
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 of the document supports exposure of Radio Analytics Information (RAI).
The document specifies the application protocols (API definition, solution sets) of the Y1 services. This version of the document supports exposure of Radio Analytics Information (RAI).
The document specifies data types that are applicable on the Y1 interface. This version of the document supports exposure of Radio Analytics Information (RAI).
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.
Introduction of new functionalities:
Performance counters for Shared Cell
Clarifications, including:
Corrections, including:
Editorial changes and fixes of typing errors.
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.
Addition of new functionality, including:
Bug fixes and clarifications to V13.00 including:
The scope of O1 interface for O-DU spec is to describe the supported management features including “start-up” installation, PNF software management, provisioning management, performance management, fault management and file management towards the O-DU via O1 interface. This spec also includes O-DU related performance counters, information models, and data models.
This version brings:
The scope of O1 interface for O-CU spec is to describe the supported management features including “start-up” installation, PNF software management, provisioning management, performance management, fault management and file management towards the O-CU-CP and O-CU-UP via O1 interface. This spec also includes O-CU related performance counters and information models.
This version brings:
The scope of U-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. U-Plane profile specification contains profiles of X2/F1/Xn U-Plane procedure for EN-DC use cases, NR-SA use cases and NR-DC use cases. Main updates compared to version 05 are:
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 v8.00:
This Technical Report identifies 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 updated version adds material on O-Cloud networking concepts.
This specification defines cloudification and orchestration use cases and requirements for O-RAN. This updated version contains additional use cases for FM, PM and O-Cloud Backup.
This specification defines O-RAN O-Cloud functions and protocols for the O-RAN O2 interface. This updated version contains added material on FM, PM, Networking and Provisioning concepts.
This specification defines O-RAN O-Cloud IMS interface functions and protocols for the O-RAN O2 interface. This updated version contains added Alarm and PM Dictionary discovery as part of inventory services, and PM service models and FM/Alarm service models.
This TS specifies the O-RAN O-Cloud’s DMS interface protocol and data model based on the ETSI NFV solutions. This updated version contains added flows and API details for FM and PM.
This specification defines O-RAN O-Cloud hardware accelerator interface functions and protocols for the O-RAN AAL interface. This version contains various corrections and updates.
This specification focuses on the Common API related to common aspects of accelerator abstraction from an administration and AAL Application perspective. This version includes the addition of HW Accelerator Manager IM, registration and reporting extensions.
This specification defines tests for O-Cloud conformance to WG6 specifications. This version contains minor updates and corrections.
This new Technical Report provides a study of the applicability of a K8s declarative interface for O-RAN O2 IMS interface, with proposals for IMS future work to support a K8s-oriented API.
This new TS defines an O-RAN Application Services Descriptor (ASD) for potential use in application package.
This document provides the initial O-Cloud IoT specification, and includes definition of the interoperability testing methodology and a set of tests for the O-Cloud Notification API.
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 adds support for All-in-One designs.
This specification defines the O-CU and O-DU software architecture, functional blocks, and API definitions. This version brings Updates to Layer 1 processing blocks for network energy savings, corrections and additions to O-DU APIs.
This specification defines interoperability test cases for O-CU and O-DU. Updates to test cases and revamp of test cases.
This document is intended to describe best practices for O-RAN fronthaul transport based on WDM technology. Version 4.0 includes updates on smart tunable optics with reference to respective MSA, and other minor editorial updates. They include specs and charts through the document to ensure alignment in recent specification activities.
The document is intended to describe best practices for O-RAN transport based on end-to-end packet switching technology. Version 7.0 updates references, as required (added 3GPP references related to certificate management, added IETF reference related to 5G transport slicing). It also includes updates in section 17.4 (IEEE 802.1X authentication towards Computes and O-Cloud-Gateways; additional section about certificate management)
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 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 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. 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:
This document outlines security requirements and controls for O-RAN defined interfaces and network functions. In version 8 of the technical specifications, new security requirements and controls have been introduced for O-Cloud logging, O-Cloud instance ID, O-Cloud Time Synchronization, NFO, FOCOM, xApp Registration Procedure, rAppIDs, and App decommissioning. Additionally, there are new security requirements for Preventing Tampering of Log Data and preventing (D)DoS attacks on Security Log Data management. Further, there are additional security controls addressing DoS/DDoS mitigation, Acceleration Abstraction Layer (AAL), and User Management Requirements for Cloud Platform Management. New security mechanisms are defined for Y1 and E2 interfaces, along with modifications to security requirements for the O1 interface and Common Application Lifecycle Management.
This document provides security protocol specifications for an O-RAN compliant implementation. In Version 08.00 Secure file transfer protocols have been added, and an update on no root remote login with SSH. The protocol ssh-ed448 has been changed to optional and additional reference on SSH has been added.
These specifications validate the proper implementation of security requirements and protocols, emulate security attacks, and validate the effectiveness of security mitigation methods. Several new change requests were added in version 6.0. These include Security Protocol & APIs Validation, Common Network Security Tests, System Logging, SBOM, O-RAN interfaces testing, O-Cloud Testing and End-to-end security test cases. Alignment for ETSI PAS and with GSMA guidelines has been included also in this version.
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.
In Version 2 of the document, new threats specifically targeting the Non-RT RIC and the O-Cloud instance ID have been introduced. This version not only acknowledges these new threats but also includes a detailed risk assessment for each. Additionally, Version 2 introduces a new security principle focused on the secure management of the O-Cloud ID, underscoring the evolving nature of threat landscapes and the necessity for continuous adaptation in security practices.
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. This version updates the technical report with content for rAppID abuse, application registration and application decommissioning.
This technical report considers the security log management as far as it applies to entities defined in the O-RAN architecture. The study analyzes a list of key issues on Security logs contents (payload), Security logs transfer mechanisms and Security logs formats/schemas and proposes solutions in order to derive security requirements, intended to be part of O-RAN security related specifications.
This technical report considers the security aspects of the Near-RT RIC platform and xApps, as well as the associated network and management interfaces (E2, A1, O1) and APIs. The study analyzes a list of key issues in the Near-RT RIC overall architecture and proposes solutions in order to derive security requirements.
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.
With the release of Version 5, the report has expanded its scope to include specific threats related to the O-Cloud instance ID. This latest version not only recognizes these new threats but also provides a comprehensive list of security recommendations specifically tailored for the secure management of the O-Cloud ID.
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.
This technical report documents a security analysis for the SMO. The TR provides assets, threats, risk scoring, and recommended security controls across 3 threat groups: SMO, O2 interface, and External Interfaces. Threat analysis is based upon the STRIDE model and risk scoring is based upon likelihood and impact. Recommended security controls were used to form normative SMO security requirements.
Updates were made to SMO Security Analysis TR to include Decoupled SMO and RAN-Core Data Sharing.
This technical report documents a security analysis for the Shared O-RU with consideration of each of the 5 architectural options. The TR provides assets, threats, risk scoring, and recommended security controls across 6 threat groups. Threat analysis is based upon the STRIDE model and risk scoring is based upon likelihood and impact. Recommended security controls were used to form normative Shared O-RU security requirements. Updates were made to Shared O-RU Security Analysis TR to include Resiliency use case.
This technical report defines the authorization framework for O-RAN elements using O-Auth2.0 and applies to the HTTP-based APIs used in the R1, O2, A1 and Y1 interfaces. The study has identified the security threats and key issues for OAuth2.0 framework.
This technical report studies a comprehensive framework for certificate management across the O-RAN environment.
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. For version 5, prepares the specification for the ETSI PAS process. Changes from previous version:
This document describes the certification and badging processes and associated detailed technical procedures for the Open Testing and Integration Centres (OTIC) and various other testing entities.
Objectives and scope:
Changes from previous version:
