This Service Interface exposes the set of operations related to Coordination and Transfer that are not necessarily required to achieve a usual/basic interoperability level.
Operations
Operation to cancel a previous assume of a flight.
Operation to transmit the intention of releasing the flight according to the provided data..
closePointOut is used in response to a pointOut notification for formally notifying the system that the notification has been processed by the receiver.
This remains a local action between the receiver and his/her system without any OLDI equivalent message.
The originator controller is capable of ending the point session, while the designated controller is capable only to remove his OEs from the recipient list (and if there is no more recipient, the point session is ended). The exception being that it is not possible to end a point session in another OLDI ATSU because OLDI considers the "point" as a one shot distribution..
The Point message is sent to controller(s) of the same ATSU or another ATSU to point out a flight in order to facilitate verbal coordination, irrespective of whether co-ordination has taken place.
This is a PNT msg equivalent.
The input of the point function shall contain the identification of the SFPL and the identification of one or several point target sector(s).
The use of a reason parameter written by the originator is only allowed for Point message sent to controller(s) of the same ATSU.
The main uses of the point function are:
- highlight: to support vocal exchanges during the co-ordination process. In such cases, the flight is designated by the giving position, and it is highlighted on the positions managing the pointed sector(s).
- manual distribution: to support the delivery of flight data to a chosen recipient:
- for information, if the recipient is not within the computed informed responsibility list (e.g. to check with an adjacent position the possibility to transfer the flight to it)
- to replace automatic distribution by manual distribution, when the system is degraded.
.
Operation to transfer the responsibility of a flight to a responsibility that is not in the list of the planned crossed responsibilities.
The input shall contain the identification of the SFPL and the name of the receiving responsibility (toSector)
.
Operation to propose the flight for hand-over to the accepting controller (unit) when required.
This is a HOP msg equivalent.
This operation is possible only if the accepting unit is another ATSU.
This operation is allowed only if no clearances request is on going (either no request has been received for the flight, or otherwise it has been answered).
The input shall contain one or more of the following transfer data: CFL, assigned heading, direct route clearance, assigned speed, assigned rate of Climb/Descent..
Operation to propose the flight for hand-over to the accepting controller (unit) when required.
This is a HOP msg equivalent.
This operation is possible only if the accepting unit is another ATSU.
This operation is allowed only if no clearances request is on going (either no request has been received for the flight, or otherwise it has been answered)..
Operation to indicate the manual acceptance by a unit of the transfer conditions previously sent (e.g. response to a propose hand over operation).
This is an ACP msg equivalent.
This operation can be a response either to a clearances request, or to a hand over proposal..
Operation from accepting unit to request some operational clearances from transferring unit.
This is a RTI msg equivalent.
This operation is allowed only if no hand over proposal is on going (either no proposal has been received for the flight, or otherwise it has been answered).
The input shall contain CFL, and optionally one or more of the following transfer data: CFL, assigned heading, direct route clearance, assigned speed, assigned rate of Climb/Descent..
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.