SIGNALBOX

SignalBox / STANAG 4609 and KLV

STANAG 4609 and KLV metadata explained

STANAG 4609 is how NATO forces exchange full-motion video from drones, aircraft and ISR sensors. What makes it different from ordinary video is the KLV metadata that travels with every frame: where the platform is, where the sensor points and exactly when the image was taken. This page explains how that works and what it takes to route these feeds without losing the metadata.

What is STANAG 4609?

STANAG 4609 is the NATO Standardization Agreement for digital motion imagery. It makes sure that video from one nation's drone or reconnaissance aircraft can be received, viewed and exploited by the systems of another. Its implementation guide is published as AEDP-8.

Rather than inventing everything itself, STANAG 4609 builds on existing standards. Video is compressed with common codecs such as H.264 or H.265, packed into an MPEG-2 transport stream, and enriched with metadata defined by the Motion Imagery Standards Board (MISB). The result is a feed any compliant system can play, while specialised exploitation software can also read exactly what the sensor was looking at.

You will find STANAG 4609 video coming from:

  • UAS ground control stations for tactical and MALE drones
  • Gimbal cameras and EO/IR sensor turrets on aircraft and helicopters
  • Remote video terminals used by ground troops
  • ISR exploitation, archive and dissemination systems

KLV metadata

KLV stands for Key-Length-Value, a compact binary encoding standardised as SMPTE ST 336. Each piece of metadata is a small packet in three parts:

KEY16-byte universal key: what this is
LENGTHBER-encoded size
VALUEthe data itself, e.g. a local set of tagged fields
One KLV packet. A receiver that does not recognise the key can skip it using the length.

Because every packet carries its own length, a receiver can skip what it does not understand and still read the rest. To save bandwidth, MISB metadata usually uses a local set: one universal key for the whole packet, followed by short numbered tags for the individual fields.

MISB ST 0601: the drone metadata set

The most widely used local set is MISB ST 0601, the UAS Datalink Local Set. It describes the platform, the sensor and the scene for each moment of video. A few of its fields:

FieldWhat it tells you
Precision Time StampThe exact time the data applies to, in microseconds. Used to line metadata up with video frames.
Platform heading, pitch, rollThe attitude of the drone or aircraft.
Sensor latitude / longitude / altitudeWhere the sensor is.
Sensor field of viewHow wide the camera is zoomed.
Slant rangeDistance from sensor to the point it is looking at.
Frame center lat / lonThe ground position in the middle of the image.
ChecksumLets a receiver detect corrupted packets.

Other MISB sets often appear next to ST 0601, such as ST 0102 for security classification markings and ST 0903 for moving target indicators (VMTI). With this data, a viewer can put the drone and its footprint on a map, measure positions in the image and search archives by place and time.

How a STANAG 4609 stream is built

A STANAG 4609 feed is normally an MPEG-2 transport stream with at least two elementary streams: compressed video and KLV metadata. Both carry timestamps, so a receiver can match each metadata packet to the right frame.

Video (H.264 / H.265)
KLV (ST 0601)
Video and KLV as separate tracks in one transport stream, kept in step by timestamps.

Metadata can be carried synchronously, with each packet tied to a specific video timestamp, or asynchronously, as a separate data track that relies on the Precision Time Stamp inside the KLV. Feeds are commonly sent over UDP, often multicast, on tactical networks, and increasingly over SRT or RTSP when they cross less reliable links.

Routing drone feeds without losing KLV

The video in a STANAG 4609 feed is ordinary enough that almost any tool will play it. That is exactly the trap. Many streaming servers, transcoders and web players only look at the audio and video tracks. When they repackage or convert a feed, the metadata track is dropped or its timing breaks. The picture still plays, but the position and sensor data that make it useful are gone, often without anyone noticing.

When you route drone and ISR feeds in an operations centre, check that:

  • the KLV track survives every hop, not just the first one
  • metadata stays in step with the video after routing and distribution
  • exploitation tools downstream still receive the original metadata
  • operators can still watch the same feed on an ordinary screen or in a browser

STANAG 4609 in SignalBox

SignalBox is a control room for live video. It takes in drone and ISR feeds alongside cameras, encoders and streaming apps, and patches any source to any destination in a visual routing matrix. For STANAG 4609 feeds, the KLV metadata stays with the picture through routing and distribution, so position, sensor and timing data arrive at every destination alongside the video.

Licensed MISB modules go further: SignalBox decodes ST 0601 telemetry into a HUD over the video, draws ST 0903 moving-target boxes and shows ST 0102 classification markings as a banner. See all modules.

Questions

What is the difference between STANAG 4609 and MISB?

STANAG 4609 is the NATO agreement that sets the standard for digital motion imagery. The technical detail it relies on, such as the KLV metadata sets, comes largely from standards published by the Motion Imagery Standards Board (MISB). STANAG 4609 tells you which of those standards to use; MISB documents such as ST 0601 tell you exactly how.

What is KLV metadata?

KLV stands for Key-Length-Value, a binary encoding defined in SMPTE ST 336. Each item starts with a key that says what it is, then a length, then the value itself. In drone video, KLV carries data such as platform position, sensor pointing angles, field of view and a precise timestamp for each moment of video.

What is MISB ST 0601?

MISB ST 0601, the UAS Datalink Local Set, is the most widely used KLV metadata set for drone video. It defines numbered tags for values such as sensor latitude and longitude, platform heading, sensor field of view, frame center coordinates and a precision timestamp.

Why does KLV metadata get lost?

Many video tools only look at the audio and video tracks. When they transcode, repackage or convert a feed to a web format, they drop the metadata track or break its timing. The video still plays, but the position and sensor data that make it useful for analysis are gone.

Can SignalBox route STANAG 4609 feeds without losing KLV?

Yes. SignalBox keeps the KLV metadata with the video when a STANAG 4609 feed is routed and distributed, so position, sensor and timing data arrive at every destination alongside the picture.