Satellite connectivity is moving closer to the cellular model. With 3GPP Non-Terrestrial Networks, or NTN, satellite access can use standards already familiar to the mobile ecosystem. That creates a practical route to connect IoT devices in remote areas, maintain service when assets leave terrestrial coverage and add resilience when ground networks fail.
The important word is complement. NTN expands where cellular IoT can operate, but it does not make satellite and terrestrial networks interchangeable. Coverage, latency, capacity, power consumption, spectrum, device design and data cost still determine whether a terrestrial, satellite or hybrid architecture is the right choice.
For a detailed view of the technology, commercial tradeoffs and market opportunity, download the brand new 3GPP NTN satellite eBook.
What 3GPP NTN Changes
Traditional satellite IoT has often relied on proprietary protocols, specialist hardware and a separate service ecosystem. Those systems can be highly efficient for their intended purpose, but they can also increase integration work and bind a deployment to a narrower supplier set.
3GPP NTN brings satellites and other non-terrestrial platforms into the standards framework used by cellular networks. Release 17 included approved work for both 5G New Radio NTN and NB-IoT or eMTC support over non-terrestrial networks. The specifications account for conditions that terrestrial radio systems do not normally face, including longer propagation delays, large Doppler shifts from moving satellites and changing satellite visibility.
For IoT, the strategic benefit is a clearer path toward common devices and network integration. A device may use terrestrial cellular service when it is available and a satellite link when it is not. That can reduce the need to design, certify and manage separate cellular-only and satellite-only product variants. The outcome will still depend on chipset, antenna, band, network and roaming support; standards compliance alone does not guarantee seamless operation in every market.
Why Hybrid Connectivity Matters
Most enterprise IoT deployments do not need satellite connectivity all the time. They need it at the moments when terrestrial coverage ends or becomes unreliable. A hybrid design can keep routine, high-volume traffic on cellular networks and reserve satellite capacity for location updates, alerts, essential telemetry or service continuity.
This pattern is especially relevant to assets that move through mixed coverage. A long-distance fleet system, for example, could transmit urgent events through satellite while a vehicle is outside terrestrial coverage, store richer diagnostics locally and upload the larger dataset when cellular service returns. The same principle can apply to containers, agricultural machinery, mining equipment, utility assets and lone-worker devices.
The market extends beyond devices designed primarily for remote operation. Transforma Insights forecasts that by 2034 nearly 63 million IoT connections will treat satellite connectivity as essential. The eBook also identifies a further 1.5 billion 3GPP cellular 5G connections that could potentially benefit when they temporarily move outside terrestrial coverage. These forecasts include different device categories and service models, so they describe an addressable opportunity rather than guaranteed NTN adoption.
Three ‘Clear Fit’ Use Cases
- Remote asset connectivity. Agriculture, mining, energy, maritime and environmental monitoring often place equipment where building terrestrial infrastructure is uneconomic. NTN can make a 3GPP-based device viable in these locations, subject to sky visibility, link budget, power and service availability.
- Coverage extension for moving assets. Vehicles and portable devices can spend most of their time within terrestrial coverage and still cross rural roads, oceans, mountains or local white spots. Satellite access can preserve a narrow set of essential functions without requiring the application to treat every link as equivalent.
- Resilient backup communications. Floods, earthquakes, wildfires and power failures can damage terrestrial networks precisely when asset status and emergency communications matter most. The GSMA identifies network resilience and emergency support as core benefits of direct-to-device satellite connectivity. A backup design still needs tested failover logic, an operating plan and a data budget; a second access path is useful only if the device and application can use it under real conditions.
The Tradeoffs Remain Important
| Decision factor | Terrestrial cellular | Satellite | Hybrid design |
|---|---|---|---|
| Coverage | Strong where ground infrastructure exists | Broad reach with outdoor sky-view requirements | Uses the best available access path |
| Latency | Usually better for real-time services | Varies materially by orbit and architecture | Can keep time-sensitive traffic on cellular |
| Capacity | Best fit for frequent or high-volume transfers | Capacity and service limits require discipline | Can defer bulk uploads until cellular returns |
| Cost | Typically lower per unit of data | Usually carries a premium | Controls cost by limiting satellite traffic |
| Complexity | Established device and roaming ecosystem | Requires satellite-aware RF and application design | Adds policy, failover and operational testing |
Orbit choice adds another layer. Low Earth Orbit satellites can reduce propagation delay and provide higher capacity, but continuous coverage needs a sufficiently dense constellation and frequent handovers. Geostationary satellites provide persistent coverage from a fixed position with fewer spacecraft, but their altitude introduces more delay. For low-duty-cycle IoT, actual service latency can also include the time a device waits for the next satellite pass.
Spectrum affects both device compatibility and network planning. Mobile Satellite Service spectrum separates satellite access from terrestrial cellular bands and can reduce certain interference concerns, but a device must support the relevant bands. Reusing terrestrial mobile spectrum may improve compatibility with existing devices, while introducing coordination, regulatory and interference challenges. The GSMA has called for licensing approaches that protect terrestrial services and support compatible satellite direct-to-device deployment.
Questions to answer before selecting NTN
- Where will the device operate, and how often will terrestrial coverage be unavailable?
- Does the device have a suitable antenna position and a reliable view of the sky?
- Which data must be sent immediately, and which data can be stored, filtered or batched?
- What latency can the application tolerate during satellite operation?
- Which spectrum bands, chipsets, modules, networks and countries must the product support?
- How will the application detect, select and test the terrestrial and satellite paths?
- What satellite usage, roaming and operational costs are acceptable over the device lifetime?
A good NTN plan starts with the traffic profile and operating environment, not with the satellite constellation. When the design reserves satellite capacity for the data that genuinely matters outside terrestrial coverage, NTN can extend service without forcing every workload onto a more expensive or constrained link.
Download the eBook
The eBook, The advent of 3GPP Non-Terrestrial Networks explains the standards, spectrum options, satellite architectures, cellular comparisons and IoT opportunity types in more detail.
Download the 3GPP NTN satellite eBook
Sources
Transforma Insights and KORE, The advent of 3GPP Non-Terrestrial Networks
- 3GPP, NB-IoT and eMTC support for Non-Terrestrial Networks, Release 17 work item
- 3GPP, Solutions for NR to support Non-Terrestrial Networks, Release 17 work item
- GSMA, Non-Terrestrial Networks Opportunities and Challenges
- GSMA, Satellite direct-to-device
Published September 30, 2026.