Connect srsUE to AEON Cloud
Run an open-source srsUE against a remote SDR lane on AEON Cloud — build push, lane reservation, cell parameters, and a first registration attach.
8 min read
This is the core open-source workflow: a stock srsUE, no tester in your building, a real TTCN-3 suite on the other side of an SDR lane.
1. Reserve a lane
aeon lanes list --sdr lime --available aeon lanes reserve --region eu-west-1 --sdr lime --duration 2h
2. Declare cell parameters
The lane runs the network side. Your srsUE must be told what to look for — band, SSB position, PLMN — and those values must match the campaign's PIXIT.
lane: band: n78 dl_arfcn: 632628 ssb_arfcn: 633000 scs: 30 bandwidth: 20 plmn: "00101" ue: build: srsue-main entrypoint: srsue config: ue.conf
3. Attach and verify
aeon exec run --suite NR_5GS_Registration --case TC_6_1_1_1 --follow # or a bare attach smoke test, no TTCN-3 aeon exec attach --lane eu-west-1/lime-03 --build srsue-main --follow
4. What success looks like
[PHY] cell found: pci=1 rsrp=-72.4 dBm [RRC] RRCSetupRequest -> RRCSetup -> RRCSetupComplete [NAS] Registration Request (initial) sent [NAS] Authentication Request -> Authentication Response [NAS] Security Mode Command -> Security Mode Complete [NAS] Registration Accept, 5G-GUTI assigned [RRC] state: RRC_CONNECTED verdict: PASS
Why this matters
Running a real conformance suite against an open-source UE used to require a six-figure tester and a lab. The tester is now a service you reach over HTTPS, which means an individual engineer, a university lab, or a two-person modem team can execute the same suites a tier-1 OEM does.
Run this against a real SDR lane
The tester is a service, not a box. Push a build, reserve a lane, get a verdict.