Why the Pentagon Is Funding OCUDU to Open‑Source 5G/6G Base‑Station Code
The article analyses the U.S. Department of Defense’s launch of the OCUDU ecosystem to open‑source 5G/6G CU and DU code, explaining the strategic push against Chinese market dominance, the shortcomings of previous Open RAN attempts, the chosen permissive BSD license, and the prospects for a Linux‑like telecom stack.
Background and DoD motivation
Chinese vendors, especially Huawei, have captured a large share of the global telecom market, while most Western equipment makers have collapsed, leaving only Ericsson and Nokia. From the Pentagon’s perspective, the communications network is a strategic nerve‑center for future warfare and cannot rely on “untrusted” black‑box equipment.
Open RAN experience
Open RAN was intended to break vendor lock‑in by opening RAN interfaces, but after eight years the global Open RAN market share remained below 5 %. Start‑ups such as Mavenir and Parallel struggled to survive, indicating a commercial failure.
OCUDU initiative
The U.S. Department of Defense announced the creation of the OCUDU ecosystem foundation, led by FutureG office director Tom Rondeau. OCUDU adds an “O” to the traditional CU (central unit) and DU (distributed unit) to signal the intent to open‑source the core 5G (and eventually 6G) base‑band code, creating a “Linux system for mobile communications”.
OCUDU open‑sources the DU and CU software that can run on generic hardware; the radio front‑end (RRU/AAU) remains proprietary because it requires specialized hardware.
Key contributors and licensing
SRS (Software Radio Systems) – provides the core RAN software stack (srsRAN). The DoD plans to acquire the code in 2025 and contribute it under a BSD‑3‑Clause license.
DeepSig – supplies AI‑driven neural‑receiver and spectrum‑sensing modules.
Nvidia and AMD – provide GPU and CPU/NPU acceleration for AI workloads.
Nokia and Ericsson – required participants, contributing legacy expertise.
AT&T , Verizon and SoftBank – act as testbeds for early deployments.
Linux Foundation – hosts the project and provides open‑source governance.
Licensing model
OCUDU adopts a permissive BSD‑3‑Clause license, allowing anyone to use, modify, and commercialise the code without having to release proprietary extensions.
Security rationale and MOSA compliance
The DoD argues that opacity is the greatest security risk. Since 2019, U.S. defense procurement must follow MOSA (Modular Open Systems Approach), which mandates five strict criteria: decoupling, clear interfaces, open standards, interoperability (“blind‑plug”), and full access to documentation and source code. By exposing the entire code base, OCUDU satisfies MOSA and enables global developers to audit, find vulnerabilities, and harden the stack.
From module‑level to code‑level transparency
Earlier Open RAN efforts opened only module interfaces; OCUDU opens the full software stack, turning base stations from black boxes into white‑box, Linux‑like platforms. This accelerates innovation: prototype verification, AI feature iteration, and algorithm testing can occur in days or weeks instead of years.
Expected impact on the telecom ecosystem
OCUDU aims to provide a common open‑source base for 5G and future 6G, lowering entry barriers for operators and vendors, and shifting development from the multi‑year 3GPP standard cycle to an open‑source cadence measured in days and weeks.
Open‑source ecosystem considerations
The BSD‑3‑Clause license lets vendors layer proprietary AI algorithms or hardware‑acceleration modules on top of the OCUDU core without exposing their own code, encouraging commercial adoption while preserving openness of the foundational stack.
Signed-in readers can open the original source through BestHub's protected redirect.
This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactand we will review it promptly.
DeepNoMind
I’m Yu Fan, a tech leader with deep technical expertise and managerial vision. Formerly at Motorola, now at Mavenir, I’ve led teams for years, focusing on backend architecture and cloud-native solutions, staying abreast of AI and other frontier fields, and championing personal growth and lifelong learning.
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.
