Mobile Communication Network Architecture (MCNA) Architecture Report (A040) DOCUMENT NUMBER: RELEASE/REVISION: RELEASE/REVISION DATE: D794-10184-1 Rev A 7/25/2005 Export Compliance Notice This document has been reviewed and approved for release to ALL by Export Compliance. Log ID: PW-05-193 Review Date: 10/18/05 Additional questions should be addressed to your designated Boeing Export Compliance Administrator. Richard M. Kling, 206-679-9284 CONTENT OWNER: GCNSS Systems Engineering Team Phantom Works ANCO (9S-7S-73CN) All future revisions to this document must be approved by the content owner before release. Document Information Document Type Original Release Date Contract Number (if required) Informal 3/10/2005 XX Preparing Organization (if different from owning organization) Hardware and Software Used XX IBM PC Microsoft Word Location of Software Files (optional) Boeing Web URL (optional) Notes and Limitations (optional) Signatures for original release AUTHOR: Al Sipe Sign and type: First Name MI Last Name Org. Number Date APPROVAL: John W. Moore Sign and type: First Name MI Last Name Org. Number Date DOCUMENT RELEASE: Sign and type: First Name MI Last Name Org. Number Date REV A ii Table of Contents 1 INTRODUCTION...............................................................................................................1 1.1 MCNA Overview...................................................................................................1 1.2 Purpose and Scope.................................................................................................3 1.3 Systems Engineering (SE) Process........................................................................4 1.4 Document Roadmap...............................................................................................6 2 MCNA COMMUNICATION LINK CANDIDATES........................................................7 2.1 Scope......................................................................................................................7 2.2 Candidate Links Table...........................................................................................7 2.3 Air-Ground Communication Systems..................................................................13 2.4 Satellite Communications Systems......................................................................17 2.5 Air-Air Communication Systems.........................................................................19 2.6 Airport Communication Systems.........................................................................22 2.7 Spectrum Considerations.....................................................................................23 3 MCNA NETWORK ARCHITECTURE...........................................................................26 3.1 MCNA Context and Relationship with SWIM....................................................26 3.2 Networking Technology Introduction..................................................................34 3.3 Routing.................................................................................................................36 3.4 Mobility [7]..........................................................................................................47 3.5 Multihoming [7]...................................................................................................52 3.6 Policy Based Routing [7].....................................................................................56 3.7 Multicast [7].........................................................................................................57 3.8 Quality of Service................................................................................................60 3.9 Security................................................................................................................65 3.10 Network Management..........................................................................................70 3.11 Network Protocol Accommodation......................................................................71 4 MCNA AVIONICS ARCHITECTURE............................................................................74 4.1 Introduction..........................................................................................................74 4.2 Avionics Starting Points.......................................................................................74 4.3 Vision State Avionics Architecture......................................................................80 4.4 Avionics Transition Concepts..............................................................................89 4.5 Standardization.....................................................................................................95 5 Mapping to Requirements..................................................................................................97 5.1 Functional Requirements.....................................................................................97 5.2 Performance Requirements................................................................................101 6 Traceability to NAS Shortcomings and Proposed Operational Enhancements from GCNSS I..........................................................................................................................103 REV A iii 7 CONCLUSIONS & RECOMMENDATIONS...............................................................108 8 REFERENCES................................................................................................................110 9 ACRONYMS..................................................................................................................113 REV A iv List of Figures Figure 1: Relationship of MCNA to SWIM and NCO...................................................2 Figure 2 Notional Physical Architecture for MCNA......................................................4 Figure 3 Architecture Definition within the FAA SE Process........................................5 Figure 4 MCNA System of Systems View.....................................................................8 Figure 5 SWIM Context Diagram.................................................................................27 Figure 6 MCNA Context Diagram...............................................................................28 Figure 7 SWIM Reference Architecture.......................................................................29 Figure 8 SWIM Configuration Alternatives.................................................................30 Figure 9 MCNA Scope.................................................................................................31 Figure 10 Implementation Options for Extending the SWIM to the Aircraft Using MCNA..........................................................................................................32 Figure 11 The ATN/CLNP Address.............................................................................38 Figure 12 Address Assignment Hierarchies.................................................................43 Figure 13 Generic Hierarchical Network Topology.....................................................45 Figure 14 Link Layer Mobility.....................................................................................49 Figure 15 Network Layer Mobility...............................................................................49 Figure 16 Application Layer Mobility..........................................................................51 Figure 17 IP-based Aircraft LAN Security Architecture..............................................68 Figure 14 Current Federated Audio Communications Architecture............................75 Figure 15 Current Federated Data Communication Architecture.................................76 Figure 16 Integrated Avionics Architecture................................................................77 Figure 17 ADN Domain Architecture..........................................................................79 Figure 18 Vision State Avionics Architecture.............................................................82 Figure 19 Cabin Information Network Architecture per AEEC...................................90 Figure 20 CMU Centric ACD Architecture for CNS/ATM Adaptation.......................91 Figure 21 FMS-based ATN Implementation Alternatives...........................................91 Figure 22 Data Link Protocol Transition Architecture.................................................92 Figure 23 Avionics Transition to SWIM Services.......................................................93 Figure 28 MCNA Functional Analysis.........................................................................97 Figure 29 Mapping 1.0 Sub-Functions to the Communications Services....................98 Figure 30 Allocations of 1.0 Functions to Architecture Elements..............................100 Figure 31 Allocations of 2.0 Sub-functions to Architecture Elements.......................101 Figure 32 MCNA Accommodation of GCNSS I Shortfall Number 1........................103 Figure 33 MCNA Accommodation of GCNSS I Shortfall Number 2........................104 Figure 34 MCNA Accommodation of GCNSS I Shortfalls Number 3 & 4...............105 Figure 35 MCNA Accommodation of GCNSS I Shortfalls Number 5 & 6...............106 Figure 36 MCNA Accommodation of GCNSS I Shortfall Number 7........................107 REV A v List of Tables Table 1 MCNA Architecture Elements..........................................................................3 Table 2 Candidate Links Table....................................................................................12 Table 3 Network Addressing Comparison...................................................................37 Table 4 IPv6 Address Heirarchy..................................................................................43 Table 5 Network Topology Comparison......................................................................46 Table 6 Mobility Comparison......................................................................................48 Table 7 Multihoming Comparison...............................................................................53 Table 8 Policy-Based Routing Comparison.................................................................56 Table 9 Multicast Comparison.....................................................................................58 Table 10 QoS Comparison...........................................................................................64 Table 11 Security Comparison.....................................................................................66 Table 12 Examples of Aircraft Configurations Supporting Multiple Network Protocols.................................................................................................................72 Table 13 Accommodation between Network Protocols...............................................73 REV A vi 1 INTRODUCTION 1.1 MCNA Overview The Mobile Communication Network Architecture (MCNA) encompasses the aggregate of all air-ground (A-G) and air-air (A-A) voice, video and data communication capabilities in support of communications, navigation and surveillance (CNS) services for Air Traffic Management (ATM) operations. MCNA is specifically concerned with the support of Air Traffic Safety (ATS) and Airline Operational Communications (AOC) services, but nature of MCNA should provide for common infrastructure to also support Airline Administrative Communications (AAC) and Airline Passenger Communication (APC) services. Like System Wide Information Management (SWIM), MCNA is a key enabling technology for transformation of the National Airspace System (NAS) towards Network Centric Operations (NCO). The MCNA effort represents a System of Systems Engineering (SoSE) based evaluation of MCNA. The specific focus of this effort is the development of the requirements, architecture and associated transition plan necessary to assure that the air-ground and air-air communications capabilities will support of the needs of SWIM-enabled applications (SEA) to provide NCO. The goal of this effort is to develop an integrated SoSE approach and technology development roadmap that will provide guidance for ongoing and planned NASA Glenn Research Center (GRC) and FAA research activities including NASA GRC’s Advanced CNS Architectures and System Technologies (ACAST) Project and NASA Airspace Systems Program’s proposed initiative for the Transformation of the NAS (TNAS). The MCNA nomenclature was introduced within the Statement of Work (SOW) of this GCNSS II contract task. As such, it is a common misconception that MCNA refers solely to the “vision” of mobile communications capabilities intended to support the most demanding SWIM-enabled applications including cockpit integration. In fact, all communications to mobile networks in the NAS, such as1090 Extended Squitter (ES), Aeronautical Communications Addressing and Reporting System (ACARS) and Future Air Navigation System (FANS) are all existing components of the MCNA. In time, these components will likely be augmented by Aeronautical Telecommunications Network (ATN) over Very High Frequency (VHF) Digital Link Mode 2 (VDLm2) and VDLm3, Universal Access Transceiver (UAT) and broadband satellite communications (SatCom). Eventually, the NAS will be supported by the suite of enhanced datalink services recommended by the Future Communication System (FCS). The key aspect of MCNA is that it extends voice and data communications to the aircraft during all phases of flight. Figure 1 illustrates how MCNA fits in the Common Data Transport (CDT) portion of the SWIM and thereby supports NCO. REV A 1 HHHuuummmaaannn---IIInnnttteeerrrfffaaaccceee AAAppppppllliiicccaaatttiiiooonnnsss DDDooommmaaaiiinnn SSSpppeeeccciiifffiiiccc AAAppppppllliiicccaaatttiiiooonnnsss NNNCCCOOO AAAAiiiirrrrssssppppaaaacccceeee FFFFlllloooowwww TTTTrrrraaaaffffffffiiiicccc SSSSeeeeppppaaaarrrraaaattttiiiioooonnnn SSSSeeeeccccuuuurrrriiiittttyyyy LLLLeeeeggggaaaaccccyyyy AAAApppppppplllliiiiccccaaaattttiiiioooonnnnssss SSSuuuppppppooorrrttt aaappppppllliiicccaaatttiiiooonnnsss SSSuuurrrvvveeeiiillllllaaannnccceee,,, AAAIIIMMM,,, WWWeeeaaattthhheeerrr,,, FFFllliiiggghhhttt ooobbbjjjeeeccctttsss,,, ......... CCCIIIMMM CCCooommmmmmooonnn IIIInnnnffffoooorrrrmmmmaaaattttiiiioooonnnn CCCCoooorrrreeee IIInnnfffooorrrmmmaaatttiiiooonnn MMMgggttt SSSWWWIIIMMM AAArrrccchhhiiittteeeccctttuuurrreee IIIIPPPP CCCCoooommmmmmmmuuuunnnniiiiccccaaaattttiiiioooonnnnssss CCCDDDTTT AAAApppppppplllliiiiccccaaaattttiiiioooonnnnssss CCCooommmmmmooonnn LLLeeegggaaacccyyy DDDaaatttaaa MMCCNNAA CCCooommmmmm TTTrrraaannnssspppooorrrttt CCCCoooommmmmmmmuuuunnnniiiiccccaaaattttiiiioooonnnnssss CCCCoooorrrreeee Figure 1: Relationship of MCNA to SWIM and NCO. While the goal of MCNA is to extend the reach of SWIM information nodes to all mobile elements of the NAS, this does not mean, even in the MCNA long-term vision state, that all communications to and from the aircraft will use SWIM as the means of information exchange. Basically, SWIM will enable the ubiquitous sharing of information between applications. The sharing of information is a result of integrating applications via common mechanisms. SWIM will support multiple integration frameworks (i.e., .NET, J2EE, CORBA, Web Services) and platforms (i.e., Windows, Linux, etc.) for flexibility and evolutionary reasons. The SWIM environment will enable both anticipated and non-anticipated users of information, with anticipated users defined primarily at build-time and unanticipated users defined primarily at run-time. But the fact that the SWIM environment will support and even promote ubiquitous information sharing doesn't mean that all applications should exchange all information with all other applications. Only authenticated and authorized users of information will be allowed to access it, as determined by the "owner" of the information source. In early SWIM development and deployment spirals, a wide variety of existing information exchange mechanisms and associated communications links will continue to coexist alongside the new SWIM mechanisms. This will be done for both reliability/availability and backwards compatibility reasons. In some cases, it may make sense to retain information exchange mechanisms outside of SWIM beyond the initial spirals. The desirability of these out-of-band information exchange mechanisms will, in general, be greater for application groups that are tightly coupled, synchronous, unlikely to change and unlikely to be expanded. But this decision will be decided on a case-by- case basis and will require a thorough analysis. In most instances the information exchange mechanisms offered by SWIM will be sufficient. REV A 2 1.2 Purpose and Scope The sub task of the MCNA effort documented in this report is the development of an architecture that integrates current and future A-G and A-A communication links into a system-of-systems communication network. Special attention is given to the disparate networking protocols and link technologies that must by integrated by this architecture to provide communication services that can meet more stringent performance requirements than any individual A-G or A-A communication link. The MCNA physical architecture is composed of the following elements which are notionally depicted in Table 1 and Figure 2. As can be seen from the notional physical architecture, the MCNA is specifically concerned with addressing issues related to the integration of multiple disparate radio links and networking protocols. Furthermore, the MCNA architecture is concerned with seamless integration into the SWIM concept. Table 1 MCNA Architecture Elements Airborne Architecture Elements Terrestrial Architecture Elements Airborne host Terrestrial host Airborne router Terrestrial router Airborne message router Terrestrial message router Airborne gateway Terrestrial gateway Airborne modem/radio Terrestrial ground station Airborne firewall Network Operations Control Center (NOCC) Domain Name Server (DNS) This task focuses on three key elements of the MCNA architecture: candidate A-G and A-A links, network architecture and the avionics architectures that comprise the aircraft portion of the other two components. Initially, the candidate links are summarized and compared. With this perspective, a proposed MCNA network architecture is defined. Specific consideration is provided for those elements of the MCNA network architecture required to extend SWIM to/from the aircraft to support NCO. The dependencies between the avionics architecture and the MCNA network architecture are described. The avionics architecture includes discussion of the avionics transition as this is one of the most critical aspects to address when considering avionics issues. Finally, the architecture is mapped to the requirements and discussion is provided regarding the ability of the MCNA architecture to address NAS shortcomings defined during the previous phase of the GCNSS contract. REV A 3 Aircraft Aircraft Network #1 Aircraft Network #1 Aircraft HHoosstt Network #2 Network #2 FFiirreewwaallll FFiirreewwaallll HHoosstt GGaatteewwaayy RRoouutteerr RRoouutteerr MMeessssaaggee RRoouutteerr Modem/Radio 1 Modem/Radio 2 Modem/Radio 3 RRoouutteerr GGrroouunndd SSttaattiioonn ##11 RRoouutteerr GGrroouunndd SSttaattiioonn ##22 Gateway Gateway Ground NeGtGwroroourunknd #d 1 NOCC NNeteGwtwrooorukrn k#d 2# 2 Network #1 SWIM CDT DNS SWIM CDT MMeessssaaggee RRoouutteerr HHoosstt Figure 2 Notional Physical Architecture for MCNA 1.3 Systems Engineering (SE) Process One view of the applicability of architecture definition activities in the development process is shown in Figure 3. Here, the system development process, as defined in the FAA Systems Engineering Manual (SEM), is used as a reference. The arrow in the figure points out where architecture definition supports the development process. Architecture definition is one of the preliminary steps in the SE task defined as synthesis within the FAA SEM. The MCNA effort was not intended to produce a comprehensive set of systems engineering products so much as to conduct a high level, broad scope survey of the MCNA concept with the intention of identifying key targets of opportunity for targeted research. As such, this architecture report does not claim to represent a complete MCNA architecture but rather facets of such and architecture and key considerations when pursuing a more detailed architectural MCNA study. The candidate link evaluation effort reviewed the results from the FCS technology prescreening and adapted those results to include existing candidate links and additional evaluation criteria from a SoSE perspective such as networking protocols and interoperability considerations at multiple REV A 4