PlatformsFaststream SiliconFaststream RadioFaststream VisionConnected EdgeFaststream SecureMobility & Rail
ProductsSemiconductor IPIP CoresWireless & RANEdge & GatewaysTracking & IdentificationSoftware & FrameworksConnected Systems
Technology5G protocol stackWireless and RF architectureBaseband and low PHYForward error correctionControl and data planeHigh-speed interfacesFirmware and bootSilicon root of trustSoftware-defined vehicleAutomotive OTAFunctional safety
AIAI Engineering ServicesEdge AI & Embedded MLComputer Vision EngineeringSensor Fusion & PerceptionAI Silicon & AccelerationMLOps for DevicesAI Visual InspectionPredictive MaintenanceDriver MonitoringVideo Analytics & Safety
SolutionsSemiconductorIndustrial AIConnected ProductsAsset TrackingMHE Tracking & UtilizationBluetooth AoA RTLSWearable TrackingAutomotive & MobilitySmart InfrastructureSecure IdentityWireless & SatelliteNTN Asset TrackingPrivate 5GSmart WashroomsFuel ManagementSmart BuildingsWorker SafetyEnergy MonitoringSmart AgricultureSmart CityAutonomous PlatformsAssembly AutomationLiDAR Rail SafetyHardware Wallet
IndustriesSemiconductorTelecommunicationsIndustrial & ManufacturingAutomotive & MobilityTransportation & RailAerospace & DefenceHealthcare & MedicalEnergy & UtilitiesOil & GasRetailConsumer ElectronicsMedia & EntertainmentSmart Infrastructure & IoT
ServicesSystem Integration overviewASIC & SoC DesignRTL to GDSIIVerification methodologyDFT and silicon testLow-power designMixed-signal integrationDesign enablementFPGA DesignFPGA-to-ASIC ConversionAnalog, Mixed-Signal & RFHardware & High-Speed PCBEmbedded SoftwareCloud, OTA & Device ManagementManufacturing TransitionHow we engage
CompanyAbout FaststreamEngineering ExcellenceLeadership & OrganisationHow We EngageQuality & ComplianceStandards & EcosystemPartners & EcosystemTrust CentreLocations & DeliveryNewsroom & MediaCareersCase StudiesKnowledge CenterWhite PapersGlossaryNewsletterResources & Support
ContactStart a projectHow we engage
Talk to us
REFERENCE ARCHITECTURE · TRACKING

What happens when your assets leave cellular coverage?

How hybrid cellular–satellite IoT keeps critical assets visible beyond terrestrial networks. Most asset trackers work beautifully — until the asset drives past the edge of the cellular map. This is what it takes to keep it visible when it does, and where the honest limits are.

November 20267 minute readSatellite IoT
THE PROBLEM

Coverage is a map with holes in it.

A cellular tracker reports reliably across a city and most of a highway, and then goes quiet — on an ocean leg, in a remote mine, across a desert haul road, in a valley the towers do not reach. For a consumer parcel, the silence is tolerable; the update arrives late and nobody is harmed. For a high-value, safety-critical or regulated asset, the silence is the expensive part: the hours you cannot account for are exactly the hours when something goes wrong.

The instinct is to treat this as a connectivity-vendor problem — buy a better SIM, add a satellite box. It is really a system-design problem. Keeping an asset visible through a coverage gap means deciding what the device does when the network disappears, which messages are worth a costly satellite slot, and how two different data streams become one trustworthy record. None of that is solved by a module on a datasheet.

Cellular carries the data where coverage exists. In the gap, GNSS still fixes position, the device buffers and prioritises, and a satellite link carries the critical messages — then the cloud reconciles everything into one continuous record.
WHEN CELLULAR RUNS OUTGNSS · position, everywhereDepotOn-routeRemote · ocean · desertSiteDestinationcellular coverageNO CELLULARcellular coverageCellularnormal transportEdge bufferhold + prioritisesatellite IoTCloud reconcilesone recordCellular in coverage · satellite in the gap · GNSS throughout · cloud reconciles one record.
FIRST PRINCIPLE

Positioning is not connectivity.

The single most useful distinction in this field: GNSS tells the device where it is; it does not tell anyone else. GPS, Galileo, GLONASS and BeiDou are one-way positioning systems — the tracker listens to satellites and computes a fix. That fix is worthless to an operator until a separate communication link carries it home.

So a tracker that survives a coverage gap carries two different kinds of radio for two different jobs. GNSS keeps working in the gap — the asset still knows where it is. What changes is the path home: cellular when it is there, and a satellite communications link when it is not. Conflating the two — assuming “it has GPS” means “we can see it” — is the mistake that produces blind spots.

One device, two jobs: GNSS for position, and two communication radios — cellular for the normal path, satellite for beyond coverage — with an MCU that buffers, prioritises and fuses, and a power budget that has to carry all of it.
HYBRID TRACKER · WHAT IS INSIDEASSET TRACKERMCU + edge logicbuffer · prioritise · fuseGNSS receiverpositionCellular modemin coverageSatellite modembeyond coverageBLE sensor hubcondition dataPower mgmtbattery budgetAntenna(s)GNSS · cell · satGNSS for position · cellular and satellite for comms · an MCU that buffers, prioritises and fuses.
WHAT CROSSES THE GAP

Fallback, prioritisation, buffering, reconciliation.

When cellular drops, four things have to happen in order, and each is an engineering decision rather than a feature you switch on.

Fallback. The device detects that the primary path is gone and escalates to the satellite link — but only for what matters, because satellite messages cost far more in energy and money per byte. Prioritisation. Not every reading earns a satellite slot; a position every few minutes and an alarm go now, routine telemetry waits. Buffering. Everything else is stored on the device, timestamped and queued, so nothing is lost while the link is down. Reconciliation. When cellular returns, the buffered backlog is forwarded, and the cloud merges the satellite stream and the cellular backlog into one ordered, de-duplicated timeline — so an operator sees a single history, not two partial ones to stitch together by hand.

The device sends over cellular when it is available and falls back to a satellite link for prioritised messages when it is not. The cloud reconciles both streams — ordering and de-duplicating — into one timeline for the dashboard and enterprise systems.
DEVICE TO CLOUD · DATA FLOWDevicebuffer + queuecellular?availableCellular networklow cost / syessatellite IoTno · priority msgsGround stationgatewayCloud ingestreconcile · order · dedupDashboard+ API / ERPCellular when available · satellite fallback for priority messages · cloud reconciles one timeline.
THE TRADE-OFFS

What you are actually buying.

Hybrid tracking trade-offs
DimensionThe trade-off
AntennaSatellite links need sky visibility and a correctly placed antenna; metal enclosures, containers and vehicle bodies block them. Placement is a design constraint, not an afterthought.
PowerA satellite transmission costs far more energy than a cellular one. Battery life is set by how often you send over satellite, so reporting policy — not chemistry — is usually the dominant variable.
Latency & deliverySome satellite IoT services are one-way (send-only) and best-effort; delivery is not instantaneous or guaranteed. Design for “eventually and in order”, not “immediately”.
CoverageSatellite footprints and pass schedules vary by service and geography. “Global” rarely means “everywhere, all the time.”
RegulatorySpectrum and device approvals differ by country and by service; a device legal in one region may need re-approval in another.
IntegrationThe hard part is rarely the module — it is the firmware logic, the message schema, the power budget and the cloud reconciliation that make the two links behave as one system.
STANDARDS

Proprietary satellite IoT and 3GPP NTN are not the same thing.

Two families of satellite connectivity are converging on this problem, and they are worth keeping distinct. Proprietary satellite IoT services use dedicated networks and modules, often optimised for very low-power, small-message, send-mostly traffic — mature today, with one-way and two-way variants. Faststream integrates these technologies — for example Globalstar’s STX3 (simplex, send-only) and its two-way RM200M satellite-and-cellular module — choosing the variant that fits the asset’s power budget and reporting needs. Standards-based 3GPP non-terrestrial networks (NTN) extend cellular itself to satellites: NB-IoT NTN for low-rate IoT and NR NTN for higher-rate links, aiming to reuse the cellular ecosystem and let one device roam between terrestrial and satellite coverage.

The choice is an engineering trade, not a slogan: message size and frequency, two-way needs, power budget, module availability, regulatory footprint and cost all push one way or another. A sound design keeps the option open at the architecture level rather than hard-wiring the business case to one network.

THE ENGINEERING

What Faststream actually builds here.

Keeping an asset visible beyond cellular is a silicon-to-cloud problem, and Faststream engineers every layer of it rather than reselling one.

Silicon

Low-power RF, analog and mixed-signal IP, and secure elements — the components a long-life tracker is built from.

Embedded & edge

The firmware that decides fallback, prioritisation and buffering, fuses GNSS with sensors, and holds the power budget.

Wireless

GNSS, cellular and satellite module integration, antenna and RF design, and the message schema across link types.

Cloud

Ingest, reconciliation and de-duplication, dashboards, APIs and enterprise (ERP/WMS) integration.

Security

Device identity, signed events and secure updates, so a record from a remote asset can be trusted.

System

The integration that makes two radios, a power budget and a cloud behave as one continuous record.

THE OPERATOR VIEW

What it looks like in use.

The payoff is an operations picture that does not go dark at the edge of the map: every asset visible with its current link state — on cellular, on satellite, or buffering — and alerts that fire on condition and geofence rather than on the operator noticing a gap. The view below is a demonstration with sample data, not live telemetry.

Demonstration dashboard — representative layout and sample data, not live telemetry. Each asset shows its current link state (cellular, satellite or buffered), last-seen, and condition and geofence alerts.
ASSET DASHBOARD · DEMONSTRATIONGLOBAL MAP · SAMPLE● on cellular ● on satellite ● bufferedFLEET · SAMPLETRK-204on satellite6m agoTRK-118on cellularjust nowTRK-077bufferedlink down 22mTRK-390on cellular2m agoALERTS · SAMPLE▲ TRK-077 out of cellular 22m · buffering▲ TRK-204 temp 31°C · threshold● TRK-390 geofence enter · Yard
WHERE IT MATTERS

Who needs it.

Remote logistics

Long hauls that cross coverage gaps between depots and destinations.

Maritime

Containers and vessels on ocean legs with no terrestrial network.

Mining

Pits, haul roads and remote sites beyond cellular reach.

Oil & gas

Wellheads, pipelines and unattended assets in remote terrain.

Agriculture

Machinery and assets across large, sparsely-covered land.

Rail & utilities

Rolling stock and distributed infrastructure along remote corridors.

COMMON QUESTIONS

Questions readers ask.

01

Does satellite IoT give continuous, always-on coverage?

No. It closes the gaps where cellular does not reach, but delivery depends on sky visibility, satellite availability and the service. The honest design uses cellular as the normal path and satellite for prioritised messages across gaps — not a promise of continuous coverage.

02

Is GNSS the same as satellite connectivity?

No. GNSS positions the device; a separate satellite or cellular link communicates the data home. A tracker uses GNSS to locate and cellular or satellite to report.

03

What drives battery life?

How often you transmit over satellite, far more than the battery chemistry. Reporting policy and message prioritisation are the dominant levers.

KEEP READING

Related work.

BUILDING ACROSS THE SPLIT?

Bring us the fronthaul and the timing.

The 7.2x fronthaul, BFP compression and sub-microsecond PTP/SyncE timing between RU and DU are where a disaggregated radio is won. Tell us the split and the transport.