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

More documents

Recommendations

Info

Core Avionics Master Plan 2012 Appendix A-2Soldier Radio Waveform (SRW). (2010-2014) SRW is a JTRS waveform beingdeveloped for dismounted and unattended applications with severe Size Weight andPower (SWaP) constraints. The US Army plans to utilize SRW as a stub network,interconnecting to other stub networks via WNW. Waveform characteristics include: 3 Signals in Space: SRW, AJ and Low Probability of Intercept / Low Probability ofDetection (LPI/LPD). Features to minimize SWaP: incorporation of a network architecture thatminimizes power demands, optimizes voice communications, and minimizesprocessing requirements. Formation of stub/leaf networks that rely on WNW for backbone services. Unique security requirements that support unclassified and classified nodes.The waveform is designed to operate in varying bandwidths from 75 KHz to 32 MHzand operating frequencies from 225 MHz to 2.5 GHz. The SRW waveform has athreshold data rate requirement of 1.2 Mbps in a 1.2 MHz channel. Achievable range isa function of the path loss, which is a function of terrain, geometry and operatingfrequency.C. Wide Area Networking (WAN).The GIG is defined as: The globally interconnected set of information capabilities,associated processes and personnel for collecting, processing, storing,disseminating, and managing information on demand to warfighters, policy makers,and support personnel. The GIG includes all owned and leased communications andcomputing systems and services, software (including applications), data, securityservices and other associated services necessary to achieve information superiority.It also includes National Security Systems. The GIG supports IP networking inaccordance with the Internet Engineering Task Force (IETF) established standards.The Defense Information Security Agency (DISA) procures and controls the DefenseInformation System Network (DISN), which provides the transport infrastructure(teleports, leased lines and commercial satellites) to enable GIG connectivity. Teleportsare shore satellite gateways linking deployed forces to the GIG via connectivity tomultiple satellite systems. DISA also manages the development of infrastructureservices referred to as Net Centric Enterprise Services (NCES) that enable user access(portals), content discovery and delivery, and synchronous collaboration in a serviceoriented architecture foundation. Further services and additional capabilities areexpected to be forthcoming in accordance with the JROC approved GIG 2.0 InitialCapabilities Document (ICD).1. Current capabilities.The Navy organic shore infrastructure that interfaces Naval forces with theDISN/GIG is made up of Naval Computer and Telecommunications Area MasterStations (NCTAMS), Naval Computer and Telecommunications Stations (NCTS) andNetwork Operations Centers (NOC). PMW 790 manages this infrastructure to providethe Navy WAN. The Automated Digital Network System (ADNS) serves as the tacticalWAN, providing the network infrastructure and services for Navy IP network operations.A-2 Information Exchange 22
Core Avionics Master Plan 2012 Appendix A-2ADNS enables deployed ships, subs and aircraft to interface with the shoreinfrastructure and connect to the DISN/GIG. ADNS integrates hardware, software RadioFrequency (RF) links and services to provide a mobile WAN. The current version,ADNS increment II, provides the following capabilities:Interconnects multiple security enclaves in a common architecture.Utilizes multiple simultaneous RF links for reach back and reach forward.Supports QoS by prioritizing data and implementing priority processing.Interfaces to platform LANs.SPAWAR PMW-160 manages the ADNS program. PMW-750 is the Air IntegrationOffice responsible for coordinating efforts with NAVAIR platforms. PMW-750 is currentlyworking with NAVAIR program offices to integrate ADNS on E-2C, EP-3E, P3-C, P-8A,MH-60R and BAMS. SPAWAR provides an airborne ADNS package, designatedAN/USQ-144(V)8, as a three-quarter Air Transport Rack (ATR) form factor. Platformsare procuring other routers that must be loaded with an ADNS routing template andtested by SPAWAR for compatibility in order to connect to the ADNS network. ADNSinterfaces to RF links on these platforms including HF-IP (E-2C, P8A), INMARSAT Swift64 (EP-3E), INMARSAT Swift Broadband (P-3C Anti-Submarine Warfare ImprovementProgram [AIP], P-9A, Broad Area Maritime Surveillance [BAMS]), Wideband GlobalSATCOM (WGS - BAMS), and Common Data Link (CDL - proof of concept on MH-60R).2. Funded Enhancements and Potential Pursuits.Cypher Text Backbone, IPv6/IPv4 dual stack, Converged IP/Enhanced Qualityof Service, Increased Bandwidth (ADNS III). (2016) ADNS increment III is the nextgeneration of ADNS and is currently implemented in NCTAMS LANT and PAC andbeing fielded on ships. The primary requirement being met by ADNS III is the GIGrequirement to implement a Cipher Text (CT) core, implemented via NSA approved IPSecurity (IP Sec) standards known as High Assurance Internet Protocol Encryption(HAIPE). In order to maintain backward compatibility with Increment II configuredplatforms not implementing HAIPE, both increments will be operating in the shoreinfrastructure through 2015. IOC for a switch over to Increment III is 2016. Thisincrement will provide:CT Backbone (‘black core’) routing in compliance with GIG requirement.IPv6/IPv4 dual stack (IPv6 in compliance with GIG requirements).Converged IP/Enhanced QoS – All traffic, voice, data and video, will be IP withdynamic Quality of Service (QoS) and bandwidth management.Load distribution over all RF links.Increased bandwidth 25 / 50 Mbps per platform (requires capable RF link).D. Robustness and Security. (see LOS Information Exchange Section G.).A-2 Information Exchange 23
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 65: Core Avionics Master Plan 2012 Appe
Page 117 and 118:
Core Avionics Master Plan 2012 Appe
Page 119 and 120:
Core Avionics Master Plan 2012 Appe
show all

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

Create successful ePaper yourself

Delete template?

Save as template?