Satellite Mesh Resilient Communications

Overview#

A forward operating base in a remote area loses its primary Starlink link during a sandstorm. Within seconds, the system has already failed over to Iridium narrowband for critical command traffic. Messages queued during the brief transition flush automatically once the link stabilises, and field teams on ATAK devices see no interruption to their common operating picture. None of that required operator intervention.

Argus Satellite Mesh Resilient Communications provides multi-layer communication resilience for operations in environments where conventional network connectivity is unavailable, unreliable, or contested. The system orchestrates communication across multiple transport layers: commercial satellite (Starlink), narrowband satellite (Iridium), and tactical mesh radio networks, with automatic failover based on availability, bandwidth, and latency requirements. Store-and-forward message queuing guarantees delivery even when all real-time links are temporarily unavailable.

Open Standards#

• Cursor on Target (CoT) 2.0: TAK situational-awareness events are encoded as CoT 2.0 XML and relayed through the satellite and mesh communication layers over UDP multicast (239.2.3.1:6969) and TCP streams, preserving the common operating picture across all transport paths.
• IETF RFC 2501 (Mobile Ad Hoc Networking): The tactical mesh radio layer implements the MANET architecture defined in RFC 2501, enabling self-organising, multi-hop connectivity between deployed nodes without reliance on fixed infrastructure.
• NATO STANAG 4677: MANET node topology and interoperability follow STANAG 4677, ensuring that mesh radio nodes conform to Alliance standards for ad-hoc network management.
• Iridium Short Burst Data (SBD): The narrowband satellite failover path uses the Iridium SBD protocol to transmit prioritised messages globally at low data rates when higher-bandwidth links are unavailable.
• NENA i3 / NG9-1-1 (ESInet): ESInet is modelled as the primary communication layer for PSAP operations, with automatic failover to satellite or mesh when the ESInet path degrades below configurable health thresholds.
• Meshtastic / LoRa (IEEE 802.15.4): The mesh radio integration supports Meshtastic devices operating over LoRa radio using IEEE 802.15.4-derived channel access, providing licence-free tactical mesh connectivity at the edge.
• GraphQL: All capability state, health queries, satellite message dispatch, and failover controls are exposed through a typed GraphQL API, enabling consistent programmatic access from any client.

Last Reviewed: 2026-04-02 Last Updated: 2026-04-14

Key Features#

• Multi-Layer Communication Stack: Three communication layers provide tiered resilience. Starlink provides high-bandwidth, low-latency connectivity as the primary layer. Iridium provides global narrowband coverage as the secondary layer for critical messages when Starlink is unavailable. Tactical mesh radio provides local area connectivity between nearby nodes independent of any satellite infrastructure. The system maintains awareness of all available layers and their current state.

• Automatic Failover Orchestration: When the active communication layer degrades below configurable thresholds (latency, bandwidth, packet loss), the system automatically promotes the next available layer. Failover is transparent to applications using the communication service: messages are routed through the best available path without operator intervention. When a preferred layer recovers, the system fails back to restore optimal performance.

• Health Monitoring with Degradation Thresholds: Each communication layer is continuously monitored for availability, latency, bandwidth, packet loss, and signal quality. Configurable thresholds define three states per layer: healthy, degraded, and unavailable. Dashboard displays show the real-time health of all communication layers, and alerts trigger when layers transition between states.

• Store-and-Forward Message Queuing: When no real-time communication path is available, outbound messages are queued locally with priority ordering. When connectivity is restored, queued messages are transmitted in priority order. Message delivery confirmation ensures that critical operational messages are not lost during communication blackouts. Queue status is visible to operators, showing pending message count and estimated transmission time.

• Tactical Edge Deployment: The communication stack is designed for forward-deployed nodes with constrained power, compute, and connectivity. The module runs on edge hardware with minimal resource requirements, managing communication layer selection and message queuing locally without dependence on a central server.

Use Cases#

• Disconnected Forward Operations: Forward operating bases maintain communication with headquarters through automatic failover between Starlink, Iridium, and mesh radio, with store-and-forward ensuring critical messages are delivered even during total communication loss.
• Convoy Communications: Moving convoys use mesh radio for vehicle-to-vehicle communication and satellite links for reach-back to headquarters, with automatic failover handling transitions between coverage areas.
• Maritime Operations: Vessels operating beyond terrestrial network coverage use satellite layers for persistent connectivity, with mesh radio for ship-to-ship coordination in close formation.
• Disaster Response: When terrestrial infrastructure is destroyed, the multi-layer communication stack provides immediate alternative connectivity for coordination between response teams and command centers.

Integration#

• CRDT Offline Collaboration: Document synchronisation traffic routes through the satellite mesh communication stack for delivery over the best available path.
• Tactical Awareness (TAK): CoT events are relayed through the communication stack, ensuring TAK situational awareness reaches all nodes regardless of connectivity state.
• Unified Operational Events: Communication layer state transitions (failover, failback, queue flush) generate events in the unified timeline.
• Drone Operations Management: Drone telemetry relay uses satellite mesh when line-of-sight datalinks are unavailable.
• System Health Monitoring: Communication layer health feeds into the platform-wide system health dashboard.

GraphQL: getCommunicationLayers, getCommunicationStackHealth, getSatelliteMessages, getFailoverEvents (queries); sendSatelliteMessage, triggerManualFailover, startHealthMonitoring, stopHealthMonitoring, updateCommunicationLayer, updateMeshNode (mutations).