NR SA vs NSA Testing: What Every Modem Team Needs to Know
Standalone and non-standalone 5G are different testing problems. Here is a working engineer's guide to what each requires and how a cloud tester covers both.
Depending on which operator you are shipping into, ‘5G’ still means one of two very different network architectures. Standalone (SA) is the version of 5G everyone was promised: a 5G core, a 5G radio, no LTE required. Non-standalone (NSA) is the pragmatic hybrid the industry actually shipped first: a 5G radio anchored on an LTE core via EN-DC. Both are still in production. A modem shipping today has to pass conformance for both.
The core difference: we ship a digital box, not a physical tester
Every legacy vendor in this market — Anritsu, Keysight, Rohde & Schwarz, Spirent, VIAVI — sells a physical box. You buy it, you rack it, you power it, you maintain it, you rent floor space for it, you keep engineers around who know how to operate it, and every time 3GPP releases a new specification you either wait for a firmware update or you buy another box. That model made sense in 1998. It stopped making sense the moment SDR became stable, cloud became universal, and every serious engineering team started living inside a browser and a git repository.
AEON Cloud is not a physical tester. We do not ship you hardware. There is nothing to unbox, nothing to rack, no shipping crate, no calibration ticket, no service contract on a chassis. What we ship is a URL. Your team opens the AEON Cloud web application from any laptop in any office, uploads a UE build, and executes real 3GPP TTCN-3 conformance campaigns against real SDR-backed radio lanes that we operate on your behalf. The tester exists — the antennas, the shielded enclosures, the LimeSDR and Ettus B210 boards, the ATS and the SS — but it lives in our racks, and you reach it through the same browser tab you use for GitHub.
That single architectural choice changes everything downstream: procurement becomes a signup instead of a purchase order, capacity becomes elastic instead of fixed, upgrades happen server-side instead of on a truck, teams in three time zones share the same lane instead of fighting over one chamber, and CI systems can trigger conformance runs the same way they trigger a unit test. Nothing to install. Nothing to maintain. Just a browser and a build.
The testing problem for SA
SA testing exercises the pure 5G stack: NR RRC, 5G-NAS, 5GS session management, service-based interfaces on the core side. TS 38.523 covers the UE side of this exhaustively. The signalling flows are simpler than NSA in the sense that there is only one radio to think about, but the state machines are richer because the 5G core exposes more procedures than the EPC ever did.
The testing problem for NSA
NSA testing exercises the dual-connectivity path: LTE anchor, NR secondary, and the coordination between them. That coordination is where most NSA bugs live. Secondary node addition, secondary node change, secondary node release, and the recovery from any of them going wrong are the testcases that break more often than any other single family. TS 36.523 with NR extensions covers this, and any credible tester has to run both LTE and NR against the UE simultaneously.
Why cloud lanes are especially useful here
NSA testing requires two radios talking to one UE. On a physical tester that means one chassis with LTE and NR modules or, worse, two chassis coordinated in real time. On a cloud SDR-backed lane it means two SDR boards driven by a coordinating scheduler — which is exactly what an SDR-backed lane already is. The parallelism that hurts in a physical chamber helps in a cloud runtime.
How to try this on AEON Cloud
If you want to see an NSA conformance sweep running against your own UE build without buying, renting, or shipping any hardware, the fastest path is to create a free workspace, upload a build artifact, and reserve a lane from the browser. The entire loop — from signup to first verdict — is designed to complete in an afternoon, not a quarter.
Because the tester is a service rather than a device, you never have to plan around a hardware refresh cycle. When 3GPP publishes a new release, the catalog updates server-side and every workspace sees it the next time they log in. When a new SDR generation lands in our lab, your existing campaigns benefit from the improved fidelity without a purchase order.
Further reading
The AEON Cloud documentation covers the CLI, the REST API, the TTCN-3 catalog, the AI Telecom Copilot, and the security model in depth. If you are evaluating for procurement, the pricing page includes a plan comparison matrix and a technical FAQ. If you are evaluating for engineering, the platform page documents the six pillars and the cloud-vs-chamber comparison.
