The O-RAN Alliance is an operator-led global industry alliance, formed in February 2018 through the merger of the C-RAN Alliance and the xRAN Forum, whose mission is to reshape how radio access networks are designed, built, and operated. Where traditional RAN stacks are vertically integrated — baseband software, radio hardware, and management tools delivered as a single vendor bundle — O-RAN promotes disaggregation: separating the RAN into open, standardised functional blocks connected by published interfaces, so a mobile operator can mix DU, CU, RU, and management software from different suppliers. The alliance’s core objectives are multi-vendor interoperability, cloud-native and virtualised deployment, programmable RAN intelligence through the RIC (RAN Intelligent Controller), and operational automation at scale. These goals address vendor lock-in, slow innovation cycles, and the cost structure of legacy RAN, while aligning with 5G and beyond requirements for network slicing, edge deployment, and AI/ML-driven optimisation.
Specification work is organised into eleven Working Groups (WGs), all under the Technical Steering Committee (TSC), each owning a slice of the architecture.
| WG | Scope |
|---|---|
| WG1 | defines use cases and the overall O-RAN architecture |
| WG2 | covers the Non-RT RIC and the A1 interface |
| WG3 | the Near-RT RIC and the E2 interface |
| WG4 | Open Fronthaul between O-DU and O-RU |
| WG5 | the midhaul/backhaul interfaces (F1, W1, E1, X2, Xn) |
| WG6 | cloudification, O-Cloud, and the O2 interface |
| WG7 | white-box hardware |
| WG8 | O-CU/O-DU stack reference design |
| WG9 | xHaul transport |
| WG10 | OAM and the O1 interface |
| WG11 | security requirements, threat modelling, and assurance |
Architecturally, O-RAN is organised around three domains. The SMO (Service Management and Orchestration) framework sits at the top as the management and automation plane, hosting the Non-RT RIC and connecting southbound through O1 (to O-RAN NFs), O2 (to O-Cloud), A1 (to Near-RT RIC), and the Open Fronthaul M-plane. The O-RAN network functions — O-RU, O-DU, O-CU-CP, O-CU-UP, and the Near-RT RIC running xApps — form the radio processing and real-time control layer. The O-Cloud at the bottom provides the virtualised infrastructure (compute, storage, networking) on which those functions run, managed by the SMO over O2. This layered separation — intelligence (RIC), data plane (CU/DU/RU), management (SMO), and infrastructure (O-Cloud) — is what makes multi-vendor composition technically feasible rather than merely aspirational.
Market adoption has moved from early proof-of-concept trials toward commercial-scale industrialisation, though the pace varies widely by operator and region. Large operators in North America, Europe, and Asia have deployed or announced Open RAN in greenfield, rural, and enterprise scenarios; vendor ecosystems spanning traditional NEPs, cloud providers, and specialist Open RAN suppliers have matured around the SMO, O-Cloud, and disaggregated RU/DU/CU stack. Industry surveys in 2025–2026 indicate that a majority of operators plan to incorporate the SMO framework into their RAN automation strategy within three years — often by evolving existing SON platforms rather than a full rip-and-replace — and that SMO/Non-RT RIC with rApps is currently ahead of Near-RT RIC/xApp deployment in production roadmaps. Full-scale Open RAN rollouts nevertheless face real constraints: performance parity with integrated RAN in high-capacity macro sites, integration and testing complexity across multi-vendor chains, and the operational maturity of the broader ecosystem. O-RAN is widely treated as a long-term structural shift in RAN procurement and architecture rather than a near-term wholesale replacement of every legacy site — with adoption strongest where openness, automation, and supplier diversity deliver clear operational or economic value.