Cellular coverage doesn't reach everywhere IoT devices need to operate. For devices that support both technologies, satellite connectivity can provide another way to send data when terrestrial networks are unavailable. The device uses cellular coverage where it can, then connects through a supported satellite network when needed, although switching may briefly interrupt communication.
Table of Contents
- What Does Cellular and Satellite IoT Connectivity Mean?
- What Happens When a Device Leaves Cellular Coverage?
- Can the Same SIM Work on Cellular and Satellite Networks?
- Can Existing Cellular IoT Devices Connect to Satellites?
- How Does Satellite Connectivity Change Device Operation?
- Is Satellite Connectivity the Same as Cellular Failover?
- What Does Seamless Cellular-to-Satellite Switching Really Mean?
1. What Does Cellular and Satellite IoT Connectivity Mean?
A tracker on a shipping container may work perfectly well over cellular networks while the container moves between warehouses, ports, and distribution centers. Once it travels beyond terrestrial coverage, the situation changes. The tracker can continue recording its position, but it has no way to send that information until a network becomes available again.
Satellite connectivity gives it another possible route.
Cellular and satellite connectivity can be combined in different ways. Some installations have separate cellular and satellite modems, while others use a satellite gateway to connect nearby IoT equipment.
But an IoT device doesn't always need a separate satellite terminal. With the right hardware, it can communicate directly with a satellite using cellular technology adapted for satellite networks. These are called Non-Terrestrial Networks, or NTN.
The cellular industry's 3GPP standards include satellite adaptations of Narrowband IoT (NB-IoT) and LTE-M. Both were originally developed for devices that exchange relatively small amounts of data over cellular networks.
With compatible hardware and network service, an IoT device can use terrestrial cellular coverage where available and communicate through satellite when the supported service and operating conditions allow it.
The application may still receive the same information: location updates, meter readings, equipment status, or alerts. What changes is how that information travels.
On a terrestrial network, the device communicates with a nearby cell tower. Over satellite NTN, its signal reaches a satellite, which may pass the data through a ground station and into the network.
2. What Happens When a Device Leaves Cellular Coverage?
At the edge of cellular coverage, a device may remain registered on the network but stop delivering measurements reliably. The modem can spend time trying to restore that connection before it looks for another network.
Whether it attempts satellite access depends on how the device and connectivity service are configured. NTN support alone isn't enough. The satellite network also has to be compatible with the hardware and available under the device's subscription.
Once the device attempts a satellite connection, several things have to happen before it can transmit data.
Preparing the satellite connection
Unlike a terrestrial cell tower, a satellite may be hundreds or thousands of kilometers from the device. Signals take longer to travel that distance, and the movement of the satellite also affects the received frequency.
The modem needs to compensate for both before it can communicate reliably. In certain NTN implementations, it uses information about its location and the satellite's position to make those adjustments.
For example, 3GPP Release 17 IoT-NTN uses satellite positioning information and GNSS, the satellite navigation technology also used for GPS-type positioning, to support these calculations.
The device may also need information about the satellite's expected position and movement, known as ephemeris data.
The important distinction is that connecting to a satellite requires capabilities beyond those of an ordinary terrestrial cellular modem. Even if both use NB-IoT technology, the hardware and software must support the satellite-specific requirements.
Establishing network access
After preparing the radio connection, the device must gain access to the satellite network.
It may need to register with the network, verify its subscription, and establish a connection that can carry application data.
These steps are similar in purpose to what happens when a cellular device connects to a mobile network, although satellite access involves additional technical requirements.
The subscription must also permit satellite connectivity. A compatible modem cannot use a satellite service simply because a satellite is visible.
Once connected, the device can send its current measurements along with any records stored while communication was unavailable.
It may continue using satellite service until terrestrial coverage returns or its network settings direct it to look for another connection.
Returning to cellular coverage
When the device reaches an area with usable terrestrial service, it may reconnect through the cellular network.
That doesn't necessarily happen the moment a cellular signal appears.
The modem may search for an eligible network at scheduled intervals or follow other connection rules. Returning to cellular can also require the device to establish a new network connection.
For equipment that sends readings periodically, the interruption may have little practical effect. Devices that maintain an ongoing connection to an application server may need to reconnect before communication can resume.
There will also be places where neither terrestrial nor satellite service is usable.
A tracker can keep its location records locally until communication returns. A meter can do the same with timestamped readings. What matters is that an unsuccessful transmission doesn't cause those records to be discarded.
Satellite connectivity reduces some coverage gaps, but devices still need a way to operate through periods when no connection is available.
RELATED GUIDE
Satellite IoT or Starlink: What Does Your Deployment Need?→
3. Can the Same SIM Work on Cellular and Satellite Networks?
A device doesn't necessarily need a second SIM to communicate over satellite. Some connectivity services allow the same SIM to be used for terrestrial cellular and satellite access, provided the device supports both technologies.
But having one SIM doesn't tell you much about how the service will be managed. Cellular and satellite access might be covered by the same subscription, while usage reporting, connection diagnostics, and network controls remain different.
For a business running hundreds or thousands of devices, these details matter. The operations team needs to know which network a device is using, why it failed to connect, and how much data it has consumed, particularly when satellite usage carries different costs.
Does a multi-carrier SIM already provide satellite access?
A multi-carrier SIM gives a device access to multiple supported terrestrial mobile networks. Depending on the service, this may involve roaming agreements or multiple subscriber identities, known as IMSIs.
In suitable configurations, devices can automatically switch across networks when their current terrestrial network becomes unavailable.
Satellite access requires additional support.
The modem must be compatible with the satellite technology, and the subscription must include permission to use the satellite service.
A device that can connect to several terrestrial carriers is therefore not automatically capable of connecting to a satellite.
4. Can Existing Cellular IoT Devices Connect to Satellites?
Some newer cellular IoT modules support NTN, but existing LTE or NB-IoT hardware should not be assumed to have that capability.
The technical requirements are different enough that compatibility needs to be checked at the exact modem or module level.
For an installed fleet, start with the exact modem model, hardware revision, and firmware version. Check the manufacturer's specifications for NTN support and the required frequency bands. A general LTE or 5G compatibility claim isn't enough.
Even firmware upgrades have limits. They may enable functions the hardware was built to support, but they won't compensate for missing radio components or unsupported frequencies.
The modem is only part of the hardware check. Antenna design and installation can prevent satellite communication even when the module itself is compatible.
Consider equipment installed inside a metal cabinet. Its terrestrial cellular connection might work through a nearby network or an external antenna. That says little about whether the satellite signal will be strong enough.
Depending on the frequency and satellite service, the installation may require a different antenna, a particular orientation, or placement where the antenna has a clearer view of the sky.
This can make satellite support a hardware and installation decision rather than a simple connectivity-plan change.
CONNECTIVITY SOLUTION
Need More Reliable Cellular Coverage for Your IoT Devices?
5. How Does Satellite Connectivity Change Device Operation?
The application may send the same data over either network, but it shouldn't assume the two connections behave identically.
The differences become noticeable when devices send frequent messages, depend on quick responses, or operate on batteries.
Message delivery and response times
Satellite connections can introduce different delays from terrestrial cellular.
Part of that comes from the distance signals must travel. Satellites in low Earth orbit are considerably closer than geostationary satellites, but distance is only one part of what determines how quickly data arrives.
The device may need time to find an available satellite signal, connect to the network, and send its message. If the transmission fails or the satellite service is temporarily unavailable, delivery can take longer.
A remote meter sending one reading every hour may have no difficulty with that.
A device expecting a response to every command within a few seconds may require a different approach.
For that reason, advertised network latency, or the delay introduced by the network, is not always the most useful measurement.
What matters to the business is how long it takes for information to reach the application and, where necessary, for a response to reach the device.
Data volume and battery consumption
Many IoT applications exchange modest amounts of data. A tracking device may send coordinates and battery status. A remote monitor may report a measurement and a diagnostic code.
That traffic can fit the capabilities of low-data-rate satellite IoT services.
Frequent diagnostic uploads, repeated transmission attempts, and unnecessary background traffic create a different workload.
They can also affect battery life.
Establishing satellite access may take additional processing or longer connection procedures. Repeated searches for an unavailable service consume energy even when no data is delivered.
There isn't a universal rule that satellite transmission always uses more power than terrestrial cellular. The result depends on the hardware, signal conditions, connection process, and reporting schedule.
For a battery-operated device, testing only successful satellite transmissions would miss an important part of its actual power consumption.
Coverage and installation conditions
A satellite coverage map doesn't tell you whether a device can establish a connection from its installed position.
Buildings, terrain, vegetation, equipment enclosures, and antenna orientation can obstruct or weaken the signal.
An outdoor sensor mounted on an exposed pole faces different conditions from one installed inside an industrial enclosure.
Mobile devices present additional complications because the antenna's orientation and surrounding obstructions change during operation.
Satellite availability can also vary by service.
Some networks provide frequent communication opportunities across their supported areas. Others may have periods when a suitable satellite connection isn't available.
A device that sends occasional measurements may be able to wait for the next opportunity. That may not work for applications requiring immediate communication.
The reporting schedule needs to reflect when the service is actually available, not simply the geographic area shown on its coverage map.
6. Is Satellite Connectivity the Same as Cellular Failover?
The distinction becomes clearer when looking at what needs to stay connected.
At a remote facility, a router may use both satellite broadband and terrestrial cellular. A satellite and cellular connectivity solution can switch traffic between those connections, allowing the site's equipment to continue using an internet connection when one path becomes unavailable.
An IoT device with NTN support operates differently. Instead of keeping an entire site connected, it may establish satellite access to send its own measurements or status information when terrestrial cellular coverage is lost.
It might not keep an active backup connection, and communication with the application could be interrupted while the modem changes networks.
For a remote meter that stores readings and transmits them once a connection is available, that may be perfectly acceptable.
For equipment requiring continuous remote control or consistently quick responses, it could be a serious limitation.
Satellite access also doesn't protect against every possible network failure. Terrestrial and satellite services may depend on some of the same infrastructure beyond the immediate wireless connection.
The important question is what the system needs to preserve when cellular coverage disappears.
If occasional measurements or alerts must continue reaching the application from remote areas, satellite IoT may provide a suitable alternative path.
Maintaining broadband internet for an entire site is a different requirement and may call for a separate failover arrangement.
CONNECTIVITY SOLUTION
Need Satellite Backup for a Remote Site?
7. What Does Seamless Cellular-to-Satellite Switching Really Mean?
A service described as seamless might use one subscription for terrestrial and satellite connectivity, common billing, and a shared management platform.
Those are useful operational features. They don't necessarily mean that an active connection remains uninterrupted when the device changes networks.
A modem may automatically leave terrestrial service and connect to the satellite network without anyone changing its settings. The application might still lose its connection during that process.
The difference matters most when communication is already in progress.
What happens to an active connection?
Suppose a device maintains an ongoing connection to an application server.
When terrestrial coverage disappears, that connection may close or stop responding. The modem then attempts satellite access and completes the steps needed to establish a new connection.
At that point, the device has network access again. But the application may still need to reconnect to its server before data can move normally.
Some network systems can maintain an ongoing connection during certain network changes. Others require the application to start a new connection after switching.
Automatic switching alone doesn't tell us which behavior a particular service supports.
A device that sends one measurement every thirty minutes may barely notice the interruption. A system depending on continuous two-way communication has different requirements.
A message sent just before the connection drops
Imagine a tracker transmitting its location while the terrestrial connection fails.
The tracker may not know whether the server received the update.
After reconnecting through satellite, the tracker has to decide what to do with that location record. Sending it again could produce a duplicate, but discarding it risks losing an update that never reached the server.
In practice, the device can retain the record until the application confirms receipt. If no confirmation arrives, it can retry later.
Each record can carry a unique message ID, allowing the server to recognize a duplicate if the tracker sends the same update again. The timestamp preserves when the location was originally recorded, even if it arrives much later.
Retries need some limits, especially on battery-powered trackers. Repeated attempts to deliver the same message while the network is unavailable can consume power without getting the data any closer to the server.
These methods aren't exclusive to satellite IoT. They're useful whenever devices operate over connections that can disappear unexpectedly.
They become particularly important when network changes are part of normal operation rather than rare failures.
Testing the transition
A modem successfully connecting to both terrestrial and satellite networks doesn't prove that application communication will recover correctly.
The useful test follows the data through the change.
Send messages over terrestrial cellular, interrupt that connection, and verify what reaches the application after satellite access is established.
Repeat the test when the device returns to cellular.
Look for missing records, duplicate messages, delayed delivery, and application connections that fail to recover.
The result is more useful than simply confirming that the device can connect to two different networks.
CONTINUE EXPLORING