Unmanned Aircraft Systems Roadmap 2005-2030 - Federation of ...
Unmanned Aircraft Systems Roadmap 2005-2030 - Federation of ... Unmanned Aircraft Systems Roadmap 2005-2030 - Federation of ...
UAS ROADMAP 2005 APPENDIX C: COMMUNICATIONS INTRODUCTION This appendix guides industry and the Services on an UA communications migration path toward improved interoperability. Service acquisition functions include requirements offices, program offices, acquisition managers, program managers, and research and development programs. Service operators include operational units, and demonstration activities. Industry includes developers, manufacturers, and professional standards groups. This appendix provides a reference to existing and binding policy and standards. It also provides time frames for implementation of various capabilities. Overview The information environment has changed fundamentally over the last 10 years. More importantly it will continue to change. The Services, in partnership with industry, must develop and field interoperable UA systems that can adapt to the evolving information environment. The challenge remains to link disparate systems, effective in their own right, but evolving separately over time, to form a cohesive collaborative information environment. To this end, DoD has invested in its own version of the internet, the GIG. The GIG, defined as virtually all DoD information technology infrastructure, exists to provide the timely and accurate information that war fighters need to assure victory. All DoD Systems shall be able to interact with the GIG. New UA systems shall be developed to comply with the GIG architecture from the outset. At a minimum, web enabled interfaces for legacy UAV systems would need to be created for the system to be recognized as an entity on the GIG. By connecting to the network, UAS become part of that network. Everyone on the GIG will become both a producer and a consumer of information. The concept of sensor will extend to virtually every piece of equipment capable of sensing and passing data, from orbiting satellites to an individual soldier’s gun sights. This information must flow seamlessly, with minimal human intervention, to unanticipated users as well as well defined, known users, to support both foreseen and unforeseen information requirements. The two overarching requirements for next generation UA communications are 1) connect to the GIG, and 2) comply with spectrum utilization policy. To connect to the GIG, UA programs must take full advantage of DoD programs and initiatives to achieve net-centricity: net enabled CDL, JTRS, Transformational Satellites (TSAT), High Assurance Internet Protocol Encryption (HAIPE), and the Defense Information Systems Agency (DISA) metadata registry. UA communications must provide secure, reliable access to all UA capabilities across the entire DoD enterprise. Initially, efforts must focus on common interfaces for sensor control and dissemination via the GIG. As new payloads and weapons are introduced, such as communications relay packages, electronic warfare suites, and guided weapons, web enabled interfaces must be developed to allow control and employment from any authorized node. The vision is a ubiquitous network where every entity exists as a node and can share and use any data produced by any other node, anytime. For complete information regarding the GIG, refer to the GIG Architecture and the GIG Enterprise Services website at https://ges.dod.mil/. EXPERIENCE A review of operations in support of recent conflicts serves to illustrate current communications capabilities for two UAS, Global Hawk and Predator. They employed a mix of dedicated point-to-point communications and networked communications. Many of the networked communications were IP based, approaching net-centric capabilities. Examples of network capabilities include posting images to an Image Product Library (IPL), which implements the Task, Post, Process, Use (TPPU) model, and the widespread use of secure internet chat. A cursory review of current methods for radio development and deployment highlights the need for a more flexible, joint approach to procuring interoperable radio systems. APPENDIX C - COMMUNICATIONS Page C-1
UAS ROADMAP 2005 Global Hawk The RQ-4 Global Hawk system consists of the aircraft, Launch and Recovery Element (LRE) and Mission Control Element (MCE). The LRE controls the aircraft via line-of-sight (LOS) CDL, LOS ultra high frequency (UHF), and beyond line-of-sight (BLOS) UHF radios. The LRE has no provision for sensor control or product receipt. The MCE contains all of the aircraft control functions of the LRE. In addition, the MCE provides for sensor control as well as receipt and dissemination of the product. The MCE maintains situational awareness. MCE aircraft command and control is accomplished using narrow band LOS UHF radio and UHF satellite communications (SATCOM), with Inmarsat as a back up command and control link. The LOS CDL as well as Ku-band SATCOM provide command and control channels as well. Sensor data flows from the aircraft to the MCE via either LOS CDL or Ku-band SATCOM. Global Hawk provided extensive mission support during OEF in Afghanistan. The LRE launched the Global Hawk from a forward operating location. Shortly after launch, the LRE transferred mission control to the forward-deployed MCE. During combat operations, Global Hawk initially flew a preplanned mission, but quickly transitioned to an ad-hoc operation. For a more complete understanding of preplanned, replanned, ad hoc and autonomous missions, refer to the section entitled UA Actions. Global Hawk transmitted images to the MCE via commercial Ku-band SATCOM at 20 Mbit/s. The MCE then routed the imagery to the collocated forward exploitation element or to a wide area network (WAN) inject point to access a fiber optic landline to the Continental United States (CONUS) based reach-back facility. The CONUS based exploitation center processed the imagery and forwarded products via Kuband SATCOM at 6-8 Mbit/s to an high-capacity image product library or directly to the CAOC for use in current operations. The Distributed Common Ground System (DCGS) supported the exploitation effort. Operators used the experience gained from Global Hawk activities in OEF to streamline operations during OIF. Again, the LRE launched the aircraft from a forward operating location; however, all operations were performed using reach-back to the MCE located in the CONUS, not forward deployed. Communication between the MCE at Beale AFB, the CAOC, and the aircraft used a combination of WAN landline and commercial Ku-band SATCOM (with transmission rates from 20-40 Mbit/s). Inmarsat was the redundant C2 link. Global Hawk again flew both preplanned and ad hoc missions in theater. It used Ku-band SATCOM for both command and control and imagery dissemination to the CONUS based MCE. WAN landline provided communications between the MCE and the analysts. Analysts searched for ad hoc targets and passed them directly to the CAOC via Ku-band SATCOM. If determined to be time-critical, targets were passed to in-flight fighters/bombers via Link-16 message. Figure C-1 depicts the Global Hawk communications architecture for both deployed and in garrison operational modes. “Secure Chat” via Secret Internet Protocol Router Network (SIPRNET) was established between the Global Hawk pilot/sensor operator, the Global Hawk liaison officer at the CAOC, and the Intelligence Mission Operations Commander at the exploitation center. This provided situational awareness and enabled command of the mission in response to ongoing operations and other emerging requirements. Predator The Predator system consists of the aircraft, a Ground Control Station (GCS), and a Launch and Recovery Element (LRE). The GCS consists of flight control equipment, sensor control equipment, LOS data link, VHF/UHF radio and Ku SATCOM data link. The LRE contains a subset of the GCS equipment, the minimum required for launch and recovery. Predator pilots manipulate aircraft flight controls in real time using the LOS data link to accomplish takeoffs and landings. Once airborne, the pilot couples the autopilot to the navigation system, and the aircraft navigates to selected waypoints. The Predator LRE has no BLOS communications, so it must maintain LOS until it transfers control to the GCS. The pilot in the GCS controls the Predator remotely via Ku-band SATCOM and receives the sensor products via the same link. APPENDIX C - COMMUNICATIONS Page C-2
- Page 64 and 65: UAS ROADMAP 2005 provide coverage t
- Page 66 and 67: UAS ROADMAP 2005 recognized today a
- Page 68 and 69: UAS ROADMAP 2005 Class A or B Misha
- Page 70 and 71: UAS ROADMAP 2005 Weight, Lb 100,000
- Page 72 and 73: UAS ROADMAP 2005 Panchromatic Calen
- Page 74 and 75: UAS ROADMAP 2005 4.4.2 Communicatio
- Page 76 and 77: UAS ROADMAP 2005 5.0 OPERATIONS 5.1
- Page 78 and 79: UAS ROADMAP 2005 labs have been inv
- Page 80 and 81: UAS ROADMAP 2005 5.3 OPERATIONS 5.3
- Page 82 and 83: UAS ROADMAP 2005 5.3.3 battlespace
- Page 84 and 85: UAS ROADMAP 2005 6.0 ROADMAP This S
- Page 86 and 87: UAS ROADMAP 2005 range/endurance ai
- Page 88 and 89: UAS ROADMAP 2005 level below that a
- Page 90 and 91: UAS ROADMAP 2005 � Unmanned syste
- Page 92 and 93: UAS ROADMAP 2005 Appendices
- Page 94 and 95: UAS ROADMAP 2005 APPENDIX A: MISSIO
- Page 96 and 97: UAS ROADMAP 2005 be treated more li
- Page 98 and 99: UAS ROADMAP 2005 3. The integration
- Page 100 and 101: UAS ROADMAP 2005 of expendables. In
- Page 102 and 103: UAS ROADMAP 2005 Range Transporter
- Page 104 and 105: UAS ROADMAP 2005 APPENDIX B: SENSOR
- Page 106 and 107: UAS ROADMAP 2005 film can. Primary
- Page 108 and 109: UAS ROADMAP 2005 mature, and integr
- Page 110 and 111: UAS ROADMAP 2005 should be encourag
- Page 112 and 113: UAS ROADMAP 2005 Contractors have p
- Page 116 and 117: UAS ROADMAP 2005 FIGURE C-1. GLOBAL
- Page 118 and 119: UAS ROADMAP 2005 GCS, Ops Cell MOB
- Page 120 and 121: UAS ROADMAP 2005 (TSAT), Net-Centri
- Page 122 and 123: UAS ROADMAP 2005 Architecture, GIG,
- Page 124 and 125: UAS ROADMAP 2005 Tier 1 Team Covera
- Page 126 and 127: UAS ROADMAP 2005 FIGURE C-7. BLACK
- Page 128 and 129: UAS ROADMAP 2005 � Aircraft Contr
- Page 130 and 131: UAS ROADMAP 2005 � Any new federa
- Page 132 and 133: UAS ROADMAP 2005 communications, pr
- Page 134 and 135: UAS ROADMAP 2005 CDL requirements e
- Page 136 and 137: UAS ROADMAP 2005 decryption and enc
- Page 138 and 139: UAS ROADMAP 2005 APPENDIX D: TECHNO
- Page 140 and 141: UAS ROADMAP 2005 specific fuel cons
- Page 142 and 143: UAS ROADMAP 2005 technology program
- Page 144 and 145: UAS ROADMAP 2005 the effect of smal
- Page 146 and 147: UAS ROADMAP 2005 Displays that show
- Page 148 and 149: UAS ROADMAP 2005 29 % ($747.3 M) in
- Page 150 and 151: UAS ROADMAP 2005 Laboratory Initiat
- Page 152 and 153: UAS ROADMAP 2005 APPENDIX E: INTERO
- Page 154 and 155: UAS ROADMAP 2005 layer 4 protocol i
- Page 156 and 157: UAS ROADMAP 2005 The family of stan
- Page 158 and 159: UAS ROADMAP 2005 Military Satellite
- Page 160 and 161: UAS ROADMAP 2005 DoD Discovery Meta
- Page 162 and 163: UAS ROADMAP 2005 STANAG 3809 (Digit
UAS ROADMAP <strong>2005</strong><br />
APPENDIX C: COMMUNICATIONS<br />
INTRODUCTION<br />
This appendix guides industry and the Services on an UA communications migration path toward<br />
improved interoperability. Service acquisition functions include requirements <strong>of</strong>fices, program <strong>of</strong>fices,<br />
acquisition managers, program managers, and research and development programs. Service operators<br />
include operational units, and demonstration activities. Industry includes developers, manufacturers, and<br />
pr<strong>of</strong>essional standards groups. This appendix provides a reference to existing and binding policy and<br />
standards. It also provides time frames for implementation <strong>of</strong> various capabilities.<br />
Overview<br />
The information environment has changed fundamentally over the last 10 years. More importantly it will<br />
continue to change. The Services, in partnership with industry, must develop and field interoperable UA<br />
systems that can adapt to the evolving information environment.<br />
The challenge remains to link disparate systems, effective in their own right, but evolving separately over<br />
time, to form a cohesive collaborative information environment. To this end, DoD has invested in its own<br />
version <strong>of</strong> the internet, the GIG. The GIG, defined as virtually all DoD information technology<br />
infrastructure, exists to provide the timely and accurate information that war fighters need to assure<br />
victory. All DoD <strong>Systems</strong> shall be able to interact with the GIG. New UA systems shall be developed to<br />
comply with the GIG architecture from the outset. At a minimum, web enabled interfaces for legacy<br />
UAV systems would need to be created for the system to be recognized as an entity on the GIG. By<br />
connecting to the network, UAS become part <strong>of</strong> that network.<br />
Everyone on the GIG will become both a producer and a consumer <strong>of</strong> information. The concept <strong>of</strong> sensor<br />
will extend to virtually every piece <strong>of</strong> equipment capable <strong>of</strong> sensing and passing data, from orbiting<br />
satellites to an individual soldier’s gun sights. This information must flow seamlessly, with minimal<br />
human intervention, to unanticipated users as well as well defined, known users, to support both foreseen<br />
and unforeseen information requirements.<br />
The two overarching requirements for next generation UA communications are 1) connect to the GIG,<br />
and 2) comply with spectrum utilization policy. To connect to the GIG, UA programs must take full<br />
advantage <strong>of</strong> DoD programs and initiatives to achieve net-centricity: net enabled CDL, JTRS,<br />
Transformational Satellites (TSAT), High Assurance Internet Protocol Encryption (HAIPE), and the<br />
Defense Information <strong>Systems</strong> Agency (DISA) metadata registry. UA communications must provide<br />
secure, reliable access to all UA capabilities across the entire DoD enterprise. Initially, efforts must focus<br />
on common interfaces for sensor control and dissemination via the GIG. As new payloads and weapons<br />
are introduced, such as communications relay packages, electronic warfare suites, and guided weapons,<br />
web enabled interfaces must be developed to allow control and employment from any authorized node.<br />
The vision is a ubiquitous network where every entity exists as a node and can share and use any data<br />
produced by any other node, anytime.<br />
For complete information regarding the GIG, refer to the GIG Architecture and the GIG Enterprise<br />
Services website at https://ges.dod.mil/.<br />
EXPERIENCE<br />
A review <strong>of</strong> operations in support <strong>of</strong> recent conflicts serves to illustrate current communications<br />
capabilities for two UAS, Global Hawk and Predator. They employed a mix <strong>of</strong> dedicated point-to-point<br />
communications and networked communications. Many <strong>of</strong> the networked communications were IP<br />
based, approaching net-centric capabilities. Examples <strong>of</strong> network capabilities include posting images to<br />
an Image Product Library (IPL), which implements the Task, Post, Process, Use (TPPU) model, and the<br />
widespread use <strong>of</strong> secure internet chat.<br />
A cursory review <strong>of</strong> current methods for radio development and deployment highlights the need for a<br />
more flexible, joint approach to procuring interoperable radio systems.<br />
APPENDIX C - COMMUNICATIONS<br />
Page C-1