CCS OperationalConfigurationDistribution v 2.0.0

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.

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.

This service will be updated to be as much as possible in line with the Service Definition produced by SESAR Virtual Centre activities

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.

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

Airspace Configuration

Area Control Centre

Airport of Destination

ATM Data Service Provider

Alerting Service

Advanced Message Queuing Protocol

Air Navigation Service Provider

Area Of Responsibility

Airport Operator

Approach

Air Traffic Control

Air Traffic Control Officer

Air Traffic Control Services

Air Traffic Flow and Capacity Management

Air Traffic Management

Air Traffic Services

Air Traffic Service Unit

Coflight Cloud Services

Controller Working Position

Demand and Capacity Balancing

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

Extended ATC Planner

European ATM Architecture

Ente Nazionale Assistenza al Volo (Italian ANSP)

Flight Data Distribution

Flight Data Processing System

Flight Plan

General Air Traffic

human machine Interface

International Civil Aviation Organization

Interface Control Document

Identifier

Interface Exchange Requirement

Instrument Flight Rules

Internet Key Exchange

Integrated Network Management and ATC planning

Internet Protocol

Internet Protocol Security protocol

Joint Undertaking

Key Performance Indicator

Local Traffic Manager

MegaByte

Message Exchange Pattern

Multipurpose Internet Mail Extensions

Multi-sector area

Network Operation Plan

Network Time Protocol

Online Certificate Status Protocol

Operational Entity

Public Key Cryptography Standards

Service Definition Document

Single European Sky Air Traffic Management Research

System Flight Plan

Service Level Agreement

SWIM Service Description

Synchronous Serial Interface

Secondary Surveillance Radar

System Wide Information Management

To Be Defined

Transfer Control Protocol

Technical Infrastructure

Tactical Instructions Proposal message

Transport Level Security

Coordinated Universal Time

Wide Area Network