OAI 5G gNB/DU/CU/CU-CP
OpenAirInterface 5G containerized RAN network function. The container image is designed to run as a monolithic 5G gNB, O-CU, O-CU-CP, or O-DU. The application depends on the supplied configuration file
OpenAirInterface tackles the fundamental challenge of implementing a fully disaggregated, standards-compliant 5G RAN stack in open-source software, where the monolithic gNB must be split into distinct functional units — the Central Unit Control Plane (CU-CP), Central Unit User Plane (CU-UP), and Distributed Unit (DU) — communicating over the F1, E1, and N2/N3 interfaces. This disaggregation demands precise protocol-layer separation across PDCP, RLC, MAC, and PHY, along with tight timing coordination, which proprietary systems traditionally handle in closed, purpose-built hardware. Compounding this, real-time PHY processing imposes strict latency and throughput constraints that are extremely difficult to meet in general-purpose software running on commodity hardware. Interoperability presents another major hurdle, as OAI must ensure compatibility with commercial UEs, multi-vendor cores, and diverse RF front-ends while tracking rapidly evolving 3GPP specifications across Releases 15, 16, and 17 and beyond. Finally, enabling true O-RAN disaggregation — where CU, DU, and RU components from different ve
To address the challenges, OAI implements the full 3GPP NR protocol stack with modular, containerizable components that support both monolithic gNB and split F1/E1 deployments, allowing operators to mix and match vendor components in a genuine O-RAN fashion. Real-time PHY processing constraints are tackled through optimized support for USRP and other RF front-ends, alongside split 7.2x via O-RAN-compliant fronthaul interfaces. At the same time, FlexRIC integration enables near-RT RIC connectivity for dynamic, programmable resource management. On the interoperability front, OAI continuously validates against commercial UEs and open-source 5G. A robust CI/CD pipeline with automated RF and emulated testing enforces protocol correctness as the codebase evolves. Active community collaboration and interaction with industrial partners keep the implementation aligned with emerging features like HARQ enhancements, carrier aggregation, and massive MIMO.
