EUROCONTROL
EUROCONTROL is an intergovernmental organisation with 42 Member and 2 Comprehensive Agreement States.
Digital NOTAM Subscription and Request Service 1.0.0
Abstract
The Digital NOTAM Subscription and Request Service allows the service consumer to get aeronautical information in accordance with the Digital NOTAM specification. The aeronautical information conforms to the event scenarios that are supported by Digital NOTAM such as runway closures. The service consumer may subscribe to the service, specifying the event scenarios of interest. It is also possible to send a direct request to the service to get the aeronautical information. The information returned is in the form of an AIXM 5.1.1 message. This supports the integration of the latest information into an existing aeronautical information store in the various ATM systems.
Service Type
SWIM_COMPLIANT
Abbreviation
EUROCONTROL
Life Cycle
Business Activity Type
INFORMATION_MANAGEMENT
Intended Consumer
Information Exchange Category
AERONAUTICAL_INFORMATION_EXCHANGE
Application Message Exchange Pattern Entity
ICAO Region
Worldwide
Geospatial Categorisation Description
Worldwide
In-Operation Date
15-May-2025
Provider
Provider Type
AERONAUTICAL_INFORMATION_SERVICE_PROVIDER
Point of Contact
General
Operational Needs
Air traffic management is defined by ICAO as the "dynamic, integrated management of air traffic and airspace including air traffic services, airspace management and air traffic flow management - safely, economically and efficiently - through the provision of facilities and seamless services in collaboration with all parties and involving airborne and ground-based functions". Stakeholders involved in air traffic management need aeronautical data concerning the establishment, condition or change in any aeronautical facility, service, procedure or hazard, the timely knowledge of which is essential for flight operations. This service satisfies this need by allowing clients to subscribe to event scenarios and to be notified when the aeronautical data described in the event scenario is affected. The aeronautical data can be used, e.g., in pre-flight information bulletins. It can also be used to improve decision making thus positively impacting the efficiency of their planning and flight executions, enabled through automatic data verification and graphical visualisation. The aeronautical data is also used in other systems such as those used for airspace reservations (ARES). A list of these is available in Appendix C. This service satisfies this need by offering the aeronautical data (in the form of event features) as regulated by ICAO Annex 15 - Aeronautical Information Services. The scope covers the event encodings outlined in the Digital NOTAM Specification including aerodrome data for the 18 airports listed in EU Implementing Regulation 2021/116 - Common Project One.
IER 1 - Digital NOTAM Exchange (A3SG-IER-05) (A3SG-IER-05 Digital NOTAM Data Exchange - Aeronautical SWIM Services - SWIM Confluence (atlassian.net))
Capabilities
The service offers subscription and request capabilities to distribute aeronautical data based on event scenarios.
Functionality
The system provides Publish-Subscribe functionality for service consumers to subscribe/unsubscribe to receive Digital NOTAMs using filtering criteria:
- event scenario(s)
- series
- Digital NOTAM publisher(s)
- event scenario provider(s)
- aeronautical feature(s)
-- aerodrome(s)
-- airspace(s)
When new Digital NOTAM is generated, the system distributes the message containing Digital NOTAM in AIXM 5.1.1 format to subscribed service consumers according to the stored subscription filters.
The service consumer is able to request aeronautical information in the form of a Digital NOTAM through WFS GetFeature query.
Access and Use
In order to be able to access and use Digital NOTAM Subscription and Request Service, Consumers need to become clients and sign the Client Agreement.
More in detail:
1. the data consumer has to register as a Data User or Commercial User Client,
2. the Organisation of the Data Consumer requires an AIMSL (B2B) license,
3. the Data Consumer user requires an EACP (European Aviation Common PKI) user certificate for authentication/authorisation purposes,
4. the Data Consumer user has to be able to use Publish-Subscribe message exchange pattern implemented using REST (Subscription management interfaces) and AMQP 1.0 (Distribution), and WFS.
The service consumers may use data in order to integrate it in data products or facilitate their operations. Reselling data is prohibited.
Customers can be negatively impacted when data usage is disproportionate and for extended periods. As protection mechanism, Digital NOTAM Subscription and Request Service will restrict excessive requests originated from the same client.
The authentication requires all users to sign the requests using an X.509 certificate.
In order to consume the services, the Data Consumer user must have the appropriate user roles corresponding to the licenses allocated to their organisation. The service ensures that satisfactory authorisation is put in place according to EUROCONTROL Specification for SWIM Technical Infrastructure (TI) Yellow Profile requirement SWIM-TIYP-0070.
Quality of Service
Response Time of Digital NOTAM Subscription and Request Service Subscription Interface is less or equal to 1 second.
Response Time of Digital NOTAM Subscription and Request Service Request Interface is designed in function of the operation complexity.
- Low Complexity filter criteria in an AIS Data Query, the average response time is less or equal to 6 seconds
- Medium Complexity filter criteria in an AIS Data Query, the average response time is less or equal to 9 seconds
- High Complexity filter criteria in an AIS Data Query, the average response time is less or equal to 22.5 seconds
- Very High Complexity filter criteria in an AIS Data Query, the average response time is less or equal to 75 seconds
- Low complexity query parameters:
-- (Dynamic) Feature Filter
--- Validity - validTime
--- Identifier
--- ADMExtension.DataSource
--- Interpretation
--- NaturalDescriptorExtension
-- Time slice Projection
--- relevantTime
--- Interpretation
- Medium complexity query parameters:
-- Any combination of Low complexity filter conditions and
-- (Dynamic) Feature Filter
--- By Feature time slice Simple Properties
-- Time slice Projection
--- By Feature time slice Simple Properties
- High complexity query parameters:
-- Any combination of filter conditions with:
--- Low complexity
--- Medium complexity and
-- (Dynamic)Feature Filter
--- By Feature time slice complex properties
--- One Spatial Filter Condition
-- Time slice Projection
--- By Feature time slice complex properties
- Very high complexity query parameters:
-- Any combination of filter conditions with:
--- Low complexity
--- Medium complexity
--- High complexity and
-- (Dynamic)Feature Filter
--- multiple Spatial Filter Condition
The throughput of the service has a capacity of 22000 WFS requests per work day an 2000 subscription requests per work day (to be updated).
The availability of the service is at least 99,975%.
The unplanned unavailability of the services shall not exceed 30 minutes (RTO = 30 minutes). In case of incidents the service ensures that no data is lost (RPO = 15) followed by operational procedures to recover potential data losses.
The service ensures confidentiality by using SWIM Technical Infrastructure (TI) Yellow Profile bindings.
The service ensures integrity by using SWIM Technical Infrastructure (TI) Yellow Profile bindings. Data integrity is ensured by the mTLS (which is based on TLS v1.2).
Validation
Service Support
Abbreviations
AIS Data Maintenance
Aeronautical Information Management
AIM Service Layer
Aeronautical Information Publication
Aeronautical Information Service
Aeronautical Information Service Provider
Aeronautical Information Exchange Model
Advanced Message Queuing Protocol
Airspace Reservation
Air Traffic Management
Business to Business
Create, Read, Update, Delete
European Union Aviation Safety Agency
Enhanced European AIS Database
EAD Service/System Information
Factory Acceptance Testing
Filter Encoding Standard
Hypertext Transport Protocol
Secure HTTP
International Civil Aviation Organization
Interface Control Document
Information Exchange Requirements
Message Exchange Pattern
Mutual TLS
Notice To Air Missions
Open Geospatial Consortium
Representational State Transfer
Simple Authentication and Security Layer
Single European Sky ATM Research
Site Acceptance Testing
Static and Dynamic Data (eEAD)
System Quality Testing
System-Wide Information Management
Technical Infrastructure
Transport Layer Security
Uniform Resource Locator
Web Feature Service
Web Feature Service - Temporality Extension
Web Service
Extensible Markup Language
Information
Information Definition
The service shall expose the event scenarios found in Appendix B. These reflect the Digital NOTAM Specification.
The event scenarios use features that are in the Aeronautical Information Exchange Model (AIXM) 5.1.1 and the AIXM Event Extension.
The AIXMBasicMessage that is returned by the service shall contain an event feature and the related AIXM features and time slices.
https://aixm.aero/page/aixm-51-511
Filtering
The Digital NOTAM Subscription and Request Service Subscription Interface allows for the selection of event scenarios of interest based on these filtering criteria:
- event scenario(s)
- series
- Digital NOTAM publisher(s)
- event scenario provider(s)
- aeronautical feature(s)
-- aerodrome(s)
-- airspace(s)
The considerations given in the General Principles for the Digital NOTAM will help AISP organise the event scenarios.
The Digital NOTAM Subscription and Request Service Request Interface shall support filtering based on the operators defined in the OGC Filter Encoding 2.0 Encoding Standard. The temporal extension (WFS-TE) shall be used to support advanced temporal filtering.
Temporal filters based on WFS-TE supporting the following temporality use cases: 3,4,6,7,8.
Source of Information
The service provider ensures that the aeronautical data offered by the services is received from the appropriate authorised originating sources. This includes:
- AIRPORT_OPERATOR,
- CIVIL_AIR_NAVIGATION_SERVICE_PROVIDER,
- MILITARY_AIR_NAVIGATION_SERVICE_PROVIDER,
- AIR_TRAFFIC_SERVICE_PROVIDER,
- AERONAUTICAL_INFORMATION_SERVICE_PROVIDER,
- COMMUNICATION_NAVIGATION_AND_SURVEILLANCE_SERVICE_PROVIDER,
- AIRSIDE_GROUND_HANDLER,
- Owners of Obstacles.
- AIRPORT_OPERATOR,
- CIVIL_AIR_NAVIGATION_SERVICE_PROVIDER,
- MILITARY_AIR_NAVIGATION_SERVICE_PROVIDER,
- AIR_TRAFFIC_SERVICE_PROVIDER,
- AERONAUTICAL_INFORMATION_SERVICE_PROVIDER,
- COMMUNICATION_NAVIGATION_AND_SURVEILLANCE_SERVICE_PROVIDER,
- AIRSIDE_GROUND_HANDLER,
- Owners of Obstacles.
Technical
Technical Constraint
Service consumer can create new subscription and link it to existing AMQP Queue that was created with previous subscription, in case both subscriptions are created for the same business topic. Queue name is generated by the system and is returned in Subscription reply message.
AMQP Queue Name convention/pattern is:
DNOTAM.<service version>.<user id>.<uuid>
Service consumer is responsible for building correct subscription filters within subscription request messages. The system allows service consumer to create multiple subscription with same filter.
Service Monitoring
A service monitoring mechanism will be made available to service consumers.
Behaviour
The service behaviour is in accordance with the patterns detailed in Message Exchange Patterns: Identification Guidelines. A combination of an AMQP 1.0 implementation and an OGC Web Feature Service 2.0 Interface Standard implementation is used.
Regarding message exchange patterns the service consists of
- SYNCHRONOUS_REQUEST_REPLY - RESTful interfaces handle the subscription and request for Digital NOTAM
- BROKERED_PUBLISH_SUBSCRIBE_WITH_PUSH_MECHANISM - an AMQP 1.0 implementation handles the distribution of the messages
The behaviour of Digital NOTAM Subscription and Request Service Subscription Interface under normal conditions:
- The service consumer sends RESTful request message to subscribe (subscription request contains valid filter)
- The service consumer remains blocked while awaiting the reply
- The service remains blocked while processing the reply
- The service sends response message with AMQP Queue name and subscription status to the service consumer (subscription is by default created with status "PAUSED", i.e. subscription will not receive any Digital NOTAM messages yet)
- The service consumer sends RESTful request message to activate subscription
- The service consumer remains blocked while awaiting the reply
- The service remains blocked while processing the reply
- The service sends response message to the service consumer, informing about subscription status change
The behaviour of Digital NOTAM Subscription and Request Service Distribution Interface under normal conditions:
- event scenario is triggered, this causes change of aeronautical data in the system
- the system generates Digital NOTAM message
- the system distributes the message to AMQP Queues based on subscriptions and their stored filters (handled by AMQP Message Broker)
- the service consumer connects to their AMQP Queue and consumes the message
- the service consumer sends acknowledgement to AMQP Message Broker, the message is removed from the queue
The behaviour of Digital NOTAM Subscription and Request Service Request Interface under normal conditions:
- The service consumer sends RESTful request message with WFS GetFeature query
- The service consumer remains blocked while awaiting the reply
- The service remains blocked while processing the reply
- The service sends response message with data.
Implementation of BROKERED_PUBLISH_SUBSCRIBE_WITH_PUSH_MECHANISM using AMQP 1.0 protocol uses technical messages to inform the service consumer about:
- creation, update or deletion of subscription
All RESTful responses provide feedback of type information, warning or error depending on the execution success.
The complete list of the response feedback is available in the ADM XML Primer document, appendix A.2 Error, info and warning messages supported by SDD.
Interfaces
Allows the service consumer to select and subscribe to event scenarios of interest. It allows the service consumer to manage the subscriptions e.g. to pause a subscription, or to unsubscribe.
Operations
This operation allows a service consumer to subscribe to event scenarios of interest.
Idempotent
IDEMPOTENT
Operation Message
Binding Method
SWIM_TI_YP_1_1_WS_LIGHT
This operation allows a service consumer to unsubscribe from event scenarios of interest.
Idempotent
IDEMPOTENT
Operation Message
Binding Method
SWIM_TI_YP_1_1_WS_LIGHT
Parameter
This operation allows a service consumer to pause the subscription for a particular topic subscription.
Idempotent
IDEMPOTENT
Operation Message
Binding Method
SWIM_TI_YP_1_1_WS_LIGHT
Parameter
This operation allows a service consumer to resume a subscription that had been paused.
Idempotent
IDEMPOTENT
Operation Message
Binding Method
SWIM_TI_YP_1_1_WS_LIGHT
Parameter
This operation allows a service consumer to obtain the list of subscriptions.
Idempotent
IDEMPOTENT
Operation Message
Binding Method
SWIM_TI_YP_1_1_WS_LIGHT
Parameter
This operation allows a service consumer to obtain information on a specific subscription.
Idempotent
IDEMPOTENT
Operation Message
Binding Method
SWIM_TI_YP_1_1_WS_LIGHT
Parameter
This operation allows a service consumer to request the list of topics (which represent type of data, i.e. SWIM services) available for subscription
Idempotent
IDEMPOTENT
Operation Message
Binding Method
SWIM_TI_YP_1_1_WS_LIGHT
This operation allows a service consumer to obtain information on a specific topic (filter criteria).
Idempotent
IDEMPOTENT
Operation Message
Binding Method
SWIM_TI_YP_1_1_WS_LIGHT
Parameter
Endpoints
Endpoint subscriptions is used for subscription management:
- creation of new subscription
- pause existing subscription
- resume existing subscription
- unsubscription/deletion of existing subscription
- get subscriptions
- get subscription details
Url
URL:/swim/v1/subscriptions/
Reference
In SWIM compliant implementation of Publish-Subscribe message exchange pattern using AMQP 1.0 protocol, the term topic is used to define service (i.e. type of data) that the future service consumer is allowed to subscribe to.
Endpoint topics is used to get:
- list of all topics
- topic details
Url
URL:/swim/v1/topics/
Reference
Service Interface Binding
The web service is bound to the REST architectural style.
Network Interface Binding
SWIM TI Yellow Profile specification
Messages
Allows the service provider to distributes Digital NOTAM Messages based on the event scenario that has triggered the need for the service consumer to be updated.
Operations
This operation allows the service provider to publish Digital NOTAM messages to service consumers based on their subscriptions. Implementation is handled through AMQP 1.0 protocol and the published message is distributed to service consumers through AMQP Queues.
Idempotent
IDEMPOTENT
Binding Method
SWIM_TI_YP_1_1_AMQP_MESSAGING
Endpoints
Endpoint is AMQP 1.0 Queue in AMQP Message Broker. Each subscription is linked to one queue, and queue name is returned in subscription response. Queue enables guaranteed messaging, that means message is kept in the queue until message consumer sends acknowledgment. Only then message is removed from the queue.
Service consumer shall be able to connect to AMQP Message Broker.
Resource Type
URL
Url
url:withheld
Reference
Service Interface Binding
The web service is bound to the AMQP 1.0 messaging protocol.
Network Interface Binding
SWIM TI Yellow Profile specification
Allows the service consumer to request an AIXM Basic Message based on filters which are linked to the event feature.
Operations
The GetFeature operation returns a selection of features from a data store.
Idempotent
IDEMPOTENT
Operation Message
Binding Method
SWIM_TI_YP_1_1_WS_LIGHT
Endpoints
Endpoint for Digital NOTAM Subscription and Request Service Request Interface is RESTful Request-Reply interface WFS.
Url
URL:/swim/wfs/5.1.1/
Reference
Service Interface Binding
EUROCONTROL Specification for SWIM Technical Infrastructure (TI) Yellow Profile
Network Interface Binding
SWIM TI Yellow Profile specification
Messages
References
Service Documents
Implemented Standards
The information scope offered by the service supports the requirements of the Digital NOTAM Specification.
This International Standard specifies the behaviour of a service that provides transactions on and access to geographic features in a manner independent of the underlying data store. It specifies discovery operations, query operations, locking operations, transaction operations and operations to manage stored parameterized query expressions.
The temporality extension has been developed in order to align the OGC WFS 2.0 and FES 2.0 standards with the AIXM 5.1.1 Temporality Concept. It allows retrieving data in AIXM 5.1.1 format via OGC WFS 2.0 requests.
Extensible Markup Language (XML) is a markup language and file format for storing, transmitting, and reconstructing arbitrary data. It defines a set of rules for encoding documents in a format that is both human-readable and machine-readable.
Revision Save Date
Mon, 05/26/2025 - 13:44
Schema version
v2