8.3 OGC GMTI Information Model
GMTIF uses a packet oriented encoding model. A packet header is sent at the beginning of each packet to identify “the format version of the data contained in the
packet, the size of the packet, and information pertaining to the platform, security, and the mission.”
8.3.1 GMTI Segments
STANAG 4607 v3 defines ten message segments to encode GMTI data all used in this report, two message segments for interactive communication ignored in this
report, as interactive communication was not addressed, and a number of placeholders, which are not further defined yet. Figure 18 provides an overview of all
segments. Green segments have been used in this report, red ones ignored, and grey ones represent placeholders in the current specification.
Figure 18: GMTI segments overview
According to STANAG 4607v3, the individual segments are defined as follows: The Mission Segment provides information concerning the mission plan, the
flight plan, the platform type and configuration, and the reference time for the mission.
The Dwell Segment is sent for each dwell of the radar beam. It provides information related to dwells and revisits, the sensor location, the coverage
area, the time of the dwell, sensor orientation, and sensor parameters. It
includes Target Reports for any GMTI detections observed within that dwell and shall be sent even if no targets are detected.
The High Range Resolution HRR Segment provides data on HRR and Range-Doppler measurements, which may be performed in conjunction with
MTI detections. It includes HRR Scatterer Data pertaining to the HRR measurements.
The Job Definition Segment provides a definition of the radar job performed by the sensor, including information pertaining to the geolocation model used
in the sensor measurement. The Free Text Segment provides a means of sending alphanumeric text messages. The Test and Status Segment provides a
means of exchanging health and status information of the platform systems.
The Processing History Segment provides a means of annotating the radar data to show its history as it is processed through various systems during
transmission.
The Platform Location Segment provides the means for the platform to transmit its location during periods when it is not collecting data.
The Job Request and Job Acknowledge Segments are recommendations only and are not required for this format. The Job Request Segment provides a
recommended format for requesting service from the sensor platform. The Job Acknowledge Segment provides a recommended format for acknowledging a
sensor service request by a sensor platform, defining the job to be performed by the sensor, and notifying the requesting operator whether the task can be
accomplished or not during the mission.
The Group, Attached, LRI, and System-Specific Segments are undefined at this time and left for future definition.
8.3.2 GMTI Exploitation Classes
As there is no “predefined order or sequence other than the requirement to preface data segments with appropriate header segments”, raw GMTIF can hardly get
directly converted into a hierarchical UMLXML model compliant to the OGC feature model approach. Instead, the GMTI data needs to get structured and organized to
prepare it for further efficient processing. In this regard, we follow the recommendations provided in the STANAG 4607 implementation guide, which
defines three exploitation classes:
Situation Awareness SA: The minimum data required for Moving Target
Indicator MTI target display.
Targeting and Tracking TT: The minimum data required for targeting and
tracking of MTI targets using current or advanced automatic tracking algorithms or precision location systems such as the Global Positioning
System GPS.
Targeting and Tracking with High Range Resolution HT: The minimum
data required for targeting and tracking of MTI targets using current or
Kategori