Page : 1 /
EUROCONTROL EXPERIMENTAL CENTRE
Brétigny-sur-Orge, FRANCE
ADS-B / TIS-B Validation Testbed
eDEP
Technical Document
Component Test Scripts
Issue: 2.6
Issue date: 23 May 2008
Document Change Log for ADS-B / TIS-B Validation Testbed CTSD /Rel. / Author / Date of the release / Description of the release / Modifications (sections affected and relevant information) /
0.1 / Graffica (Kirkwood) / 20th Oct. 2005 / Document Created / All
1.0 / Graffica(Thom) / 15 Aug 2007 / Version number change to Graffica standard / N/A
Document Change Log for eCockpit CTSD /
Rel. / Author / Date of the release / Description of the release / Modifications (sections affected and relevant information) /
0.1 / Graffica (Cooper) / 3rd Sept 2004 / Document Created / All
0.2 / Graffica (Cooper) / 24th Sept 2004 / Updated following on-site testing at EEC (13th-17th Sept, 2004) / All
0.3 / Graffica (Cooper) / 1st Oct 2004 / Added initials and date to comments / All Observations
0.4 / Graffica (Cooper) / 2nd Nov 2004 / Added WP2.4 Tests and updated following comments from EEC. / Added sections for ARTAS, IAS and flight plan modifications.
Added references to STP test cases where omitted.
Added eDEP integration test cases.
0.5 / Graffica (Cooper) / 12th Nov 2004 / Updated WP2.4 tests. / Updated details in tests for ARTAS and IAS section.
0.6 / Graffica (Kirkwood) / 3rd December 2004 / Added WP2.5 CDTI tests. / Section 12
0.7 / Graffica (Kirkwood) / 11th January 2005 / Minor changed to WP2.5 CDTI tests / Section 12
0.8 / Graffica (Cooper) / 1st February 2005 / Added WP2.3 tests. / Section 13
0.9 / Graffica (Kirkwood) / 8th February 2005 / Added UDP forwarding test. / Section 14
0.10 / Graffica (Cooper) / 11th February 2005 / Updated Tests / All Sections.
0.11 / Graffica (Kirkwood) / 15th February 2005 / Extended UDP forwarding tests to include Cat 244 and Cat 62. / Section 14.1
0.12 / Graffica (Cooper) / 22nd February 2005 / Updated tests involving PWP. / Section 13
0.13 / Graffica (Kirkwood) / 12th April 2005 / Updated UDP forwarding tests. / Section 14.1.
0.14 / Graffica (Kirkwood) / 13th April 2005 / Run tests and made observations. / All
0.15 / Graffica (Kirkwood) / 14th April 2005 / Added Test for ARTAS replay tool. / Section 15.
0.16 / Graffica (Kirkwood) / 20th April 2005 / Added Dynamic Flightplan correlation test. / Section 10.2.5
0.17 / Graffica (Kirkwood) / 26th April 2005 / Updated tests. / All
0.18 / Graffica (Kirkwood) / 3rd May 2005 / Updated Test EE_UDP_004, timeOfDay field. / Section 14.1.3
0.19 / Graffica (Kirkwood) / 4th May 2005 / Corrections to Test EE_UDP_005. / Section 14.1.4
0.20 / Graffica (Kirkwood) / 13th May 2005 / Modifications following ARTAS refactoring. / Section 4.4 (Test Removed), Section 9.2.1
0.21 / Graffica (Kirkwood) / 9th June 2005 / Added PM Generated Cat-244 UDP forwarding test. / 14.1.5
0.22 / Graffica (Kirkwood) / 20th June 2005 / Updated resource locations following resource refactoring. / All
0.23 / Graffica (Kirkwood) / 24th June 2005 / Updated tests following refactoring and test run. / All
0.24 / Graffica (Kirkwood) / 29th June 2005 / Updated tests according to AVT action list and following Flightplan based Trajectory ID for PM generated ADSBReports. / All
0.25 / Graffica (Kirkwood) / 21st October 2005 / Added test for eCockpit and PWP coexistence. / Section 16
0.26 / Graffica (Kirkwood) / 1st April 2007 / Added tests for AVT Cristal Med / Sections 9.3, 9.4, 10.2, 18
1.0 / Graffica(Thom) / 14th Aug 2007 / Version number change to Graffica standard / N/A
Document Change Log /
Rel. / Author / Date of the release / Description of the release / Modifications (sections affected and relevant information) /
2.0 / Graffica (Kirkwood) / 27th Nov 2007 / Merged AVT and eCockpit CTSD / All
2.1 / Graffica (Kirkwood) / 29th Nov 2007 / Merged eCockpit STP. Added SRD compliancy matrix. / Section 1, 2, 20
2.2 / Graffica (Kirkwood) / 4th Jan 2008 / Added test for flight list window.
Fixed typographical errors.
Added ADSB/TISB/ARTAS/Asterix tests to compliancy matrix. / Section 19, 20.
2.3 / Graffica (OWEN) / 11th Mar 2008 / Updated the Compliance matrix to: replace XX in requirements by category; merged the two ARTAS_ATX_Multiple_001 rows / Section 20.1
2.4 / Graffica (Kirkwood) / 11th Mar 2008 / Compliancy Matrix correction. / Section 20.1
2.5 / Graffica (Hargreaves) / 15th April 2008 / Updated ARTAS_ATX_Multiple_001 following testing. / Section 9.4
2.6 / Graffica (Hargreaves) / 17th April 2008 / Updated IAS_MODE_001 removing check for a non existent Flight level deviation. / Section 10.1
Table of contents
Page : 1 /
1 Introduction 9
1.1 Purpose 9
1.2 Intended audience 9
1.3 Responsibilities 9
1.3.1 General documentation 9
1.4 Background 9
1.5 Development Process 9
1.6 Software & Software Testing 10
1.7 Project Milestones 10
2 Process reviews 10
2.1 Testing and Review Processes 11
2.1.1 Design Reviews 11
2.1.2 Code Reviews 11
2.1.3 Unit Testing 11
2.1.4 Integration Testing 11
2.1.5 System Testing 11
2.2 Review Schedule 12
2.2.1 SSP3 – WP2.1 eCockpit / eDEP Integration 12
2.2.2 SSP4 – WP2.2 Live Air System 12
2.2.3 SSP6 – WP2.4 Pseudo Live AIR/GRD 12
2.2.4 SSP7 – WP2.5 CDTI Modifications 12
2.2.5 SSP5 – WP2.3 Simulated Air/Ground 12
2.2.6 WP 7.1 – ADS-B Validation Trials 12
3 eCockpit Test Configuration 12
4 test environment 14
4.1 Related Documents 14
4.2 File Structure 14
4.3 Launcher HMI 14
5 EDEP Integration Tests 14
5.1 Time and IFPL Services 14
5.2 Airspace Service 15
6 ASTERIX Message Tests 16
6.1 Cat21 Message Format 16
6.2 Cat244 Message Format 16
6.3 Cat62 Message Format 17
7 ADS-B Tests 17
7.1 Cat21 Messages 17
7.1.1 Receipt of ADS-B Cat21 Message 17
7.2 Cat244 Messages 19
7.2.1 ADS-B Cat244 Message Generation 19
7.3 Joint Cat244 and Cat21 Messages 20
7.3.1 eCockpit Visibility Through ADS-B Messages 20
8 TIS-B Tests 21
8.1 Cat62 Messages 21
8.1.1 Receipt of TIS-B Cat 62Message 22
9 ARTAS Proxy Server Tests 23
9.1 Cat62 Messages 23
9.1.1 Receipt of ARTAS Cat62 Message 23
9.2 Cat32 Messages 24
9.2.1 Transmission of ARTAS Cat32 Message 24
9.3 Cat21 Messages 25
9.3.1 Receipt of ARTAS Cat21 Message 25
9.4 Multiple Input streams 26
9.4.1 Receipt of ARTAS Cat21 and Cat62 Messages 26
10 IAS Tests 28
10.1 IAS Connection Tests 28
10.1.1 LIVE Mode Test 28
10.1.2 AIR Mode 29
10.2 IAS Correlation 29
10.2.1 ARTAS Report Correlation – SSR Code 30
10.2.2 ARTAS Report Correlation – Callsign 30
10.2.3 No Correlation 32
10.2.4 False Correlation 32
10.2.5 Replay of ARTAS Cat-62 Data with Dynamic Flightplans 33
10.2.6 ARTAS Cat-21 Report Correlation – Callsign, ICAO Address and False Correlation 35
11 Flight Plan Modification Test 36
11.1 ICAO 24-Bit Address 36
11.1.1 ICAO 24-Bit Address in eDEP 36
11.1.2 ICAO 24-Bit Address in eCockpit 37
12 CDTI Tests 38
12.1 CDTI / ND Plugin framework 38
12.1.1 Navigation Display Plug-in Components 38
12.1.2 Navigation Display Static Plug-in Components 38
12.1.3 Navigation Display Route/Beacon Plug-in Components 39
12.1.4 Navigation Display Surrounding Aircraft Plug-in Components 40
12.1.5 Navigation Display Surrounding Aircraft Plug-in Components 41
13 WP2.3 Simulated Environment Tests 41
13.1 PM ADS-B Tests 42
13.1.1 Receipt of ADS-B Messages from eCockpit 42
13.1.1.1 EEPM_REC_001 – ADS-B Report Receipt from eCockpit 42
13.1.1.2 EEPM_REC_002 – ADS-B Data Content from eCockpit 43
13.1.2 Generation of ADS-B Messages 44
13.1.2.1 EEPM_GEN_001 – Datalink Equipped Flights 44
13.1.2.2 EEPM_GEN_002 – Non-Datalink Equipped Flights 45
13.1.2.3 EEPM_GEN_003 – Mixed Datalink/Non-Datalink Equipped Flights 46
13.1.3 ADS-B Generation with PWP 47
13.1.3.1 EEPM_GEN_004 – PWP 47
13.2 IAS Tests 49
13.2.1 ADS-B Tests 49
13.2.1.1 EEIAS_DAP_001 – Receipt and Forwarding of DAP Data 49
13.2.2 Track Report Generation 51
13.2.2.1 EEIAS_GEN_001 – Non-Datalink Equipped Flights 51
13.2.2.2 EEIAS_GEN_002 – Mixed Datalink/Non-Datalink Flights 52
13.3 CWP Tests 53
13.3.1 DAP Data 54
13.3.1.1 EECWP_DAP_001 – DAP Data Content 54
13.3.1.2 EECWP_DAP_002 – DAP Data Display 56
13.4 eCockpit Tests 58
13.4.1 Message Receipt 58
13.4.1.1 EECP_REC_001 – ADS-B Only Datalink Equipped Flights 58
13.4.1.2 EECP_REC_002 – TIS-B Only Non-Datalink Equipped Flights 59
13.4.1.3 EECP_REC_003 – Mixed Datalink/Non-Datalink Flights 60
13.4.2 Service Volume Filtering 61
13.4.2.1 EESV_FILT_001 – Service Volume Filtering 62
13.5 RMI Tests 63
13.5.1 EE_RMI_001 – RMI and Data Serialisation Test 63
13.6 EDEP ATC Testing 63
14 UDP Forwarding Tests 64
14.1 UDP Forwarding Tests 64
14.1.1 EE_UDP_001 – UDP forwarding from eDEP to external clients Cat 21 and reception of Cat 244. 64
14.1.2 EE_UDP_002 – UDP forwarding from eDEP to external clients Cat 244. 66
14.1.3 EE_UDP_004 – UDP forwarding from eDEP PM generated Cat 21 to external clients. 68
14.1.4 EE_UDP_005 – UDP forwarding from external cockpit to PM with correlation. 70
14.1.5 EE_UDP_006 – UDP Cat 244 forwarding from PM to external clients. 72
15 ARTAS Replay Tests 73
15.1 ARTAS Replay Tests 73
15.1.1 EE_REP_001 – Replay of ARTAS Cat-62 Data 74
16 Simulated & cockpit flight coexistence 75
16.1 Simulated and Cockpit flight coexistence 75
16.1.1 ECP_PWP_10 – ECockpit and PWP coexistence 75
17 eDEP / AVT Integration Tests 76
17.1 Test Configuration 76
17.2 test environment 77
17.2.1 File Structure 77
17.2.2 Launcher HMI 77
17.3 ECockpit / AVT integration test. 77
17.4 EDep Traffic Generator / AVT integration test. 78
17.5 eDEP FDPS / AVT integration test. 78
17.6 eDEP Cat-21 AVT integration test. 79
17.7 eCockpit Cat-21 AVT integration test. 80
18 ADS-B Validation Trials HMI 81
18.1 Display of multiple Cat-21 / Cat-62 message streams 81
18.2 Radar Coverage 83
19 Flight List Window 96
19.1 Flight List Window 96
20 Compliance Matrix 99
20.1 Test Case To Test Specification Reference 99
AVT_CTSD.docPage : 1 /
1 Introduction
1.1 Purpose
This document contains off-site tests for the eDEP/eCockpit Integrated system, being developed for TRSB164/2003 (see [Ref 1] and [Ref 2]Error! Reference source not found.) and for eDEPs integration with the AVT system (see [Ref 9]).
1.2 Intended audience
This document is of interest to all eDEP developers working with the AVT project.
1.3 Responsibilities
The Graffica project manager is responsible for updating this document.
1.3.1 General documentation
/ Title / Reference / Filename / Author / Date /[Ref 1] / TRS B164 / 2003 / TRS_Phase_eDEP_SSP_v1.0.doc / D.Smith / 15/11/03
[Ref 2] / TRS B164 / 2003 Annex / TRS ANNEX eDEP SSP Demonstrator_v1.0.doc / D.Smith / 14/11/03
[Ref 3] / eDEP Acceptance Test Plan / eDEP_AcceptanceTestPlan.doc / R.Aynsworth / 26/11/02
[Ref 4] / eDEP/eCockpit Integration Project System Software Requirements / srd.doc / M.Vere / 02/04/04
[Ref 5] / eCockpit Validation Tests / eCockpit_VTD.doc / P.Hafeneder et. al. / 18/05/04
[Ref 6] / eDEP/eCockpit Integration Project Detailed Design Document. / eCockpit_DDD.doc / T.Cooper
[Ref 7] / eDEP Component Test Script / eDEP_ComponentTestScripts.doc / D.Smith / 14/05/04
[Ref 8] / eDEP/eCockpit Integration Component Test Script / ECockpit_CTS.doc / T.Cooper
[Ref 9] / EDEP future task for the use of eDEP in ADS-B Validation Trials (CRISTAL MED),
Ref: TEC/eDEP/A34PT-50/WPE7.1 / TRS A34PT-2005_FutureTask_WP.7.1_AVT_Annex_v1.0.doc / L. Van der Hoorn / 30/8/2006
[Ref 10] / EDEP Software requirements Document
Ref: GL/eDEP/SRD/1/3.0 / eDEP_SRD.doc / S. Owen / 13/8/2007
[Ref 11] / Future task for the use of eDEP in ADS-B Validation Trials / AVT_WPE7-1.DD.doc / D.Kirkwood / 11/9/2006
1.4 Background
The original eCockpit software is a stand-alone application providing a cockpit display for an aircraft. The eDEP/eCockpit integration project shall incorporate the original eCockpit software into the eDEP application and component structure and provide a connection to the ARTAS and SMART systems for communication of ADS-B and TIS-B messages.
1.5 Development Process
The eDEP/eCockpit software integration development process consists of an iterative approach, adding functionality to the system in discrete steps. At each step, testing will be performed to ensure the functionality of the system is maintained and new functionality is adequately tested.
1.6 Software & Software Testing
The eDEP/eCockpit integrated software is 100% Java built upon the JDK 1.4 SDK, the eDEP software library and the ILog JViews graphics library. The eDEP software can also be build upon the JSDK 1.6 SDK apart from eCockpit which is a know issue. This is as a result of the current version of JView which is used for the cockpit graphics being incompatible with Java 1.6.
The software shall be tested throughout development and for each milestone using the test processes and strategy outlined in section 2.
1.7 Project Milestones
The eDEP/eCockpit integration project WP2 consists of a number of milestones, each adding discreet functionality to the system:
Due date / Work Package ID and Name / Deliverable ID and Description25/06/04 / WP2.1 / Deliverable SSP3 : eCockpit / eDEP Integration
eDEP/eCockpit integrated application using eDEP flight, airspace and initial flight plan services provided by eDEP. Restructured code following design patterns for application and entity management demonstrated in the GSDK and ATC software.
23/08/04 / WP2.2 / Deliverable SSP4 : Live Air System
eDEP/eCockpit integrated application using ADS-B and TISB services through eDEP UDP connections to SMART / ARTAS.
14/10/04 / WP2.4 / Deliverable SSP6 : Pseudo Live AIR/GRD
Modification to IAS to support Cat32 messages.
19/11/04 / WP2.5 / Deliverable SSP7 : CDTI Modifications
eDEP/eCockpit integrated application with CDTI Plug-In framework and update of CDTI graphical displays with new functionality.
10/12/04 / WP2.3 / Deliverable SSP5 : Simulated Air/Ground
Modifications to the PM and IAS servers to use ADS-B and TIS-B messages respectively.
Table 1 – WP2 Milestones
The CRISTAL MED project WP7.1 consists of two milestones:
Due date / Work Package ID and Name / Deliverable ID and DescriptionEnd 2006 / WP7.1_1 / Delivery 1: eDEP capable of processing Asterix CAT 21.
Early 2007 / WP7.1_2 / Delivery 2: eDEP capable of handling multiple input streams.
Early 2008 / WP7.1_3 / Delivery 1: searching and higlighting flights
2 Process reviews
This section details the processes that will be used in order to ensure the integrated software meets the software requirements for the project.