antares pres5 system design and ... - european space agency

27/05/2010

Business Unit Telecommunications

All rights reserved © 2010, Thales Alenia Space

ANTARES System Design and Relevant OptionsPaolo Conforto and Giacinto Losquadro

Iris Information EventPrague, 26-27 May, 2010

27/05/2010 All rights reserved © 2010, Thales Alenia Space


Presentation Contents

Foreword

ANTARES satellite system requirements

ANTARES Phase B system design approach System dimensioning and performance System options

Concluding remarks



Overview of the ANTARES Satellite System Requirements



Main ANTARES Satellite System Requirements (1/2)

Space Segment Design based on GEO satellites

Compatible with later addition of Highly Elliptic Orbit (HEO) and/or Low Earth Orbit (LEO) satellites

Allowing timely replacement of a satellite In order to comply with the required system availability without degradation

of service performance

System Topology Compatible with centralized as well as a decentralized ground segment EATM

network access architecture Compatible with centralized as well as a decentralized ground segment network

management and control architecture



Main ANTARES Satellite System Requirements (2/2)

System Architecture and Design Allowing incremental deployment of its elements or sub-elements Allowing to met service requirements during aircraft manoeuvring

Over the specified coverage region Maximum bank angle of 35° (TBC) Maximum pitch angle 20° (TBC)

Providing linking and handover with other ATM regional services Using the same Communication Standard and compatible user terminals

Allowing static, semi-static and dynamic capacity and resources allocation between ground earth stations (GESs) To cover traffic pattern changes during lifetime, daily and in case of system

failures



ANTARES System and the External Supported Network

SOC/SCC

Controller HMI

FDP

Application

ATN Network

Data Link

Physical

ATN Network

Data Link

Physical

Data Link

Physical

ATN Network

ATN Network

Data Link

Physical

Data Link

Physical

GES (1,2,….N) NOC

(1,2,..N)Master NOC

EATM Network

Pilot HMI

CMU

Application

UT Network

ANTARES SatComSystem

European ATM System

User Term

inal

ATC

or AO

C C

entre

Data Link

Physical



ANTARES System compatibility with HEO/LEO Satellite Components

System baseline Two GEO satellites + in-orbit spare satellite

Allowing timely replacement of a satellite (to comply with the required system availability)

Compatibility with later addition of HEO/LEO Satellites HEO orbit

geosynchronous Tundra orbit (one sidereal day period) and/or Molnya orbit

LEO orbit

GEO orbit

LEO orbit

HEO orbit



System Design Approach



ANTARES System Architectural Design Flow

System OptionsSystem Requirements

Space Segment

User Segment

Communication Protocols

Ground Segment

System Components

RAMS, Coverage, Coordination etc.

Constellation Definition

Satellite Design

User Terminal Design

ArchitectureDefinition

Ground Earth Station Design

Protocols Design



(*) The ENR/TMA (En Route/Terminal Manoeuvring Area) System requirement is equal to 0.99995, equally shared with the Terrestrial Data Link System (TDL)

(**) In the ORP (Oceanic Remote Polar) Area the Satcom System is not complemented and satisfies the whole requirement

RAMS REQUIREMENTS

System Requirements Document

Product Assurance Requirements

Applicable Documents

System RAMS Requirements

SPACE SEGMENT

LINK

USER TERMINAL

GROUND SEGMENT

ANTARES System and Segments

APPORTIONMENT TO SEGMENTS AND LINK

PROVISIONSPACE SEGMENT AVAILABILITY

REQUIREMENTSYSTEM AVAILABILITYPreliminary apportionment

(conservative)

0,9965

0,9800

0,99990,9995ORP (**)

0,99920,9980ENR/TMA (*)

USE

System Availability and Space Segment Availability



ECAC Service Area and Field of View from a GEO Satellite

ECAC Service AreaElevation Contours

GEO Longitude 1.5° West



ANTARES Geostationary (GEO) Satellite Coverage at L-band for SES/ECAC area

ANTARES geostationary (GEO) satellite coverage at L-band for SES/ECAC area L-band multibeam coverage Number of beams to be defined during the ANTARES Phase B1 taking into account (among others)

GEO satellite orbital position Radiofrequency performance of satellite links via low cost terminals Technological and accommodation constraints for the L-band payload antenna

Example of 3-beams coverage (lat/long coordinate system, az/el coordinate system) here following

-3

-3

-2

-2

-1

-1

31.71

-3

-3

-2

-2

-1

-1

33.35

-3

-3

-2

-2

-1

-1

33.40SA

TSO

FT

-8.00 -6.00 -4.00 -2.00 0.00 2.00 4.00 6.00 8.00Azimuth in Degrees

0.00

2.00

4.00

6.00

8.00

10.00

Ele

vatio

n in

Deg

rees

-3

-3

-3

-2

-2

-2

-1

-131.71

-3

-3

-3

-2

-2

-2

-1

-1

33.35

-3

-3

-3

-2

-2

-1

-1

33.40

SAT

SOFT

-40.00 -20.00 0.00 20.00 40.00 60.00East Longitude (Degrees)

10.00

30.00

50.00

70.00

Nor

th L

atitu

de (D

egre

es)

Example of the L Band coverage (satellite view and rectangular coord view)



Theoretical Achievable Link Data Rate 3 Beams Coverage

Maximum achievable FW link data rate Min: 23 Kbps (Banking 27°)

101 Kbps (En Route) Max: 998 Kbps (En Route/Banking 27°)

Maximum achievable RT link data rate Min: 1.8 Kbps (Banking 27°)

10.3 Kbps (En Route) Max: 81.0 Kbps (En Route/Banking 27°)

Aircraft in manoeuvring (banking angle 27°)



System Options

System Options to cope with a “selected set” of system and user requirements uncertainty / variability

SO1: Information and Communication Security SO2: Transmission Security SO3: System Capacity SO4: End User Terminal Capabilitywith the additional architectural option for the ground segment: Centralized/ Distributed Architecture

System Options combination and system architecture Several system architectures may be defined by combining the System Options

System Configuration Options Reduced set and hence sub-set of system (highly representative) architectures

System Configuration Options identified and characterised Relevant Figures of Merit (both technical and non-technical)

Include representative cases for system design covering the extreme values of the defined ranges

The baseline configuration for the System Architecture will be selected at the end of the ANTARES phase B1 Decision involving SESAR JU



System Options Definitions

Radiofrequency transmission performance (EIRP) of the end user terminal on-board the Satcom equipped aircrafts.

End User Terminal CapabilitySO4

Information volume (Mbps) entering the ANTARES System at network layer.System CapacitySO3

Applied within the ANTARES System boundaries, in order to mitigate the threats deriving from RF interference sources that may affect the provisioning of the AOC and ATC servicesAttributes of SO2 are determined to mitigate the RF interferences generated by: known equipment transmitting in the useful bandwidth (intra-system and/or

inter-systems interferences) unknown sources (either intentional/malicious or unintentional) that transmit in

the useful bandwidth.

Transmission SecuritySO2

Applied within the ANTARES System boundaries in order to mitigate the threats on informatics system and on communication devices or other electronic systems.SO1 addresses both AOC and ATC, according to their specific user and service requirements.Attributes of SO1 for ATC and AOC: to be determined by threat analysis results

Information and Communication

SecuritySO1

System Option DefinitionSystem Option Name



InfoComm Security: System Option 1

GES NCC, NMC SCC/SOC

AES

EATM

B

C ATC/AOCCentre

ATC/AOC Application A

SO1 applies to the following interfaces of the ANTARES systemA. Satellite air interface between GES and AESB. Communication interfaces between elements of the ground segment (GES, NCC, etc.)C. TC and TM interfaces between the ground segment and the on-ground space control

segment

AES: Aeronautical Earth Station AOC: Airline Operation ControlATC: Air Traffic ControlGES: Ground Earth StationNCC: Network Control CentreNMC: Network Management CentreSCC: Satellite Control CentreSOC: Satellite Operation CentreTC: Tele CommandTM: TeleMetry

ANTARES System



InfoComm Security: SO1 Attributes

Attribute Logical Value

YES (TBC)NONOThe transmitter or the receiver is not allowed to deny its actsNon repudiation

YES (TBC)NONOThe users privilege to access the resources of a system is granted only to authorized users, programs, processes, or other systemsAccess Control

YESYESNOThe identity of the entities involved in a communication is verifiedAuthentication

YESYESNOMessages are received with no modification. Data are unchanged and are not accidentally or maliciously modified, altered or destroyedIntegrity

YES (TBC)NONOTransmitted data are not disclosed to unauthorized entities or processConfidentiality (Encryption)

SO1=HIGHSO1=LOWSO1=NULLAttribute DefinitionAttribute Id. and

Name



GES NCC, NMC SCC/SOC

AES

EATM

BC

ATC/AOCCentre

ATC/AOC Application

A

AES: Aeronautical Earth Station AOC: Airline Operation ControlATC: Air Traffic ControlGES: Ground Earth StationNCC: Network Control CentreNMC: Network Management CentreSCC: Satellite Control CentreSOC: Satellite Operation CentreTC: Tele CommandTM: TeleMetry

SO2 applies to the following interfaces of the ANTARES systemA. Satellite air interface between GES and satellite payload (feeder link)B. Satellite air interface between AES and satellite payload (user ink)C. Satellite air interface between SCC and spacecraft (TC/TM link)

ANTARES System

Transmission Security: System Option 2



Transmission Security: SO2 Attributes Characterisation

YES(see Note 1)

YES (see Note 1)

Immunity level (dB) on known equipment transmitting in the useful bandwidth (inter-system and intra-system RF Interference)

Immunity against known equipment interference

Rejection (dB) of unknown external RF interference sources (malicious or unintentional) transmitting in the useful bandwidth

AttributeDefinition

Acceptable in-band out-of-channel interference: rejection > 20 dB

Acceptable in-band out-of-channel interference: rejection < 20 dB

Acceptable in-band in-channel interference:(I/S) < 3 dB (see Note 2)

Acceptable in-band in-channel interference: (I/S) < - 10 dBImmunity against

un-known equipment interference on the L-band Return Link

SO2=HIGHSO2=LOW

Attribute Logical ValueAttribute

Note 1: The ANTARES satellite system is designed to cope with known interferences, both inter and intra-system Interferences

Note 2: The ANTARES satellite system operates with degraded performance



System Capacity: System Option 3 Attributes Characterisation

HIGH+:50% on top of the high capacity scenario

High “plus” capacity scenario (EUROCONTROL high growth of air traffic and 50% extra applications on top of full COCR applications)PIAC=7400

HIGH:FWD capacity = 5.8 MbpsRTN capacity = 1.4 Mbps

High capacity scenario (EUROCONTROL high growth of air traffic and full COCR applications)PIAC=7400

MEDIUM:FWD capacity = 4.2 MbpsRTN capacity = 1.0 Mbps

Medium capacity scenario (EUROCONTROL low growth of air traffic and full COCR applications)PIAC=5400

LOW:FWD capacity = 1.05 MbpsRTN capacity = 0.85 Mbps

Low capacity scenario (EUROCONTROL low growth of air traffic, with Modified COCR application requirements: e.g. WXGRAPH)PIAC=5400

ANTARES system traffic capacity

Attribute ValueReference scenariosAttribute



End User Terminal Capability: System Option 4

SO4 attributes refer to two different cases of aeronautical user terminal design “Low’ performance user terminal

Perceived to correspond to lower recurrent unit cost and installation cost “High” performance user terminal

User terminal performance is represented by EIRP Corresponding to two different sizes of the airborne power amplifier (PA), namely

PA power = 20W PA power = 40W

In both cases the EIRP is calculated at the antenna bore-sight

HighEIRP ≥ 13.5 dBW

LowEIRP ≥ 10.5 dBWTransmission PA power

Attribute Logical ValueThresholdsAttribute



System Design Finalisation: Concluding Remarks

A sub set of (highly representative) System Configuration Options has been identified and characterised Coming from the combination of System Options To cope with undefined or to-be-agreed user requirements With the relevant Figure of Merit, in terms of range of performance and

complexity

Comprehensive tradeoffs, analyses and dimensioning activities have been performed in order to quantify the impacts at system and segment level

Undefined or to-be-agreed user requirements are to be solved/removed in order to select the preferred System Configuration and to finalise the relevant system design

The baseline System Configuration, to be selected at the end of the ANTARES phase B1, will be refined and detailed during the Phase B2