Avenue Omg

Download Avenue Omg

Post on 12-Jan-2015

598 views

Category:

Technology

0 download

Embed Size (px)

DESCRIPTION

 

TRANSCRIPT

<ul><li> 1. AVENUEATM Validation ENvironment for Use towards EATMSTRANSPORT RESEARCH PROGRAMME DG7 - TRANSPORT/AIR TASK N 4.1.3/24A OMG transportation16 November 1999 </li></ul> <p> 2. Contents Avenue Overview Technical Overview CCM OASIS (Open Architecture for SImulation System) andPLUG(Presentation layer Universal Generator) System Development Approach Logical Model Component Interface Definition (CIDs) and APIs Component interconnection (first instance of the system). 3. Contents Avenue Overview Technical Overview CCM OASIS and PLUG System Development Approach Logical Model Component Interface Definition (CIDs) and APIs Component interconnection (first instance of the system). 4. AVENUEEuropean Union Project (4th Framework) Construct a European ATM Validation Platform European agreement on IDL interfaces 1st Platform built using OASIS Industry Driven Validate operational concepts Harmonize system interfaces Provide practical system solutions 5. AVENUE PartnersAENA Aeropuertos Espanoles y Navegacion Aerea (E) Arospatiale Socit Nationale Industrielle (F) Airsys ATM SA (F), ATM UK Ltd (GB) Alcatel ISRInformatique de Systmes et rseaux (F) ALENIA Alenia Difesa, un'Azienda Finmeccanica SpA (I) DERA Defense Evaluation and Research Agency (GB) DFSDeutsche Flugsicherung GmbH (D) EECEUROCONTROL Experimental Centre INDRADTD, S.A (E) ISDEFE Ingeniera de Sistemas para la Defensa de Espana (E) NLRNationaal Lucht- en Ruimtevaartlaboratorium (NL) SOFREAVIA Socit Franaise d'Etudes et de Ralisations d'Equipements Aronautiques (F) 6. Main design areasInfrastructure (middleware, recording, configuration etc.)CORBA Component ModelDeveloped by EEC in line with standards : OASISSupport by AIRSYS tools : PLUGApplication architectureIDL specification Independent of physical architecture 7. AVENUE component model Component context events Component transactional Application tech sup propertiesRecording ContainerEvents Connect SupTighter rulesIncreasing OASIS services NSEDS IRPXSPcomplexityCORBA services CORBAORB 8. Contents Avenue Overview Technical Overview CCM OASIS and PLUG System Development Approach Logical Model Component Interface Definition (CIDs) Component interconnection (first instance of the system). 9. CORBA ComponentsIndustry drivenbased on experience of building complexdistributed systemsfollows other emerging models (EJB, JavaBeans)Major contentComponent extensions to IDLContainer / Component Model 10. Component IDL (IDL3) Extension to IDL packaging language Define a component in terms of...Offered functionalityinterfaces providedevents emitted Dependenciesdistant interfaces requiredevents consumed Configuration attributes 11. Component IDLIDL3 provides architecture clarity natural connectivity dependency visibility 12. Components need containerscontainer handles, component interconnection event issues transactions config / packaging issues other functionsComponent is isolated fromthe underlying architecture.this is a standard &amp; formalway of creating wrappers. 13. Component/Container interaction Component interacts with container Container interacts with Componentother container Components exchange information 14. Component/ContainersContainers are like wrappersthat isolate/protect the core function from thearchitecture of the platformprovide a neutral and simple interface to thecore function.Tighten the rules for developersbut also...can provide additional added value functions,such as data recording, data managementcan be automatically generated. E.g for a different architecture we need only use a different code generator. 15. Component IDLIDL3 is parsed, producing : IDL3 an IDL interfacedefines the what and notthe howimplemented by Parsercomponent developersmiddleware independentcontainer codeprovides the vendorContainerspecific how IDL 16. Contents Avenue Overview Technical Overview CCM OASIS and PLUG System Development Approach Logical Model Component Interface Definition (CIDs) Component interconnection (first instance of the system). 17. OASIS (Open Architecture for SImulation System)CORBA middlewarelarge scale simulation and pre-operationalvalidationBuilt on ORBIX +.. lifecycle publish subscribe data management supervision supports ADA83, C++ and JAVA 18. Technical framework Component context events Component transactional Application tech sup propertiesRecording ContainerEvents Connect SupTighter rules OASIS services NSEDS IRPXSP CORBA services CORBAORB 19. OASIS in Avenue Standard within EUROCONTROLused by external partnersselected for AVENUE but upgradedmodified to CORBA component/containermodel.Container uses OASIS servicesCode generation (PLUG) 20. PLUG Code Generation Toolkit : TDL parser Plug :Presentation layer Universal GeneratorTDL : Template Description LanguageOASIS IDL 3 to IDL 2 Template TemplateIDL3 TDLIDLParser ParserContainer IDL2 21. Contents Avenue Overview Technical Overview CCM OASIS and PLUG System Development Approach Logical Model Component Interface Definition (CIDs) Component interconnection (first instance of the system). 22. Logical architecture Logical modules derived from CMS (common modular simulator) Daarwin (Distributed ATM Architecture Integrating RNAV, Workstations, Tools and Networks)ESCAPE (EUROCONTROL Simulation Capabilities And Platform for Experimentation) PATIO for ATM Tools Integration up to Pre-operation)(Platform Defined in SSDD (system/segment design document)Interface definitions in terms of API(Provided interfaces in IDL). 23. Decomposition is based on 3 viewsFDP ViewABS/AS ViewAGDC View 24. AGDCFDP ViewGGDCSFPL Flight infoFPGFir Exit PointFPL TerminationTACTADS Session Control (trajectory request) Messages to be sent Flight Validity IFPL dataReceived ADS-C gnd reportmessages (Aircraft Trajectory) IFPL requests ACR IFPL dataFlightActivation AS Slots dataAircraft data ADS-Radar TracksASP TrajectoriesAirspace data FDPDFPMFlight positionFlight progressionTrajectory deviationsW eather data Trajectories W EADMAN constraints Flight Conflicts SFPL data SFPL dataSFPL dataFLIPCY warningM TCD TrajectoriesAMAN constraintsCW P commands DM AN AMAN SNETCW P 25. Airborne/Surveillance View ACRRadaremulatorAircraft Data Raw plots A/C Logon Request A/C Contact ResponseABS ADS-C report AFPL A/C Logon ResponseA/C Contact Request ADS-B CPDLC Link management TIS Air CPDLC dialogue mngmnt AGDCCPDLC UM &amp; DMADS-B server 26. Air-ground data link viewCWPGround CPDLC dialogue mngmnt Link statusABSDownlink CPDLC messagesDLIC warning A/c Logon Response A/c Contact Request FLIPCY warningUplink CPDLC A/c Logon Request messages A/C Contact Response ADS-C reportAFPL CPDLC link management Air CPDLC dialogue mngmnt AGDC CPDLC UM &amp; DMADS-C Session controlADS-C gnd report (Aircraft TrajectoryADS-C gnd Report AS SFPL Flight info ADS-C Session control Fir Exit Point FPL TerminationADS-C gnd Report ADS Session Control (trajectory request) Flight ValidityWEAFDPD 27. Modules are decomposed further into sub modules IFPM, supporting the Initial Flight Plan Information Management and the IFPL dataset, RTEM, supporting the Route Management and the Route dataset, CTRM, supporting the ATC Constraints Management and the Constraints dataset, TP, supporting the Trajectory Predictor and the Trajectory dataset, CDNM, supporting the Co-ordination Management and the Traversed Sector List and the Co-ordination Sector List datasets. SSRM, supporting the SSR Code Management and the SSR Code dataset, NTFM, supporting the Notification Management and the Notified Sector List dataset, CMCM, supporting the Civil/Military Crossings Management and the Civil/Military Crossings dataset, OCLM, supporting the Oceanic Clearance Management and the Oceanic Clearance dataset,CORL, supporting the Track/Callsign Correlation function and the Correlation dataset, and FLIPCY, supporting the Flight Plan Consistency function. No additional datasets are owned by this module. 28. Example: Trajectory Predictor Context WEA SFPL ACR Weather Data IFPL, Route, CTRMConstraintsAircraft Data Compute Trajectory TPCompute TrajectoryCDNM TrajectoryFlight position, Flight progression,Trajectory deviations SFPL FPM 29. APIsAn API is defined for each module.No mapping to physical componentsNo implementation detailsJust a large number of services in CORBAIDL covering the ATM functionsFirst level (main) of interfaceharmonization 30. Example: Weather API#include #include component AvWea{//provided interfaces provides AvWeaServices::Services process; // processing services// Emitted events. publishes AvWeaEvents::Event sigmet_event;};#endif // AV_WEA_MD_INCLUDED 31. Contents Avenue Overview Technical Overview CCM OASIS and PLUG System Development Approach Logical Model Component Interface Definition (CIDs) Component interconnection (first instance of the system). 32. ComponentsModules are mapped to physical peercomponentsInterfaces defined in CIDs (provided andrequired interfaces in IDL) Required services Provided services 33. Relationship between API and CID Provides XRequires A Provides XModule Provides Y Module is allocated to Provides Y physical component/s Requires B API maps directly to provided interface of CIDRequired interface is added to CID 34. Contents Avenue Overview Technical Overview CCM OASIS and PLUG System Development Approach Logical Model Component Interface Definition (CIDs) Component interconnection (first instance of the system). 35. The first instance In parallel with module to componentmapping is the physical architectureconnecting components togetherstatic &amp; dynamic modeling of the whole 36. The Avenue 1st InstanceGroundASAS ASASATN Router EOLIA DATAMASS ECSADSPARTAS DLICFLIPCY ADS-CFUSION X XX ABSRADAR DATALINKSURVEILLANCE CPDLC GATEWAY EMULATOR GATEWAY GATEWAY JANEAVENUE Middleware, Arcades Recording and TMCS supervision DIS/HLA XXXXSimulators DataEONSTP interconexion FPM CPServers..... (SIMINGA). SACTA/FD XX Private protocol RecordinData P (Asterix) gpreparation FilesAVENUE APIFilesXXX Private protocol(X.25, OLDI/SYSCO)AVENUE 1stARISTOTEEVA IPASInstanceOff-lineComponent </p>