Le standard AVENUE. Un exemple d interopérabilité pour les plate-formes temps-réel de contrôle du trafic aérien

Transcription

1 EUROCONTROL Le standard AVENUE Un exemple d interopérabilité pour les plate-formes temps-réel de contrôle du trafic aérien Pierre-Yves GAUTHIER FORUM Systèmes & Logiciels pour les NTIC dans le Transport «Intégration & Interopérabilité» Eurocontrol / Brétigny-sur-Orge, jeudi 19 janvier

2 Interopérabilité dans l ATC Constat Systèmes ATC européens hétérogènes -> relativement peu d interopérabilité: Fournisseurs industriels multiples (technologies et conception variant de l un à l autre) Spécificités propres à chaque pays (procédures et fonctionnalités attendues du système) Différence de modernité des systèmes (cycle de remplacement des systèmes non synchronisé entre pays) Quelques standards d interopérabilité existants: OLDI/SYSCO (coordination inter-centres) ASTERIX (données de surveillance: radar) 2

3 Constraintes Quelques contraintes liées à l hétérogénéité des systèmes ATC européens: Lenteur dans le déploiement de nouveaux concepts/outils (de l idée à l utilisation) Adaptations multiples de ces nouveaux concepts/outils aux différents systèmes (coûts d investissement global important) Absence d environnement de référence pour l évaluation des nouveaux concepts/outils Problème de développement de méthodes de travail Européenne (Collaborative Decision Process) Faible optimisation des ressources (coûts de fonctionnement européen élevés) 3

4 Apport de plus d intéropérabilité (1/2) Plus d interopérabilité (via la définition de standards) dans les systèmes ATC européens signifierait: Plus de granularité dans les divers composants des systèmes ATC Meilleure intégration/adaptation de nouveaux outils Évolution progressive du système dans le temps Possibilité de partager (mettre en commun) des composants réduction des coûts (production, maintenance) Élargissement de l éventail de fournisseurs possibles réduction des coûts (concurrence) Optimisation/Réduction des coûts globaux de fonctionnement 4

5 Apport de plus d interopérabilité (2/2) Plus d interopérabilité (via la définition de standards) dans les systèmes ATC européens signifierait: Possibilité d évaluer les nouveaux concepts/outils dans des environnements de référence Possibilité d évaluer des composants (ou sous-systèmes) plutôt que des systèmes entiers Test de composants proposés par plusieurs fournisseurs (dans un environnement technique identique) Interchangeabilité de composants (plug and play) Le Standard AVENUE: Définition d une architecture logique pour un environnement de référence (plateforme de validation) premier pas vers plus d interopérabilité 5

6 AVENUE European Commission Project (launched in 1997) Construct a European ATM Validation Platform European agreement on IDL interfaces 1st Platform built using the OASIS middleware (built by EEC in the context of Avenue and based on PATIO, project of the Commission) Industry Driven Validate operational concepts Harmonize system interfaces Provide practical system solutions 6

7 AVENUE Standard Architecture Standard IDL (ATM industry driven EC project) Aiming at standardising ATM platform architecture in Europe Favoring plug-and-play for exchanging component 7

8 AVENUE An ATM Validation Environment for Use Towards EATMS The Partners Airsys ATM FR Bagneux SOFREAVIA Paris DERA Malvern&Bedford Airsys ATM UK Chessington NLR Amsterdam ISR Paris DFS Frankfurt Eurocontrol Brétigny Alenia Marconi Rome INDRA Madrid Aena ISDEFE Madrid Isdefe Ingeniería de Sistemas AENA Madrid AEROSPATIALE Toulouse CENA Toulouse EC DG VII Transport Programme (4.1.3/24A) Contract : AI-97-SC

9 AVENUE standard architecture Standard IDL (ATM industry driven EC project) Aiming at standardising ATM platform architecture in Europe Favoring plug-and-play for exchanging component Does not impose a particular physical implementation focus on (ATC) business only 9

10 Scope of AVENUE logical model FDP View AS View AGDC View 10

11 AVENUE standard architecture Standard IDL (ATM industry driven EC project) Aiming at standardising ATM platform architecture in Europe Favoring plug-and-play for exchanging component Does not impose a particular physical implementation focus on (ATC) business only Library of public IDL interfaces defining: ATC domain types (Data Dictionary) ATC services (logical methods and events) Defined in IDL (Interface Definition Language) 11

12 AVENUE Data Dictionary BASIC layer Time types (AvTim) Standard types (AvStd) BASIC ATC layer BasicAirspaceModelTypes (AvBamt) BasicAircraftTypes (AvBact) BasicSystemUnitsTypes (AbBsut) BasicRadarTypes (AvBrat) BasicFlightPlanTypes (AvBfpt) Flight related types Aircraft related types AS related types Conflict related types AGDC related types Common Flight Types (AvCflgt) AircraftTypes (AvAirct) Radar Plots types (AvRadpt) Conflict Monitoring Types (AvConft) Common AGDC types (AvCagdt) Coordination Types (AvCoort) ADS-B types (AvAdsbt) ADS-C types (AvAdsct) ATC layer Constraint Types (AvCstrt) Deviation Types (AvDevit) Sectorisation Types (AvSectt) Flight Plan Types (AvFlplt) Trajectory Types (AvTrajt) Meteo related types Traffic Info. Service types (AvTist) MeteoTypes (AvWeatt) Surveillance Tracks types (AvTrakt) GGDC related types GGDC types (AvCommt) Airspace related types Common Airspace types (AvCaist) Airspace Types (AvAirst) Approach Types (AvAppt) 12

13 AVENUE Interfaces Flight related APIs Corelation Manager (AvCorlm) Constraint Manager (AvCtrm) Initial Flight Plan Mngr (AvIfpm) Sectorisation Manager (AvSectm) Route Manager (AvRtem) Environment related APIs Traj. Predictor Mngr (AvTpm) Aircraft Performance (AvAcr) Coordination Manager (AvCdnm) Oceanic Clearance (AvOclm) Airspace (AvAsp) Weather (AvWea) SSR code Manager (AvSsrm) System Flight Plan (AvSfpm) Conflict related APIs Conflict and SNETS (AvConf) AS related APIs Air Surveillance (AvAs) Simulator related APIs FPM related APIs Flight Path Monitor (AvFpm) Air Borne Simulator (AvAbs) Radar Emulator (AvRe) Flight Plan Generator (AvFpg) AGDC related APIs ADS-C (AvAdsc) AMAN/DMAN related APIs Arrival Manager (AvAman) Data Link Capability (AvDlic) Flight Plan Consistency (AvFlipcy) Departure Manager (AvDman) Terminal Manager (AvTma) CPDLC (AvCpdlc) GGDC related APIs GGDC (AvGgdc) 13

14 Functional Model overview Aircraft data IPAS AADC Remote pseudopilot Simulation exercise Results ADS-B ACAS Remote pseudo-pilot orders plots ABS ADS-B TIS CPDLC link Air CPDLC dialog CPDLC UM A/C logon request A/C contact response ADS-C reports A/C contact request A/C logon response ADS-C requests ADS-C reports Downlink CPDLC DLIC Link status AGDC ADS-Radar tracks Ground CPDLC dialog Uplink CPDLC ADS-C requests ADS-C reports ADS-C session control (trajectory request) SFPL flight info FIR exit point FPL termination ADS-C ground report (aircraft trajectory) Airspace data CWP ASP Airspace data Weather data WEA Restricted areas Aircraft data Flights conflicts Trajectories ACR MTCD DMAN PREP off-line geographical data R/A ADS_B server Significant points passed Navigation support Deviations STCA MSAW CWP commands SFPL data FLIPCY warnings FDPD DMAN constraints SFPL data AMAN constraints SFPL data IFPL data AMAN Traffic SNET Significant points Trajectories IFPL requests IFPL data FPG RE ADS-B reports ADS-B session control Radar plots AS ADS-Radar tracks ADS-Radar tracks FPM Flight progressions Trajectories deviations Trajectories Flight activation Slots data Received messages Message to be sent GGDC ADS-Radar tracks TACT 14 Wind data Aircraft data

15 Example of Avenue Logical Description : Fdpd.Tp : Ggdc : Environment.Airspace : Environment.Aircraft TrajectoryFP AirspaceData RunwayStateChangeEvent DepartureSequenceMessage TMAData RunwayAllocationStrategy : Fdpd.Ifp InitialFP ArrivalSequenceMessage AircraftData : Environment.Weather CoordinationInfoFP : Aman AirportWeather MeteoProfile : Fdpd.Cdn AmanOrders AmanConstraintPoint <<external>> : Prep offline subsystem ArrivalSequence AmanAdvisory : Cwp 15

16 Examples of Avenue IDLs Data Dictionary examples // types of aircraft. enum AircraftType { JET, TURBO, LGHT, UNKNOWN_AIRCRAFT_TYPE }; // Definitions related to Navigation Points: typedef char NavigationPointName[5]; // const NavigationPointName NULL_NAVIGATION_POINT_NAME = -----"; Logical method and service examples void create_sfpl_from_route ( in AvFlplt::InitialFP ifp, in AvFlplt::BasicRouteFP route, out AvFpgTypes::FpgReportCode report_code); struct Event { AvBfpt::FlightKey AvFpmTypes::Progression::FlightProgression flight; flight_progression}; 16

17 From AVENUE to a platform instance Instance independent : Logical Model (AVENUE) Functional Model definition Definition of logical interfaces (API) Logical model can be reused and evolve independently of technology Instance dependent : Physical Model (Ex: ESCAPE) Components Interface Definition (CDL) Dynamic Model of Execution Containers (generated) 17

18 ESCAPE Platform Eurocontrol Simulation Capability And Platform for Experimentation. Emulates an ATC/ATM environment with the air traffic controller as the main key player Complete simulated environment Shadow-mode (connected to live data) Mainly used to support: a wide range of R&D projects (Eurocontrol, EC) Organisational ATC simulations (member states) Controller training (Luxembourg, Maastricht) Already presented in NTIC Simulations et Transports in January

19 Some ESCAPE sub-systems Aircraft Simulator Datalink System Ground System Controller Working Positions 19

20 Some Ground FDPS Components Trajectory Predictor Flight Manager Flight Plan Generator OASIS middleware SYSCO Airspace Server Aircraft Data Server ETC Granularity: for the whole platform, there is more than 50 different types of CORBA components, mostly driven by Avenue 20

21 From AVENUE to a platform instance Instance independent : Logical Model (AVENUE) Functional Model definition Definition of logical interfaces (API) Logical model can be reused and evolve independently of technology Instance dependent : Physical Model (Ex: ESCAPE) Components Interface Definition (CDL) Dynamic Model of Execution Containers (generated) 21

22 ESCAPE Component An ESCAPE Component is defined/implemented through its CDL. A CDL stipulates: The services the component provides The events it publishes The services it uses The events it consumes Defined in CDL (component description language) CORBA 3 concept 22

23 AVENUE IDL and ESCAPE CDL relationships Provides X AVENUE Module A Interface X Interface Y Provides Y Provides Z ESCAPE Comp. 1 AVENUE Module B Interface Z Uses X ESCAPE Comp. 2 23

24 UML to Support Interoperability A UML model of ESCAPE physical instance to detail the dynamic use of Avenue UCR229.2-Input Aman Sequence Orders UCR Dispatch AceP4d : AceAman Re-evaluate : AceFM : AceGgdc : AceCWP sequence Component based on CDL UCR Dispatch AceRte If allocated runway(s) has/have been changed UCR Update FP UCR229.4-Input Aman Slot Orders input_strategic_order(in AvBfpt::FlightKey, in AvCstrt::StrategicOrder, out AvCtrmTypes::CtrmReportCode) AvCstrt::StrategicOrderKind is - ARRIVAL_STRATEGIC_ORDER UCR229.5-Input Aman Flight Orders send_aman_dman_message(out AvGgdcTypes::GgdcReportCode, in AvSeqmt::AmanDmanMessage) I f inter-centre data have changed Av_IDL.API.Aman.AceAmanEvents.SequenceEvent.Event( ) use of Avenue Services and Events based on CDL descriptions 24

25 ESCAPE Component Structure CORBA IDL Generated Code Wrapping Wrapping Code Code Component Isolates generated IDL Core from & IDL Templates Implementation for Ada95 Client Types and Server Implementations C, C++, java 25

26 ESCAPE Component Structure CORBA IDL Generated Code Wrapping Wrapping Code Code Component Isolates generated IDL Core from & IDL Templates Implementation for Ada95 Client Types and Server Implementations C, C++, java 26

27 Use of Interoperability in G2G Project SUP OASIS AGDC FS OI EM DIS THALES TP ASP TP WEA FPG ACR IAS FM SNET ENAV AMAN AMAN SFPD GGDC TDM INDRA OpSup INDRA EONS CWP INDRA EONS ARTAS Asterix Audio LAN ERGO SYSCO 27

28 Middleware Interoperability Application Layer (ESCAPE Component) Avenue IDL Application Layer (Any Component From other platform) GenericPlatform Services Corba Services Corba Services Avenue IDL ORB (ORBIX) OASIS IIOP Any Other ORB (for example TAO) 28

29 ESCAPE instances in Europe Malmö G2G FI Maastricht Eur NO SE EE RU Brussels Eur Luxembourg Eur Brétigny Eur Budapest Eur Rome G2G Séville G2G PT IE ES GB FR NL BE LU CH M C DK DE IT LV LT BY PL CZ SK AT HU SI HR RO BH S-M BG MK AL GR MD UA TR KZ GEAM AZ Naples SICTA MA DZ TN MT CY 29

30 État Actuel du standard AVENUE Le standard a été amélioré par le projet de la Commission «Gate To Gate» Il est connu de l essentiel des acteurs de l ATC en Europe Il n est pas (encore?) utilisé par les systèmes industriels opérationnels mais il est très fortement recommandé par la Commission pour tous les projets de développement de plateforme ATC dans le cadre des FrameWork Programmes 6 et 7 30

31 EUROCONTROL Thank you for listening For further information, you may visit 31