Release 26.10 of the OCUDU open source RAN stack introduces satellite connectivity alongside a set of new 5G capabilities, marking the community's most notable functional expansion since the project's earlier milestones.

The update, detailed by Light Reading, extends the open source radio access network code base to support non-terrestrial network (NTN) links — the satellite-based connectivity model that 3GPP has been standardizing since Release 17. Until now, open source RAN implementations have focused almost entirely on terrestrial deployments, leaving direct-to-device satellite work to proprietary vendors such as Apple's Globalstar partnership, AST SpaceMobile and Starlink's T-Mobile service.

What does the new release actually contain?

According to the report, OCUDU 26.10 bundles two broad categories of change:

• Satellite connectivity support, bringing NTN concepts into the open source RAN pipeline for the first time in this release line
• Additional 5G capabilities across the stack, extending the functional baseline that operators and integrators can build on without licensing proprietary RAN software

The release is the work of the community's contributing members rather than a single vendor, which is the operating model open RAN advocates have promoted as an alternative to the concentrated supplier market dominated by Ericsson, Nokia, Huawei and ZTE.

Why satellite support matters for open RAN

Satellite connectivity has moved from fringe technology to mainstream operator strategy over the past three years. Mobile network operators are increasingly treating NTN as a coverage-extension layer for rural and maritime regions where terrestrial cell buildout is uneconomic. Standardization work in 3GPP has given the approach an interoperable foundation, and vendors have rushed to claim NTN readiness.

Bringing satellite support into an open source RAN stack changes the commercial equation in one specific way: it gives smaller operators, research bodies and neutral-host providers a code base they can inspect, modify and deploy without negotiating NTN features into a proprietary contract. That stands apart from vendor marketing claims of "satellite-ready" platforms, where the actual depth of NTN integration often remains opaque to buyers.

Commercial reality versus community ambition

Open source RAN remains a smaller part of the market than its supporters envisioned when the O-RAN movement gained regulatory backing in the US and EU. Large operators continue to run the majority of live networks on conventional vendor equipment, and open RAN wins have clustered around greenfield deployments, private networks and a handful of high-profile tier-one builds.

A release like 26.10 narrows the functional gap between open source stacks and commercial RAN portfolios. It does not close the operational gap — integration, testing and carrier-grade support remain the practical barriers that community code alone does not solve.

For telecom engineers, the most concrete takeaway is that NTN experimentation no longer requires a proprietary sandbox. Labs and operators evaluating satellite-direct-to-device architectures can now prototype against an open, community-maintained code base that tracks the relevant 3GPP standards direction.

The community's next releases will show whether satellite support matures from an initial implementation into deployment-grade functionality, and whether operators move it from trial environments into production planning.