Validate every O-RAN function.
Then prove the AI that runs it.
ABot tests DU, CU, RIC and SMO stacks across the control, user and management planes, simulating whatever is missing. Now it can also act as an independent referee for the xApps and rApps that make decisions on your RAN.
Any O-RAN function, real or simulated
Bring the device under test. ABot simulates the rest of the topology and drives O-RAN and 3GPP test cases across every interface.
Real and simulated, mixed
Interwork real and simulated NFs to build any wraparound topology.
Ready test repository
3GPP and O-RAN WG-compliant cases, written in English-like language.
Traffic on top
Video and IMS traffic simulation over the full end-to-end path.
Specification coverage
An xApp that steers traffic is making live decisions. Prove it gets them right.
xApps and rApps close the loop on a live RAN. ABot recreates a RAN condition with a known cause, lets your app respond, then checks the decision and its effect against deterministic evidence. All before go-live.
What gets measured
xApps
Near-RT RIC · 10 ms to 1 s- Is the E2 control decision right for the condition?
- Does it hold up under load and handover churn?
- Does it clash with another xApp on the same cells?
rApps
Non-RT RIC in SMO · over 1 s- Do A1 policies produce the intended RAN outcome?
- Are O1 configuration changes safe and reversible?
- Has the ML model drifted since the last release?
Example app types to put through the loop
Training data too, not just tests. The O-RAN WG2 AI/ML workflow says a model should be trained and tested before it's deployed. The ABot Scenario Factory generates labelled RAN and Core scenarios with a known cause, so your models learn from operational experience, not only from documents.
xApp and rApp developers
Benchmark your app on known-cause scenarios and show buyers the scorecard.
RIC and SMO vendors, SIs
Onboard third-party apps with a repeatable acceptance gate.
Operators
An independent second opinion before any app gets control of live cells.
When a multi-vendor RAN breaks, find out exactly where
ABot AI correlates artefacts from every split of the RAN and the Core with deterministic telecom engines first. The LLM only explains evidence that's already been checked.
Monolithic and disaggregated
The same analysis for a single gNB or a split DU/CU deployment.
RAN and Core interop
gNB and DU/CU interoperability with the Core, end to end.
Same answer every run
Deterministic first, so findings are repeatable and auditable.
New platform capabilities, one test stack
ORAN testing runs on the same ABot platform as our 4G/5G solution, so it shares the latest platform upgrades.
On-demand test bench
Emulators spin up for the test and release compute when it ends.
4G/5G Test Solution →Scenario Factory
AI-generated test cases and labelled scenarios for every new release.
4G/5G Test Solution →Digital twin
Replay a field issue in a sandbox and prove the fix before rollout.
4G/5G Test Solution →Built for every team in an open RAN
System integrators
Multi-vendor interop testing before and after deployment, across distributed networks.
OEMs
Wraparound testing of DUTs, with performance across MEC and edge deployment models.
Operators
Continuous E2E testing, network audits, scale tests and zero-touch test assurance.
Sample case studies
Multi-vendor DU, CU, RIC and SMO validation on the C, U and M planes, cloud-native.
Know more →Network slice analysis of multi-vendor O-RAN and 5G NFs for E2E call flow debugging.
Know more →O-RAN workload placement and performance benchmarking on OpenShift.
Know more →Go deeper
Put your xApp through the loop
Book a session to run your RIC app against known-cause scenarios.
