Roadmap 2026: 5G-Advanced, NTN, and RedCap on a Browser-Accessed Tester

The 3GPP treadmill does not stop. 5G-Advanced (Release 18 and 19) is landing in commercial products. Non-terrestrial networks (NTN) are being tested against real satellites. Reduced-capability devices (RedCap) are opening a whole new device class between LTE-M and full NR. Each of these would traditionally have arrived as a new hardware line item on a chamber vendor's price list.

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.

How new releases land on a cloud tester

Every new release, every new feature, every new testcase category lands on AEON Cloud server-side. Your workspace inherits it the next time you log in. There is no purchase order, no shipping crate, no chamber upgrade, no firmware pin migration. If your device is Release 18-capable, you can run Release 18 testcases against it the day the catalog updates.

Why this compounds

The organisational compounding is more important than any single release. A team that has stopped thinking about hardware refresh cycles has more attention left for the actual product. A team that has stopped scheduling chambers has more calendar space for engineering. A team that has stopped filing tickets against a tester vendor has more energy for its own users. The advantage is not one line item — it is that every future release is somebody else's operational problem.

How to try this on AEON Cloud

If you want to see the latest release catalog 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.