Title
Land Tactical C2 Information Exchange Profile
Description
The Land Tactical C2 Information Exchange Profile provides standards and guidance with regard to a core set of Command and Control information and also on how to exchange XML messages within a coalition tactical environment with mobile units.

Reference document

Org
FMN
Pubnum
Date
2021-10-22
Version
Title
FMN Spiral 4 Specification

Taxonomy

Standards

Obligation: MANDATORY, Lifecycle: CURRENT

AEP-76 is to be used for direct C2 Data Exchange between coalition units at the Mobile Tactical Edge, where a shared interoperability network is in place built upon the loaned radio concept. The data model of AEP-76 is based on variant of MIP 3.1 XML messages. The following 8 messages of the messages defined in Volume II are mandatory for federating JDSS in coalition operations Presence MessageIdentification MessageContact /Sighting MessageSketch MessageGenInfo MessageReceipt MessageOverlay MessageCasualty Evacuation Request Message (Request Message Body only)

Obligation: MANDATORY, Lifecycle: CURRENT

Obligation: MANDATORY, Lifecycle: CURRENT

Obligation: MANDATORY, Lifecycle: CURRENT

Guidance

Developers may useAEP-76 Ed A V2 XML Schema Definitionsfor implementing JDSS.

See SIP for Loaned Radio Connector for an interim replacement of the cancelled standard AEP-86 (STANAG 4619).

AEP-76 is to be used for direct C2 Data Exchange between coalition units at the Mobile Tactical Edge, where a shared interoperability network is in place built upon the loaned radio concept. The information exchange mechanism of AEP-76 supports the efficient information exchange of XML messages over a coalition mobile tactical edge network.

The following two JDSS messages are out-scoped for FMN Spiral 4

  • Coordination message. STANAG 4677 provides the Overlay message that is a superset of functionality that is provided by the coordination message and can be used instead..
  • NBC message. STANAG 4677 provides the Overlay message that is a superset of functionality that is provided by the coordination message and can be used instead.

For the Casualty Evacuation message, the Reply Message Body is out-scoped. Instead of the dedicated reply message body, the Geninfo message can be used to coordinate casualty evacuations after the initial dedicated CasEvac request message.

Status

URI

History

Flag Date RFC Version
added 2022-12-23 14-059 15
UUID
570aeac2-6cef-47f1-ac72-cbf24cf385f0

Utilization

This profile is used by the following profiles: