esa iris programme technical overview - artes.esa.int · impact on aircraft avionics, channel...
TRANSCRIPT
[email protected], [email protected]
ESA Iris ProgrammeTechnical Overview
15.10.2008 Conference Call
2
System Design Hypothesis & Options from Ph.A studies
3
Role of Satellite CommunicationsContinental airspace + oceanic
European AOC Centre
Airportnetwork
Airport Terminal Manoeuvering Area / En-route(continental area: dual link )
Oceanic, Remote & Polar
Future terrestrialnetwork
System Wide Information Management (SWIM) Satcom
European Air Traffic Control Centre
Login (no traffic)
4
Iris Satellite System architecture
Terrestrial network(SWIM)
5 SWIM Infrastructure
CPDLC
CPDLC
ATN/IPS
ATN/IPS
ATN/IPS
PHY
MAC MAC
MAC
PHY PHY
Pilot HMI
CMU
ControllerHMI
FDP
SpaceSegment
ATC
Cen
tre
AES
NM
C/N
CCGES
ATC
Ser
vice
Satcom
syste
m
signa
lling
Boundaries ofthe Iris System
Boundaries of Communication System Design
6
Phoenix
Design Option 1
...0110101001010.
.
ICOS
...0110101001010.
.
Specificationsfor Ph. B ITT
SimulationsUpdatedSRD
ATM TrafficModel
Design Option 2AssessmentMethodology
PerformanceAssessment
Iris Expert Group
• Requirements
Iris Expert Group
• Assess options
• Align with SESAR
Respective merits of options proposed by ICOS and Phoenix areassessed against the same performance criteria, in an impartial mannerto define a baseline for Phase B. The most promising techniques will bereferenced in the technical annex of Phase B ITT.
Communication System DesignPhase A process
7
Communication System DesignPerformance assessment
Evaluation criteria:– Solution free of Intellectual Property Rights– Spectrum required– System scalability and flexibility– Interface with terrestrial network and aircraft on-board systems– Support ATS and AOC service performances as defined in COCR– Link performance
8
Communication parameters dimensioningfor the satellite design
The size of the antenna for the return link is driven
by the user terminal peak ratei.e whatever the volume of
data, the size will be the same
The payload (mass+power) is driven by the capacity
on the forward link (i.e. the number of carriers,
linked to the number of a/c)
9
SESAR service area (European controlledairspace ECAC + surrounding oceanic area)NB: Airport surface not applicable
System in full operation post 2020
Assumes all IFR aircraft equipped
Possible extensions of coverage:- Visible Earth from GEO orbit
- Northern latitudes areas byagreement with other countriesoperating ATM Satcom services onHEO satellite systems
Analysis and definition of the satellite systemService coverage options
10
Antenna patterns of Phase A studies propose either 3 or 6 spotbeams forECAC.This design is based on initial assumption, a refinement is on going followinginput from both Communication studies and further capacity assessments
Analysis and definition of the satellite systemECAC coverage options
11
The Iris solution: system architecture(when fully deployed)
12
Iris Subset:Minimum infrastructure required for validation
Pre-operational phase
for CertificationOperational System (2020)System validated (2015)
Subset SpaceSegment
Subset GroundSegment (2 GES,NMC, NCC)
Test flights Deployment
2015-2020+
13
Service Provision: some open issues
• Centralised or distributed Ground Segment? (i.e. multiple Ground Earth Stationsmight be required to avoid monopolistic service provision models)• How will AOC service provision differ from ATS?• Deployment of SESAR full operational system will be financed by a mix of publicbudgets, private investments and cost recovery from end user via route charges.Who will be the owner of the infrastructure? What is the financing model?
The service model influences technical choices: the system architecture shallbe refined after consolidation of the business case
Role of SESAR JU, as system architect to define the system architecture anddeployment process
Public Budgets Private Investors End Users European Commission budgets
Eurocontrol
European Space Agency
Aerospace companies
Satellite Operators
Lenders (banking sector)
Communication Service Providers
Airlines
ANSPs
14
Some technical issues are given attention during Phase 1:
How could the service also rely on 3rd party HEO, GEO or LEOinfrastructure?
Service operator in high-latitude regions to define capacityrequired, and HEO or LEO system designer/operator to defineimpact on aircraft avionics, channel model, and systemsinterconnectionService operator of GEO (Inmarsat) to define impact on its system
Dependability issues (Reliability, Availability, Maintainability andSafety) to prepare the safety case
Study with NATS (UK) to interpret target figures into satellite systemdesign criteria and prepare the safety case
Complementary system activities
15
Coordination of a common position regarding AMS(R)S spectrumamong European and National Frequency Management offices Support activities to seek a European consensus and establishextra-European alliances within ITU
Iris Phase 1Complementary regulatory activities
ESA participates in ICAO WorkingGroup F and ITU Working Party 4Cactivities, to prepare WRC11agenda item on AMS(R)S withestimates of spectrum requirements
Status: methodology to estimatespectrum requirements based onESA inputs to be proposed to ITUWP4C as ICAO WG-F input
Aviationcommunication
needs
Satellitesystem
parameters
Methodology toderive AMS(R)S
spectrumrequirements forWRC-11 A.I. 1.7
Total bandwidthrequirements for
AI 1.7
16
ICOS + Phoenix studies andtheir evaluation Completion end October 2008 Consolidation of trade-off
AVISAT, Samara, andcomplementary system studies Completion end 2008
Results will be available viawww.telecom.esa.int/iris
Iris Phase 1Technical results
17
Phase 2 activities
18
2009 2020
SESAR DEVELOPMENT PHASESESAR DEPLOYMENT PHASE
2011
DESIGN CANDIDATESYSTEM
CHECKPOINT:-Choose Subset- Select Operator
DEVELOP & DEPLOYSUBSET
mid-2014
SYSTEM VERIFICATION
Subset Payload
ca. 2018
RedundantPayload
CERTIFICATION & FULL DEPLOYMENT
mid-2015
SYSTEMVALIDATION
ESA ASSETSTRANSFER
IRIS PHASE 2: DEVELOPMENT
The Iris solution: deployment sequence
19
Tasks in the System WP:• Capture and consolidate requirements• Define the overall system architecture and the “subset” required for
validation• Coordination with entities external to the Iris programme• Support of regulatory activities for access to RF spectrum• Cost/benefit analysis and business case• Define verification procedures, coordinate validation and system
certification• Prepare transition to the pre-operational phase
Iris Phase 2 - WP1 System
Consolidaterequirements& selectsubcontractors
Syst
em v
alid
ated
Phase C Phase D Phase E1Validation
Iris Phase 2.2
PDR CDR Launch
Iris Phase 2.1
iris “subset”(Min. infrastructure
required forvalidation)
Phase B
mid-2009 end 2010 end 2012 mid 2014 mid 2015
20
Iris Phase 2 - WP2 Communication Standard
2 Documents are required for a new ICAO Standard: Amendment of ICAO SARPs (Systems and Recommended Practices) Development of a new Technical Manual
Tasks in the Communication Standard WP:• Consolidate trade-off from Phase A, coordinate with S-JU & ICAO• Detailed design• Develop verification testbed & initiate standardisation (with S-JU/EC)• Develop demonstration testbed• Develop certification / interoperability testbed
Consolidateoptions trade-off from Phase
A (CCN)
DevelopTechnicalManual &
amend SARPS
Demonstration testbed
Iris Phase 2.2
ICAO Technical manual ready
Iris Phase 2.1Testbedsavailable
(Required forvalidation of comsystem, AES and
GES)
mid-2009 end 2010 end 2011 mid 2014
Detaileddesign
Verificationtestbed
Certification &interoperability testbed
21
Tasks in the User Terminal (AES) WP:• Development of a proof of concept• Development of the prototypes (different versions for various types of aircraft)• Support development of the key standardisation documents (MASPS and MOPS)
under the umbrella of EUROCAE or RTCA• AES design until “red label” so that flight tests can be undertaken• Support verification and validation
Iris Phase 2 - WP3 User Terminal
Proof ofconcept Prototype
Product(industrialised)
“Blue Label”avionics
“Red Label”avionics
“Black Label”avionics(industry)
MASPS (Minimum Aviation System Performance Standards)MOPS (Minimum Operational Performance Standards)EUROCAE
Iris Phase 2.2: Design AES mature for flight testsIris Phase 2.1
mid-2009 end 2010 mid 2013 mid 2014 Certification
22
By 2015, the main purpose of the pre-operational space segment (“subset”) isto support the end-to-end validation required for the safety service to allowfor procurement, by the owner and before 2020, of the complete operationalinfrastructure.
Iris Phase 2 - WP4 Space Segment
Tasks in the Space Segment WP:• Capture and consolidate requirements• Definition of the Space Segment architecture• Definition of adaptations possibly required for the Satellite Control Centre
and the Satellite Operation Centre• Space Segment Phase B• Phase C/D of the space segment of the “subset” only• Prepare space segment validation & transition to the pre-operational phase
Consolidaterequirements Phase C Phase D Phase E1
Validation
Iris Phase 2.2
PDR CDR
Launch
Iris Phase 2.1
Phase B
mid-2009 end 2010 mid 2012 mid 2014
AcceptanceReview
end 2013 mid 2015
23
Tasks in the Ground Segment WP:• Capture and consolidate requirements• Definition of the Ground Segment architecture• Detailed design of NCC/NMC and GES; development of emulators• Develop GES, NMC and NCC required for validating the system (ground
segment of the “subset”)• Ground segment end-to-end validation and prepare transition to the pre-
operational phase
Iris Phase 2 - WP5 Ground Segment
Ground segment elements:- Ground Earth Stations- Network Management Centre- Network Control Centre
NCC
GES 1
GES n
To ANSP and airlines
Consolidaterequirements
Design &prototype
Developproducts
Iris Phase 2.2
PDR CDR
Iris Phase 2.1
Specs
mid-2009 end 2010 end 2012 end 2013
Deploysubset
Acceptancereview of
subset
mid 2014
1st GES ready
24
ESA Iris Programme
[email protected]@esa.int
ESA Iris System Design Studies
[email protected]@esa.int
www.telecom.esa.int/iris
Iris - Contact Points
25
Back-up slides
26
Iris Phase 1 design studies
Satellite CommunicationSystem studies
Analysis & Definition ofSatellite System studies
Avionics PreliminaryDesign
RxTx
CtrlPWR
AntDiplexer
LNA
HPAUp/Dwn Cvtr
MODEMBase-Band Unit
Outside
Inside
Avionic Bay
Com.System
Iris
Phas
e A
stu
dies
1Q08
to
4Q
08 ICOS + Phoenix
SatelliteSystem
Service provision +Business case model
AVISAT + Samara
PreliminaryDesign
Specifications
...0110101001010..
Which types of protocols?
Are COCR performancesachievable?
Link budget?...
What is new/COTS?
Antennas: where?how many?
Target cost?...
PreliminaryDesign
Specifications
Out
com
eex
pect
ed
Which type ofarchitecture?
Dependability?
Target cost?...
Who operates what?
Who procures what?
Financing scheme?...
27
Iris new Satellite Communications Standard
− System specifically designed for aeronautical Air/Ground Satcoms− Quality of Service management− Light terminals: small antenna and reduced High Power Amplifiers− Improved spectrum efficiency− Can be used with any type of satellite (GEO, LEO, HEO)
AMSS
NEW
– Interoperable standard supporting multiple Service Providers– Use protected radio-spectrum in L-band (AMS(R)S band: 1,545-
1,555 MHz and 1,646.5 – 1,656.5 MHz)– Support voice and data
Design optimisation hypothesis:• Meet capacity needs for 2025 (voice + data)• Flexible and scalable architecture without constraint on the number of Ground
Earth Stations• Avionics cost to be kept low (i.e. optimise operation modes and the technology
to limit power consumption and heating)
28
Capacity Requirements
time
Amount of data
From one flight
flight path / phases
cruise
departure
arrival
at airport
begin end
airport departure cruise arrival airport
at airport
time
flight - 1
time
flight - 2
time
flight - i
...
...
time
flight -N
time
Total instantaneous
throughput
00:00 24:00
Calculation of the informationthroughput over a given area duringthe busiest day of the year
X
29
Consolidation of requirements for ATSservices driving the design
• Peak rate of information– FLIPINT (return link only)– COTRAC– D-ALERT (return link only)This is the dimensioning parameter for the satellite antenna Calculated peak rates vary between 42kbps to 64kbps on the
Forward Link and 21kbps to 36kbps on the Return Link. Need to analyse FLIPINT CoS TD95 and continuity requirements
• Volume of information– WXGRAPH for the forward link if considered as unicast– COTRAC (Forward and return link )– Transport Layer acknowledgments (Forward and return link )This is the dimensioning parameter for the satellite capacity (power) Volume varies between 3.7Mbps to 5Mbps for the forward link, and
between 2.75Mbps to 3.45Mbps for the return link. Need to analyse feasibility of using multicast for WXGRAPH and
ways to reduce Transport layer ACK volume
30
Consolidation of requirementsMultiple access methods
• Initial analytical trade-off performed has shown that a MF-TDM schemeon the forward link and a MF-TDMA scheme on the return links performbetter than either CDM(A) or OFDM(A) technologies.
• As the traffic from each a/c is bursty, random access time slots areused on the return link to request capacity when needed rather thanhaving capacity permanently allocated to each terminal
• Simultaneous requests from different AES may collide and requireretransmission of the request, which impacts the delay until themessage is finally transmitted
⇒ Need to have efficient techniques to limit the probability ofcollisions or to increase the number of slots dedicated to thoseRandom Access requests
⇒ Need to limit the number of retransmissions