ATN 2001, London - 18 Sep 01 1 PETAL II and II Extension Maastricht Multi-stack Implementation...

ATN 2001, London - 18 Sep 01 1EUROCONTROL MAASTRICT UACEUROCONTROL MAASTRICT UAC

PETAL II and II ExtensionPETAL II and II ExtensionMaastricht Multi-stack Maastricht Multi-stack

ImplementationImplementationLessons LearntLessons Learnt

Prepared by Gustaaf Janssens/Konrad Koebe

Maastricht UAC


TOPICSTOPICS

What Do We Mean by Multi-Stack? Why Multi-Stack ? What Are Multi-Stack Design Considerations ? MUAC Ground Architecture MUAC Schedule Achievements How Do We Test ? What Are Our Lessons Learnt ? Next Steps Conclusions


What Do We Mean by Multi-Stack ?What Do We Mean by Multi-Stack ?

Accommodating Existing Specifications for AGDL NEAN Extension (Prototype VDL4) FANS-1/A ATN SARPs

Aim Communicate With Any Avionics Equipment Using

One Of The Specifications


Why Multi-Stack ?Why Multi-Stack ?

PETAL-II Project Needs for MUAC Operations - Hide AGDL Technology for User

Operational Requirements Validation Independent From AGDL Technology

Quick Implementation Project Has to Compete With Daily Life Activities at

an Operational Centre Take Advantage of Existing Operational Avionics

Equipment Encourage ATN SARPs based Air and Ground

Implementations


Design Constraints (1)Design Constraints (1) Fit In MUAC Existing Ground Structure

HMI, FDPS, Gateways Add Functionality in HMI and FDPS, Add AGDL Gateway

HMI Add to Normal Controller Presentation and Interface

FDPS Based on ATN SARPs Ground End User Applications

Definitions AGDL Gateway

Single Access Point for FDPS Access Points for Underlying AGDL Technologies


Design Constraints (2)Design Constraints (2)

Evolutionary Development Next Step Building on Results of Predecessor


Maastricht Multi-stack GROUND End System (1)Maastricht Multi-stack GROUND End System (1)

Controller

HMIController

HMIController

HMIController

HMI

Flight Data Processing SystemATM Services

NEAN GWY

NEAN

9705BER

P2GW (PETAL 2 GATEWAY)

FANS-1/A GWY

SITA

ProATN ES9705PER

VDL2-ATNProATNROUTER


Maastricht Multi-stack GROUND End System (2)Maastricht Multi-stack GROUND End System (2)

ControllerHMI

ControllerHMI

ControllerHMI

ControllerHMI

Flight Data Processing System- Flight plan / address association- ATN SARPs (ICAO 9705) CM, ADS, CPDLC- All datalink service logic and dialogue control

P2FEP

NFEP- Aircraft address/state- ASE emulation CM, CPDLC, ADS- Conv. to NEAN specs.

FAFEP- Aircraft address/state- ASE emulation CM, CPDLC, ADS- Conv. To FANS specs

ALLA- P2PI- Aircraft address/state- BER-PER Conversion.

ProATN - ASEs: CM, CPDLC, ADS - ATN Router

FANS-1/A Gateway

NEANServer

9705BER

9705PER

P2GW


Design Constraints (3)Design Constraints (3)

P2GW Holds and Manages Addressing Data Buffers FDPS from Unexpected

communications MADAP Msg= {Msg ID, Infra

ID+24bits+FID+Reg.Mark+9705-BER-Msg} Hides Communication and Network Specifics from

FDPS


Design Constraints (4) Design Constraints (4) AGDL Applications implemented

CM, ADS, CPDLC

FDPS AGDL Services Using these Applications CM: DLIC AcceptanceCM: DLIC Acceptance ADS: ADS demand (FLIPCY), ADS periodic (CAP)ADS: ADS demand (FLIPCY), ADS periodic (CAP) CPDLC: (ACL, ACM, AMC)CPDLC: (ACL, ACM, AMC)

FDPS Functionality Used for AGDLFDPS Functionality Used for AGDL Manages Flight plan Operational StatusManages Flight plan Operational Status

DLIC acceptance and ADS, CPDLC requestsDLIC acceptance and ADS, CPDLC requests Terminates CPDLC, ADSTerminates CPDLC, ADS


Design Constraints (5) Design Constraints (5) Controller AuthorisationController Authorisation

Only Controlling Sector handles CPDLCOnly Controlling Sector handles CPDLC FDP Controls Sequence ExtractionFDP Controls Sequence Extraction

Next internal or external sector (NDA) identitiesNext internal or external sector (NDA) identities Controls Automatic Flight Plan ActionControls Automatic Flight Plan Action

CMContact at OLDI ABI eventCMContact at OLDI ABI event CPDLC (NDA) at OLDI ACT eventCPDLC (NDA) at OLDI ACT event

Extracts Information for Controller HMIExtracts Information for Controller HMI radar picture and tabular displayradar picture and tabular display

Provides Authorised Input Sequences and Provides Authorised Input Sequences and Guidance on Controller HMIGuidance on Controller HMI


MUAC Schedule Achievements (1)MUAC Schedule Achievements (1)

NEAN IN 4/98 FANS 1/A 2/99 P2GW - BAC1/11 using

ATIF/SATCOM, P-II message set. 5/00 MC-P2GW-BAC1/11 Flight using

ATIF/SATCOM, P-IIe message set. 9/00 Application Testing: FDPS-Avionics 11/00 FDPS, P2GW Ready 3/01


MUAC Schedule Achievements (2)MUAC Schedule Achievements (2)

FANS1/A ONLINE: P-IIe Message set 4/01 NEAN OUT 4/01 CERTification Testing Support 5/01 Non Revenue Flights 6/01 MUAC-RUAC Shadow Flight 7/01 Revenue Flight 8/01


MUAC Technical Achievements (1)MUAC Technical Achievements (1)

ICAO 9705 Compliant FDPS Implementation Usage of ATN, FANS1/A and Prototype VDL4 First Fully Certified ATN avionics CPDLC Flights May1998-June2001 = 8455

(FANS/NEAN) Test Infrastructure Test Methodology


How Do We Test (1) ?How Do We Test (1) ? Test Approach

Local Tests HMI, FDPS, P2GW

End-to-End Application Tests: FDPS- Other ATC Centre - Avionics

• grounded avionics

• airborne avionics

Operational Observation

Overview of Our Test Configurations


P2GW EMUL

FAME

AGDG-FANSFDPS EMUL

AFAME

PSF

AGD

G ATN

NON REV


PIIe Operational ObservationPIIe Operational Observation

VDL M2

B767

P2GW

MAASTRICHT UAC Control Centre

PROATNR

PROATNEnd

SystemFDPS

LANLAN

CPDLC ServicesVIAATN/VDL Mode 2


What Are Our Lessons Learnt (1) ?What Are Our Lessons Learnt (1) ? Step by Step Implementation

NEAN Validation of Technical Concept and Architecture

FANS 1/A Validation of ‘Multi Stack’ Concept

• HMI, FDPS Independent From AGDL Technology

ATN SARPs Validation of SARPs Compliant Implementation Additional Operational Messages and Stack Functions

Lessons More Testing Effort due to Regression Testing ?


What Are Our Lessons Learnt (2) ?What Are Our Lessons Learnt (2) ?

ATN SARPs Implementation Tests Early Feedback = Early Application Error Detection

and Correction BAC1-11 Test Flights ATIF-ground Testing End-to-End Application testing

No Application Errors Detected During CERT, Non-Revenue and Revenue Flights


What Are Our Lessons Learnt (3) ?What Are Our Lessons Learnt (3) ?

Local Tests as Much as Possible Avionics Emulators Test Automation Protocol Test facilities

External Testing is Expensive Test Setup Test Execution Time Consuming

Good Test Objectives and Strategies


What Are Our Lessons Learnt (4) ?What Are Our Lessons Learnt (4) ? Future Requirements for Test Tools and Strategies

Reference Test Tools Required Available For All Implementers Common Development A lot of Tools exist. Usable to further develop ?

Reference Test Objectives and Strategies Separate Test Network Required

Connect Test Systems Intra Centre Test Avionics Tests


Next Steps (1)Next Steps (1) Complete PETAL-IIe

System Safety Assessment Document Lessons Learned Consolidate Documentation Evaluate Test Automation (GEODE)

New Project (P2L = PETAL To LINK2000+)

(in approval and initiation phase)


Next Steps (2)Next Steps (2) P2L Objectives

Maintain a State of the Art Implementation of the Existing AGDL Implementation.

Ensure Safety of all Operational Systems Increase the Number of aircraft applying AGDL

Services (FANS, ATN) Support the LINK 2000+ Project

Enabler for aircraft to equip. Enabler for other Centres Enabler for COMS Enabler for Test and Validation tools - Common

Development and Support.


CONCLUSIONCONCLUSION

MULTI STACK CONCEPT WORKS ! SERVE MORE AIRCRAFT CONNECT TO NEIGHBOUR ATC CENTRES

THANK YOU PARTNERS FOR THE COOPERATION !

ATN 2001, London - 18 Sep 01 1 PETAL II and II Extension Maastricht Multi-stack Implementation...

Documents

Transcript of ATN 2001, London - 18 Sep 01 1 PETAL II and II Extension Maastricht Multi-stack Implementation...