Part of: 4G / 5G & O-RAN
OCUDU is an open-source 5G base station. This page explains what it is, how its parts are laid out on COSMOS, which COSMOS hardware it uses, and which tutorial to take first.
A mobile network has three parts: the phone (the UE), the base station (in 5G, the gNB), and the core network, which checks the SIM, hands out an IP address and forwards traffic to the internet. OCUDU is the base station. It turns IP packets from the core into a radio signal and back, and it runs as an ordinary program on a Linux server. It is built on the srsRAN Project code base, is permissively licensed, and needs no licence server.
On COSMOS, OCUDU is paired with the Open5GS core and with either a software UE (srsue, from the older srsRAN 4G project) or a commercial 5G modem. The same base-station program runs in every OCUDU tutorial; what changes from one tutorial to the next is only what sits between it and the UE: nothing at all, a radio, or a separate O-RAN radio unit. That makes OCUDU a good platform to learn on, because each step adds one piece of hardware to a setup you have already seen working.
A 5G base station is divided into functional units. 3GPP splits it into a central unit (CU), which holds the upper protocol layers and the links to the core, and a distributed unit (DU), which holds the real-time layers (scheduling and the upper physical layer). The CU is split again into a control-plane part (CU-CP) and a user-plane part (CU-UP). The O-RAN Alliance adds the radio unit (RU), which holds the lowest physical layer and the RF, and defines the fronthaul between DU and RU at split 7.2x. 5G SA fundamentals explains the layers and O-RAN and the 7.2x fronthaul explains the split.
OCUDU's gnb program contains the CU-CP, CU-UP and DU in one process. The radio is chosen in its YAML configuration file, so the same program covers every modality.
| Part | What it does | OCUDU component | Where it runs on COSMOS |
|---|---|---|---|
| CU (CU-CP + CU-UP) and DU | radio protocols, scheduling, upper physical layer, links to the core | gnb, one process |
a COSMOS server (/opt/ocudu/build/apps/gnb/gnb) |
| Radio | lower physical layer and RF | no radio: ZMQ sockets to a software UE · over the air: ru_sdr drives a USRP · O-RAN 7.2: ru_ofh talks to a separate O-RU |
no radio: the same server · over the air: a USRP N310 in sb1 · O-RAN 7.2: a commercial O-RU on the fronthaul network |
| O-RU management (M-Plane) | configures an O-RU over NETCONF | separate tools, not part of gnb: ocudu_o1_adapter (client) and ocudu_netconf (simulated O-RU) |
any server; the O-RU in the M-Plane tutorial is simulated |
| RAN controller link | lets a near-real-time RIC read measurements | E2 agent inside gnb (E2SM-KPM) |
the gnb server, with a RIC on another host |
| Core | authenticates the UE, assigns its IP address, forwards its traffic | Open5GS, native services | the same server as gnb |
| UE | the phone | srsue software UE (no-radio tutorial) · Quectel RM520N-GL modem · Amarisoft lteue simulated UE |
srsue on the gnb server; the modem and lteue on a separate UE node |
All OCUDU tutorials use test PLMN 00101 and UE pool 192.168.100.0/22 (gateway 192.168.100.1, with internet access). The UE pool is IPv4 only: OCUDU refuses a dual-stack (IPv4v6) PDU session, which the over-the-air tutorial shows how to handle.
ocudu.ndz with omf load. It points at the newest promoted build; on 2026-10-20 that was ocudu-20261020, which carries the OCUDU 26.10 release, srsue, Open5GS, ProtO-RU (a software O-RU) and the O-RU tooling used by the 7.2 tutorial. It is built to run on every COSMOS server CPU class.rrail (Arm Grace CPU + Hopper GPU), runs OCUDU with NVIDIA's GPU physical layer: see OCUDU on NVIDIA Aerial.sb1, reached over the server's data network, with a Quectel modem on a UE node in the same domain.osc, sb1 and rrail, PTP time from the fronthaul switch, and a commercial O-RU from the O-RU pool (Benetel RAN650, LiteOn FlexFi, Foxconn RPQN-7801). A 7.2 server needs CPU isolation, which the image deliberately does not carry because the right cores differ per server; see Preparing a real-time RAN host.| Tutorial | Radio? | Domains | Time | What you learn |
|---|---|---|---|---|
| ocudu-soft | no | any | 20–30 min | what a working 5G network looks like: core, base station and software UE on one server; the attach milestones in the logs; measuring throughput |
| ocudu-ota | yes: USRP N310 + Quectel modem | sb1 |
60–90 min | running a real cell over the air; attaching a commercial modem and the Amarisoft lteue simulated UE; real-time sample streaming to a radio |
| ocudu-72 | yes: commercial O-RU + Quectel modem | osc, sb1, rrail |
60–90 min first run | the O-RAN 7.2 split: an O-DU on a server driving a commercial radio unit over the fronthaul; host preparation; restoring the O-RU's known-good state |
| ocudu-sdcore | no (zmq profile; n310/b210 optional) |
osc, sb1 — any two servers |
30–45 min first run | a cloud-native core (Aether SD-Core on Kubernetes) on one server and the gNB on another, N2/N3 across the data network; moving a Kubernetes core to a new host; provisioning SIMs from the COSMOS SIM deb |
| ocudu-mplane | no (simulated O-RU) | any | 20 min | the O-RAN M-Plane: provisioning an O-RU over NETCONF, deriving the DU's fronthaul settings from it, and moving its carrier to a new frequency |
Step-by-step procedures that are not yet packaged as cosmos-tutorial runs (they are run by hand, and may be older):
Measured throughput for every OCUDU build, by radio and CPU platform, is on OCUDU performance by build.
Glossary
- gNB — the 5G base station. CU / DU — its central and distributed units (3GPP).
- RU / O-RU — the radio unit; "O-RU" when it follows the O-RAN specifications. O-DU — a DU that drives an O-RU.
- 7.2x split / fronthaul — the O-RAN split point inside the physical layer, and the Ethernet link between O-DU and O-RU.
- M-Plane — the O-RAN management plane: NETCONF over SSH, used to configure an O-RU.
- ZMQ — a software message transport; here it carries radio samples between
gnbandsrsueinstead of a radio.- PLMN — the network identity (
00101on COSMOS). PDU session — the UE's data connection, which gives it an IP address.- E2 / near-RT RIC — the interface and the controller that read measurements from a live base station.
How every OCUDU build performed, round by round, with one chart per radio, carrier and CPU platform (13 series, newest round 2026-11-02), is on OCUDU performance trend by build. Every weekly rebake and test round adds to it.
docs.ocudu.org.ocudu_o1_adapter and ocudu_netconf.srsue, the software UE.ocudu.ndz image.Author(s): COSMOS team · Tags: ocudu, srsran, 5g, sa, oran, overview