ArrivalSequenceDistribution Service v1.1

Abstract
This Service is part of DSNA services. It supports the distribution of arrival sequences related to major hub airports.
Service Type
SWIM_CANDIDATE
Lifecycle Stage
PROSPECTIVE
Business Activity Type
TRAFFIC_SYNCHRONISATION
Intended Consumer
CIVIL_AIRSPACE_USER
AIR_TRAFFIC_SERVICE_PROVIDER
AIRPORT_OPERATOR
Information Exchange Category
FLIGHT_INFORMATION_EXCHANGE
Application Message Exchange Pattern
PUBLISH_SUBSCRIBE_WITH_PUSH_MECHANISM
Aerodrome ICAO Location Indicator
LFPG
LFPB
LFPO
LFPN
LFPV
FIR ICAO Location Indicator
No Information Provided
State ICAO Nationality Letters
No Information Provided
In-Operation Date
30-Jun-2021
Provider
DSNA

The direction des Services de la navigation aérienne (DSNA) is the agency in charge of air traffic control, communication and information for France. It is a part of the Ministry of Sustainable Development and was created by decree in February 2005.

Provider Type
CIVIL_AIR_NAVIGATION_SERVICE_PROVIDER
Support
No Information Provided
Point of Contact
DSNA SWIM service team
To request access to the service
Email
dsna_registry_access_manager@eei.cena.fr
Telephone
No Information Provided
COMMISSION IMPLEMENTING REGULATION (EU) No 716/2014
Operational Need
the service is defined to satisfy the requirement Arrival Management extended to en-route Airspace. The Implementing Regulation requires the upgrade of existing AMAN to provide connection with cooperative En-Route Air Traffic Service Units (ATSU) to coordinate the actions to be taken by the cooperative ATSUs to make the correct time adjustment to flights under their control, in order to get the best and most efficient arriving flight sequence at the relevant airports based on AMAN arriving planning tool.
Operational and Business context
Operational Need
The purpose of the AMAN RP SWIM service is to make available to external partners (ADP or Airline Companies) the sequence data provided by the AMAN APPs (CDG and ORY), in the format defined by ED-254 and without any transformation of the information.
Publish arrival sequence
Description
Publication of current arrival sequence information
Real World Effect
All subscribers are informed of any change about the arrival sequence of one or more airports, according to their subscription parameters.
Versioning Policy
Service update: This service will be updated when new operational needs are identified. Please get in touch with the Service Provider/Consumer Point of Contact for any evolution request regarding this Service. Backwards compatibility is guaranteed between minor versions but not for major. Given a version number MAJOR.MINOR.PATCH, DSNA will increment: the MAJOR version number when incompatible API changes occur, the MINOR version number when functionality evolve in a backwards compatible manner, the PATCH version number when backwards compatible bug fixes occur.
Lifecycle Policy
DSNA will manage 3 versions of the service: Versions N (i.e. nominal version of the service) and N-1 (if existing) provided by the operational system, Version N-1 will be removed when all consumers have migrated to the nominal version of the service or when the version N+1 is commissioned (Constraint of evolutivity). Version N or N+1 (if existing) provided by a pre-operational (preops) system. Please get in touch with the Service Provider / Consumer Point of Contact for any evolution request regarding this Service.
Access to the service
The access to the service is subject to the signature of a Service Agreement between DSNA and the Recipient. Please contact DSNA SWIM Services Responsible (§1.2) for more information.
Service consumption constraints
Two access points are provided for access to the service from Internet: One operational access point associated with the operational system (standard WSDL and amqps endpoint). One pre-operational access point associated with the pre-operational system (PREOPS WSDL and amqps endpoint). The certificate provided by DSNA is specific to the service and the endpoint (operational or pre-operational). Consumer must not use an operational certificate to invoke the pre-operational system. One subscription per certificate (and as a consequence, one AMQP connection).
Confidentiality
Communications are secured by TLS protocol. Communications (HTTPS and AMQPS) are secured by the TLS v1.2 protocol. SSL, TLS v1 to v1.1 versions are not supported. Suites using the AES -256 or ChaCha20 block cipher algorithm are preferred. The AES-128 algorithm is an acceptable alternative. Suites using the SHA2 and later hash functions are the only ones supported. Communications (HTTPS and AMQPS) require mutual authentication of the correspondents based on X-509 certificates (see § Authentication): The consumer must provide its full certificate during the connection phase. This certificate must not have been corrupted or revoked. The consumer's certificate also allows identification and secure access to the only distribution channel linked to its subscription. The server also transmits its full certificate during the connection phase.
Integrity
Communication integrity is guaranteed by TLS encryption.
Authentification
X.509 certificate All communications are secured by mutual authentication of correspondents using X.509 certificates. A consumer is entitled to one subscription per X.509 certificate and therefore one AMQP connection. The lifetime of a subscription and therefore of an AMQP connection is limited by the expiry date of the certificate. Upon service restart, active subscriptions are not lost. The certificates are issued to the consumer by the DSNA during the service contractualisation phase. Certificates have an expiry date and their renewal must therefore be managed in advance by both parties. Transport authentication: TLS with mutual authentication and SASL ANONYMOUS.
Authorisation
The consumer is authorized to access any Arrival Sequence information using a valid X.509 certificate associated with the Arrival Sequence Distribution Service (see Authentication).
Avaibility
The contractual service availability is defined in the Service Agreement (see §1.7.1). Target values: Availability of 99% over a rolling period of 1 calendar month Maximum Time to Recover: 24 hours.
Concepts
No Information Provided
A-CDM
Airport CDM (Collaborative Decision Making)
ADES
Aerodrome of Destination
AMQP
Advanced Message Queuing Protocol
ANSP
Air Navigation Service Provider
AOR
Area Of Responsibility
APTT
AMAN Planned Threshold Time
ATCO
Air Traffic Control Officer
ATM
Air Traffic Management
ATS
Air Traffic Services
ATSU
Air Traffic Service Unit
DSNA
Direction des Services de la Navigation Aerienne (French ANSP)
EH
Extended Horizon
EUROCAE
European Organisation for Civil Aviation Equipment
HTTP
Hypertext Transfer Protocol
IAF
Initial Approach Fix
ICAO
International Civil Aviation Organization
IP
Internet Protocol
OSED
Operational Services & Environment Description
SLA
Service Level Agreement
SOAP
Service Oriented Architecture Protocol
STA
Scheduled Time of Arrival
TCP
Transfer Control Protocol
TMA
Terminal Manoeuvring Area
URL
Uniform Resource Locator
WSDL
Web Services Description Language
XSD
SML Schema Definition
Information
Exchange Schema
SharedTypes.xsd
Description
No Information Provided
Schema Language
XML
Reference
https://api.dsna.fr/media/document/191
TLS 1.2
The service relies on TLS 1.2 to provide integrity and confidentiality.
X.509v3 Server Certificate
The service utilizes X.509v3 public certificate to authenticate the provider. (see Access and use conditions for more information)
X.509v3 Client Certificate
The service utilizes X.509v3 public certificate to authenticate the consumer. (see Access and use conditions for more information)
List of available arrival sequences
Find below the list of available arrival sequences or ADES codes that can be used in subscription requests or that can be present in received messages. CDG : LFPG, LFPB; Orly : LFPO, LFPN, LFPV.
Sizing and performance
For each selected ADES, a consumer must be able to receive one message every 15 sec. (standard sequence calculation period) without generating congestion in its queue. Unprocessed messages will be automatically suppressed after expiration of time to live (TTL) delay. This behavior is not critical due to the cyclical nature of the arrival sequence calculation (see ED-254-REQ 0870). The use of a message listener with deferred processing is recommended in this case. The consumer infrastructure must be able to handle the resulting flow rate from their subscription. The filter capability of the subscription request can be used to reduce the resulting flow rate (remove uninteresting ADES or flights). Find below some orders of magnitude for arrival sequence message size and associated flow rate (calculation period 15 sec.). Flights in the sequence Sequence size (bytes) Flow rate (with protocol overhead) (kb/s) Average ADES situation 40 44550 24 Loaded ADES situation 20 220550 118 The following values are given as a guide: Constant Indicative Value MAX_DELIVERY_TIME (cf. ED-254-REQ 0800, 0805) 10 sec MAX_CONSUMER_NUMBER (cf. ED-254-REQ 0885) 100 (no clear value identified at this stage)
In the event of a problem on the DSNA side:
The “back-end” server can stop the message service completely. It then issues a ProviderException message with the status AMAN_UNAVAILABLE (see ED-254-REQ 0575).
The problem may also be partial:
The server sends a providerException message for one or more ADES (specified in the impactedAdesList elements of the message) while continuing to serve the other arrivalSequence messages (see Figure 4 'alt on LFPO source error'):
If the consumer is not logged on when a providerException message is sent, the consumer will have to wait for a full message transmission cycle to identify the problem.
The maximum duration of a complete cycle for an aerodrome is given by the duration of the transmission cycle (@calculationPeriod) plus the maximum processing time ({MAX_DELIVERY_TIME}).
Message distribution resumes as soon as the cause of the problem is corrected (see ED-254-REQ 0590).
In the event of a one-off problem on the consumer side, a SOAP communicateProblem operation is available.
Information will be logged on DSNA side.
ArrivalSequenceInformationPublisher
Subscription management interface.The service consumer is able to subscribe and unsubscribe to the arrival sequence information and by using the same interface, the consumer is able to send problem reports.
PROVIDER_SIDE_INTERFACE
SWIM_TI_YP_1_0_WS_SOAP
IPV4_SECURE_UNICAST
SYNCHRONOUS_REQUEST_RESPONSE
Operations
OPERATIONAL
Address
https://eaman.swim.dsna.fr:443/aman/arrivalsequence/1.1.0/subscription
Description
operational network address
PRE-OPERATIONAL
Address
https://eaman.preops.swim.dsna.fr:443/aman/arrivalsequence/1.1.0/subscription
Description
pre-operational network address
SOAP over HTTPS: SOAP 1.1 / HTTP 1.1 / TLS 1.2 / TCP / IPv4
ArrivalSequenceInformationSubscriber
DSNA Arrival Sequence Service - Data distribution interface
CONSUMER_SIDE_INTERFACE
SWIM_TI_YP_1_0_AMQP_MESSAGING
IPV4_SECURE_UNICAST
No MEP Specified
Operations
communicateException
Operation to inform the service consumer about problems occurring, at service run-time, on provider side.
Operational
Address
amqps://eaman.swim.dsna.fr:5671
Description
operational network address
Pre-Operational
Address
amqps://eaman.preops.swim.dsna.fr:5671
Description
pre-operational network address
AMQPS: AMQP 1.0 / TLS 1.2 / TCP / IPv4
References
No Information Provided
Arrival Sequence Service Performance Standard

Standardised SWIM service design for an AMAN Sequence Service. (available standard by EUROCAE: https://eshop.eurocae.net/eurocae-documents-and-reports/ed-254/)

This EUROCAE standardised service design follows the specification documents for service descriptions as provided by EUROCONTROL. Together with them, it can be used as a basis to implement SWIM Service instances.

Revision Save Date
Tue, 05/18/2021 - 10:00
Revision Number
59836