Airborne Network Architecture - phoenixaerospace.us

1、AIRBORNE NETWORK ARCHITECTURESystem Communications Description&Technical Architecture ProfileVersion 1.17 October 2004This document contains a description of the USAF Airborne Network Architecture. It is expected that this architecture will continue to be developed in terms of both the level of deta

2、il in which it is expressed and in the evolution of its fundamental concepts. Please contact the Chair of the Airborne Network Special Interest Group to determine the most recent version of this document.Prepared by HQ ESC/NI1 for theUSAF Airborne Network Special Interest GroupTable of Contents1.Int

3、roduction11.1Definition of Airborne Network11.2Purpose of Document11.3Relationship to Other Documents11.4Contents21.5Intended Use32.Operational Context42.1Operational Concept Description for the Airborne Network (OV-1)42.2Objective Airborne Network Communications Capabilities43.Airborne Network Tene

4、ts74.Airborne Network Description (SV-1)94.1Overview94.2Network Functions94.2.1Inter-node Connectivity94.2.2Information Assurance (IA)114.2.3Network Management124.2.4Link Management134.2.5Network Services144.3Network Topologies (Nodes and Links)144.3.1Node Types154.3.2Link TypesBackbone254.

5、3.2.2Subnet2Network Access2Legacy264.3.3Typical Topologies2Space, Air, Ground Tether2Flat Ad-Hoc2Tiered Ad-Hoc2Persistent Backbone285.Airborne Network System Functions (SV-4)305.1On-Board Infrastructure305.1.1Intra Platform Distribution30Serial

6、Data Buses30Local Area Networks305.1.2Platform Information Assurance305.1.3Platform Network Management315.1.4Gateways/Proxies3Legacy Infrastructure Gateways3Legacy Transmission System Data Link Gateways3TDL Gateways3Performance Enhancing Proxies325.2AN Equipmen

7、t335.2.1Inter-node Connectivity3Routing/Switching3Quality of Service (QoS)/Class of Service (CoS)3.1QoS-Aware Application Interfaces3.2QoS/CoS Mechanisms3.3QoS-Based Routing/Switching3.4QoS Manager385.2.2Information Assurance3GIG IA Architectur

8、e40Supporting Infrastructures4.1Security Management Infrastructure (SMI)4.2DoD Key Management Infrastructure (KMI)4.3Public Key Infrastructure (PKI)4AN Information Flows4.1Least Privilege4.2User Traffic4.3Policy Dissemination4.4N

9、etwork Management4.5Network Control4AN IA Boundary4Dynamic Policy Based Security Management (PBSM)50.1PBSM Framework5.2Policy Protection5.3Security Management System5Data Protection5.1Application Layer Protection5.2Network Layer

10、Protection5.3Link Layer Protection5Key Management5Authentication System5ASWR5.1Network Intrusion Detection System5.2Virus Detection, Prevention, and Removal60.3Vulnerability Assessment System (VAS)600Protocol Security601Other Secur

11、ity Functions61.1Firewalls61.2Guards Cross Domain Solutions61.3Covert channels62Security Modeling and Simulation615.2.3Network Management6Cluster-Based Management Architecture6.1Network Manager6.2Cluster Managers6.3Intelligent NM Agents

12、6Policy Based Management Framework6Network Management System Components665.2.4Link Management6Link Management Architecture6Link Management System Components705.2.5Network Services7Overview7Name Resolution Service7.1Naming Service Features735.2.

13、5.2.2Naming Service Architecture7Dynamic Network Configuration Management7Network Time Service755.3Off-Board Transmission Systems766.GIG Integration and Interoperability786.1GIG Operational Mission Concepts786.1.1Provide Common Services796.1.2Provide Worldwide Access796.1.3Provide Dy

14、namic Resource Allocation796.1.4Provide Dynamic Group Formation806.1.5Provide Computer Network Defense (CND)806.1.6Provide Management and Control of GIG Network and Resources806.2GIG Enterprise Services816.2.1Enterprise Service Management/Network Operations816.2.2Information Assurance/Security816.3G

15、IG Transport Convergence836.4GIG Routing Architecture836.5GIG Quality of Service Architecture836.6Interface Definition858.Node and Link Configurations for Candidate Platform Types (SV-5)948.1Approach948.2Fighter Platform948.2.1Operational Profile948.2.2AN Capabilities, Links, and Topologies958.2.3AN

16、 System Configuration968.2.4Airborne Fighter Platform AN Issues and Risks978.3Airborne C4ISR Platform978.3.1Operational Profile978.3.2AN Capabilities, Links, and Topologies988.3.3AN System Configuration998.3.4C4ISR Platform AN Issues and Risks1008.4Airborne Communications Relay Platform1008.4.1Opera

17、tional Profile1008.4.2AN Capabilities, Links, and Topologies1018.4.3AN System Configuration1028.4.4Airborne Communications Relay Platform AN Issues and Risks1039.Recommended Network Standards1049.1Current Standards (TV-1)1049.2Emerging Standards (TV-2)1139.3Areas for Further Development12010.AN Arch

18、itecture Issues12911.List of Acronyms13612.References1401421.IntroductionThis document represents the work performed by the USAF Airborne Network Special Interest Group to define an Objective Airborne Network Architecture. Additional efforts are planned to further define this architecture. TBDs (to

19、be determined) inserted in the text indicate areas still being worked.1.1Definition of Airborne NetworkThe Airborne Network is defined to be an infrastructure that provides communication transport services through at least one node that is on a platform capable of flight. This can best be visualized

20、 in the context of the operating domains served by the Global Information Grid (GIG). The Transformational Communications Satellite System (TSAT) network will provide space connectivity and the GIG-Bandwidth Expansion (GIG-BE) network together with networks such as those provided under the Combat In

21、formation Transport System and Theater Deployable Communications will provide surface connectivity. Airborne connectivity within the GIG will be provided by the Airborne Network. The Airborne Network will connect to both the space and surface networks, making it an integral part of the communication

22、s fabric of the GIG.1.2Purpose of DocumentIn general, a network architecture defines a set of high-level design principles that guides the technical design of a network. Its role is to ensure that the resulting technical design will be consistent and coherent the pieces fit together smoothly and tha

23、t the design will satisfy the requirements on network function associated with the architecture. The architecture is more general than a particular conformant technical design, and is expected to be relatively long-lived applicable to more than one generation of technology. Finally, the architecture

24、 should guide technology development in a consistent direction, preventing the implementation of inconsistent point solutions throughout the network that could lead to the loss of functionality and interoperability. Source: Developing a Next-Generation Internet Architecture, July 2000The Airborne Ne

25、twork Architecture defines the structure of Airborne Network components, their relationships, and the principles and guidelines governing their design and evolution over time. It consists of the design tenets, technical standards, architectural views (system and technical) and a description of the o

26、perational capabilities achieved. The architecture is documented following the guidance of the DoD Architecture Framework. This document defines a “To-Be” or objective set of airborne network capabilities, functions and system components to be used to assist planning activities associated with the a

27、cquisition or implementation of a particular network capability. It should not be used on its own as an all-encompassing design for the Airborne Network.1.3Relationship to Other DocumentsThe following documents also provide acquisition or implementation planning details for the Airborne Network, and

28、 are related to this document as indicated: Airborne Network Architecture Progress Summary Version 1.0 Provides the scope, purpose, and intended uses of the Airborne Network Architecture, describes the process used to develop the architecture, and summarizes the major results and conclusions. Airbor

29、ne Network Architecture Roadmap (Draft) Provides a time phased approach for implementing the Airborne Network capabilities and network functions. Airborne Network Technical Requirements Document (Draft) Provides detailed technical requirements for system components needed to implement the Airborne N

30、etwork. ConstellationNet Addendum to C2 Constellation CONOPS Provides the required operational capabilities of the ConstellationNet of which the Airborne Network is a component. USAF ConstellationNet Sub-Enterprise Architecture (formerly known as the AF Infostructure Architecture) Provides context a

31、nd overall guidance for domain level architectures for implementing a net-centric infostructure. Includes operational, system, and technical views of the Air Force information infrastructure (to include the Airborne Network) at the Enterprise level. Command and Control Enterprise Reference Architect

32、ure (C2ERA) Provides the technical direction for designing, acquiring and integrating the computing and communications capabilities of the Air Force C2 Enterprise. Net-Centric Enterprise Solutions for Interoperability (NESI) Provides a technical architecture and implementation guidance to facilitate

33、 the design, development, maintenance, evolution, and usage of information systems that support the Network-Centric Warfare (NCW) environment. 1.4ContentsThe Airborne Network Architecture is documented in terms of the following perspectives: Operational Context Objective communications capabilities

34、that the Airborne Network must provide to the warfighter to support future network-centric operations are described in Section 2. Tenets Network principles applicable to any Airborne Network design that provide high level guidance for decision making are contained in Section 3. Systems Architecture

35、Views Guidelines for where and when to implement different system functions or technologies are contained in Sections 4 through 7. Section 4 describes the objective Airborne Network functions and topologies; Section 5 identifies the systems components needed to provide those functions; Section 6 dis

36、cusses implications of integrating the Airborne Network into the future Global Information Grid (GIG); Section 7 contains several model diagrams for the network and platforms; and Section 8 presents notional system configurations for several candidate platform types. Technical Standards Technical st

37、andards for major Airborne Network components and interfaces, both existing and emerging, are listed in Section 9. Issues Architectural and technical issues identified during the development of the architecture that require further research are presented in Section 10.1.5Intended Use The Airborne Ne

38、twork Architecture is intended to guide the acquisition of network capability for airborne platforms by defining investment opportunities, system requirements, technical standards, implementation guidelines, and GIG interoperability directives. Investment Decisions The Airborne Network Architecture

39、identifies functional areas requiring further investigation and development to define technical solutions and/or standards. Requirements Definition The Airborne Network Architecture provides a common framework to identify required network, platform, and communications component functionality to enab

40、le a desired set of network capabilities needed to support future Air Force mission operations. Standards Definition The Airborne Network Architecture provides a list of key technical standards for use in near-term and interim airborne network implementations. Implementation Guidance The Airborne Ne

41、twork Architecture provides a list of tenets and system configuration diagrams that should be used to guide the development of lower level system architectures and system designs. GIG Interoperability Direction The Airborne Network Architecture identifies GIG interoperability directives and architec

42、tural guidance relevant to the airborne network 2.Operational Context 2.1Operational Concept Description for the Airborne Network (OV-1)Network-centric operations and network-centric warfare (NCW) refers to an information superiority-enabled concept of operations that generates increased combat powe

43、r and air mobility by networking sensors, decision makers, and shooters to achieve shared awareness, increased speed of command, higher tempo of operations, greater lethality, increased survivability, and a degree of self synchronization. In essence, NCW translates information superiority into comba

44、t power by effectively linking knowledgeable entities in the battlespace. Source: Network Centric Warfare, Alberts, Gartska and Stein, 1999The Department of Defense (DoD) Joint Vision (JV) 2020 projects to a future period of United States dominance across the full spectrum of military operations. Th

45、e military capabilities necessary to realize this vision depend upon achieving Information and Decision Superiority through the implementation of an internet-like, assured Global Information Grid (GIG). Within the AF, achieving Information and Decision Superiority depends upon extending the capabili

46、ties of the GIG into the airborne and space environments. When fully realized, this AF vision will enable interoperable network-centric operations between Joint Service, Allied, and Coalition forces. Source: Airborne Network Prioritization PlanTo realize the AF vision, the extension of the GIG in th

47、e airborne domain the Airborne Network, must be easy to use, configure, and maintain and must provide: Ubiquitous and assured network access to all Air Force platforms GIG core services whose integrity is assured Quality appropriate to the commanders intent and rules of engagement (ROE) Rapid respon

48、se to mission growth, emerging events and changing mission priorities End-to-end interoperation with joint services, coalition, and non-DoD partners and legacy systems in all physical network domains (sub-surface, surface, airborne and space)Source: Operating Concept for C2 Constellation ControlNet

49、Network Centric Infostructure2.2Objective Airborne Network Communications CapabilitiesThe Objective Airborne Network that can provide the capabilities listed in section 2.1 will be a communications utility that provides an adaptable set of communications capabilities that can be matched to the parti

50、cular mission, platforms, and communications transport needs. Communications capabilities can be expressed in terms of the connectivity that can be established, the services that can be supported over the network connections, and the operations that are required for the user to establish, maintain,

51、and access the network connections. Table 2-1 identifies an objective set of communications capabilities for the Airborne Network. All of these capabilities would not necessarily be needed for every instantiation of the Airborne Network, but will be necessary to support all missions, operations, and

52、 platforms.Table 2-1. Summary of Airborne Network Objective CapabilitiesNetwork Capability & AttributesAirborne Network Objective CapabilitiesConnectivityCoverageGeographic span of links directly interfacing to a subject node Beyond Line of Sight (BLOS) extending Globally (enabling access to anywher

53、e from anywhere)Diversity of linksTotal number and types of links that can be used to “connect” to the subject node Number of links (system and media) matched to the mission matched to the environment (to enable guaranteed access) Type of links extend across the spectrum of radio frequencies includi

54、ng infrared and opticalThroughputTotal average throughput of all links directly interfacing to the subject node Throughput matched to the mission and automatically adaptable to accommodate unplanned or transient conditions Dynamically reconfigurable to optimize performance, cost, and mission effecti

55、venessType of connectionNature of connections that can be established between the subject nodes and directly connected nodes Flexible connections able to forward GloballyNetwork interfaceNetworks that can be directly interfaced from the subject node (e.g., DISN (NIPRNET, SIPRNET, JWICS), Transformat

56、ional Communications, TDL Networks, CDL Networks) Interface to AN subnet and backbone links, as well as, legacy (i.e., TDL or CDL), coalition and GIG component networks operating any version network protocol (i.e., IPv6 or IPv4), as neededServicesReal-time dataAny data flows that must be sent in real time (i.e., low latency) with assured delivery (e.g., AMTI or GMTI tracks, munition terminal stage updates, RPV control, TCT&ISR tipoffs, NBC alert) Multiple simultaneous multilevel precedence and preemption (MLPP) real-time data