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 OperationalConfigurationManagement service is consistent with the other CCS services.
It allows the ACC/Approach operational supervisor to manage the operational configuration in the ATSU by processing his input on the following on-line data:
- the mapping of control roles and responsibilities (control volume, ADES, set of runways,...) to Control Working Positions
- Airspace status management (ARES/CDR activation...)
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 OperationalConfigurationManagement Service implies the use of CCS OperationalConfigurationDistribution Service for sector mappings and of CCS AirspaceStatusDistribution Service for ARES/CDR.
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
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
General
Operational Needs
Operational Need
CCS OperationalConfigurationManagement Service allows the ACC/Approach operational supervisor to manage the operational configuration in the ATSU by processing his input on the following on-line data:
- the mapping of control roles and responsibilities (control volume, ADES, set of runways,...) to Control Working Positions
- Airspace status management (ARES/CDR activation...)
Functionality
Description
Update sector mapping
Real World Effect
Change the operational configuration of the ATSU
Description
Activate sector mapping
Real World Effect
Change the current operational configuration of the ATSU (using a next or an off-line pre-defined sector mapping)
Description
Update ARES activation status
Real World Effect
Change and lock the activation status of the ARES
Description
Unlock ARES activation status
Real World Effect
Unlock a previous manual ARES activation status: the activation status of the ARES is unlocked and automatically updated by the system from ARES timesheets, information off-line defined and information issued from the CFMU.
Description
Update CDR activation status
Real World Effect
Change and lock the status of the CDR to open or closed.
Description
Unlock CDR activation status
Real World Effect
Unlock a previous manual CDR status: the status of the CDR is unlocked and automatically updated by the system from CDR timesheets, information off-line defined and information issued from the CFMU.
Access and Use
In accordance with their internal contractual rules on IPRs, DSNA, ENAV and Skyguide retain exclusive ownership of the information contained in this document and which is to be deemed as foreground of the Coflight Cloud Services project (aiming at delivering remote flight data processing).
This Service shall be consumed simultaneously with the other CCS SWIM Services
This service will be updated to be as much as possible in line with the Service Definition produced by SESAR Virtual Centre activities
As a consistent whole, the package of CCS swim services available is versioned. And each swim services is although versioned.
At least 2 versions of swim services could be maintained in the same time, taking benefit the capacities of technologies used in CCS such as protobuf.
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.
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.
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 AQMP 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.
Quality of Service
No Information Provided
Validation
Prior to any Service publication in the European Swim Registry, CCS partners organise a joint validation that involve both CCS Providers and the 1st CCS Customer.
Test Cases dealing with several test topics are run using a happy flow of few flights to check that the services are consistent, compliant with the actual service description and meet the acceptance criteria formulated by the 1st CCS Customer.
Regarding the CCS Operational Configuration Management Service, 3 different test cases have been performed, covering the following tests topics, using also Distribution Services to check the consistent behaviour of all services.
Initialise sectorisation, Activate Predefined Mapping and Publish Sector Configuration
- Retrieve initial sector configuration for Zurich & Geneva when OPSUP tool is started after the Provider systems
- Activate Predefined Sector Mapping in Zurich & Geneva
- Corresponding Sector Configuration distribution
- Impacts on FlightData distribution
Initialise sectorisation, Modify Current Mapping and Publish Sector Configuration & Flight Plans
- Retrieve initial sector configuration for Zurich & Geneva when OPSUP tool is started before the Provider systems
- Modify Current Sector Mapping in Zurich & Geneva:
=> move a part of the responsibilities to another LCWP on Geneva
=> move all the responsibilities to another CWP on Zurich
- Corresponding Sector Configuration distribution
- Impacts on FlightData distribution
CDR
- Retrieve the applicable CDR set in the dataset
- Close of the CDR-28A
- Unlock the TS200E
Concepts
Concepts
No Information Provided
Abbreviations
No Information Provided
Information
Information Definition
AIRM Conformant
Off
AIRM Version
No Information Provided
Enables to activate a sector mapping: the supervisor selects a mapping (next or pre-defined mapping) that will replace the current mapping of the concerned ASTUSectorConfiguration.
The supervisor may also choose to revert back to the pre-defined default sector mapping. If not, the input parameters shall be the identifier and the state (next or pre-defined) of the origin sector mapping.
If the request is successful, the new current mapping is published using the SectorConfigurationSubscriber Service Interface in order to be displayed in the Controller and Operational Supervisor HMIs.
When applying a new current mapping, loaded from the next mapping, then the next mapping becomes current and the former "current" mapping is deleted.
Note:The cardinality of the parameter sectorMappingId is optional, because the operation "ActivateSectorMapping" covers also the case of reverting back to default mapping. Indeed, when the parameter revertToDefaultMapping is not filled or set to FALSE, then sectorMappingId is mandatory. If the supervisor chooses to revert back to the default mapping, this field is unused.
AIRM Conformant
Off
AIRM Version
No Information Provided
The airspace (ARES or CDR) designator.
AIRM Conformant
Off
AIRM Version
No Information Provided
The name of the ARES/CDR.
Note: the CDR name used for the identification of the CDR is limited to 7 characters in CCS; this is the name of the CDR airway.
AIRM Conformant
Off
AIRM Version
No Information Provided
The full textual designator of the airway area of the CDR.
Geographical area designator to be associated to an airway name to make a unique ID of the airway.
AIRM Conformant
Off
AIRM Version
No Information Provided
Boolean
AIRM Conformant
Off
AIRM Version
No Information Provided
The CDR identification: CDR name and optionally the start and last points of the CDR.
AIRM Conformant
Off
AIRM Version
No Information Provided
Status of the ARES activation:
- ACTIVE: the ARES is active.
- INACTIVE: the ARES is inactive.
AIRM Conformant
Off
AIRM Version
No Information Provided
The CDR status:
- CLOSED: the CDR is closed.
- OPEN: the CDR is open.
AIRM Conformant
Off
AIRM Version
No Information Provided
Indicates the type of instance used to activate this sector mapping. The original mapping is either an off-line predefined mapping or a next mapping
AIRM Conformant
Off
AIRM Version
No Information Provided
This data type may be used to distinguish the instance of sectorConfiguration, that can be the Current or the Next ones.
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
It is used to indicate the role concerned. The role represents the various ATM operation functions in an ATSU
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
Generic type to address comment/description/remark attributes within a short 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
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
A Logical CWP is used to define a set of control Responsibilities (e.g. control sectors "S1", "S2", "S3") to be managed by a role (e.g. "Tactical") on a controller working position.
A logical CWP may have no associated role/responsibility, but when it is operationally used, it is always defined by a list of Responsibilities (e.g. control sectors, set of STARs...) and an associated role ("Tactical", "Planner"...).
A Responsibility cannot be mapped to more than one Logical CWP for the same role.
Off-line defined parameters identify which Logical CWP is mapped to which actual "physical" CWP.
AIRM Conformant
Off
AIRM Version
No Information Provided
LogicalCWP identifier
AIRM Conformant
Off
AIRM Version
No Information Provided
String to identify a logicalCWP.
AIRM Conformant
Off
AIRM Version
No Information Provided
String to identify the name of a sector mapping.
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
The report related to the client request
AIRM Conformant
Off
AIRM Version
No Information Provided
A Responsibility defines a domain assigned to a controller. Typically, a control Responsibility might be a control volume dealing with GAT IFR traffic, but it can also be, for example, an ACC AOR, an aerodrome, a runway, a set of runways, a set of stands at an aerodrome or any identifiable set of flights.
In EnRoute context, a control Responsibility is often a control volume composed of several unitary control sectors.
AIRM Conformant
Off
AIRM Version
No Information Provided
The unique identifier of the ASTUSectorConfiguration
AIRM Conformant
Off
AIRM Version
No Information Provided
ID to support the identification of the ATSUSectorConfiguration.
AIRM Conformant
Off
AIRM Version
No Information Provided
The designator of the SectorMapping.
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 milliseconds since the Unix epoch time - 00.00 hours - Jan, 1st, 1970 (UTC).
AIRM Conformant
Off
AIRM Version
No Information Provided
Message definition for the operational supervisor inputs related to airspace configuration (ARES and CDR activation, timesheets definition...).
AIRM Conformant
Off
AIRM Version
No Information Provided
Message definition for the operational supervisor inputs
AIRM Conformant
Off
AIRM Version
No Information Provided
Message definition of the operation corresponding to the same class name.
Specialisation of the common RequestReport.
AIRM Conformant
Off
AIRM Version
No Information Provided
Message definition for the operation of the same name
AIRM Conformant
Off
AIRM Version
No Information Provided
Message definition for the operation of the same name
AIRM Conformant
Off
AIRM Version
No Information Provided
Message definition for the operation of the same name
AIRM Conformant
Off
AIRM Version
No Information Provided
Message definition for the operation of the same name
AIRM Conformant
Off
AIRM Version
No Information Provided
Enables to modify a current mapping or a next mapping of a given ATSUSectorConfiguration.
The input parameters shall be at least the identifier of the ATSUSectorConfiguration, the name and the state of the sectorMapping and the sectorMapping content.
If the request is successful, the new mapping is published using the Operational Configuration Distribution Service in order to be displayed in the Controller and Operational Supervisor HMIs.
When the supervisor updates a sector mapping and fixes its defaultCommunicationResponsibility:
- some mapping checks and restriction when entering the fields prevent from possible inconsistencies,
- the CCS system allocate dynamically the frequencies to each logical CWP according to the Role/Responsibilites (e.g. Sectors for Tactical ATCO) mapped on it.
- the radio frequency allocation plan is unchanged.
Note:The cardinality of the parameter sectorMappingId for the UpdateSectorMapping operation is mandatory. Cfr ActivateSectorMapping operation description
Data Structures
CCS_operationalConfigurationManagement.proto v3.0.0.0
Schema Language
Protobuf
Reference
No Information Provided
CCS_operationalConfigurationManagement.proto v3.0.0.0
Schema Language
Protobuf
Reference
No Information Provided
CCS_operationalConfigurationManagement.proto v3.0.0.0
Schema Language
Protobuf
Reference
No Information Provided
CCS_operationalConfigurationManagement.proto v3.0.0.0
Schema Language
Protobuf
Reference
No Information Provided
CCS_operationalConfigurationManagement.proto v3.0.0.0
Schema Language
Protobuf
Reference
No Information Provided
CCS_operationalConfigurationManagement.proto v3.0.0.0
Schema Language
Protobuf
Reference
No Information Provided
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 operations used by the Operational Supervisor to modify on-line Airspace (ARES or CDR) Status data
PROVIDER_SIDE_INTERFACE
SWIM_TI_YP_1_0_AMQP_MESSAGING
IPV4_SECURE_UNICAST
SYNCHRONOUS_REQUEST_RESPONSE
Operations
Enables to unlock a previous manual ARES activation status.
Enables to update the status (activated or deactivated)and the comment associated to the ARES
Enables to unlock a previous manual CDR status.
Enables to lock the CDR status to open or closed.
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
This Service Interface exposes operations used by the Operational Supervisor to modify the Sector Configuration Data.
PROVIDER_SIDE_INTERFACE
SWIM_TI_YP_1_0_AMQP_MESSAGING
IPV4_SECURE_UNICAST
SYNCHRONOUS_REQUEST_RESPONSE
Operations
Enables to activate a sector mapping
Enables to modify a current mapping or a next mapping of a given ATSUSectorConfiguration.
Endpoints
Address
For security reasons, the adresses will be communicated only to Customers
Description
No Information Provided
Interface Binding Description Overview
Information 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
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
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.
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
Revision Save Date
Wed, 05/06/2020 - 14:08
Revision Number
42431
The service description has currently reached the "PUBLISHED" status.