Key Length Value (Klv) Metadata; Inserting Klv Metadata; Exploitation Support Data (Esd) To Local Data Set (Lds) - VBrick 9000 Admin Manual

Key Length Value (KLV) Metadata

Inserting KLV Metadata

VBrick supports Key Length Value (KLV) and Local Data Sets (LDS) metadata insertion in
accordance with Motion Imagery Standards Board (MISB) standards. KLV is a data encoding
standard often used to embed information in video feeds. Items are encoded into key-length-
value triplets where key identifies the data, length specifies the data's length, and value is the
data itself. In a typical KLV/LDS application, GPS (global positioning) or telemetry data is
embedded in the video using one of the following supported methods:
Table 1. KLV Methods
KLV Method
ESD to LDS
LDS Passthrough
CoT to LDS
In all cases, the encoded video has embedded metadata—typically including the time and
geographic location of the video stream. In all cases, the VBrick encoder remaps the
metadata into KLV/LDS per MISB 601.3. This metadata can only be embedded in an
MPEG2TS transport stream as defined on the Encoder Configuration > Streams page.
Note: KLV metadata is supported on the serial port(s) and on the network port. If you
are using the serial ports on a device with multiple channels, only the first two channels
support KLV metadata in the stream: Channel 1 uses COM2 and Channel 2 uses
COM1. If you are receiving KLV or CoT into the encoding encoder, there is a
maximum of one network KLV stream per video input.

Exploitation Support Data (ESD) to Local Data Set (LDS)

Exploitation Support Data (ESD) to Local Data Set (LDS) uses line 21 (typically used for
closed captions) of the video format as an in-band transport mechanism. The embedded text
is limited to 120 characters per frame. Control and management of the LDS insertion
parameters are available using the VBAdmin Web interface, the Command Line Interface, or
VBrick 9000 Encoder Admin Guide
Description
Exploitation Support Data (ESD) is accepted via CC, converted to
LDS packets and transported over Transport Stream as a Metadata
AU.
LDS is accepted through the following interfaces and transported in
the Transport Stream as a Metadata AU.
• LDS over Serial port
• LDS over SDI interface
• LDS over IP network
Cursor on Target (CoT) converted to LDS and transported over
Transport Stream as a Metadata AU. CoT is accepted over the
following interfaces:
• CoT over Serial port
• CoT over IP network
Chapter 9
169