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

More documents

Recommendations

Info

Core Avionics Master Plan 2012 Appendix A-2INMARSAT Global Xpress Ka Band Satellite System. (2014) In addition to itscurrent L-band services, INMARSAT has embarked on a new capability and will soonbe launching a new satellite service in the Ka band. Global Xpress has been designedfrom the bottom up to meet the requirements of government aviation applications suchas intelligence surveillance and reconnaissance, which require high sustained datathroughput. Global Xpress will provide 50 Mbps downlink and 5 Mbps uplink speeds.INMARSAT expects to have the service in place starting in 2014. As of yet, there are noNaval Aviation programs currently planning to use this service.High Data Rate Aviation Terminal (HDRAT). (2017) HDRAT would provide forsecure Ka/Ku high data rate satellite links (over commercial and government ownedassets) and LOS communications supporting Airborne Intelligence, Surveillance, andReconnaissance (AISR) platforms. It would also provide AISR platforms with antennasolutions, modem assemblies, and the appropriate waveforms capable of supportinghigh resolution sensor data and C2 links at speeds up to 274 Mbps (platform andmission dependent).D. High Frequency (HF).1. Current capabilities. HF, HF Automatic Link Establishment (ALE), HFInternet Protocol (IP).HF radios operate between 3 and 30 MHz and are still maintained on platforms thatcan accommodate the antennas for back-up BLOS communications. HF commonlyuses ionosphere propagation of radio waves to span BLOS distances. HF datatransmissions typically operate at user data rates 1200 to 2400 bps with advancedmodem waveforms capable of 9600 bps within 3 kHz channels. HF amplifiers typicallytransmit at 20 to 150 Watts for portable units and up to 2000 Watts for high powerstations. HF usage enables ad hoc connectivity (no prior access permissions or timeslot coordination required).HF - Automatic Link Establishment (HF-ALE) was developed based on the militarystandard for interoperability and performance standards for medium and high frequencyradio systems (MIL-STD-188-141A and -141B). HF-ALE enables the radio to initiate acircuit between itself and another HF radio station or network of stations along withautomated frequency selection for the connection. ALE also incorporates NATOStandardization Agreement (STANAG) 5066, which specifies protocols which separateapplication data and modem/radio level information.HF internet Protocol (HFIP or HF-IP) is usually associated with ALE and HF radiodata communications. HFIP provides protocol layers enabling internet file transfer, chat,web, or email.2. Funded Enhancements and Potential Pursuits.Increased Throughput (Wideband HF). (2018) Wideband HF is a waveform indevelopment that will be able to offer users higher data rates over HF. MIL-STD-188-110C is the military standard for HF digital voice.E. Robustness and Security. (see LOS Information Exchange Section G.).A-2 Information Exchange 18
Core Avionics Master Plan 2012 Appendix A-2II. IP Networking.Mandates and Milestones:Internet Protocol Version 6 (IPv6) Implementation. (2008) In 2003 a DoD ChiefInformation Officer Memorandum directed the implementation of IPv6 within DoD forapplications interfacing with the Global Information Grid (GIG). This guidance alsocovers Mobile IPv6 (MIPv6). Follow-on guidance set Dec 2008 as the target compliancedate for all DoD network systems. The main impetus for moving to IPv6 was theexpectation that by 2010, worldwide demand for IP traffic would exceed the 4 billionaddresses provided by 32 bit IPv4. IPv6 uses a 128 bit address which enables avirtually infinite number of addresses. The extended header size of IPv6 requiresadditional bandwidth, which is problematic for tactical links operating in limited spectrumand exchanging short messages.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.Capability Element Evolution:A. Tactical Airborne Network Local Area Network (LAN).1. Current capabilities. (none). [2016: Wideband Airborne Networking at theTactical Edge: Tactical Targeting Networking Technology (TTNT)].There currently is no airborne equivalent to ground-based LANs. The challenge hasbeen to identify a wireless waveform and architecture capable of the bandwidth andsecurity robustness presented by LANs. TTNT had been successfully demonstrated toprovide higher bandwidth connectivity in flight testing in 2005, and used as a backbonenetwork in multiple Joint Fleet Exercises (JFEXs) through 2009. However, delays wereencountered as the Services tried to Jointly commit to a single waveform. Ultimately,Navy convinced DoD that it was their best option to achieve a near to mid-term solutionto meet their requirements.2. Advance Research and Technology Development.Secure Waveform Development & Protocols [TTNT Version 7.0] (2011-2013)The Air Force, Navy, and Joint Tactical Radio System (JTRS) Network EnterpriseDomain (NED) have continued development of a TTNT JTRS Software CompliantArchitecture (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 over earlier versions:Improved data efficiency through decreased message overhead requirements.Improved routing methods through destination and distance evaluations.Link Adaptation to allow spectrum reuse.New algorithms to reduce retransmissions and multicast messaging.Improved Signal In Space performance.Compliance with JTRS Software Compliant Architecture (SCA).Compliance with NSA Unified Information Security Criteria (UISC) requirements.A-2 Information Exchange 19
Page 1 and 2:
PMA209Endorsement and DistributionP
Page 3 and 4:
Table of ContentsExecutive SummaryE
Page 5 and 6:
Core Avionics Master PlanExecutive
Page 7 and 8:
Core Avionics Master Plan Ensure th
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 Plan2. Where p
Page 15 and 16: Core Avionics Master Plan3. Leverag
Page 17 and 18: Core Avionics Master PlanSECNAVISNT
Page 19 and 20: Core Avionics Master PlanThe follow
Page 21 and 22: Core Avionics Master PlanIn 2010, P
Page 23 and 24: Core Avionics Master PlanDoD 4140.1
Page 25 and 26: Core Avionics Master Plan 2012Appen
Page 27 and 28: Core Avionics Master Plan 2012 Appe
Page 61: Core Avionics Master Plan 2012 Appe
Page 113 and 114:
Core Avionics Master Plan 2012 Appe
Page 115 and 116:
Page 117 and 118:
Page 119 and 120:
show all

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

Create successful ePaper yourself

Delete template?

Save as template?