eDEP TCT (Tactical Controller Tools) Detailed Design Document · Since the two STCD conflict detection components must subscribe to this interface to receive the TCT trajectories,

EUROCONTROL Reference GL/eDEP/DDD/TCT/1/2.0

04 Feb 2009

Page 1 of 28

eDEP TCT (Tactical Controller Tools)

Detailed Design Document

Version: 2.0

Date: 04 Feb 2009


04 Feb 2009

Page 2 of 28

Document Change Log Release Author Date of the

release Description of the

release Modifications (sections affected and relevant

information) 2.0 Graffica

(OWEN) 04 Feb 2009 Replacement for 1.0 ALL

Acceptance and Reviewing Procedures Name (s) Date of acceptance/ review Date of approval

Document distribution to/cc Name Role


04 Feb 2009

Page 3 of 28

CONTENTS

1 INTRODUCTION ..........................................................................................................................5

1.1 Related Documents .................................................................................................................5

1.2 References...............................................................................................................................5

1.3 Glossary ..................................................................................................................................5

2 Architectural Design .......................................................................................................................7

2.1 Context....................................................................................................................................7

2.2 Subscribed Data ......................................................................................................................8

2.3 Published Data ........................................................................................................................8

2.4 TCT Service Interface.............................................................................................................9

2.5 Use Cases..............................................................................................................................10

3 TCT Server....................................................................................................................................11

3.1 Overview...............................................................................................................................11

3.2 Required Services .................................................................................................................11

3.3 TCT Component Controller ..................................................................................................12

3.4 Tactical Trajectory Management ..........................................................................................12

3.5 State Vector Trajectory Management ...................................................................................14

3.6 Tactical Conflict Processor ...................................................................................................17

3.7 State Vector Conflict Processor ............................................................................................18

3.8 Server Conflict Messages......................................................................................................18

3.9 Server Conflict Message Distributors ...................................................................................19

3.10 Flight Plan Processor ............................................................................................................19

4 TCT Entities..................................................................................................................................20

4.1 TacticalConflict.....................................................................................................................20

4.2 StateVectorConflict...............................................................................................................20

4.3 MissedManoeuvreConflict....................................................................................................20

4.4 TCTFlight .............................................................................................................................20

5 TCT Client ....................................................................................................................................21

5.1 Tactical Service.....................................................................................................................21

5.2 Client Flight Conflicts...........................................................................................................22

5.3 TCT CWP .............................................................................................................................22

6 TCT Recording .............................................................................................................................25

6.1 TctModule.............................................................................................................................25

6.2 TctDataRecorderImpl............................................................................................................25

7 STCD (Short Term Conflict Detection)........................................................................................26

7.1 Overviw.................................................................................................................................26


04 Feb 2009

Page 4 of 28

7.2 STCD Service .......................................................................................................................26

7.3 STCD Server.........................................................................................................................27

7.4 Stcd Flight Conflict Entity Manager.....................................................................................27

7.5 Operation...............................................................................................................................28


04 Feb 2009

Page 5 of 28

1 INTRODUCTION

This document describes the detailed design of the eDEP TCT component whose functional description is described in the TCT Concept of Operations document, accompanied by screen-shots of the associated HMI features.

In general, the capability for TCT has been integrated into CORE software, so that the graphics classes and the TCT client are extensions to standard eDEP components. The TCT-specific software is thus reduced to the following:

� A modified MTCD server (STCD server) which is an optimised version of the MTCD server for trajectories that are being regularly updated, and improves the accuracy of the conflicts by introducing a double-pass mechanism that evaluates contextual and conflicting aircraft separately.

� A TCT server that creates the Tactical and State Vector trajectories and performs the conflict detection on them (using a dedicated STCD server each type of trajectory). The trajectories and the conflicts (which are transformed into the appropriate classes of TCT conflict) are returned to the TCT client using the normal eDEP subscription mechanism.

� A set of extended graphics in the CWP to add the additional TCT information in the PVD, VAW, and PPD.

1.1 RELATED DOCUMENTS

Document Version Reference Source

TCT Concept Description 1.0 (04/10/2006) EHQ

TCT Mechanisms N/A N/A EHQ

TCT Operational Requirements Document 0.1 (09/03/2006) EHQ

TCT HMI Specifications 0.3 (01/08/2006) EHQ

eDEP_TCT_Concept_of_Operations 1.0 GL/eDEP/CONCEPT/TCT/1/1.0 Graffica

1.2 REFERENCES

Document Version Reference Source

eDEP_GRD_DDD 2.5.3 GL/DEP/DDD/1/2.5.3 Graffica

1.3 GLOSSARY

AFL Actual Flight Level

ATC Air Traffic Control

CFL Cleared Flight Level

CPA Closest Point of Approach

CWP (ATC) Controller Working Position

DFL Dynamic Flight Leg


04 Feb 2009

Page 6 of 28

ECHOES EEC's current CWP HMI standard

EEC Eurocontrol Experimental Centre

eDEP Early Development and Evaluation Platform

FASTI First ATC Supporting Tools Implementation

HMI Human-Machine Interface

MONA Monitoring Aids

MTCD Medium Term Conflict Detection

PPD Potential Problem Display

PVD Plan View Display (CWP Radar Display)

RFL Requested Flight Level

SPD Sector Package Demonstrator (an eDEP demonstrator platform based on ECHOES)

STCA Short Term Conflict Alert

STCD Short Term Conflict Detection

TCT Tactical Controller Tool

VAW Vertical Aid Window

XFL Exit Flight Level (from an ATC Unit)


04 Feb 2009

Page 7 of 28

2 ARCHITECTURAL DESIGN

2.1 CONTEXT

The Context Diagram for the TCT component id shown in Figure 2-1.

Figure 2-1 TCT Context Diagram

2.1.1 Dependent Services

TCT uses the following system services:

� TimeService (for the simulation time)

� AirspaceService (for the airspace definition)

� IFPLService (for the initial flight plans)

� TrackService (for aircraft track data)

� FlightService (for the system flight plan and trajectory data)

� MonitorService (for MONA deviation data)

� PerformanceService (for aircraft peformance)

2.1.2 TCT Dedicated Services

TCT uses the following dedicated services which are connected to servers exclusively used by TCT:

� StcdService components (a dedicated TCT service for short term conflict info - one for Tactical Trajectories, and one for State Vector Trajectories)

� ShortTermConflictService (a dedicated TCT service for finding candidates for State Vector Conflicts)

TCT

CWP

subscribeTacticalConflictMessage subscribeStateVectorConflictMessage subscribeMissedManoeuvreConflictMessage subscribeSystemFlightPlanMessage subscribeSFPLDeletedMessage

TimeService

TrackService

AirspaceService

IFPLService

MonitorService

FlightPlanMessage

TimeTickMessage

FlightService SystemFlightPlanMessage

TrackUpdateMessage

E

E

E

E

R airspace data

DeviationUpdateMessage

E

TacticalConflictMessage StateVectorConflictMessage MissedManoeuvreConflictMessage SystemFlightPlanMessage SFPLDeletedMessage

E

S

PerformanceService

R

performance data


04 Feb 2009

Page 8 of 28

� TrajectoryService (a dedicated TCT service for the updates to the Tactical and StateVector Trajectories)

2.2 SUBSCRIBED DATA

The TCT component requires the following data inputs:

Data Item Origin Description

TimeTickMessage TimeService The TimeTickMessage supplies the simulation time, and enables the event scheduler in the server.

Airspace Data (read at start up)

AirspaceService Provides the waypoint data required in the flight plans and trajectories

Performance Data (read at start up)

PerformanceDervice Provides the aircraft performance data.

FlightPlanMessage IFPLService Provides the Initial Flight Plans for the aircraft in the simulation

TrackUpdateMessage TrackService Provides the position of the aircraft from regular radar updates.

SystemFlightPlanMessage FlightService Provides the FM GROUND trajectories for the aircraft in the simulation.

DeviationUpdateMessage MonitorService Provides alerts when an aircraft deviates from the system GROUND trajectory.

StcdUpdateMessage StcdService Provides the conflict information for the Tactical and State Vector trajectories. The former conflicts are transformed into Tactical Conflicts before being exported to the subscribed clients, whereas the latter conflicts are analysed before being transformed into either State Vector Conflicts or Missed-Manoeuvre Conflicts.

ConflictUpdateMessage ShortTermConflictService This is a conflict message from a dedicated STCA server (not the normal STCA), with wide separation standards so as to detect flights that are candidates for a State Vector Conflict.

TrajectoryUpdateMessage TrajectoryService Provides the Tactical and StateVector Trajectory updates using the ConstraintList created by TCT.

2.3 PUBLISHED DATA

The TCT component provides the following data items:


04 Feb 2009

Page 9 of 28

Data Item Description

SystemFlightPlanMessage Provides for updates for the Tactical Trajectory and the State Vector Trajectory.

SFPLDeletedMessage Provides deletion notification for the Tactical Trajectory and the State Vector Trajectory

TacticalConflictMessage Provides the Tactical Conflict information between Tactical Trajectories.

StateVectorConflictMessage Provides the State Vector Conflict information between State Vector Trajectories.

MissedManoeuvreConflictMessage Provides the Missed-Manoeuvre Conflict information between State Vector Trajectories or between a State Vector Trajectory and a Tactical Trajectory (hybrid conflict).

2.4 TCT SERVICE INTERFACE

The TacticalService has the following interface:

public interface TacticalService extends ComponentS ervice, SystemPlanService { /** * Get the name of the server attached to this s ervice. * @return the name of the server attached to th is service (or null, if none) */ String getAttachedServerName(); /** * Register to receive the StateVectorConflictEv ent for updated StateVectorConflict * information. * @param action the listener for the StateVecto rConflictEvent * @param filter a filter for the StateVectorCon flictEvent * @return the EventScheduler SubscriptionID for the registration */ public SubscriptionID registerForStateVectorConf lictEvent EventListener action, SubscriberFilter filter ); /** * Register to receive the TacticalConflictEvent for updated TacticalConflict information. * @param action the listener for the StateVecto rConflictEvent * @param filter a filter for the StateVectorCon flictEvent * @return the EventScheduler SubscriptionID for the registration */ public SubscriptionID registerForTacticalConflic tEvent ( EventListener actio n, SubscriberFilter filter ); /** * Register to receive the MissedManoeuvreConfli ctEvent for updated MissedManoeuvreConflict * information. * @param action the listener for the MissedMano euvreConflictEvent * @param filter a filter for the MissedManoeuvr eConflictEvent * @return the EventScheduler SubscriptionID for the registration */ public SubscriptionID registerForMissedManoeuvre ConflictEvent ( EventListener actio n, SubscriberFilter filter ); }

Note: The TacticalService extends the SystemPlanService interface to provide the SystemFlightPlanMessage and SFPLDeletedMessage subscription mechanism for the TCT trajectories. Since the two STCD conflict detection components must subscribe to this interface to receive the TCT trajectories, and since TCT is subscribed to those same STCD components to receive the conflicts on those trajectories, there is a two-way dependency between TCT and STCD.


04 Feb 2009

Page 10 of 28

2.5 USE CASES

2.5.1 Initialisation

� Register with the FlightService to receive the system GROUND trajectories

� Register with the TrackService to receive regular aircraft position

� Register with the MonitorService to receive MONA alerts about aircraft deviation

� Register with the StcdServices to receive conflict information for the Tactical Trajectories and the State Vector Trajectories

2.5.2 Tactical Trajectory Update

� Use the system GROUND trajectories and aircraft position to create a Tactical Trajectory which starts at the aircraft position and rejoins (if necessary) the cleared flight plan (using a dedicated trajectory predictor).

� Send a SystemFlightPlanMessage for the Tactical Trajectory to subscribed clients

2.5.3 Tactical Conflict Update

� Receive the detected conflicts from the STCD responsible for the Tactical Trajectory and re-package them as Tactical Conflicts.

� Send a TacticalConflictMessage with the Tactical Conflicts to subscribed clients

2.5.4 Create or Update a State Vector Trajectory

� Analyse the regular ConflictUpdateMessage from the dedicated TCT STCA server with wide tolerances which detect aircraft that could have a State Vector Conflict. For the involved aircraft create a State Vector Trajectory.

� Send a SystemFlightPlanMessage for the State Vector Trajectory to subscribed clients.

2.5.5 Destroy a State Vector Trajectory

� Analyse the regular ConflictUpdateMessage from the dedicated STCA server.

� If a State Vector Trajectory exists for a flight that is not mentioned in the ConflictUpdateMessage then destroy it.

� Send an SFPLDeletedMessage to the subscribed clients.

2.5.6 State Vector Conflict and Missed-Manoeuvre Conflict Update

� Receive the detected conflicts from the STCD responsible for the State Vector Trajectory.

� Analyse each conflict to categorise it as a State Vector Conflict or a Missed-Manoeuvre Conflict

� Re-package the conflicts as State Vector Conflicts or as Missed-Manoeuvre Conflicts.

� Send a StateVectorConflictMessage for the State Vector Conflicts and a MissedManoeuvreConflictMessage for the Missed-Manoeuvre conflicts to the subscribed clients.


04 Feb 2009

Page 11 of 28

3 TCT SERVER

3.1 OVERVIEW

The TCT server (package tct.tct.server) is responsible for the creation and distribution of TCT information to the CWP clients. The TCT server creates and regularly updates the TCT trajectories, then receives the associated conflicts from dedicated STCD servers. The TCT interface contains a subscription mechanism for the clients to be informed of updates to these TCT trajectories and conflicts. The produced objects are:

� Tactical Trajectory

� State Vector Trajectory

� Tactical Conflict

� State Vector Conflict

� Missed-Manoeuvre Conflict

3.2 REQUIRED SERVICES

Figure 3-1 TCT Server Services Class Diagram

Figure 3-1 shows the class diagram for the services used by the TCT server. See section 2.1 for more details.


04 Feb 2009

Page 12 of 28

3.3 TCT COMPONENT CONTROLLER

Figure 3-2 TCTControllerImpl Class Diagram

Following the pattern of other eDEP server components, the TCTControllerImpl class:

� extends ComponentControllerImpl which provides the server component functionality

� has its own TCTDatabase (extending ScenarioImpl) for managing the component's Entity objects

� uses a TCTDefaults class for centralising TCT parameters

3.4 TACTICAL TRAJECTORY MANAGEMENT

The TCT must provide a Tactical Trajectory at all times since it represents the route being followed by the flight.

When the Tactical Trajectory requires updating, TCT uses the Constraint List associated with the current GROUND trajectory and the current aircraft position to calculate a new Tactical Trajectory Constraint List which is sent to the dedicated trajectory predictor; the returned Tactical Trajectory is then sent to the subscribed clients in a SystemFlightPlanMessage.

3.4.1 Criteria for Updating the Tactical Trajectory

The Tactical Trajectory is updated if:

� the system GROUND trajectory is updated

� the current aircraft position is outside of a tight tolerance to the existing Tactical Trajectory (much tighter than the MONA tolerances).

� at least once per minute so that the Tactical Conflict STCD is triggered regularly to re-calculate the conflicts up to the TCT lookahead time.


04 Feb 2009

Page 13 of 28

3.4.2 Constructing the Tactical Trajectory Constraint List

A new Constraint List for the Tactical Trajectory is constructed by the TacticalTrajectoryUpdater using the following process:

� extract the Constraint List for the current GROUND trajectory (including the current heading and/or height-rate clearances).

� insert a position constraint at the current aircraft position.

� if deviating (according to the MONA MonitorService), determine the waypoint in the flight plan at which the GROUND trajectory should be re-joined and remove any intermediate lateral constraints. The rejoin point should be at or before the exit from the current ATC sector.

� if climbing or descending, remove any altitude constraint that interferes with the current CFL. Other altitude constraints are left alone.

3.4.3 Updating the Tactical Trajectory

The constructed Constraint List is sent to the trajectory predictor using the dedicated TrajectoryService. The TacticalTrajectoryProcessor listens for the returned trajectory which is sent to subscribed clients in a standard SystemFlightPlanMessage. Since the STCD associated with the Tactical Trajectory is a client for this message, this will trigger an update to the Tactical Conflicts.

3.4.4 Sequence Diagram

Figure 3-3 Tactical Trajectory and Conflicts Sequence Diagram

Figure 3-3 shows the basic sequence of events when a Tactical Trajectory and its associated conflicts are updated. When an update is necessary the TacticalTrajectoryUpdater constructs a Constraint List which is submitted to the trajectory predictor (TP). The returned trajectory is notified to the subscribed clients (CWP and STCD) in a SystemFlightPlanMessage. The STCD updates the conflicts for the new trajectory and returns them to the TacticalConflictProcessor which sends them to the


04 Feb 2009

Page 14 of 28

CWP clients in a TacticalConflictMessage (using an intermediary TacticalConflictMessageDistributor which sends only the conflicts required by the AtcAuthority of each client)

3.5 STATE VECTOR TRAJECTORY MANAGEMENT

The State Vector Trajectory is not needed all the time since it is only shown in the HMI when there is a State Vector Conflict.

When the State Vector Trajectory requires creating/updating, TCT uses the current heading and height-rate clearances (from the Constraint List associated with the current GROUND trajectory) and the current aircraft position to calculate a new State Vector Trajectory Constraint List which is sent to the dedicated trajectory predictor; the returned State Vector Trajectory is then sent to the subscribed clients in a SystemFlightPlanMessage.

3.5.1 Performance Issues

The updating of the State Vector (SV) Trajectory on every track cycle would be onerous and inefficient due to the nature of the operation of the STCD component which detects conflicts on that trajectory. The STCD server compares all trajectories whenever a single trajectory is updated, thus such a policy would entail the computing of conflicts between ALL SV trajectories after EACH SV trajectory update following the track update. To improve this situation, two mechanisms are considered:

1. The use of a dedicated STCA-type server using wide separation margins in order to detect candidates for SV conflicts. Since the STCA server (unlike the STCD server) works with tracks, and a single track update is for all flights in eDEP, then a single operation determines all the aircraft at risk. When a candidate conflict is found then a SV trajectory is created for the candidate flights which are picked up by the STCD server for the definitive check for a SV conflict. This limits the number of trajectories and greatly reduces the load in the SV STCD server.

2. The use of a similar mechanism as for the Tactical Trajectory whereby a SV Trajectory always exists but is only updated when the aircraft is outside of a tolerance from the existing SV trajectory. This could be coupled with a special mode in the STCD server to only perform a conflict search after a track update, rather than as each trajectory is updated. The conflict search would probably be programmed to occur half way through a track cycle to ensure that all the associated SV trajectories were updated following the associated track update.

The first method is currently implemented, since the SV trajectory is only needed when there is a State Vector conflict (unlike the Tactical Trajectory which must always be available). This method is the most efficient in eDEP, but it relies on the wide separation standards in the special STCA server catching the conflict candidates. E.g. when an aircraft is climbing from low altitude, the speed and height-rate of the aircraft change substantially during the TCT's 10 minute lookahead and the wider margins need to ensure that all the candidates are found when using an STCA algorithm that relies on current height-rate and speed.

3.5.2 Criteria for Updating the State Vector Trajectory

A ShortTermConflictsEventHandler in the TCT server listens for a ShortTermConflictsEvent from the dedicated ShortTermConflictService. The ShortTermConflictsEvent (received every track cycle while there is something to report) contains details of flights that are involved in a state vector conflict based on the current track, speed, and height-rate using large separation standards, as described above. All flights in the message are considered as candidates for a State Vector Conflict.


04 Feb 2009

Page 15 of 28

3.5.3 Updating the State Vector Trajectory Conflict List

For each flight which is a candidate for a State Vector Conflict, the State Vector Trajectory Constraint List is constructed by the StateVectorTrajectoryUpdater associated with the TCTFlight as follows:

� extract the current clearance information from the current GROUND trajectory constraint list, and create a constraint list with these clearances with a constraint at the current aircraft position.

� create a lateral constraint ahead of the aircraft following current track and up to the TCT lookahead time.

� if the CFL != AFL then set a forward altitude constraint = CFL on the first constraint.

3.5.4 Updating the State Vector Trajectory

The constructed Constraint List is sent to the trajectory predictor using the dedicated TrajectoryService. The StateVectorTrajectoryProcessor listens for the returned trajectory which is sent to subscribed clients in a standard SystemFlightPlanMessage. Since the STCD associated with the State Vector Trajectory is a client for this message, this will trigger an update to the State Vector Conflicts.

3.5.5 Deleting the State Vector Trajectory

If there exists a State Vector Trajectory for a flight that is no longer in the candidate list, the trajectory is deleted and clients notified with a standard SFPLDeletedMessage. Since the STCD associated with the State Vector Trajectory is a client for this message, this will trigger an update to remove any remaining State Vector Conflicts.

3.5.6 Sequence Diagram

Figure 3-4 State Vector Trajectory and Conflicts Sequence Diagram 1


04 Feb 2009

Page 16 of 28


Figure 3-4 and Figure 3-5 show the basic sequence of events when a State Vector Trajectory and its associated conflicts are updated. For each flight listed in the ShortTermConflictsEvent from the dedicated ShortTermConflictService, the ShortTermConflictsEventHandler requests the StateVectorTrajectoryUpdater to construct a Constraint List which is submitted to the trajectory predictor (TP) . The returned trajectory is notified to the subscribed clients (CWP and STCD) in a SystemFlightPlanMessage. The STCD updates the conflicts for the new trajectory and returns them to the StateVectorConflictProcessor which uses a StateVectorCriticalManoeuvreSetter to classify the conflicts as State Vector Conflicts or as MissedManoeuvre Conflicts. These are then sent to the CWP clients in a StateVectorConflictMessage and a MissedManoeuvreConflictMessage (using an intermediary StateVectorConflictMessageDistributor and MissedManoeuvreConflictMessageDistributor which send only the conflicts required by the AtcAuthority of each client).


04 Feb 2009

Page 17 of 28


Figure 3-6 shows the simpler case where a flight that has a State Vector Trajectory ceases to be a candidate for a State Vector Conflict. An SFPLDeletedMessage is notified to the subscribed clients (CWP and STCD). The STCD deletes any conflicts for the flights and notifies the empty list to the StateVectorConflictProcessor which in turn sends an empty StateVectorConflictMessage and MissedManoeuvreConflictMessage to the subscribed clients. Note: the messages mentioned above are only sent if there previously existed State Vector and Missed Manoeuvre Conflicts that need to be removed.

3.6 TACTICAL CONFLICT PROCESSOR

As previously described, when a Tactical Trajectory is updated, the TCT receives the latest conflict information message from the associated STCD service. The TacticalConflictProcessor listens for this message and re-packages each conflict as a TacticalConflict in a TacticalConflictMessage which is forwarded to the clients using a TacticalConflictMessageDistributor.

Figure 3-7 TacticalConflictProcessor Class Diagram


04 Feb 2009

Page 18 of 28

3.7 STATE VECTOR CONFLICT PROCESSOR

As mentioned previously, when a State Vector Trajectory is updated the TCT receives the latest conflict information message from the associated STCD service. The StateVectorConflictProcessor listens for this message and re-packages each conflict as a MissedManoeuvreConflict or as a StateVectorConflict depending on the presence of a critical manoeuvre in the flight plan of one (or both) of the flights which, if followed, means that the conflict will not materialise. If one of the flights is not following its flight plan then the conflict becomes a StateVectorConflict immediately.

Figure 3-8

It is the StateVectorCriticalManoeuvreSetter class which performs the test for the critical manoeuvre. to decide if the conflict is a StateVectorConflict or MissedManoeuvreConflict. For a MissedManoeuvreConflict, a further probe is performed (using a HybridDetector) to find the intersection of the subject flight's State Vector Trajectory and the other flight's Tactical Trajectory (rather than between the two State Vector Trajectories); if this exists it replaces the original conflict since, for the missed-manoeuvre case, the ATC Controller needs to know the intersection between the subject flight's State Vector Trajectory and the other flight's route, represented by the Tactical Trajectory. If this hybrid conflict doesn't exist then the original conflict is used, and it represents a potential conflict if BOTH flights do not perform a critical manoeuvre.

Note: Normally a conflict is symmetric between two flights, and so the conflict Entity is the same for both flights, and as the trajectory of each of the two flights is updated then it is the same conflict being updated. For a Missed Manoeuvre Conflict this symmetry is lost and each flight needs its own view of the same problem; thus when the first flight's trajectory is updated and a Missed Manoeuvre Conflict is created, the name of the Entity is suffixed with the callsign of the flight so that it remains independent of the other Flight's Entity. The same process is performed when the second flight's trajectory is updated, and because the Entities have different names they will co-exist in the TCT clients' Entity database.

The StateVectorConflicts are put in a StateVectorConflictMessage and sent back to the clients by the StateVectorConflictMessageDistributor, and the MissedManoeuvreConflicts are put in a MissedManoeuvreConflictMessage and sent back to the clients by the MissedManoeuvreConflictDistributor.

3.8 SERVER CONFLICT MESSAGES

The TCT server provides 3 types of conflict message for subscribed clients:

� TacticalConflictMessage

� StateVectorConflictMessage


04 Feb 2009

Page 19 of 28

� MissedManoeuvreConflictMessage

Figure 3-9 TCT Server Messages Class Diagram

The conflict message classes extend the standard core MTCDUpdateMessage and add no extra functionality. (Each conflict has its own message class to make the interface clearer)

3.9 SERVER CONFLICT MESSAGE DISTRIBUTORS

The TCT server only sends information to a client concerning conflicts which are of concern to the AtcAuthority specified during the conflict subscription process. There is a distributor for each class of conflict message.

Figure 3-10 TCT Server Message Distributors Class Diagram

E.g. if the TacticalConflicts are updated for a flight, the TacticalConflictMessageDistibutor sends a unique TacticalConflictMessage to each client containing only the conflicts relevant to the declared AtcAuthority.

3.10 FLIGHT PLAN PROCESSOR

The FlightPlanProcessor receives the initial flight plans from the IFPLService and creates an associated Flight Entity object to which it attaches the flight plan.


04 Feb 2009

Page 20 of 28

4 TCT ENTITIES

TCT introduces the following minor extensions to MTCD core Entities.

4.1 TACTICALCONFLICT

The tct.tct.entity.TacticalConflict extends the atc.mtcd.entity.Conflict and adds:

� static attribute 'tctConflictsNotPlanned' TRUE if the conflict should be immediately in the responsibility of the Tactical Controller (resource-defined).

4.2 STATEVECTORCONFLICT

The tct.tct.entity. StateVectorConflict extends the atc.mtcd.entity.Conflict and adds:

� static attribute 'tctConflictsNotPlanned' TRUE if the conflict should be immediately in the responsibility of the Tactical Controller (resource-defined).

4.3 MISSEDMANOEUVRECONFLICT

The tct.tct.entity. MissedManoeuvreConflict extends the atc.mtcd.entity.Conflict and adds:

� FlightIdentity subjectFlight; the subject flight which has the 'critical manoeuvre' that must be performed to avoid the conflict.

� Waypoint criticalWaypoint; the waypoint at which the 'critical manoeuvre' must be performed

4.4 TCTFLIGHT

The tct.tct.entity.TCTFlight is only used in the TCT server, and stores state about the current number of conflicts that have been signalled to the TCT clients, and also objects for updating the TCT trajectories.


04 Feb 2009

Page 21 of 28

5 TCT CLIENT

5.1 TACTICAL SERVICE

The TCT client (package tct.tct.client) communicates with the server using a TacticalService class which extends the CommonConflictServiceImpl (the same base class as for the standard MTCD's ConflictService).

The TacticalService contains a separate FlightConflictReceiver for each type of conflict received from the server, and each receiver has its own FlightConflictUpdater which put the conflicts into a unique EntityManager, and attaches the conflicts to the Flight's FlightConflict plugin into a unique ConflictList.

The TacticalService also has an SFPLReceiver and an SFPLDeletedReceiver which manage the creation, updating, and deletion of the TCT trajectories.

Other than for these additions, the TacticalService works in the same way as the MTCD ConflictService, and ensures that the pattern for updating and receiving the TCT conflicts and trajectories integrates seamlessly into the existing eDEP platform.

Figure 5-1 Tactical Service Classes

Figure 5-1 shows the class diagram for the TacticalService. Each type of conflict has its own receiver and updater instances, as well as a unique EntityManager. The conflicts are attached to the associated Flight by the FlightConflictUpdater instances.

There is also an SFPLReceiver for receiving updates to the TCT Trajectories, and an SFPLDeletedReceiver for receiving notifications of deleted TCT trajectories.

Otherwise the TacticalServiceImpl inherits its behaviour from the CommonConflictServiceImpl which manages issues concerning: the inter-CWP communication; the AtcAuthority; the deletion of flights; and the regular updating of the conflicts in the client as the aircraft advances.


04 Feb 2009

Page 22 of 28

5.2 CLIENT FLIGHT CONFLICTS

Apart from being stored in a dedicated EntityManager, each conflict is also stored with the associated Flight Entities. No extensions were necessary for TCT since the core platform already segregates conflicts from different EntityManagers and conflicts associated with different trajectory tags (see the MTCD section of the eDEP_GRD_DDD for details).

E.g. a list of the Tactical Conflicts for a flight may be obtained using:

flight.getPlugin(FlightConflict.PLUGIN_ID).getConflictList (AbstractConflict.getTypeId(TacticalConflict.class), null, null);

…where the null parameters are for an optional trajectory tag and an optional results filter.

5.3 TCT CWP

The CWP used in TCT (package tct.graphics) has a number of extensions in order to:

� visualise the various TCT conflicts in the aircraft label following a defined priority

� visualise the TCT Flight Legs in the PVD for the Tactical and State Vector Trajectories, with their associated conflict lines and symbols

� extend the FlightLegConfigurer interface for configuring the opening of TCT Flight Legs from the aircraft label buttons.

� add the State Vector Conflict Indication object

� add the extra conflicts, scope shading, lookahead-time sliders and separation sliders to the PPD

� extend the CWP's ConflictVisibility interface to define the parameters for the visibility of TCT conflict information in the HMI

5.3.1 Aircraft Label

The aircraft label shown in the PVD is a special tct.graphics.aclabel.TctAccLabel class which extends the FastiAccLabel and differs only in that it incorporates several derived atcgraphics.eatmp.buttons.ConflictButton instances (one for each type of conflict), and that it uses a modified fasti.graphics.buttons.aclabel.ExitWaypointButton that opens the SPD atcgraphics.echoes.menus.DatalinkDirectMenu menu rather than the standard EATMP atcgraphics.graphics.menus.DirectMenu. In the PVD, the SPD version shows a dotted line from the aircraft position to the waypoint under the cursor in the menu.

See the eDEP_TCT_Concept_of_Operations for more details on the different conflicts and the SPD DatalinkDirectMenu menu.

5.3.2 Aircraft Label Conflict Indicator

In order to be able to have the appropriate Conflict Indicator (RED, YELLOW or BLUE dot) in the aircraft label to signal a conflict to the ATC controller, the standard MTCD atcgraphics.eatmp.buttons.ConflictButton has been extended to create three new classes, the tct.graphics.buttons.TacticalConflictButton for the Tactical Conflict, the tct.graphics.buttons.MissedManoeuvreConflictButton for the Missed-Manoeuvre Conflict, and the tct.graphics.buttons.StateVectorConflictButton for the State Vector Conflict. These classes are very simple since they simply override the tag of the associated trajectory and the TYPE_ID of the associated conflict. The MissedManoevreConflictButton also verifies that the current flight is the subject flight. Only one of the buttons will be displayed at any one time (the highest priority) and this is controlled by a special AwsFieldDisplayer (tct.graphics.displayfunctions.TctConflictDisplayer). If the State Vector Conflict has the highest priority the StateVectorConflictButton is not shown since this conflict has a different HMI representation.

See the eDEP_TCT_Concept_of_Operations for more details on the priority of conflicts.


04 Feb 2009

Page 23 of 28

5.3.3 Flight Legs

TCT uses a number of specific Flight Leg classes (package tct.graphics.flightleg.*) and they have the capability to work in a TCT ENABLED or DISABLED mode (in which case the revert to the equivalent Flight Leg for the system GROUND trajectory).

See the eDEP_TCT_Concept_of_Operations for images of these Flight Legs.

5.3.3.1 TctMtcdFlightLegSet

The TctMtcdFlightLegSet extends the CORE MtcdFlightLegSet and adds the following capability:

� It provides a dual MTCD/TCT capability to work either with the Tactical Trajectory (TCT enabled) or with the GROUND trajectory (TCT DISABLED).

� It modifies the scope line of the Flight Leg to be for the TCT lookahead time

� It changes the scope colour to ORANGE if the flight is deviating according to MONA.

5.3.3.2 TctMissedManoeuvreFlightLegSet

The TctMissedManoeuvreFlightLegSet is a new TCT Flight Leg for showing the special case where a conflict would exist if a flight did not perform a 'critical' manoeuvre in the flight plan.

5.3.3.3 TctPoFlightLegSet

The TctPoFlightLegSet is an extended PoFlightLegSet. It modifies the associated trajectory and conflict to be the Tactical Trajectory and Tactical Conflict respectively. It falls back to operate as an ordinary PoFlightLegSet if TCT is disabled.

5.3.3.4 TctSvoFlightLegSet

The TctSvoFlightLegSet is a new TCT Flight Leg for showing a State Vector Conflict between two State Vector Trajectories. This is similar to the PoFlightLegSet, but shows the Flight Leg in YELLOW.

5.3.4 FlightLegConfigurer

The default atcgraphics.graphics.flightleg.configurer.DefaultFlightLegConfigurer is extended by a tct.graphics.flightleg.configurer.TctFlightLegConfigurer. This configurer is associated with the eDEP PVD Radar Toolbox and permits the user to associate a particular HMI action with the opening of a Flight Leg in the PVD and/or VAW, and whether the Extended Label Window is opened for the flight. The TCT class extends the capability for the TCT Flight Legs.

See the eDEP_TCT_Concept_of_Operations for an diagram of the FlightLegConfigurer.

5.3.5 State Vector Conflict Indication

The tct.graphics.cwp.plugins.conflictdisplay.ConflictIndication object is a new TCT class which displays a YELLOW line between two aircraft that have a State Vector Conflict. The line contains a label which displays the time to the start of the conflict, and the minimum separation between the two flights at the CPA.

The ConflictIndication is only shown if:

� There exists a State Vector Conflict

� The two aircraft are in ASSUMED or ADVANCED coordination state

� There is not an STCA alert for one of the two flights

� The separation and time to start of conflict are within the thresholds that the local ATC Controller has specified (reflected in the local ConflictVisibility plugin interface).

See the eDEP_TCT_Concept_of_Operations for a diagram of the State Vector Conflict Indication.


04 Feb 2009

Page 24 of 28

5.3.6 PPD Additions

The TCT uses existing CORE objects to provide the extra functionality. See the eDEP_TCT_Concept_of_Operations for diagrams of the TCT PPD.

5.3.6.1 TctCursorDisplayer

The standard atcgraphics.eatmp.ppd.cursors.DefaultCursorDisplayer is extended to create a tct.graphics.ppd.cursors.TctCursorDisplayer which modifies the RED tactical controller lookahead time cursor to correspond to the TCT tactical lookahead time. It also adds a new RED cursor for the TCT Tactical Conflict separation distance threshold, and two new BLUE cursors for the TCT Missed-Manoeuvre tactical controller lookahead time and separation thresholds. The TctCursorDisplayer notifies the modified lookahead and separation values to the TctConflictVisibiltyImpl which extends the basic ConflictVisibilty interface in the local CWP. In this way the PPD is provided with increased filtering capability for conflict alerts that appear in the HMI.

5.3.6.2 Cursors

The TCT PPD cursors (tct.graphics.ppd.cursors.*) are standard cursors with a modified colour.

5.3.6.3 Conflicts

The standard atcgraphics.eatmp.ppd.conflictdisplayer.DefaultConflictSymbolDisplayer which attaches Conflict Symbols to the PPD is extended by a tct.graphics.ppd.conflictdisplayer. TctPpdConflictSymbolDisplayer to attach (and prioritise) the TCT conflicts that are shown in the PPD. For any flight pair the PPD shows the first conflict in the following priority:

� State Vector Conflict

� Tactical Conflict

� MTCD Conflict

Note: Missed Manoeuvre Conflicts are not shown in the PPD.

5.3.6.4 TCT Scope

The atcgraphics.eatmp.ppd.scope.PpdScope interface in the CORE PPD is implemented by the tct.graphics.ppd.scope.TctPpdScope class which shows the TCT lookahead time and TCT separation standard as a dark grey rectangle in the PPD indicating the scope of conflicts produced by the TCT server. Note: The TCT lookahead time is the time within conflicts are being detected, and is not the same as the tactical lookahead time, which is the time within which the ATC Controller wishes to see an alert for the conflict in the HMI. The tactical lookahead time must less than or equal to the TCT lookahead time.

5.3.7 TctConflictVisibilty

The standard atc.mtcd.client.conflictvisibility.ConflictVisibility plugin interface is extended by the tct.tct.client.config.TctConflictVisibilty interface to add the TCT specific parameters which influence the visibility of conflicts in the HMI (as a function of time-to-conflict, minimum separation, risk, etc.). The TctConflictVisibilty interface is implemented by the tct.tct.client.config.TctConflictVisibiltyImpl.


04 Feb 2009

Page 25 of 28

6 TCT RECORDING

TCT introduces some minor updates to the STORIA recording classes in order to record TCT conflict data.

6.1 TCTMODULE

The tct.rec.TctModule extends the core eec_atc.storia.rec.server.modules.MtcdModule to register with the TCT server for the TCT conflicts then write them out with the standard MtcdModule methods. It also writes out changes to the risk of those conflicts, and any conflict destruction events.

6.2 TCTDATARECORDERIMPL

The tct.rec.TctDataRecorderImpl extends the core eec_atc.storia.rec.server.DataRecorderImpl to use the above TctModule.


04 Feb 2009

Page 26 of 28

7 STCD (SHORT TERM CONFLICT DETECTION)

7.1 OVERVIW

The STCD component was created for the TCT project; it was designed to be more efficient than the standard MTCD and more specialised for regular updates using a shorter lookahead. The STCD differs from the standard MTCD in the following ways:

1. When a trajectory is received by STCD it calculates a 3D zone of occupancy for the complete trajectory. During the conflict search process the zone is used to eliminate aircraft from the search whose regions do not overlap.

2. The conflict search is performed in a double pass: the first pass is a 2D search during which the risk is set to CONTEXTUAL; the second pass is a 3D search (using the standard vertical separation) along the trajectories of flights that were conflicting during the first pass. Conflicts found during the second pass have their risk elevated to CONFLICT, and their start and end updated to delimit the real conflict period. This is an improvement from the standard MTCD which implements a compromise of the double pass mechanism, consisting of a single 3D search using an extended vertical separation to catch CONFLICT and CONTEXTUAL aircraft in one pass. The result of this compromise is that only a limited number of CONTEXTUAL aircraft are found (those within the extended vertical separation), and a diminished accuracy for the CONFLICT since the start and end time correspond to the loss of the extended vertical separation.

3. Regular inspection of conflicts to see if the start time has entered within the tool's lookahead time is not done. This feature is redundant because the STCA assumes that trajectories are being regularly updated.

Note: The STCD server should not be confused with the STCA server which only works with aircraft track information and knows nothing about trajectories.

For more information on the MTCD component see the eDEP_GRD_DDD.

7.2 STCD SERVICE

The StcdService is a simplified ConflictService used by the MTCD.

public interface StcdService extends ComponentService { /** * Get the name of the attached Conflict detection server. * @return the name of the attached Conflict detection server, or null if none attached. */ String getAttachedServerName(); /** * Perform a what - if conflict probe for the given trajectory using the separation * settings given. * @param probeSettings the configuration settings for the probe * @param flight the flight for which a trajectory is being probed * @param traj the flight trajectory being probed * @param tag the trajecory tag * @param resultListener the listener that will receive the asynchronous result * (type = atc.mtcd.entity.ConflictList) */ void probeForConflicts (StcdProbeSettings probeSettings , Flight flight, Trajector y traj, String tag, EventListene r resultListener); /** * Register to receive the StcdUpdateEvent generated when the conflict information is * updated from * the STCD server's StcdUpdateMessage. * @param action the listener to be notified */ SubscriptionID registerForStcdUpdateEvent( Event Listener action ); }


04 Feb 2009

Page 27 of 28

The interface contains the following methods:

� getAttachedServerName() – get the name of the attached STCD server component

� probeForConflicts() – probe the given trajectory against the STCD's stored trajectories (with optional probe separation parameters)

� registerForStcdUpdateEvent() – register to receive updates to the STCD's conflicts

7.3 STCD SERVER

The STCD server is a simplified MTCD server. It provides conflict detection on one type (tag) of trajectory, has no updates due to the lookahead time advancing (since it is assumed the trajectory is regularly updated), and has none of the extra probing functions present in MTCD.

7.3.1 Class Diagram

Figure 7-1 STCD Controller Class Diagram

Figure 3-1 shows the main classes in the StcdController. Similarly to the MTCD it has a database (StcdDatabase) for the Entities used by the server, and a TrajectoryFactory for creating a Trajectory from a TrajectoryDescription passed in with a conflict probe request.

7.4 STCD FLIGHT CONFLICT ENTITY MANAGER

The StcdFlightConflictEntityManager is an extended FlightConflictEntityManager used in MTCD and is the EntityManager for the conflicts in the STCD server. The STCD version simply gives all the conflicts an ID of 0. Normally each new conflict is given a unique ID that is shown in the HMI as a reference between the ATC Controllers. For STCD this is not done because the server is aimed at trajectories that may be changing quickly (as an aircraft deviates) and it was felt that:

� it could not be guaranteed that the number wouldn't race off into high numbers when the system doesn't detect that a conflict is equivalent to one that already existed before

� it is known that the ATC Controllers don't actually have a conflict-centric view of problems but a route-centric view in which the callsigns are more important


04 Feb 2009

Page 28 of 28

� it conveniently helps distinguish between MTCD and STCD conflicts

7.5 OPERATION

The StcdFlightConflictProbe is a slight variation of the MTCD version, although it uses the same ConflictCalculator to detect conflicts between two trajectories. When a trajectory is updated:

� the SfplUpdateHandler updates 3D zone of occupancy of the trajectory

� the SfplUpdateHandler request the new ConflictList from the StcdFlightConflictProbe

� the StcdFlightConflictProbe performs a lateral conflict search between the given trajectory and all other trajectories that have an InterestZone that overlaps with it. Each conflict is given a risk level = Conflict.CONTEXTUAL.

� For each flight that had conflicts in the lateral search a 4D conflict search is performed. Any lateral conflict that is also a 4D conflict is upgraded to a Conflict.CONFLICT and the conflict start and end times updated to that of the 4D conflict.

� The list of CONTEXTUAL and CONFLICT conflicts is returned to the SfplUpdateHandler which uses an StcdAtcAuthorityMessageDistributor to send the relevant subset of the conflicts to each subscribed client (similar to the MTCD).

The process is the same when a request for a conflict probe is received except that it is not necessary to update the flights InterestZone.