What is the OCUDU Ecosystem Foundation?
The OCUDU Ecosystem Foundation is a collaborative program hosted by the Linux Foundation dedicated to accelerating open, secure, and interoperable Open RAN CU/DU implementations. OCUDU curates reference architectures, conformance tooling, and deployment playbooks while operating community CI and interoperability labs to help the industry move from pilots to production.
What does “OCUDU” stand for, and what problem is it solving?
OCUDU stands for Open Centralized Unit Distributed Unit; will serve as the open source foundation layer for next-generation RAN systems, enabling interoperability, AI-driven orchestration, and real-time optimization across distributed and cloud-native radio networks.
What is the OCUDU technical project vs. the OCUDU Ecosystem Foundation program?
The OCUDU Ecosystem Foundation will house the OCUDU Technical project and other associated open source projects over time. The Foundation will create a public-private commercial and research ecosystem and an open source stack for Open Source CU and DU (part of Open RAN).
What does “6G in Code” mean in practice?
With the ever increasing pace of innovation in the technologies related to 6G, including AI, it is no longer feasible to have long phases of standardization followed by implementation. In order to deliver the promise of 6G, engineers must create rapid prototypes, fail fast and reiterate until reaching the optimal solutions. The availability of software such as OCUDU enables engineers to start with a working code base, add the latest and greatest developments, and iterate quickly towards what will become the architecture that will define 6G.
What gaps does OCUDU address that existing Open RAN efforts do not?
OCUDU provides one of the most complex pieces of the RAN architecture that is feature rich, has transparent and modifiable source code, with a permissive open source license. Previous initiatives fell short from addressing all these three aspects together.
What CU/DU components are in scope (and what is explicitly out of scope)?
For the first few releases, the focus is on the CU and DU components. Other components of the O-RAN architecture such as SMO, RIC, RU are out of scope for the time being as there are already good open source solutions for these components coming from LF Networking and the O-RAN Software Community.
Does OCUDU include reference architectures and “super blueprints”? What are those?
The OCUDU project provides the software required to implement the CU/DU components of the RAN. Adjacent Linux Foundation projects, such as the “LFN Super Blueprints” are beginning to work on end-to-end architecture integration reference implementations (also called ‘Super Blueprints’). Those will provide a collection of additional OSS components, including the packet core, and the necessary software to build and deploy the end-to-end solutions (scripts, playbooks, configurations, etc.).
How does OCUDU enable AI-driven orchestration and real-time optimization?
AI-driven orchestration and optimization can be implemented either internally inside the CU/DU components or through its external interfaces towards the Near RT and non-RT RICs. AI Agents and applications running as xApps or rApps may perform orchestration actions of real-time resource management to the CU and DU through the O1 and E2 interfaces. Additionally, since OCUDU is fully open sourced with a permissive license, developers can implement AI based functionality inside the CU/DU such as Massive MIMO & Beamforming Optimization, Real time resource scheduling, and Dynamic spectrum sensing.
What kinds of AI-enabled use cases does OCUDU prioritize?
Being a community driven initiative, OCUDU is not prioritizing one use case over another. Any organization or individual may implement the functionality related to the use cases of interest to them. Some of the more popular use cases discussed in the context of AI for RAN include Massive MIMO & Beamforming Optimization, Real time resource scheduling, and Dynamic spectrum sensing.
How will you ensure multi-vendor interoperability?
By nature, the OCUDU community and ecosystem has representation from various industry players. No one entity is ‘in full control’. The ecosystem is neutrally hosted by the Linux Foundation and uses the best practices for meritocracy that were curated by the LF over many years and deployed successfully in other ecosystems.
How will OCUDU address security requirements for critical infrastructure?
OCUDU will adopt the tools, frameworks and methodologies developed by the OpenSSF foundation, including, but not limited to, the OSPS Baseline that brings together guidance from standards like the NIST SSDF, the EU Cyber Resilience Act, and ISO 27001. It turns these into clear, outcome-focused controls that maintainers and contributors can use in day-to-day work.
Who can participate—members only or open community?
Participation in the OCUDU technical open source project is open to all. Any individual or organization may make contributions in the form of code, requirements, test cases, documentation or any other technical contribution. Participation in community discussions over mailing lists and messaging tools is also open to all. Some of the non-technical aspects of the ecosystem may be limited to members only, and that may include participation in product certification, research, and other activities.
What are the roles of government, industry, universities, and labs?
The unique blend of entities in the OCUDU ecosystem allows for various types of contributions that together strengthen the project. There is strong participation from government entities acting as end users and providing requirements driven by their unique use cases. Industry participants provide the domain expertise by contributing features and enhancements, test and validation know-how and other development resources. Researchers in universities use OCUDU as a substrate for cutting edge innovation and contribute the results of their work as new code. Integration and testing labs provide the opportunity to test the interoperability of OCUDU with other RAN and core equipment, making sure it is production-ready.
Is there a path for startups, researchers, or individual contributors to engage?
Yes! Organizations of all sizes are encouraged to join and get involved in any way they see fit, be it line of code, documentation, tests, use cases, requirements or anything of the sort. Individual contributors who are excited about open RAN are also welcome.
How does OCUDU complement other open source RAN stacks like Duranta?
OCUDU provides a production-ready path for the Centralized Unit (CU) and Distributed Unit (DU) components of the RAN. While it can be deployed alongside projects like OSC and Aether, it fills a specific niche in the transition from research to commercialization.
Key differentiators include:
- Development Path: OCUDU utilizes seed code from the srsRAN project, serving as the primary platform for the future evolution of that codebase.
- Research vs. Commercialization: While the Linux Foundation’s Duranta project offers CU and DU implementations, it is primarily optimized for academic and experimental research.
- Production Focus: Developers typically start with Duranta for initial experimentation; however, as functionality matures, OCUDU provides the stable, robust foundation required for building commercial-grade products.
- A Thriving Research Ecosystem: Duranta already benefits from a vibrant and established research community. Our primary goal is to continue fostering and growing this ecosystem to ensure it remains a hub for cutting-edge development.
Choosing Your Starting Point: The right project often depends on your specific research focus. For instance, researchers specifically targeting AI-RAN (Artificial Intelligence for Radio Access Networks) may find OCUDU’s specialized architecture more aligned with their goals, while others may prefer Duranta’s existing framework for broader research.
Alignment Through “Cross-Pollination”: While there are no plans for a formal merger, both projects reside under the Linux Foundation (LF) umbrella. This allows for natural “cross-pollination,” where the two projects will likely see increased technical alignment and shared innovation over time.
What open source license(s) will OCUDU use?
OCUDU code is available under the BSD-3-Clause-Open-MPI permissive license ensuring end users and developers can leverage the code for commercial and non-commercial purposes.
How do I contribute (code, tests, docs, integration, labs)?
Details about code contributions could be found at the GitLab repository. To discuss contributing labs and other resources please join the project mailing list.
Is this intended for global adoption and deployments outside the U.S.?
Yes. Ecosystem participation is not limited to the U.S. only, and technical contributions to the project are welcome from anyone, anywhere in the world.
How does OCUDU ensure neutrality and avoid vendor lock-in?
OCUDU operates under the Linux Foundation’s neutral governance model, ensuring no single entity dominates the project through a meritocratic Technical Steering Committee and a formal Charter that serves as the community’s constitution. This structured oversight supports a diverse ecosystem where government entities provide requirement-driven use cases, industry participants contribute domain expertise and development resources, and university researchers utilize the platform for cutting-edge innovation. This collaborative environment is further bolstered by integration and testing labs that validate interoperability with other RAN and core equipment, ensuring that the project remains production-ready and technically robust.