15 December 2014 Boeing ATNIPS Aeronautical Telecommunications NetworkInternet Protocol Suite Activities ATN Aeronautical Telecommunications Network Originally intended to replace ACARS as an ICAO compliant network ID: 774886
Download Presentation The PPT/PDF document " Greg Saccone ICAO Communications Panel" is the property of its rightful owner. Permission is granted to download and print the materials on this web site for personal, non-commercial use only, and to display it on your personal computer provided you do not modify the materials and that you retain all copyright notices contained in the materials. By downloading content from our website, you accept the terms of this agreement.
Slide1
Greg SacconeICAO Communications Panel1-5 December 2014
Boeing ATN/IPS (Aeronautical Telecommunications Network/Internet Protocol Suite) Activities
Slide2ATN: Aeronautical Telecommunications NetworkOriginally intended to replace ACARS as an “ICAO compliant network”OSI: Open Systems InterconnectionGeneric data communications framework based on a 7-layer protocol architecture (‘stack’)Each layer has a specific set of functionsData presentation, physical medium access, connection management, etc.Limited COTS availability, not widely usedIPS: Internet Protocol SuiteFramework based on a 4-layer protocol stackEach layer has a specific set of functionsThe protocol of the Internet, widely used COTS
Definitions (1)
Slide3ATN/OSIDefined in ICAO Doc 9705 and Doc 9880OSI-based ATN used for LINK 2000+ programAlso refers to a specific selection of standard and custom specifications for each protocol layer for aviation useATN/IPSIdentified as future ATS/AOC protocol by FAA, SESAR, ICAOSupports Voice over IP (VoIP)Defined in ICAO Doc 9896Also refers to a specific selection of standard specifications for each protocol layer for aviation useSpecifies a Dialog Service as intermediary between LINK 2000+ and Baseline 2 (B2) applications and IPSAllows applications to remain unchanged while using IPSSupports ACARS (e.g., AOC and FANS) applications as well
Definitions (2)
Slide4Current ATN/OSI situationLack of beyond line of sight network, no multiple subnet capability currently implementedATN/OSI technical issues in EuropeSecurity provisions are TBDResource spend on ATN/OSI development/fixes/maintenanceContinued concerns about ATN/OSI complexityProtocol for ATS use only, no business case for ATN/OSI AOCOSI unable to support future IP applications and requirements (more data, moving towards simplified/unified aircraft architectures, need for broadband)Obsolescence of OSI, defacto standard of IP-based technology
How to leverage work already done without re-inventing the ATS applications, and be able to take advantage of other communication protocols without being tied to legacy OSI?
ATN/IPS Concept Need
Slide5Boeing and many others have recognized these ATN/OSI limitationsBoeing helped to define ATN/IPS standards via ICAO (Doc 9896) to mitigate these limitations and provide future technology pathATN/IPS provides initial technical provisions for application support over TCP/UDP and IPAlso supports legacy ACARS applications (AOC messaging, FANS-1/A)Rudimentary specifications at the network level (no implementation detail…essentially “use IP”, referencing standard RFCs) – done on purposeGoal is to have no changes to the existing applications (e.g. LINK2000+ CPDLC) while moving away from OSI-based protocolsAvoids having to re-do flight decks, aircraft applicationsRemoves dependency on applications from OSI protocolsCreates a logical transition path to future IP-based communication linksCan support B2 service introductionCan provide a common security frameworkIn-line with Boeing enterprise communication strategy
ATN/IPS Approach
Slide6Created an identical dialog service interface (the interface between the application and the upper protocol layers) regardless of ATN/OSI or ATN/IPSInitial specifications validated by EUROCONTROL via lab trials, LFV (Sweden) via PC-based flight trials
ATN/IPS Dialog Service Concept
ATN-App AE
ATN-App
ASE
CF
Security
ASO
ACSE
Application User
ATN-App ASE (e.g. CPDLC)
TCP/UDP
IPS
Applications
Unchanged
Interfaces
Unchanged
ATN/OSI
Application and Stack
Structure
ATN/IPS Application
and Stack Structure
No difference
to the
user
Upper Layers
CLNP
TP4
Application User
IPS Dialog Service
Slide7Envisaged Boeing ATN/IPS Architecture (DRAFT)
Comm
Service Provider
EFB
Display
CMC/
ACMF
Cabin Systems
Comm Management
Media Routing Logic
ACARSNetwork
ATNNetwork
HF
SDU
VDR
CMF
FMS
AOC/ATC
AOC
Air
Ground
AeroMACS
SBB/Iridium
NEXT/Other
IP
Network
AOI
LDACS
Slide8Boeing Research and Technology and Honeywell Advanced Technology started a Joint Research Project based around identified common interestsDetermining implementation constraints of ATN/IPSHow it would work in current aircraft architecturesPrototyping ATN/IPS using realistic hardware and adjacent aircraft systemsTesting in live communication environment (SATCOM)Lots of areas for further definition/investigationRoutingMobilityPerformanceSecurityATN/OSI – ATN/IPS interoperability and transitionATN/IPS over VDLM2 performanceetc
Boeing – Honeywell Activities
Slide9Honeywell has provided Boeing with a prototype ATN/IPS CMUPromising results so far…Prototype ATN/IPS CMU swapped for ATN/OSI CMU on Boeing 737 test rackInitial ATN/IPS application-level compatibility provenNo changes to ATS functionality from the flight crew and avionics perspectiveCPDLC, CM behave exactly the same as OSI versionNo changes to MCDU displaysInternal avionics interfaces unchanged Boeing and Honeywell are continuing work to investigate/define other aspects of ATN/IPSCurrently performing lab trials with Honeywell and Boeing ATN/IPS ground systems, sending/receiving CM and CPDLC messagesScheduled to perform SATCOM and VDLM2 testing over this year and nextPotential flight trials via ecoDemonstrator, 2015-2016
Boeing – Honeywell Activities Current Status
Slide10Boeing and Airbus currently have schedule and technical disconnects in this areaAirbus, via SESAR/ESA projects, is planning to tunnel ATN/OSI over INMARSAT’s SwiftBroadband service with a trials capability by 2017Is an acknowledged “interim step”…transition past interim not yet definedPerformance benefits of ATN/OSI over SBB still TBDTarget fleets and numbers to be defined; very few narrowbodies have SATCOMBoeing would rather go directly to ATN/IPS than do an expensive, complicated interim step that may delay further IP developmentLooking at ~2022 for ATN/IPS capability, and planning research accordinglyNo need for interim solution prior to then; understand and solve European issues first rather than introducing additional complexityWork towards accommodating Oceanic/Domestic B2 programs with ATN/IPS
Boeing and Airbus are working towards a converged roadmap
Boeing/Airbus Alignment on ATN/IPS
Slide11Still being worked between Boeing and Airbus and other stakeholders
Datalink Roadmap (Boeing Vision, DRAFT)
Legacy Com means
Future Com means
2020
2025
2030
AeroMACS
LDACS
2015
Iridium NEXT
2035
VHF Voice
VHF
Data/VDLM2
HF
Satcom Data 2
2017
2030
2016
?
?
?
Airborne ATS
Router
ACARS
?
ATN/OSI (B1, Europe)
SATCOM (SBB/IRIS)
2016
?
?
ATN/IPS
Slide12Far from being a mature standardAggressive work needs to be done to validate ATN/IPS and quantify product line impactsArchitectural impacts, including CMU/routerSATCOM/VDLM2 support, including multiple vendors, multi-media performanceMobilityTCP vs UDPAddressingSecurityCompatibility between ATN/OSI and ATN/IPS and transition needs to be definedLikely a ground gateway, similar to how FANS-1/A – ATN/OSI gateways operateBoeing plans to continue progressing studies in these areas and expand trials
ATN/IPS Work to be Done
Slide13Thank you!
Questions?
Slide14Slide15Backup
Slide16Move from ATN/OSI to ATN/IPS and broadband IPBe 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 additionsBe based on stated and validated performance requirement needsBe a true transition towards the end state ATN/IPS, not an interim short term throw away stepBe applicable globallyMake maximum use of COTSHave a positive business case for the customer airlines and ANSPsDomestic and Oceanic environmentsPreserve current investments in ground and aircraft assetsMove routing complexities and gateway functionalities to the groundSupport ACARS (FANS and AOC) traffic
Guiding Principles for Migration to Future Comm
(network/
subnetwork
level)