Metadata Preprocessing.

If your source stream already contains Klv information, there are 3 processing options you can select from:

Drop Existing Klv - the source's Klv PID will be removed from the output.
Keep Existing Klv - the source's Klv PID will be passed though (as is) to the output.
Restamp Existing Klv - the source's Klv packets timestamp (Tag 2) may be re-stamped with either current time or predefined initial time.
Merge Existing Klv - the source's Klv data will be merged with the default packet.

You can Add / Replace selected metadata fields by using a Template packet. With a Template packet defined, and Add/Replace option selected, a KlvInjector will add the metadata information to every injected packet. If a corresponding field is present in the incoming metadata, it will be replaced with the one defined in the Template packet.

Figure 1. Preprocessing parameters configuration.

A Template packet is either a regular KLV encoded packet (in binary format) or json file that resembles MISB601 hierarchy. A Timestamp field is ignored, so it may be omitted from the packet (or have any value, which is ignored).

Here is an example of a template Metadata Packet.

Figure 2. Template Metadata Packet.

It represents the following information:

Figure 3. Decoded Template metadata Packet.

Note: You can use a Composer option of the 3 application to generate a template metadata packet.

Figure 4. Using KlvComposer for Template Metadata Packet generation.

Default Packet Insertion.

It is possible to define a minimal time interval required for packet insertion. If no data has arrived within the defined period, a default packet (with a proper timestamp) will be generated and inserted.

Figure 1. Defining Min Time interval.

Note: If a Min Interval is selected with a combination of Add/Replace and/or Remove packets, the inserted packet will be preprocessed as described in Metadata Preprocessing..