AFRL,
Alburqueque NM: Researchers are investigating future concepts for network-centric command and control operations using intelligent, autonomous data link management to pass real-time information over ad hoc networks.
As the Air Force (AF) slowly integrates data links into the operational fleet and manufacturers investigate newer, highcapacity data links, researchers must work to develop advanced methods of data link operation. This article describes an approach that employs autonomous data link management and ad hoc networks to conduct networkcentric warfare against dynamic targets.
The approach will support two future adjunct programs by cooperatively using information gathered by all participating platforms in the battlespace to help dissipate the fog of war.
As more aircraft and weapons become equipped with existing data links (e.g., Joint Tactical Information Distribution System Link-16) and future high-capacity data links (e.g., Wideband Data Link), researchers are creating ad hoc networks that support machine-to-machine (M2M) operations, which provide a more effective capability to find, fix, track, target, and engage dynamic targets.
AFRL researchers propose the use of autonomous software data link controllers to manage operations selfsynchronization using real-time information at and around the target scene. Such operations would include (1) positive identification; (2) determination of which in-theater asset has the better weapon, sensor, or fuel status to perform the mission; (3) resolution of legal issues and rules of engagement; (4) correlation with no-hit lists; (5) compliance with restricted operation zones; (6) assessment of collateral damage; (7) route deconfliction; and (8) estimates of threat severity. Collaborative M2M messaging among the command and control (C2) and strike aircraft, ground air operations center (AOC), control and reporting centers (CRC), and wing operations centers (WOC) can quickly produce the legal command to attack the time-critical target (TCT). Operators could also use the ad hoc networks to coordinate support packages, such as those involving tankers, jammers, search and rescue, or escort aircraft.
To accomplish this M2M capability, all potential system nodes must have a software management layer (autonomous data link controllers) established over the radio link to interpret all received action requests. This layer interfaces with the sensor and display managers to communicate with operational flight program services and databases, as well as pilots, when necessary.
The ground node of this 'system of systems' integrates M2M with automatic AOC dynamic targeting processes. The autonomous data link management software layer acts as an additional remote entry into the aircraft sensor management system. A data link request may involve temporarily pointing a sensor to a particular location and returning the processed result or sharing a previously saved track file from the requested location.
Researchers must establish a common architecture and transport protocol along with the data link message dictionary to find correct nodes and respond accordingly to information requests. This message ontology is the next generation to the Tactical Digital Information Link-J messages defined in the 1980s for a lesser functionality. Laboratory researchers named this additional software component for managing data links the 'Embedded Attack Commander' (EAC) (see Figure 1).
The intent is for EAC to communicate using M2M exchanges with the AOC and its connected systems, airborne manned platforms in theater, and unmanned aircraft and weapons. The AF is already automating AOCs through the TCT Dynamic Decision Enabler program, and researchers could test a first spiral of EAC using limited Link-16 messages in the near future. A more robust system that uses the Multiplatform Common Data Link, or other communication links, could expand information formats to include map clips, graphics, or even real-time video streaming.
When this robust EAC capability becomes available, it could have two additional roles, the first of which pertains to the Multiship/Sensor Information Manager (MSIM) concept (see Figure 2). MSIM represents a generalized system integration of concepts researched in the platformtailored designs of the Affordable Moving Surface Target Engagement and Multiplatform Targeting Experiment programs, both of which share targeting information across multiple platforms.
The MSIM collaborative decision aid facilitates first-pass TCT kill by reducing target location error, or by supplying additional sensor information to make a positive identification or supplement a future automatic target recognizer. A strike platform with incomplete data could request other assets in the area to contribute their sensor information for the location in question.
Unless a pilot turns a sensor to private, MSIM could share its information autonomously, a pilot's sensors would time-share momentarily to scan the requested area and reply to the requester with their assessments. The data fusion occurs at the AOC/CRC/WOC, C2 aircraft, or requesting platform. This requires that all aircraft are cognizant of the full air tasking order (ATO) and are monitoring the position and status of all nearby platforms within sensor range.
A second potential role of the EAC intelligent communication capability pertains to performing a continuous, serendipitous, automated intelligence, surveillance, and reconnaissance (ISR) function while the aircraft is flying the ATO-directed mission.
This program, the Onboard Information Collection Broker (OBICB), automatically monitors all sensor events, directs additional sensor coverage of events along its flight path, and immediately sends ISR data to the CRC/AOC for upto- date evaluation (see Figure 3). The pilot reads only the directed functions of those sensors while pursuing the specific ATO mission, but OBICB unobtrusively collects all suspicious sensor data along the route. The system may temporarily store information until a safe transmit time occurs in the mission and data links are available.
Nevertheless, OBICB returns ISR information to the AOC within minutes or seconds, and with much greater accuracy than a pilot debrief occurring hours later and based upon notebook entries and memory. The ground receiver time-tags and position-logs the ISR data. The pilot may restrict or deny OBICB operation, but when almost every flying asset is an ISR source over the battlefield, the ISR tasking operation at the AOC may be drastically reduced and the freshness of the data greatly improved.
The EAC, along with MSIM and OBICB adjunct programs, depends on a much more highly automated kill-chain process and command, control, computers, and communications operations than are available today. The design of the concept, scalable architecture, and extendable intelligent messaging protocol on top of existing data link formats and currently envisioned Joint Battlespace Infosphere will be an enormous challenge. The resulting capabilities, however, will be significant for the warfighter combating time-critical, dynamic targets.
