Future SESAR COM Architecture

V1.1
Future SESAR COM Architecture
Iris Information Event
Prague, May 26th, 2010
Nikos Fistas
SWP15.2 Manager
The European Organisation for the Safety of Air Navigation

Agenda
1) Future Aeronautical Communications – Key Assumptions
2) Future data links in the SESAR context
3) Terrestrial Data Links
• LDACS: SESAR project P15.2.4
• AEROMACS: SESAR project P15.2.7
2

Basic Assumptions (1/2)
• Future (2020+) system needs to support ATS and AOC end-toend
communications including air/ground and air/air
• In future operating concept data becomes the primary mode of
communications
• In case of failure of data com, voice is unlikely to be able to
sustain operations at the same capacity level. Therefore
different data links may be needed to maintain capacity of
operations
• In the future concept voice will remain available for emergency
communications
3

Basic Assumptions (2/2)
• No single technology meets all requirements across all
operational flight domains
• Future system will be a system of systems integrating existing
communication systems (voice, VDL) as well as new
communications systems to meet the operational requirements
(Airborne) Integration of technologies needs to be facilitated
• Future system should support digital voice in the long term,
however in the short term the emphasis is to support data
communications
• Appropriate spectrum allocations: AM(R)S and AMS(R)S
4

Baseline of current work
5

Legacy systems and New Data Links
Legacy Systems
Multilink
Concept
Airport surface: C band
General terrestrial: L Band
Satellite: Oceanic + Continental
6

FCI: Future Com Infrastructure
• Enabler supporting the realisation of SESAR objectives
(especially in terms of safety and capacity)
• Global standards and support for worldwide interoperability
7

SJU WBS
SESAR Programme
WP B WP C WP D
Target Concept &
Architecture Maintenance
Master Plan
Maintenance
ATM Network R&D
Programme
WP 3
Validation
Infrastructure
WP 16
R&D Transversal
Areas
WP 7
Network
Operation
WP 4
En Route
Operation
WP 5 WP 8 WP 14 W 11 WP 15 WP 13
TMA Information SWIM F/WOC CNS Network
Operation Management
Information
Management
SWIM Thread
Systems
(NIMS)
WP 6
Airport
Operation
WP 9
Aircraft
WP 10
En-route
APP
ATC
Systems
WP 12
Airport
Systems
8

Communication Projects in
SESAR (1/2)
WP 9: Aircraft
• Project 9.16: New Communication Technology at Airport
• Project 9.19: Swim Air-Ground Capability
• Project 9.20: Military data link accommodation
• Project 9.21: ADS-B - 1090 Higher Performance Study
• Project 9.22: Mid & Full ADS-B Capability
• Project 9.24: ADS-B In/Out for military aircraft
• Project 9.44: Flexible Communication Avionics
• Project 9.49: Avionics Architecture and Interoperability
Roadmap
9

Communication Projects in
SESAR (2/2)
WP 15: Ground CNS Infrastructure
• Project 15.1.6: Spectrum Management & Impact
Assessment
• SWP 15.2: Communication
• Project 15.2.4: Future Mobile data Link system definition
• Project 15.2.6: Future Mobile Satellite Communication
• Project 15.2.7: Airport Surface Data link
• Project 15.2.8: Civil-Military Data Link Interoperability
• Project 15.2.10: Terrestrial communication infrastructure -
SWIM backbone
10

FCI: ATM Communications in
2020+ and SJU projects
9.21/9.22
9.20/9.24/15.2.8
9.44/9.49
15.2.6
15.2.4
15.2.7/9.16
9.19
VHF
New
Terrestrial
System(s)
NETWORK
15.2.10
VHF
11

Project P 15.2.4:
Future Mobile Data Link System Definition
12

Project in brief
Partners
Airbus, Alenia, DFS, DSNA, EUROCONTROL, Frequentis,
Honeywell, INDRA, NORACON and Thales
Project scope
• General system aspects of future data link systems
• L band system definition (LDACS)
Divided into two steps
• Step 1: Early Tasks (up to March 2011)
• Step 2: Follow on activities (2011-2016)
13

Project Activities
• Task 1: Operational requirements (refined COCR)
• Task 2: Transport layer management specification
• Task 3: Recommendation for the terrestrial a/g data link system
• Task 4: Description of work for Phase 2 (development of
terrestrial a/g data link)
14

Early Tasks Activities (and links
to Full Project Tasks)
• EWA1: Operational requirements refinement (Task 1)
• EWA2: Multilink Operational Concept - COM Architecture
(Tasks 1, 2 and 3)
• EWA3: Upper layers and QoS mechanisms (Task 2)
• EWA4: LDACS selection facilitation activities (Task 3)
15

Key activities for all links
‣ Multilink Operational Concept
‣ QoS management and network layer
‣ Refined communication requirements
16

Project P 15.2.7:
Airport Surface System
17

Project P15.2.7 and 9.16:
AeroMACS
• Partners:
• P15.2.7: AENA, DSNA, INDRA, NATMIG, Selex, Thales
Airbus and ECTL
• P9.16: AIRBUS, Selex, Thales and ECTL
• Duration: March 2010 to 2013
18

Projects P15.2.7 and 9.16:
Overall Aim
Define, validate and demonstrate
a technical profile and architecture
for a new airport surface communication system (AeroMACS)
based on 802.16e IEEE standard
by studying, developing, integrating and testing
system prototypes
• Project 15.2.7 covers overall system aspects and ground
component
• Project 9.16 covers airborne component
19

Project P15.2.7 scope
• Overall system functional and performance definition
• Definition of a new specific profile
• Development of validation plans and scenarios
• Specification of test objectives and procedures
• Specification and development of (prototype) ground segment
• Analysis, simulations and test campaigns addressing
interoperability (multiple manufacturers) in laboratory and real
airport environments
• Security and safety analysis
• Coordination with standardization bodies (RTCA and
EUROCAE)
20

Project P9.16 scope
• System requirements and architecture definition for the airborne
side
• Specification and development of airborne prototype for
mainline aircraft
• Specification of test objectives and procedures for airborne side.
• Integration of the airborne prototype in a representative mainline
aircraft environment
• Testing in real environment (on airport, using a/c representative
platforms, and up to integration in a real flight test a/c),
• Advanced studies (limited effort): MIMO studies, integrated
antennas, WiMAX evolutions (e.g. 802.16m)
21

Thank you
(nikolaos.fistas@eurocontrol.int)
22