Boeing Data Link Strategy Presented to LINK2000 Workshop February 1516, 2005

1
Boeing Data Link StrategyPresented toLINK2000
WorkshopFebruary 15-16, 2005
Scott Pelton Avionics Chief Engineer Dung
Nguyen Data Link System EngineerRob MeadSystems
Engineer The Boeing Company
2
Content

• Background Data
• Situation and Target
• Airplane and Ground Migration
• Strategy

3
Datalink Environment
Communication Satellite
Navigation Surveillance Satellite
Airport and Air Traffic Services (Domestic and
Oceanic)
Flight Crew
Cabin Crew
Passengers
Ground Crew
Airline Operation Center
Ground Telecommunications Network
4
Datalink Enables Air Traffic Management Vision
Hybrid Ground and Space Based Communication, Navig
ation, and Surveillance
Trajectory Based Airspace Management
Simplified airspace design
Wide-Scale Information Management

• Layered security approach
• Open system principlesgrowth for the future
• Phased transition planbuilds on existing plans

5
Datalink Applications
6
Datalink Networks
7
Datalink Media
POA Plain Old ACARS VDLM2 VHF Digital Link
Mode 2
8
Total Datalink System
AIR
GROUND
Flight Management
VHF Mode A
Datalink Service Provider
Traffic Surveillance Unit
VDL Mode 2
Electronic Flight Bag
Datalink Service Provider
VDL Mode 3
Airline
VDL Mode 4
Datalink Service Provider
Comm. Management -ACARS -ATN -IP
Airplane Condition Monitoring
Mode S
Datalink Service Provider
UAT
Central Maintenance
HF
Datalink Service Provider
Air Traffic Control
SATCOM
Datalink Service Provider
Swift 64
Display
Datalink Service Provider
Swift Broadband
Boeing Connexion
Datalink Service Provider
Emerging network
Gatelink WiFi/GSM
Not supported
Complex and costly if not controlled
9
Situation

• Network
• ACARS/VHF
• VHF frequency congestion is becoming the
  communication bottleneck
• ACARS network is approaching saturation point
• The world is migrating to VDLM2
• ATN
• Europe is building support and infrastructure for
  ATN network
• IP
• The use of IP with broadband network is migrating
  into the aircraft for APC
• Lack of standards and requirements on IP
  protocols and networks that could be used to
  support AOC and ATS datalink
• Applications
• AOC
• AOC data link traffic is growing rapidly
• New AOC functionalities and applications are
  being introduced
• ATS
• Both FANS-1 and ATN Baseline 1 continue to grow

FANS-1 Future Air Navigation System Packet 1
10
Target

• Highest benefit, least cost to operators, Boeing,
  and industry
• Support the air traffic management vision
• Enable network-based operations
• Responsive to market needs for datalink
• Accommodate different datalink product
  generations in the fleet (backwards compatible)

11
Datalink Network Traffic Migration
gt90 Traffic
lt10 Traffic

• AOC is going directly to broadband IP, by-passing
  ATN
• AOC service experience with broadband IP is
  critical to demonstrating adequacy for ATS
• ATS will migrate to broadband IP, but not in the
  near future. For interim, Boeing will monitor
  market demand for ATN.
• ACARS and ATN will continue to exist in the
  foreseeable future, do not wait for broadband IP

12
Airborne Migration Challenges
FANS-3
FANS-2
FANS-1
FANS App.
ATN App.
ATN App. (next generation)
Application
Broadband IP
ACARS
ATN
Network
Current
Longer Term Solution
Next Generation

• Boeing strongly encourages FMS integrated
  datalink
• Future systems must be backwards compatible
• Future systems may not be available on all
  aircraft due to architecture complexity and cost

FMS Flight Management System
13
Migration Strategy
FANS over ACARS
ATN over ATN
Airborne
Migration Strategy Needed
Ground
Gateway
Gateway
FANS over ACARS
ATN over ATN
14
Migration Strategy guiding principles

• Do not delay equipage waiting for the next step
• Support FANS programs
• Support ATN programs
• Support ground-based dual-stack in all airspaces
• Need ground to do this in order to resolve all
  the issues
• Ground-based is essential to driving convergence
• Support use of integrated data link solutions
• Support work on broadband IP
• Work on broadband IP standards for aviation
• Conduct trials, especially AOC, to establish
  service history for aviation suitability
  judgments
• Maintain backwards compatibility

15
Application Migration
(GW) via a Gateway (internal or external to
the ANSPs local systems)
16
Network Sub-network Migration
17
And there is "integrated data link

• Integrated data link is essential to our ATM
  vision, in order to enable
• Decreased reaction time and reduced frequency
  occupancy
• Seamless interoperability and operations thru
  flight domains
• 4-D Trajectory negotiation and separation
• Large-scale data sharing of aircraft intent,
  ground air
• Airspace redesign
• Integrated data link includes a full CNS solution
  (CNS, not only 'C')
• Data link applications
• CPDLC Controller Pilot Data Link Communications
• ADS-C Automatic Dependant Surveillance-Contract
• Others, e.g AOC, etc
• For aircraft, the capability to interface with
  avionics (HMI, RMP, FMC)
• For ANSPs, the capability to share and use ATM
  data
• Primary examples frequency, flight plan
  consistency, flight plan conformance, route
  clearance, trajectory negotiation

18
Strategy and Why
19
Strategy Summary

• Migrate AOC to Broadband IP
• Migrate ATS to Broadband IP, monitor market needs
  for intermediate solution
• Free up VHF, do not support VDLM3 or VDLM4
• Maintain backwards compatibility in aircraft
• Support worldwide ground accommodation
• Encourage FMS - integrated datalink

20
Next Steps

• To support broadband IP in the future and
  migration strategy, we need to understand
• Security Requirements
• Required Communication Performance (RCP)
• Support air/ground datalink implementation
  programs using FANS and ATN
• Dont delay equipage waiting for IP
• Active implementation programs like LINK are
  essential to progress

21
Questions?Thanks!Rob.Mead_at_Boeing.comDung.Q
.Nguyen_at_Boeing.comScott.L.Pelton_at_Boeing.com