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 FIGURE C-7. BLACK TRANSPORT EDGE-TO-EDGE. DoD Net-Centric Data Strategy For data from one computer or software application to be useable in a different computer or software application, that data must be in a format that is compatible to both. Traditionally, DoD has accomplished this compatibility through data administration, standardizing and controlling data element definitions and structures across the DoD enterprise. This approach proved too cumbersome, in part due to the constantly evolving technology and in part due to the sheer scope of the enterprise. DoD/CIO has since published an updated approach to achieving data interoperability called the DoD Net- Centric Data Strategy. This approach expands the focus beyond mere standardization of format, to making data visible and accessible across the network. It recognizes that in addition to predefined sets of users, there will be unanticipated users requiring access to the data. The key tenet to this strategy is the development, registration and publication of metadata. This allows developers full access information about data made available and simplifies the creation of interfaces to feed the data to various applications. Complete information regarding the DoD Net-Centric Data Strategy is available at the DoD Metadata Registry and Clearing house at http://diides.ncr.disa.mil/mdregHomePage/mdregHome.portal. UA SYSTEMS ENGINEERING Implementing network interfaces between all UA systems and subsystems provides three key benefits: (1) connects the UA to the GIG through either legacy, current, or programmed physical links - copper wire, optical fiber, RF, laser (2) enhances the GIG’s aggregate data handling capacity, and (3) facilitates separating UA functions, making it easier to create modular plug and play components. Separate Physical Connection From Transport Protocol UA systems do not have to wait until a net-centric wireless technology is fielded to connect to the GIG. The physical connection between two nodes, be it wire, radio waves or light, merely transfers a signal from one point in space to another. Embedded in that signal is the sequence of ones and zeros that constitute the data being passed. IP based network connections can be implemented using any physical connection. This makes it possible to connect legacy systems to the GIG by replacing tightly coupled, unique data transfer implementations with IP based network connections. Creating an IP network based transport layer separates the data transfer protocols from the physical connection and integrates UA into the GIG regardless of the wireless technology employed (C-band, CDL, JTRS, LaserComm). APPENDIX C - COMMUNICATIONS Page C-13
UAS ROADMAP 2005 Contribute to the GIG’s Aggregate Bandwidth Currently, UA communicate with their respective control elements via dedicated, point-to-point data links. These data links provide continuous information handling capacity between the nodes, up to the maximum data rate supported. During long cruise segments of a mission, however, traffic across the dedicated link may drop to nearly zero. The closed system design precludes other users from taking advantage of the unused bandwidth. Implementation of an IP based, packet switched network interface, between UA systems with multiple data links, control elements and other nodes, provides a path through the UA communications links through which routers can pass packets during lulls in the primary system’s communications needs. Each UA system adds its individual throughput capacity to the larger network. Access priority can be controlled using QoS and COS technologies as defined by IEEE standard 802.1p giving top priority to the primary system’s communications requirements. Looking at the operating theater’s communications infrastructure as a whole, it becomes clear that implementing networked interfaces for all communications links, not just UA, significantly increases data handling in theater, with no compromise to the data needs of the primary system. Separate UA Functions In addition to migrating point to point links to network interfaces, UA components and functions must be separated, modularized and connected using network interfaces. In keeping with the net-centric approach to system design, Figure C-8 illustrates one approach to separating and modularizing UA components and functions, within the UA. The platform’s local area network (LAN) connects sensors, sensor management, and flight management units. The communications equipment connects to the WAN traffic manager and links the platform LAN to other Local Area Networks. Within the control station (ground, afloat, or airborne) the same approach applies. Consoles connect to the LAN, and the communications equipment provides pathways between that LAN and other LAN segments. UA Flight Control Payload Control and Product Dissemination Weapons Employment Situational Awareness • Separable functional interfaces • Modular payloads and weapons • IP based network interfaces • Standard Control Interface Mapping Other Interfaces SATCOM CDL/NDL/JTRS/WNW ATC/ATM FIGURE C-8. AIRCRAFT SYSTEMS ENGINEERING MODEL – IP FRIENDLY NETWORK INTERFACES. Communications and infrastructure requirements for all UAS will be defined in terms of four key functional interfaces. APPENDIX C - COMMUNICATIONS Page C-14 User User Control Station Terrestrial
- 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 114 and 115: UAS ROADMAP 2005 APPENDIX C: COMMUN
- 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 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 166 and 167: UAS ROADMAP 2005 Level 1: Indirect
- 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
UAS ROADMAP <strong>2005</strong><br />
FIGURE C-7. BLACK TRANSPORT EDGE-TO-EDGE.<br />
DoD Net-Centric Data Strategy<br />
For data from one computer or s<strong>of</strong>tware application to be useable in a different computer or s<strong>of</strong>tware<br />
application, that data must be in a format that is compatible to both. Traditionally, DoD has accomplished<br />
this compatibility through data administration, standardizing and controlling data element definitions and<br />
structures across the DoD enterprise. This approach proved too cumbersome, in part due to the constantly<br />
evolving technology and in part due to the sheer scope <strong>of</strong> the enterprise.<br />
DoD/CIO has since published an updated approach to achieving data interoperability called the DoD Net-<br />
Centric Data Strategy. This approach expands the focus beyond mere standardization <strong>of</strong> format, to<br />
making data visible and accessible across the network. It recognizes that in addition to predefined sets <strong>of</strong><br />
users, there will be unanticipated users requiring access to the data. The key tenet to this strategy is the<br />
development, registration and publication <strong>of</strong> metadata. This allows developers full access information<br />
about data made available and simplifies the creation <strong>of</strong> interfaces to feed the data to various applications.<br />
Complete information regarding the DoD Net-Centric Data Strategy is available at the DoD Metadata<br />
Registry and Clearing house at http://diides.ncr.disa.mil/mdregHomePage/mdregHome.portal.<br />
UA SYSTEMS ENGINEERING<br />
Implementing network interfaces between all UA systems and subsystems provides three key benefits:<br />
(1) connects the UA to the GIG through either legacy, current, or programmed physical links - copper<br />
wire, optical fiber, RF, laser (2) enhances the GIG’s aggregate data handling capacity, and (3) facilitates<br />
separating UA functions, making it easier to create modular plug and play components.<br />
Separate Physical Connection From Transport Protocol<br />
UA systems do not have to wait until a net-centric wireless technology is fielded to connect to the GIG.<br />
The physical connection between two nodes, be it wire, radio waves or light, merely transfers a signal<br />
from one point in space to another. Embedded in that signal is the sequence <strong>of</strong> ones and zeros that<br />
constitute the data being passed. IP based network connections can be implemented using any physical<br />
connection. This makes it possible to connect legacy systems to the GIG by replacing tightly coupled,<br />
unique data transfer implementations with IP based network connections. Creating an IP network based<br />
transport layer separates the data transfer protocols from the physical connection and integrates UA into<br />
the GIG regardless <strong>of</strong> the wireless technology employed (C-band, CDL, JTRS, LaserComm).<br />
APPENDIX C - COMMUNICATIONS<br />
Page C-13