Core Avionics Master Plan - NAVAIR - U.S. Navy

More documents

Recommendations

Info

Core Avionics Master Plan 2011 Appendix A-2Core AvionicsCapability EvolutionRoadmapsInternet Protocol NetworkingCapabilityElementsNetwork Centric Warfare & Information DominanceAirborne Networking at theTactical Edge [Tactical TargetingNetworking Technology (TTNT)]Secure Waveform Development & Protocols [TTNT v7.0] Wideband TacticalNetworking (TTNT )TacticalAirborneNetwork(LAN)Interoperability w/ Tactical EdgeGround Networks [WNW & SRW]TacticalGroundNetwork(LAN) Wideband Networking Waveform (WNW); Soldier Radio Waveform (SRW)GIG Connectivity [Navy Wide Area Network (WAN)]Wide AreaNetworking(WAN)Cipher Text Backbone, IPv6/IPv4 dual stack, ConvergedIP/Enhanced QoS, Increased Bandwidth [ADNS III]Single Security Level, Non-programmable COMSEC, HAIPEMultiple Level Security (MLS)ProgrammableCrypto; Stand-aloneEncryption [VACM]NSA Compliant Secure Comms;Multiple Independent Level Security (MILS)Security(also applies toLOS & BLOSComms)ADNSIncrement IIIMandates &MilestonesFY: 10 11 12 13 14 15 16 17 18Mandate orMilestoneUnfunded PotentialCapability DevelopmentFunded CapabilityEnhancementAdv ResearchOr Tech DevCurrent CapabilityBaseline StateA-2 Information Exchange 16
Core Avionics Master Plan 2011 Appendix A-2III. IP Networking.Mandates and Milestones:Automated Digital Network System (ADNS) Increment III. (2016) The US Navy isconverting IP Wide Area Network (WAN) to Cipher Text (CT). All platforms connectingto the Navy WAN must be Increment III compliant by 2016.A. Tactical Airborne Network Local Area Network (LAN).1. Current capabilities.TTNT is an L-band anti-jam networking waveform well suited to support airbornecollaborative applications. It was successfully demonstrated in flight testing in 2005, andbeen used as a backbone network in multiple Joint Fleet Exercises (JFEXs) from 2004through 2009. It was designated as an initial increment of Joint Airborne Network -Tactical Edge (JAN-TE) requirements document in 2006, however the designation wassubsequently rescinded in 2009 and funding for integration into the MIDS-J terminalwas retracted. The ISR Task Force is using TTNT in an operationally relevantdemonstration to support the timely transport of ISR data to geographically separatedcommand structures. It provides a secure, ad hoc mesh network infrastructure.2. Advance Research and Technology Development.Secure Waveform Development & Protocols [TTNT Version 7.0] The Air Force,Navy, and JTRS Network Enterprise Domain (NED) have continued development of aTTNT JTRS SCA waveform which has been designated as version 7.0. The CriticalDesign Review (CDR) for this version was completed in 2008 and the JTRS NEDschedule for completion of the waveform is 4Q 2013. The TTNT Version 7.0 waveformwill provide the following improvements to version 6.0:Improved data efficiency through decreased message overhead requirementsImproved routing methods through destination and distance evaluationsLink Adaptation to allow spectrum reuseNew algorithms to reduce retransmissions and multicast messagingImproved Signal In Space performanceIncorporated JTRS SCAIncorporated NSA Unified Information Security Criteria (UISC) requirements3. Funded Enhancements and Potential Pursuits.Wideband Tactical Networking (TTNT). (2016) Currently there is no fundingprogrammed for development of a TTNT transceiver or integration of the waveform intoMIDS-J. The current version of the waveform, employed in legacy terminals, is version6.0. A limited number of EDM terminals are being used by the UCAS-N program todemonstrate carrier landing and aerial refueling capabilities for that platform. Platformintegration of a TTNT terminal currently presents the best near term opportunity toestablish a wideband tactical network capability for Naval Aviation.A-2 Information Exchange 17
Page 3 and 4:
Table of ContentsExecutive SummaryE
Page 5 and 6:
Core Avionics Master PlanExecutive
Page 7 and 8:
Core Avionics Master PlanPursue Per
Page 9 and 10: I. INTRODUCTION.Core Avionics Maste
Page 11 and 12: IV. RECOMMENDED PRACTICES.Core Avio
Page 13 and 14: Core Avionics Master Plan4. Define
Page 15 and 16: Core Avionics Master PlanAvCIP proc
Page 17 and 18: Core Avionics Master PlanSECNAVISNT
Page 19 and 20: Core Avionics Master PlanSimilar to
Page 21 and 22: Core Avionics Master PlanInterface
Page 23 and 24: Core Avionics Master PlanSECNAV Mem
Page 25 and 26: Core Avionics Master Plan 2011Appen
Page 27 and 28: Core Avionics Master Plan 2011 Appe
Page 43 and 44: EP-3EP-3CRQ-4AMQ-8BEP-8AP-8AAH-1WAH
Page 59: Core Avionics Master Plan 2011 Appe
Page 111 and 112:
Core Avionics Master Plan 2011 Appe
Page 113 and 114:
Page 115 and 116:
show all

Core Avionics Master Plan - NAVAIR - U.S. Navy

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?