Why HF radios are mission-critical: NATO standards for military comms

For beyond line of sight (BLOS) communication, SATCOM has increasingly become the technology of choice within the defence industry due to its high speed and reliability. However, satellite communication is vulnerable to attack in a warfare situation. In fact, the UK’s National Cyber Security Centre (NCSC) recently confirmed that Russia was behind a cyber-attack targeting commercial satellites in Ukraine, causing thousands of outages and permanently damaging terminals.

Unlike SATCOM, high-frequency (HF) radios require minimal infrastructure as they utilise the ionosphere for radio wave transmission. All that is required are the interface/receiver components, antenna, and power source. HF radio services are not vulnerable to operation-denial attacks, so should be considered mission-critical as a backup system when SATCOM is not available.

NATO specifications for HF communication

NATO’s current standardised agreement for HF radio data communication, STANAG 5066, provides peer protocols that operate above an HF modem and below the application level. The standard includes the compulsory Subnet Interface Service (SIS) protocol, which enables an application to connect to an HF Modem through a STANAG 5066 server over TCP/IP. It also defines the CAS and DTS layers, including automatic repeat query (ARQ) methods for data transmission.

Isode’s HF Vision, Strategy & Road Map

  • Broadcast and Ship to Shore (BRASS) services using the ACP 127 protocol, which utilises a continuous HF broadcast.
  • Link-11 is a Command and Control (C2) protocol which can be used over HF and other links to support tactical communication using standardised short messages. Link-22 provides an update to Link-11 operation over HF.
  • Compressed File Transfer Protocol (CFTP)/Battle Force Email (BFEM).

Improvements in HF technology such as STANAG 4539 (for high-speed data transmission), automatic link establishment (ALE), wideband HP, and multi-node HF networks, has led to NATO introducing updated requirements. BRE1TA, followed by the anticipated BRE2TA, intend to keep the BRASS programme moving forward in tandem with HF technology advancements. The BRASS IP Enhanced System (BRIPES) project extends on BRE1TA with CSMA and WTRP, as well as XMPP services.

HF system solutions

Isode is a provider of mission-critical software for the defence and aerospace industries, with product categories including Military Messaging, XMPP Chat, Directory services, and HF radio.

When an HF solution is deployed, Isode’s partner companies provide the interface components and underlying communications infrastructure, while Isode provides the software needed above this.

Icon-5066 is Isode’s modem-independent STANAG 5066 server. Icon-5066 will connect to one or two HF modems, providing a single interface to an HF network that can be shared by multiple applications. It can be deployed in conjunction with an HF network and two peers in compliance with STANAG 5066.

In keeping with NATO initiatives to keep up to date with HF technology advancements, Icon-5066 provides 2G, 3G and 4G ALE support. When it comes to wideband HF, Icon-5066 also provides support for operations using STANAG 5069 contiguous waveform up to 240 kbps. The server also supports the Carrier Sense Multiple Access (CSMA)/Annex K approaches for sharing a single-channel operation, which is ideal for channels shared by a large number of nodes for ARQ protocols.

Isode’s Icon-PEP enables IP applications to be deployed over an HF network using the STANAG 5066 link layer as the interface. It enables generic switching of IP packets, so it can function as an IP subnet and optimise support for TCP over IP using a Performance Enhancing Proxy (PEP).

Isode’s web-based server, Red/Black, enables users to control and monitor different devices and servers. It is specifically designed to support HF radio systems and to display and manage communication chains. These servers can be used on their own or as a pair across a secure boundary, such as Isode’s M-Guard, which controls the flow of status and control messages across the boundary.