{ "informationServiceDescription": { "title": "CCS CoordinationAndTransferManagement", "referenceDate": "2022-06-13", "edition": "2.0.0", "serviceAbstract": "

This Service is part of Coflight Cloud Services (CCS), which are primarily designed to support the Virtual Centre concept. As such, these CCS Services support the interactions between the CCS ATM Data Service Provider (ADSP) and Virtual Centre Air Traffic Service Units (ATSUs). The CCS CoordinationAndTransferManagement service is consistent with the other CCS services. It addresses the CWP manual interactions for managing Coordination and Transfer operations, and is to be used for automatic coordination of standard conditions as well as for manual coordination of non-standard conditions. This version of the service is intended to be used in 'test mission', which aims at providing services and support to the Customer(s) to enable them to test any version of their ATM system during development. Note: Only civil flights are handled by CCS services. Please note that the use of CCS CoordinationAndTransferManagement service implies the use of CCS FlightDataDistribution Service to get the output coordination and transfer information, i.e.:

- Current status of coordination and transfer of flights between the crossed controller positions (AoR)

- On-going Change proposals for those coordination and transfer

 

Service retired from 20/03/2023

", "serviceIdentification": { "name": "CCS CoordinationAndTransferManagement", "version": "2.0.0" }, "serviceProvider": { "name": "DSNA&ENAV", "description": "

DSNA: the French air navigation service provider

ENAV; the Italian air navigation service provider

", "type": [ "CIVIL_AIR_NAVIGATION_SERVICE_PROVIDER" ] }, "serviceCategorisation": { "businessActivityType": [ "INFORMATION_MANAGEMENT" ], "intendedConsumer": [ "CIVIL_AIR_NAVIGATION_SERVICE_PROVIDER" ], "informationCategory": [ "FLIGHT_INFORMATION_EXCHANGE" ], "lifeCycle": [ { "lifeCycleStage": "RETIRED" } ] }, "generalDescription": { "operationalEnvironment": { "operationalNeeds": [ { "name": " 1 General operational need", "description": "CCS CoordinationAndTransferManagement Service addresses the CWP manual interactions for managing Coordination and Transfer operations, and is to be used for automatic coordination of standard conditions as well as for manual coordination of non-standard conditions.It provides a set of operations to support the Coordination and Transfer process between controller positions. It addresses operations such as:-ActivateCoordination,-AssumeFlight,-CoordinationProposal,-ForceAssume,-HandOver,-..." } ] }, "functionality": [ { "name": "Manually activate a coordination", "description": "Manually activate a coordination", "realWorldEffect": "To manually trigger the coordination before the automatic event" }, { "name": "Assume a flight", "description": "Assume a flight", "realWorldEffect": "The control of the flight is transferred to the controller assuming it." }, { "name": "Deassume a flight", "description": "Deassume a flight", "realWorldEffect": "To give back the control of the flight to the controller previously assuming the flight." }, { "name": "Force assume a flight", "description": "Force assume a flight", "realWorldEffect": "To force the transfer of the control of the flight to the controller assuming it (delegation or in advance)." }, { "name": "Force Hand over a flight", "description": "Force Hand over a flight", "realWorldEffect": "Transfer at the request of an upstream responsibility with a shortcut or towards a responsibility not crossed by the flight." }, { "name": "Hand over a flight", "description": "Hand over a flight", "realWorldEffect": "The downstream controller receiving the hand over input, is informed that the controller in charge of the flight intends to release it according to the agreed transfer conditions." }, { "name": "Initiate a dialogue with a new coordination proposal", "description": "Initiate a dialogue with a new coordination proposal", "realWorldEffect": "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." }, { "name": "Manually accept a coordination proposal (e.g. response to a proposal or a counter proposal)", "description": "Manually accept a coordination proposal (e.g. response to a proposal or a counter proposal)", "realWorldEffect": "The coordination status of the transition is set to ACCEPTED and the trajectory is updated taking into account the agreed coordination data (the corresponding whatIF flight is deleted from CCS)." }, { "name": "Manually reject a coordination proposal (e.g. response to a proposal or a counter proposal)", "description": "Manually reject a coordination proposal (e.g. response to a proposal or a counter proposal)", "realWorldEffect": "The coordination status of the transition is set to REJECTED (the corresponding whatIF flight is deleted from CCS)." }, { "name": "Input a verbal coordination with the downstream/upstream responsibility", "description": "Input a verbal coordination with the downstream/upstream responsibility", "realWorldEffect": "This service is used by either the upstream or the downstream controller, when the coordination agreement has to be done by phone.Once a verbal agreement has been performed, the controller must perform this operation to feed the system with a stable coordination state." }, { "name": "Point out a flight to another responsibility", "description": "Point out a flight to another responsibility", "realWorldEffect": "The Point message is sent to highlight (ou point out) a flight to another controller(s) within the same ATSU or in adjacent ATSU.This is a PNT msg equivalent." }, { "name": "End a PointOut notification", "description": "End a PointOut notification", "realWorldEffect": "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 expected output is the removal of the controller involvement in the FDD PointOut session, or the end of the PointOut session if no more controller involved." }, { "name": "Recall a transferred flight", "description": "Recall a transferred flight", "realWorldEffect": "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.Intra-centre operation: no OLDI msg equivalent." }, { "name": "Request the transfer of a flight", "description": "Request the transfer of a flight", "realWorldEffect": "Operation to force in advance the request of the transfer of the flight.This is a ROF msg equivalent." }, { "name": "Send a counter proposal after a coordination proposal", "description": "Send a counter proposal after a coordination proposal", "realWorldEffect": "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 msg, 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." }, { "name": "Delegate the responsibility of a flight", "description": "Delegate the responsibility of a flight", "realWorldEffect": "Operation to transfer the responsibility of a flight to a controller whose responsibilities are not part of the planned control sectors list." }, { "name": "Change the list of the planned control sectors", "description": "Change the list of the planned control sectors", "realWorldEffect": "Operation to discard the responsibilities of the originator LogicalCWP from the planned control sectors list.Once this is done, this operation allows undoing it." }, { "name": "Request clearances", "description": "Request clearances", "realWorldEffect": "Operation from accepting unit to request some operational clearances from transferring unit" }, { "name": "Send a Hand Over proposal", "description": "Send a Hand Over proposal", "realWorldEffect": "Operation to propose the flight for hand-over to the accepting controller (unit) when required." }, { "name": "Reject a transfer conditions proposal", "description": "Reject a transfer conditions proposal", "realWorldEffect": "Operation to indicate the manual rejection by a unit of the transfer conditions previously sent (response to a request clearances operation)." }, { "name": "Accept a transfer conditions proposal", "description": "Accept a transfer conditions proposal", "realWorldEffect": "Operation to indicate the manual acceptance by a unit of the transfer conditions previously sent (response to a hand over proposal or to a request clearances operation)." } ], "accessAndUseConditions": [ { "name": "Information ownership", "type": "LEGAL_CONSTRAINT", "description": "IPRIn accordance with their internal contractual rules on IPRs, DSNA, ENAV and skyguide retain exclusive ownership of the information contained in this document, which is to be deemed as foreground of the Coflight Cloud Services project (aiming at delivering remote flight data processing).Access to the ServiceThis service is provided to Service Consumers under a contractual basis signed between the CCS Service Provider and the Service Consumer." }, { "name": "Dependencies with other CCS Services", "type": "SERVICE_CONSUMPTION_CONSTRAINT", "description": "If the service consumer also consumes other CCS services, this Service shall be consumed simultaneously with the other CCS SWIM Services that are part of the contractual agreement between the service consumer and CCS service provider." }, { "name": "Alignment to SESAR Virtual Centre activity", "type": "SERVICE_POLICY", "description": "This service will be updated to be as much as possible in line with the Service Definition produced by SESAR Virtual Centre activities" }, { "name": "Service versioning", "type": "SERVICE_POLICY", "description": "Both the SWIM Service Description documents / Protobuf files and the CCS Services are versioned.The version assigned to SSDs and to Protobuf files is composed by four digits in the form x.y.z.w.New releases are numbered according to the following rule (compared to the previous version): -w increased by one: means that some content that could be ignored by the developers changed and the changes do not affect the protobuf files generation. For example, changes in the comments or in the descriptions of services, fields and data structures.-z increased by one: means that some content is changed by adding (but not changing or removing) some messages and/or data types. The generated protobuf files are expected to be an extension of the previous one and as result they are backward compatible.-y increased by one: means that the file is changed by changing or removing some operations. The generated protobuf files are not expected to be compatible with the previous one.-x increased by one: means that the file contains a new baseline. Major changes are expected to be present.The service version is composed by 3 digits a.b.c assigned according to the following rule:- a could be 0,1,2 depending on the status of the service with respect to the SWIM registration phase:0: before the service application (as candidate)1: if candidate2: if compliant- b Increments if major changes have been done with respect to the previous version (modify/remove). No backward compatibility.- c Increments if minor changes have been done with respect to the previous version (addition/description modified). Full backward compatibility." }, { "name": "KPIs monitoring", "type": "SERVICE_POLICY", "description": "Services management review are regularly organized with CCS customers to monitor the usability of the services and the KPI related to the quality of service described in the SLA." }, { "name": "Confidentiality and integrity", "type": "SECURITY_CONSTRAINT", "description": "The interface of CCS business services is accessible from outside DSNA premises through Internet using IPV4. An IPSEC link (IKE v1 or IKE v2) is used between CCS provider and CCS customer terminal network equipment." }, { "name": "Authentication and authorisation", "type": "SECURITY_CONSTRAINT", "description": "The CCS provider acts as a certificate authority to provide and validate X.509 certificates. Before service operation, a package including X509 certificate and private key, will be delivered to the customer using the PKCS#12 archive file format. Mutual authentication with X509 certificates is used between the AMQP broker and its client. Prior to any exchanges of AMQP Messages, the CCS customer shall establish with CCS Provider a TLS session using TLS 1.2 version. -CCS customer shall provide its certificates when establishing the connection. The certificates shall be valid (nor corrupted, nor revoked). The certificates of the CCS customer allow its identification for the use of the different CCS services (CCS business services at lower level).-The CCS provider transmit its complete certificate during the connection phase and allow OCSP stapling to allow the CCS customer to check if it is valid or not.-For the cryptographic algorithms, the authorized cipher suites must be agreed between the CCS provider and the customer based on the standards.As an ATSU, the CCS business services customer, once identified, has access to all CCS services.In the case of a Customer that would fail to authenticate 3 times in less than 3 minutes, the IP address would be ban and has to trigger the incident management procedure." } ], "dateInOperation": "2020-07-01", "abbreviations": [ { "name": "ABI", "description": "Advanced Boundary Message" }, { "name": "AC", "description": "Airspace Configuration" }, { "name": "ACC", "description": "Area Control Centre" }, { "name": "ACP", "description": "Accept Message" }, { "name": "ACT", "description": "Activate Message" }, { "name": "ADSP", "description": "ATM Data Service Provider" }, { "name": "AFTN", "description": "Aeronautical Fixed Telecommunication Network" }, { "name": "AIRM", "description": "ATM Information Reference Model" }, { "name": "AMQP", "description": "Advanced Message Queuing Protocol" }, { "name": "ANSP", "description": "Air Navigation Service Provider" }, { "name": "APL", "description": "Abbreviated Flight Plan" }, { "name": "APP", "description": "Approach" }, { "name": "ATC", "description": "Air Traffic Control" }, { "name": "ATCO", "description": "Air Traffic Control Officer" }, { "name": "ATCS", "description": "Air Traffic Control Services" }, { "name": "ATM", "description": "Air Traffic Management" }, { "name": "ATS", "description": "Air Traffic Services" }, { "name": "ATSU", "description": "Air Traffic Service Unit" }, { "name": "AoR", "description": "Area of Responsibility" }, { "name": "CCS", "description": "Coflight Cloud Services" }, { "name": "CDN", "description": "Coordination Message" }, { "name": "CFL", "description": "Cleared Flight Level" }, { "name": "COF", "description": "Change of Frequency Message" }, { "name": "COP", "description": "Coordination Point" }, { "name": "CTM", "description": "Coordination and Transfer Management" }, { "name": "CWP", "description": "Controller Working Position" }, { "name": "DSNA", "description": "Direction des Services de la Navigation A0xC3 0xA9rienne (French ANSP)" }, { "name": "EFL", "description": "Entry Flight Level" }, { "name": "ENAV", "description": "Ente Nazionale Assistenza al Volo (Italian ANSP)" }, { "name": "ETN", "description": "Estimated Time of Entry" }, { "name": "ETX", "description": "Estimated Time of Exit" }, { "name": "FABEC", "description": "Functional Airspace Block Europe Central" }, { "name": "FDD", "description": "Flight Data Distribution" }, { "name": "FDM", "description": "Flight Data Management" }, { "name": "FDO", "description": "Flight Data Operator" }, { "name": "FDPS", "description": "Flight Data Processing System" }, { "name": "FL", "description": "Flight Level" }, { "name": "FP", "description": "Flight Plan" }, { "name": "HMI", "description": "human machine Interface" }, { "name": "IAS", "description": "Indicated Airspeed" }, { "name": "ICAO", "description": "International Civil Aviation Organization" }, { "name": "ID", "description": "Identifier" }, { "name": "IER", "description": "Interface Exchange Requirement" }, { "name": "IFR", "description": "Instrument Flight Rules" }, { "name": "IKE", "description": "Internet Key Exchange" }, { "name": "IP", "description": "Internet Protocol" }, { "name": "IPSEC", "description": "Internet Protocol Security protocol" }, { "name": "JU", "description": "Joint Undertaking" }, { "name": "KPI", "description": "Key Performance Indicator" }, { "name": "MAS", "description": "Manual Assumption of Communications Message" }, { "name": "MB", "description": "MegaByte" }, { "name": "MEP", "description": "Message Exchange Pattern" }, { "name": "NTP", "description": "Network Time Protocol" }, { "name": "OCSP", "description": "Online Certificate Status Protocol" }, { "name": "OE", "description": "Operational Entity" }, { "name": "OLDI", "description": "On-line Data Interchange" }, { "name": "OPSUP", "description": "Operational Supervision" }, { "name": "PAC", "description": "Preliminary Activate Message" }, { "name": "PKCS", "description": "Public Key Cryptography Standards" }, { "name": "RAP", "description": "Referred Activate Proposal Message" }, { "name": "RJC", "description": "Reject Message" }, { "name": "ROCD", "description": "Rate of Climb Descend" }, { "name": "RRV", "description": "Referred Revision Proposal Message" }, { "name": "SDD", "description": "Service Definition Document" }, { "name": "SESAR", "description": "Single European Sky Air Traffic Management Research" }, { "name": "SFPL", "description": "System Flight Plan" }, { "name": "SLA", "description": "Service Level Agreement" }, { "name": "SSD", "description": "SWIM Service Description" }, { "name": "SSI", "description": "Synchronous Serial Interface" }, { "name": "SSR", "description": "Secondary Surveillance Radar" }, { "name": "SWIM", "description": "System Wide Information Management" }, { "name": "TBC", "description": "To Be Confirmed" }, { "name": "TCP", "description": "Transfer Control Protocol" }, { "name": "TI", "description": "Technical Infrastructure" }, { "name": "TLS", "description": "Transport Level Security" }, { "name": "UTC", "description": "Coordinated Universal Time" }, { "name": "VC", "description": "Virtual Centre" }, { "name": "VFR", "description": "Visual Flight Rules" }, { "name": "XFL", "description": "Exit Flight Level" } ] }, "informationDescription": { "informationDefinition": [ { "name": "Service Information Definition", "definition": "", "airmCorrespondence": "" } ] }, "technicalDescription": { "technicalConstraint": [ { "name": "Time synchronisation", "description": "CCS provider and CCS customer use the date and time for the operation of each service and they must be able to date the traces and the information passed to the SSI log collector. NTP is the standard solution to synchronize time accurately. So, CCS Provider and CCS Customer should use, each of them, at least one NTP server (stratum N), integrated in a NTP network containing a stratum 0 reference time clock." }, { "name": "Provider-Customer interface-Exchange patterns", "description": "Each services interface of the CCS business services relies on the concept of AMQP queues and topics. -The CCS customer shall use an implementation of the AMQP 1.0 specification to connect to the CCS provider AMQP 1.0 endpoint. -The CCS provider endpoint is an AMQP 1.0 broker managing queue and topics. The message payloads are encoded following a protobuf format. The message exchange patterns used by the CCS services are request/reply and publish/subscribe. The CCS customer acts as requester and subscriber. The CCS provider acts as responder and publisher.Concerning publish-subscribe, the CCS customer subscribes to a CCS distribution service by directly listening to an appropriate AMQP topic, which name follows the CCS derivation rules.The subscription to CCS Distribution Services is not performed via subscription operations, but by connecting to the appropriate AMQP Topic described in the .protobuf files as topic://..The subscribers can filter the messages they want to receive by using the filter parameters defined for each subscription operation.Please note that, after subscribing to a CCS Distribution Service, the current repository of messages needs to be obtained from CCS via the get operation defined for each CCS Distribution Service (see \"Subscription\" section of the distribution operation of the service).N.B:- If the CCS platform restarts while the Customer is connected to the AMQP Broker, the current repository of messages is published again.- The acknowledgement that a Customer receives to his request (\"RequestReport\") may be received after the data distribution that this request has triggered, as these two messages are managed asynchronously by AMQP Queues and TopicsConcerning request-reply the CCS customer sends a request by sending a message to an appropriate AMQP queue, which name follows the CCS derivation rules, to make a request. The request message contains the name of the queue into the CCS customer listens and in which the reply from the CCS provider is expected." }, { "name": "Provider-Customer interface-Connection management", "description": "The Customer is the one that initiates the TCP connection and in case of a Network / Connection failure, it is the responsibility of the CCS customer to try to reconnect regularly." }, { "name": "Provider-Customer interface-Queue management", "description": "The AMQP broker creates the physical resources associated with a destination (queue, topic) on demand when messages are actually sent to them.Permissions on queues and topics (read/write access) are granted based on intended usage. The CCS customer will have: -Write access on the request queue-Read access on the reply queue -Read access on the topic for distribution service" } ] }, "references": { "serviceDocument": [ { "documentType": "AIRM_TRACE", "title": "CCS AIRM mapping CTM service", "version": "1.0", "description": "AIRM traceability for CCS Coordination And Transfer Management service payload" }, { "documentType": "SERVICE_VALIDATION_REPORT", "title": "CCS Validation evidence document - CoordinationAndTransferManagement", "version": "1.0", "description": "Validation evidence for CCS Coordination And Transfer Management service" }, { "documentType": "MACHINE_READABLE_SERVICE_DESCRIPTION", "title": "CCS_coordinationAndTransferManagement.proto", "version": "5.0.0.5", "description": "Protobuf files describing the exchanged information" }, { "documentType": "MACHINE_READABLE_SERVICE_DESCRIPTION", "title": "CCS_common.proto", "version": "5.5.1.2", "description": "Protobuf file describing the exchanged information common to two or more CCS Services" }, { "documentType": "MACHINE_READABLE_SERVICE_DESCRIPTION", "title": "metadata.proto", "version": "v1.2.0.0", "description": "Protobuf file describing the metadata used by the CCS Services" }, { "documentType": "SERVICE_SPECIFICATION", "title": "CCS CoordinationAndTransferManagement Service Description", "version": "5.2.0.9", "description": "Complete service specification" }, { "documentType": "SERVICE_SPECIFICATION", "title": "CCS Errors Management Document", "version": "2.0", "description": "Document that includes the list of all applicable error messages for CCS services" } ], "implementedStandard": [ { "title": "EUROCONTROL Specification for SWIM - Service Description ", "version": "2.0", "description": "This specification contains requirements for describing information services in the context ofInitial System Wide Information Management (iSWIM). The requirements prescribe the minimum set of elements a service descriptionhas to contain", "standardType": "EUROCONTROL_SPECIFICATION_FOR_SWIM_SERVICE_DESCRIPTION", "conformanceStatement": "Description of Service according to EUROCONTROL specifications" }, { "title": "EUROCONTROL Specification for SWIM - Information Definition", "version": "1.0", "description": "This specification contains requirements forinformation definitions, meaning the formal descriptions of exchanged information, in the context of Initial System Wide Information Management (iSWIM). This contributes to semantic interoperability of information. ", "standardType": "EUROCONTROL_SPECIFICATION_FOR_SWIM_INFORMATION_DEFINITION", "conformanceStatement": "Information definition according to EUROCONTROL specifications" }, { "title": "EUROCONTROL Specification for SWIM - Technical Infrastructure (TI) Yellow Profile", "version": "1.0", "description": "This specification contains requirements for system interfaces (e.g. protocols) and for IT infrastructure capabilities required to enable a reliable, secure and efficient exchange of information in the context of Initial System Wide Information Management (iSWIM).This contributes to technical interoperability", "standardType": "EUROCONTROL_SPECIFICATION_FOR_SWIM_TECHNICAL_INFRASTRUCTURE", "conformanceStatement": "Implementation of service and network bindings" } ] }, "serviceInterface": [ { "name": "AdvancedCoordinationAndTransferManagementProvider", "description": "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.", "provisionSide": "PROVIDER_SIDE", "operations": [ { "name": "deassumeFlight", "description": "Operation to cancel a previous assume of a flight. ", "messages": [ { "name": "DeassumeFlight", "direction": "IN" }, { "name": "CoordinationAndTransferResponse", "direction": "OUT" } ] }, { "name": "forceHandOver", "description": "Operation to transmit the intention of releasing the flight according to the provided data.. ", "messages": [ { "name": "ForceHandOver", "direction": "IN" }, { "name": "CoordinationAndTransferResponse ", "direction": "OUT" } ] }, { "name": "closePointOut", "description": "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.. ", "messages": [ { "name": "ClosePointOut", "direction": "IN" }, { "name": "CoordinationAndTransferResponse ", "direction": "OUT" } ] }, { "name": "pointOut", "description": "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.. ", "messages": [ { "name": "PointOut", "direction": "IN" }, { "name": "CoordinationAndTransferResponse ", "direction": "OUT" } ] }, { "name": "delegate", "description": "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). ", "messages": [ { "name": "Delegate", "direction": "IN" }, { "name": "CoordinationAndTransferResponse ", "direction": "OUT" } ] }, { "name": "handOverProposal", "description": "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.. ", "messages": [ { "name": "HandOverProposal", "direction": "IN" }, { "name": "CoordinationAndTransferResponse ", "direction": "OUT" } ] }, { "name": "handOverRejection", "description": "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).. ", "messages": [ { "name": "HandOverRejection", "direction": "IN" }, { "name": "CoordinationAndTransferResponse ", "direction": "OUT" } ] }, { "name": "transferAcceptation", "description": "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.. ", "messages": [ { "name": "TransferAcceptation", "direction": "IN" }, { "name": "CoordinationAndTransferResponse ", "direction": "OUT" } ] }, { "name": "clearancesRequest", "description": "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.. ", "messages": [ { "name": "ClearancesRequest", "direction": "IN" }, { "name": "CoordinationAndTransferResponse ", "direction": "OUT" } ] } ], "endpoints": [ { "name": "AdvancedCoordinationAndTransferManagementProvider", "url": "For security reasons, the addresses will be communicated only to Customers" } ], "messageExchangePattern": "SYNCHRONOUS_REQUEST_RESPONSE" }, { "name": "CoordinationAndTransferManagementProvider", "description": "This Service Interface exposes the set of basic operations needed for Coordination and Transfer.", "provisionSide": "PROVIDER_SIDE", "operations": [ { "name": "assumeFlight", "description": "Operation to indicate the assume of the flight.. ", "messages": [ { "name": "AssumeFlight", "direction": "IN" }, { "name": "CoordinationAndTransferResponse ", "direction": "OUT" } ] }, { "name": "handOver", "description": "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).. ", "messages": [ { "name": "HandOver", "direction": "IN" }, { "name": "CoordinationAndTransferResponse ", "direction": "OUT" } ] }, { "name": "coordinationAccept", "description": "Operation to accept a coordination data proposal previously sent . ", "messages": [ { "name": "CoordinationAccept", "direction": "IN" }, { "name": "CoordinationAndTransferResponse ", "direction": "OUT" } ] }, { "name": "coordinationProposal", "description": "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.. ", "messages": [ { "name": "CoordinationProposal", "direction": "IN" }, { "name": "CoordinationAndTransferResponse ", "direction": "OUT" } ] }, { "name": "coordinationRejection", "description": "Operation to reject a coordination data proposal previously sent. ", "messages": [ { "name": "CoordinationRejection", "direction": "IN" }, { "name": "CoordinationAndTransferResponse ", "direction": "OUT" } ] }, { "name": "activateCoordination", "description": "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.. ", "messages": [ { "name": "ActivateCoordination", "direction": "IN" }, { "name": "CoordinationAndTransferResponse ", "direction": "OUT" } ] }, { "name": "forceAssume", "description": "Operation to indicate the assume of the flight when the protocol cannot be followed. . ", "messages": [ { "name": "ForceAssume", "direction": "IN" }, { "name": "CoordinationAndTransferResponse ", "direction": "OUT" } ] }, { "name": "coordinationManualAgreement", "description": "Operation to input a verbal coordination dialogue in inter-centre.. ", "messages": [ { "name": "CoordinationManualAgreement", "direction": "IN" }, { "name": "CoordinationAndTransferResponse ", "direction": "OUT" } ] }, { "name": "handOverRecall", "description": "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.. ", "messages": [ { "name": "HandOverRecall", "direction": "IN" }, { "name": "CoordinationAndTransferResponse ", "direction": "OUT" } ] }, { "name": "handOverRequest", "description": "Operation performed by the accepting unit to the transferring unit, when required, to request the transfer of the flightThis 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.. ", "messages": [ { "name": "HandOverRequest", "direction": "IN" }, { "name": "CoordinationAndTransferResponse ", "direction": "OUT" } ] }, { "name": "coordinationCounterProposal", "description": "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.. ", "messages": [ { "name": "CoordinationCounterProposal", "direction": "IN" }, { "name": "CoordinationAndTransferResponse ", "direction": "OUT" } ] }, { "name": "replaceSectors", "description": "Operation to discard (eq. skip) all the responsibilities* of the originator LogicalCWP from the control sectors list of an SFPL (ex. {A,B,C,D} is replaced by {A,D}, if B and C are the responsibilities of the originator LogicalCWP).*: the responsibilities of the relevant internal segment. The request shall contain the responsibility to skip in the ControlSector list (respTraversalId).The skipped LogicalCWP traversal is no more taken into account (from a frequency point of view); the upstream LogicalCWP transfers the flight directly to the downstream LogicalCWP.The skip processing does not impact the application of constraints and the trajectory prediction.. ", "messages": [ { "name": "ReplaceSectors", "direction": "IN" }, { "name": "CoordinationAndTransferResponse ", "direction": "OUT" } ] } ], "endpoints": [ { "name": "CoordinationAndTransferManagementProvider", "url": "For security reasons, the addresses will be communicated only to Customers" } ], "messageExchangePattern": "SYNCHRONOUS_REQUEST_RESPONSE" } ] } }