GateFusion Wireless Content Delivery

1. GateFusionWireless Content Delivery Andy Wood ARINC awood@arinc.com

2. Agenda • What is Gatelink? • Gatelink Technical Requirements • The Advent of Gatelink • Wi-Fi and Wi-Max • What is GateFusion? • Gatelink issues resolved by GateFusion • GateFusion system components • Making GateFusion a Reality

3. What is Gatelink? • Terrestrial data communications providing wireless access to the aircraft • Began as a tethered solution, moved to infra-red, now Wi-Fi (802.11x) • Gatelink includes a set of industry standards focused on data communications between an aircraft and a gate • Capable of larger uploads/downloads than traditional wireless communications • WiFi commonplace at airports • Supports aircraft operational requirements • More aircraft centric data makes ‘Sneaker-net’ less viable • New aircraft models incorporate Terminal Wireless LAN Units (TWLU) • Boeing B777/B787, Airbus A380, Several retrofit progams

4. Gatelink Technical Issues • Getting TO the Network • Version of Wi-Fi (802.11a/b/g) • Proximity to Access Point • SSID/Encryption Method • Getting THROUGH the Network • Authentication • Delivery of large files at required airports with varying connectivity • Getting the Data on/off the aircraft • Bandwidth utilization • WAN performance • Handling Interruptions • Partial loading

5. Traditional Avionics ArchitectureCurrent Data Streams Flight Management Computer MCDU ACMS/ Maintenance Computer ACARS CMU Engine/Exceedence Snapshot Reports QAR/Data Interface VHF Digital Radio HF Data Radio Inmarsat/Iridium SDU Flight Operations Quality Assurance Engine/Data Downloads (Sneaker-net) ACARS Messaging

6. AeroSync Flight Management Computer EFB MCDU ACMS/ Maintenance Computer TWLU ACARS CMU IFE Server QAR/Data Interface VHF Digital Radio HF Data Radio Inmarsat/Iridium SDU • Gatelink Data: • Flight Operations Quality Assurance (FOQA) • Electronic Flight Bag (EFB) Content • Cabin System Updates • In Flight Entertainment (IFE) Content • Flight Release Paperwork • Nav Database Updates

7. GateFusion Resolves Gatelink Complexities • ARINC brings years of experience with Airport Wi-Fi, ground networks, and common use services to solve the following Gatelink challenges: • Global Technical Solution • Consistent technical interface from airport-to-airport • Eliminates Bandwidth Limitations • Data Delivery Service eliminates bandwidth variables between aircraft and airline’s application host • Global Reach • Single point of contact for fully-managed service worldwide

8. Wi-Fi and Wi-Max for Aviation • ARINC has been involved with Wi-Fi standardization for aviation for nearly 10 years • Latest AEEC specification (822) fully addresses security, authentication, and interoperability • Wi-Max is a promising technology, and ARINC is supporting efforts to address compatibility/security issues for aviation • Latest standard ratified by IEEE less than one year ago • Communication products/standards require time to mature • Advantages and disadvantages of either technology • Bandwidth sharing • Distance from transmitter

9. Wi-Fi and Wi-Max for Aviation Wi-Fi Standardization for Aviation AEEC ratifies 822 Full avionics compatibilityStandards for security/authentication 2007 AEEC ratifies 763-3 2005 Limited avionics compatibilityBasic security introduced IEEE ratifies 802.11g 2003 AEEC ratifies 763-1 Incompatible avionicsNo security/authentication 1999 IEEE ratifiesinitial 802.11 1997

10. Airport A Airport B Airport C Gatelink Issue #1 – inconsistent global technical solution Airport interfaces are all different! SSID: Provided by IP Service Provider Security: WPA-2 Authentication: Provided by Airline SSID: Provided by Airport B Security: WEP Authentication: Provided by Airport B SSID: Provided by Airline Security: None Authentication: Provided by Airport A

11. GateFusion Solution – Global Interface Transparency SSID:SAME Security:SAME Authentication:SAME Airport A ARINC Global Network Airport A SSID:SAME Security:SAME Authentication:SAME Airport B SSID:SAME Security:SAME Authentication:SAME Airline Application Server Airport C Airport interfaces look the same!

12. Gatelink Issue #2 – Bandwidth limitations Gatelink Bandwidth on airport premise is Mbps Mbps Aircraft to app throughput in this case is effectively in kbps Airport A Data throughput is limited to lowest circuit speed in the data path kbps Bandwidth between airport and airline network can be minimal Mbps Airline Application Server Airline Network Bandwidth from airline network to app host is Mbps

13. GateFusion Solution #2 – Data Delivery Service Resolves Bandwidth limitations ARINC Global Network Airport A Airport D Central Authentication Server Tail Assignment Location Destination Airport C Airport B Local Delivery Server Central Delivery Server Airline Application Server

14. GateFusion’s Global Reach • ARINC has negotiated access with multiple airport authorities • Americas, Europe, Asia • Technical terms are met and satisfied • Initial commercial terms are established • Negotiating T&Cs with Authorities • Coverage negotiated per individual airline requirements • Preliminary agreements reached with 65 airports • Expect several hundred airports by end of 2007

15. IFE Content Delivery Scenario Airport A ARINC Global Network Airport A Airport B IFE Server Airport C

16. ARINC Infrastructure at Airport ARINC Global Network Summary: GateFusion for IFE Wireless Delivery • Common Use for Cost Savings • Seamless Connectivity at all Airports • Authentication and Wireless Security • Data Delivery Service to Stage Data at Airports Prior to Aircraft Arrival • Industry rethink on media delivery?