Your device doesn’t care whether it’s connected through a cellular tower or a satellite. It cares whether it can send the data it was built to collect.
Unfortunately, connectivity still has blind spots. A shipping container spends three weeks crossing the Pacific. A mining vehicle disappears beyond terrestrial coverage. An environmental sensor sits hundreds of miles from the nearest cell tower. In each case, the application is still running, but the network isn’t.
For years, solving that problem meant deploying an entirely separate satellite solution, different hardware, different providers, different management platforms, and often a completely different operational model. That’s changing.
Non-Terrestrial Networks (NTN) are bringing satellite connectivity into the same 3GPP standards that already power NB-IoT, LTE-M, and 5G. Instead of treating satellite as a specialized technology, NTN makes it another access network that devices can use alongside terrestrial cellular.
The result isn’t simply “satellite IoT.” It’s the beginning of software-defined connectivity that extends beyond the reach of traditional cellular networks.
This blog explains what NTN is, how it differs from legacy satellite IoT, where the technology stands today, and what enterprises should know before planning their next deployment.
What NTN Is
NTN (Non-Terrestrial Network) is 3GPP’s framework for extending cellular connectivity beyond terrestrial infrastructure. Instead of relying exclusively on ground-based cell towers, devices can communicate through satellites (or eventually high-altitude platforms) using the same cellular standards that already power modern IoT deployments. That distinction matters.
Satellite connectivity isn’t new. Enterprises have relied on it for decades to monitor assets in remote environments. What’s new is that satellite is no longer a separate networking technology. It’s becoming another part of the cellular ecosystem.
Rather than designing one connectivity strategy for terrestrial deployments and another for remote locations, organizations can begin treating satellite as another network that software can intelligently select when terrestrial coverage disappears.
That’s a much bigger shift than simply adding another radio.
Legacy Satellite vs. 3GPP NTN: The Real Difference
The biggest innovation behind NTN isn’t satellites. It’s standardization.
Legacy satellite IoT has been incredibly successful, but every deployment came with compromises. Devices required proprietary hardware, applications were often tied to a single operator, and satellite connectivity usually lived in its own operational silo. For enterprises managing thousands of devices, that meant maintaining separate hardware strategies, separate contracts, and separate management platforms simply to reach assets outside terrestrial coverage.
3GPP NTN changes that model. By extending open cellular standards (including NB-IoT, LTE-M, and eventually 5G NR) into satellite networks, NTN moves the industry toward interoperability rather than proprietary ecosystems.
The long-term opportunity isn’t replacing existing satellite providers. It’s giving developers, enterprises, and connectivity platforms the flexibility to use multiple access networks without redesigning the application whenever coverage changes. That’s exactly why NTN is generating so much attention.
The Orbits: GEO vs. MEO vs. LEO
One of the first questions people ask about NTN is, “Which orbit is best?”
The reality is, there isn’t a universal answer. Every orbit represents a different balance of coverage, latency, power consumption, and cost. The right choice depends entirely on what your devices are trying to accomplish.
- GEO (geostationary orbit) satellites sit roughly 35,786 km above Earth and appear fixed in the sky. Because a single satellite can cover a huge footprint, as few as three satellites are needed for near-global coverage. The tradeoff is latency. Signals travel much farther, resulting in round-trip latency of roughly 500–700 ms and higher power consumption for battery-powered IoT devices.
- MEO (medium Earth orbit) occupies the middle ground. Orbiting roughly 10,000–20,000 km up, MEO offers lower latency, typically in the 30–120 ms range, with a constellation size in the dozens rather than the thousands. MEO has traditionally been used for navigation systems and aviation or maritime communication rather than large-scale IoT.
- LEO (low Earth orbit) is where most of today’s innovation is happening. Operating between about 160–2,000 km above Earth, LEO dramatically reduces latency and improves the link budget for small, battery-powered devices. The downside is that covering the globe takes hundreds to thousands of satellites, and a device sees any given satellite for only a few minutes before it passes below the horizon.
That’s why most commercial NTN deployments today are built around LEO constellations. For asset tracking, environmental monitoring, smart agriculture, remote infrastructure, and other low-power IoT applications, LEO provides the right balance of coverage, performance, and device efficiency.
The important takeaway isn’t memorizing the differences between GEO, MEO, and LEO. It’s understanding that each solves a different connectivity problem. As NTN matures, enterprises will increasingly evaluate which orbit best supports their application rather than thinking of satellite as a single technology.
3GPP Standards: Release 17 / 18 / 19 and NB-IoT & LTE-M over NTN
You’ll often hear vendors say they’re “NTN compliant.” That’s only half the story.
The capabilities available today depend heavily on which 3GPP release a device, module, or network actually supports. Saying “it supports NTN” without mentioning the release is a bit like saying a phone supports 5G without explaining which features are available.
Release 17 is the milestone that made standardized IoT satellite connectivity commercially possible. It introduced NB-IoT, NTN, and LTE-M (eMTC) over satellite, along with the timing, synchronization, and Doppler compensation mechanisms needed to overcome the challenges of communicating with moving satellites. It also introduced NR-NTN for higher-bandwidth 5G applications.
Release 18 builds on that foundation. Rather than reinventing NTN, it improves mobility between terrestrial and satellite networks, strengthens coverage, introduces additional power-saving capabilities, enhances positioning, and expands support for broadband NR-NTN deployments operating in higher-frequency spectrum.
Release 19 looks further ahead. It focuses on deeper integration with the 5G Core, store-and-forward capabilities for delay-tolerant applications, RedCap support, and regenerative payload architectures that allow satellites to perform more network intelligence themselves instead of acting solely as relays.
For most enterprises evaluating NTN today, Release 17 is the benchmark that matters because it’s what enables commercially deployable IoT solutions today. Releases 18 and 19 are important because they make those deployments more efficient, more seamless, and ultimately more autonomous.
The takeaway is simple: don’t just ask whether a platform supports NTN. Ask which release it supports and what capabilities it actually enables.
How an IoT Device Connects to NTN
Connecting to a satellite isn’t as simple as attaching to the nearest cellular tower.
Because satellites are constantly moving relative to the device, and because signals travel much farther than they do over terrestrial networks, the device has to perform more preparation before a connection can be established.
The first step is obtaining a GNSS (GPS) position fix. Unlike a terrestrial cellular network, an NTN device needs to know exactly where it is so it can calculate the timing and frequency adjustments required to communicate with a moving satellite. Release 17 assumes every IoT-NTN device includes a GNSS receiver for this reason.
Next, the network provides satellite ephemeris and timing information through System Information Block 31 (SIB31). Using that information, the device calculates where the satellite is located and pre-compensates its own timing and frequency before transmitting. Rather than relying on the network to correct these differences after the fact, much of the work happens on the device itself.
Once the connection is established, the device continuously adjusts its timing as the satellite moves overhead. A new GPS fix isn’t required throughout the session, but if the connection drops, the process begins again before a new session can be established.
For developers, the practical implication is that NTN performance isn’t determined solely by the satellite link. GPS acquisition time, timing calculations, and power consumption all influence connection time and battery life. In many deployments, getting a fast and reliable GNSS fix can have just as much impact on overall performance as the radio technology itself.
Where NTN Is Real Today vs. Still Hype
NTN is no longer a research project. Commercial deployments are happening today.
But it’s also one of the most overhyped topics in connectivity. Some vendors make it sound like any IoT device can already roam seamlessly between terrestrial cellular and every satellite constellation on Earth. That’s not today’s reality.
What’s real today is Release 17 NB-IoT NTN. Certified modules are shipping. Commercial services are live. Enterprises are successfully deploying asset tracking, telemetry, environmental monitoring, and remote infrastructure using standardized satellite connectivity.
What’s still evolving are the capabilities often highlighted in keynote presentations: ubiquitous broadband NTN, regenerative payloads, seamless interoperability across multiple satellite operators, and fully integrated 5G-core architectures.
The takeaway isn’t that NTN is early. It’s that buyers should understand exactly which release, which module, which operator certifications, and which deployment model they’re evaluating before assuming every product delivers the same capabilities.
Not all “NTN-ready” solutions are created equal.
The Bigger Picture
NTN isn’t replacing cellular. It’s eliminating the places where cellular stops.
As 3GPP standards continue to mature, satellite connectivity will become less of a specialized technology and more of another network that software-defined platforms can orchestrate automatically alongside public cellular, private LTE/5G, and emerging connectivity options. For enterprises, that’s the real opportunity.
The future isn’t choosing between terrestrial and satellite networks. It’s building applications that don’t need to care which network they’re using because the connectivity platform makes that decision automatically.
That’s where the industry is headed, and why NTN matters far beyond satellite itself.
The takeaway? Most enterprises shouldn’t be choosing between terrestrial and satellite connectivity. They should be choosing a platform that can intelligently orchestrate both.
That’s where the industry is heading. Satellite is no longer a separate networking strategy: it’s becoming another access network that software-defined connectivity platforms can use automatically when terrestrial coverage disappears. Learn more during the Bridging Earth and Orbit with NTN Satellite Technology for Global Asset Tracking webinar on August 27 at 1:00 PM PDT.
Frequently Asked Questions
What does NTN stand for?
NTN stands for Non-Terrestrial Network, 3GPP’s term for extending cellular connectivity beyond traditional ground-based towers. The name is admittedly more technical than intuitive; it’s essentially the standards body’s way of describing networks that aren’t terrestrial, including satellites and future high-altitude platforms.
What matters isn’t the name. It’s what NTN enables: ordinary cellular technologies like NB-IoT, LTE-M, and 5G NR can communicate through satellites using standardized 3GPP specifications instead of proprietary satellite protocols.
How is NTN different from traditional satellite IoT?
The headline: it’s the same single off-the-shelf cellular modem. Legacy satellite IoT (Iridium’s classic service, Globalstar, Orbcomm) needs proprietary chips, proprietary networks, and their own airtime. With NTN you use a standard 3GPP modem (NB-IoT / LTE-M / 5G NR), one SIM/eSIM, and the device roams between the ground network and the satellite the same way it roams between two terrestrial operators. Same hardware, same core, no bolt-on satellite radio.
Is NTN the same as Direct-to-Device (D2D)?
D2D and Direct-to-Cell are the same idea, just different marketing; a satellite talking straight to an unmodified device. For phones, that’s Starlink Direct to Cell and AST SpaceMobile (AST got FCC commercial authorization in April 2026); for IoT it’s NB-IoT/LTE-M over satellite.
Is NTN commercially available today?
Yes. 3GPP-based NTN is commercially available today for narrowband IoT applications like asset tracking, remote monitoring, and telemetry. Operators including Skylo and Iridium offer commercial NTN services, while broadband Direct-to-Device (D2D) capabilities continue to evolve. For most IoT deployments, NTN extends connectivity where terrestrial cellular coverage ends.
Can existing IoT devices use NTN?
Sometimes. Devices must support the required 3GPP NTN specifications, frequency bands, and, in some cases, operator certification. Many newer IoT modules are NTN-ready, while older cellular hardware cannot be upgraded through software alone.
What does “Skylo-certified” actually mean?
Skylo certification means a module has been validated to operate on Skylo’s commercial NTN service using supported 3GPP standards. Certification is specific to both the hardware and the network, so not every NTN-capable module is automatically certified for every operator.
Does NTN work everywhere?
Not always. NTN dramatically expands coverage beyond terrestrial cellular networks, but availability depends on satellite coverage, country-specific regulations, and a clear view of the sky. Devices generally won’t connect reliably indoors, underground, or in heavily obstructed environments.
What should I consider before deploying NTN?
Start with compatible hardware, then consider certification, provisioning, power consumption, antenna design, and your application’s data requirements. Most NTN deployments are optimized for small, infrequent messages rather than continuous communication. We’ll explore deployment best practices, module selection, and power budgets in upcoming articles.
