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 Level 1: Indirect receipt/transmission of UA related payload data. . (provided by other standards in the NIIA - STANAG 4586 not required) Level 2: Direct receipt of ISR/other data where “direct” covers reception of the UA payload data by the UCS when it has direct communication with the UA (provided by other standards in the NIIA - STANAG 4586 not required) Level 3: Control and monitoring of the UA payload in addition to direct receipt of ISR/other data . (handover of sensor control as defined in STANAG 4586). Level 4: Control and monitoring of the UA, less launch and recovery (handover of air vehicle control as defined in STANAG 4586). Level 5: Control and monitoring of the UA (Level 4), plus launch and recovery functions The interoperability levels defined above can be achieved through the standardization of interfaces between the UA airborne elements and the UCS, between the air vehicle elements and external C4I elements, and between the UCS and external C4I Systems. In order to achieve interoperability, the UCS Architecture and interfaces must support the appropriate communication protocols and message formats for legacy as well as new UA systems. Level 2 and above (2+) of interoperability requires the use of a ground data terminal (GDT) that is interoperable with the air data terminal (ADT), as defined in CDL/STANAG 7085 (e.g., connectivity between the GDT and ADT is prerequisite for level 2+ interoperability). At all levels, the data formats and data transfer protocols must also comply with the NIIA standards. For level 1 or level 2, the NIIA standards for data format and data transfer provide the required interface requirements. For levels 3 and above, STANAG 4586 provides the sensor and airborne platform control functionality for the higher levels. There are already a number of existing or emerging STANAGs that are applicable to UA systems. They provide standards for interoperable data link (STANAG 7085), digital sensor data between the payload and the AV element of the data link (STANAG 7023, 4545), and for on board recording device(s) (STANAG 7024, 4575). Additionally, the STANAG 4586, unmanned control system (UCS), describes interfaces applicable to ground control stations and air vehicles, to include air vehicle control. Although somewhat limited as to broad mission area application, this STANAG contains an interface description, the DLI, which provides an excellent starting point for the development of a robust air vehicle interface, to include vehicle control functions. Thus, the approach to achieving the desired level of UA interoperability is based on compliance with existing standards or establishing new standards for a number of UA functions. � An open network architecture using industry standards including internet protocol, Ethernet and generic framing procedure. � A data link system(s) that provides connectivity and interoperability between the UCS and the AV(s). The data link system(s) must accommodate legacy as well as future systems. STANAG 7085, Interoperable Data Links for Imaging Systems, specifies a data link system that would provide the required connectivity and interoperability. The data link must just provide for transmission of data over the RF link, not be the interface for the sensor and flight management functions or do routing functions. � Format for payload/sensor data for transmission to the UCS via the data link and/or for recording on the on-board recording device. STANAG 7023, NATO Primary Image Format Standard, with addition for non-imagery sensors, (e.g., electronic support measures (ESM)), and STANAG 4545, NATO Secondary Imagery Format, are the required data formats for imagery. If GMTI data is to be used, STANAG 4607 defines the required format, and STANAG 4609 defines the format for digital motion imagery. � Recording device for on board recording of sensor data, if required, STANAG 7024, Imagery Air Reconnaissance Tape Recorder Standard, and STANAG 4575, NATO Advanced Data Storage Interface, specify standard recording devices and interface respectively. APPENDIX E – INTEROPERABILITY STANDARDS Page E-15
UAS ROADMAP 2005 � A standard describing the interfaces and messages necessary to control an air vehicle. A starting point for this activity is the DLI segment of STANAG 4586. PROCESS FOR SELECTING STANDARDS UA standards are usually selected for implementation by a development program from those in the DISR. New standards are added to the DISR periodically and existing ones updated based on technological advancement. However, the DISR is very broadly written to encompass the full range of interoperability needs. Therefore, subsets must be chosen for specific mission areas, such as UA. Additionally, some needed standards are not specifically included in the DISR, due to time lag as new technologies emerge or due to lack of specificity for lower level protocols. Currently, there is not a formal process in-place for choosing subsets of the DISR standards for UA application except during development of the UA Roadmap. The fundamental criterion for standards selection should be whether or not the proposed standard will improve UA systems interoperability. The following criteria must be considered the minimal set required for interoperability or reuse: � Standards are technically mature and stable � Technically implemental � Publicly available � Consistent with law, regulation, policy, or guidance documentation � Preferred standards are those that are commercially supported in the marketplace with several validated implementations by multiple vendors (e.g., mainstream products) Standards Compliance A formal standards process must be put in-place for choosing subsets of the DISR standards for UA application and feed development of the UA Roadmap. Wherever possible, this must be worked as part of broader manned aviation, ISR and strike community activities. APPENDIX E – INTEROPERABILITY STANDARDS Page E-16
- 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
- Page 164 and 165: UAS ROADMAP 2005 � SDN.706, X.509
- Page 168 and 169: UAS ROADMAP 2005 APPENDIX F: AIRSPA
- Page 170 and 171: UAS ROADMAP 2005 Class A or B Misha
- Page 172 and 173: UAS ROADMAP 2005 Hawk and Predator,
- Page 174 and 175: UAS ROADMAP 2005 knowledge skills r
- Page 176 and 177: UAS ROADMAP 2005 decision and the a
- Page 178 and 179: UAS ROADMAP 2005 OSD ROADMAP GOALS
- Page 180 and 181: UAS ROADMAP 2005 APPENDIX G: TASK,
- Page 182 and 183: UAS ROADMAP 2005 APPENDIX H: RELIAB
- Page 184 and 185: UAS ROADMAP 2005 throughout its ACT
- Page 186 and 187: UAS ROADMAP 2005 17% 14% 12% 19% 38
- Page 188 and 189: UAS ROADMAP 2005 that for a number
- Page 190 and 191: UAS ROADMAP 2005 RECOMMENDATIONS Ba
- Page 192 and 193: UAS ROADMAP 2005 APPENDIX I: HOMELA
- Page 194 and 195: UAS ROADMAP 2005 CUSTOMS AND BORDER
- Page 196 and 197: UAS ROADMAP 2005 APPENDIX J: UNMANN
- Page 198 and 199: UAS ROADMAP 2005 Joint Robotics Pro
- Page 200 and 201: UAS ROADMAP 2005 Anti-Personnel/Obs
- Page 202 and 203: UAS ROADMAP 2005 The UGV family wil
- Page 204 and 205: UAS ROADMAP 2005 In Phase I, an exp
- Page 206 and 207: UAS ROADMAP 2005 is NSWC Panama Cit
- Page 208 and 209: UAS ROADMAP 2005 APPENDIX K: SURVIV
- Page 210 and 211: UAS ROADMAP 2005 such as flares, ch
- Page 212 and 213: UAS ROADMAP 2005 TABLE K-1. SURVIVA
UAS ROADMAP <strong>2005</strong><br />
� A standard describing the interfaces and messages necessary to control an air vehicle. A starting point<br />
for this activity is the DLI segment <strong>of</strong> STANAG 4586.<br />
PROCESS FOR SELECTING STANDARDS<br />
UA standards are usually selected for implementation by a development program from those in the DISR.<br />
New standards are added to the DISR periodically and existing ones updated based on technological<br />
advancement. However, the DISR is very broadly written to encompass the full range <strong>of</strong> interoperability<br />
needs. Therefore, subsets must be chosen for specific mission areas, such as UA. Additionally, some<br />
needed standards are not specifically included in the DISR, due to time lag as new technologies emerge or<br />
due to lack <strong>of</strong> specificity for lower level protocols. Currently, there is not a formal process in-place for<br />
choosing subsets <strong>of</strong> the DISR standards for UA application except during development <strong>of</strong> the UA<br />
<strong>Roadmap</strong>. The fundamental criterion for standards selection should be whether or not the proposed<br />
standard will improve UA systems interoperability.<br />
The following criteria must be considered the minimal set required for interoperability or reuse:<br />
� Standards are technically mature and stable<br />
� Technically implemental<br />
� Publicly available<br />
� Consistent with law, regulation, policy, or guidance documentation<br />
� Preferred standards are those that are commercially supported in the marketplace with several<br />
validated implementations by multiple vendors (e.g., mainstream products)<br />
Standards Compliance<br />
A formal standards process must be put in-place for choosing subsets <strong>of</strong> the DISR standards for UA<br />
application and feed development <strong>of</strong> the UA <strong>Roadmap</strong>. Wherever possible, this must be worked as part <strong>of</strong><br />
broader manned aviation, ISR and strike community activities.<br />
APPENDIX E – INTEROPERABILITY STANDARDS<br />
Page E-16