CCS OperationalConfigurationManagement 2.0.0
Current JSON Original JSON

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...)

- Airspace planning management (ARES/CDR timesheets)

- Aerodrome configuration management

- RadioFrequency allocation plan management

Note: Only civil flights are handled by CCS services.

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, aerodrome configuration and radio frequency allocation and of CCS AirspaceStatusDistribution Service for ARES/CDR.

 

Service retired from 20/03/2023

Service Type
SWIM_COMPLIANT
Life Cycle
RETIRED
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
In-Operation Date
01-Jul-2020
Provider
DSNA&ENAV

DSNA: the French air navigation service provider

ENAV; the Italian air navigation service provider

Provider Type
CIVIL_AIR_NAVIGATION_SERVICE_PROVIDER
Point of Contact
1 General 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...)
- Airspace planning management (ARES/CDR timesheets)
- Aerodrome configuration management
- RadioFrequency allocation plan management

Information ownership

IPR
In 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 Service
This service is provided to Service Consumers under a contractual basis signed between the CCS Service Provider and the Service Consumer.

Dependencies with other CCS Services

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.

Service versioning

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 candidate
2: 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.

KPIs monitoring

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.

Confidentiality and integrity

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.

Authentication and authorisation

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.

Services level objectives

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.

Network performance

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.

Rate limitation

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.

AC

Airspace Configuration

ACC

Area Control Centre

ADES

Aerodrome of Destination

ADSP

ATM Data Service Provider

AFTN

Aeronautical Fixed Telecommunication Network

AIRM

ATM Information Reference Model

AMQP

Advanced Message Queuing Protocol

ANSP

Air Navigation Service Provider

AOR

Area Of Responsibility

APL

Abbreviated Flight Plan

ARES

Airspace Reservations

ASD

Airspace Status Distribution

ASM

Airspace Status Management

ATC

Air Traffic Control

ATCO

Air Traffic Control Officer

ATCS

Air Traffic Control Services

ATFCM

Air Traffic Flow and Capacity Management

ATM

Air Traffic Management

ATS

Air Traffic Services

ATSU

Air Traffic Service Unit

CCS

Coflight Cloud Services

CDM

Collaborative Decision Making

CDR

Conditional Route

CFMU

Central Flow Management Unit

CWP

Controller Working Position

DCB

Demand and Capacity Balancing

DSNA

Direction des Services de la Navigation A0xC3 0xA9rienne (French ANSP)

EAP

Extended ATC Planner

EATMA

European ATM Architecture

ENAV

Ente Nazionale Assistenza al Volo (Italian ANSP)

FAB

Functional Airspace Block

FABEC

Functional Airspace Block Europe Central

FDD

Flight Data Distribution

FDM

Flight Data Management

FDO

Flight Data Operator

FDPS

Flight Data Processing System

GAT

General Air Traffic

HMI

human machine Interface

ICAO

International Civil Aviation Organization

ID

Identifier

IFR

Instrument Flight Rules

IKE

Internet Key Exchange

INAP

Integrated Network Management and ATC planning

IP

Internet Protocol

IPSEC

Internet Protocol Security protocol

IPV4

Internet Protocol version 4

JU

Joint Undertaking

KPI

Key Performance Indicator

LTM

Local Traffic Manager

MSA

Multi-sector area

NOP

Network Operation Plan

NTP

Network Time Protocol

OCSP

Online Certificate Status Protocol

OE

Operational Entity

OPSUP

Operational Supervision

PKCS

Public-Key Cryptography Standards

SDD

Service Definition Document

SESAR

Single European Sky Air Traffic Management Research

SFPL

System Flight Plan

SLA

Service Level Agreement

SSD

SWIM Service Description

SSI

Synchronous Serial Interface

SWIM

System Wide Information Management

TAD

Technical Architecture Description

TBC

To Be Confirmed

TCP

Transfer Control Protocol

TDA

Temporary Danger Area

TI

Technical Infrastructure

TLS

transport level security

TSA

Temporary Segregated Area

UTC

Coordinated Universal Time

Information
TLS 1.2

TLS 1.2 is used to provide confidentiality and integrity at transport layer.

IPsec v4

IPsec is used to provide confidentiality, authentication and integrity at network (internet) layer

Time synchronisation

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.

Provider-Customer interface-Exchange patterns

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 Topics

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.

Provider-Customer interface-Queue management

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

AerodromeConfigurationManagementProvider

This Service Interface exposes operations used by the Operational Supervisor to modify the Aerodrome Configuration Data.

PROVIDER_SIDE
SWIM_TI_YP_1_0_AMQP_MESSAGING
IPV4_SECURE_UNICAST
SYNCHRONOUS_REQUEST_RESPONSE
Operations
modifyRunwayConfiguration

Allows to modify the current configuration of the runways for an aerodrome of a given Aerodrome Group.
This operation enables an eligible user (normally a supervisor) to modify the following data of a given runway or of the runway(s) of an aerodrome: landing and/or take-off rates, IAP in operation and operating mode (open or closed).
It is also possible to revert to default rate values of runway(s) if no rate value is provided in the operation..

Synchronous
SYNCHRONOUS
TI Protocol Methods
transfer
Operation Message
ModifyRunwayConfiguration
Processing Consideration
Successful request
activateAerodromeGroupConfiguration

Allows replacing the current Aerodrome Group Configuration with another given aerodrome group configuration.
The user may activate an offline predefined aerodrome group configuration, activate the one previously defined as the Next one or revert back to the default one.

When the aim of this operation is to :
- activate an offline predefined aerodrome group configuration, aerodromeGroupConfigName should be filled with the name of the configuration,
- activate the next aerodrome group configuration, aerodromeGroupConfigName should not be filled,
- revert back to the default aerodrome group configuration, aerodromeGroupConfigName should not be filled and aerodromeConfigurationOrigin should be DEFAULT.
.

Synchronous
SYNCHRONOUS
TI Protocol Methods
transfer
Operation Message
ActivateAerodromeGroupConfiguration
Processing Consideration
Successful request
modifyAerodromeConfiguration

Allows modifying the configuration parameters of an aerodrome.

The 3 possibilities given by this operation are :
- revert to default the aerodrome Altitude Correction
- revert to default the aerodrome Transition Level. In this case, defaultAltitudeCorrection should be set to FALSE
- modify one or several of the following parameters : transitionLevel, altitudeCorrection, modeSCapabilityState. In this case, revertToDefault should not be filled

aerodromeGroup is ignored by CCS..

Synchronous
SYNCHRONOUS
TI Protocol Methods
transfer
Operation Message
ModifyAerodromeConfiguration
Processing Consideration
Successful request
planifyNextAerodromeGroupConfiguration

Allows changing the next configuration to be applied for an aerodrome group by selecting another aerodrome configuration from a predefined configuration list, and/or to change the date and time that the configuration is planned to be activated.
.

Synchronous
SYNCHRONOUS
TI Protocol Methods
transfer
Operation Message
PlanifyNextAerodromeGroupConfiguration
Processing Consideration
Successful request
AerodromeConfigurationManagementProvider
Url

For security reasons, the addresses will be communicated only to Customers

Addressable Resource

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.

Service behaviour

The detailed behavior of the service is provided in each operation dedicated section

AirspacePlanningManagementProvider

This Service Interface exposes operations used by the Operational Supervisor to modify on-line Airspace (ARES or CDR) Planning data.

PROVIDER_SIDE
SWIM_TI_YP_1_0_AMQP_MESSAGING
IPV4_SECURE_UNICAST
SYNCHRONOUS_REQUEST_RESPONSE
Operations
createARESTimesheet

Allows to add a timesheet into an ARES timetable to define new activation periods.
The input parameters shall be the originator, the ARES name and the timesheet data containing the activation levels, an activation time period, and optionally a periodicity..

Synchronous
SYNCHRONOUS
TI Protocol Methods
transfer
Operation Message
CreateARESTimesheet
Processing Consideration
CFMU timesheets
createCDRTimesheet

Allows to add a timesheet to a CDR.
The input parameters shall be the originator, the CDR identifier (airway name and names of the start and last points of the CDR) and the timesheet data containing an activation time period, and optionally the activation levels and/or a periodicity..

Synchronous
SYNCHRONOUS
Precondition
The consumer has pre-defined (off-line) all his CDRs as portion of airways.
TI Protocol Methods
transfer
Operation Message
CreateCDRTimesheet
Processing Consideration
CFMU timesheets
deleteCDRTimesheet

Allows to remove an existing activation periods timesheet from a CDR timetable.
The input parameters shall be the originator, the CDR identifier (airway name and names of the start and last points of the CDR) and the identifier of the timesheet to remove..

Synchronous
SYNCHRONOUS
Precondition
The consumer has pre-defined (off-line) all his CDRs as portion of airways.
TI Protocol Methods
transfer
Operation Message
DeleteCDRTimesheet
Processing Consideration
Successful request
updateARESTimesheet

Allows to update an existing activation periods timesheet for an ARES.
The input parameters shall be the originator, the ARES name, the identifier of the timesheet to update and the timesheet data containing the activation levels, an activation time period, and optionally a periodicity..

Synchronous
SYNCHRONOUS
TI Protocol Methods
transfer
Operation Message
UpdateARESTimesheet
Processing Consideration
CFMU timesheets
updateCDRTimesheet

Allows to update an existing CDR timesheet.
The input parameters shall be the originator, the CDR identifier (airway name and names of the start and last points of the CDR), the identifier of the timesheet to update and the timesheet data containing an activation time period, and optionally the activation levels and/or periodicity..

Synchronous
SYNCHRONOUS
Precondition
The consumer has pre-defined (off-line) all his CDRs as portion of airways.
TI Protocol Methods
transfer
Operation Message
UpdateCDRTimesheet
Processing Consideration
Predefined timesheet modification
AirspacePlanningManagementProvider
Url

For security reasons, the addresses will be communicated only to Customers

Addressable Resource

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.

Service behaviour

The detailed behavior of the service is provided in each operation dedicated section

AirspaceStatusManagementProvider

This Service Interface exposes operations used by the Operational Supervisor to modify on-line Airspace (ARES or CDR) Status data.

PROVIDER_SIDE
SWIM_TI_YP_1_0_AMQP_MESSAGING
IPV4_SECURE_UNICAST
SYNCHRONOUS_REQUEST_RESPONSE
Operations
unlockCDRStatus

Enables to unlock a previous manual CDR status.
The input parameters shall be the originator and the CDR identifier (airway name and names of the start and last points of the CDR)..

Synchronous
SYNCHRONOUS
Precondition
The consumer has pre-defined (off-line) all his CDRs as portion of airways.
TI Protocol Methods
transfer
Operation Message
UnlockCDRStatus
Processing Consideration
Successful request
updateCDRStatus

Enables to lock the CDR status to open or closed.
The input parameters shall be the originator, the CDR identifier (airway name and names of the start and last points of the CDR) and the CDR status..

Synchronous
SYNCHRONOUS
Precondition
The consumer has pre-defined (off-line) all his CDRs as portion of airways.
TI Protocol Methods
transfer
Operation Message
UpdateCDRStatus
Processing Consideration
Successful request
AirspaceStatusManagementProvider
Url

For security reasons, the addresses will be communicated only to Customers

Addressable Resource

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.

Service behaviour

The detailed behavior of the service is provided in each operation dedicated section

RadioFrequencyAllocationManagementProvider

This Service Interface exposes operations used by the Operational Supervisor to modify the Radio Frequency Allocation.

PROVIDER_SIDE
SWIM_TI_YP_1_0_AMQP_MESSAGING
IPV4_SECURE_UNICAST
SYNCHRONOUS_REQUEST_RESPONSE
Operations
updateFrequency

Allows a consumer to modify the radio frequency assigned to control responsibility(ies):
- either by selecting a new radio frequency,
- or by reverting back to the predefined value (off-line defined) of the radio frequency assigned to the given control responsibility (if it has been on-line updated before).

The input parameters shall be:
- the value of the new radio frequency and the controlResponsibility(ies) where the indicated frequency shall be assigned,
- or the controlResponsibility(ies) where the default frequency shall be assigned.

When the aim of this operation is to :
- apply a new frequency to one or several Responsibilities, frequency should be filled
- revert to default frequency for one or several Responsibilities, revertToDefaultFreq should be set to TRUE and frequency shouldn't be filled
.

Synchronous
SYNCHRONOUS
TI Protocol Methods
transfer
Operation Message
UpdateFrequency
Processing Consideration
system checks
updateFrequencyPlan

Allows a consumer to change the current radio frequency allocation:
- either by selecting a new radio frequency allocation plan among the predefined radio frequency configurations,
- or by reverting back to the predefined default radio frequency configuration (offline defined).

The input parameters shall be:
- the name of the requested ATSUSectorConfiguration,
- and the name of the radio frequency configuration to load in place of the current one (except on the operation of reverting back to the default one: in this case this is the default radio frequency configuration which will be loaded).

When the aim of this operation is to :
- apply a new plan to an ASTUSectorConfiguration, radioFrequencyAllocationName should be filled
- revert to default frequency plan an ASTUSectorConfiguration, revertToDefaultPlan should be set to TRUE and radioFrequencyAllocationName shouldn't be filled
.

Synchronous
SYNCHRONOUS
TI Protocol Methods
transfer
Operation Message
UpdateFrequencyPlan
Processing Consideration
system checks

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.

Service behaviour

The detailed behavior of the service is provided in each operation dedicated section

SectorConfigurationManagementProvider

This Service Interface exposes operations used by the Operational Supervisor to modify the Sector Configuration Data.

PROVIDER_SIDE
SWIM_TI_YP_1_0_AMQP_MESSAGING
IPV4_SECURE_UNICAST
SYNCHRONOUS_REQUEST_RESPONSE
Operations
activateSectorMapping

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.
As a consequence, the parameter sectorMappingId is MANDATORY when the parameter revertToDefaultMapping is not filled or set to FALSE (but if revertToDefaultMapping is set to YES, sectorMappingId is not needed)..

Synchronous
SYNCHRONOUS
TI Protocol Methods
transfer
Operation Message
ActivateSectorMapping
Processing Consideration
Successful request
deleteSectorMapping

Enables to delete a given sector mapping. Only the next sector mapping can be deleted.
The input parameter is the identifier of the concerned ATSUSectorConfiguration (sufficient to delete a next mapping knowing that only one next sector mapping per ATSUSectorConfiguration).
.

Synchronous
SYNCHRONOUS
TI Protocol Methods
transfer
Operation Message
DeleteSectorMapping
Processing Consideration
Successful request
SectorConfigurationManagementProvider
Url

For security reasons, the addresses will be communicated only to Customers

Addressable Resource

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.

Service behaviour

The detailed behavior of the service is provided in each operation dedicated section

References
CCS AIRM mapping OPSUPM service

AIRM traceability for CCS Operational Configuration Management service payload

Reference
https://confluenceccs.se-dmf.eu/display/CDFSR/CCS+Operational+Configuration+Management+Service
Note: to request access to Confluence, please refer to the point of contact section
CCS_common.proto

Protobuf file describing the exchanged information common to two or more CCS Services

Reference
https://confluenceccs.se-dmf.eu/display/CDFSR/CCS+Operational+Configuration+Management+Service
metadata.proto

Protobuf file describing the metadata used by the CCS Services

Reference
https://confluenceccs.se-dmf.eu/display/CDFSR/CCS+Operational+Configuration+Management+Service
CCS Errors Management Document

Document that includes the list of all applicable error messages for CCS services

Reference
https://confluenceccs.se-dmf.eu/display/CDFSR/Applicable+Documents
EUROCONTROL Specification for SWIM - Service 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

EUROCONTROL Specification for SWIM - Information Definition

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.

Revision Save Date
Mon, 03/25/2024 - 23:20
Schema version
v2