Overview
MAPS Messaging integrates with satellite IoT services from Viasat, Inmarsat, and Orbcomm.
These services extend secure messaging into remote areas where terrestrial connectivity is unavailable.
Context
-
Viasat
A global satellite communications company and the parent of Inmarsat (acquired in 2023). Viasat operates multi-band satellite networks (Ka-, Ku-, and L-band) that deliver broadband, mobility, and secure communications. Its L-band services are focused on highly reliable, always-on IoT and safety applications. -
Inmarsat
Now part of Viasat. Inmarsat brings a heritage of L-band GEO satellites that provide near-global coverage for maritime, aviation, land mobility, and critical infrastructure. These L-band services are valued for resilience, low-power terminals, and guaranteed availability, especially in safety-of-life and remote IoT use cases. -
Orbcomm
A long-standing IoT service provider and technology partner. Orbcomm’s infrastructure and devices integrate with the Viasat/Inmarsat L-band network, powering both legacy IsatData Pro (IDP) and newer OGx / IoT Nano services. Orbcomm adds application services, device platforms, and vertical-specific solutions on top of the satellite connectivity.
Service Types
-
IsatData Pro (IDP)
Legacy two-way satellite messaging service, optimized for small, periodic telemetry messages. Still widely used in maritime and asset tracking. -
IoT Nano (OGx)
Next-generation two-way IoT service providing:- Larger payloads (up to ~1 MB)
- Faster transmission speeds
- Reduced power consumption
- Backward compatibility with IDP devices
Together, these services enable global, reliable, low-bandwidth messaging across industries such as:
- Maritime (ship telemetry, AIS)
- Aviation (aircraft tracking, safety systems)
- Utilities & energy (pipeline monitoring, smart grids)
- Agriculture & mining (remote sensors, heavy equipment monitoring)
End-to-End Flow (High Level)
Figure: MAPS Messaging in a satellite IoT deployment.
Legend
- Remote MAPS Servers
Deployed at field sites (ships, vehicles, remote stations). These connect to local modems and sensors. - IoT Modems (IDP / IoT Nano)
Handle uplink and downlink messaging via satellite. - Satellite (L-band GEO)
Provides global coverage, relaying data between remote devices and the ground infrastructure. - Ground Station
Receives satellite traffic and forwards it into the Orbcomm / Inmarsat core network. - Enterprise MAPS Server
Runs in the enterprise/datacenter environment. Integrates via REST APIs or direct links into Orbcomm/Inmarsat. Connects back to enterprise applications (MQTT, AMQP, NATS, REST). - Enterprise Apps
Consume normalized, protocol-agnostic messages.
Flow
- Remote device → Remote MAPS Server
Device telemetry is ingested and normalized by the local MAPS instance. - Remote MAPS Server → Satellite link
Messages are passed through IoT Nano or IDP modems, sent when a satellite is visible. - Satellite → Ground Station
The GEO satellite relays data to the ground segment. - Ground Station → Enterprise MAPS Server
Messages are routed into the enterprise side via Orbcomm/Inmarsat APIs. - Enterprise MAPS Server → Enterprise Applications
MAPS bridges into MQTT, AMQP, NATS, or REST, delivering messages where they are needed. - Optional ML Filtering
MAPS can apply machine learning models to detect anomalies and filter noise before data is transmitted or forwarded, reducing costs and highlighting critical events.
MAPS Integration (High Level)
MAPS Messaging provides a protocol-agnostic bridge into these satellite networks.
It can connect at two levels:
- At the Modem End — directly interfacing with IoT Nano (OGx) and IDP modems installed on vessels, vehicles, or remote stations.
- At the REST API End — integrating with Orbcomm / Inmarsat cloud APIs for message delivery and terminal management.
This flexibility allows MAPS to support both edge deployments (local modem connectivity) and enterprise integrations (REST API connections to the satellite network).
Built-in ML Capabilities
MAPS includes machine learning integration to add intelligence on top of satellite data flows:
- Anomaly Detection — flag unusual events (e.g., abnormal engine readings, unexpected location changes).
- Filtering — reduce bandwidth costs by discarding noise before sending data across high-latency satellite links.
- Adaptive Models — models can evolve over time, accounting for seasonal changes, sensor drift, or environmental variation.
- Event Routing — anomalous data can be automatically routed to separate topics or alerting systems for fast response.
This ensures that satellite links carry only the most relevant data, improving efficiency while enabling proactive monitoring.