EUROCONTROL is an intergovernmental organisation with 42 Member and 2 Comprehensive Agreement States.
- Home
- Service Descriptions
- ADS-C Ground Distribution SWIM Service
The ADS-C Ground Distribution Service distributes to ground users the ADS-C data collected from ATS B2 equipped aircraft by the ADS-C Common Service. It supports a Publish/Subscribe Push Message Exchange Pattern for the distribution of ADS-C data, flight status changes and Request/Reply Message Exchange Pattern to support the creation of Demand Contract Requests and to query flight status by ground users.
This service definition summarizes the service as defined in the full specification EUROCONTROL Specification for Data Link Ground Distribution SWIM Services. The specification should be considered the primary reference. Please consult it for complete and authoritative information.
EUROCONTROL is an intergovernmental organisation with 42 Member and 2 Comprehensive Agreement States.
The demonstration of an ADS-C Common Service to collect and distribute ADS-C data from flights has been achieved by SESAR PJ38 (ADSCENSIO). The SESAR PJ38 deliverable identified operational needs and benefits of such an ADS-C Common Service.
The SWIM ADS-C Ground Distribution Service shall be implemented over a Technical Infrastructure conformant with the SWIM-TI Yellow Profile (v1.1+) Infrastructure Capabilities Specification. Conformance with the SWIM-TI Yellow Profile Infrastructure Capabilities Specification is achieved by satisfying the requirements of the Infrastructure Capabilities of the SWIM-TI Yellow Profile (v1.1+)
The ADS-C Ground Distribution Service enables a number of operational use cases that are described in the EUROCONTROL Specification for Data Link Ground Distribution SWIM Services: Subscribe to ADS-C Messages by Specific ICAO 24-bit Aircraft Addresses. Subscribe to ADS-C Messages matching a Filter Condition. Receive Messages from Predefined Subscriptions. Enables consumer to perform a Demand Contract Request. Enables a consumer to query Flight Status details about a flight. ADS-C Ground Distribution Service Status Monitoring.
The service consumer shall be able to subscribe to a specific list of aircraft identified by their ICAO 24-bit aircraft address.
The service consumer shall be able to subscribe to a list of flight matching a filter condition.
The service consumer shall be able to receive a number of predefined subscriptions which are readily available without requiring the establishment of a specific filter. The specific set of predefined subscriptions and their filters is left as an implementation option.
The service consumer shall be able to perform a demand contract request to the ADS-C Ground Distribution Service. The demand contract request is processed by the ADS-C Common Service and, if successful, relayed via the ATN network to the aircraft.
The service consumer shall be able to query the following details about a flight: ICAO 24-bit aircraft address, Status, Last Report, Periodic and Event Contract settings.
The service consumer shall be able to receive technical messages about the status and health of the service.
The service shall ensure consumer authentication in accordance with EUROCONTROL Specification for SWIM Technical Infrastructure (TI) Yellow Profile requirement SWIM-TIYP-0042 (use of a X.509 certificate). The service shall ensure provider authentication in accordance with EUROCONTROL Specification for SWIM Technical Infrastructure (TI) Yellow Profile requirement SWIM-TIYP-0042 (use of a X.509 certificate).
The service shall ensure that satisfactory authorisation is put in place according to EUROCONTROL Specification for SWIM Technical Infrastructure (TI) Yellow Profile requirement SWIM-TIYP-0070. The specific details of the authorization verification are left as an implementation choice for the service provider, they could include aspects like: Number of active contract requests by the consumer, Number of pending contract requests by the consumer, Consumer permissions.
The service shall ensure point-to-point confidentiality in accordance with EUROCONTROL Specification for SWIM Technical Infrastructure (TI) Yellow Profile through the use of Transport Layer Security (TLS) 1.2 or above.
The service shall ensure point-to-point integrity in accordance with EUROCONTROL Specification for SWIM Technical Infrastructure (TI) Yellow Profile through the use of Transport Layer Security (TLS) 1.2 or above.
The service shall achieve a quality that is sufficient to ensure the service is fit for purpose.
The service shall achieve a quality that is sufficient to ensure the service is fit for purpose.
The service shall achieve a quality that is sufficient to ensure the service is fit for purpose.
The service shall achieve a quality that is sufficient to ensure the service is fit for purpose.
The service shall ensure confidentiality by using SWIM Technical Infrastructure (TI) Yellow Profile bindings.
The service shall ensure integrity by using SWIM Technical Infrastructure (TI) Yellow Profile bindings.
The information offered by the service shall be verified by the service provider. The information offered by the service shall be encoded according to the rules of the AIRM standard.
Air Navigation Service Provider
Aircraft Operator
Application Programmable Interface
Air Traffic Management
Aeronautical Telecommunication(s) Network
Air Traffic Services Baseline 2
Current Data Authority
Context Management
Common Project 1
Data Link Initiation Capability
European Union Aviation Safety Agency
European Commission
Extended Projected Profile
European Organisation for Civil Aviation Equipment
General Air Traffic
Ground Distribution Service Specification
International Civil Aviation Organization
Interface Control Document
Log-On Forwarding message (OLDI)
Logon Service
Next Authority Notified message
Next Data Authority
Network Manager
On-Line Data Interchange
Simple Authentication and Security Layer
Single European Sky
System Wide Information Management
Technical Infrastructure
Universally Unique Identifier version 4
VHF Digital Link Mode 2
Web Services
Extensible Markup Language
XML Schema Definition
The following interfaces shall allow for the selection of subscription based on clearly defined criteria: Flight Status Subscription Management Interface, Subscription Management Interface. Subscription and AMQP 1.0 message filtering can be done based on the value of this "application-property" using the "APACHE.ORG:SELECTOR" syntax. The service may support other filters based on the operators defined in the OGC Filter Encoding 2.0 Encoding Standard on a case by case basis.
A service monitoring mechanism shall be made available to service consumers. The Service Status Monitoring Interface covers the Service Monitoring requirement.
The service behaviour shall be in accordance with the patterns detailed in the Message Exchange Patterns: Identification Guidelines. The service behaviour is completely described in the EUROCONTROL Specification for Data Link Ground Distribution SWIM Services in chapter 5 containing all sequence diagrams for each interfaces of the service.
The Demand Contract Request Interface allows a consumer of the SWIM ADS-C Ground Distribution Service to request the creation of a demand contract with a specific aircraft.
The Demand Contract Request Interface allows a consumer of the SWIM ADS-C Ground Distribution Service to request the creation of a demand contract with a specific aircraft. The Consumer receives a "demandContractReply" confirming the Demand Contract Request has been delivered.
The WS Light Interface Binding as detailed in the EUROCONTROL Specification for SWIM Technical Infrastructure Yellow Profile, edition 1.1.
The service shall use the network bindings of the SWIM Technical Infrastructure (TI) Yellow Profile.
The Service Status Monitoring Interface allows a consumer to retrieve updates of the SWIM ADS-C Ground Distribution Service health and operational status.
This operation allows the interface consumer to retrieve updates of the SWIM ADS-C Ground Distribution Service health and operational status.
The WS Light Interface Binding as detailed in the EUROCONTROL Specification for SWIM Technical Infrastructure Yellow Profile, edition 1.1.
The Service Status Monitoring Interface shall be conformant with the SWIM-TI Yellow Profile (v1.1+) Network Interface Bindings Specification.
The Flight Status Interface allows a consumer of the SWIM ADS-C Ground Distribution Service to query: The ICAO 24-bit aircraft address based on the information available to the ADS-C Common Service based on the logon information received, The flight status of the aircraft, The last report of the aircraft.
The Flight Status Interface allows a consumer of the SWIM ADS-C Ground Distribution Service to query the ICAO 24-bit aircraft address based on the information available to the ADS-C Common Service based on the logon information received.
The Flight Status Interface allows a consumer of the SWIM ADS-C Ground Distribution Service to query the flight status of the aircraft.
The Flight Status Interface allows a consumer of the SWIM ADS-C Ground Distribution Service to query the last report of the aircraft.
The Flight Status Interface allows a consumer of the SWIM ADS-C Ground Distribution Service to query the last demand report of the aircraft.
The Flight Status Interface allows a consumer of the SWIM ADS-C Ground Distribution Service to query the last event report of the aircraft.
The Flight Status Interface allows a consumer of the SWIM ADS-C Ground Distribution Service to query the last periodic report of the aircraft.
The Flight Status Interface allows a consumer of the SWIM ADS-C Ground Distribution Service to query the contract settings of the aircraft.
The service shall use the network bindings of the SWIM Technical Infrastructure (TI) Yellow Profile.
The Flight Status Subscription Management Interface allows a consumer of the SWIM ADS-C Ground Distribution Service to subscribe to flight status changes he is interested in to receive via the Flight Status Data Publication Interface.
This operation allows a consumer of the SWIM ADS-C Ground Distribution Service to subscribe to flight status changes he is interested in to receive, via the Flight Status Data Publication Interface.
This operation allows a service consumer to unsubscribe from the flight status changes he is subscribed to.
This operation allows a service consumer to obtain the list of subscriptions.
This operation allows a service consumer to obtain information on a specific subscriptions.
The service shall use the network bindings of the SWIM Technical Infrastructure (TI) Yellow Profile.
The Flight Status Data Publication Interface allows a consumer to obtain updates of the ADS-C exchanges of the flights he is interested in. It provides two ways of doing so: By creating an endpoint from which a consumer can listen to updates of flights matching certain filtering criteria defined in a subscription created through the Flight Status Subscription Management Interface. In which case he will receive in its subscription response the endpoint address created specifically for his subscription. The dynamic endpoint created for a specific subscription is labelled by /<address> in this document, the specific value taken by the <address> placeholder is resolved in runtime and provided in the subscription response. By defining a number of preconfigured static endpoints where predefined filters are already applied. These preconfigured static endpoints do not require the creation of a specific subscription by the consumer, they are created in design-time by the service provider and are readily available for any consumer, subject to authorization verification. These static endpoints are labelled by /<predefinedSubscription> in this document, the specific values taken by these endpoints is defined by the service provider during design-time.
This operation allows the service provider to publish flight status updates to service consumers based on their subscriptions. By creating an endpoint from which a consumer can listen to updates of flights matching certain filtering criteria defined in a subscription created through the Flight Status Subscription Management Interface. In which case he will receive in its subscription response the endpoint address created specifically for his subscription. The dynamic endpoint created for a specific subscription is labelled by /<address> in this document, the specific value taken by the <address> placeholder is resolved in runtime and provided in the subscription response.
By defining a number of preconfigured static endpoints where predefined filters are already applied. These preconfigured static endpoints do not require the creation of a specific subscription by the consumer, they are created in design-time by the service provider and are readily available for any consumer, subject to authorization verification. These static endpoints are labelled by /<predefinedSubscription> in this document, the specific values taken by these endpoints is defined by the service provider during design-time.
The AMQP_MESSAGING Interface Binding as detailed in the EUROCONTROL Specification for SWIM Technical Infrastructure Yellow Profile, edition 1.1
The service shall use the network bindings of the SWIM TIYP. AMQP 1.0 shall be used to distribute messages as explained in the Publish/Subscribe Push MEP: Implementation Guidance: https://reference.swim.aero/technical-infrastructure/guidance-for-pub-s…
The Subscription Management Interface allows a consumer of the SWIM ADS-C Ground Distribution Service to select the set of datalink messages he is interested to receive via the Data Publication Interface.
This operation allows a consumer of the SWIM ADS-C Ground Distribution Service to select the set of datalink messages he is interested to receive via the Data Publication Interface.
This operation allows a service consumer to unsubscribe from the set of datalink messages changes he is subscribed to.
This operation allows a service consumer to obtain the list of subscriptions.
This operation allows a service consumer to obtain information on a specific subscriptions.
The service shall use the network bindings of the SWIM Technical Infrastructure (TI) Yellow Profile.
The Data Publication Interface allows a consumer to obtain updates of the ADS-C exchanges of the flights he is interested in. It provides two ways of doing so: By creating an endpoint from which a consumer can listen to updates of flights matching certain filtering criteria defined in a subscription created through the Subscription Management Interface. In which case he will receive in its subscription response the endpoint address created specifically for his subscription. The dynamic endpoint created for a specific subscription is labelled by /<address> in this document, the specific value taken by the <address> placeholder is resolved in runtime and provided in the subscription response. By defining a number of preconfigured static endpoints where predefined filters are already applied. These preconfigured static endpoints do not require the creation of a specific subscription by the consumer, they are created in design-time by the service provider and are readily available for any consumer, subject to authorization verification. These static endpoints are labelled by /<predefinedSubscription> in this document, the specific values taken by these endpoints is defined by the service provider during design-time.
This operation allows the service provider to publish flight status updates to service consumers based on their subscriptions. By creating an endpoint from which a consumer can listen to updates of flights matching certain filtering criteria defined in a subscription created through the Flight Status Subscription Management Interface. In which case he will receive in its subscription response the endpoint address created specifically for his subscription. The dynamic endpoint created for a specific subscription is labelled by /<address> in this document, the specific value taken by the <address> placeholder is resolved in runtime and provided in the subscription response.
By defining a number of preconfigured static endpoints where predefined filters are already applied. These preconfigured static endpoints do not require the creation of a specific subscription by the consumer, they are created in design-time by the service provider and are readily available for any consumer, subject to authorization verification. These static endpoints are labelled by /<predefinedSubscription> in this document, the specific values taken by these endpoints is defined by the service provider during design-time.
The AMQP_MESSAGING Interface Binding as detailed in the EUROCONTROL Specification for SWIM Technical Infrastructure Yellow Profile, edition 1.1
The service shall use the network bindings of the SWIM TIYP. AMQP 1.0 shall be used to distribute messages as explained in the Publish/Subscribe Push MEP: Implementation Guidance: https://reference.swim.aero/technical-infrastructure/guidance-for-pub-s…
This specification contains requirements for the ground implementation of data link common services for the Aeronautical Telecommunications Network (ATN) as defined by ICAO Annex 10 (Volume III, Part 1) https://www.eurocontrol.int/publication/eurocontrol-specification-data-… - 11/12/23
This specification contains requirements for service descriptions in the context of System Wide Information Management (SWIM) in Europe. https://www.eurocontrol.int/publication/eurocontrol-specification-swim-… - 15/03/22
The EUROCONTROL Specification for SWIM Information Definition contains requirements for information definitions in the context of iSWIM in Europe. https://www.eurocontrol.int/publication/eurocontrol-specification-swim-… - 01/12/17
The EUROCONTROL Specification for SWIM Technical Infrastructure Yellow Profile 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 iSWIM. This contributes to technical interoperability. https://www.eurocontrol.int/publication/eurocontrol-specification-swim-… 05/07/20
Aircraft can provide essential information to support accurate and reliable trajectory prediction or alternative scenarios during the execution of a flight. The EU-funded PJ38-W3-ADSCENSIO project will improve several characteristics of air traffic control through the better prediction of flightsâ behaviour. The project demonstrated the improvements in several operations performed by air traffic controllers as well as the efficiency and strength of a technological infrastructure to support the data link communications between the aircraft and ground on trajectory-related exchanges. The adoption of technical and operational solutions reduced controller workload in high traffic conditions, increase airspace capacity, and reduce flight delays, fuel consumption and CO2 emissions. https://cordis.europa.eu/project/id/101017626/results 27/06/23
This standard provides the operational, safety, and performance requirements (SPR) for the implementation of data communication services that support air traffic services (ATS). https://eshop.eurocae.net/eurocae-documents-and-reports/ed-228a/# - 2016
This standard provides the operational, safety, and performance requirements (SPR) for the implementation of data communication services that support air traffic services (ATS). It is intended to support the communication element of the implementation of communication, navigation, and surveillance / air traffic management (CNS/ATM) systems in worldwide application. Revision B will take into account results from SESAR and NextGen validation exercises. It will also align the standard to relevant ICAO documentation and remove the D-RNP Requirements. https://www.eurocae.net/news/posts/2023/october/ed-228b-safety-and-perf… - 09/23
This document provides the interoperability requirements (INTEROP) standard for the implementation of the Air Traffic Service (ATS) applications supporting the Baseline 2 data link services as specified in the Baseline 2 Safety and Performance Requirements (SPR) document [10]. This document addresses the interoperability of the ATS applications using the Aeronautical Telecommunication Network (ATN). https://eshop.eurocae.net/eurocae-documents-and-reports/ed-229a/ - 01/01/2016
This document provides the interoperability requirements (INTEROP) standard for the implementation of the Air Traffic Service (ATS) applications supporting the Baseline 2 data link services as specified in the Baseline 2 Safety and Performance Requirements (SPR) document. Revision B takes into account results from SESAR and NextGen validation exercises, and maintaining portable data link services and applications independent, to the maximum extent practical, of the underlying network technology. Revision B will take into account results from SESAR and NextGen validation exercises. It will also align the standard to relevant ICAO documentation and remove the D-RNP Requirements. https://www.eurocae.net/news/posts/2023/october/ed-229b-interoperabilit… 09/23
The Advanced Message Queuing Protocol (AMQP) is an open internet protocol for business messaging. It defines a binary wire-level protocol that allows for the reliable exchange of business messages between two parties. AMQP has a layered architecture and the specification is organized as a set of parts that reflects that architecture. Part 1 defines the AMQP type system and encoding. Part 2 defines the AMQP transport layer, an efficient, binary, peer-to-peer protocol for transporting messages between two processes over a network. Part 3 defines the AMQP message format, with a concrete encoding. Part 4 defines how interactions can be grouped within atomic transactions. Part 5 defines the AMQP security layers. https://docs.oasis-open.org/amqp/core/v1.0/os/amqp-core-messaging-v1.0-… 10/12
A message exchange pattern (MEP) identifies a repeatable sequence of messages exchanged between two systems, specifying the order, direction and cardinality of these messages (e.g. Request/Reply, Publish/Subscribe). https://reference.swim.aero/technical-infrastructure/message-exchange-p… 02/07/19
The SESAR Deployment Programme provides a common workplan to all operational stakeholders involved in the deployment of Regulation (EU) n. 2021/116, so called Common Project One (CP1), clearly defining the scope of the implementation activities, the synchronisation needs, as well as the suggested deployment approach. https://assets.ctfassets.net/krj50g99u3hm/3UqsgbBqgoXAPsnTXromQ4/6b4c06…
The objective of this document is to describe the Concept of Operations (CONOPS) upon which the development of standardisation material will be prepared for the Operational Excellence Programme (OEP) workstream topic 12.2 to support implementation of the CP1 regulation [Ref 11] on ATM Functionality 6 (AF6) (Initial Trajectory Sharing). https://www.eurocontrol.int/sites/default/files/2022-10/eurocontrol-oep…
The Single European Skys ATM Research project, SESAR, is one of the most ambitious modernisation projects launched by the European Union, contributing to the implementation of the Single European Sky. SESARs goal is to define, develop and deploy the technological solutions needed to increase the performance and digitalisation of Europes ATM system in the most cost-, flight-efficient and environmentally friendly conditions. The adoption of the Reg. (EU) n. 716/2014 (Pilot Common Project or PCP), the establishment of the SESAR Deployment Manager as per Reg. (EU) n. 409/2013, as well as the subsequent elaboration of the initial SESAR Deployment Programme, marked all together a key step towards the Deployment Phase of SESAR. https://www.sesardeploymentmanager.eu/news/common-project-1-a-new-europ… 02/02/2021