LINK Programme. Generic Interop Test Plan for Avionics - Part 1 Upper Layers and CM/CPDLC applications. Cooperative Network Design

Transcription

1 Edition 2.3 Author: LINK Test Facility Edition date: Reference nr: LINK2000+/LIT/Avionics Test Plan LINK Programme Generic Interop Test Plan for Avionics - Part 1 Upper Layers and CM/CPDLC applications Cooperative Network Design EUROCONTROL

2 EUROCONTROL EUROCONTROL LINK2000+ Programme Generic Interop Test Plan for Avionics - Part 1 Upper Layers and CM/CPDLC applications Doc Ref. Author : LINK2000+/LIT/Avionics Test Plan : LINK Test Facility Rev. No. : 2.3 Date : 15 th June 2010

3 DOCUMENT CONTROL LOG SECTION DATE REV. NO. REASON FOR CHANGE OR REFERENCE TO CHANGE All 01-Sept-09 Issue 1.0 Creation All 27-Nov-09 Issue 1.1x Test Case modifications made, new Test Cases added, and Editorial changes made. All 07-Dec-09 Issue 2.0 LIT Review, Editorial Changes All 08-Jan-10 Issue 2.1 Test case added, Test cases updated, Matrix updated All 08-Apr-10 Issue 2.2 Test cases added, Test cases updated, Matrix updated All 15-June-10 Issue 2.3 Test cases added, Test cases updated, Matrix updated Issue 2.3 i

4 TABLE OF CONTENTS 1. Scope Scope of the document Document Overview Reference documents Terminology Interoperability Tests approach Conditions and methods for the tests Human Resources Configurations Real Test Configuration Simulated Test Configuration ATN configurations Test cases configurations Tests Cases Description Tests using Real Test Configuration CM Application CPDLC Application Tests using Simulated Test Configuration CM Application Tests CPDLC Application Tests Traceability Matrix...87 Issue 2.3 ii

5 TABLE OF FIGURES Figure 1: Sample ATN physical topology... 8 Figure 2: Sample ATN routing topology... 9 Issue 2.3 iii

6 1. Scope 1.1 Scope of the document This document provides guidelines to Avionics vendors on ATN Upper Layers and CM&CPDLC end to end interoperability testing to be used in the validation of their avionics implementations before they are placed in a live operational environment. The document details the Interoperability tests (application level) proposed to be performed between the avionics implementation (System Under Test, SUT) and the LINK2000+ Data link Test Facility ground test tools. However, these tests could also be exercised/performed against the ground test tools the avionics vendor may have or have contracted for the purpose of the avionics validation. 1.2 Document Overview The document structure is based on the following headlines: - Chapter 1 introduces the document, - Chapter 2 specifies the approach taken to Interoperability Testing - Chapter 3 outlines conditions and methods required for testing. - Chapter 4 provides the test procedures descriptions, and - Chapter 5 provides a traceability matrix that illustrates the allocation of test identifiers to ED-110B requirements (ref. [1]) and to the Eurocontrol Specification on Data Link Services (ref. [2]). 1.3 Reference documents [1] Interoperability Requirements Standard for Aeronautical Telecommunication Network Baseline 1, ED-110B, December (EUROCAE) [2] EUROCONTROL Specification on Data Link Services SPEC Terminology A/G ACSP AGTS AMIC ANSP Air/Ground Air/Ground Communications Service Provider Air/Ground Test System Application Message Integrity Check Air Navigation Service Provider Issue 2.3 4

7 APM ARINC ATC ATSU AVLC CDU CMU EEC ES FIB G Tool R-ATSU SITA STC SUT T-ATSU Aircraft Personality Module Aeronautical Radio Incorporated Air Traffic Control Air Traffic Service Unit Aviation VHF Link Control Control Display Unit Communications Management Unit Eurocontrol Experimental Center End System Forwarding Information Base Ground Test Tool End System (from EEC Test Facility) Receiving Air Traffic Service Unit Société Internationale de Télécommunications Aéronautiques Simulated Test Configuration System Under Test Transferring Air Traffic Service Unit VDL-M2 VHF Digital Link Mode 2 VDR VGS VHF VHF Data Radio VDL-M2 Ground Station Very High Frequency Issue 2.3 5

8 2. Interoperability Tests approach The approach to Interoperability Testing, taken in this document, is to provide a suite of tests that cover the essential airborne requirements detailed in ED-110B [1], and which can be used as a guideline by Avionics vendors in the validation of their systems. This approach provides the minimum Interoperability tests coverage for validation of the airborne system, and it does not have the intent to cover every airborne requirement. A Traceability Matrix in section 5 matches the airborne ED- 110B [1] requirements and the airborne Eurocontrol DLS Spec [2] requirements to their corresponding tests where covered. Tests have been divided into two configurations: a) Real Test Configuration where tests can be run using a real ANSP ground implementation or alternatively by using Ground Test Tools. This configuration covers nominal tests cases; b) Simulated Test Configuration - where tests need to be run using Ground Tools only, and covers non-nominal cases (e.g. error and robustness cases, etc.). 3. Conditions and methods for the tests 3.1 Human Resources Two Data Link Experts are required to manually perform the test procedures outlined in this document, one on the Ground side and one on the Airborne side. 3.2 Configurations Real Test Configuration Tests specifying Real Test Configurations (RTC) are tests which could be carried between the avionic equipment and a real ANSP Ground Implementation. These tests usually cover nominal cases. A Real Test Configuration aims to validate operational test situations in a lab environment. A Real Test Configuration is composed of the following elements: An avionic pallet/installation providing the real avionic equipment under test. It is mainly composed of a Communication Management Unit (CMU), a Multi-Function Control and Display Unit (MCDU) and a VHF Data Radio (VDR) for air/ground communication. This pallet may be situated locally at the EEC if integration is possible, or it may be located remotely. One, two or three ground data link ground systems depending on the scenario to be executed. These could be real ANSP Ground Implementation or Ground Test Tools applications. Issue 2.3 6

9 A set of ATN routers to build the ATN topology Simulated Test Configuration Tests specifying Simulated Test Configurations (STC) are tests which need to be carried out between the avionics and a simulated Ground environment using Test Tools. These tests cover non-nominal cases: error and robustness cases etc. Real ANSP Ground Implementation cannot be used for tests falling under this category. A Simulated Test Configuration is composed of the following elements: An avionic pallet/installation providing the real avionic equipment under test. It is mainly composed of a Communication Management Unit (CMU), a Multi-Function Control and Display Unit (MCDU) and a VHF Data Radio (VDR) for air/ground communication. This pallet may be situated locally at the EEC if integration is possible, or it may be located remotely. One, two or three ground data link ground systems depending on the scenario to be executed. The ground systems host Ground Test Tools applications. A set of ATN routers to build the ATN topology ATN configurations The following figure depicts the physical topology used in the context of the above mentioned RTC or STC configurations, describing the Aircraft Avionics system connected to the EEC test facility platform: Issue 2.3 7

10 EEC Datalink Facility ATC1 Ground Test Tool X.25or IP VDL2 Avionics SUT ATN network ATC2 Ground Test Tool X.25or IP Legend: End to end communication SUT System Under Test Figure 1: Sample ATN physical topology The following figure depicts a typical ATN routing topology, with the Avionics system: either local to the EEC connected to the EEC Air/Ground Test System (AGTS) or remotely connected via ARINC or SITA ACSPs. The topology also shows that a ground ANSP implementation could be reachable from the EEC: via the ANSP s local ACSP (link 1 and link 2 on the figure below) - additional G/G routing policy rules may have to be added on the CSP ATN G/G router to enable the EEC avionics to reach the ANSP ground implementation. or with a direct G/G adjacency established between EEC and the ANSP (link 3 on the figure below) Issue 2.3 8

11 Aircraft Domain ES/ABIS SUT A/G BIS EEC Datalink Facility G/G BIS A/G BIS Aircraft Domain SUT ARINC RD SITA RD ES/ABIS 1 2 ATC G BIS ES ANSP Routing domain Legend : mobile link interdomain link intradomain link 3 EEC Main Ground Domain G/G BIS AGTS RD G/G BIS G BIS A/G BIS ES EEC ATIF Domain GND 2 GND GND1 2 ES Figure 2: Sample ATN routing topology Test cases configurations In the following test specifications, different Real Test Configurations (RTCx) or Simulated Test Configurations (STCx) are applied: Issue 2.3 9

12 RTC1/STC1: when only two peers are involved. The Air side is AIRCRAFT (avionics vendor implementation) and the Ground side is GND1 RTC2/STC2: when two ground sites are involved. The Air side is AIRCRAFT (avionics vendor implementation) and the Ground sides are GND1 and GND2. RTC3/STC3: when three ground sites are involved. The Air side is AIRCRAFT (avionics vendor implementation) and the Ground sides are GND1, GND2 and GND3. Points of Control and Observation are defined as: System AIRCRAFT GND1 GND1Disp GND2 GND2Disp GND3 GND3Disp Title Avionic equipment Input and Display System Input device on GND1 system Display/logging and trace device on GND1 system Input device on GND2 system Display/logging and trace device on GND2 system Input device on GND3 system Display/logging and trace device on GND3 system Issue

13 4. Tests Cases Description 4.1 Tests using Real Test Configuration CM Application CM-logon: nominal case CM_N010 To check the Airborne System correctly generates the CM Logon request and successfully handles the logon procedure ED110B Requirements / / / / / ES DLS Requirements A / A / A / B RTC1 AIRCRAFT is authorized to logon to GND1. 1. AIRCRAFT ENTER AIRCRAFT sends a Logon request to GND1. 2. GND1Disp VERIFY GND1 receives the CM-logon indication from AIRCRAFT: Check CPDLC version = 1. Check that the list of air initiated applications is empty, Check that the ground initiated applications contain an entry with a CPDLC TSAP address, version = 1, and AEQ = 22. Check that airportdeparture and airportdestination fields are provided. 3. GND1 ENTER GND1 responds with a positive CM-logon response to AIRCRAFT. 4. AIRCRAFT VERIFY AIRCRAFT Logon/Notify status reads LOGGED ON/NOTIFIED Issue

14 CM-logon: rejected response ED110B Requirements ES DLS Requirements No SYSTEM Action Description CM_N020 To check the Airborne system correctly handles a negative CMlogon response (step3)/ / A / A RTC1 On AIRCRAFT, enter a flight ID with non possible correlated flight plan 1. AIRCRAFT ENTER AIRCRAFT sends a CM Logon request to GND1. 2. GND1Disp VERIFY Check GND1 receives the CM-logon indication from AIRCRAFT 3. GND1 ENTER GND1 responds with a rejected CM-logon response to AIRCRAFT. (Empty Logon response) 4. AIRCRAFT VERIFY AIRCRAFT Logon/Notify status reads FAILED CM-logon: timer timeout CM_N030 To check the Airborne system correctly handles a CM-Logon tts timer timeout (where implemented) ED110B Requirements / ES DLS Requirements A / A RTC1 No SYSTEM Action Description 1. AIRCRAFT ENTER AIRCRAFT sends a CM-logon request to GND1. 2. GND1Disp VERIFY Check GND1 receives the CM-logon indication from AIRCRAFT. 3. WAIT Wait for a period longer than the air Logon tts value (At least > 60s) 4. AIRCRAFT VERIFY Logon/Notify status is displayed as FAILED/TIMEDOUT 5. GND1Disp VERIFY Check GND1 receives a CM-User-Abort Indication Issue

15 CM-logon: invalid EOBT CM_N040 When the datetimedepartureetd element of the CM-logon request is used, to check that the Airborne system sets the date field of datetimedepartureetd element to 01/01/1996 when an operationally valid date is not available. ED110B Requirements ES DLS Requirements A / A / B RTC1 No SYSTEM Action Description 1. AIRCRAFT ENTER AIRCRAFT sends a CM-logon request to GND1 (valid date not available) 2. GND1Disp VERIFY Check GND1 receives the CM-logon indication from AIRCRAFT with the date field of datetimedepartureetd element set to 01/01/ GND1 ENTER GND1 responds with a positive CM-logon response to AIRCRAFT. 4. AIRCRAFT VERIFY AIRCRAFT Logon/Notify status reads LOGGED ON/NOTIFIED CM-contact: successful CM_N050 To check the Airborne System correctly handles the CM-contact service. RTC2 ED110B Requirements / /4.1.4 ES DLS Requirements A / A / B AIRCRAFT is logged on GND1. AIRCRAFT is authorized to logon to GND2. GND1 ENTER Send the CM-contact request to AIRCRAFT to contact GND2 1. system. 2. AIRCRAFT AIRCRAFT receives the CM-contact indication from GND1, and generates a CM-logon request to GND2. 3. GND2Disp VERIFY Check GND2 receives a CM-logon indication from AIRCRAFT. 4. GND2 ENTER GND2 responds with a CM-logon response to AIRCRAFT providing supported application information. 5. AIRCRAFT AIRCRAFT receives the CM-logon confirmation from GND2 providing supported application information. 6. AIRCRAFT AIRCRAFT sends a successful CM-contact response to GND1. 7. GND1Disp VERIFY Check GND1 receives a successful CM-contact confirmation from AIRCRAFT. Issue

16 CM-contact: not successful CM_N060 To check that the Airborne System correctly handles an unsuccessful CM-contact response. ED110B Requirements /4.1.4 ES DLS Requirements A / A RTC2 AIRCRAFT is logged on GND1. AIRCRAFT is authorized to logon to GND2. GND2 system is not ATN connected. 1. GND1 ENTER Send the CM-contact request to AIRCRAFT to contact GND2. 2. AIRCRAFT AIRCRAFT receives the CM-contact indication from GND1 and generates a CM-logon request to GND2. 3. WAIT Termination of the tlogon timer value. 4. GND1Disp VERIFY Check GND1 receives an unsuccessful CM-contact confirmation from AIRCRAFT. 5. AIRCRAFT VERIFY Check the Logon/Notify status is still LOGGED ON/NOTIFIED CPDLC Application CPDLC Connection Handling CPDLC Connection accepted CPDLC_N010 To verify that a logged on Airborne System correctly handles the CPDLC connection procedure with a ground centre. In this test, the ground CPDLC-start request is accepted. RTC1 ED110B Requirements: ICAO Doc Ed.2 Req / AIRCRAFT is already logged on GND1 1. GND1 ENTER Send a CPDLC-start request to AIRCRAFT 2. GND1Disp VERIFY Check GND1 receives the accepted CPDLC-start confirmation from AIRCRAFT. 3. AIRCRAFT AIRCRAFT sends the (DM99) CURRENT DATA AUTHORITY message to GND1 requesting a LACK 4. GND1Disp VERIFY Check GND1 receives the (DM99) CURRENT DATA AUTHORITY message from AIRCRAFT. 5. GND1 ENTER Send the (UM227) LACK message to AIRCRAFT to acknowledge (DM99) CURRENT DATA AUTHORITY message. 6. AIRCRAFT VERIFY Check GND1 is displayed as Current Data Authority Issue

17 CPDLC connection: rejected 1 CPDLC_N020 To check that the Airborne System, with a CPDLC connection established, can terminate CPDLC thereby placing the system in the CPDLC INHIBITED state. To check that the system correctly rejects a subsequent CPDLCstart Indication while in the CPDLC INHIBITED state. RTC1 ED110B Requirements: ES DLS Requirements: A AIRCRAFT is logged on and CPDLC connected to GND1 1. AIRCRAFT ENTER/ VERIFY Terminate CPDLC and verify that the avionics system has reverted to the CPDLC INHIBITED state. 2. GND1Disp VERIFY A CPDLC-User Abort indication with reason (commanded termination) is received 3. GND1 ENTER Send a CPDLC-start request to AIRCRAFT 4. GND1Disp VERIFY Check GND1 receives the rejected CPDLC-start confirmation from AIRCRAFT including a CPDLC message containing the concatenation of message element DM62 (ERROR (errorinformation)) with the choice (2) followed by message element DM98 (AIRCREW HAS INHIBITED CPDLC). 5. GND1Disp VERIFY Check CPDLC/TP4 connection with AIRCRAFT is closed. Issue

18 CPDLC connection: rejected 2 CPDLC_N025 To check that the Airborne System, while logged on but with no CPDLC connection established, can disable CPDLC thereby placing the system in the CPDLC INHIBITED state. To check that the system correctly rejects a subsequent CPDLCstart Indication Note: Not all Avionic systems support this reversion to the CPDLC INHIBITED state when no CPDLC connection is in place. RTC1 ED110B Requirements: ES DLS Requirements: A (Recommendation) AIRCRAFT is logged on (and consequently in a CPDLC ENABLED state) 1. AIRCRAFT ENTER Disable CPDLC and verify that the system has reverted to the CPDLC INHIBITED state. 2. GND1 ENTER Send the CPDLC-start request to AIRCRAFT 3. GND1Disp VERIFY Check GND1 receives a rejected CPDLC-start confirmation message from AIRCRAFT including a CPDLC message containing the concatenation of message element DM62 (ERROR [errorinformation]) with the choice (2) followed by message element DM98 ( AIRCREW HAS INHIBITED CPDLC ). 4. GND1Disp VERIFY Check that no CPDLC connection between AIRCRAFT and GND1 exists. Issue

19 CPDLC connection: rejected 3 CPDLC_N030 To check that an Airborne system in the CPDLC INHIBITED state, remains in the CPDLC INHIBITED state following receipt of a CMcontact Indication and that any subsequent CPDLC-start Indication is rejected. RTC2 ED110B Requirements: ES DLS Requirements: A AIRCRAFT is in the CPDLC INHIBITED state. AIRCRAFT is authorized to logon to GND2. 1. GND1 ENTER Send a CM-contact request to AIRCRAFT to contact GND2 system. 2. AIRCRAFT AIRCRAFT receives the CM-contact indication from GND1. 3. AIRCRAFT AIRCRAFT sends a CM-logon request to GND2. 4. GND2Disp VERIFY Check GND2 receives a CM-logon indication from AIRCRAFT. 5. GND2 ENTER GND2 responds with a CM-logon response to AIRCRAFT providing supported application information. 6. AIRCRAFT AIRCRAFT receives the CM-logon confirmation from GND2 providing supported application information. 7. AIRCRAFT AIRCRAFT sends a successful CM-contact response to GND1. 8. GND1Disp VERIFY Check GND1 receives a successful CM-contact confirmation from AIRCRAFT. 9. AIRCRAFT VERIFY Check AIRCRAFT remains in the CPDLC INHIBITED state. 10. GND2 ENTER Send a CPDLC-start request to AIRCRAFT 11. GND2Disp VERIFY Check GND2 receives the rejected CPDLC-start confirmation from AIRCRAFT including a CPDLC message containing the concatenation of message element DM62 (ERROR [errorinformation]( with the choice (2) followed by message element DM98 ( AIRCREW HAS INHIBITED CPDLC ). 12. GND1Disp VERIFY Check no CPDLC connection with AIRCRAFT exists GND2Disp Issue

20 CPDLC/TP4 Connection Maintained and TP4 Keepalives CPDLC_N070 To check that once a CPDLC connection is established, both CPDLC and TP4 connections are maintained, even without any application exchanges. To verify that TP4 AK TPDUs are sent at the expected time intervals, dependent on the remote Inactivity Time, in the absence of transfer of DT TPDUs. RTC1 ED110B Requirements: ICAO Doc Ed.2 Req ES DLS Requirements: B.2.5.1/B AIRCRAFT is already logged on and CPDLC connected to GND1. 1. GND1 SEND Send the CPDLC-start request to AIRCRAFT 2. AIRCRAFT VERIFY Check that GND1 is still displayed as Current Data Authority 3. GND1Disp VERIFY Check that CPDLC and TP4 connections are still established 4. GND1Disp VERIFY Check that ACK TP4 PDUs have been exchanged as per TP4 Window Time expected interval CPDLC messages - TP4 Acknowledgment CPDLC_N071 To check that once a CPDLC connection is established, a TP4 ACK TPDU is sent by the AIRCRAFT within the required interval following successful receipt of an uplink TP4 DT TPDU conveying a CPDLC message. RTC1 ED110B Requirements: ICAO Doc Ed.2 Req ES DLS Requirements: B.2.5.1/B AIRCRAFT is already logged on and CPDLC connected to GND1. 1. GND1 ENTER Send UM183 ( CURRENT ATC UNIT GND1, TEST, CENTRE ) to AIRCRAFT, without requiring a LACK 2. AIRCRAFT VERIFY Check AIRCRAFT receives the UM183 ( CURRENT ATC UNIT GND1, TEST, CENTRE ) freetext message 3. GND1Disp VERIFY Check that a TP4 ACK TPDU has been received in the required interval to acknowledge the TP4 DT TPDU conveying the CPDLC freetext message. Issue

21 ACL Service Aircrew initiated dialogues CPDLC Messages Exchange ACL speed dialogue CPDLC_N080 To check that the Airborne System correctly handles a speed type dialogue. This ACL dialogue is initiated by airborne side and uses the STANDBY message. ED110B Requirements / ES DLS Requirements: A.2.1.1/A.2.1.2/A / A.2.3.3/B.2.2.1/B RTC1 1. AIRCRAFT ENTER Send the DM18 REQUEST [speed] message to GND1. 2. GND1Disp VERIFY Check GND1 receives the DM18 REQUEST [speed] message 3. GND1 ENTER Send UM227 LACK message to acknowledge DM18 REQUEST [speed] message. 4. AIRCRAFT VERIFY Check DM18 REQUEST [speed] message status 5. GND1 ENTER Send UM1 STANDBY message in response to DM18 REQUEST [speed] message. 6. AIRCRAFT VERIFY Check AIRCRAFT receives the UM1 STANDBY message in response to DM18 REQUEST [speed] message. 7. AIRCRAFT AIRCRAFT sends DM100 LACK message to acknowledge UM1 STANDBY message. 8. GND1Disp VERIFY Check GND1 receives DM100 LACK message acknowledging the UM1 STANDBY message. 9. GND1 ENTER Send UM106 MAINTAIN [speed] message to AIRCRAFT in response to DM18 REQUEST [speed] message. 10. AIRCRAFT VERIFY Check AIRCRAFT receives UM106 MAINTAIN [speed] message, in response to DM18 REQUEST [speed] message. 11. AIRCRAFT AIRCRAFT sends DM100 LACK message to acknowledge UM106 MAINTAIN [speed] message. 12. GND1Disp VERIFY Check GND1 receives DM100 LACK message, acknowledging UM106 MAINTAIN [speed] message. 13. AIRCRAFT ENTER Send DM0 WILCO message in response to UM106 MAINTAIN [speed] message. 14. GND1Disp VERIFY Check GND1 receives DM0 WILCO message in response to UM106 MAINTAIN [speed] message. 15. GND1 ENTER Send UM227 LACK message to acknowledge the DM0 WILCO message. 16. AIRCRAFT VERIFY Check the speed dialogue appears as CLOSED Variant: Run the test with the DM1 UNABLE response instead of the DM0 WILCO. Issue

22 CPDLC Messages Exchange ACL level dialogue. CPDLC_N090 To check that the Airborne System correctly handles a level type dialogue. This ACL dialogue is initiated by airborne side. It will also check for a valid CPDLC timestamp. ED110B Requirements / / ES DLS Requirements: A.2.1.1/A.2.1.2/A / A.2.3.3/ B /B RTC1 1. AIRCRAFT ENTER Send the DM6 REQUEST [level] message to GND1. 2. AIRCRAFT VERIFY Check the time the DM6 REQUEST [level] message has been released by the pilot 3. GND1Disp VERIFY Check GND1 receives the DM6 REQUEST [level] message from AIRCRAFT. 4. GND1Disp VERIFY Check the DM6 REQUEST [level] message has a valid timestamp with the format: date YYMMDD, time HHMMSS and matches the timestamp noted in step #2. 5. GND1 ENTER Send UM227 LACK message to acknowledge DM6 REQUEST [level] message. 6. AIRCRAFT VERIFY Check DM6 REQUEST Level message status 7. GND1 ENTER Send UM20 CLIMB TO [level] to AIRCRAFT in response to DM6 REQUEST [level] message. 8. AIRCRAFT VERIFY Check AIRCRAFT receives UM20 CLIMB TO [level] in response to DM6 REQUEST [level] message. 9. AIRCRAFT VERIFY Check AIRCRAFT sends DM100 LACK message to acknowledge UM20 CLIMB TO [level] message. 10. GND1Disp VERIFY Check GND1 receives DM100 LACK message, acknowledging UM20 CLIMB TO [level] message. 11. AIRCRAFT ENTER Send DM0 WILCO message in response to UM20 CLIMB TO [level] message. 12. GND1Disp VERIFY Check GND1 receives DM0 WILCO message in response to UM20 CLIMB TO [level] message. 13. GND1 ENTER Send UM227 LACK message to acknowledge the DM0 WILCO message. 14. AIRCRAFT VERIFY Check the level type dialogue appears as CLOSED. Variants: Run this test with the DM1 UNABLE response instead of the DM0 WILCO. This dialogue can also be lengthened using the DM2 STANDBY. Issue

23 CPDLC Messages Exchange ACL route dialogue CPDLC_N100 To check that the Airborne System correctly handles a route type dialogue. The airborne side initiates this ACL dialogue. ED110B Requirements ES DLS Requirements: A.2.1.1/A.2.1.2/A /A /B RTC1 1. AIRCRAFT ENTER Send the DM22 REQUEST DIRECT TO [position] message to GND1. 2. GND1 VERIFY Check GND1 receives the DM22 REQUEST DIRECT TO [position] message from AIRCRAFT. 3. GND1 ENTER Send UM227 LACK message to acknowledge DM22 REQUEST DIRECT TO [position] message. 4. AIRCRAFT VERIFY Check AIRCRAFT receives the UM227 LACK message, acknowledging DM22 REQUEST DIRECT TO [position] message. 5. GND1 ENTER Send UM74 PROCEED DIRECT TO [position] to AIRCRAFT in response to DM22 REQUEST DIRECT TO [position] message. 6. AIRCRAFT VERIFY Check AIRCRAFT receives UM74 PROCEED DIRECT TO [position] in response to DM22 REQUEST DIRECT TO [position] message. 7. AIRCRAFT VERIFY Check AIRCRAFT sends DM100 LACK message to acknowledge UM74 PROCEED DIRECT TO [position] message. 8. GND1Disp VERIFY Check GND1 receives DM100 LACK message, acknowledging UM74 PROCEED DIRECT TO [position] message. 9. AIRCRAFT ENTER Send DM0 WILCO message in response to UM74 PROCEED DIRECT TO [position] message. 10. GND1Disp VERIFY Check GND1 receives DM0 WILCO message in response to UM74 PROCEED DIRECT TO [position] message. 11. GND1 ENTER Send UM227 LACK message to acknowledge the DM0 WILCO message. 12. AIRCRAFT VERIFY Check the route type dialogue is CLOSED. Variant Run the test with the DM1 UNABLE response instead of the DM0 WILCO. This dialogue could also be lengthened using the DM2 STANDBY. Issue

24 Ground initiated dialogues CPDLC Messages Exchange ACL level dialogue CPDLC_N110 To check that the Airborne System correctly handles a level type dialogue. This ACL dialogue is initiated by ground side. ED110B Requirements ES DLS Requirements: A.2.1.1/A.2.1.2/A /A /B RTC1 1. GND1 ENTER Send the UM19 MAINTAIN [level] message to AIRCRAFT. 2. AIRCRAFT VERIFY Check AIRCRAFT receives the UM19 MAINTAIN [level] message 3. AIRCRAFT AIRCRAFT sends a DM100 LACK message to acknowledge UM19 MAINTAIN [level] message. 4. GND1Disp VERIFY Check GND1 receives the DM100 LACK message acknowledging the UM19 MAINTAIN [level] message. 5. AIRCRAFT ENTER Send the DM1 UNABLE message in response to UM19 MAINTAIN [level] message. 6. GND1Disp VERIFY Check GND1 receives the DM1 UNABLE message in response to UM19 MAINTAIN [level] message. 7. GND1 ENTER Send UM227 LACK message to acknowledge DM1 UNABLE message. 8. AIRCRAFT VERIFY Check the level type dialogue appears as CLOSED Variant: Run this test with the DM0 WILCO response instead of the DM1UNABLE. This dialogue can also be lengthened using the DM2 STANDBY. Issue

25 CPDLC Messages Exchange ACL speed type dialogue CPDLC_N120 To check that the Airborne System correctly handles a speed type dialogue with the use of STANDBY message. The Ground System initiates this ACL dialogue. ED110B Requirements ES DLS Requirements: A.2.1.1/A.2.1.2/A.2.3.1/B RTC1 1. GND1 ENTER Send the UM106 MAINTAIN [speed] message to AIRCRAFT. 2. AIRCRAFT VERIFY Check AIRCRAFT receives the UM106 MAINTAIN [speed] message from GND1. 3. AIRCRAFT AIRCRAFT sends a DM100 LACK message to acknowledge UM106 MAINTAIN [speed] message. 4. GND1Disp VERIFY Check GND1 receives the DM100 LACK message acknowledging the UM106 MAINTAIN [speed] message. 5. AIRCRAFT ENTER Send the DM2 STANDBY message in response to UM106 MAINTAIN [speed] message. 6. AIRCRAFT VERIFY Check the ground initiated speed type dialogue is still OPEN and WILCO/UNABLE are still available 7. GND1Disp VERIFY Check GND1 receives the DM2 STANDBY message in response to UM106 MAINTAIN [speed] message. 8. GND1 ENTER Send the UM227 LACK message to acknowledge the DM2 STANDBY message. 9. AIRCRAFT VERIFY Check DM2 STANDBY message status 10. AIRCRAFT ENTER Send the DM1 UNABLE message in response to UM106 MAINTAIN [speed] message. 11. GND1Disp VERIFY Check GND1 receives the DM1 UNABLE message in response to UM106 MAINTAIN [speed] message. 12. GND1 ENTER Send UM227 LACK message to acknowledge DM1 UNABLE message. 13. AIRCRAFT VERIFY Check the speed type dialogue appears as CLOSED Variant: Run this test with the DM0 WILCO response instead of the DM1 UNABLE. Issue

26 CPDLC Messages Exchange ACL route type dialogue CPDLC_N130 To check that the Airborne System correctly handles a route type dialogue. This ACL dialogue is initiated by ground side. ED110B Requirements ES DLS Requirements: A.2.1.1/A.2.1.2/A /B RTC1 1. GND1 ENTER Send the UM74 PROCEED DIRECT TO [position] message to AIRCRAFT. 2. AIRCRAFT VERIFY Check AIRCRAFT receives the UM74 PROCEED DIRECT TO [position] message from GND1. 3. AIRCRAFT AIRCRAFT sends a DM100 LACK message to acknowledge the UM74 PROCEED DIRECT TO [position] message. 4. GND1Disp VERIFY Check GND1 receives the DM100 LACK message acknowledging the UM74 PROCEED DIRECT TO [position] message. 5. AIRCRAFT ENTER Send the DM1 UNABLE message in response to UM74 PROCEED DIRECT TO [position] message. 6. GND1Disp VERIFY Check GND1 receives the DM1 UNABLE message in response to UM74 PROCEED DIRECT TO [position] message. 7. GND1 ENTER Send UM227 LACK message to acknowledge DM1 UNABLE message. 8. AIRCRAFT VERIFY Check the ground initiated route type dialogue appears as CLOSED Comments: Run this test with the DM0 WILCO response instead of the DM1 UNABLE. This dialogue can also be lengthened using the DM2 STANDBY. Issue

27 CPDLC Messages Exchange ACL Heading type dialogue CPDLC_N140 To check that the Airborne System correctly handles a heading type dialogue. This ACL dialogue is initiated by ground side. ED110B Requirements ES DLS Requirements: A.2.1.1/A.2.1.2/A.2.3.1/B RTC1 1. GND1 ENTER Send the UM190 FLY HEADING [degrees] to AIRCRAFT. 2. AIRCRAFT VERIFY Check AIRCRAFT receives the UM190 FLY HEADING [degrees] message from GND1. 3. AIRCRAFT AIRCRAFT sends a DM100 LACK message to acknowledge the UM190 FLY HEADING [degrees] message. 4. GND1Disp VERIFY Check GND1 receives the DM100 LACK message acknowledging the UM190 FLY HEADING [degrees] message. 5. AIRCRAFT ENTER Send the DM0 WILCO message in response to the UM190 FLY HEADING [degrees] message. 6. GND1Disp VERIFY Check GND1 receives the DM0 WILCO message in response to the UM190 FLY HEADING [degrees] message. 7. GND1 ENTER Send UM227 LACK message to acknowledge DM0 WILCO message. 8. AIRCRAFT VERIFY Check this heading type dialogue appears as CLOSED Comments: Run this test with the DM1 UNABLE response instead of the DM0 WILCO. This dialogue can also be lengthened using the DM2 STANDBY. Issue

28 CPDLC Messages Exchange ACL time type dialogue CPDLC_N150 To check that the Airborne System correctly handles a time type dialogue. This ACL dialogue is initiated by ground side. ED110B Requirements ES DLS Requirements: A.2.1.1/A.2.1.2/A.2.3.1/ A /B RTC1 1. GND1 ENTER Send the UM51 CROSS [position] AT [time] message to AIRCRAFT. 2. AIRCRAFT VERIFY Check AIRCRAFT receives the UM51 CROSS [position] AT [time] message from GND1. 3. AIRCRAFT AIRCRAFT sends a DM100 LACK message to acknowledge UM51 CROSS [position] AT [time] message. 4. GND1Disp VERIFY Check GND1 receives the DM100 LACK message acknowledging the UM51 CROSS [position] AT [time] message. 5. AIRCRAFT ENTER Send the DM0 WILCO message in response to UM51 CROSS [position] AT [time] message. 6. GND1Disp VERIFY Check GND1 receives the DM0 WILCO message in response to UM51 CROSS [position] AT [time] message. 7. GND1 ENTER Send UM227 LACK message to acknowledge DM0 WILCO message. 8. AIRCRAFT VERIFY Check this time type dialogue appears as CLOSED Comments: Run this test with the DM1 UNABLE response instead of the DM0 WILCO. This dialogue can also be lengthened using the DM2 STANDBY. Issue

29 CPDLC Messages Exchange ACL Instruction type dialogue CPDLC_N160 To check that the Airborne System correctly handles an instruction type dialogue. This ACL dialogue is initiated by ground side. ED110B Requirements ES DLS Requirements: A.2.1.1/A.2.1.2/A / A /B RTC1 1. GND1 ENTER Send the UM123 SQUAWK [code] message to AIRCRAFT. 2. AIRCRAFT VERIFY Check AIRCRAFT receives the UM123 SQUAWK [code] message from GND1. 3. AIRCRAFT AIRCRAFT sends a DM100 LACK message to acknowledge UM123 SQUAWK [code] message. 4. GND1Disp VERIFY Check GND1 receives the DM100 LACK message acknowledging the UM123 SQUAWK [code] message. 5. AIRCRAFT ENTER Send the DM0 WILCO message in response to UM123 SQUAWK [code] message. 6. GND1Disp VERIFY Check GND1 receives the DM0 WILCO message in response to UM123 SQUAWK [code] message. 7. GND1 ENTER Send UM227 LACK message to acknowledge DM0 WILCO message. 8. AIRCRAFT VERIFY Check the instruction type dialogue appears as CLOSED Variant: Runt this test with the DM1 UNABLE response instead of the DM0 WILCO. This dialogue could also be lengthened using the DM2 STANDBY. Issue

30 Concatenated message elements CPDLC_N190 To check that the Airborne System and the Ground System correctly send messages conveying concatenated message elements. RTC1 ED110B Requirements: / ES DLS Requirements A.2.1.1/A.2.1.2/A.2.3.3/B.2.2.1/B No SYSTEM Action Description 1. GND1 ENTER Send the CPDLC-message containing the following concatenation: UM20 CLIMB TO [level] + UM106 MAINTAIN [speed]. 2. AIRCRAFT VERIFY Check AIRCRAFT receives the CPDLC-message indication containing the following: UM20 CLIMB TO [level] + UM106 MAINTAIN [speed]. 3. AIRCRAFT AIRCRAFT sends the DM100 LACK message to GND1 to acknowledge UM20 CLIMB TO [level] + UM106 MAINTAIN [speed] message. 4. GND1Disp VERIFY Check GDN1 receives the DM100 LACK message from AIRCRAFT acknowledging the UM20 CLIMB TO [level] + UM106 MAINTAIN [speed] message. 5. AIRCAFT1 ENTER Send the DM1 UNABLE + DM66 DUE TO AIRCRAFT PERFORMANCE in response to the UM20 CLIMB TO [level] + UM106 MAINTAIN [speed] message. 6. GND1Disp VERIFY Check GND1 receives the DM1 UNABLE + DM66 DUE TO AIRCRAFT PERFORMANCE message. 7. GND1 ENTER Send the UM227 LACK message to AIRCRAFT to acknowledge DM1 UNABLE + DM66 DUE TO AIRCRAFT PERFORMANCE message. 8. AIRCRAFT VERIFY Check both Level and Speed type dialogues appear as CLOSED Comments: The dialogue could also be completed with the DM0 WILCO response instead of the DM1 UNABLE. This dialogue could also be lengthened using the DM2 STANDBY. Issue

31 AMC Service CDPLC_N250 To check that the Airborne system is capable of receiving a Microphone Check message. RTC1 ED110B Requirements: ES DLS Requirements: A.2.1.1/A.2.1.2/A / A.2.4.3//B GND1 ENTER Send the UM157 Check Stuck Microphone [frequency] to AIRCRAFT 1 2. AIRCRAFT VERIFY Check AIRCRAFT receives the UM157 CHECK STUCK MICROPHONE [frequency] message. 3. AIRCRAFT AIRCRAFT sends the DM100 LACK message to acknowledge the UM157 CHECK STUCK MICROPHONE [frequency] message. 4. GND1Disp VERIFY Check GND1 receives the DM100 LACK acknowledging the UM157 Check Stuck Microphone [frequency] Remarks: Some implementations may use UM183 instead of UM157 as described in ED110B. Some implementations do not require LACK when sending the UM157 CHECK STUCK MICROPHONE [frequency] message. In this case, steps 3 and 4 are not executed. Check the UM157 dialogue appears as CLOSED on air and ground display systems. Issue

32 CPDLC Timers CPDLC timer: Airborne tr timer CPDLC_N220 To check that the Airborne System correctly implements requirements related to the tr timer. This test describes the nominal case of tr timer management. Note: as ED-110B states that implementation of tr timer is a local matter, this test is applicable only if the Airborne System implements the tr timer. RTC1 ED110B Requirements / / ES DLS Requirements: A.2.1.1/A.2.1.2/A //B AIRCRAFT ENTER Send the DM6 REQUEST [level] message to GND1. 2. AIRCRAFT VERIFY Check appropriate message status from history logs for DM6 3. GND1Disp VERIFY Check GND1 receives the DM6 REQUEST [level] message from AIRCRAFT. 4. GND1 ENTER Send UM227 LACK message to acknowledge DM6 REQUEST [level] message within the time period of the tr timer expiry value. (40secs). 5. AIRCRAFT AIRCRAFT receives the UM227 LACK message, acknowledging DM6 REQUEST [level] message. 6. AIRCRAFT VERIFY Check appropriate message status from history logs for DM6 7. GND1 ENTER Send UM20 CLIMB TO [level] to AIRCRAFT in response to DM6 REQUEST [level] message. 8. AIRCRAFT VERIFY AIRCRAFT receives UM20 CLIMB TO [level] in response to DM6 REQUEST [level] message. 9. GND1Disp VERIFY Check GND1 receives DM100 LACK message, acknowledging UM20 CLIMB TO [level] message. 10. AIRCRAFT ENTER Send DM0 WILCO message in response to UM20 CLIMB TO [level] message. 11. GND1Disp VERIFY Check GND1 receives DM0 WILCO message in response to UM20 CLIMB TO [level] message. 12. GND1 ENTER Send UM227 LACK message to acknowledge the DM0 WILCO message. 13. AIRCRAFT VERIFY Check the level dialogue type is CLOSED Remark: Issue

33 CPDLC timer: Airborne ttr timer expiry CPDLC_N230 Demonstrate that expiry of a ttr timer following an uplink message without an aircrew response causes a warning to be displayed at the airborne HMI, and an ERROR message to be sent. Note: as the test focuses on ttr timer, the steps related to LACK messages exchanges will not be detailed. RTC1 ED110B Requirements / / ES DLS Requirements: A.2.1.1/A.2.1.2/A /B No SYSTEM Action Description 1. GND1 ENTER Send the UM20 CLIMB TO [level] to AIRCRAFT 2. AIRCRAFT VERIFY Check UM20 CLIMB TO [level] message is received 3. WAIT Wait ttr timer value (100 sec.) 4. GND1Disp VERIFY Check a DM62 ERROR [errorinformation] message with the choice (2) followed by message element DM98 (AIR SYSTEM TIMEOUT) is received 5. AIRCRAFT VERIFY Check the aircrew is informed of the timeout. Check the level type dialogue with GND1 is CLOSED. Remarks: Issue

34 CPDLC timer: Airborne ttr timer reset and closure response CPDLC_N231 Demonstrate that a STANDBY response to an uplink message resets the ttr timer, and that a subsequent aircrew closure response can be sent. RTC1 ED110B Requirements / / / ES DLS Requirements: A.2.1.1/A.2.1.2/A /B No SYSTEM Action Description 1. GND1 ENTER Send the UM20 CLIMB TO [level] to AIRCRAFT 1 2. AIRCRAFT VERIFY UM20 CLIMB TO [level] message is received 3. WAIT Wait 60 seconds 4. AIRCRAFT ENTER Send the DM2 STANDBY in response to UM20 CLIMB TO [level] message. 5. AIRCRAFT VERIFY STANDBY response is annotated and closure responses (WILCO/UNABLE) are still available 6. GND1Disp VERIFY Check GND1 receives the DM2 STANDBY message 7. WAIT Wait 60 seconds 8. AIRCRAFT ENTER Send the DM0 WILCO message in response to UM20 CLIMB TO [level] message 9. GND1Disp VERIFY DM0 WILCO message in response to UM20 CLIMB TO [level] message is received 10. AIRCRAFT VERIFY Check the CPDLC level type dialogue is CLOSED Remarks: The level type dialogue could also be completed with the DM1 UNABLE response instead of the DM0 WILCO. Issue

35 CPDLC timer: Airborne ttr timer expiry after Standby CPDLC_N232 Demonstrate that a STANDBY response to an uplink message resets the ttr timer, and upon expiry without a further aircrew response causes a warning to be displayed at the airborne HMI, and a downlink DM62 ERROR message to be sent RTC1 ED110B Requirements / / / ES DLS Requirements: A.2.1.1/A.2.1.2/A /B No SYSTEM Action Description 1. GND1 ENTER Send UM20 CLIMB TO [level] message to AIRCRAFT 1 2. AIRCRAFT VERIFY UM20 CLIMB TO [level] message is received 3. WAIT Wait 30 seconds 4. AIRCRAFT ENTER Send the DM2 STANDBY in response to UM20 CLIMB TO [level] message. 5. AIRCRAFT VERIFY STANDBY response in annotated and closure responses are still available 6. GND1Disp VERIFY Check GND1 receives the DM2 STANDBY message 7. WAIT Wait ttr timer value (100 seconds) 8. GND1Disp VERIFY Check a DM62 ERROR [errorinformation] message with the choice (2) followed by message element DM98 (AIR SYSTEM TIMEOUT) is received 9. AIRCRAFT VERIFY Check the aircrew is informed of the timeout 10. AIRCRAFT VERIFY Check the CPDLC level type dialogue is CLOSED/EXPIRED Remarks: Issue

36 ACM service Internal transfer: nominal case CPDLC_N260 To verify that the Airborne system correctly handles an internal transfer of frequency (from T-Sector to R-Sector). RTC1 ED110B Requirements: ES DLS Requirements: A.2.1.1/A.2.1.2/A / A / A GND1 (T-sector) ENTER Send the transfer instruction message to AIRCRAFT to identify the next sector for control. 2. AIRCRAFT VERIFY Check AIRCRAFT receives the transfer instruction message identifying the next sector for control. 3. AIRCRAFT AIRCRAFT sends a DM100 LACK message to acknowledge the transfer instruction message. 4. GND1Disp (T-sector) VERIFY Check GND1 receives the DM100 LACK message acknowledging the transfer instruction message. 5. AIRCRAFT ENTER Send the DM0 WILCO in response to the transfer instruction message. 6. GND1Disp (T-Sector) VERIFY Check GND1 receives the DM0 WILCO message in response to the transfer instruction message. 7. GND1 (T-Sector) ENTER Send the UM227 LACK message to acknowledge the DM0 WILCO message. 8. AIRCRAFT VERIFY Check AIRCRAFT receives the UM227 LACK acknowledging the DM0 WILCO message. 9. AIRCRAFT ENTER Send DM89 MONITORING [unitname] [frequency] to confirm unit name and frequency assignment. 10. GND1Disp (R-Sector) 11. GND1 (R-Sector) VERIFY ENTER Check GND1 receives the DM89 MONITORING [unitname] [frequency] confirming unit name and frequency assignment. Send the UM227 LACK message to acknowledge DM89 MONITORING message. 12. AIRCRAFT VERIFY Check AIRCRAFT receives the UM227 LACK message acknowledging DM89 MONITORING [unitname] [frequency] message. 13. GND1 (R-Sector) ENTER Send the UM183 CURRENT ATC UNIT message, specifying GFD, Facility Name and Facility Function. 14. AIRCRAFT VERIFY Check AIRCRAFT receives the UM183 CURRENT ATC UNIT message, specifying GFD, Facility Name and Facility Function. 15. AIRCRAFT AIRCRAFT sends a DM100 LACK message to acknowledge the UM183 CURRENT ATC UNIT message. 16. GND1Disp (R-Sector) VERIFY Check GND1 receives the DM100 LACK message acknowledging the UM183 CURRENT ATC UNIT message. Remarks: The transfer instruction message element may be UM117 CONTACT [unitname] [frequency] or UM120 MONITOR [unitname] [frequency]. * Steps 9-12 are performed only when the transfer instruction is UM120 MONITOR. Check all CPDLC dialogues with GND1 appear as CLOSED for AIRCRAFT. Issue

37 Internal transfer: rejected CPDLC_N270 To verify that the Airborne system correctly rejects an internal transfer of frequency (from T-Sector to R-Sector). RTC1 ED110B Requirements: ES DLS Requirements: A.2.1.1/A.2.1.2/A GND1 (T-sector) ENTER Send the transfer instruction message to AIRCRAFT to identify the next sector for control. 2. AIRCRAFT VERIFY Check AIRCRAFT receives the transfer instruction message identifying the next sector for control. 3. AIRCRAFT AIRCRAFT sends a DM100 LACK message to acknowledge the transfer instruction message. 4. GND1Disp (T-sector) VERIFY Check GND1 receives the DM100 LACK message acknowledging the transfer instruction message. 5. AIRCRAFT ENTER Send the DM1 UNABLE in response to the transfer instruction message. 6. GND1Disp VERIFY Check GND1 receives the DM1 UNABLE message in response to (T-Sector) the transfer instruction message. 7. GND1 ENTER (T-Sector) 8. AIRCRAFT VERIFY Check the CPDLC dialogue is CLOSED Remarks: Send the UM227 LACK message to acknowledge the DM1 UNABLE message. The transfer instruction message element may be UM117 CONTACT [unitname] [frequency] or UM120 MONITOR [unitname] [frequency]. Issue

38 Internal transfer: Ttr timeout CPDLC_N280 To verify that the Airborne system correctly handles a ttr timeout during an internal transfer of frequency (from T-Sector to R- Sector). RTC1 ED110B Requirements: ES DLS Requirements: A.2.1.1/A.2.1.2/A GND1 (T-sector) ENTER Send the transfer instruction message to AIRCRAFT to identify the next sector for control. 2. AIRCRAFT VERIFY Check AIRCRAFT receives the transfer instruction message identifying the next sector for control. 3. AIRCRAFT AIRCRAFT sends a DM100 LACK message to acknowledge the transfer instruction message. 4. GND1Disp (T-sector) VERIFY Check GND1 receives the DM100 LACK message acknowledging the transfer instruction message. 5. WAIT Wait 100 secs 6. AIRCRAFT AIRCRAFT sends a DM62 ERROR [errorinformation] message with choice as 2 concatenated with a DM98 FREETEXT message ( AIR SYSTEM TIMEOUT ) 7. GND1Disp (T-Sector) VERIFY Check that GND1 receives the DM62 ERROR [errorinformation] message with choice as 2 concatenated with a DM98 FREETEXT message ( AIR SYSTEM TIMEOUT ) 8. AIRCRAFT VERIFY Check the CPDLC dialogue with GND1 appears as EXPIRED. Remarks: The transfer instruction message element may be UM117 CONTACT [unitname] [frequency] or UM120 MONITOR [unitname] [frequency]. Issue

39 Internal transfer with open air/ground initiated pending dialogs CPDLC_N290 To verify that the AIRBORNE system correctly handles an internal transfer of frequency (from T-Sector to R-Sector) with open air/ground initiated dialogs. RTC1 ED110B Requirements: ES DLS Requirements: A.2.1.1/A.2.1.2/A / A / A.2.2.6/A.2.2.9/A GND1 ENTER Send the UM20 CLIMB TO [level] to AIRCRAFT 2. AIRCRAFT VERIFY Check AIRCRAFT receives the UM20 CLIMB TO [level] message. 3. AIRCRAFT AIRCRAFT sends a DM100 LACK to acknowledge the UM20 CLIMB TO [level] message. 4. GND1Disp VERIFY Check GND1 receives the DM100 LACK acknowledging UM20 CLIMB TO [level] message. 5. AIRCRAFT ENTER Send the DM18 REQUEST [speed] to GND1. 6. GND1Disp VERIFY Check GND1 receives DM18 REQUEST [speed] message. 7. GND1 ENTER Send the UM227 LACK to acknowledge the DM18 REQUEST [speed] message. 8. AIRCRAFT VERIFY Check AIRCRAFT receives UM227 LACK acknowledging the DM18 REQUEST [speed] message. 9. GND1 (T-sector) ENTER Send the transfer instruction message to AIRCRAFT to identify the next sector for control. 10. AIRCRAFT VERIFY Check AIRCRAFT receives the transfer instruction message identifying the next sector for control. 11. AIRCRAFT VERIFY Check that AIRCRAFT sends a DM100 LACK message to acknowledge the transfer instruction message. 12. GND1Disp (T-sector) VERIFY Check GND1 receives the DM100 LACK message acknowledging the transfer instruction message. 13. AIRCRAFT ENTER Send the DM0 WILCO in response to the transfer instruction message. 14. GND1Disp (T-Sector) VERIFY Check GND1 receives the DM0 WILCO message in response to the transfer instruction message. 15. GND1 (T-Sector) ENTER Send the UM227 LACK message to acknowledge the DM0 WILCO message. 16. AIRCRAFT VERIFY Check AIRCRAFT receives the UM227 LACK acknowledging the DM0 WILCO message. 17. AIRCRAFT ENTER Send DM89 MONITORING [unitname] [frequency] to confirm unit name and frequency assignment. 18. GND1Disp (R-Sector) 19. GND1 (R-Sector) VERIFY ENTER Check GND1 receives the DM89 MONITORING [unitname] [frequency] confirming unit name and frequency assignment. Send the UM227 LACK message to acknowledge DM89 MONITORING message. 20. AIRCRAFT VERIFY Check DM89 MONITORING [unitname] [frequency] message status 21. GND1 (R-Sector) ENTER Send a UM183 CURRENT ATC UNIT message, specifying GFD, Facility Name and Facility Function. 22. AIRCRAFT VERIFY Check AIRCRAFT receives the UM183 CURRENT ATC UNIT message, specifying GFD, Facility Name and Facility Function. 23. AIRCRAFT AIRCRAFT sends a DM100 LACK message to acknowledge the UM183 CURRENT ATC UNIT message. Issue

40 24. GND1Disp (R-Sector) VERIFY Check GND1 receives the DM100 LACK message acknowledging the UM183 CURRENT ATC UNIT message. 25. AIRCRAFT ENTER Send the DM0 WILCO message in response to UM20 CLIMB TO [level] message (c.f. step #1). 26. GND1Disp VERIFY Check GND1 receives DM0 WILCO message in response to UM20 CLIMB TO [level] message. 27. GND1 ENTER Send the UM227 LACK message to acknowledge the DM0 WILCO message. 28. AIRCRAFT VERIFY Check DM0 WILCO message status 29. GND1 ENTER Send the UM106 MAINTAIN [speed] in response to DM18 REQUEST [speed] message (c.f. step #5). 30. AIRCRAFT VERIFY Check AIRCRAFT receives the UM106 MAINTAIN [speed] in response to DM18 REQUEST [speed] message. 31. AIRCRAFT AIRCRAFT sends a DM100 LACK to acknowledge the UM106 MAINTAIN [speed]. 32. GND1Disp VERIFY Check GND1 receives the DM100 LACK acknowledging the UM106 MAINTAIN [speed] message. 33. AIRCRAFT ENTER Send the DM0 WILCO in response to UM106 MAINTAIN [speed] message. 34. GND1Disp VERIFY Check GND1 receives DM0 WILCO message in response to UM106 MAINTAIN [speed] message. 35. GND1 ENTER Send UM227 LACK to acknowledge the DM0 WILCO message. 36. AIRCRAFT VERIFY Check DM0 WILCO message status 37. AIRCRAFT VERIFY Check that the transfer instruction, the speed and level type dialogues with GND1 appear as CLOSED Remarks: The transfer instruction message element may be UM117 CONTACT [unitname] [frequency] or UM120 MONITOR [unitname] [frequency]. * Steps are followed only when the transfer instruction is UM120 MONITOR. From step 25, processing of pending dialogues can continue. The speed and level type dialogues could also be completed with the DM1 UNABLE response instead of the DM0 WILCO. Issue