ATCCommandsManagementProvider

This Service Interface encompasses the different operations performed by the ATCO and modifying the Flight Plan Data. These operations can be divided in two sets of operations: the tactical instructions and the system inputs performed to modify the planed route:
- ATC tactical Instructions: Holding, Heading, Speed, Cleared Flight Level (CFL),Rate Of climb/Descend (ROCD), Direct To and Cleared To,
- System inputs: entry FL (EFL), exit FL (XFL), enCruiseFL (ECL) and requested Flight Level (RFL).

Operations

Operation to process the input of a Cleared Flight Level given the flight identifier and the value of the level to be applied.
The input may contain applicationStart data that can be a route point, distance before/after a route point or after current position..

Operation to process the input of a direct instruction given the flight identifier and the target point of the direct (not overflown point already belonging to the route).
The input may contain application data that can be a route point, distance before/after a route point or after current position..

Operation to process the input of a heading clearance.
It allows to assign either:
- an absolute heading. To do this:
- routePointId should not be filled
- continueHeading should be either not filled or set to FALSE
- either assignedHeading or application end point shoud be filled. If filled, the application end point should be expressed in the geographical point type
- a relative heading. To do this:
- routePointId should not be filled
- continueHeading should be either not filled or set to FALSE
- directionOfTurn and assignedHeading shoud be filled
- a maintain order. To do this:
- routePointId should not be filled
- continueHeading should be set to TRUE
- a resume own navigation order. To do this, routePointId should be filled..

Operation to process the modification of a route portion for a specified flight.
The input shall contain:
- the flight identifier,
- the new portion of route.
The input may contain either an application end point (routePoint not overflown used to rejoin the old route) or a new destination aerodrome.
The input may also contain application start data that can be a route point, distance after/before a route point, distance after current position.
.

Operation to process the input of the Entry Flight Level used for coordination between two logical positions.

Operation to process the input of the Exit Flight Level used for coordination between two logical positions.

Operation to process the input of an En-Route cruise level (ATC planning constraint) given the flight identifier and the value of the level to be applied.

Operation to process the input of a Requested Flight Level given the flight identifier and the value of the level to be applied.

Operation to process the input of an ROCD (Rate Of Climb or Descent) instruction..

Operation to process the input of a holding clearance a holding exit clearance or a holding cancellation clearance.
The input shall contain the flight identifier.
.

Behaviour
Interface Binding Description

Information is exchanged in Protobuf format. Protocol buffers or Protobuf are Google's language-neutral, platform-neutral, extensible mechanism for serializing structured data similar to XML, but smaller, faster, and simpler.

Interface Provision Side
TI Primitive Message Exchange Pattern
Service Interface Binding
Network Interface Binding