This Service is part of DSNA services. It supports the distribution of arrival sequences related to major hub airports.
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.
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.
Publication of current arrival sequence information
Business and operational policies are defined in the Service Agreement.
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.
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.
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.
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).
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.
Communication integrity is guaranteed by TLS encryption.
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.
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).
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.
Airport CDM (Collaborative Decision Making)
Arrival management
AMAN Planned Time Over
AMAN Planned Threshold Time
AMAN Target Landing Time
Extended Horizon
European Organisation for Civil Aviation Equipment
Initial Approach Fix
Metering Point
Operational Services & Environment Description
Runway
Service Oriented Architecture Protocol
Scheduled Time of Arrival
SWIM Technical Infrastructure
Terminal Manoeuvring Area
Top Of Descent
Time To Gain
Time To Lose
Uniform Resource Locator
Web Services Description Language
SML Schema Definition
WSDL
XML
XML
XML
The service utilizes X.509v3 public certificate to authenticate the provider. (see Access and use conditions for more information)
The service utilizes X.509v3 public certificate to authenticate the consumer. (see Access and use conditions for more information)
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.
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)
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.
SOAP subscription Operation
SOAP unsubscription Operation
Operation to log a problem in the DSNA monitoring system
operational network address
pre-operational network address
SOAP over HTTPS: SOAP 1.1 / HTTP 1.1 / TLS 1.2 / TCP / IPv4
The following diagram illustrates the interaction between the service consumer and the service:
DSNA Arrival Sequence Service - Data distribution interface
Operation to transmit the ArrivalSequence message to the service consumer
Operation to inform the service consumer about problems occurring, at service run-time, on provider side.
operational network address
amqps://eaman.swim.dsna.fr:5671
pre-operational network address
amqps://eaman.preops.swim.dsna.fr:5671
AMQPS: AMQP 1.0 / TLS 1.2 / TCP / IPv4
The following diagram illustrates the interaction between the service consumer and the service:
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.