Wi-Fi access points, controlled by your O-RAN RIC.

OpenWiRAN turns commodity OpenWrt access points into E2 nodes of any O-RAN-compliant Near-RT RIC. Your xApps can monitor and control Wi-Fi with the same tools they use for 5G, without changes to the RIC or to client devices.

Open source under the Apache 2.0 license.

From the radio to the xApp, over standard E2

OpenWiRAN adds three pieces to an existing O-RAN deployment. Nothing in the RIC platform changes: access points connect to it exactly like a gNB does.

Agent on the access point

Runs on OpenWrt

A lightweight Python service collects station and channel statistics from the Wi-Fi driver and hostapd, aggregates them locally, and carries out control actions.

Wi-Fi service model

Carried over E2

Wi-Fi measurements travel in standard E2SM-KPM reports and control actions follow the E2SM-RC structure, so existing RIC tooling can read them.

SDK for xApps

Runs in the RIC

A Python library gives xApps a live view of access points, radios, BSSs and stations, next to 5G cells and UEs, and turns control actions into simple calls.

What your xApps can see and do

Each access point advertises what its driver supports when it connects, and xApps subscribe only to what they need, periodically or on events.

Observe

Measurements and events, from the access point to the RIC

  • StationSignal strength, PHY rate and MCS, throughput, retries, airtime
  • RadioChannel busy, transmit and receive time, noise floor, channel and width, transmit power
  • BSSNeighbouring networks and their signal, from 802.11k reports
  • EventsAssociations, steering responses, signal or load crossing a threshold

Act

Control actions, from the RIC to the access point

  • RadioSwitch channel and width without disconnecting clients
  • RadioSet transmit power
  • StationSteer a client to another BSS with an 802.11v transition request
  • BSSAllow or deny client associations

Know when an action has taken effect

In Wi-Fi, some actions are requests: a client can take its time to move, or decline. OpenWiRAN confirms when the access point has executed an action, and reports separately when the client has actually followed it, so xApps can wait for the result or fall back to another action.

Executed
acknowledged
Took effect
client moved to the target BSS

Example xApps

Two xApps ship with OpenWiRAN to show the full loop, from telemetry to control.

Load-aware band steering

Watches how busy the 2.4 and 5 GHz radios are and moves clients between bands to balance airtime, instead of steering every strong client to 5 GHz and simply moving the congestion.

Uses channel busy time, 802.11k signal reports, 802.11v steering and admission control.

Interference-aware channel selection

Detects when transmitters outside your network take over a channel, picks a cleaner one, and moves the radio there with a channel switch announcement, so clients stay connected.

Uses channel busy, transmit and receive time, neighbour reports and channel switching.

Runs on hardware you already have

No special access points and no RIC fork.

  • Any OpenWrt board with 128 MB of RAM or moreThe agent uses only Python, the standard Linux wireless interface and hostapd.
  • Any O-RAN-compliant Near-RT RICAccess points speak standard E2AP, so they connect without modifications to the RIC.
  • Unmodified client devicesSteering relies on 802.11k/v, which most current clients support.

Reference setup

Access point
OpenWrt One, OpenWrt 25.12
Wi-Fi
Wi-Fi 6, 2.4 and 5 GHz
RIC
O-RAN SC Near-RT RIC, Release I, on Docker
Agent
Python, with pycrate for E2AP
License
Apache 2.0

Get in touch

Questions, collaborations, or a deployment you would like to try OpenWiRAN on? Write to us.

Roberto Riggio

Università Politecnica delle Marche

r.riggio@univpm.it