Safety Services Using the Internet Protocol Suite

Transcription

1 ACSICG/3 IP/6 Agenda Item 7 03/05/16 Engineering, Operations & Technology Boeing Research & Technology Airspace & Operational Efficiency Safety Services Using the Internet Protocol Suite Greg Saccone, Mike Matyas

2 Boeing IPS Approach Refresher Boeing (and Honeywell and others) helped to define initial IPS standards via ICAO to address limitations and provide future technology path Doc 9896 (IPS) provides initial technical provisions for application support over TCP/UDP and IP Also supports legacy ACARS applications (AOC messaging, FANS-1/A) Ground rule is to have no changes to the existing applications (e.g. LINK2000+ CPDLC) while moving away from ACARS and OSI-based protocols Avoids having to re-do flight decks, aircraft applications Removes dependency on applications from ATN protocols Creates a logical transition path to future IP-based communication links Can support AOC, FANS-1/A, LINK2000+ and B2 applications Can provide a common security framework (e.g. IPSec) Now is the time to take this further 2

3 IPS Protocol Transition 3

4 Boeing Honeywell Activities Boeing Research & Technology and Honeywell Advanced Technology started a Joint Research Project based around identified common interests Determining implementation constraints of IPS How it would work in current aircraft architectures Prototyping IPS using realistic hardware Testing in live communication environments (SATCOM, VDLM2) Lots of areas for further definition/investigation: Routing Mobility Performance characterizations Transport protocol selection Security ATN IPS interoperability and transition Plus many more 4

5 Boeing Honeywell Inmarsat SITA Activities Update Honeywell provided Boeing with a prototype IPS CMU Honeywell Mk II+ CMU with updated software (standard CMU form factor) ICAO Doc 9896 compliant, including both TCP and UDP capabilities Also provided IPS ground end system for additional testing INMARSAT provided access to SwiftBroadband in order to test over a representative subnetwork Non-safety services channel, Ethernet interface to SDU Service provision from Boeing Field SITA provided VDLM2 Link Required protocol modifications jointly defined by all (air, ground side) IPS prototype VHF Ground Station (VGS) at Boeing Field Boeing provided the test facilities Boeing 737 avionics test rack at Boeing Integrated Aircraft Systems Laboratory (IASL) at Boeing Field, with SDU/VHF connections Boeing internally developed IPS ground end system (extended from ACAT ATN/FANS/AOC datalink test tool), ICAO Doc 9896 compliant 5

6 Boeing Honeywell Inmarsat SITA Activities Update Initial application-level compatibility proven with Honeywell prototype IPS CMU Tested in a standard Boeing 737 avionics bench at IASL No changes to ATS functionality from the flight crew and avionics perspective 6

7 Boeing Honeywell Inmarsat SITA Activities Update Successful demonstration of LINK2000+ message exchange using IPS (TCP) over SwiftBroadband CM and CPDLC messages exchanged between prototype Honeywell IPS CMU and prototype Boeing ground system Successful demonstration of LINK2000+ message exchange using IPS (UDP) over VDLM2 CM and CPDLC message exchanged using back-back connection with RF attenuator and over-the-air using operational VDLM2 frequency Continued work in 2016 Prototype CMU updates Performance characterization for IPS over VDLM2 More in-depth SATCOM testing Ground gateway requirements Flight trials via Honeywell demonstration aircraft 7

8 Guiding Principles for Migration to Future Comm (network/subnetwork level) Move from OSI to IPS and broadband IP Support ACARS (FANS and AOC) traffic Be a single stack, with media management in-line with FANS-1/A (i.e. allow multiple subnets, and not tied to one particular vendor implementation) Have minimal impacts on avionics, at a minimum in terms of application impact, multiple LRU changes, hardware additions Be based on stated and validated performance requirement needs Be a true transition towards the end state IPS, not an interim short term throw away step Be applicable globally Provide flexible and globally interoperable security mechanisms Make maximum use of COTS Have a positive business case for the customer airlines and ANSPs Domestic and Oceanic environments Preserve current investments in ground and aircraft assets Move routing complexities and gateway functionalities to the ground 8

9 Boeing IPS Viewpoint Boeing would rather go directly to IPS than do additional, complicated interim steps that will delay further IP development Understand and solve current European ATN issues first (ELSA) rather than introduce additional complexity and cost Concerns from vendors about cost/complexity of extending OSI to SATCOM Looking at mid-2020s for IPS capability and planning development accordingly No need for interim solution prior to then; schedule and technology realities of LINK2000+ in Europe (2018 for ground, 2020 for aircraft), FANS-1/A in US through mid-2020s Pushing a new solution prior to then jeopardizes all of Data Comm FAA has no current plans to implement OSI Work towards AOC, FANS-1/A, LINK2000+/B2 programs with IPS Define transition strategies (e.g. Gateway) Working towards a converged industry roadmap 9

10 IPS Transition IPS and OSI can coexist, although ground accommodation will likely need to be done Application and network already separated Interoperability manageable by ground gateways FANS-1/A and ATN gateways used today in Europe For IPS and OSI gateway, application data remains the same regardless of the network protocol so it s more straight-forward than FANS-1/A and ATN gateways Provides a transition path for both air and ground Supports all types of aircraft within a given technology environment IPS can also support ACARS-type messaging (AOC and FANS- 1/A) 10

11 ATN/IPS Gateway Transition Key features: Legacy SATCOMM Application data untouched important for cert Correlation of IPS OSI peer systems FANS-1/A Support Simplified addressing for OSI Takes advantage of IP networks IP SATCOMM B1 - OSI Aircraft VDLM2 VDL0, VDLM2 FANS Aircraft FANS - IPS Aircraft VDLM2, Other VDL, AeroMACS (surface) B2 - IPS Aircraft IPS Gateway Protocol Conversion and flight correlation ANSP CSP ULCS FastByte TP4 CLNP ARINC 620 TCP IP IP DS TCP/UDP IP CSP ANSP 11

12 Datalink Roadmap (Boeing Vision) VHF Voice VHF Data/VDLM2 HF Satcom Data 2??? Legacy Comm means 2016 AeroMACS 2017 Iridium NEXT 2030? LDACS 2016 Inmarsat SBB/IRIS Precursor 2028 Iris Future Comm means ACARS? ATN (Europe) IPS 2019 Standards Available ~2024 IOC? Airborne ATS Router Still being worked between Boeing and Airbus and other stakeholders 12

13 Boeing s Plan for NextGen and SESAR > Forward Fit Retrofit Forward Fit Retrofit FANS-1 FANS-1 FANS-2 FANS-2 FANS-3 FANS-3 FANS-1 FANS-1 + LINK2000+ FANS-2 FANS-3 FANS-1 FANS-1 + LINK2000+ FANS-3 Forward Fit 747 FANS-1 FANS-2 FANS-3 Retrofit FANS Forward Fit Retrofit FANS-1 FANS-1 757/767 EU Domestic OPS Forward Fit Retrofit CMU LINK2000+ CMU LINK2000+ Notes: 1. FANS-1 and CMU LINK2000+ are mutually exclusive. Only one can be installed/enabled due to differences in HMI and host system. 2. FANS-2 (integrated) is FANS-1 + LINK FANS-3 (integrated) is FANS-1 + B will not have integrated LINK LINK2000+ does not support integration will have FANS 2. 13

14 > EU Domestic OPS Forward Fit Retrofit CMU LINK2000+ CMU LINK2000+ FANS-3 Forward Fit 737 FANS-1 FANS-2 FANS-3 Retrofit FANS MD90 MD10 MD11 Forward Fit Retrofit FANS-1 Notes: 1. FANS-1 and CMU LINK2000+ are mutually exclusive. Only one can be installed/enabled due to differences in HMI and host system. 2. FANS-2 (integrated) is FANS-1 + LINK FANS-3 (integrated) is FANS-1 + B2 4. Most 737 customers have selected non-integrated CMU LINK

15 IPS Next Steps Keep to Proposed Schedules Current data comm implementation programs are critical to successfully complete (FAA Segment 1, European LINK2000+) AEEC Roadmap activity leading to the start of standards work Continue working high-risk areas via R&D and industry collaboration Coordinate with other relevant projects E.g. Iris Service Evolution project, FAA, EUROCONTROL, etc Work with stakeholders to define data comm harmonization roadmap Data comm deployment plans for FAA, Europe and Others, including application and network levels Work through AEEC, ICAO, RTCA to define specifications Input from all of the above into specifications 15

16 Infrastructure: Existing Networks ACARS and ATN Avionics Air/Ground Comms. Ground Networks Ground Users Application Sets SATCOM Airline Operations Narrowband Communications ACARS HF Airline Operations Comm. (AOC) Airline Administrative Comm. (AAC) VHF Air Traffic Control VHF ATN / OSI Future Air Navigation System (FANS) Air Traffic Services (ATS) ATN Link2000+ ATS (current) Baseline2 (future) Aircraft Communications Addressing and Reporting System (ACARS) Character-oriented, in use since late 1970s Defined by ARINC Specifications 618 and 620 Aeronautical Telecommunications Network (ATN) Based on Open Systems Interconnection (OSI) reference model Bit-oriented, in use since early 2000s Defined by ICAO Doc 9705 and Doc

17 ATN and ACARS Situation Boeing, Honeywell and many others have recognized ATN and ACARS limitations ATN technical issues in Europe Continued concerns about ATN complexity and overhead Continued resource spend on ATN deployment/fixes/maintenance ATN protocol for ATS use only, no business case for ATN AOC ATN and ACARS not conducive to future broadband communication services Lack of beyond line of sight network for ATN, no multiple subnet capability currently implemented Security provisions are TBD for ATN and ACARS Obsolescence of ATN and ACARS, de facto standard of IP-based technology 17

18 End-to-end Testing Setup for Inmarsat SwiftBroadband 18

19 End-to-end Testing Setup for SITA VDLM2 SITA (Montreal, QC) Remote VGS Config Boeing 737 ACARS bench Boeing Integrated Aircraft Systems Laboratory (Seattle, WA) Honeywell ATN/IPS CMU Internet Fin Antenna Firewall RF Cable Boeing Development ATN/IPS End System Local LAN VDLM2 SITA Rhode & Schwarz Radio Gateway VHF Rx VHF Tx RF Cable Fin Antenna Boeing Airspace and Operational Efficiency Laboratory (Kent, WA) VGS Controller 19

20 Envisaged Boeing IPS Architecture Work to be Done EFB Display CMC/ ACMF Cabin Systems FMS AOC/ATC Unaffected Components Future Comm Components Changed/New Air Components CMF Router Logic, Media management (High Level) Comm Management Media Routing Logic ACARS Over IP AOC Dialog Service Interfaces ACARS/IP Profile Changed/New Gnd Components Red Text/Lines: areas to be defined Air Ground ACARS Logic ATN Logic HF SDU VDR SBB/Iridium NEXT/Other IP Logic AeroMACS Network Profiles/ Specification, mobility Network interfaces (coordinated with relevant groups) LDACS Ground Accommodation Comm Service Provider ANSPs, AOCs 20

21 IPS-over-VDLm2 Protocol Detail [2/2] 21 VDLm2 supports Connection Oriented Protocol used in the existing ATN/OSI framework: The protocol stack is composed of AVLC/8208/M-SNDCF/CLNP/TP4 complemented by a VME/LME Link Management Layer (XID messages) VDLm2 also support a Connectionless Data Transfer capability using Unnumbered Information (UI) Frames. With the existing ATN/VDLM2 protocol overhead statistics in mind, the use of Datagram as a general principle, and UI frames in particular, was selected as a design objective for IPS-over- VDLM2. By modifying AVLC and VME and removing 8208 and VME/LME from the protocol stack, the overhead from XID exchanges, typical AVLC RRs, and 8208 Call Request/Confirms is eliminated Some expected benefits are: Reduction of overhead in general, and increase of RF efficiency Receipt of downlink by multiple receivers (thanks to multicast addressing), leading to increased downlink success rate For uplinks, offers the service provider the option to switch ground stations if the current station is experiencing problems delivering uplinks 21

22 IPS-over-VDLm2 End-to-end Protocol Diagram 22 Avionics VDLm2 Ground System ATN End System CMU VDR Ground Station G-G Router Ground ES ATN Applications ATN Applications IPS Dialog Service ATNPKT IPS Dialog Service UDP UDP SN- SME VDR Controller IP Layer -to- VDLM2 Adapter (IVA) VME IP ASIP AVLC Williamsburg Version 3 ARINC 429 VDLm2 IP Packet ASIP Williamsburg Version 3 ARINC 429 MAC Interface VDLM2 MAC CSMA PHY D8PSK IP Datalink Interface VME AVLC L2 VDLM2 MAC CSMA PHY D8PSK L1 L2 L1 IP L2 L1 IP L2 L1 Legend: Not Modified Modified New Prior 2014 Effort VDLm2 Datalink 22

23 IPS-over-VDLm2 Protocol Detail [1/2] 23 ATN Applications (CM, CPDLC) DS App Data App Data IPS Dialog Service Per Doc UDP Per Doc IP Per ISO 9577, an Initial Protocol Identifier (IPI) with the value 0xCC specifies a frame containing an IP packet IP UDP UDP maps to ATNPKT ATNPKT ATNPKT AVLC F A C IP UDP VDLm2 IP Packet ATNPKT Control = Un-numbered Information (UI) Frame FCS Address DL (source = aircraft; destination = CSP broadcast address) UL (source = CSP ground station; destination = aircraft) Start/End Flag = F Frame Check Sequence 23