DSNA&ENAV
DSNA: the French air navigation service provider
ENAV; the Italian air navigation service provider
Provider Type
CIVIL_AIR_NAVIGATION_SERVICE_PROVIDER
Abstract
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. 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 Type
SWIM_CANDIDATE
Lifecycle Stage
PROSPECTIVE
Business Activity Type
INFORMATION_MANAGEMENT
Intended Consumer
CIVIL_AIR_NAVIGATION_SERVICE_PROVIDER
Information Exchange Category
FLIGHT_INFORMATION_EXCHANGE
Application Message Exchange Pattern
SYNCHRONOUS_REQUEST_REPLY
Aerodrome ICAO Location Indicator
No Information Provided
FIR ICAO Location Indicator
No Information Provided
State ICAO Nationality Letters
No Information Provided
In-Operation Date
No Information Provided
Provider
Support
No Information Provided
Point of Contact
Coflight Cloud Services Program Director - To request access to the CCS service
Email
Guillaume.Ramonet@aviation-civile.gouv.fr
Telephone
No Information Provided
- For Incidents on services in operation, contact the Service desk [working hours/opening days] as described in the related support service (incident management) supplied by CCS provider to CCS customer during the procurement phase
Email
No Information Provided
Telephone
No Information Provided
General
Operational Needs
Operational Need
CCS FlightDataManagement Service addresses the CWP manual interactions for managing Flight Plan updates related to inputs made by the controller or by the Flight Data Operator. It addresses operations related to:
- the System Flight Plan Data: Create, Cancel, Delete, Retrieve, Create Abbreviated and Non tactical modifications,
- to ATC Instructions: Holding, Heading, Speed, CFL, ROCD, EFL, XFL, DirectTo, ClearedTo, RFL and ECL,
- the correction of erroneous AFTN messages,
- WhatIf: Accept/Reject and Open/Close.
Note: in this version of the document, CCS FDM contains all the operations listed above except those related to WhatIf.
Functionality
Description
Process a Cleared Flight Level instruction
Real World Effect
The trajectory of the flight is updated accordingly.
Description
Process a Direct instruction
Real World Effect
The trajectory of the flight is updated with the direct clearance.
Description
Process an en-route cruise Flight Level instruction
Real World Effect
The trajectory of the flight is updated accordingly.
Description
Process an Entry Flight Level instruction
Real World Effect
The Exit Flight Level related to the concerned coordination is updated and the trajectory of the flight is updated.
Description
Process an Exit Flight Level instruction
Real World Effect
The Exit Flight Level related to the concerned coordination is updated and the trajectory of the flight is updated.
Description
Process a Heading instruction
Real World Effect
The trajectory of the flight is updated with the heading clearance.
Description
Process a Holding instruction (stretched objective)
Real World Effect
The trajectory of the flight is updated with the holding clearance.
Description
Process a modification of Route
Real World Effect
The route and the trajectory of the flight are updated with the route amendment.
Description
Process a Requested Flight Level instruction
Real World Effect
The trajectory of the flight is updated accordingly.
Description
Process an ROCD instruction
Real World Effect
The trajectory of the flight is updated with the ROCD clearance.
Access and Use
No Information Provided
Quality of Service
The service level objectives regarding the availability, response time, throughput and recoverability of CCS Services depend on the purpose (mission) for which the Customer intend to use them (e.g. integration, test, training, operational purpose).
These service level objectives are therefore negotiated with the Customers, based on their safety analysis, and are detailed in the specific Service Level Agreement established with each CCS Customer.
The minimum Bandwidth required to consume CCS services (hypothesis for the technical integration service of 300 simultaneous flight managed by the system) is 10MB/s.
Customer ATSU shall restrict the overall rate of requests to a maximum of 720 request/minutes. The detailed rate limitation per services is detailed in the associated swim service description of each service.
Concepts
Concepts
No Information Provided
Abbreviations
No Information Provided
Information
Information Definition
AIRM Conformant
Off
AIRM Version
No Information Provided
Airspeed value expressed in knot or in mach.
AIRM Conformant
Off
AIRM Version
No Information Provided
The name by which the route is known.
AIRM Conformant
Off
AIRM Version
No Information Provided
Boolean
AIRM Conformant
Off
AIRM Version
No Information Provided
The direction types:
- DOWNSTREAM: coordination data for a downstream transition.
- UPSTREAM: coordination data for an upstream transition.
AIRM Conformant
Off
AIRM Version
No Information Provided
Type to transmit the success code of an operation.
AIRM Conformant
Off
AIRM Version
No Information Provided
A code describing the release indications.
AIRM Conformant
Off
AIRM Version
No Information Provided
Code describing the different modes of surveillance.
- MODE_3A : The identification of an aircraft as reported by its SSR transponder. This 12-bits code is manually set by the pilot on request of ATC. This code is often called the 'squawk identification' and is usually represented as 4 octal digits (e.g. 0627). Special codes are reserved for emergency situations (7500 = hijack, 7600 = radio failure, 7700 = general emergency). (often abbreviated as: SSR code).
- MODE_A-C : The altitude of an aircraft as reported by its SSR transponder expressed in flight levels. Possible values are between FL 12 and FL 1267.
- MODE_S : An enhanced mode of SSR which permits the interrogation of SSR equipped aircraft and addressed interrogations with two way data exchange for suitably equipped aircraft
- INTERMODE : aircraft mode S equipped that can answer to mode A or mode C interrogations.
AIRM Conformant
Off
AIRM Version
No Information Provided
The value of the collection stamp.
AIRM Conformant
Off
AIRM Version
No Information Provided
Generic type to address comment/description/remark attributes within a medium length frame
AIRM Conformant
Off
AIRM Version
No Information Provided
Identification of a specific controller (originator of a request, served for SFPL distribution, target/originator of a PointSession...).
AIRM Conformant
Off
AIRM Version
No Information Provided
String to identify a controller.
AIRM Conformant
Off
AIRM Version
No Information Provided
Indicates the direction of the coordination proposal.
The CoordinationData of real SFPL are always from the entry to the exit sector.
AIRM Conformant
Off
AIRM Version
No Information Provided
Identifier of the error.
AIRM Conformant
Off
AIRM Version
No Information Provided
A string supporting the value of a parameter in an error description.
AIRM Conformant
Off
AIRM Version
No Information Provided
Flight Identifier
AIRM Conformant
Off
AIRM Version
No Information Provided
Type supporting a unique flight identifier that can be : an internal flight Id assigned by the FDPS, an IFPLIdentifier, an aircraftRegistration, a flightNumber...
AIRM Conformant
Off
AIRM Version
No Information Provided
The flight level to climb/descend to.
AIRM Conformant
Off
AIRM Version
No Information Provided
Geographical Point definition of a Significant Point.
AIRM Conformant
Off
AIRM Version
No Information Provided
Heading type angle in degrees.
AIRM Conformant
Off
AIRM Version
No Information Provided
A string of points (and connecting airways or DCTs where applicable) describing an ATS route or path of xes no more than 30 minutes ying time or 200nm apart, including those points where a change of speed, level, track, or flight rules is planned. Points can be listed by their coded designator (i.e. LN, MAY, HADDY), a 7 or 11-character representation of their coordinates (i.e. 46N078W, 4620N07805W), or a point relative to a reference point based on bearing and distance (i.e. DUB190040 being 40nm out on the 190 degree magnetic bearing from DUB). Change of speed and/or level is indicated by appending data formatted as in 15 CRUISING SPEED and LEVEL to a point, after a slash (i.e. MAY/N0305F180, 46N078W/M082F330). Change of flight rules are shown by a standalone VFR or IFR to indicate the beginning of that phase of flight.
AIRM Conformant
Off
AIRM Version
No Information Provided
Simple class providing an IAS value.
AIRM Conformant
Off
AIRM Version
No Information Provided
Simple class providing a mach value.
AIRM Conformant
Off
AIRM Version
No Information Provided
Other operational entity mapped on the originator working position.
Note: Even if the originator is a single controller, he may belong to a logical position composed of several operational entities (several Role/Responsibility couples).
AIRM Conformant
Off
AIRM Version
No Information Provided
Published Point definition of a Significant Point.
AIRM Conformant
Off
AIRM Version
No Information Provided
Rate of Climb or Decent, respectively + or -.
Expressed in Feet/Minute
AIRM Conformant
Off
AIRM Version
No Information Provided
Radial Point definition of a Significant Point.
AIRM Conformant
Off
AIRM Version
No Information Provided
The report related to the client request
AIRM Conformant
Off
AIRM Version
No Information Provided
String to identify a Responsibility.
AIRM Conformant
Off
AIRM Version
No Information Provided
A route element may be either an airway or (exclusive) a published point name.
Upstream or downstream truncation of an airway to be used is to be made in conjunction with a previous or next RouteElement providing the corresponding point name.
AIRM Conformant
Off
AIRM Version
No Information Provided
The number assigned to a particular multiple pulse reply signal transmitted by a transponder in Mode A or Mode C.
AIRM Conformant
Off
AIRM Version
No Information Provided
Mode A/S value of the transponder.
4-digit octal representation
AIRM Conformant
Off
AIRM Version
No Information Provided
The Area of Responsibility of a Unit is internally represented by a group of Sectors. They are the smallest entities that can be assigned to a controller or a group of controllers for ATM purposes.
A Sector could be first defined by a volume or other airspace element such as STAR, an airway or a group of airways and has a responsibility assigned for controlling purposes. The responsibility can depend on several criteria:
- Type of airspace controlled (ACC, APP,...)
- Type of traffic.
- Type of aircraft.
- etc.
Sectors shall be either ControlSectors or InformedSectors and are linked to the Unit they are partOf to support external coordination.
AIRM Conformant
Off
AIRM Version
No Information Provided
System reference number to identify the Sector by pointing to its position in the list of controlSector
AIRM Conformant
Off
AIRM Version
No Information Provided
A specified geographical location used in defining an ATS route or the flight path of an aircraft and for other navigation and ATS purposes.
A SignificantPoint can be defined as a PublishedPoint, a GeographicalPoint or a RadialPoint.
AIRM Conformant
Off
AIRM Version
No Information Provided
Name of a significant point.
Note: ICAO norm maximum length is 5 characters.
AIRM Conformant
Off
AIRM Version
No Information Provided
The version number of an item.
AIRM Conformant
Off
AIRM Version
No Information Provided
Number of seconds since the Unix epoch time - 00.00 hours - Jan, 1st, 1970 (UTC).
AIRM Conformant
Off
AIRM Version
No Information Provided
Number of seconds since beginning of current day (UTC)
AIRM Conformant
Off
AIRM Version
No Information Provided
Number of milliseconds since the Unix epoch time - 00.00 hours - Jan, 1st, 1970 (UTC).
AIRM Conformant
Off
AIRM Version
No Information Provided
WhatIf class is used in the FlightDataDistribution service to indicate if the published FlightData is a copy of the real flight used to negotiate potential changes without affecting the corresponding data of the actual flight.
The WhaIf is used in the following operations of CoordinationAndTransferManagement:
coordinationAccept, coordinationRejection, coordinationCounterProposal.
The WhaIf is used in the following probing operations of FlightDataManagement:
- requestProcessCFL
- requestProcessDirect
- requestProcessECL
- requestProcessEFL
- requestProcessHeading
- requestProcessHolding
- requestProcessRFL
- requestProcessROCD
- requestProcessRoute (CCS limitation)
- requestProcessXFL
AIRM Conformant
Off
AIRM Version
No Information Provided
Unique identifier of a what-if context in the CCS system.
AIRM Conformant
Off
AIRM Version
No Information Provided
Message definition of the operation corresponding to the same class name
AIRM Conformant
Off
AIRM Version
No Information Provided
Message definition of the operation corresponding to the same class name
Note: coordinationReference is a parameter common to all C&T operations, but which is not needed in the case of the assumeFlight operation, therefore its multiplicity is set to 0.
AIRM Conformant
Off
AIRM Version
No Information Provided
Message definition of the operation corresponding to the same class name
AIRM Conformant
Off
AIRM Version
No Information Provided
Generic definition of the CTM operations
Note: coordinationReference is a parameter common to all C&T operations, but which is not needed in the case of the assumeFlight and handover operations, therefore its multiplicity is set to 0.
AIRM Conformant
Off
AIRM Version
No Information Provided
Specialisation of the common RequestReport.
AIRM Conformant
Off
AIRM Version
No Information Provided
Data on the transition point between two sectors of the same ATC unit or from adjacent units.
Note: by default, the transition point is the entry point of the receiving sector (responsibility). The entry of an AoR is determined either by the entry of the control volume, a segment transition point (if the 2 sectors belong to different segments), or according to the pre-defined responsibility rules if more than one responsibility is determined from a control volume.
AIRM Conformant
Off
AIRM Version
No Information Provided
Message definition of the operation corresponding to the same class name.
AIRM Conformant
Off
AIRM Version
No Information Provided
Message definition of the operation corresponding to the same class name
AIRM Conformant
Off
AIRM Version
No Information Provided
Message definition of the operation corresponding to the same class name.
AIRM Conformant
Off
AIRM Version
No Information Provided
Message definition of the operation corresponding to the same class name
AIRM Conformant
Off
AIRM Version
No Information Provided
Message definition of the operation corresponding to the same class name.
AIRM Conformant
Off
AIRM Version
No Information Provided
Message definition of the operation corresponding to the same class name.
Note: - coordinationReference is a parameter common to all C&T operations, but which is not used by CCS for the handOver operation.
- no transferData can be sent via this operation, this is a Coflight limitation.
- toSector has to be filled only if the ATCO wants to perform a hand-over to a specific Sector instead of the next Sector. However, if the toSector attribute is filled, then it is mandatory to also fill the corresponding attribute toSectorTraversalId (only this identifier is really used by Coflight).
AIRM Conformant
Off
AIRM Version
No Information Provided
Directives issued by air traffic control for the purpose of requiring a pilot to take a specific action.
Only the clearedRoute parameter is applicable to the operation coordinationManualAgreement.
Data Structures
No Information Provided
Schema Language
Protocol buffer
Reference
CCS_coordinationAndTransferManagement.proto v3.0.1.1
No Information Provided
Schema Language
Protocol buffer
Reference
CCS_coordinationAndTransferManagement.proto v3.0.1.1
No Information Provided
Schema Language
Protocol buffer
Reference
CCS_coordinationAndTransferManagement.proto v3.0.1.1
No Information Provided
Schema Language
Protocol buffer
Reference
CCS_coordinationAndTransferManagement.proto v3.0.1.1
No Information Provided
Schema Language
Protocol buffer
Reference
CCS_coordinationAndTransferManagement.proto v3.0.1.1
No Information Provided
Schema Language
Protocol buffer
Reference
CCS_coordinationAndTransferManagement.proto v3.0.1.1
No Information Provided
Schema Language
Protocol buffer
Reference
CCS_coordinationAndTransferManagement.proto v3.0.1.1
No Information Provided
Schema Language
Protocol buffer
Reference
CCS_coordinationAndTransferManagement.proto v3.0.1.1
No Information Provided
Schema Language
Protocol buffer
Reference
CCS_coordinationAndTransferManagement.proto v3.0.1.1
Technical
Security Mechanism
Mutual authentication with X509 certificates is used between the AMQP broker and its client established within a TLS session
TLS 1.2 is used to provide confidentiality and integrity at transport layer.
IPsec is used to provide confidentiality, authentication and integrity at network (internet) layer
Technical Constraint
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.
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.
Concerning 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.
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.
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
Monitoring Description
CCS services are supervised in real time by trained and licensed ATSEPS
. A dedicated service to supervise the complete CCS swim services portfolio is available to the customer.
For more information, please refer to the swim service description of the CCS technical supervision distribution service
. A dedicated service to supervise the complete CCS swim services portfolio is available to the customer.
For more information, please refer to the swim service description of the CCS technical supervision distribution service
Interfaces
This Service Interface exposes the set of basic operations needed for Coordination and Transfer.
PROVIDER_SIDE_INTERFACE
SWIM_TI_YP_1_0_AMQP_MESSAGING
IPV4_SECURE_UNICAST
SYNCHRONOUS_REQUEST_RESPONSE
Operations
Operation to indicate the assume of the flight.
Operation to transmit the intention of releasing the flight according to the agreed transfer conditions.
Operation to accept a coordination data proposal previously sent
Operation to input a dialogue with a new coordination proposal.
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 transmit the intention of releasing the flight according to the provided data.
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 cancel a previous assume of a flight, for example when an unexpected ForceAssume has been performed.
This operation has been identified as stretched objective in the context of CCS Program. For this reason it has not implemented at Software level, despite it is defined at SSD and protobuf ones.
Endpoints
Address
For security reasons, the adresses will be communicated only to Customers
Description
No Information Provided
Interface Binding Description Overview
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 Binding Configurations
No Information Provided
Behaviour
The detailed behavior of the service is provided in each operation dedicated section
References
Service Documents
Service Description Document (SDD) from PJ.16-03 on which the CCS Service is based
Protobuf files describing the exchanged information
Complete service specification
Implemented Standards
No Information Provided
Revision Save Date
Wed, 07/01/2020 - 10:46
Revision Number
46211
The service description has currently reached the "PUBLISHED" status.