Put real traffic mixes through your 5G network.
Web, video, voice, IoT and gaming at once.
ABot runs both ends of every flow. The data client pushes a realistic application mix through the RAN and core, and the data server answers on N6. Low-latency L4S and URLLC probes ride the same path, so you see how they behave under real load.
Several clients, one N6 exit
Each kind of traffic has its own client and its own server endpoint. They all cross your RAN and core, and they all leave the UPF over N6 to the ABot data server.
Mixed application traffic
HTTP, video, VoIP, IoT and gaming run as one mix. Each type gets its own share and its own connection rate.
Low latency on the same path
L4S (ECT(1)/CE) and URLLC (one-way delay and RTT) run alongside the mix, not instead of it. That's where low-latency traffic gets tested for real.
iPerf and IMS beside the mix
Quick throughput checks and SIP/RTP voice each have their own server endpoint, so they never get folded into the mix profile.
Pick your topology
A complete traffic bench with no external dependencies. Good for building and tuning a mix.
Load your UPF and control plane with a realistic mix from many simulated UEs.
The data client sends through COTS handsets over Wi-Fi or USB, into your RAN and a real or ABot core.
Build a traffic mix in one feature file
Each row is one traffic profile with its own share, connection rate, client IP pool and server port. Switch the low-latency probes on or off, set the UE pool, and save from the toolbar.
Example mix
Shares always add up to 100%.
| Traffic | Transport | Workload | Share | CPS |
|---|---|---|---|---|
| HTTP file download | TCP | PCAP | 40% | 1000 |
| IoT (MQTT) | TCP | PCAP | 30% | 50 |
| Video | TCP | JSON model | 10% | 5 |
| VoIP | UDP | RTP PCAP | 10% | 100 |
| Gaming | UDP | PCAP | 10% | 20 |
Switches
Common parameters
Start UE IP and config file name are set in the feature file.
Three knobs, three jobs
Set per profile. CPS = 100 means about 100 new connections of that template every second.
How much of the mix each application takes. A separate input from CPS, so you shape the mix without touching its pace.
Applied when traffic starts and scales every profile by the same factor. Turn it up and the mix keeps its shape.
Want more load? Change the multiplier. Want a different mix? Change CPS or share.
The right traffic tool for the job
ABot isn't trying to be every traffic tool. Here's where it does the job and where something else is the better pick today.
| Tool type | Good for | Not built for |
|---|---|---|
| Throughput tools (such as iPerf) | A fast TCP/UDP link check | Application mixes, PCAP replay, L4S feedback |
| Packet generators | Crafted or stateless packets for PPS stress | Stateful application sessions, L4S feedback |
| Application QoE platforms | Deep application emulation and video/IoT QoE scoring | An integrated gNB/UPF test bench driven from the same feature files as your 3GPP tests |
| ABot Traffic Generator | ✓Application mix, L4S ECT(1)/CE and URLLC on one N6 path, with per-application gNB/UPF counters, inside your ABot test runs | Application QoE scores such as video startup, rebuffering or MOS (not offered today) |
A functional lab on four machines
Ubuntu 22.04 throughout. Software only, on hardware or VMs you already have.
ABot Test Bench
BDD framework, 5G core control plane and analytics
ABot UPF
User plane for the emulated core
ABot Data Server
L4S server, IMS and NAT
ABot Data Client
The traffic generator, on a laptop
Sized for functional testing. For sustained rates above roughly 2-3 Gbit/s, we'll size a higher-throughput lab with you.
Traffic is one step in the test, not a separate lab
On-demand Test Bench
Spin up the emulators and traffic for the run, then release the compute.
Scenario Factory
Traffic steps live in the same BDD feature files as your generated 3GPP test cases.
Core Digital Twin
Put a realistic load on the twin when you replay a field issue and prove the fix.
ABot AI
Hand the PCAPs and KPIs from a traffic run to deterministic root cause analysis.
Built for teams that carry real traffic
Service providers
Check UPF, slicing and L4S readiness under a mix that looks like your subscribers, before launch.
Network equipment vendors
Regress gNB and UPF builds against the same traffic mix in every CI run.
Integrators and labs
Drive multi-vendor setups with emulated or real UEs, without buying a separate traffic platform.
Go deeper
Put your network under a real mix
Bring your RAN or core. We'll bring the traffic.












