ACE eDEP Gateway Technical Document Design Document

Ace Edep Gateway Technical Document Design Document-Free PDF

  • Date:22 Dec 2019
  • Views:47
  • Downloads:0
  • Pages:101
  • Size:1.08 MB

Share Pdf : Ace Edep Gateway Technical Document Design Document

Download and Preview : Ace Edep Gateway Technical Document Design Document


Report CopyRight/DMCA Form For : Ace Edep Gateway Technical Document Design Document


Transcription:

ACE eDEP Gateway Reference GL AEG TR 1 3 0 Draft 1. 15 Feb 2008,Table of Contents,1 Introduction 5,1 1 Document purpose 5. 1 2 Methodology 5,1 3 Document Change History 5,1 4 Document Structure 6. 1 5 Related Documents References 6,1 6 Acronyms 7,2 Architecture 8. 2 1 Introduction 8,2 2 Logical Architecture 8,2 3 Design Options 9. 2 4 Mechanisms 11,2 5 Component Definition Language 12.
3 AEG Gateway Component 17,3 1 Introduction 17,3 2 Design Issues 17. 3 3 Gateway Design 20,3 4 Reference Mapping 20,4 Common AEG Proxy Component Features 23. 4 1 General 23,4 2 Design Issues 23,4 3 Framework 26. 5 Test Plan 27,6 Data Presentation 28,6 1 Format 28. 6 2 Guide to the Data Tables 28,6 3 Key to data type information 29.
6 4 Data Conversions 29,7 Time Server TS Proxy component 33. 7 1 General 33,7 2 Proxy Design 33,7 3 Data Analysis 34. 7 4 eDEP Modifications 34,7 5 Limitations 34,8 Initial Flight Plan IFPL Proxy component 35. Page 2 of 101, ACE eDEP Gateway Reference GL AEG TR 1 3 0 Draft 1. 15 Feb 2008,8 1 General 35,8 2 Proxy Design 35,8 3 Data Analysis 38.
8 4 eDEP Modifications 44,8 5 Limitations 44, 9 Integrated Air Surveillance IAS Proxy component 45. 9 1 General 45,9 2 Proxy Design 45,9 3 Data Analysis 48. 9 4 eDEP Modifications 51,9 5 Limitations 51,10 Flight Path Monitor FPM Proxy component 52. 10 1 General 52,10 2 Proxy Design 52,10 3 Data Analysis 57. 10 4 eDEP Modifications 59,10 5 Limitations 59,11 Flight Manager FM Proxy component 60.
11 1 General 60,11 2 Proxy Design 60,11 3 Data Analysis 63. 11 4 eDEP Modifications 74,11 5 Limitations 74,12 Pilot Manager PM component 75. 12 1 GeneRal 75,12 2 Proxy Design 75,12 3 Data Analysis 76. 12 4 eDEP Modifications 77,12 5 Limitations 77,13 Coordination Server CS Proxy component 78. 13 1 General 78,13 2 Proxy Design 78,13 3 Data Analysis 86.
13 4 eDEP Modifications 92,13 5 Limitations 92,14 Development Plan 93. Page 3 of 101, ACE eDEP Gateway Reference GL AEG TR 1 3 0 Draft 1. 15 Feb 2008, 15 Limitations Known Issues and Suggested Enhancements 94. 15 1 Limitations and Issues 94,15 2 Suggested Enhancements 97. A Annex Data Questions Answers 98,Page 4 of 101, ACE eDEP Gateway Reference GL AEG TR 1 3 0 Draft 1.
15 Feb 2008,1 INTRODUCTION,1 1 DOCUMENT PURPOSE, eDEP is a low cost lightweight web enabled ATM simulator platform offering an ideal environment for. research and advanced concept projects to rapidly prototype applications For a full description see the. Architecture Design Document reference 1 More information is also available online at. http www eurocontrol int eec public standard page ERS edep html. ACE is the latest generation of ESCAPE the EEC s ATM platform for real time simulation training and pre. operational validation For a full description see the High Level Description document reference 5 More. information is also available online at http www eurocontrol int eec public standard page ERS ace html. http www eurocontrol int eec projects projects 276 htm. eDEP is to be integrated with ACE so that eDEP can be run with high fidelity trajectories and so that it can be. used as a test tool for ACE EDEP s lightweight and flexible architecture means new versions can be made. available for new ACE releases much quicker than for traditional ACE components allowing testing to be. carried out earlier This integration is done using a gateway the ACE eDEP Gateway AEG which provides. the connections with the ACE platform and includes proxy components to replace some of the standard eDEP. components, This document defines the architecture for the AEG and the detailed design for the individual AEG. components, This document and the AEG implementation builds on an initial proof of concept integration and outline. design produced by NEOSYS reference 6,1 2 METHODOLOGY. The detailed mapping between the ACE and eDEP data types was developed after thorough examination of. both sets This was supported both by a general description of the ACE datasets from the ERIS team. responsible for ESCAPE and question and answer sessions on specific points These questions and answers. are documented in Annex A,1 3 DOCUMENT CHANGE HISTORY.
Release Author Release Date Release Description Modifications sections affected. and relevant information,1 0 M Humphrey 7 May 2004 First Release All. 1 1 M Humphrey 14 May 2004 Update following Revisions to 2 4 3 4 6 4 8 3. customer comments Additions to 11 Plan updated in 13. 1 2 M Humphrey 30 September 2004 Update following FDPS Sections 3 4 6 7 8 11 13 updated. implementation Section 5 Test Plan moved to separate. document Section 14 added, 1 3 M Humphrey 24 January 2005 Update following full Section 2 5 CDL and sections 6 4. implementation and conversions 9 10 11 12 14 updated. integration with ACE, 1 4 M Humphrey 28 December 2005 Update following AEG Section 13 added. CS implementation and Section 2 5 CDL 8 3 11 3 14 15. integration with ACE5A previously 13 14 updated, 1 5 M Humphrey 28 June 2007 Update for AEG 7A Updated FM mappings in section 11 3. and coordination details in section 13, 2 0 Graffica Thom 14 Aug 2007 Version number change N A.
to Graffica standard, 2 1 Graffica 03 January 2008 eDEP 7 3 Coordination upgraded section 13. Draft 1 Humphrey,Page 5 of 101, ACE eDEP Gateway Reference GL AEG TR 1 3 0 Draft 1. 15 Feb 2008, Release Author Release Date Release Description Modifications sections affected. and relevant information, 3 0 Graffica 15 February 2008 Updated for AEG 8A Minor updates to sections 1 2 3. Draft 1 Humphrey,Table 1 1 Document Change History.
1 4 DOCUMENT STRUCTURE,This document contains the following sections. Section 1 outlines the purpose of the document and its contents. Section 2 describes the overall architecture of the AEG. Section 3 defines the design of the gateway component i e the part that connects directly to ACE. Section 4 details the common aspects of the AEG proxy components. Section 5 originally set out the testing strategy for the AEG but is now empty the contents having been moved. to the separate component test document reference 9. Section 6 serves as an introduction to the subsequent sections describing the format of the data presented. Sections 7 to 13 define the detailed design and data analysis for the individual proxy components. Section 14 details the development plan for the AEG. Finally section 15 describes the limitations of the AEG both internal and those due to ACE plus suggested. enhancements and any other known issues,1 5 RELATED DOCUMENTS REFERENCES. Ref Title Doc Reference Authors Date, 1 eDEP Architecture Design Doc GL eDEP ADD 1 V2 0 M Vere August 2007. 2 eDEP ATC Detailed Design GL eDEP DDD 1 2 0 M Vere et al August 2007. 3 eDEP User Guide GL eDEP USER 1 3 Various December 2007. 4 eDEP Platform Developers Guide GL eDEP UG 2 V2 0 M Vere August 2007. 5 ESCAPE High Level Description Various January 2003. 6 eDEP ACE eDEP gateway Design,Neosys November 2003. eDEP Acceptance Plan STP V0 4 December 2003, 8 eDEP Component Test Scripts V2 2 Various December 2007.
9 ACE eDEP Gateway Test Scripts GL AEG TR 2 3 0 M Humphrey February 2008. 10 eDEP Air Layer Detailed Design GL eDEP DDD 1 1 0 Graffica August 2007. Table 1 2 References,Page 6 of 101, ACE eDEP Gateway Reference GL AEG TR 1 3 0 Draft 1. 15 Feb 2008,1 6 ACRONYMS,Abbreviation Meaning,ACE AVENUE Compliant ESCAPE. AEG ACE eDEP Gateway,ATM Air Traffic Management, AVENUE ATM Validation Environment for Use towards EATMS. CDL Component Definition Language,CLI Command Line Interface. CORBA Common Object Request Broker Architecture,EATMP European Air Traffic Management Programme.
EATMS European Air Traffic Management System,eDEP Early Development and Evaluation Platform. EEC EUROCONTROL Experimental Centre, ERIS EATMP Reference Industry Based Simulation Platform. ESCAPE EUROCONTROL Simulation Capability And Platform for Experimentation. FDPS Flight Data Processing System,FM Flight Manager. FPM Flight Path Monitor,IAS Integrated Air Surveillance. IDL Interface Definition Language,IFPL Initial Flight Plan.
IOR Interoperable Object Reference,OASIS Open Architecture for Simulation Systems. ORB Object Request Broker,PM Pilot Manager,POA Portable Object Adapter. PVT Profile Validation Tool,RDPS Radar Data Processing System. RMI Remote Method Invocation,TS Time Server,Table 1 3 Acronyns. Page 7 of 101, ACE eDEP Gateway Reference GL AEG TR 1 3 0 Draft 1.
15 Feb 2008,2 ARCHITECTURE,2 1 INTRODUCTION, ACE is the latest generation of the ESCAPE platform ESCAPE uses the CORBA based OASIS middleware. eDEP has been integrated with ACE so that it can be run with high fidelity trajectories An initial proof of. concept integration was performed in which the eDEP Time Server component was replaced by a proxy. component receiving time information from ACE Three further integration steps have now been completed. 1 FDPS integration eDEP IFPL FM TP ACR components replaced with proxies. 2 RDPS integration eDEP IAS FPM PM components replaced with proxies. 3 CS integration eDEP CS component replaced by a proxy. The ACE eDEP Gateway AEG provides the interfaces between the CORBA based ACE services and the. RMI based component framework of the eDEP platform ACE runs on Unix machines and eDEP is normally. run on PCs so the integration also has to take the different platforms into account The rest of this section. describes the architecture and design of the AEG,2 2 LOGICAL ARCHITECTURE. The following diagram illustrates the scope and logical layers of the AEG. ACE platform and services,Gateway component,Proxy components. eDEP components,Figure 2 1 AEG Scope,2 2 1 AEG Gateway Component. The gateway will be a Java component This will allow it to communicate directly with the Proxy components. using RMI and to communicate with the ACE platform via CORBA. In order to subscribe to and receive the ACE events that the AEG needs to feed into the proxy components the. gateway component must follow the conventions of the ESCAPE platform To this end it shall respect the. OASIS lifecycle model,Page 8 of 101, ACE eDEP Gateway Reference GL AEG TR 1 3 0 Draft 1.
15 Feb 2008,2 2 2 AEG Proxy Components, As mentioned above several eDEP components are to be replaced with proxy components These proxies will. contain reduced logic compared with the original components sourcing data from ACE events to provide their. services rather than reading it from a file or calculating it internally Note that in some cases some logic will. remain as not all information can be substituted by ACE. The proxy components will isolate the rest of the eDEP system from the ACE connection so that those eDEP. components not replaced by proxies will be unaffected by the ACE integration they will just request a service. as normal unaware that it is being provided by a proxy component Note that this will also apply to proxy. components that use services provided by other proxy components Although such a proxy component will. obviously be aware of the ACE integration with respect to its own services other services will be used as. normal even if the data ultimately comes from ACE This will not be mentioned explicitly in the individual. proxy component sections,2 3 DESIGN OPTIONS, This section looks at two possible AEG architectures. 1 Distributed AEG split between the ACE and eDEP platforms. 2 Centralised AEG wholly on ACE platform,2 3 1 Distributed AEG. This solution has a simple CORBA based component of the AEG running on a Unix platform This forwards. all CORBA messages to an intermediate CORBA gateway running on the PC This intermediate gateway then. communicates with the proxy components, This is illustrated in the following diagram The shaded box marks the scope of the AEG. OASIS ACE Data,TME FM TP Sets,OASIS CORBA,Communication.
AEG Gateway,Communication,proxy proxy,Communication. CWP CWP AMAN,Figure 2 2 Distributed AEG architecture. Page 9 of 101, ACE eDEP Gateway Reference GL AEG TR 1 3 0 Draft 1. 15 Feb 2008, The main advantage of this approach is that it minimises the data flow across the network from the Unix to the. The main disadvantage is that it requires the use of CORBA on both platforms. 2 3 2 Centralised AEG, This solution has the entire AEG running on the Unix Here the gateway and proxy components reside in the.
same virtual machine Each proxy component runs on a separate thread which will give a good data. throughput, This is illustrated in the following diagram The shaded box marks the scope of the AEG. OASIS ACE Data,TME FM TP Sets,OASIS CORBA,Communication. AEG Gateway,proxy proxy ACE on,Communication,CWP CWP AMAN. Figure 2 3 Centralised AEG architecture, The main advantage of this approach is that it has the AEG and proxy components on Unix machines This. restricts the use of CORBA to the Unix machines where it is already used. The main disadvantage is that with all the proxy components on the Unix the communications with the eDEP. components on the PC might cause network loading issues This will be no worse than if the normal eDEP. 5 ESCAPE High Level Description Various January 2003 6 eDEP ACE eDEP gateway Design Document Neosys November 2003 7 eDEP Acceptance Plan STP V0 4 D Smith Graffica December 2003 8 eDEP Component Test Scripts V2 2 Various December 2007 9 ACE eDEP Gateway Test Scripts GL AEG TR 2 3 0 M Humphrey February 2008

Related Books