Connect your UE to AEON Cloud
The three ways to attach a device under test: upload a build image, run the UE launcher against a remote lane, or tunnel a physical UE from your bench.
6 min read
There is no physical tester on your side, but the UE still has to reach the lane. AEON supports three attachment models. Pick based on where your UE stack runs.
Model A — hosted software UE
Your UE is software (srsUE, OAI UE, or your own stack compiled for x86/ARM). Push it as a build and we run it inside the lane, cabled to the SDR. Lowest latency and fully deterministic. This is the default for open-source UE work.
aeon builds push ./srsue-bundle.tar.gz --tag main aeon exec run --suite NR_5GS_Registration --build main
Model B — remote UE over tunnel
Your UE runs on your bench (a dev board, a modem module, a reference phone). The AEON agent creates an authenticated tunnel so the lane drives your device over IP while RF terminates locally.
aeon tunnel up --lane eu-west-1/lime-03 --local-ue 192.168.10.24:9000 aeon tunnel status
Model C — shipped device
For RF-heavy campaigns (TS 38.521) you can ship a device once and keep it racked in a shielded enclosure. It becomes a persistent target you address by ID from CI, indefinitely, without ever touching a chamber yourself.
Choosing a model
| Need | Model |
|---|---|
| Open-source UE, protocol conformance | A — hosted software UE |
| Proprietary modem on your own bench | B — tunnel |
| RF / RRM conformance, long-lived target | C — shipped device |
Run this against a real SDR lane
The tester is a service, not a box. Push a build, reserve a lane, get a verdict.