honeywell advanced technologies europe - esa artes terminal j.stecha.pdf · honeywell advanced...

ANTARES WP33 User Terminal Design

Honeywell Advanced Technologies EuropeRadek Zaruba, Jaromir Stecha, February 2013

2 Copyright © 2013 Honeywell

WP33000 - Czech Consortium

• Honeywell- Project leader and coordinator- Main technical contribution to prototype development (platform

selection, protocol implementation etc.)- Investigation of larger GA aircraft requirements

• TL Elektronic- Investigation of small general aviation aircraft requirements- PC Control Application development- Support to embedded SH / HW design and development- Analysis of packaging options- Avionics interfaces module design

• RFspin- HPA design

• Scientis EU- Standardization studies


What is GA?- GA Definitions are ambiguous: The British Business and General Aviation Association:

• All aeroplane and helicopter flying except that performed by the major airlines and the Armed Services

UK General Aviation Awareness Council (GAAC):• All Civil Aviation operations other than scheduled air services and non-scheduled air

transport operations for remuneration or hire Aircraft Owners and Pilots Association (AOPA) – Germany:

• General Aviation is all civilian flying except for Scheduled Passenger and Cargo Airlines (OR: It´s Individual Air Traffic, just like driving a vehicle on the streets for most different nonscheduled purposes)


Gulfstream

Dassault Falcon Jet

Cessna

Hawker Beechcraft

Embraer

Bombardier

Pilatus

Epic Aircraft

Harbin Aircraft

Viking

Gulfstream

Dassault Falcon Jet

Cessna

Hawker Beechcraft

Embraer

Bombardier

Pilatus

Epic Aircraft

Harbin Aircraft

Viking

Business & General Aviation Customers and Products

Key CustomersKey Customers• Propulsion systems• APUs and power

generation• Integrated avionics

systems• Advanced safety

systems and applications

• Synthetic vision systems

• Flight management systems

• Cabin management systems and services

• Cockpit displays• Satellite

communications systems

• Digital flight guidance systems and controls

• Digital radio systems• Environmental Control

Systems

Key Products• Environmental Control

Systems• On-Board Inerting Gas• Generation Systems• General Aviation panel

mount and portable avionics

• Required Navigation • Performance Special • Aircraft and Aircrew • Authorization

Required • (RNP SAAAR)

Services• Flight support services• Maintenance service

plans, avionics warranty plans, and remote diagnostic services

• Global Asset Rental Banks

• Electronic flight bags


ATC COMM – Current Status

Voice (VHF)


GA ATC – Possible Future

Command

Reception confirmed

Execution confirmed

Confirmed by Pilot

voice

DATA TRANSFERS

VDLm2, L-DACS, AeroMACS, SATCOM

More than just new radio is needed for GA (HMI, data processing…)


The Need for New Satcom

• Improved data connectivity to critical aircraft domainsAircraft Control Domain (ACD)Control the aircraft• Cockpit displays• Flight Controls• FMS• Propulsion• etc

Airline Information Services Domain (AISD)Operate the airline• Airlines communication• Maintenance• EFB (Electronic Flight Bag)• Passenger support services• Administrative services

Passenger Information and Entertainment Services (PIESD)• Movies, games etc.

Passenger Owned Devices• Laptops• Cell phones • etc

Entertain the passengers

Current satcom radios• Inmarsat, Iridium• DAL‐D avionics only• Complex protocol stack

“Broadband” data for passengers• Hundreds of kbps (Inmarsat SBB)• Emails, internet connectivity…• Phone calls• Noncritical comm. in GA (Iridium)Narrowband “cockpit” comm.

• Units of kbps• High latency (tens of seconds)• Only oceanic airspaceFuture Iris radio

• DAL‐C avionics• Simple stack• Segregated comm. High performance “cockpit” comm.

• Tens of kbps (user data)• Low latency, high availability• Optimized for “sporadic data traffic”• Suitable also for continental airspace

This is what is missing and what Iris intends to deliver


Cockpit Satcom Performance Roadmap

• Performance specifications for future satcom being currently proposed under NEXUS Working Group.- Subgroup of EUROCONTROL’s NexSAT group - Objective is to update the AMS(R)S ICAO SARPS

• Following classification is proposed and used within NEXUS- Class A satcom system shall allow to: Support all the future oceanic and continental applications with low latency and high

availability (full 4D) Expected to be used in multi-link environment with terrestrial system(s) for improved reliability

- Class B satcom system should allow to: Support current and emerging ATM concepts (initial 4D) Offer additional capacity in oceanic and continental areas Extend the geographical coverage of the terrestrial infrastructure

Class C Class B Class A

Today“Current satcom”

Mid-Term Future (2017?)

Long-Term Future (2020+)This is what ANTARES intends to solve

ANTARES targets most advanced ATM applications in 2020+


UT Key Design Drivers

• Affordable for all IFR aircraft- Equipage cost should be comparable to nowadays IFR equipage For small GA needs to be in the order of several thousands of EUR

- For aircraft already equipped with datalink and satcom systems, the impact on existing avionics need to be minimized Ideally just SW upgrades of existing equipment and as little HW

modifications as possible- Communication Standard designed to allow low cost avionics Low gain antenna, single carrier transmission, no forced air cooling…

- For non-equipped aircraft (small GA) we need extremely simplified, small and cheap solution Limited features, services, simple HMI…

- Public funding reduces avionic supplier investments non-recurring cost element reduced

- The core technology (waveform, core HW elements…) should be developed once and reused across more products



• Coexistence with existing and future COM radios- Integration with future Inmarsat satcom avionics desirable- For future aircraft possible integration with other COM radios Substantial modification of aircraft radios and COM architecture Addressed in SESAR 9.44

- Via coordination with SESAR 9.44 and possibly other projects Iris waveform is expected to become part of future flexible radio products

• Mixed Development Assurance Levels (DAL)- Objective is to minimize amount of SW and HW which needs to

be designed above DAL D The need for DAL-C datalink radios is yet to be confirmed, but obviously it

doesn’t make sense to have e.g. ATN/OSI specific parts of the ANTARES protocol stack at DAL-C when ATN/OSI itself is only DAL-D.

- Avoid or absolutely minimize need for recertification of already existing SW and HW



• Technically suitable for all IFR aircraft- Different limitations for different aircraft Size, weight and form factor constraints (25x15x10cm / <4kg for small GA) Absence of forced air cooling HPA design constraints Antenna size and location constraints small low gain antenna needed Integration with existing avionics

“Standalone” product for low‐end GA retrofit

LRU type of product for today’s high‐end GA

Number of substantially different products needed

SDU DLNA or IPLD

SW hosted on the future SDR platform+

dedicated satcom antenna unitSESAR 9.44


UT Architecture Options

• Numerous options for split between SDU in the avionics bay and the “Antenna Unit” near the antenna- Different options may be suitable for different aircraft

Diplexer LNA RF_RXRF to IF down conversion

ADC+ optional preproc.

HPA RF_TxIF to RF up conversion

ANT

Ant. Unit

ANTARES IF signal Processor (L1 and L2)

Avionics processor and interfaces

SDU

RF head control signals

DAC+ optional preproc.

Diplexer LNA RF_RXRF to IF down conversion

ADC+ optional preproc.

HPA RF_TxIF to RF up conversion

ANT

Ant. Unit

ANTARES IF signal Processor (L1 and L2)

Avionics processor and interfaces

SDU

DAC+ optional preproc.

Future radio architecture with “smart” Antenna Unit

Classic Arinc satcom architecture


UT Prototype Status

• Accomplished until today:- COTS SDR prototyping platform selected and demonstrated- Control interface for the platform developed and tested- UT Prototype architecture partially defined Detailed functional architecture and HW/SW allocation for ANTARES L1 Preliminary functional architecture for L2

- Key physical layer algorithms designed, tested and partially implemented Synchronization, equalization, demodulation, LDPC decoder, TCC

encoder… ibd [SysML Internal Block] L1 Tx [L1 Tx Functional Architecture]

IN

RF_OUT

CTRLL1 TxIN

RF_OUT

CTRL

CTRL_OUT

CTRL_INPHY AdaptationCTRL_OUT

CTRL_IN

DATA_INAUX_IN

CTRL

Spreading DATA_INAUX_IN

CTRL

CTRL

Add CRC-32CTRL

CTRL

ScramblerCTRL

CTRL

FEC EncoderCTRL

CTRL

Bit InterleaverCTRL

CTRL

PHY Framing (PHF)CTRL

CTRL

Modulator

CTRL

Tx RF Front-End

UTP Top Level Functional Hierarchy

CTRLAuxilliary Channel

CTRL

«flowSpecification»PHA-INT Control

SOF,EOF

«flowSpecification»BURST_CONFIG

«flowSpecification»RTN_CORRECTIONS

CHIP_CLK

BIT_CLK

BIT_CLK

«flowSpecification»MOD_OUT

SOF,EOF

«flowSpecification»RTN_PLFRAME

CONFIG_ID

SOF,EOF

«flowSpecification»RTN_ACH

SOF,EOF

CHIP_CLK

DATA_READY

«flowSpecification»RTN_PSDU

«flowSpecification»RF_OUT

«flowSpecification»RTN_DD,RTN_BB_DATAFIELD

«flowSpecification»RTN_BBFRAME

«flowSpecification»RTN_S_BBFRAME

«flowSpecification»RTN_FECFRAME

«flowSpecification»RTN_DCH

«flowSpecification»RTN_XFRAME

ibd [SysML Internal Block] L1 Rx [L1 Rx Functional Architecture]

OUT

RF_IN

CTRL

TEST

L1 RxOUT

RF_IN

CTRL

TEST

Rx RF Front-End

IN

CTRLOUT Deinterleaver

IN

CTRLOUT

OUT CTRL_OUT

CTRL_ININ

FEC DecoderOUT CTRL_OUT

CTRL_ININ

OUT

IN CTRL_IN

CTRL_OUTDescramblerOUT

IN CTRL_IN

CTRL_OUT

IN

OUT CTRL_OUT

CTRL_IN

Check CRC-32

IN

OUT CTRL_OUT

CTRL_IN

OUT

IN CTRL_IN

PHY adaptationOUT

IN CTRL_IN

UTP Top Level Functional Hierarchy

INCTRL_IN

OUT

dem1 : DemodulatorINCTRL_IN

OUT

INCTRL_IN

OUT

dem2 : DemodulatorINCTRL_IN

OUT

INCTRL_IN

OUT

demN : DemodulatorINCTRL_IN

OUT

Air Interface Top Level Data Flows

OUT

INfb1 : I_XFRAME buffer

OUT

IN

OUT

INfb2 : I_XFRAME buffer

OUT

IN

OUT

INfbN : I_XFRAME buffer

OUT

IN

L1 Rx Internal Flows

CNT

CTRL

L1 PER counter

CNT

CTRL

«flowSpecification»MODCOD_ID,FWD_I_XFRAME



«flowSpecification»FEC-in Control

«flowSpecification»FWD_FECFRAME

«flowSpecification»FEC-out Control

«flowSpecification»FEC-out Control

«flowSpecification»FWD_DD,FWD_BB_DATAFIELD

«flowSpecification»FWD_PPDU

«flowSpecification»FWD_BBFRAME

BURST_DET

L1_PER

FEC_FAIL,CRC_OK

«flowSpecification»CRC-out Control

«flowSpecification»FWD_PSDU,CHANNEL_ID


UT Prototype – Next Steps

• Ongoing and near term activities- Consolidate the VTB and UT prototype specifications- Implement the L1 algorithms on target platform FPGA/DSP- Define the detailed L2 SW architecture- High efficiency HPA prototype development Single carrier transmission relaxes the requirements compared to

Inmarsat avionics – this needs to be exploited in order to deliver viable products suitable for small GA.

• Final objectives for phase B2- Implement ANTARES L1 and L2 on the prototype- Perform in-house testing At this stage of system development limited by absence of a

dedicated ANTARES test equipment- Support integration of the UT Prototype in the VTB and

execution of the CS testing


Phase B2 Outcomes

• Prototype development is the major objective of this phase

• Additional objectives- Draft the “technical specifications” for the future UT product Scope comparable to MOPS – shall serve as baseline for future

standardization- Refine the supporting studies performed in previous phases Architecture analysis Electronics design analysis (primarily HPA) Interference analysisCost analysis Standardization roadmap definition


UT Development Timeline

2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024

ANTARES ph. BLab prototype of the Iris UT waveformsIri

s

Deployment supportUT TRL6Flight-worthy Iris UT waveform

Phase 1Avionic SDR concept definitionS9

.44 Phase 2

Avionic SDR platform prototype development

Product developmentTarget A/C selection, certification

Target platform

TRL6 avionic Iris SDR prototypeReady for experimental flight tests

SESAR 2Clean Sky 2

Indu

stry Standardization

At least mature version of MOPS (if not final) is needed to start the product development

TRL3-4

Questions?

honeywell advanced technologies europe - esa artes terminal j.stecha.pdf · honeywell advanced...

Documents