Part of: 4G / 5G & O-RAN
BubbleRAN is a commercial O-RAN platform that runs a complete 5G network, from radio to core to RAN controllers, as Kubernetes workloads. This page explains what it is, how it is deployed on COSMOS, what it has measured, and where the hands-on tutorial is.
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. O-RAN adds two controllers that sit beside the base station: a near-real-time RIC, which reads live measurements over the E2 interface and runs control apps (xApps), and a non-real-time RIC, which sets policy over the A1 interface and runs rApps.
BubbleRAN packages all of these. You do not start each program by hand: you describe the network you want in one Kubernetes object, and BubbleRAN's operators create, wire up and supervise the pods. The network functions themselves are open-source code bases (OpenAirInterface for the RAN, OAI-CN or Open5GS for the core, FlexRIC for the near-RT RIC) built and packaged by BubbleRAN. The platform, its images and its documentation are BubbleRAN products under BubbleRAN's licence.
BubbleRAN's control software is called Trirematics. Its operators extend Kubernetes with custom resources (CRDs):
| Part | What it does | BubbleRAN component | Kubernetes objects |
|---|---|---|---|
| Network operator | turns a network description into running network functions | Athena | Network (access, core and edge sections, slices), Element (one per network function), Terminal (a UE and its SIM), CompositionModel (the deployable building blocks) |
| Non-RT RIC and policy | accepts A1 policies from rApps and deploys the xApp that enforces each one | ODIN | PolicyJob, MonitoringJob, DynamicXApp, DynamicRApp |
| Node resources | advertises CPU sets, hugepages, fronthaul virtual functions, tunnel devices and attached O-RUs to the Kubernetes scheduler | Gaia (with its Pontus agent on each node) | node resources gaia.t9s.io/* |
| Command line | installs, inspects, tests and removes networks, terminals and policies | brc (snap br-t9s) |
wraps the objects above |
| RAN | CU, DU or a monolithic gNB, with an RF simulator or an O-RAN 7.2 fronthaul to an O-RU | OAI, BubbleRAN build (oai-ran model) |
Elements of the Network's access section |
| Core | registration, sessions, user plane | OAI-CN or Open5GS (oai-cn, open5gs models) |
Elements of the core section |
| Near-RT RIC | E2 termination; xApps connect over E42 | FlexRIC (mosaic5g model), plus a KPM monitoring xApp |
Elements of the edge section |
| UE | a software UE for the RF simulator | OAI nrUE (terminal model) |
Terminal |
| Monitoring | metrics and dashboards | VictoriaMetrics and Grafana | namespace monitoring |
Two SDKs come with the platform: the xApp SDK (C and Python, against FlexRIC; AGPL-3.0-or-later) and the rApp SDK (Python, against ODIN's A1 interface; Apache-2.0). COSMOS runs the 2026-10 SDKs (xApp SDK from oai v14.0.0-br, rApp SDK 2026.10) against the emerald cluster.
BubbleRAN runs on a dedicated Kubernetes cluster in the rrail domain, installed by hand (never omf load these servers):
srv1.rrail is the control plane and the place you work (kubectl, brc, both SDKs). srv2–srv4.rrail (2× Intel Xeon E5-2680 v4) run the cores and the monitoring stack. srv7.rrail (1× AMD EPYC 9355P, 32 cores, real-time kernel, Intel E810 fronthaul NIC, PTP from the fronthaul switch) runs every RAN and RIC pod, because the current RAN images need AVX-512.brc 3.1.3 (2026-11-10). The operators update themselves from BubbleRAN's registry, so the tutorial records the versions it was verified with.bubbleran: a monolithic OAI gNB on the RF simulator, an OAI-CN core, FlexRIC with the KPM monitoring xApp, and an emulated UE (ue1). It needs no radio, so it is where xApps and rApps are developed and tested.liteon: an OAI CU and DU driving the LiteOn FlexFi O-RU over the O-RAN 7.2 fronthaul (n78, centre 3750.24 MHz, 100 MHz, TDD), an Open5GS core and FlexRIC. Commercial 5G modems on node1.rrail attach to it over the air. The LiteOn is shared with the OCUDU and Duranta tutorials, so it is brought into BubbleRAN's configuration (its golden state) with the COSMOS tool cosmos-oru before the DU starts, and the over-the-air network runs only while it holds the radio.internet, UE pool 192.168.100.0/22, one slice (SST 1, no SD).iperf3 throughput, receiver side. Every row names the CPU platform of the host that runs the gNB or DU. Round-trip time from the modem to the internet is about 20 ms.
| Network | CPU platform | UE | DL (Mbit/s) | UL (Mbit/s) | Measured |
|---|---|---|---|---|---|
liteon (LiteOn FlexFi, n78, 100 MHz) |
1× AMD EPYC 9355P — 32 cores / 32 threads | Quectel RM510Q, TCP 4 streams | 184–262 | 45.7–54.0 | 2026-11-10, emerald (oai-ran v13.2.0-br) |
liteon (LiteOn FlexFi, n78, 100 MHz) |
1× AMD EPYC 9355P — 32 cores / 32 threads | Quectel RM510Q, UDP | 500 lossless, 562 max | 55.7 | 2026-11-10, emerald (oai-ran v13.2.0-br) |
bubbleran (RF simulator) |
1× AMD EPYC 9355P — 32 cores / 32 threads | emulated ue1, TCP 1 stream (brc test throughput) |
416–420 | 253 | 2026-11-10, emerald (oai-ran v13.2.0-br) |
bubbleran with a 100 Mbit/s A1 SLA policy |
1× AMD EPYC 9355P — 32 cores / 32 threads | emulated ue1, TCP 1 stream |
95–102 | — | 2026-11-10, emerald, ODIN 1.2.1 |
The KPM xApp in the tutorial reads the same rate from the gNB over E2: about 445 000 kbit/s of DL throughput for ue1 at 375 DL PRBs and MCS 28 (2026-11-10).
| Tutorial | Radio? | Domain | Time | What you learn |
|---|---|---|---|---|
| BubbleRAN on rrail 🔒 | liteon network: LiteOn O-RU + modem · bubbleran network: none |
rrail |
30 min, plus 30 min for the xApp and rApp | checking a BubbleRAN network with brc and kubectl; bringing the O-RU and the DU up in the right order; attaching a COTS modem and measuring throughput; Grafana; a KPM xApp on FlexRIC; an A1 SLA policy through ODIN |
🔒 The tutorial is available to members of the rrail group, who have access to the cluster. Other COSMOS users can ask the testbed staff about access.
Glossary
- gNB — the 5G base station. CU / DU — its central and distributed units. O-RU — the O-RAN radio unit, on the far side of the 7.2 fronthaul.
- Near-RT RIC / xApp — the controller that reads and steers a live base station over E2, and the apps that run on it. KPM — the E2 service model for performance measurements.
- Non-RT RIC / rApp — the policy layer above it; rApps send policies over A1. In BubbleRAN, ODIN turns each policy into an xApp that enforces it.
- CRD / operator — a Kubernetes custom resource type, and the controller that acts on objects of that type.
- RF simulator — OAI's software replacement for the radio: samples travel between gNB and UE over a socket.
brc reference, the xApp and rApp training labs and the ODIN guide. © BubbleRAN, linked and not reproduced.Author(s): COSMOS team · Tags: bubbleran, trirematics, oai, flexric, odin, oran, ric, overview