CafeTele
🛰️ O-RAN Alliance · Open & Intelligent RAN

O-RAN — the open, disaggregated radio access network, explained

What Open RAN actually is, how the O-RU/O-DU/O-CU split works, the RIC and its xApps and rApps, and every open interface — grounded in real O-RAN Alliance specifications. A complete, engineer-grade Open RAN resource built by working RAN engineers.

O-RU·O-DU·O-CUDisaggregated RAN
7.2xOpen Fronthaul split
RICxApps & rApps
Multi-vendorNo lock-in

01 — FUNDAMENTALSWhat is O-RAN?

O-RAN (Open RAN) is an open, disaggregated radio access network defined by the O-RAN Alliance. It breaks the traditional single-vendor base station into interoperable building blocks — the O-RU, O-DU and O-CU — joined by open, standardised interfaces, and makes the RAN programmable and intelligent through the RAN Intelligent Controller (RIC).

Crucially, O-RAN is not a replacement for 3GPP. 3GPP defines 5G NR and the functional CU/DU split (TS 38.401); the O-RAN Alliance defines the open interfaces, the RIC and the management architecture that turn that split into a true multi-vendor, AI-driven RAN.

One-line definition. O-RAN = open interfaces + RAN disaggregation (O-RU / O-DU / O-CU) + intelligence (the RIC, running xApps and rApps), specified by the O-RAN Alliance on top of 3GPP NR.

Start with the Complete O-RAN Architecture Guide (built on O-RAN.WG1 OAD), then the honest take in O-RAN vs Traditional RAN.

02 — COMPARISONO-RAN vs traditional RAN

DimensionTraditional RANO-RAN (Open RAN)
Vendor modelSingle vendor, end to endMulti-vendor, mix & match
InterfacesProprietary fronthaulOpen Fronthaul (7.2x) + open interfaces
IntelligenceEmbedded, closedProgrammable via the RIC (xApps/rApps)
HardwarePurpose-built appliancesCOTS + O-Cloud, virtualised/containerised
InnovationVendor roadmap-boundOpen ecosystem, third-party apps
Trade-offSimple, proven integrationMore flexible, but harder multi-vendor integration

Deep-dive: O-RAN vs Traditional RAN — the honest comparison.

03 — ARCHITECTUREThe O-RAN architecture: O-RU, O-DU, O-CU

O-RAN follows 3GPP's 7.2x functional split, dividing the base station into three logical nodes:

NodeFunctionLayers
O-RU (Radio Unit)RF + lower physical layer (FFT, CP, beamforming)Low-PHY
O-DU (Distributed Unit)Higher PHY, MAC and RLC — real-time schedulingHigh-PHY · MAC · RLC
O-CU (Central Unit)PDCP, SDAP and RRC — split into CU-CP and CU-UPPDCP · SDAP · RRC

The O-RU and O-DU connect over the Open Fronthaul (the 7.2x split), the defining O-RAN interface that lets a radio from one vendor work with baseband from another.

Full walkthrough: O-RAN Architecture Deep Dive · the physical-layer angle: 5G O-RAN physical layer.

04 — INTERFACESThe O-RAN interfaces

InterfaceBetweenPurpose
Open Fronthaul (7.2x)O-RU ↔ O-DUThe open radio-to-baseband split — the heart of O-RAN.
F1 / E1O-DU ↔ O-CU / CU-CP ↔ CU-UP3GPP CU/DU split interfaces.
E2Near-RT RIC ↔ O-DU/O-CUNear-real-time RAN control (10 ms–1 s).
A1Non-RT RIC ↔ Near-RT RICPolicies, ML models, enrichment (>1 s).
O1Managed elements ↔ SMOFCAPS management & orchestration.
O2SMO ↔ O-CloudCloud infrastructure management.

05 — INTELLIGENCEThe RIC: xApps & rApps

The RAN Intelligent Controller is what makes Open RAN intelligent. It comes in two flavours running on different timescales:

🧠

Non-RT RIC

In the SMO, >1 s loops. Runs rApps over A1 — policy, ML training, optimisation.

Near-RT RIC

10 ms–1 s loops. Runs xApps over E2 — traffic steering, interference & mobility control.

📦

xApps

Near-real-time RAN apps — the optimisation logic, decoupled from the base station.

🗂️

rApps

Non-real-time apps in the SMO — analytics, policy and AI/ML model management.

Build intelligence: O-RAN xApps & rApps — building RAN intelligence · run it: the O-RAN lab.

06 — OPERATIONSSMO & the O-Cloud

The Service Management and Orchestration (SMO) framework manages the whole Open RAN — it hosts the Non-RT RIC and drives the O1 and O2 interfaces. The O-Cloud is the cloud platform (COTS hardware + virtualisation) on which the virtualised RAN functions actually run, managed over O2.

Together they turn the RAN into software running on general-purpose infrastructure — the basis for automation, energy saving and AI-driven operations. See it alongside SDN/NFV in the SDN/NFV lab.

07 — FAQO-RAN questions, answered

What is O-RAN?
O-RAN (Open RAN) is an open, disaggregated RAN architecture from the O-RAN Alliance. It splits the base station into interoperable O-RU/O-DU/O-CU nodes joined by open interfaces, and adds intelligence via the RAN Intelligent Controller (RIC).
Is O-RAN the same as 3GPP?
No. 3GPP defines 5G NR and the CU/DU split (TS 38.401); the O-RAN Alliance defines the open interfaces, the RIC and the management architecture on top of it.
What is the difference between O-RU, O-DU and O-CU?
O-RU = RF + low-PHY; O-DU = high-PHY, MAC, RLC; O-CU = PDCP, SDAP, RRC. They follow the 7.2x split, with O-RU↔O-DU over the Open Fronthaul.
What is the RIC?
The RAN Intelligent Controller. Non-RT RIC (in the SMO, >1 s, rApps over A1) and Near-RT RIC (10 ms–1 s, xApps over E2) make the RAN programmable and AI-driven.
What are the main O-RAN interfaces?
Open Fronthaul (7.2x), F1/E1 (3GPP CU/DU), E2 (Near-RT RIC↔RAN), A1 (Non-RT↔Near-RT RIC), O1 (management↔SMO) and O2 (SMO↔O-Cloud).
Why does O-RAN matter?
It breaks vendor lock-in and makes the RAN programmable and intelligent. The trade-off is added integration complexity and the need for rigorous multi-vendor interoperability testing.

08 — LIBRARYEvery O-RAN resource on CafeTele

Engineer-grade deep-dives, a hands-on lab, a full course and a book — grounded in O-RAN Alliance and 3GPP specifications.

Master Open RAN, hands-on

From the 7.2x split to building xApps on the RIC — a full course, a deep book, and a live lab, built by field engineers. Lifetime access from $14.99.