COSMOS operates a pool of nine commercial O-RAN radio units spanning five vendors, FDD and TDD, 4T4R and 8T8R — one of the few places you can run the same O-DU/gNB stack against radios from different vendors and compare. All units speak the O-RAN 7.2x fronthaul split over 10/25 G Ethernet with GPS-traceable PTP (G.8275.1) timing.
| Unit | Vendor / model | Band | Range (MHz) | Duplex | Antennas |
|---|---|---|---|---|---|
| benetel-oru | Benetel RAN650 | n78 | 3300–3800 | TDD | 4T4R |
| foxcon-oru1 | Foxconn RPQN-7800 | n78 | 3300–3600 | TDD | 4T4R |
| foxcon-oru2 | Foxconn RPQN-4800 | n48 (CBRS) | 3550–3700 | TDD | 4T4R |
| jabil-fdd-oru | Jabil B1 (Evenstar-derived) | n1 | 1920–1980 UL / 2110–2170 DL | FDD | 4T4R |
| jabil-tdd-oru | Jabil 8T8R (Evenstar-derived) | n78 | 3450–3650 | TDD | 8T8R (25 G fronthaul) |
| liteon-oru | LITEON FlexFi Indoor | n78, n79 | 3300–3800 / 4400–5000 | TDD | 4T4R |
| corning-oruhub + corning-oru1/oru2 | Corning Everon hub + 2 remotes | n78 | 3450–3550 | TDD | 4T4R per remote |
The O-RUs park in the instrument domain and are reservable into four experiment domains: rrail, accord, osc, and sb1.cosmos. Reserving one through the portal's O-RU Scheduler moves its fronthaul VLAN so the unit appears on your domain's network for the duration — same radio, wherever your compute lives.
Each unit keeps a canonical address (same last two octets in every domain), so your O-DU configuration ports across domains by changing only the prefix.
Fronthaul timing is a GPS-disciplined G.8275.1 telecom profile tree: a FibroLan grandmaster clock disciplines the fronthaul switches, which serve PTP to every O-RU and to the servers that run your O-DU — no per-experiment timing setup required.
Pair an O-RU with an O-DU/CU on servers in the target domain (OpenAirInterface, OSC O-DU, or a commercial stack). The 5G tutorials cover working configurations; M-plane (NETCONF) details per unit are available to experimenters on request via problems@cosmos-lab.org.