RF Conformance (TS 38.521) Without an RF Chamber: What SDR Can and Can't Do
An honest map of which parts of TS 38.521 belong on a shielded SDR lane and which parts still belong in an anechoic chamber.
The most common objection to cloud-based conformance testing is that it cannot cover RF. That objection is partially right and mostly wrong. TS 38.521 is not one thing; it is four parts, and the parts differ meaningfully in what infrastructure they demand.
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.
What runs cleanly on an SDR lane
The conducted parts of TS 38.521-1 and 38.521-2 — the tests where the UE is cabled to the tester rather than radiating over the air — run well on a shielded SDR lane. Transmitter power, spectrum emission, receiver sensitivity for conducted measurements, and blocker rejection all behave predictably on a calibrated SDR pair. The bulk of a routine RF regression campaign is conducted, and the bulk of it therefore fits cleanly into cloud economics.
What still belongs in a chamber
The OTA parts of TS 38.521-2 for FR1, and essentially all of TS 38.521-3 for FR2, need calibrated antennas, controlled propagation, and — for millimeter-wave — an anechoic environment with beam-steering test heads. Nothing about SDR changes those requirements. An honest cloud tester will tell you plainly which testcases it can run and which it cannot, and route the ones it cannot to a partner chamber or to your own remaining OTA infrastructure.
The right posture: hybrid, not either-or
The best-run RF programmes in 2026 use SDR-backed cloud lanes for the daily and release-candidate grind, and reserve chamber time for the pre-certification sweep and for the OTA-mandated testcases. That posture recovers most of the cost and speed advantage of the cloud while keeping full compliance where it genuinely matters.
How to try this on AEON Cloud
If you want to see a conducted TS 38.521 subset 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.
