O-RAN ALLIANCE Work Groups and Focus Groups recently published 53 new technical documents completing its Release 002. It includes 2 new specification titles:
All O-RAN specifications are based on the following logical architecture and available for download at our website.
The O-RAN Architecture Description document (O-RAN.WG1.O-RAN-Architecture-Description.v07.00) specifies the overall architecture of O-RAN. It describes all of the O-RAN functions and relevant interfaces that connect these functions. This version adds the concept of SBA (Service Based Architecture) as part of the SMO Architecture Principles. SBA describes the roles of service producer and service consumer together with standardized service-based interfaces to enable interoperability within the SMO.
This document describes potential O-RAN use cases, emphasizing how the use case is enabled by the O-RAN architecture along with basic input data expectations and resulting actions. This version includes addition of three new detailed use cases (“Energy Savings”, “MU-MIMO Optimization”, “Shared O-RU”).
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 addition of a new use case (“MU-MIMO Optimization”) and additions to an existing use case (“Shared O-RU” use case updates for Multi-vendor slices use case impact.)
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 includes the initial content related to multi-Operator RAN Slice Subnet Management use case.
This document specifies the general aspects and principles of the A1 interface. This version brings updates according to the new drafting rules and improvements to the terms and definitions.
This document describes the transport protocol of the O-RAN A1 interface. This version adds Mutual Transport Layer Security (mTLS) support for the mutual authentication of the Non-RT RIC and one or more Near-RT RICs.
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 includes guidelines on how to define A1 Enrichment Information datatypes and datatypes for UE location and velocity.
This document describes use cases for the A1 interface with associated stage 2 level flow charts.
The R1 GAP Specification summarizes the R1 interface specification objectives and specifies the principles and procedures related to the R1 interface. This version includes streamlining of the Data management and exposure services procedures that include: the data request, data subscription, data offer, updates to procedures on Service management and exposure, A1 policy management services and O1-FM related services. New procedures were introduced for A1 -EI related services and O1 -CM related services.
This document describes transport protocols for the R1 interface services. This version includes updates to security protocol to align with the Security specifications that include alignment to support mTLS and OAuth2.0.
This document describes use cases and requirements for the R1 interface. This version introduces new use cases for Data management and exposure services, A1 policy management service and O1-FM related services, and adds requirements to Services management and exposure services.
This document provides the technical specification for the Non-Real-Time RAN Intelligent Controller (Non-RT RIC) architecture. This version includes adding data offer service as part of DME services. It introduces new O1-related procedures of querying alarm and changing alarm acknowledgement state.
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 specs introduces requirements for two additional use cases, Slice SLA Assurance and Massive MIMO.
This document specifies the first version of E2SM-CCC, which aims at exposing configuration and control related processes on a cell-level basis. The main use case supported in E2SM-CCC v1.0 is Slice SLA assurance whose configuration parameters are carried in corresponding information elements with JSON encoding.
This specification defines the functions and protocols of the E2 interface, which connects the O-RAN Near-RT RIC to the underlying O-RAN nodes (i.e. E2 nodes). This version includes minor updates and corrections to v2.02 (bin range definition of distribution type measurements, Sequence of Matched UE IDs for Granularity Periods, "Logical OR" into UE filtering conditions) as well as introduction of new measurements related to non-GoB mMIMO feature.
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 only adds one correction on RAN parameter ID.
This specification defines the application protocol of the E2 interface. This version introduces editorial corrections and one ASN.1-related correction.
This specification defines the internal architecture of O-RAN Near-Real-Time Radio Intelligent Controller (Near-RT RIC) from a functional perspective. This version has progressed on xApp APIs Stage-2 aspects, such as alignment with E2AP Global Procedures, a failure case to allow xApp to report error with incoming E2 Indication, E2 Subscription procedure limited to a Single E2 node, A1-related procedures for xApps, clarification on management function, E2 Subscription Delete Query and Notification procedure, and various clean-ups.
This document specifies the control plane, user plane and synchronization plane protocols used over the fronthaul interface linking the O-DU (O-RAN Distributed Unit) with the O-RU (O-RAN Radio Unit) with a Lower Layer Functional Split-7-2x based architecture. This version brings introduction or modification of functionalities, including:
- Acknowledgement / Negative Acknowledgement (ACK/NACK) for C-Plane messages
- Support for Shared O-RU
- Added FFT/iFFT size 3072 to the definition of the frameStructure field
Clarifications, including:
- Uplink frame timing to Downlink frame
- Aligned S-plane limits with ITU-T
- Handling of precoding schemes with Transmit Diversity and Spatial Multiplexing with Large Delay DDD
- Downlink C-Plane and U-Plane timing
- Byte order for U-Plane data in Section Extension 11 and19
- extended Antenna-Carrier ID (eAxC_ID) assignment
- Timing error requirements for LLS-C3 configuration
Corrections to:
n-ta-offset value per 3GPP specification
Citation of IEEE 1588
This specification describes the Cooperative Transport Interface (CTI) and related message protocol when the fronthaul between the O-DU and O-RU is realized via a resource allocation-based transport network. This version of specification brings:
- Clarification of terminology used to refer to the Transport Control Plane (TCP) and Transport Management Procedure (TMP) specifications - the terms with “plane” such as “T-plane” and “TM-plane” which have proven confusing in the past have been removed
- Clarification that the companion CTI-TMP specification is about the Information Model (IM) and Data Model (DM) of the CTI TC plane, and more explicitly shows the management interactions in the context of CTI so that CTI TM is not mistaken for some management plane (update of Figure 2-1).
- Note: there are no functional changes compared to CTI-TCP v2.
This document describes the Transport Management Procedures for the Cooperative Transport Interface (CTI). This version brings:
- Comprehensive overhaul of the Information Model (IM) and Data Model (DM) of v2 in order to align it to O-RAN guidelines for O1 and to 3GPP best practices
- Description of attaching the CTI IM into the wider O-DU IM
- Clarification about the scope of the TMP specification as was introduced in v3 of the CTI-TCP specification
- Note: there are no functional changes compared to CTI-TMP v2.
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 of specification brings introduction or modification of functionalities, including:
Addition of options to TDD Profile 1
- additional 2 TDD configurations; 9bitIQ; llsC3; 1 lane 10GHz OFH
- 3 new IOT Profile Test Configurations
Addition of options to TDD Profile 2
- additional TDD configuration
- 2 new IOT Profile Test Configurations
- Update of references to CUS/M-Plane specs accounting for ETSI-PAS section renumbering
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. This Technical Specification is used in combination with a set of associated YANG models to enable operation of an O- RAN alliance defined O-RU. This version brings addition of new functionalities, including:
- Shared O-RU functionality for single and multi-operator deployments
- IEEE 802.1X Port Based Access Control
- Introduction of O-RU Connector concepts
- Support of DUID/IAID when using DHCPv4
- Updated SFP compliance does
- Mapping certificates to NETCONF accounts
- New fault information fields
Bug fixes and clarifications to previous v09.00 include:
- Clarify contradicting statements with regards to TLS 1.2
- Array element fault source and fault source improvements
- Software management clarification
- Correction for module privileges
- Persistence of configured subscription
- Correction for O-RU call home port
- Clarify operation of filter based on xpath
- Clarify operation with factory default software
- Clarification to path definition for file management
- Password for FTPES server
- Call home with multiple A/AAAA records
- PKI Clarifications
- Hybrid management clarifications
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:
Alignment to WG4 Fronthaul specification versions - O-RAN Control, User and Synchronization Plane Specification v9.0 (CUS.0-v09.00) and O-RAN Management Plane Specification v9.0 (MP.0-v09.00):
- Focused on references to renumbered clauses from ETSI PAS effort
Clarification or correction found during OTIC testing:
- S-Plane clarifications, especially around performance test cases
- Beamforming tests changed to conditional mandatory for Category A radio not supporting beamforming
Various corrections and enhancements to M-Plane test cases:
- Additional Access Control test cases
Editorial clarifications of various beamforming test cases
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 of the specification adds:
o several new use cases
o corrections
The scope of O-DU O1 Interface spec is to specify the interface that links O-DU to the Service Management and Orchestration (SMO) framework. It is focused on O-DU management operations, performance counters, fault supervision, software management, synchronization management, and configuration parameters for O-DU
Compared to v04.00, this version of O-DU O1 spec includes the following updates:
- CTI YANG Modules introduced to WG5 Data Models
- Corrections to PM counters related to SSB index
- Addition of PM counters for BWP
- Updates to PM subcounter for IP Latency DL
- Editorial fixes and updates
The scope of O-CU O1 Interface spec is to specify the interface that links O-CU-CP and O-CU-UP to the Service Management and Orchestration (SMO) framework. It is focused on O-CU management operations, performance counters, fault supervision, software management, and configuration parameters for O-CU
Compared to v03.00, this version of O-CU O1 spec includes the following updates:
- Clarification of alignment to O1 Interface Specification
- Editorial fixes and updates
The scope of WG5 IOT spec is to specify Interoperability tests for O-RAN nodes from different vendors implemented in accordance to the WG5 C-plane and U-plane profiles.
This version of the IOT spec focuses on;
- X2 interoperability testing (Devices under Tests (DUTs) are eNB and en-gNB)
- F1 interoperability testing (DUTs are en-gNB consisting of the gNB-CU and gNB-DU)
- Xn interoperability testing (DUTs are gNBs)
Main Updates compared to v03
- Addition of more X2, F1, and Xn test cases
- Minor editorial corrections
This document introduces and examines different scenarios and use cases for O-RAN deployments of Network Functionality into Cloud Platforms. This version includes updates for PDP support and for O-Cloud Infrastructure Management Services (IMS) provisioning concepts.
This document contains use cases for O-RAN orchestration of virtualized RAN and the associated requirements on interfaces used for management and orchestration. This version adds use cases for O-Cloud functional status update, alarm dictionary discovery, logging management, PM job query and job delete, and K8s cluster creation and deletion, as well as updates to the recovery use cases.
This document details the AAL specification consisting of the description of the interface, information models and requirements to implement an AALI (AAL Interface), for the AAL_DOWNLINK_High-PHY and AAL_UPLINK_High-PHY profiles. This version includes modifications to the mMIMO Beam Forming tables as well as updates for new parameters to align with ORAN-WG4-MP Section 15.2.
This specification outlines the deployment management services of the O2dms interface profile based on Kubernetes Native API for containerized NFs. This version introduces referenced Kubernetes Native namespace scoped resource objects.
This specification outlines the general aspects and principles of the O2 interface. This version introduces updates to the Performance Management concepts for PM Job and further examples.
This specification focuses on the Common API related to common aspects of accelerator abstraction from an administration and application perspective. This version updates the management object model and common API requirements, and adds an abstraction framework and call flow for transport of information between applications and accelerators within the O-Cloud.
This specification outlines the deployment management services of the O2dms interface profile based on ETSI NFV protocol and data models. This version introduces support for the Heal NF Deployment operation.
This specification outlines the general aspects and principles of the O2 interface. This version introduces updates to the Performance Management concepts for PM Job and further examples.
This document defines a REST API that allows Event Consumers (EC) such as a vO-DU or CNF to subscribe to events/status from the O-Cloud. This version incorporates support for multiple event producers and has been updated for consistency and to fix errors.
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 adds support for CBGTI.
This specification defines O-RAN O-Cloud hardware accelerator interface functions and protocols for the O-RAN AAL interface, including configuration and management functions, procedures, operations and corresponding solutions. This version adds further updates and alignments.
This document describes the white box Hardware Architecture and Requirement of O-CU, O-DU, and O-RU based on deployment scenario and base station classes specification (O-RAN.WG7.DSC.0-v03.00.pdf). The OMAC-HAR specification document presents the high level deployment scenario and the respective O-DU and O-RU reference architecture for O-RAN Split option 7-2x. The high level hardware block diagrams for O-CU, O-DU, and O-RU are shown and the functional modules of each diagram are described.
In this version, the conventional and massive MIMO O-RU7-2x high level functional block diagrams and high level reference architectures of O-RU split option 2 are added and their functional blocks are also briefly described. Furthermore, the additional operating frequency bands and bandwidths are updated in O-RU7-2x performance requirement table.
This document specifies all deployment scenarios as identified by operators.
This document specifies the hardware reference design based on architecture and requirements for the Outdoor Microcell (O-RAN.WG7.OMAC-HAR.0-v02.00.pdf) and deployment scenario and base station classes (O-RAN.WG7.DSC.0-v03.00.pdf) specifications.
This specification defines the O-CU and O-DU software architecture, functional blocks, and API definitions. This version includes:
- Updates to sections on O1 and cloud architecture reference in O-CU and O-DU
- Updated references section
- New template
This document specifies the requirements, conditions, configurations, profiles, and sequences for interoperability testing of O-RAN O-CU and O-DU deployment scenarios with other O-RAN components in standalone (SA) mode. This version includes:
- New test cases for Massive MIMO, RAN slicing and O1
- Fixes and minor updates to older test cases
- New template
This document defines the testing requirements for an Open Xhaul transport infrastructure. This version adds new test cases for synchronization and WDM.
The document is intended to describe best practice for O-RAN architecture and solution for X-haul timing & synchronization. This version includes enhancements related to security considerations and Resiliency, Single and duplex fiber solutions for passive WDM systems, etc.
This document defines O-RAN OAM interface functions and protocols for the O-RAN O1 interface. This version of O1 specification incorporates approved CRs:
- O-RAN counter name clarification
- File management update
- O1 Notification
- Plug and Connect uplift
- UE Identifiers for Trace header
- CM Notifications uplift
- Editorial update related to copyright statements
This document specifies security requirements and controls for O-RAN defined interfaces and network functions. In version 4.0, new security requirements on the O-Cloud image protection were defined, the security requirements for the Non-RT RIC and its interfaces were updated. Requirements on A1 and R1 were added. It also includes an update on Near-RT RIC specifications for consistency with other WG11 specifications.
The objective of this document is to give a comprehensive and high-level view of the organization of security within the O-RAN system. This version adds the O-Cloud risk assessment. The risk assessment is based on the identified threats from the O-Cloud technical report.
These specifications validate the proper implementation of security requirements and protocols, emulate security attacks, and validate the effectiveness of security mitigation methods. Four new change requests were added in version 3.0. These include image signing and verification, validation of OAuth2.0, expansion of the TLS with mutual TLS, the addition of TLS on the A1 interface, and IPSec on the E2 interface.
This document contains security protocol specifications for an O-RAN-compliant implementation. In this version, mutual TLS was added to the TLS section. OAuth2.0 was introduced to set up the authorization framework for O-RAN APIs. CMPv2 protocol for certificate management is now included. Furthermore, new cryptographic operations within the security protocols for the protection of O-Cloud Apps/VNFs/CNFs packages are now described.
This document describes the certification and badging processes and associated detail technical procedures for the Open Testing and Integration Centers (OTIC) and various other testing entities. This version of specification brings:
- CRs on potential decoupling the direct referencing to test cases in WG Test Spec
- CRs with updates on Certificate & Badging (C&B) launching logistics
- CRs on 2nd level test report template including more info such as test equipment
Changes from previous version:
- Revising Chapter 4, 5, 6 to decouple this document from directly referencing test cases defined in underlying WG test specifications.
- Revising section 3.2.8.2 to provide further clarifications on centralized O-RAN web catalogue for issued O-RAN certificates and badges
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. Changes from previous version include correction on DoS source address and duration for security testing in Section 7.2, clarification on the E2E test report relationship with the Certification and Badging test report, and addition of summary tables of test cases for each of the chapters to remove redundancy with the Certification and Badging specification.
