NATO Interoperability: Link-16 / TADIL-J Integration

Overview#

Link-16 (standardised as TADIL-J -- Tactical Digital Information Link J) is the primary secure tactical data link used by NATO and allied forces to share real-time track data, targeting information, and status messages between air, sea, and land platforms. It operates in the J-series message format over a TDMA radio network and is the backbone of interoperability between fighter aircraft, naval vessels, AWACS platforms, and ground-based air defence systems. Argus integrates Link-16 via a SIMPLE-compatible message decoder, persisting decoded track data to PostgreSQL and making operational tracks available for fusion with other data sources on the common operational picture.

Key Features#

SIMPLE-Compatible Message Decoding#

Ingest Link-16 messages encoded in base64 via the

ingestLink16Message

mutation. The

decode_link16_message

adapter parses the binary J-series message format, extracting the message type (J2.0 Track report, J3.0 Reference point, J7.0 Electronic combat, etc.), track number, platform type, position (latitude, longitude, altitude), velocity, heading, and identity (friend/unknown/assumed friend/hostile). Decoded track data is immediately persisted to PostgreSQL.

Track Inventory#

Query the ingested track database via

link16Tracks

with filtering by track number, platform type, or classification level. Tracks are returned in chronological order with full decoded field sets. The

link16TrackStats

query returns counts by J-series message type and platform category (air, surface, subsurface, land).

SIMPLE Standard Alignment#

The integration is built against the LINK16_SIMPLE standard designation, aligning with NATO information exchange requirements for coalition Link-16 data sharing. This ensures decoded track data carries the correct source tagging for EDF audit trail compliance.

SecrecyLevel-Controlled Track Access#

Track records carry

secrecy_level

tags. Operational track data from a live tactical network segment is typically classified NATO CONFIDENTIAL or above. The row-level secrecy filter prevents lower-clearance users from accessing operational track data, satisfying multi-level security requirements for combined joint task force environments.

EDF Audit Trail#

Every Link-16 message ingestion generates an interop ingest audit record with source standard

LINK16_SIMPLE

, timestamp, decoded track count, and the acting user and organisation identifiers.

Use Cases#

Air Defence Common Operational Picture: Fuse Link-16 air track data with Argus surveillance zone definitions and geofencing alerts to trigger automated notifications when tracks enter or exit defined airspace boundaries.
Joint Task Force Coordination: Aggregate Link-16 tracks from multiple participating units into a single Argus operational picture, enabling command-level staff without direct Link-16 terminal access to see the tactical air picture.
Exercise Data Recording and Replay: Record all ingested Link-16 tracks during a coalition exercise for post-exercise analysis, timeline reconstruction, and lessons-learned reporting.
Cross-Domain Track Fusion: Correlate Link-16 air tracks with maritime AIS data, ATAK ground unit positions, and sensor-fused detections to build a comprehensive multi-domain operational picture.

Integration#

Available via GraphQL:

link16Tracks

link16TrackStats

(queries);

ingestLink16Message

(mutation). All operations require authentication and organisation scoping.

Standard: LINK16_SIMPLE / TADIL-J. Works alongside DIS (ground unit simulation fusion), HLA-RTI (coalition exercise environment), ATAK (ground force positions), and the Operational Picture domain.

Last Reviewed: 2026-03-18

Metadatos del modulo

Documentacion renderizada