Preserve a Binary Message

Binary messages encode information as bytes. A track’s known identity and position give [R]DP clients enough information to put a minimal WDM Object on a map, while consumers retain access to the original message. A second example maps a binary tasking message to an Action.

The source metadata labels this sample Link-16. The six placeholder bytes illustrate storage; the examples' track and task fields are supplied separately.

Source data

The capture system supplies original bytes and metadata. captureAuthority and captureId identify one captured message. capturedAt records the source capture time; receivedAt records when the mapping received or copied it. The format is reported as Link-16, with its profile and message subtype unspecified.

{
  "captureAuthority": "demo.example",
  "captureId": "capture-001",
  "sourceFormat": "Link-16",
  "sourceProfile": "unspecified",
  "messageSubtype": "unspecified",
  "capturedAt": "2026-10-01T12:00:00Z",
  "receivedAt": "2026-10-01T12:00:02Z",
  "mediaType": "application/octet-stream",
  "isSimulated": true
}

The bytes in hexadecimal, which represents each byte as two digits:

00 01 02 7f 80 ff

The binary-source.bin file contains these six bytes.

Pack the bytes

google.protobuf.BytesValue wraps the original bytes in a protobuf message, which an Any container can carry in externalRefs. Both typeUrl and payload.@type identify that wrapper, allowing consumers to unpack it. In ProtoJSON, protobuf’s JSON representation, the bytes appear as base64 text. See Preserve Source Data for packing code and these formats.

details enriches both the Object and Action with readable capture metadata alongside the raw bytes in externalRefs. The agreed com.example.mapping.v1.BinaryCaptureMetadata structure lets an Object stream filter select tracks by details.value.sourceFormat without decoding the message. Its byte length and SHA-256 digest, a value calculated from the contents, let consumers check that the message is intact. See Modeling with WDM for the custom-field convention.

WDM track Object

Position places the track on a map; affiliation marks it friendly. symbology.sidc, the Symbol Identification Code, identifies the military marker to draw, and symbology.version identifies the standard that defines it. These known fields make the Object useful before a fuller mapping is available.

The example supplies track key demo.example:track-9, position (38, -77) in WGS-84 (the geographic reference used by GPS), a friendly MIL-STD-2525C symbol, and observation time 2026-10-01T12:00:00Z separately from the placeholder bytes:

{
  "id": "binary-track:demo.example:track-9",
  "security": {
    "raw": "UNCLASSIFIED",
    "components": {
      "classification": "UNCLASSIFIED",
      "ownerProducer": [
        "USA"
      ]
    }
  },
  "name": "Track 9",
  "identities": [
    {
      "system": "demo.example",
      "identifier": "track-9"
    }
  ],
  "flags": {
    "isSimulated": true
  },
  "status": "OBJECT_STATUS_ACTIVE",
  "ttl": "2026-10-01T12:01:00Z",
  "location": {
    "position": {
      "latitudeDegrees": 38.0,
      "longitudeDegrees": -77.0
    }
  },
  "assessment": {
    "affiliation": "AFFILIATION_FRIEND"
  },
  "symbology": {
    "sidc": "SFGPUCI----K---",
    "version": "SIDC_VERSION_2525C"
  },
  "details": {
    "@type": "com.example.mapping.v1.BinaryCaptureMetadata",
    "value": {
      "captureAuthority": "demo.example",
      "sourceFormat": "Link-16",
      "sourceProfile": "unspecified",
      "messageSubtype": "unspecified",
      "mediaType": "application/octet-stream",
      "representation": "original_bytes",
      "originalByteLength": 6,
      "sha256": "da2cb6ad175bc966de5e79c6e16777f8a98b610c2424a894132df2815be50677",
      "isSimulated": true
    }
  },
  "externalRefs": [
    {
      "typeUrl": "type.googleapis.com/google.protobuf.BytesValue",
      "externalId": "capture-001",
      "sourceSystem": "demo-link16-capture",
      "payload": {
        "@type": "type.googleapis.com/google.protobuf.BytesValue",
        "value": "AAECf4D/"
      },
      "capturedAt": "2026-10-01T12:00:02Z",
      "label": "Original message bytes"
    }
  ],
  "provenance": {
    "id": "track:demo.example:track-9:observation-001",
    "name": "Demo tactical track source",
    "updatedAt": "2026-10-01T12:00:00Z",
    "producer": "example-binary-track-adapter-v1"
  }
}

The Object ID follows the track across captures. Provenance records the observation’s source and time; its expiry timestamp, ttl, is 60 seconds after that observation. externalRefs keeps the complete binary message for consumers that need its full contents.

See Publish Object for how to send this record.

WDM task Action

For a binary movement instruction, an Action describes the task to move Track 9 to Checkpoint Bravo. scope and type classify the task, and objectLinks identifies the unit performing it. externalRefs preserves the original tasking message for consumers that need its full contents.

The task key demo.example:move-001, instruction, and source update time 2026-10-01T12:00:00Z are supplied separately from the placeholder bytes.

{
  "id": "task:demo.example:move-001",
  "security": {
    "raw": "UNCLASSIFIED",
    "components": {
      "classification": "UNCLASSIFIED",
      "ownerProducer": [
        "USA"
      ]
    }
  },
  "name": "Move to Checkpoint Bravo",
  "description": "Move Track 9 to Checkpoint Bravo.",
  "type": "movement",
  "scope": "ACTION_SCOPE_TASK",
  "state": "ACTION_STATE_DRAFT",
  "objectLinks": [
    {
      "objectId": "binary-track:demo.example:track-9",
      "type": "OBJECT_LINK_TYPE_ASSET"
    }
  ],
  "details": {
    "@type": "com.example.mapping.v1.BinaryCaptureMetadata",
    "value": {
      "captureAuthority": "demo.example",
      "sourceFormat": "Link-16",
      "sourceProfile": "unspecified",
      "messageSubtype": "unspecified",
      "mediaType": "application/octet-stream",
      "representation": "original_bytes",
      "originalByteLength": 6,
      "sha256": "da2cb6ad175bc966de5e79c6e16777f8a98b610c2424a894132df2815be50677",
      "isSimulated": true
    }
  },
  "externalRefs": [
    {
      "typeUrl": "type.googleapis.com/google.protobuf.BytesValue",
      "externalId": "capture-001",
      "sourceSystem": "demo-link16-capture",
      "payload": {
        "@type": "type.googleapis.com/google.protobuf.BytesValue",
        "value": "AAECf4D/"
      },
      "capturedAt": "2026-10-01T12:00:02Z",
      "label": "Original message bytes"
    }
  ],
  "provenance": {
    "id": "task:demo.example:move-001",
    "name": "Demo tasking source",
    "updatedAt": "2026-10-01T12:00:00Z",
    "producer": "example-binary-task-adapter-v1"
  }
}

See Create Action for how to send this record.

Store large messages outside WDM

An attachment points to a file stored separately, keeping large messages out of the WDM record. This example uses ATTACHMENT_KIND_MESSAGE for a tactical message. Its uri gives the storage address:

{
  "uri": "s3://example-source-captures/demo.example/capture-001.bin",
  "kind": "ATTACHMENT_KIND_MESSAGE",
  "contentType": "application/octet-stream",
  "capturedAt": "2026-10-01T12:00:00Z",
  "caption": "Message capture-001",
  "sizeBytes": "6",
  "contentDigest": "sha256:da2cb6ad175bc966de5e79c6e16777f8a98b610c2424a894132df2815be50677"
}

The attachment replaces the copy in externalRefs.payload, while source identifiers and capture metadata stay with the record. Size and digest let consumers check the retrieved file; the storage address needs to remain accessible for as long as they use the reference.