Cellular is the normal path; satellite carries continuity where terrestrial coverage does not reach. Treating them as one connected-asset architecture rather than two product lines produces a single record of where an asset has been, instead of two partial records with a gap exactly where loss tends to occur.
LTE-M, NB-IoT or LTE Cat-1, with the network scan and attach behaviour tuned so a failed attempt does not drain the battery on a long timeout.
Messages are stored locally with their original timestamps, so a coverage gap costs latency rather than data.
Routine position reports wait. Alarm conditions — geofence breach, tamper, temperature excursion — escalate immediately.
The satellite link carries the message where continuity is required, with payload reduced to what genuinely must arrive now.
When terrestrial coverage returns, the buffer is flushed in timestamp order and normal reporting resumes.
The platform assembles one continuous history from both transports, rather than presenting two datasets a human has to merge.
| Dimension | Cellular (LTE-M / NB-IoT) | NTN satellite |
|---|---|---|
| Coverage | Populated and transit corridors | Global, with sky visibility |
| Energy per message | Low | Substantially higher |
| Cost per message | Low | Substantially higher |
| Payload size | Comfortable | Constrained; every byte matters |
| Latency | Seconds | Seconds to minutes by constellation and pass |
| Best role | Default transport | Continuity and alarm escalation |
Reporting interval, not cell chemistry, is what determines how long a tracker lasts. A device reporting every fifteen minutes and one reporting hourly differ by roughly a factor of four in radio energy, which is most of the energy budget.
So policy should be adaptive. Report more often while moving and less often while stationary. Report more often inside a geofence of interest. Report immediately on an alarm condition regardless of schedule. And use a different, sparser policy on the satellite transport, because a message that costs ten times as much should not be sent at the same rate.
The common mistake is a fixed interval chosen for the worst case and applied everywhere, which produces a fleet that reports uselessly often while parked in a yard and exhausts its batteries before the assets it tracks need replacing.
A non-terrestrial network carries connectivity over satellite rather than terrestrial cell sites. In a tracking architecture it is a continuity layer — cellular remains the default, and NTN carries messages where terrestrial coverage is unavailable or where an alarm must escalate immediately.
It can, because a satellite message costs substantially more energy than a cellular one. Which is why the satellite transport uses its own sparser reporting policy and reduced payloads rather than mirroring the cellular schedule.
Messages are buffered with original timestamps and flushed in order when coverage returns, and the platform reconciles both transports into one asset history rather than presenting two datasets.
Written for engineers. Share it with one.
Tell us the specification, the constraint and the deadline. Programmes that cross silicon, radio, embedded and AI are where Faststream is strongest.