How Battlefield Networks Actually Work: Tactical Data Links, Mesh Radios, and the Common Operating Picture

A brigade combat team on the move in eastern Europe occupies roughly 600 square kilometres. It contains several thousand soldiers, hundreds of vehicles, a dozen or more helicopters, and supporting artillery batteries spread across terrain that ranges from dense forest to open farmland intersected by rivers and urban areas. Every one of those elements needs to know where it is, where the enemy is, and where the other friendly units are. The brigade headquarters needs to receive sensor data from forward reconnaissance, fuse it with intelligence feeds from national assets, and push orders back down to subordinate battalions in near real time. All of this must work while the adversary is actively trying to jam radio frequencies, spoof GPS signals, and intercept every transmission.

This is the problem that battlefield networking exists to solve, and it is among the hardest networking problems in engineering. The constraints bear no resemblance to building a corporate LAN or even a large-scale civilian wireless network. There is no fixed infrastructure. The nodes are moving at speeds from 5 km/h (dismounted infantry) to 250 km/h (helicopters) to supersonic (fast jets). The radio spectrum is contested. The network topology changes constantly as units manoeuvre, take casualties, or are deliberately repositioned. Latency requirements vary from seconds (for logistics data) to milliseconds (for fire control). And the whole system must operate across multiple classification levels, often between coalition partners who do not share the same cryptographic keys.

This article covers the full stack of battlefield networking: tactical data links, soldier radios, vehicle networks, blue force tracking, the common operating picture, satellite backhaul, electronic warfare threats, and where the technology is heading.

1. Why Battlefield Networking Is Hard

The civilian internet solves connectivity with an abundance of fixed infrastructure: fibre optic cables, cell towers cemented to rooftops, data centres with redundant power. Military tactical networks have none of that. The core engineering challenges are worth enumerating because they drive every design decision in the systems described in later sections.

Mobility and topology change. A MANET (Mobile Ad-hoc Network) serving a mechanised battalion might have 200 radio nodes. When the battalion advances 30 kilometres over four hours, every node's position relative to every other node changes continuously. Links that existed ten minutes ago may be blocked by a ridgeline. New links form as units converge. The routing layer must adapt in seconds, not minutes.

Terrain and propagation. UHF and VHF signals do not propagate well through dense urban environments, forests, or hilly terrain. A soldier in a valley cannot reach a radio relay on the far side of a 400-metre hill. The path loss in the 225 to 400 MHz military UHF band over rough terrain with vegetation is substantially worse than free-space models predict. Real-world planning tools like the Terrain Integrated Rough Earth Model (TIREM) and the Irregular Terrain Model (ITM) are used to predict coverage, but actual conditions vary with weather, foliage density, and soil moisture.

Spectrum scarcity and interference. The electromagnetic spectrum allocated for military use is finite. A brigade might have hundreds of radios all competing for bandwidth in UHF and L-band. Frequency planning, the process of assigning channels and time slots to avoid mutual interference, is a major staff function that can take days to complete for a large exercise. In combat, the plan rarely survives contact with the adversary's electronic warfare capabilities.

Jamming and electronic attack. A peer adversary fields dedicated electronic warfare units whose purpose is to deny communications. Russian EW systems such as the Krasukha-4 and the R-330Zh Zhitel can jam across wide frequency bands. Narrowband jamming can deny a specific channel; broadband barrage jamming raises the noise floor across entire bands. Every tactical radio system must incorporate electronic counter-countermeasures (ECCM): frequency hopping, spread spectrum, power management, directional antennas.

Coalition interoperability. A NATO operation involves forces from 30+ nations, each with different radio systems, different national cryptographic devices, and different battle management software. Link 16 provides a common standard for air and maritime operations, but at the land tactical level, interoperability remains a persistent challenge. The NATO Federated Mission Networking (FMN) initiative attempts to address this, but progress is measured in years, not months.

Classification and cryptographic separation. Information flows at multiple classification levels: UNCLASSIFIED, NATO RESTRICTED, NATO SECRET, national SECRET, and sometimes higher. A single vehicle might carry radios operating on different networks at different classification levels, each with its own cryptographic keying material. Cross-domain solutions that allow data to flow between classification levels are expensive, complex, and introduce latency.

Bandwidth constraints. Even with modern wideband waveforms, the total data throughput available to a tactical formation is a tiny fraction of what a civilian enterprise takes for granted. A company-level MANET might sustain 2 to 10 Mbps aggregate throughput shared among 40 nodes. That must carry voice, position reports, sensor imagery, video feeds, and battle management system data. Bandwidth management and quality of service (QoS) are not optional features; they are survival requirements.

2. Link 16 (TADIL J / MIDS): The NATO Standard Tactical Data Link

Link 16 is the most widely deployed tactical data link in the Western world. It connects fighter aircraft, warships, ground-based air defence systems, and command centres into a shared network that exchanges track data, weapons coordination messages, and electronic warfare information. If you have ever seen a military briefing showing blue and red symbols on a map with tracks updating in near real time, Link 16 is almost certainly part of the underlying infrastructure.

Architecture and TDMA Structure

Link 16 uses a Time Division Multiple Access (TDMA) scheme. Time is divided into 12.8-minute epochs. Each epoch contains 98,304 time slots. Each time slot is 7.8125 milliseconds long. Participants are pre-assigned specific time slots in which they are authorised to transmit, and they receive during all other slots. This is a key architectural decision: there is no contention for access. A transmitter knows exactly when it will transmit, and all receivers know when to listen for each participant. This eliminates the collision problem that plagues CSMA-based protocols, but it means the network must be planned in advance. Time slot assignments are distributed as part of the network design, produced by a tool called the MIDS/JTIDS Network Design facility.

Participants are organised into Network Participation Groups (NPGs). An NPG is a logical grouping of units that share a common set of time slots and exchange a specific type of data. For example, NPG 1 (the Surveillance NPG) carries air track data. NPG 6 (the Fighter-to-Fighter NPG) carries messages between fighter aircraft within a flight. A single Link 16 terminal can participate in multiple NPGs simultaneously. The NPG concept allows the network to be partitioned so that, for example, the enormous volume of surveillance data exchanged between E-3 AWACS aircraft and ground-based air defence sites does not consume time slots needed for fighter coordination.

Frequency Hopping and the Physical Layer

Link 16 transmits in the 960 to 1215 MHz band (L-band), which is shared with secondary surveillance radar (SSR) and distance measuring equipment (DME) used in civilian aviation. To avoid interference and provide some protection against jamming, Link 16 uses a pseudo-random frequency hopping pattern across 51 frequencies within this band. The hopping pattern is generated from a cryptographic algorithm using a shared key, so only participants with the correct cryptographic variables can follow the hops.

Each time slot can carry data at one of several packing structures. The standard packing (Standard Double Pulse) provides approximately 28.8 kbps per time slot. With multiple time slots assigned, a single terminal can achieve data rates up to approximately 238 kbps aggregate. This is not a lot of bandwidth by modern standards. Link 16 was designed in the 1970s and 1980s, when 238 kbps was substantial. Today, it is a constraint that limits what kind of data can be exchanged. Link 16 carries structured message data (track positions, identification, weapons status), not video streams or large imagery files.

The terminal hardware is the MIDS (Multifunctional Information Distribution System). The primary variant in NATO service is the MIDS-JTRS (Joint Tactical Radio System), manufactured by L3Harris Technologies and ViaSat (now part of L3Harris after the 2023 acquisition). MIDS-JTRS is a four-channel terminal that supports Link 16, TACAN (tactical air navigation), and concurrent operations. The terminal fits into a standard LRU (line replaceable unit) form factor for aircraft installation. Ground-based versions are rack-mounted in shelter systems.

Message Formats

Link 16 data is structured into J-series messages. The "J" designates TADIL-J, the formal name for the Link 16 message standard, documented in MIL-STD-6016 (US) and STANAG 5516 (NATO). Key message types include:

J2.2 (Air Track): Reports the position, identity, speed, heading, and altitude of an air target. This is the workhorse message for air surveillance. When an E-3 AWACS detects an aircraft with its radar and transmits the track over Link 16, it sends a J2.2 message.

J2.3 (Surface Track): Reports the position and identity of a surface contact (ship, vehicle).

J3.0 (Reference Point): Reports the position of a fixed geographic reference point, such as a waypoint, an airfield, or a target area.

J3.2 (Emergency Point): Used for reporting emergency locations such as downed aircrew positions.

J7.0 (Track Management): Used to assign track numbers, correlate tracks between different sensors, and manage the overall track picture.

J12.6 (Electronic Warfare Control/Coordination): Coordinates electronic warfare actions, such as designating a jamming target or reporting an emitter location.

Each J-series message is composed of fixed-format words (75-bit data words). The structure is rigidly defined, which makes parsing efficient but limits flexibility. Adding a new message type or modifying an existing one requires a formal change to the standard, a process that takes years through the NATO committee structure.

Cryptography

Link 16 transmissions are encrypted using KGV-135B or equivalent national cryptographic devices that implement TSEC/KGV-135 series algorithms. The cryptographic material (keys) must be distributed to all participating terminals before operations begin. Key distribution is a significant logistical challenge, particularly for coalition operations where not all nations may be authorised to receive the same key material. There is ongoing work to move towards over-the-air rekeying (OTAR) to reduce the burden.

Line of Sight and Relay

Link 16 is a line-of-sight (LOS) system. At L-band frequencies, there is no ionospheric reflection or significant diffraction around terrain. Two terminals can only communicate if they have an unobstructed radio path between them. For aircraft at high altitude, LOS extends to several hundred kilometres. For ground terminals, LOS may be limited to tens of kilometres depending on antenna height and terrain.

To extend coverage, Link 16 supports a relay function. A terminal can be designated as a relay unit (RU), which retransmits messages received in one time slot in a different time slot. An airborne relay, such as an E-3 AWACS orbiting at 9,000 metres, can bridge messages between two ground terminals that cannot see each other. This extends the effective network range but doubles the latency for relayed messages and consumes additional time slots.

3. Link 22 (NILE): The IP-Enabled Successor

Link 22 was developed under the NATO Improved Link Eleven (NILE) programme to address the limitations of Link 16 and its predecessor, Link 11. Where Link 16 is a fixed-format, circuit-oriented data link, Link 22 introduces key architectural improvements.

IP routing. Link 22 incorporates network layer routing, allowing messages to traverse multiple hops without the rigid relay structure of Link 16. This makes the network more resilient: if a direct link fails, data can be rerouted through alternative paths. The protocol stack is closer to conventional IP networking than Link 16's bespoke architecture.

HF beyond-line-of-sight. Link 22 supports transmission over HF (High Frequency, 2 to 30 MHz) radio in addition to UHF. HF signals can propagate beyond line of sight via ionospheric reflection (skywave), potentially reaching distances of several thousand kilometres. This gives Link 22 a capability that Link 16 cannot match: connectivity between units that are over the horizon from each other without satellite relay. The HF channel is low bandwidth (typically a few kbps), so it carries only the most critical messages, but its existence transforms the network architecture for maritime operations where ships may be separated by hundreds of nautical miles.

Improved ECCM. Link 22's waveform design incorporates more sophisticated spread-spectrum techniques and error correction coding than Link 16, providing improved resistance to jamming.

Flexible message catalogue. While Link 22 still uses structured messages, the format is more extensible than Link 16's J-series, making it somewhat easier to add new message types as requirements evolve.

Link 22 reached initial operational capability with several NATO navies in the early 2020s. France, Germany, Italy, Spain, the United Kingdom, and the United States are all participating nations. However, deployment has been slower than originally planned, and Link 16 will remain the dominant tactical data link for at least another decade. Many platforms will carry both Link 16 and Link 22 terminals, using Link 16 for air operations (where its installed base is enormous) and Link 22 for maritime networking.

4. Soldier-Level Radios and MANETs

While Link 16 and Link 22 connect aircraft, ships, and headquarters, the individual soldier on the ground needs a different class of radio. The requirements at this echelon are portability (the radio cannot weigh more than about 1.5 kg with battery), robustness (it will be dropped, immersed in water, coated in mud), and the ability to form ad-hoc networks with other radios in the section and platoon without centralised network planning.

Software-Defined Radios

Modern soldier radios are software-defined radios (SDRs), meaning the modulation, coding, and networking protocols are implemented in software running on a general-purpose processor and FPGA rather than in fixed hardware. This allows a single radio to support multiple waveforms: a legacy single-channel voice mode for interoperability with older equipment, a modern MANET waveform for data networking, a SATCOM waveform for reach-back, and potentially others.

L3Harris AN/PRC-163: This is the two-channel leader radio in the US Army's HMS (Handheld, Manpack, and Small Form Fit) programme. It operates from 30 MHz to 2.6 GHz, supports the MUOS SATCOM waveform, SRW, ANW2, SINCGARS, and HAVEQUICK II. It weighs approximately 1.0 kg for the handheld variant. The two-channel capability allows simultaneous operation on two different networks, which is critical for a squad leader who needs to talk to both higher headquarters and the soldiers in the squad.

Thales SYNAPS: Developed by Thales in France, SYNAPS is a family of SDRs covering handheld (SYNAPS-H), manpack (SYNAPS-M), and vehicular (SYNAPS-V) form factors. SYNAPS implements the ESSOR (European Secure Software-defined Radio) HDR (High Data Rate) waveform, which is the European collaborative waveform developed by a consortium including France, Finland, Germany, Italy, Poland, and Spain. SYNAPS radios have been selected for the French CONTACT programme (Communications Numeriques Tactiques) and are being fielded across the French Army.

Elbit Systems E-LynX: Developed by Elbit Systems in Israel with significant European operations, E-LynX is a software-defined radio family that implements a proprietary broadband MANET waveform. E-LynX radios have been selected by several European armed forces, including Switzerland, and form part of Elbit's TORCH battle management system ecosystem. The E-LynX MANET supports data rates of up to 8 Mbps in wide channels and provides integrated voice, data, and video distribution.

Rohde & Schwarz SOVERON: The German company Rohde & Schwarz produces the SOVERON family of SDRs for vehicular and dismounted use. SOVERON D (dismounted) and SOVERON HR (handheld radio) implement the German-developed SVFuA (Software-defined Vehicle Radio System) waveform architecture. SOVERON radios are a key component of Germany's Digitisation of Land-Based Operations (D-LBO) programme.

MANET Waveforms and Routing

A MANET waveform is the combination of physical layer modulation, medium access control (MAC), and network layer routing that allows a group of radios to form a self-organising mesh network. When a soldier turns on a MANET-capable radio, it scans for neighbouring radios, exchanges cryptographic authentication, and joins the network. If two nodes cannot reach each other directly, intermediate nodes relay traffic automatically.

The key waveforms in Western service or development include:

SRW (Soldier Radio Waveform): Developed by the US for networking at the squad and platoon level. SRW operates in the UHF band and provides modest data rates (approximately 1.2 to 1.5 Mbps) with low latency. It was designed for small networks (up to about 40 nodes) and uses a TDMA MAC with adaptive time slot assignment.

ANW2 (Adaptive Networking Wideband Waveform): A higher-bandwidth waveform for vehicle-mounted radios, providing throughput of 5+ Mbps. ANW2 is designed for the vehicular and manpack echelon where more spectrum and higher transmit power are available. It incorporates MIMO (Multiple Input, Multiple Output) antenna techniques for increased throughput and resilience.

ESSOR HDR (European Secure Software-defined Radio, High Data Rate): The European collaborative waveform designed to enable interoperability between different national SDR platforms. ESSOR HDR operates in the UHF band and provides data rates comparable to SRW. The critical difference is that ESSOR is a multinational programme, meaning a French SYNAPS radio running ESSOR can communicate directly with a German SOVERON radio running the same waveform. This is the European answer to the interoperability problem.

Routing in tactical MANETs is a specialised problem. Standard IP routing protocols (OSPF, BGP) were designed for networks with static or slowly changing topologies and reliable links. MANET routing protocols must handle rapid topology changes, high packet loss rates, and asymmetric links (a radio can hear a neighbour, but the neighbour might not hear it due to terrain or antenna orientation).

The two broad categories are proactive and reactive protocols. Proactive protocols (such as OLSR, the Optimised Link State Routing protocol, specified in RFC 3626) maintain routing tables at all times by periodically exchanging topology information. This means a route is always available when data needs to be sent, but the periodic broadcasts consume bandwidth. Reactive protocols (such as AODV, Ad hoc On-Demand Distance Vector, in RFC 3561) discover routes only when needed, reducing overhead but introducing route discovery latency. Most military MANET waveforms use proprietary routing protocols that incorporate elements of both approaches, optimised for the specific characteristics of the waveform's MAC layer and the expected operational scenarios.

5. Vehicle and Platform Networks

A modern infantry fighting vehicle such as the PUMA (manufactured by Rheinmetall and KMW for the German Army) or the AJAX (General Dynamics UK, for the British Army) is a complex sensor and communications platform in its own right. It carries multiple sensors (thermal imaging sights, laser rangefinders, sometimes a radar or an acoustic shot-detection system), multiple radio systems, an inertial navigation system with GPS, and a battle management system terminal. All of these must be integrated internally and connected to the wider tactical network.

Internal Vehicle Networks

Inside the vehicle, sensors and systems communicate over military-grade data buses. Older vehicles used MIL-STD-1553B, a robust but low-bandwidth (1 Mbps) serial bus standard dating from the 1970s. Newer platforms use Gigabit Ethernet (defined in the VICTORY, Vehicular Integration for C4ISR/EW Interoperability, standard in the US, and GVA, Generic Vehicle Architecture, in the UK and NATO). GVA, specified in UK Defence Standard 23-009, mandates an Ethernet-based backbone within the vehicle, with standardised data models and interfaces. This means that a sensor module from one manufacturer can, in principle, be integrated with a battle management system from another manufacturer, as long as both conform to GVA.

The vehicle's Battle Management System (BMS) terminal is the crew's primary interface to the digital battlespace. The BMS displays a moving map with blue force positions, enemy tracks, and operational graphics (boundaries, objectives, routes). The crew can create reports (contact reports, spot reports, logistics status) and send them over the tactical radio network. The BMS also receives orders and overlays from higher headquarters.

Major BMS Systems

Elbit Systems TORCH-X: A comprehensive C4I (Command, Control, Communications, Computers, and Intelligence) system used by the Israel Defence Forces and several European and Asia-Pacific customers. TORCH-X runs on ruggedised computing hardware and provides commanders at all echelons with a common operational picture. At the vehicle level, TORCH-X interfaces with vehicle sensors and with Elbit's E-LynX radios to exchange track data and messages over the MANET.

Thales ATLAS: Thales developed the ATLAS BMS for the French Army's SCORPION programme, which is a comprehensive modernisation of France's medium-weight armoured forces. ATLAS integrates with SYNAPS radios and the French CONTACT communications system. It provides collaborative combat capabilities, allowing vehicles to share sensor detections automatically. When a JAGUAR reconnaissance vehicle's optronic turret detects an enemy vehicle, the detection can be automatically shared over the network as a track, appearing on every other ATLAS terminal in the battlegroup.

BAE Systems BMS / MORPHEUS: The UK's battlefield information system, part of the Morpheus programme, replaces the legacy Bowman system. Morpheus provides the communication infrastructure and BMS for British land forces, integrating new SDR radios with Falcon, the existing wide-area trunk communications system. The BMS component provides situational awareness, messaging, and collaborative planning tools.

Systematic SitaWare: A Danish company, Systematic, produces the SitaWare suite of C2 (Command and Control) software. SitaWare Headquarters provides operational planning and coordination tools, while SitaWare Edge and SitaWare Frontline provide lighter-weight interfaces for vehicles and dismounted soldiers. SitaWare is used by numerous NATO nations, including Denmark, the UK, Germany, Australia, and the United States. Its widespread adoption makes it a de facto interoperability tool: if two different nations both use SitaWare, their data exchange problems are substantially simplified.

Data Sharing From Vehicle to Network

When a vehicle's thermal imager identifies a target at a range of 3,200 metres, the process of sharing that detection with the network proceeds through several steps. The fire control system computes the target's position using the vehicle's own GPS position, the turret bearing, and the laser rangefinder distance. This produces a target grid reference (in UTM or MGRS format) with an associated accuracy estimate. The BMS software packages this as a track report (or contact report) in a standardised message format, typically conforming to MIP (Multilateral Interoperability Programme) standards or NATO's ADatP-3/ADatP-36 message formats. The message is transmitted over the MANET radio to other vehicles in the platoon and upwards to the company and battalion headquarters. At each echelon, the incoming track is correlated with existing tracks to avoid duplication.

6. Blue Force Tracking

Blue force tracking (BFT) is the capability to plot every friendly unit on a map in near real time. It sounds simple. It is, from a concept standpoint, nothing more than each unit periodically broadcasting its GPS position along with its unit identifier, and a central system aggregating those positions and distributing them to all authorised subscribers. The engineering, however, involves substantial complexity.

Architecture

A typical BFT system has three layers. At the bottom is the tracking device: a GPS receiver coupled with a radio transmitter. The device periodically (typically every 30 seconds to 5 minutes, configurable based on echelon and operational requirements) computes its position and transmits a short message containing unit identifier, position, time stamp, speed, and heading.

The transmission medium depends on the architecture. In the US Joint Battle Command Platform (JBC-P, the successor to FBCB2), position reports are transmitted via the Blue Force Tracking satellite network, which uses L-band SATCOM transponders on commercial satellites. This provides global coverage but introduces latency and bandwidth constraints. European systems such as the French SIR (Systeme d'Information Regimentaire) and the German FuInfoSys use tactical radio networks (MANET or trunk radio) for BFT within the formation, with SATCOM backhaul to higher echelons.

In the middle layer, a server at brigade or division headquarters receives all position reports, validates them, and maintains a database of current positions. The server also receives position data from other sources: Link 16 tracks (for air assets), AIS (Automatic Identification System) data for maritime units, and manual position reports entered by operators.

At the top layer, the aggregated blue force picture is distributed back down to all subscribers. Every BMS terminal in the formation displays the blue force overlay on its map. This is typically done via the same tactical radio network, using multicast or publish-subscribe protocols to minimise bandwidth.

Fratricide Prevention

The military term for friendly fire is fratricide, and preventing it is one of the primary justifications for BFT investment. In the 1991 Gulf War, roughly 24% of US combat casualties were caused by friendly fire. In the 2003 invasion of Iraq, the figure was still significant despite improvements in situational awareness. BFT directly addresses this by giving every commander and crew a continuously updated picture of where friendly forces are.

The mechanism is straightforward but depends on several things going right simultaneously. The BFT position must be accurate (which requires GPS to be working and the report to be recent), the display must be up to date (which requires the network to deliver position reports promptly), and the operator must actually check the BFT display before engaging a target (which is a training and human factors issue, not purely a technology one).

Combat identification (CID) procedures layer on top of BFT. Before engaging a target, a crew is required to verify that the target is not friendly. BFT provides one input to that verification: "There is no friendly track at the location where I see this target through my sight." But BFT has limitations. If a friendly unit's radio has failed, or if GPS is being jammed and the position report is stale, the BFT picture may not reflect reality. Doctrine accounts for this by requiring multiple means of identification and by maintaining minimum safe distances between friendly units and indirect fire targets.

SitaWare and the Danish Model

Systematic's SitaWare provides integrated BFT as part of its C2 suite. The SitaWare Frontline application, running on a ruggedised Android tablet carried by a soldier, uses the device's GPS and the tactical radio network to report positions and display the blue force picture. The lightweight nature of the hardware (a tablet and a small radio, rather than a dedicated BFT terminal) has made this approach attractive to numerous armed forces. Denmark, which developed the concept domestically, has demonstrated BFT down to the individual soldier level using SitaWare Frontline paired with L3Harris or Thales handheld radios.

7. The Common Operating Picture

The Common Operating Picture (COP) is the holy grail of military C2 systems. It is the ambition to present every commander with a single, coherent, real-time display that integrates all relevant information: blue force positions, enemy tracks, sensor coverage, weather, terrain analysis, logistics status, and operational graphics (phase lines, boundaries, objectives).

Data Fusion

Building a COP requires fusing data from radically different sources. Consider a single enemy armoured column detected by multiple sensors:

A reconnaissance UAV (an Airbus Tracker or a Schiebel Camcopter S-100) spots the column with its electro-optical camera and reports three vehicles at a specific grid reference.

A ground surveillance radar (such as the Thales Ground Master 60, operating in a ground surveillance mode) detects moving targets in the same area and reports five radar returns.

A Link 16 participant (perhaps a helicopter with a radar) transmits a track on the same group.

An intelligence report from signals intelligence (SIGINT) analysis indicates that a known enemy battalion radio net has been emitting from that area.

The COP system must determine that all of these reports describe the same entity, assign it a single track number, compute the best estimate of its position and composition, and present it to the commander as one icon on the map, not four separate reports. This is the track correlation problem, and it is computationally and doctrinally complex.

Track Correlation Challenges

Positional error. Each sensor reports positions with different accuracies. The UAV camera might provide a 10-metre circular error probable (CEP). The ground radar might provide 50-metre CEP at that range. The Link 16 track might have been generated by an airborne radar with 100-metre CEP. The SIGINT report might only localise the emitter to a 500-metre radius. The correlation algorithm must account for these different error distributions when deciding if two reports describe the same target.

Temporal offset. Data arrives at different times. The UAV report might be 15 seconds old by the time it reaches the fusion system. The radar track might be 3 seconds old. For a column moving at 40 km/h, that 15-second delay means the actual position could differ from the reported position by approximately 170 metres. The fusion system must propagate reported positions forward in time (dead reckoning) before comparing them.

Identity ambiguity. The UAV reports "three vehicles." The radar reports "five returns." Are these the same group, or are there two separate groups close together? The radar might be detecting vehicles that the UAV's narrow field of view missed. Or the radar might be generating false returns from terrain clutter. Resolving this requires combining sensor performance models with tactical intelligence about enemy organisation.

Classification conflicts. One source identifies a target as a T-72 tank. Another source classifies the same detection as a BMP-2 infantry fighting vehicle. The fusion system must have rules for resolving such conflicts, typically weighting the source with higher classification confidence (an imagery analyst examining high-resolution video is generally more reliable than an automated radar classifier).

Display and Dissemination

The fused COP is displayed on command-post workstations running C2 software such as SitaWare Headquarters, Thales CommandoNet, or the NATO C2 Information Services (C2IS) toolset. The display typically uses MIL-STD-2525D standard military symbology (or the NATO equivalent, APP-6D): blue rectangles for friendly ground units, red diamonds for enemy ground units, semicircles for air tracks, and so on. Each symbol can be queried to show the underlying data: track history, source sensor, classification confidence, time of last update.

The COP must be distributed to subordinate units, but at reduced fidelity to conserve bandwidth. A battalion headquarters might see every individual vehicle track, while a company commander sees only platoon-level icons. This filtering, sometimes called tailored COP or TCOP, is essential when the network cannot support pushing the full picture to every node.

8. Satellite Communications for Tactical Networks

The tactical radio networks described above, MANETs, Link 16, trunk radio, all have limited range. A MANET might cover a brigade area of operations (roughly 30 by 20 kilometres). Link 16 extends to line-of-sight distances. But a division or corps headquarters needs to communicate with its brigades, with national headquarters hundreds or thousands of kilometres away, and with coalition partners. Satellite communications (SATCOM) provides this beyond-line-of-sight backbone.

Military SATCOM Systems

Skynet 5 (United Kingdom). Operated by Airbus Defence and Space under a Private Finance Initiative contract with the UK Ministry of Defence, Skynet 5 provides UHF and SHF (Super High Frequency, X-band and beyond) military SATCOM to UK and NATO forces. The constellation consists of satellites in geostationary orbit providing coverage of the UK's primary areas of interest: Europe, the Middle East, and the Atlantic. Skynet 5 supports voice, data, and video at various data rates depending on terminal size and atmospheric conditions. A typical vehicular SATCOM terminal (such as the Elbit SATCOM-on-the-Move, or SOTM, systems) can achieve 512 kbps to 2 Mbps on Skynet.

Syracuse IV (France). The Syracuse IV constellation, with first satellites launched in 2021 and 2022, provides X-band and Ka-band military SATCOM for French forces. Built by Thales Alenia Space and Airbus Defence and Space, Syracuse IV offers higher throughput and better anti-jam capability than its predecessor, Syracuse III. Ka-band operation provides higher bandwidth but is more susceptible to rain fade, requiring adaptive coding and modulation.

SatcomBW (Germany). Germany's military SATCOM capability is provided by the SatcomBW system, which includes dedicated military payloads hosted on the COMSATBw satellites and leased commercial SATCOM capacity. The system provides UHF SATCOM for narrowband communications (voice and low-rate data) and SHF SATCOM for higher-bandwidth applications.

NATO SATCOM. NATO operates the NATO Satellite Communication (SATCOM) capability, which provides wideband communications between NATO headquarters, deployed forces, and member nations. The capability is provided through a combination of dedicated NATO capacity on allied national satellites and commercial SATCOM leases.

Terminal Types

Tactical SATCOM terminals range from small handheld devices to large vehicle-mounted systems:

Manpack SATCOM: A soldier-portable terminal with a directional antenna that can be set up in a few minutes. Typical data rates are 9.6 to 128 kbps. Used for reach-back from small teams (special forces, forward observers) to higher headquarters when beyond tactical radio range.

Vehicular SOTM (SATCOM on the Move): A vehicle-mounted terminal with a stabilised antenna that maintains satellite lock while the vehicle is moving. Data rates of 512 kbps to several Mbps are achievable depending on antenna size and satellite capacity. These terminals connect vehicles and mobile command posts to the rear network while on the move.

Transportable VSAT: A larger terminal (typically 1.2 to 2.4 metre dish) set up at a static headquarters or logistics node. Provides the highest data rates (10+ Mbps) but requires time to set up and is not mobile while operating.

Bandwidth Management

SATCOM bandwidth is expensive and limited. A single Skynet 5 transponder might provide 20 to 40 Mbps of total capacity, shared across an entire theatre of operations. When a brigade headquarters requests a video teleconference with division headquarters, that single session might consume 2 Mbps, representing a significant fraction of available capacity.

Bandwidth management is performed by a network control centre that allocates SATCOM resources according to priority and mission need. Voice traffic is typically given assured minimum bandwidth. Battle management system data (position reports, orders, intelligence updates) gets the next priority. Imagery and video are allocated bandwidth on a best-effort basis, often compressed heavily (JPEG2000 for still imagery, H.264/H.265 for video at low bitrates). Routine administrative traffic (email, personnel databases) gets whatever is left.

9. Electronic Warfare Threats to Networks

Every tactical network described in this article is vulnerable to electronic attack. A peer adversary with capable EW systems can degrade or deny communications across significant portions of the electromagnetic spectrum. Understanding these threats is necessary to understand why tactical networks are designed the way they are.

Jamming of Tactical Radios

A jammer can target tactical MANET radios by transmitting high-power noise in the UHF band where these radios operate. The effectiveness depends on the jammer's power, its distance from the victim radios, and the ECCM capabilities of the radios.

Frequency hopping provides the first layer of protection. If a radio hops across 200 channels in a band, a narrowband jammer on a single channel only disrupts 1/200th of the transmissions. The radio's forward error correction coding can typically recover from this level of interference. To counter frequency hopping, the adversary must either use broadband barrage jamming (spreading power across the entire hopping band, which reduces the effective jamming power per channel) or use a follower jammer that detects the frequency of each hop and retransmits a jamming signal on that frequency before the hop ends. Follower jamming is technically demanding, requiring detection, frequency measurement, and response within microseconds.

Spread spectrum techniques distribute the signal energy across a wide bandwidth using a pseudo-random code. The receiver uses the same code to de-spread the signal, concentrating the energy while spreading any jamming signal. The processing gain (the ratio of spread bandwidth to information bandwidth) provides a measure of jam resistance. A waveform with 20 dB of processing gain can tolerate a jammer that is 100 times more powerful than the desired signal (at the receiver's antenna).

Power management is another ECCM technique. By transmitting at the minimum power necessary to reach the intended receiver, the radio minimises its signature and reduces the area over which a jammer must operate to be effective. Modern MANET radios adjust transmit power dynamically based on link quality measurements.

Directional antennas concentrate transmitted energy toward the intended receiver and attenuate signals (including jamming) from other directions. Vehicle-mounted MANET radios can use phased array or sector antennas to achieve 6 to 12 dB of directional gain, which directly reduces the effective jamming power.

GPS Denial

Blue force tracking depends on GPS. If GPS is jammed or spoofed, position reports become inaccurate or misleading. GPS jamming is comparatively easy: a low-power jammer can deny GPS over a radius of tens of kilometres because the GPS signal arriving from orbit is extremely weak (approximately -130 dBm at the Earth's surface).

Military GPS receivers using the M-code signal have better anti-jam performance than civilian receivers, partly due to the higher effective power of the M-code broadcast and partly due to more sophisticated receiver processing (null-steering antennas, beamforming). However, a sufficiently powerful jammer can still overwhelm even military GPS.

Countermeasures include inertial navigation systems (INS) that provide position estimates when GPS is denied. Modern tactical INS units using ring laser gyroscopes or fibre-optic gyroscopes can maintain position accuracy of about 1 km per hour of GPS denial. For vehicle-mounted systems, odometry (wheel rotation counting) and terrain-referenced navigation can extend the accuracy further. The key point is that BFT degrades gracefully under GPS denial: positions become less accurate over time, but the system does not fail catastrophically.

Jamming of Link 16

Link 16's frequency hopping across 51 frequencies in L-band provides moderate jam resistance. An adversary would need to barrage-jam a significant portion of the 960 to 1215 MHz band to effectively deny Link 16. This requires substantial jammer power because the band is 255 MHz wide. However, Link 16 operates at relatively low data rates with short time slots, which limits the processing gain available. Against a peer adversary with high-power standoff jammers, Link 16 connectivity in contested airspace is not guaranteed. This is one of the motivations for developing Link 22 (with better ECCM) and for investigating alternative waveforms for air operations.

Cyber Threats

Beyond RF jamming, tactical networks face cyber threats. If an adversary can access the network through a compromised node or a vulnerability in the protocol stack, they could inject false track data, corrupt routing tables, or exfiltrate intelligence. The cryptographic protections (COMSEC) on Link 16 and MANET radios are designed to prevent unauthorised access, but implementation vulnerabilities are always possible. Network monitoring and intrusion detection systems are being integrated into tactical network management tools, though this is a developing field in the military context.

10. Future Directions

Battlefield networking is evolving rapidly, driven by the return of great-power competition and the recognition that information advantage is as decisive as firepower.

JADC2 (Joint All-Domain Command and Control)

The US Department of Defense's JADC2 concept envisions connecting every sensor and shooter across all domains (land, sea, air, space, cyber) into a seamless network. The goal is to reduce the sensor-to-shooter timeline from minutes to seconds. In practical terms, this means that an F-35's radar detection of a surface target could be transmitted directly to an artillery battery's fire control system, bypassing multiple echelons of manual processing. The technical challenges are immense: the data formats, classification levels, and network protocols used by the Air Force, Navy, and Army are all different, and integrating them requires both technical standards and institutional change.

NATO DIANA and European CJTF Networking

NATO's DIANA (Defence Innovation Accelerator for the North Atlantic) initiative funds technology development in areas including secure communications and AI for network management. European nations are also investing in combined joint task force (CJTF) networking capabilities through programmes like the European Defence Fund's (EDF) military mobility and C2 projects.

The ESSOR programme continues to develop collaborative waveforms that enable interoperability between European SDR platforms. The next phase of ESSOR aims to deliver a wideband networking waveform that can replace proprietary national waveforms for coalition operations, providing a truly interoperable European tactical internet.

Mesh Satellite Constellations

The most transformative technology on the horizon may be Low Earth Orbit (LEO) satellite constellations for tactical communications. Commercial LEO constellations (Starlink, OneWeb, SES mPOWER) have demonstrated that thousands of small satellites can provide high-bandwidth, low-latency connectivity globally. Military variants or dedicated military use of commercial LEO constellations could provide the bandwidth that tactical networks desperately lack.

The European Space Agency and several national defence agencies are studying LEO SATCOM for military use. Airbus Defence and Space and Thales Alenia Space have both proposed military LEO constellation concepts. The attraction is obvious: a LEO constellation at 550 km altitude provides round-trip latency of approximately 10 to 20 milliseconds (compared to 240 milliseconds for GEO), and a large constellation can provide aggregate bandwidth of hundreds of Gbps over a theatre of operations.

The challenges are equally obvious. LEO satellites move relative to the ground, requiring tracking antennas or electronically steered phased arrays. The satellites are vulnerable to anti-satellite weapons. The ground terminals must be small enough for tactical use. And the entire system must be resilient to jamming, which is easier against LEO signals (lower link margin) than against GEO military SATCOM.

SES, headquartered in Luxembourg, is developing its mPOWER MEO constellation specifically with government and military customers in mind, offering higher resilience and lower latency than traditional GEO SATCOM. The constellation uses digital transparent processors that allow flexible allocation of bandwidth to specific geographic areas, matching capacity to demand.

AI for Network Management

Managing a tactical network with hundreds of nodes, multiple waveforms, contested spectrum, and dynamic topology is currently a labour-intensive task requiring specialist signal officers and network managers. AI and machine learning are being investigated for automating several aspects of network management:

Dynamic spectrum management: An AI system that monitors spectrum usage and jamming activity and automatically reassigns frequencies and waveforms to maintain connectivity.

Predictive routing: Using terrain data, unit movement plans, and historical link quality to predict which routes will be available in the next few minutes and pre-compute routing tables.

Bandwidth allocation: Automatically prioritising traffic based on the current operational phase. During a deliberate attack, fire control data gets maximum priority. During consolidation, logistics reporting is prioritised.

Anomaly detection: Identifying unusual network behaviour that might indicate a cyber intrusion or a jamming attack and automatically implementing countermeasures.

These capabilities are in various stages of research and prototype development. NATO's Allied Command Transformation and the European Defence Agency have both funded AI for network management studies. Production deployment is likely several years away, but the direction is clear: the complexity of future tactical networks will exceed the capacity of human operators to manage them manually, and automation is not optional but necessary.

Tying It Together: From Sensor to Decision

The systems described in this article do not operate in isolation. Consider a concrete scenario to illustrate how they interact.

A German PUMA IFV on a reconnaissance patrol in Lithuania detects a group of vehicles 4 kilometres to the east using its MUSS (Multifunctional Self-Protection System) sensor suite. The crew classifies the targets as enemy armoured vehicles using the PUMA's thermal imager. The onboard BMS computes the target position from the vehicle's GPS coordinates and the turret's bearing and range data, producing an MGRS grid reference.

The BMS formats this as a contact report and transmits it over the SOVERON radio's MANET waveform to the platoon net. Other PUMA vehicles in the platoon receive the track and display it on their own BMS terminals. The platoon leader, seeing the contact on three vehicles' sensors, confirms the report and elevates it to the company headquarters over the same MANET.

At company level, the contact report is correlated with an intelligence report received over the battalion SATCOM link indicating enemy armour moving west in that sector. The company commander requests fire support. The request goes via the battalion BMS (running SitaWare) over a trunk radio link to the artillery battery.

Meanwhile, the contact report has been propagated up to the brigade headquarters, where the COP system fuses it with a Link 16 track from a NATO AWACS that has detected the same vehicle group on its ground moving target indicator radar. The brigade's air liaison officer, seeing the correlated track on the COP, coordinates with an Italian Eurofighter Typhoon flight that has just checked in on the Link 16 net. The Typhoon flight receives the target coordinates as a J3.0 reference point via Link 16.

The entire sequence, from initial detection to fire mission coordination, has taken approximately 90 seconds. Without digital networking, the same sequence would involve voice radio calls at each echelon, manual plotting of grid references on paper maps, voice relay of coordinates, and manual re-entry into fire control systems. That analog process takes 15 to 30 minutes and is far more error-prone.

That compression of the sensor-to-shooter timeline, from tens of minutes to tens of seconds, is the operational payoff of battlefield networking. Every component described in this article, Link 16, MANET radios, BMS software, blue force tracking, SATCOM, the common operating picture, exists to make that compression possible. The engineering is formidable. The systems are imperfect, vulnerable to jamming, constrained by bandwidth, and dependent on planning that does not always survive contact with the adversary. But the alternative, fighting without a digital network, is no longer viable against any adversary with modern capabilities. The network is as critical to a modern military formation as its ammunition supply, and considerably harder to engineer.