Unmanned Aircraft Systems Roadmap 2005-2030 - Federation of ...

Unmanned Aircraft Systems Roadmap 2005-2030 - Federation of ... Unmanned Aircraft Systems Roadmap 2005-2030 - Federation of ...

06.01.2013 Views

UAS ROADMAP 2005 CDL requirements evolution Feed into JTRS WNW requirements Evolve SCA compliant software defined CDL hardware and software, and fold into JTRS family of software defined radios JTRS WNW capable of 274Mbps+ And range exceeding 250 nm SCA compliant, JTRS version of software defined CDL FIGURE C-10. POTENTIAL CDL MIGRATION PATHS. JTRS The Joint Tactical Radio System program addresses legacy radio problems (refer to the section entitled Radios) through a two-pronged approach: software and hardware. First, the SCA, written for the JTRS program, specifies guidelines for developing software-defined waveforms. The Object Management Group (OMG) has adopted the SCA as an industry standard. In addition to software, JTRS certified hardware is being developed that can import software-defined waveforms and communicate using them. The JTRS program will oversee development of a family of software-defined radios, based on a set of common hardware components and software applications. All UA programs that require radios must synchronize purchases with the JTRS schedule. In cases where JTRS radios are not yet available, these programs must obtain a waiver, procure the minimum required number of legacy radios, and have a migration plan to procure and install JTRS counterparts as they become available. Figure C-11 shows IOC dates for key UA related JTRS programs. Cluster 1 and the MIDS JTRS should reach IOC in 2007. USN/USA will demonstrate and begin fielding Fire Scout with an integrated SCA compliant CDL (TCDL), using a JTRS Cluster I terminal equipped with a high-band modem module. AMF JTRS is expected to reach IOC in 2009. This schedule may change, but it remains a requirement for UA programs to coordinate all future radio purchases with the JTRS program office. For more detailed information about JTRS Clusters refer to the section entitled “Joint Tactical Radio System.” Additional information about the JTRS program and means of contact can be found at http://jtrs.army.mil/index.htm. APPENDIX C - COMMUNICATIONS Page C-21

UAS ROADMAP 2005 JTRS Cluster 1 AMF JTRS MIDS JTRS TSAT UA Related Program Schedules CY04 CY05 CY06 CY07 CY08 CY09 CY10 CY11 CY12 CY13 CY14 CY15 HAIPE Cluster 1 NSA Certification AMF JTRS Vehicular and Rotary Wing Platforms (i.e. FIreScout) IOC Airborne, Maritime and Fixed Station Applications Link 16, TACAN and Digital Voice MIDS JTRS NSA Certification IOC IOC Contract Award PDR CDR Key Decision Point LRIP APPENDIX C - COMMUNICATIONS Page C-22 TSAT 1 TSAT 2 IOC TSAT 3 TSAT 4 FIGURE C-11. CONSOLIDATED HIGH LEVEL PROGRAM SCHEDULE. TSAT DoD relies extensively on SATCOM for UA command and control as well as product dissemination. Reliance on foreign commercial vendors, however, entails some risk. A government owned, broadband, SATCOM constellation will reduce reliance on commercial SATCOM and provide more available and cost effective BLOS communications support to UA operations. For a more complete description of current UA communications, refer to the section entitled “Historical Perspective,” and its discussions of Global Hawk and Predator operations. The TSAT constellation implements the space borne component of the GIG, moving data globally through an orbiting optical and RF based network. The first TSAT is scheduled for launch in FY13 (CY12). An additional TSAT will be launched each year until all 5 TSAT systems are established in their geosynchronous orbits (Figure C-11). TSAT will connect to the terrestrial backbone via teleports located at strategic points throughout the globe. TSAT will be transparent to most GIG users, and be experienced simply as a high data rate transfer capability. UAS, such as Global Hawk and Predator, will connect to TSAT directly through the FAB-T, which include both RF and Optical data links. High Assurance Internet Protocol Encryption Devices The principal objective of Information Assurance is to assure access to authorized users while denying access to unauthorized users. For example, imagery exploiters and operations center personnel may need UA data, but a medical technician does not. Historically the separation has been accomplished through physically securing the classified networks, and encrypting the information as it leaves the protected facility. Circuits that transfer unencrypted classified information are designated red in security accreditation plans. Circuits carrying unclassified information or encrypted classified information are designated black. Open connections between red circuits and black circuits are prohibited. This principle of red/black separation guides the design and implementation of classified information processing facilities. A variation on the idea of red/black separation, and a fundamental tenet of the GIG, is the concept of red edge/black core. Information created in classified enclaves (red edge) is encrypted and sent across the GIG as unclassified (black core) information. This concept allows all information to traverse the web through any available series of networks, regardless of encryption schemes employed. Some daunting architectural challenges must be overcome in order to achieve red edge/black core. One issue has to do with embedded enclaves, which under the current architecture would require successive

UAS ROADMAP <strong>2005</strong><br />

JTRS<br />

Cluster 1<br />

AMF JTRS<br />

MIDS JTRS<br />

TSAT<br />

UA Related Program Schedules<br />

CY04 CY05 CY06 CY07 CY08 CY09 CY10 CY11 CY12 CY13 CY14 CY15<br />

HAIPE<br />

Cluster 1 NSA Certification<br />

AMF JTRS<br />

Vehicular and Rotary Wing Platforms<br />

(i.e. FIreScout)<br />

IOC<br />

Airborne, Maritime and Fixed Station Applications<br />

Link 16, TACAN and Digital Voice<br />

MIDS JTRS NSA Certification<br />

IOC<br />

IOC<br />

Contract Award PDR CDR Key Decision Point LRIP<br />

APPENDIX C - COMMUNICATIONS<br />

Page C-22<br />

TSAT 1 TSAT 2 IOC TSAT 3 TSAT 4<br />

FIGURE C-11. CONSOLIDATED HIGH LEVEL PROGRAM SCHEDULE.<br />

TSAT<br />

DoD relies extensively on SATCOM for UA command and control as well as product dissemination.<br />

Reliance on foreign commercial vendors, however, entails some risk. A government owned, broadband,<br />

SATCOM constellation will reduce reliance on commercial SATCOM and provide more available and<br />

cost effective BLOS communications support to UA operations. For a more complete description <strong>of</strong><br />

current UA communications, refer to the section entitled “Historical Perspective,” and its discussions <strong>of</strong><br />

Global Hawk and Predator operations.<br />

The TSAT constellation implements the space borne component <strong>of</strong> the GIG, moving data globally<br />

through an orbiting optical and RF based network. The first TSAT is scheduled for launch in FY13<br />

(CY12). An additional TSAT will be launched each year until all 5 TSAT systems are established in their<br />

geosynchronous orbits (Figure C-11). TSAT will connect to the terrestrial backbone via teleports located<br />

at strategic points throughout the globe. TSAT will be transparent to most GIG users, and be experienced<br />

simply as a high data rate transfer capability.<br />

UAS, such as Global Hawk and Predator, will connect to TSAT directly through the FAB-T, which<br />

include both RF and Optical data links.<br />

High Assurance Internet Protocol Encryption Devices<br />

The principal objective <strong>of</strong> Information Assurance is to assure access to authorized users while denying<br />

access to unauthorized users. For example, imagery exploiters and operations center personnel may need<br />

UA data, but a medical technician does not. Historically the separation has been accomplished through<br />

physically securing the classified networks, and encrypting the information as it leaves the protected<br />

facility. Circuits that transfer unencrypted classified information are designated red in security<br />

accreditation plans. Circuits carrying unclassified information or encrypted classified information are<br />

designated black. Open connections between red circuits and black circuits are prohibited. This principle<br />

<strong>of</strong> red/black separation guides the design and implementation <strong>of</strong> classified information processing<br />

facilities.<br />

A variation on the idea <strong>of</strong> red/black separation, and a fundamental tenet <strong>of</strong> the GIG, is the concept <strong>of</strong> red<br />

edge/black core. Information created in classified enclaves (red edge) is encrypted and sent across the<br />

GIG as unclassified (black core) information. This concept allows all information to traverse the web<br />

through any available series <strong>of</strong> networks, regardless <strong>of</strong> encryption schemes employed.<br />

Some daunting architectural challenges must be overcome in order to achieve red edge/black core. One<br />

issue has to do with embedded enclaves, which under the current architecture would require successive

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!