CCS FlightDataDistribution

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 FlightDataDistribution service is consistent with the other CCS services. It supports: - the distribution of Flight Plan information every time an update of a relevant Flight Plan is processed by the ADSP. The modifications of the Flight Plans can be triggered from several sources (other CWPs or functionality of the ADSP). - The distribution of Erroneous AFTN messages information referred to FDO for manual correction, every time an AFTN message reception fails Coflight checks. 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.

Service retired from 20/03/2023

Categorisation

Service Type

SERVICE_DESCRIPTION

Life Cycle Stage

RETIRED

Business Activity Type

INFORMATION_MANAGEMENT

Intended Consumer

CIVIL_AIR_NAVIGATION_SERVICE_PROVIDER

Information Exchange Category

FLIGHT_INFORMATION_EXCHANGE

Provider

DSNA&ENAV

Description

DSNA: the French air navigation service provider

ENAV; the Italian air navigation service provider

Type

CIVIL_AIR_NAVIGATION_SERVICE_PROVIDER

Point of Contact

Restricted

Contact Information

Restricted

Name

1 General operational need

Description

CCS FlightDataDistribution Service supports:- the distribution of Flight Plan information every time an update of a relevant Flight Plan is processed by the ADSP,- the distribution of Erroneous AFTN messages information every time an AFTN message reception fails Coflight checks.

Name

Publish flight data

Description

Publish flight data

Real World Effect

All subscribers are informed of any change on the flight plan information of a flight when this flight is updated

Name

Publish erroneous AFTN messages

Description

Publish erroneous AFTN messages

Real World Effect

All subscribers receive the AFTN messages information concerning the erroneous AFTN messages that need to be referred to FDO for manual correction.

Name

Get erroneous AFTN messages

Description

Get erroneous AFTN messages

Real World Effect

On request, a subscriber gets the AFTN messages information concerning the erroneous AFTN messages that need to be referred to FDO for manual correction.

Name

Get flight data

Description

Get flight data

Real World Effect

On request, a subscriber gets the flight plan information.

Information ownership

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.
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.
Alignment to SESAR Virtual Centre activity

This service will be updated to be as much as possible in line with the Service Definition produced by SESAR Virtual Centre activities
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 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.
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.

Name

Subscription filter for FlightDataSubscriber interface///~~///~~///62a8554c8b154

Name

Subscription filter for ErroneousFlightDataSubscriber interface///~~///~~///62a8554c8b157

ABI

Advanced Boundary Message
AC

Airspace Configuration
ACC

Area Control Centre
ACH

ATC Change Message (ICAO format, CFMU special)
ACP

Accept Message
ACT

Activate Message
ADEP

Airport of Departure
ADES

Airport of Destination
ADEXP

ATS Data Exchange Presentation
ADS

Automatic dependent surveillance
ADSP

ATM Data Service Provider
AFPL

Abbreviated Flight Plan
AFTN

Aeronautical Fixed Telecommunication Network
AIRM

ATM Information Reference Model
ALRS

Alerting Service
AMQP

Advanced Message Queuing Protocol
ANSP

Air Navigation Service Provider
AOI

Area Of Interest
APCH

Approach
APL

ATC Flight Plan Message (ICAO)
APOC

Airport Operator
APP

Approach
AR

Authorisation Required
ARR

Arrival
ATC

Air Traffic Control
ATCO

Air Traffic Control Officer
ATCS

Air Traffic Control Services
ATD

Actual Time of Departure
ATFCM

Air Traffic Flow and Capacity Management
ATI

Automatic Tracking Initiation
ATM

Air Traffic Management
ATN

Aeronautical Telecommunication(s) Network
ATO

Actual Time Over
ATOT

Actual Take-Off Time
ATS

Air Traffic Services
ATSU

Air Traffic Service Unit
CCS

Coflight Cloud Services
CDN

Coordination Message
CDR

Conditional Route
CFL

Cleared Flight Level
CHG

ICAO ATS Change Message
CLDM

Consolidated Logical Data Model
CNL

ICAO ATS Cancel Message
COF

Change of Frequency Message
COP

Coordination Point
CORRD

Correlation Distribution
CPDLC

Controller Pilot Datalink Communications
CWP

Controller Working Position
DAD

Dialogue and Distribution
DCB

Demand and Capacity Balancing
DCT

Direct Routing
DEP

Departure
DLA

ICAO ATS Delay Message
DOF

Date of Flight
DSNA

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

Extended ATC Planner
EATMA

European ATM Architecture
ECL

En-Route Cruise Level
EET

Estimated Elapsed Time
EFL

Entry Flight Level
ENAV

Ente Nazionale Assistenza al Volo (Italian ANSP)
ENV

Environment
EOBD

Estimated Off-Block Date
EOBT

Estimated Off-Block Time
EQPT

Equipment
ETA

Estimated Time of Arrival
ETN

Estimated Time of Entry
ETX

Estimated Time of Exit
FABEC

Functional Airspace Block
FANS

Future Air Navigation Systems
FDD

Flight Data Distribution
FDM

Flight Data Management
FDO

Flight Data Operator
FDPS

Flight Data Processing System
FL

Flight Level
FNM

Flight Notification Message
FP

Flight Plan
FPL

Flight Plan Message (ICAO)
GAT

General Air Traffic
GGDC

Ground Ground Data Communications
HMI

human machine Interface
HOP

Hand Over Proposal message
IACH

Individual ATC Modification Message
IAP

Instrument Approach Procedure
IAPL

Individual ATC Flight Plan Message
IARR

Individual Arrival Message
IAS

Indicated Airspeed
ICAO

International Civil Aviation Organization
ICD

Interface Control Document
ICHG

Individual Modification Message
ICNL

Individual Cancellation Message
ID

Identifier
IDEP

Individual Departure Message
IDLA

Individual Delay Message
IER

Interface Exchange Requirement
IFPL

Individual Flight Plan Message
IFPS

Integrated initial flight plan processing system
IFR

Instrument Flight Rules
IKE

Internet Key Exchange
INAP

Integrated Network Management and ATC planning
IOP

Interoperability
IP

Internet Protocol
IPSEC

Internet Protocol Security protocol
IPV4

Internet Protocol version 4
JU

Joint Undertaking
KPI

Key Performance Indicator
LAM

Logical Acknowledgment Message
LOA

Letter of Agreement
LOF

Logon Forward
LP

Logical Position
LTM

Local Traffic Manager
MAS

Manual Assumption of Communications Message
MB

Mega byte
MEP

Message Exchange Pattern
MSA

Multi-sector area
MTCD

Medium Term Conflict Detection
NDA

Next Data Authority
NM

Network Manager
NOP

Network Operation Plan
NTP

Network Time Protocol
OAT

Operational Air Traffic
OCA

Oceanic Control Area
OCL

Oceanic Clearance
OCM

Oceanic Clearance Message
OCSP

Online Certificate Status Protocol
OE

Operational Entity
OLDI

On-line Data Interchange
PAC

Preliminary Activate Message
PBN

Performance Based Navigation
PKCS

Public-Key Cryptography Standards
PRO

Profile
PTA

Planned time of Arrival
RFL

Requested Flight Level
RJC

Reject Message
RNAV

Area Navigation
ROC

Rate of Climb
ROCD

Rate of Climb Descend
ROF

Request on Frequency
RPL

Repetitive Flight Plans
RTI

Request Tactical Instructions message
RVSM

Reduced Vertical Separation Minima
SAC

System Area Code
SDD

Service Definition Document
SDM

Supplementary Data Message
SESAR

Single European Sky Air Traffic Management Research
SFPL

System Flight Plan
SIC

System Identification Code
SID

Standard Instrumental Departure
SLA

Service Level Agreement
SSD

SWIM Service Description
SSI

Synchronous Serial Interface
SSR

Secondary Surveillance Radar
SSRM

Secondary Surveillance Radar Management
STAR

Standard Arrival Route
SWIM

System Wide Information Management
TBC

To Be Confirmed
TBD

To Be Defined
TCP

Transfer Control Protocol
TI

Technical Infrastructure
TIM

Transfer Initiation Message
TIP

Tactical Instructions Proposal message
TLS

transport level security
TP

Trajectory Prediction
UHF

Ultra High Frequency
UTC

Coordinated Universal Time
VC

Virtual Centre
VFR

Visual Flight Rules
VRCD

Vertical Rate Climb Descent
XFL

Exit Flight Level

Name

Service Information Definition

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 shall use, each of them, at least one NTP server (stratum N), integrated in a NTP network containing a stratum 0 reference time clock. CCS customer may use a CCS provider server as a NTP server, however this usage is restricted to time synchronization test or monitoring purpose.
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, if any, defined for the 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.
Provider-Customer interface-Connection management

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

FlightDataSubscriber

This Service Interface exposes one operation for publishing updates of flight plan data on a specific flight immediately when updated.

PROVIDER_SIDE

FIRE_AND_FORGET
- publishFlightDataDistribution
  
  This operation sends the flight plan data of a flight when it is updated..
  git
  Messages
  
  FlightDataMessage
  
  IN
  
  void
  
  OUT
Endpoints

Restricted
ErroneousFlightDataSubscriber

This Service Interface exposes one operation for publishing the erroneous AFTN message information for FDO correction.

PROVIDER_SIDE

FIRE_AND_FORGET
- publishErroneousAFTNMessageData
  
  This operation sends the erroneous AFTN messages information for FDO correction.Upon reception of an AFTN erroneous message associated to a given SFPL, this message is referred to FDO.Only the following AFTN messages are referred to FDO by CCS (the other are not yet within the scope of PJ16): ACH, APL, ARR, CHG, CNL, DEP, DLA, FPL, IACH, IAPL, IARR, ICHG, ICNL, IDEP, IDLA, IFPL.The consumer can receive two other kinds of referred message: blocked and not checked.The information referralType is used to differentiate an erroneous message referred for correction from a message "blocked" by FDM since an erroneous message for the same SFPL was already referred to FDO.
  git
  Messages
  
  ErroneousAFTNMessage
  
  IN
  
  void
  
  OUT
Endpoints

Restricted
FlightDataProvider

This Service Interface exposes the technical operation that allows the consumer to get the current flight plan data of all flights on request. It is typically used when starting the Service, for initialisation.

PROVIDER_SIDE

SYNCHRONOUS_REQUEST_RESPONSE
- flightDataRepositoryRequest
  
  Allows a consumer to get the applicable flight plan data related to all relevant flights concerning this consumer.In the request, the parameter oe allows to filter the flights to be received in return (the criteria is fulfilled if oe is part of the list of servedController.controller.identifier for the flight). If no oe is filled, no fliter is applied to the response (all flights known by the system are expected). The parameter wpId is ignored by CCS..
  git
  Messages
  
  FlightDataRepositoryRequest
  
  IN
  
  FlightDataRequestReport
  
  OUT
Endpoints

Restricted
ErroneousFlightDataProvider

This Service Interface exposes two technical operations that allows the consumer to get the erroneous AFTN message information for FDO correction, on request. It is typically used when starting the Service, for initialisation.

PROVIDER_SIDE

SYNCHRONOUS_REQUEST_RESPONSE
- getErroneousAFTNMessage
  
  Allows a consumer to get the erroneous AFTN messages referred to FDO for manual correction, either for a specific erroneous message by filling the messageId, or all the erroneous messages if the messageId attribute is empty.Refer to publishErroneousAFTNMessageData description for more details about the list of errors that can be enc.
  git
  Messages
  
  GetErroneousAFTNMessage
  
  IN
  
  GetErroneousAFTNMessageReport
  
  OUT
- getErroneousAFTNMessageSummary
  
  Allows a consumer to get the summary of erroneous AFTN messages referred to FDO for manual correction.Refer to publishErroneousAFTNMessageData description for more details about the list of errors that can be encountered.
  git
  Messages
  
  GetErroneousAFTNMessageSummary
  
  IN
  
  GetErroneousAFTNMessageSummaryReport
  
  OUT
Endpoints

Restricted

CCS AIRM mapping FDD service

AIRM traceability for CCS Flight Data Distribution service payload

AIRM_TRACE

1.0
CCS Validation evidence document - FlightDataDistribution

Validation evidence for CCS Flight Data Distribution service

SERVICE_VALIDATION_REPORT

1.0
CCS_flightDataDistribution.proto

Protobuf files describing the exchanged information

MACHINE_READABLE_SERVICE_DESCRIPTION

5.2.0.2
CCS_common.proto

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

MACHINE_READABLE_SERVICE_DESCRIPTION

5.5.1.2
metadata.proto

Protobuf file describing the metadata used by the CCS Services

MACHINE_READABLE_SERVICE_DESCRIPTION

v1.2.0.0
CCS Flight Data Distribution Service Description

Complete service specification

SERVICE_SPECIFICATION

5.5.0.3
CCS Errors Management Document

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

SERVICE_SPECIFICATION

2.0

Title

EUROCONTROL Specification for SWIM - Service Description

Standard Type

EUROCONTROL_SPECIFICATION_FOR_SWIM_SERVICE_DESCRIPTION

Conformance Statement

Description of Service according to EUROCONTROL specifications

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

Title

EUROCONTROL Specification for SWIM - Information Definition

Standard Type

EUROCONTROL_SPECIFICATION_FOR_SWIM_INFORMATION_DEFINITION

Conformance Statement

Information definition according to EUROCONTROL specifications

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.

Title

EUROCONTROL Specification for SWIM - Technical Infrastructure (TI) Yellow Profile

Standard Type

EUROCONTROL_SPECIFICATION_FOR_SWIM_TECHNICAL_INFRASTRUCTURE

Conformance Statement

Implementation of service and network bindings

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

CCS FlightDataDistribution v 2.0.0

Categorisation

Provider