Overview#
Argus gives coalition operators a single authenticated API to configure, query, and monitor Joint Range Extension Applications Protocol (JREAP) tactical data links in compliance with NATO STANAG 5518. JREAP carries the J-series tactical messaging of Link-16 over IP-based transport, extending the recognised picture beyond the range of a line-of-sight radio network so that geographically separated nodes share the same track and status data.
Coalition operators and system integrators manage the full lifecycle of a JREAP link without building bespoke persistence, classification handling, or audit infrastructure. Each link record holds its source node, target node, protocol version, live message count, error rate, operational status, and secrecy level, all scoped per organisation so that one partner never sees another's link estate. Link health is visible in real time, and classification-aware access control ensures every operator sees only what their clearance permits.
The module also bridges JREAP link state into the wider Argus operational picture. A degraded or misconfigured JREAP link surfaces immediately alongside CoT tracks, Link-16 J-series data, and MTFXML traffic in the Tactical Interoperability Workbench, so a fault in the range-extension path is treated as an operational event, not a silent infrastructure problem.
Key Features#
- Full Link Lifecycle Management: Provision, update, and retire JREAP links through one upsert-based operation, so re-running a configuration with the same link name updates the existing record rather than creating a duplicate.
- Real-Time Link-Health Visibility: Every link record carries its live message count, error rate, and active or inactive status, giving operators an immediate read on whether a range-extension path is carrying traffic cleanly or degrading.
- Status Roll-Up Statistics: A dedicated statistics view returns link counts grouped by status, so a watch officer can see at a glance how many links are active, inactive, or in error across the whole estate.
- Source and Target Node Mapping: Each link names its source node and target node explicitly, documenting the end-to-end topology of the range-extension network for both operators and auditors.
- Protocol Variant Tagging: Records capture the protocol version in use, distinguishing the JREAP-A, JREAP-B, and JREAP-C transport variants that govern how J-series messaging is carried over the link.
- Classification-Aware Access Control: Post-query clearance filtering enforces multi-level security, returning only records at or below the requesting operator's authorised secrecy level.
- Per-Organisation Data Sovereignty: All link records are persisted to PostgreSQL scoped per organisation, keeping each coalition partner's link estate isolated from every other tenant.
- Built-In Audit and Picture Emission: Every configuration event is written to the interoperability audit trail and emitted as a coalition-domain operational entity, so link changes are both traceable and visible on the shared picture.
Use Cases#
Coalition Air and Maritime Operations#
A combined task force extends its Link-16 picture across separated cells over IP transport. Operators provision the JREAP links that join those cells, then watch message count and error rate to confirm the range-extension path is healthy before relying on it for shared track data.
System Integration and Onboarding#
A systems integrator standing up a new coalition node configures its JREAP links programmatically through the authenticated API, mapping source and target nodes and tagging the correct protocol variant, without writing any bespoke storage or audit code.
Network Operations and Fault Detection#
A network watch team monitors link statistics grouped by status. When a link slips from active to error or its error rate climbs, the change appears in the operational picture beside other tactical data, prompting investigation before the degradation affects the shared track picture.
Multi-Level Security Environments#
A combined joint task force operating across classification boundaries relies on clearance filtering so that operators at one level never retrieve link records classified above their authorisation, satisfying multi-level security requirements for shared environments.
Exercise and Readiness Verification#
Interoperability teams confirm that the expected JREAP links are configured, active, and carrying traffic as part of certifying a coalition exercise or mission environment for go-live.
Integration#
The capability is exposed over GraphQL behind authenticated, organisation-scoped resolvers, so it plugs into the same authorised session a customer already uses for the rest of the Argus platform. Read paths return link inventories and status roll-ups; the write path provisions or updates a link by name.
Operations exposed:
- jreapLinks returns the organisation's JREAP links, with optional filtering by link variant and pagination.
- jreapStats returns link counts grouped by operational status.
- configureJreapLink performs an upsert-based provision or update of a single link.
Authentication uses OAuth2 bearer access tokens carrying JWT claims, with every field guarded by an authentication permission class and every resolver scoped to the caller's organisation. Each configuration event is recorded on the interoperability audit trail and emitted as a normalised coalition-domain operational entity, so JREAP link state flows onto the common operational picture using the same entity model as CoT, Link-16, and MTFXML feeds. Customers plug in their existing identity provider and link topology, and gain link-health telemetry, audit, and picture fusion without building any of that supporting infrastructure themselves.
Open Standards#
- NATO STANAG 5518 (JREAP, Joint Range Extension Applications Protocol): The NATO standardisation agreement governing range extension of tactical data links over IP and other long-haul bearers; the module persists and audits links explicitly against this standard designation.
- JREAP-A: The satellite-oriented JREAP transport variant for extending Link-16 J-series messaging over long-haul links; captured via the per-link protocol version field.
- JREAP-B: The point-to-point serial JREAP transport variant for extending J-series messaging over dedicated circuits; captured via the protocol version field.
- JREAP-C: The IP-network JREAP transport variant carrying Link-16 J-series messaging over standard internet protocol bearers; captured via the protocol version field.
- Link-16 J-Series Messaging: The tactical message family that JREAP range-extends; JREAP link state is fused on the operational picture alongside native Link-16 J-series track data.
Security & Compliance#
Every operation requires an authenticated, organisation-scoped session, and all link records are isolated per organisation in PostgreSQL so coalition partners remain segregated. Post-query clearance filtering enforces multi-level security by returning only records at or below the requesting operator's secrecy level. Each link record carries its own classification tag, and every configuration event is written to an immutable interoperability audit trail capturing the acting user, organisation, standard, record identifier, and secrecy level, supporting accountability and after-action review in coalition environments.
Last Reviewed: 2026-05-26 / Last Updated: 2026-05-26