Skip to main content

👮🏻‍♀️ MISB ST 0902 General Info

Overview​

MISB ST 0902 defines the Motion Imagery Mission Management Set (MISMMS), a profile-oriented metadata set used to report mission-summary information over time. Motion Imagery Sensor Minimum Metadata Set (MISMMS) is defined as a Local Set profile of MISB ST 0601, specifically designed to enable the threshold capabilities of Situational Awareness (SA), Discovery & Retrieval (D&R), and Cross-Domain Dissemination

Purpose​

The MISMMS rule ensures that Motion Imagery systems provide a consistent, minimum set of source-derived metadata to support ISR mission accomplishment . By standardizing these fields, the rule facilitates the transition from analog to all-digital architectures and ensures that users can effectively search archives and maintain situational awareness regardless of the platform

MISB ST 0902

In ST Inspector, MISB ST 0902 coverage is represented by the MISMMS rule family. Those rules evaluate both per-packet content and stream-level behavior, including required item presence, reporting continuity, and cross-layer relationships for embedded VMTI carriage.

What ST Inspector Checks​

The MISB ST 0902 rules currently cover:

  • overall MISMMS rule compliance checks
  • required top-level item presence across the stream
  • inclusive-OR and exclusive-OR profile requirements
  • motion-imagery core identifier presence
  • per-packet ST 0601 identity and core-item integrity
  • top-level field length and type conformance
  • zero-length-item handling
  • 30-second reporting continuity requirements
  • Tag 2 monotonicity and advisory cadence checks
  • parent metadata preservation when embedded VMTI is present

Typical Failure Themes​

Common MISB ST 0902 findings include:

  • required MISMMS items missing from the stream
  • metadata groups that never satisfy an inclusive-OR requirement
  • mutually exclusive items reported together in one packet
  • invalid top-level field length or type
  • zero-length items used where they should not count toward compliance
  • required items not being refreshed often enough over time
  • non-monotonic Tag 2 timestamps in claimed MISMMS packets
  • missing parent ST 0601 context when embedded VMTI is present

Rule Details​

The MISMMS profile mandates the use of a specific Universal Label and requires that a defined set of metadata items be present and refreshed regularly

Universal Label: Every MISMMS packet must use the 16-byte MISB ST 0601 Universal Label: 06.0E.2B.34.02.0B.01.01.0E.01.03.01.01.00.00.00

Mandatory Items: All items identified in the MISMMS summary table (Table 1) are mandatory unless they are explicitly marked as conditionally dependent

Update Frequency: While individual items may update at different rates (e.g., "Fast" for dynamic data like orientation or 10 seconds for constant data like Mission ID), the standard mandates that every item in the MISMMS must be reported at least once every thirty (30) seconds

Validation Criteria​

To be considered MISMMS-compliant, a KLV stream must satisfy the following technical requirements:

Expression (ST 0902.3-01): All metadata must be expressed according to the guidelines in MISB ST 0107

Encoding (ST 0902.3-03): All items must be populated and encoded in accordance with the data types and lengths defined in MISB ST 0601

Continuity (ST 0902.3-04): No metadata item within the MISMMS can go unreported for longer than 30 seconds

Zero-Length Items (ST 0902.8-05): Zero-Length Items (ZLI) cannot be used to satisfy the minimum reporting requirements

Logical Metadata Rules:

Inclusive OR: The system must provide at least one item from specific coordinate/altitude groups (e.g., Tag 15, Tag 75, or Tag 104 for sensor height)

Exclusive OR: Tag 75 (Sensor Ellipsoid Height) and Tag 104 (Sensor Ellipsoid Height Extended) are mutually exclusive and shall not both be present in the same packet

System Identification: A Motion Imagery Core Identifier (Tag 94) is mandatory whenever data is disseminated from the system

Failure Modes​

A validation failure occurs if any of the following are detected: Missing Core Identifiers: The packet lacks Tag 94, which is essential for enterprise management of Motion Imagery data . Frequency Violations: Any required item (such as Platform Designation or Sensor Latitude) is missing from the stream for a period exceeding 30 seconds . Invalid Packet Construction: The packet does not begin with the correct 16-byte Universal Label or ends with an incorrect 16-bit Checksum (Tag 1) . Prohibited ZLI usage: A ZLI is used for a mandatory field in an attempt to meet the 30-second reporting requirement

Example​

The following hex string represents a compliant "Dynamic Only" MISMMS packet, which is typically sent at higher rates to conserve bandwidth while still meeting frequency mandates

06 0E 2B 34 02 0B 01 01 0E 01 03 01 01 00 00 00 // Universal Label
61                                              // BER Short Form Length (97 bytes)
02 08 00 04 60 50 58 4E 01 80                   // Tag 2: Precision Time Stamp
05 02 71 C2                                     // Tag 5: Platform Heading Angle
06 02 FD 3D                                     // Tag 6: Platform Pitch Angle (Short)
07 02 08 B8                                     // Tag 7: Platform Roll Angle (Short)
0D 04 55 95 B6 6D                               // Tag 13: Sensor Latitude
0E 04 5B 53 60 C4                               // Tag 14: Sensor Longitude
0F 02 C2 21                                     // Tag 15: Sensor True Altitude (MSL)
... [Remaining Dynamic Tags] ...
41 01 06                                        // Tag 65: UAS LS Version
01 02 5C 2B                                     // Tag 1: Checksum
[Example encoded per Annex C of the standard]

For more information, see the main Validation Rules section.