3GPP has been formally integrating satellite access into 5G since Release 17 in 2022, when the first enforceable NTN specifications – covering both 5G NR and IoT devices on GEO, LEO, and MEO orbits – moved from study notes to a real standard. Releases 17 and 18 established the foundational architecture, with products already shipping from Qualcomm, MediaTek, and Skylo. Release 19, frozen in December 2025, resolved a pivotal debate over satellite payload design in favor of regenerative payloads – putting a full 5G base station on the satellite itself – unlocking inter-satellite links and store-and-forward operation for the most demanding coverage scenarios. Commercially, the market is moving fast: the global 5G NTN market is projected to grow from $7.65 billion in 2025 to nearly $114 billion by 2034, with IoT NTN alone forecast at a 38.2% CAGR. Looking ahead, 3GPP’s Release 20 6G studies are now underway with the explicit goal of making NTN a native part of 6G architecture – not a retrofit, but a co-designed foundation.
There was a time when satellite communication meant clunky terminal equipment, eye-watering latency, and a bill that made your CFO wince. That world still exists – but alongside it, a parallel one has taken shape, where a standard smartphone connects to a low Earth orbit (LEO) satellite without special hardware, using the same 5G protocols that power your city’s mobile network.
That shift is the result of years of deliberate standards work inside the 3rd Generation Partnership Project (3GPP). And right now, that work is at a genuinely interesting inflection point. The global 5G NTN market was valued at approximately $7.65 billion in 2025 and is projected to approach $114 billion by 2034 at around 35% annual growth. That’s a market signal saying this story has moved well past the white paper stage.
From Study Item to Real Standard
3GPP’s NTN work started with Release 15 in 2018 – but calling it “NTN” then would be generous. Releases 15 and 16 were study items: channel modeling, deployment scenarios, and working out what it would take to run 5G over a satellite link. The physics are non-trivial. A LEO satellite moves at roughly 7 km/s relative to the user, creating Doppler shifts that dwarf those of a terrestrial network. Propagation delays are long enough to break timing assumptions built into the 5G air interface.
Release 17, frozen in mid-2022, changed everything. It was the first release to include normative NTN specifications – actual, enforceable requirements, not just study notes. It covered NR-NTN (5G New Radio for satellite use) and IoT-NTN (NB-IoT and eMTC for low-power devices), targeting both GEO and LEO/MEO constellations. The 3GPP NTN Standards package won Via Satellite’s Satellite Technology of the Year award in 2024 – a sign of how the broader industry views the work.
What’s Locked Down: Releases 17 and 18
The core technical challenge in Release 17 was synchronization: keeping a device in sync with a network when both the satellite and the cell boundary are constantly moving. The solution was elegant – devices use their own GNSS position data plus satellite ephemeris information to self-synchronize, pre-compensating for Doppler offset and propagation delay. That design kept changes to the 5G air interface minimal, which matters enormously for the device ecosystem.
Release 18 – the start of 5G-Advanced – built on this in meaningful ways: it extended support to FR2 (Ku and Ka-band) for VSAT terminals on aircraft and vessels, improved TN-NTN handover management, and introduced power-saving enhancements for IoT devices in discontinuous coverage. Skylo has deployed Release 17 NB-IoT NTN commercially. Chipsets supporting Release 17 NTN are now shipping from Qualcomm and MediaTek.
The Architecture Debate That Defined Release 19
Release 19 is where things got contentious. The argument: should a satellite carry a full gNB (a complete 5G base station) or just a gNB-DU, with the central unit staying on the ground? After a full year of debate across four TSG RAN meetings, the community settled on the full gNB, also known as a “regenerative” payload. A gNB on board natively supports inter-satellite links, inter-satellite mobility, and store-and-forward operation for delay-tolerant communications. The gNB-DU path would have required the feeder link to stay live at all times, and with 6G RAN studies (expected in Release 20) likely moving away from the CU-DU split entirely, it looked like a dead end.
Release 19 was frozen in December 2025 and also added RedCap device support, Multicast and Broadcast Services (MBS), and early steps toward reducing GNSS dependency. In September 2024, Iridium announced its NTN Direct service would be built on Release 19 NB-IoT NTN specs, calling it the world’s first truly global 5G NB-IoT service. Industry commitment to a release still in progress is a strong signal that these standards aren’t theoretical.
| PRO TIP Know the Difference Between Transparent and Regenerative Payloads Before Specifying Your Architecture Transparent (bent-pipe) payloads, standardized in Releases 17 and 18, keep the gNB on the ground. They’re simpler to deploy and upgrade but require a live feeder link. Regenerative payloads (Release 19+) put the full gNB on the satellite, enabling inter-satellite links and store-and-forward operation – critical for polar coverage and delay-tolerant IoT. If your network needs to operate in feeder-link-denied conditions (remote maritime, polar routes, deep rural), nail down which payload model the satellite operators you’re evaluating actually support. The two architectures have materially different implications for backhaul, latency budgets, and service continuity. |
What the Market Is Doing Right Now
Standards progress is happening against a backdrop of rapid commercial activity. In February 2025, Eutelsat, MediaTek, and Airbus completed the first successful 5G NTN connection over OneWeb’s LEO satellites. Verizon launched satellite texting to Android devices in March 2025. SpaceX now operates over 10,000 Starlink satellites in orbit as of early 2026, and AST SpaceMobile is scaling its BlueBird constellation with direct-to-device services that will eventually align with 3GPP standards. The IoT NTN segment of the satellite NTN market is forecast to grow at a CAGR of 38.2% through 2034, driven by asset tracking, agricultural monitoring, and industrial IoT use cases that terrestrial networks can’t reach.
The Road to 6G NTN
3GPP’s Release 20 6G study work is now underway, having kicked off at the end of 2025. Normative 6G specifications are expected from Release 21, with the final timeline to be confirmed at the June 2026 Plenary. The key shift: rather than adapting a terrestrial standard to accommodate satellites, the intent is for NTN to be a native component of 6G architecture from day one. EU-funded projects such as NexaSphere and 6G-NTN are already exploring what a truly unified TN/NTN system would look like. GNSS independence will also grow in importance – Releases 17 and 18 assume GNSS-capable devices throughout, and 6G NTN work will push toward hybrid positioning that doesn’t rely on a separate navigation system.
What This Means for System Integrators and IT Teams
If you’re a system integrator in telecom, now is the time to get ahead of the curve. Track which satellite operators have committed to Release 17+ 3GPP NTN specs versus those using proprietary approaches – the migration path between the two is not trivial, and operators locked into proprietary stacks today may face costly transitions by 2027. Get clear on the distinction between transparent and regenerative payloads, as it has real implications for your ground-segment design, core-network integration, and service-continuity architecture.
If you’re in IT or enterprise networking – particularly in maritime, energy, agriculture, logistics, or aviation – the NTN roadmap belongs in your connectivity strategy now, not later. Release 17 and 18 devices are shipping. The ability to manage devices across both terrestrial and satellite access under a single framework is no longer speculative. Ask your managed service providers specifically whether their satellite offerings are on track to align with 3GPP standards. The answer tells you everything about their long-term interoperability posture
Frequently Asked Questions
Q: What is a Non-Terrestrial Network (NTN), and how does it differ from a standard 5G network?
A: An NTN is any network that uses airborne or space-based infrastructure – satellites, high-altitude platforms, or drones – as part of the radio access layer. What makes 3GPP NTN different from older satellite systems is standardization: the same 5G protocols used on a terrestrial cell tower are adapted to run over a satellite link. That means NTN-capable devices don’t need separate chipsets or special hardware – just software and chipset support for the extended timing and Doppler compensation the satellite environment requires.
Q: Which 3GPP release should I be tracking if I’m planning an NTN deployment today?
A: For most deployments starting now, Release 17 is the practical baseline – it’s the first release with normative NTN specifications, and devices and chipsets are already shipping against it. If your use case involves higher-bandwidth terminals (aircraft, vessels, or fixed premises), Release 18 adds support for FR2 (Ku/Ka-band). Release 19, frozen in December 2025, is the one to watch for regenerative payload architectures and RedCap device support – the ecosystem around it will mature through 2026 and 2027.
Q: What’s the practical difference between a transparent payload and a regenerative payload satellite?
A: A transparent (bent-pipe) satellite relays radio signals between the device and a ground station; all 5G baseband processing happens on the ground. It’s proven and easy to upgrade, but it requires a continuous feeder link to function. A regenerative satellite runs a full 5G base station (gNB) on board, processing signals in orbit. That allows it to operate independently of a live ground link, support inter-satellite routing, and handle store-and-forward traffic for remote or delay-tolerant applications. The right choice depends entirely on your coverage requirements and tolerance for feeder-link outages.
Q: Does 3GPP NTN support IoT devices, or is it primarily aimed at smartphones and broadband terminals?
A: Both. Release 17 introduced IoT-NTN alongside NR-NTN, covering NB-IoT and eMTC (LTE-M) device classes over satellite. These are low-power, low-data-rate protocols designed for sensors, trackers, and remote monitoring equipment – exactly the asset classes that terrestrial networks can’t reliably reach. Skylo’s commercial deployment is one real-world example. Release 19 adds RedCap (Reduced Capability) device support, which sits between IoT-NTN and full NR-NTN in terms of capability and cost, further broadening the addressable device range.
Q: How does 6G change the NTN story? Isn’t 5G NTN still being rolled out?
A: Both things are true at once. 5G NTN is being actively deployed, and the Release 17/18/19 ecosystem is just getting started commercially. At the same time, 3GPP has begun Release 20 study work for 6G, with the explicit goal of making NTN a native part of the 6G architecture rather than a retrofit. That matters because it changes the design starting point entirely – rather than patching satellite access onto a terrestrial system, the two environments will be co-designed from the outset. For most operators and integrators, 5G NTN is the near-term investment; 6G NTN is the long-term architectural direction to keep in view.
Q: Where can I go deeper on the intersection of private wireless, sovereign AI, and enterprise connectivity?
A: The PrivateLTEand5G.com Connected AI Edge Virtual Bootcamp Series runs from May through December 2026 – nine focused sessions designed specifically for enterprise IT/OT leaders, systems integrators, and MSPs navigating exactly these decisions. Sessions cover private 5G architecture, IT/OT convergence, AIoT device ecosystems, programmable networks, and vertical-specific deployments across manufacturing, logistics, agriculture, and higher education. Every bootcamp ends with a Pro Tips segment – practitioner-sourced, immediately actionable, and compiled into a downloadable reference card after each session. The series is built for people making real deployment decisions, not vendor roadmap watchers. Sessions are recorded and available on-demand to registered attendees. If the compliance and infrastructure questions raised in this article are live issues for your organization or your clients, this is the community and the curriculum to work through them with. View the full program and register at PrivateLTEand5G.com.
