FlightDataDistribution Service 1.4.3
Current JSON Original JSON

Abstract

This SWIM Service supports the distribution of Flight Plan information every time an update of a relevant Flight Plan is processed by the ADSP in the context of Virtual Centre. The modifications of the Flight Plans can be triggered from several sources (other CWPs or functionality of the ADSP). The content of the published flight plan addresses the expectations from a CWP, or any other ATSU HMI, whatever the data is targeted for a direct display to a final user, or is used by the CWP to calculate some specific information to be displayed as well. Therefore this service differs significantly from the other FP services which mostly target FDP consumers rather than CWP consumers, thus missing a very large set of specific and detailed data.required by a CWP.

The following high level topics are provided by the FDD service:

- Aircraft: data specific to the aircraft executing the FP (WTC, equipments...)

- Flight Data Info: general flight data (callsign, ADEP, flight rules...)

- Departure: departure data (various OBT, SID,...) - Arrival: arrival data (various arrival times, STAR...)

- Route: expanded route data

- Segment: management of the trajectory in terms of system AoR

- SSR Code: the current FP various SSR codes

- Trajectory: the detailed calculated trajectory, including the expected sector crossing sequence

- CoordinationAndTransfer: the management of the flight coordination and transfer operations

- Point Session: the management of the point out operations as specified by OLDI, or internal session

- Served Controller: list of the controllers expected to receive the FP data.

 

Service Type
SWIM_COMPLIANT
Abbreviation
DSNA
Life Cycle
PROSPECTIVE
Business Activity Type
INFORMATION_MANAGEMENT
Intended Consumer
AIR_TRAFFIC_SERVICE_PROVIDER
CIVIL_AIR_NAVIGATION_SERVICE_PROVIDER
CIVIL_AIRSPACE_USER
PROVIDER_OF_DATA_SERVICES
Information Exchange Category
FLIGHT_INFORMATION_EXCHANGE
Application Message Exchange Pattern Entity
BROKERED_PUBLISH_SUBSCRIBE_WITH_PUSH_MECHANISM
State ICAO Nationality Letters
LF
Other
Service Type: FLIGHT_INFORMATION_FEATURE_ACCESS_SERVICE
In-Operation Date
09-Feb-2027
Provider
DSNA

DSNA (Direction des Services de la Navigation Aerienne) is the national air navigation services provider of France.

DSNA is entrusted with the provision of air traffic services, associated communication, navigation and surveillance services and aeronautical information services in all airspace under French responsibility and at designated airports. DSNA is member of A6, FABEC and SESAR JU.

Paris ACC : At the crossroads of the biggest European platforms, Paris ACC manage one of the densest airspace in Europe. Paris ACC act to develop Paris airports capacity. The traffic handled by Paris ACC consists of 72% of flights departing or arriving at Parisian airports. With its 1.3 million controlled flights in 2018, Paris ACC is one the most important ACC in Europe.

Core business is to manage the regulated Air Traffic Control Services (ATCS), for which it is entrusted, allowing aircraft to fly within the assigned airspace with constantly enhanced levels of safety, optimizing the effectiveness of the service provided and the efficiency of the company"

Provider Type
PROVIDER_OF_DATA_SERVICES
Point of Contact
General operational need

FlightDataDistribution Service supports the distribution of Flight Plan information every time an update of a relevant Flight Plan is processed by the ADSP.

Subscription

Consumers needs to contact DSNA to register administratively to this service.

Aviation users

Only service consumers within the aviation domain can use this service.

Non aviation users

The service consumers cannot pass the information obtained from the service to non-aviation users without prior authorisation from DSNA.

Service versioning

At least 2 versions of this swim service could be maintained in the same time, taking benefit the capacities of technologies used in DSNA such as protobuf.

Service reviews

Services management review are regularly organized with customers to monitor the usability of the services and the KPI related to the quality of service described in the SLA.

Internet Accessibility

The interface of DSNA business services is accessible from outside DSNA premises through Internet using IPV4. An IPSEC link (IKE v1 or IKE v2) is used between DSNA provider and customer terminal network equipment.

Mutual authentication with X509 certificates

Authentication is required - Mutual authentication with X509 certificates is used between the AMQPS broker and its client established within a TLS session. IPsec is used to provide confidentiality, authentication and integrity at network (internet) layer.

Confidentiality

The service relies on TLS 1.2 to provide integrity and confidentiality.

Integrity

The service relies on TLS 1.2 to provide integrity and confidentiality.

Services level objectives

The service level objectives regarding the availability, response time, throughput and recoverability of DSNA Services depend on the purpose (mission) for which the Customer intend to use them (e.g. 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 DSNA Customer.

Network performance

The minimum Bandwidth required to consume DSNA 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.

Recoverability

The service level objectives regarding the recoverability of the Service depend on the purpose (mission) for which the Customer intend to use it (e.g. test, training or 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 Customer.

Availability

The service level objectives regarding the availability of the Service depend on the purpose (mission) for which the Customer intend to use it (e.g. test, training or 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 Customer.

Confidentiality

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

Integrity

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

Subscription filter for FlightDataSubscriber interface
ADEP

Airport of Departure

ADSP

ATM Data Service Provider

AMQP

Advanced Message Queuing Protocol

ANSP

Air Navigation Service Provider

AOR

Area Of Responsibility

ATC

Air Traffic Control

ATM

Air Traffic Management

ATSEP

Air Traffic Safety Electronics Personnel

ATSU

Air Traffic Service Unit

CWP

Controller Working Position

DO

Direction des Opérations

DSNA

Direction des Services de la Navigation Aerienne (French ANSP)

FDD

Flight Data Distribution

FP

Flight Plan

HMI

Human Machine Interface

HTTP

Hypertext Transfer Protocol

ICAO

International Civil Aviation Organization

IP

Internet Protocol

IPV4

Internet Protocol version 4

KPI

Key Performance Indicator

NTP

Network Time Protocol

OE

Operational Entity

OLDI

On-line Data Interchange

SDD

Service Definition Document

SESAR

Single European Sky Air Traffic Management Research

SLA

Service Level Agreement

SSD

SWIM Service Description

SWIM

System Wide Information Management

TCP

Transfer Control Protocol

TI

Technical Infrastructure

TLS

Transport Level Security

URL

Uniform Resource Locator

UTC

Universal Time Coordinated

XML

Extensible Markup Language

Information
Operational entities

The Consumer subscribing to the operation publishFlightDataDistribution can filter the distributed messages on the required Operational entities.

The flight plan data can be triggered from several sources (other CWPs or functionalities of the ADSP).
Time synchronization

NTP is the standard solution for accurately synchronizing systems to UTC time. So, DSNA Provider and DSNA 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.

Technical behaviour

Each service interface of the DSNA business services relies on the concept of AMQP queues and topics. - The customer shall use an implementation of the AMQP 1.0 specification to connect to the DSNA provider endpoint. - The DSNA provider endpoint is an AMQP 1.0 broker managing queue and topics. The message payloads are encoded following a protobuf format. The customer acts as requester and subscriber. The DSNA provider acts as responder and publisher. Concerning publish-subscribe, the customer subscribes to a DSNA distribution service by directly listening to an appropriate AMQP topic, which name follows the DSNA derivation rules. The customer requests on the Subscription management queue the creation of a new subscription. The DSNA provider returns on the Reply queue, the address of the Publication queue(s) to receive data (one queue per type of subscribed data). The subscribers can filter the messages they want to receive by using the filter parameters defined for each subscription operation. N.B: - If the DSNA 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. - More generally, since the distribution events from different services are asynchronous (independent topics), they may be received in a few ms before reaching consistency. Concerning request-reply (used for subscription technical operations or management operations) the DSNA customer sends a request by sending a message to an appropriate AMQP queue, which name follows the DSNA derivation rules, to make a request. The request message contains the name of the queue into the DSNA customer listens and in which the reply from the DSNA provider is expected.

Reconnection

The Customer is the one that initiates the TCP connection and in case of a Network / Connection failure, it is the responsibility of the DSNA customer to try to reconnect regularly.

Permission on Topic

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 DSNA customer will have: - Write access on the request queue - Read access on the reply queue - Read access on the topic for distribution service

SubscriptionManagement

The following section lists the available subscription operations:
subscribe, resume a subscription, pause a subscription, get a subscription, get susbscription list, refresh a subscription, renew a subscription, udate a subscription, unsubscribe.

For more information on how to subscribe to this service, please contact DSNA customer 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
Operations
Endpoint

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

Url

amqps://

SWIM_TI_YP_1_0_AMQP_MESSAGING

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.

FlightDataMessage
References
CCS_common.proto

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

metadata.proto

Protobuf file describing the metadata used by the DSNA Services

Revision Save Date
Tue, 05/12/2026 - 16:55
Schema version
v2