O-RAN Release 003 includes enhancements to RAN Slicing and SMO features. It also introduces new features:
O-RAN Release 003 also includes 10 new specification titles:
All O-RAN specifications are available for download at our website.
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 additional content related to multi-Operator RAN Slice Subnet Management use case.
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 (“RAN-Core Data Sharing”) and minor editorial updates.
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 a new detailed use cases (“Integrated RRM-SON”), and updates to three use cases (“Shared O-RU”, “RAN Slice SLA Assurance – Reliability Assurance”, “Traffic Steering – Enrichment Based Optimization”).
This technical report captures potential O-RAN energy savings use cases. This first version of the report includes two sub use cases; “Carrier and Cell switch off/on” and “RF Channel Reconfiguration”.
The O-RAN Architecture Description document specifies the overall architecture of O-RAN. It describes all of the O-RAN functions and relevant interfaces that connect these functions. This version includes the Y1 interface for exposing RAN analytics information to internal and/or external functions. Its content has been reformatted and all references to future work items (e.g., O1 interface between SMO and O-RU, planned security enhancements etc.) have been removed to align with O-RAN drafting rules. In addition, C-RNTI (Cell Radio Network Temporary Identifier) has been added to the UE identifier so that it can be optionally reported by O-CU-CP, O-DU, and O-eNB.
This Technical Report proposes a decoupled SMO architecture to enable standardized interworking between SMO Functions sourced from different vendors to better serve the needs of mobile network operators. In this version, the terms SMOF (SMO Function) and SMOS (SMO Service) have been defined while the current SMO services and other external services to SMO have been analyzed. Scenarios and use cases of SMO services for RAN NF (Network Function) OAM, Non-RT RIC, Topology and Inventory, Service Management and Exposure (SME), Data Management and Exposure (DME), and O-Cloud resources management and orchestration have been illustrated. The potential solutions for RNOAM SMOF (RAN NF OAM SMO Function) and ORMO SMOF (O-Cloud Resources Management and Orchestration SMO Function) have also been provided.
This document specifies the general aspects and principles of the A1 interface. This update brings alignment to O-RAN drafting rules.
This document describes use cases for the A1 interface. This update brings alignment to O-RAN drafting rules.
This document describes the transport protocol of the O-RAN A1 interface. This update brings alignment to O-RAN drafting rules.
This update brings alignment to O-RAN drafting rules. Enhanced alignment between A1-P and A1-EI, and between A1AP and A1TD.
This update brings alignment to O-RAN drafting rules. It also provides enhanced alignment between A1-P and A1-EI, and between A1AP and A1TD.
This version introduces A1-P and A1-EI interoperability test cases for Non-RT RIC and Near-RT RIC. It also brings alignment to O-RAN drafting rules.
This version updated the specs of O-RAN TS skeleton, as well as SME and DME services modularization. It also renamed the O1 related services to RAN OAM related services.
This version updates the specs of O-RAN TS skeleton and adds the DME and RAN OAM (PM and FM) requirements. It also adds new use cases to RAN OAM services (related to PM services), DME discover services, and the Subscription termination use case to DME services.
This new specification provides the Versioning of the APIs and Versioning of the Open APIs, as well as the API structure for the SME. It also covers the Service registration and discovery.
This version of the specification introduces E2 requirements for RAN Analytics Information Exposure (as part of QoE Optimization Use Case) and updates to massive MIMO requirements for non-GoB solution.
This version of the specification introduces the stage-2 aspects of newly defined RIC Service Query and RIC subscription modification procedure as well as a reference to execution order handling in the E2AP specification.
This version of the specification captures the Stage-3 signaling details of newly defined RIC Service Query and RIC subscription modification procedure as well as an additional information element to enforce the execution order of multiple RIC actions. Additionally, minor corrections to references and subscription duration limit were implemented.
This version of the specification mirrors the addition of E2SM-CCC and RIC Query service, plus a minor correction to 3GPP references.
This version of the document further clarifies the definition of Non-GoB beamforming mode index and adds a correction to Time Stamp definition to allow for millisecond-level granularity in the Collection Start Time.
This version of the specification contains minor fixes to JSON schemas and addition of Control Outcome.
This specification defines O-RAN OAM interface functions and protocols for the O-RAN O1 interface for the Near-RT RIC. The document studies the functions conveyed over the interface, including management functions, procedures, operations, and corresponding solutions, and identifies existing standards and industry work that can serve as a basis for O-RAN work.
This version introduces additional conformance tests cases for RIC subscription delete request, miscellaneous subscription procedures for E2SM-KPM, IOT test methodology description, and IOT cases for RIC global procedures as well as functional procedures of E2SM-KPM.
This version adds Y1 interface description within Near-RIC architecture and Stage-2 Management API procedures.
This technical specification defines signaling and data transport protocols for Near-RT RIC APIs. The protocols are developed in accordance with the functionalities and interactions stated in O-RAN.WG3.RICARCH specification.
This document specifies the control plane, user plane and synchronization plane protocols used over the Fronthaul interface. This update brings:
Introduction/modification of functionalities, including:
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 version brings:
Addition of new functionality, including:
Bug fixes and clarification to V10.00 including:
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:
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:
Support testing of Fronthaul Multiplexor:
Various corrections and clarifications, including M-Plane and UC-Plane corrections or clarifications from contributors with active testing
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 several new use cases and corrections.
The scope of WG5 IOT spec is to specify Inter operability tests for RAN Node from different vendors implemented in accordance to the WG5 C-plane and U-plane profiles.
This version of the IOT spec focuses on;
Main Updates compared to v03 are:
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 v05.00, this version of O-DU O1 spec includes the following updates:
Adds the definition of an AAL Application and updated the AAL Resource Relationship and Cardinality diagrams. Updated the AAL-LPU example mapping diagrams to clearly show the logical deployment options.
Enhanced e2e and transport workflow including transport APIs and initial alignment with AAL GAnP and O2 definitions.
Revised to add new text for the Executive summary and introductions and separation of references into normative and informative references.
This version incorporates new use cases for PM Job management, alarm list management and IMS software update, and updates to use cases for network slicing, healing and platform software update.
This specification outlines the general aspects and principles of the O2 interface. This version introduces the Alarm Suppression concept for Fault Management, and a new section on O-Cloud Operational Modes which includes Maintenance mode and Test mode.
This specification outlines the deployment management services of the O2dms interface profile based on ETSI NFV protocol and data models. This version introduces support the Scale NF Deployment operation.
This document describes the hardware architecture, requirements and reference designs for the enterprise microcell deployment scenario based on Deployment Scenario and Base Station Classes specification (O-RAN.WG7.DSC.0-v04.00.pdf). It specifies the high-level deployment scenario, hardware block diagrams, functional modules, and system requirements. It also present examples of O-CU, O-DU, and O-RU reference designs for this scenario.
This document describes the white box Outdoor Macrocell Hardware Reference Designs of O-CU, O-DU, and O-RU based on deployment scenario and base station classes specification (O-RAN.WG7.DSC.0-v04.00.pdf).
The OMAC-HRD specification document describes examples of O-CU, O-DU, and O-RU reference designs for O-RAN Split option 7-2x. Specific devices and their part numbers are recorded in respective annex.
In November 2022 specification, multiple examples of massive MIMO O-RU7-2x hardware architecture were added.
This version brings updates to cloudification and security sections of O-DU and O-CU. Added references.
CU/DU IOT test cases updated for test profiles, O1 configuration and Fronthaul interface procedures.
The document is intended to describe best practices for O-RAN transport Network Element (TNE) management interfaces. Version 05.00 added content in section 9.3 and section 10 in support of the network slicing use case for the transport network.
The document is intended to describe best practices for O-RAN transport based on end-to-end packet switching technology. Version 04.00 document aligns with O-RAN slicing phase 3 standards efforts and enhances transport network element security to align with WG11 efforts.
This document is intended to describe best practices for O-RAN Fronthaul transport based on WDM technology. Version 03.00 aligns link budget, Asymmetry and OAM with other workgroup and standard efforts.
This version of OAM Arch specification incorporates MnS capability retrieval at SMO over OAM interface.
O-RAN WG10 Information Model and Data Model v4 incorporates Guidance on how to create IMs, and introduction of Managed Application IOC IM. It also contains additional updates:
This version of O1 specification incorporates:
Document title changed (added “-R003” release version). Rapporteur’s editorials triggered by the application of O-RAN Drafting Rules process:
This document specifies security requirements and controls for O-RAN defined interfaces and network functions. In version 5.0, a security control mapping table for RIC APIs, security requirements for SMO Logging, and multiple O-Cloud security requirements and updates have been added. The updates for O-Cloud involve the image security requirements for Apps/VNF/CNF and the normative security requirements for image protection. Additional to the updates, the following security requirements were added to the O-Cloud section, secure storage, chain of trust, software image protection, and controls for virtualization and isolation.
This document contains security protocol specifications for an O-RAN-compliant implementation. In this version, within the TLS section, the cipher specifications got replaced with references to 3GPP TS.33.210.
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 provides an update to the O-Cloud risk assessment, which has been introduced in the previous version, and an update of the SMO security assets, threats, risks, and security controls. The updates are the results of the “O-Cloud Security Analysis” and “SMO Security” technical reports.
The technical report on the security analysis of O-Cloud components and interfaces analyzes the following topics:
This technical report on the security for application lifecycle management 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. This version discusses 13 key issues developed from identified threats and proposes solutions to mitigate the key issues as well as recommendations for future updates to the technical report and other specifications.
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 (TR) provides the security analysis for the SMO, including the SM Framework, Non-RT RIC, external interfaces, and O2 interfaces. The sections of the TR follow the security analysis process with asset and threat identification, threat analysis, risk analysis, and recommended security controls. This TR will provide input for normative security requirements of the SMO.
This technical report (TR) provides the security analysis for the Shared O-RU. This first revision focuses on the steps of the security analysis identifying the Shared O-RU assets and threats. Future revisions will complete additional sections of the TR as the security analysis progresses to include threat analysis, risk analysis, and recommended security controls. This TR will provide input for normative security requirements of the Shared O-RU.
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 objective and scope of that updated version were to implement CRs on Summary Report and Test Report, CR on Multi-vendor scenario. This update also brings changes from previous version in revising relevant sections across the whole document to align the terminology and contents related to the changes on Summary Report and Test Report, Adding section 5.2.10 to provide clarifications on multi-vendor scenario.