SWIM_TI_YP_1_0_AMQP_MESSAGING

Allows a consumer to get the erroneous AFTN messages referred to FDO for manual correction, either for a specific erroneous message by filling the messageId, or all the erroneous messages if the messageId attribute is empty.

Refer to publishErroneousAFTNMessageData description for more details about the list of errors that can be enc.

This operation allows a generic client (eq. Air Server system) to inform that an aircraft has made a Datalink logon and to associate the corresponding logon parameters with an SFPL..

Operation to indicate the assume of the flight..

Operation to transmit the intention of releasing the flight according to the agreed transfer conditions.
Depending on the LoAs: e.g. expecting a further AssumeFlight operation or just waiting for a radio contact to release the flight.
This is an OLDI COF (Change Of Frequency) message equivalent.

This operation also offers the possibility to hand over the flight to another crossed responsibility than the expected one (eq. shortcut forceHandOver input). In that case, it is expected to provide explicitly the new responsibility traversal to which the transfer is performed, as well as the identifier of this responsibility (available in the SFPL ControlSector list).
This operation also offers the possibility to hand over the flight to a responsibility not in the list of crossed (eq. delegate input)..

Operation to accept a coordination data proposal previously sent .

Operation to input a dialogue with a new coordination proposal.
This service is to be used by either the upstream or the downstream controller.
When the proposal is initiated by the downstream, this is an OLDI CDN message equivalent. When the proposal is initiated by the upstream, this is mainly an OLDI RRV equivalent.
When the proposal is initiated by the upstream, it may be a RAP message equivalent if the downstream is not yet NEAR_PLANNING and if RAP transmission is off-line authorised. Else it may be an RRV message equivalent if the downstream is at least NEAR_PLANNING.
The input shall contain the identification of the SFPL, the receiving responsibility, the coordinationReference value (downstream or upstream proposal) and at least one of the following proposed coordination data:
- in case of downstream proposal: Transfer Flight Level, Route (including direct to a new point), Next SSR code, COP, Time on transition point.
- in case of upstream proposal: the Transfer Flight Level or the Route (including direct to a new point).

In both cases, the proposal input can also contain a Supplementary Flight Level, the boundary point type and, only when sent to another sector of the same ATSU, the following tactical instructions: Heading, Speed, ROCD and CFL (the application point of tactical instructions in coordinationProposal is considered IMMEDIATE).

The controller of the consulted responsibility receives a whatIF flight with the proposed coordination data and the coordination status of the transition is set to PROPOSED..

Operation to reject a coordination data proposal previously sent.

Operation to force in advance (prior to the automatic coordination event) the triggering of the coordination event for a given transition between two responsibility traversals by sending specific flight details..

Operation to indicate the assume of the flight when the protocol cannot be followed. .

Operation to input a verbal coordination dialogue in inter-centre..

Operation to indicate that the upstream controller requests to recover the flight control after a handOver operation.
The flight is then expected to get back into the previous state. However, for the receiving responsibility, there may be some exceptions (when the flight is a re-entering flight which was HANDED_OVER or RELEASED, or when it is a stolen flight which was DEASSUMED).
This operation being only for intra-centre operation, there is no OLDI message equivalent.
.

Operation performed by the accepting unit to the transferring unit, when required, to request the transfer of the flight
This is a ROF msg equivalent.
It may be used:
- in reply to a handOverProposal (HOP) to signify the acceptance of the flight under the proposed conditions,
- or to request the early transfer of the flight.
.

Operation to forward a counter proposal from the accepting unit to the transferring one or vice versa during the coordination phase.
This is basically replicating the CDN message, but the application context is extended beyond the OLDI scope in order to possibly support counter proposal from transferring to accepting when sent to another sector of the same ATSU.
Counter-proposal input is accepted only if no counter-proposal has been issued before.
The input shall contain the identification of the SFPL, of downstream the responsibility of the transition on which the coordination dialogue was initiated and at least one of the following proposed coordination data: Transfer Flight Level, Route (including direct to a new point), Next SSR code, COP, Time on transition point..