Task Status
This page is part of the ongoing SWIM communities of interest discussions. The content is working material. It should not be treated as final as it is still subject to review, comment and change.
Guidance
This template allows for the documentation of service definitions based on the requirements found at: /wiki/spaces/SCOI/pages/59605116
General requirements to remember:
SWIM-DEFN-010 | Service definition coverage | A service definition shall define a single service | Note: This concerns the definition of a service that can be implemented by service providers. It is not used to describe a running service - use a service description in that case. Note: This requirement uses "define" rather than "describe". |
SWIM-DEFN-020 | Service definition language | The textual descriptions in a service definition shall be written in English using the spelling listed as the primary British spelling when conflicting spellings exist. | - |
Status Key
- TBD - No work has started
- WORKING - Content is being worked on, comments discussed
- DRAFT - Draft is ready, comments resolved
- REVIEWED - Group has reviewed, edited the final draft
- AGREED - Content is finalised and agreed
Service Definition Identification
TBD
Trace
service definition identification | title | Service Definition for Aeronautical Events Service |
---|---|---|
edition | 00.00.01 | |
reference date | 2022-04-27 |
Service Identification
WORKING
Trace
service identification | service name |
|
---|
Service Abstract
TBD
Trace
service abstract | The ... 8.3.10:The main purpose of the AeronauticalInformationNotification service is to provide notifications (alerts) to consumers providing them with a simple mechanism to maintain their systems updated to the latest information available. SNOW: The SNOWTAM is special series NOTAM |
---|
Service Definition Provider
TBD
Trace
service definition provider | name | EUROCONTROL |
---|---|---|
abbreviated name | ||
description | EUROCONTROL is an intergovernmental organisation with 41 Member and 2 Comprehensive Agreement States. |
Geographical Extent of Information
WORKING
Trace
geographical extent of information |
---|
Service Categories
WORKING
Trace
Working notes
SAT 2022-11-11:
service categories | category | category name | regulated information exchange |
---|---|---|---|
value | AERONAUTICAL_INFORMATION_EXCHANGE | ||
scheme | |||
category | category name | information domain | |
value | AERONAUTICAL_INFORMATION | ||
scheme | https://reference.swim.aero/information-services/service-categories/CodeInformationDomainType.html | ||
category | category name | business activity | |
value | INFORMATION_MANAGEMENT | ||
scheme | http://reference.swim.aero/information-services/service-categories/CodeBusinessActivityType.html | ||
category | category name | intended service consumer | |
value | CIVIL_AIRSPACE_USER, MILITARY_AIRSPACE_USER, CIVIL_AIR_NAVIGATION_SERVICE_PROVIDER, MILITARY_AIR_NAVIGATION_SERVICE_PROVIDER, AIR_TRAFFIC_SERVICE_PROVIDER, REGULATED_METEOROLOGICAL_SERVICE_PROVIDER, AERONAUTICAL_INFORMATION_SERVICE_PROVIDER, COMMUNICATION_NAVIGATION_AND_SURVEILLANCE_SERVICE_PROVIDER, PROVIDER_OF_DATA_SERVICES, NETWORK_MANAGER, AIRPORT_OPERATOR, AIRSIDE_GROUND_HANDLER, MILITARY_DEFENCE_CENTRE | ||
scheme | http://reference.swim.aero/information-services/service-categories/CodeStakeholderType.html | ||
category | category name | intended service provider | |
value | AERONAUTICAL_INFORMATION_SERVICE_PROVIDER | ||
scheme | http://reference.swim.aero/information-services/service-categories/CodeStakeholderType.html | ||
category | category name | service type | |
value | AERONAUTICAL_INFORMATION_SUBSCRIPTION_SERVICE | ||
scheme | http://reference.swim.aero/information-services/service-categories/CodeServiceType | ||
category | category name | service type | |
value | AERONAUTICAL_FEATURE_ACCESS_SERVICE | ||
scheme | http://reference.swim.aero/information-services/service-categories/CodeServiceType |
Service Standard Reference
DRAFT
Trace
service standard reference | reference | Digital NOTAM Specification (https://ext.eurocontrol.int/aixm_confluence/display/DNOTAM/Overview) |
---|---|---|
implemented options | The information scope offered by the service supports the requirements of the Digital NOTAM Specification. | |
deviations/additions |
Operational Environment
DRAFT
Trace
Working notes
SAT 2022-11-11:
Look to https://ext.eurocontrol.int/aixm_confluence/display/DNOTAM/Digital+NOTAM+Specification for scenarios that will help write the operational need.
It was agreed that this service focuses on what the AISP makes available to the next intended user. Therefore it will not cover:
These will be looked at later and in the context of a different service.
To discuss: does the term NOTAM cover SNOWTAM and ASHTAM. All of these are available in the Event Extension for AIXM.
operational environment | operational needs | 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 to personnel concerned with flight operations. This service satisfies this need by allow clients to register for notification about aeronautical events. When an event occurs, the subscription service sends notification to all clients who have registered an interest in the event. The changes notified can be used immediately - re-routings, on board navigational databases could be potentially updated on flight with new digital NOTAM messages being issued., etc. They can also be used to improve their decision making process thus positively impacting the efficiency of their planning and flight executions, enabling through automatic data verification and graphical visualisation The scope covers the event encodings including aerodrome data for the 18 airports listed in EU Implementing Regulation 2021/116 - Common Project One. |
---|---|---|
capabilities | The service offers notification in the changes to aeronautical data about features. and/or This identified service will provide structured digital aeronautical information that can be processed. | |
information exchange requirements |
Service Functions
DRAFT
Trace
Working notes
SAT 2022-11-11:
Options
- All data is pushed - PUB/SUB containing the payload.
- can also just be a notification containing a link to the data.
scenarios come from the digital NOTAM spec including aerodrome data for the 18 airports. Service providers declare which ones their service supports.
service functions | function | name | subscription |
---|---|---|---|
description | There shall be a mechanism to subscribe/unsubscribe | ||
real-world effect | Service consumer subscribes to topics offered by the service. | ||
function | name | topic selection | |
description | There shall be filtering mechanisms to only subscribe to specific contents. | ||
real-world effect | |||
function | name | notification | |
description | When new data is available, it shall be distributed to the subscribers. | ||
real-world effect | Service consumer is notified when a change happens to a topic of interest. | ||
function | name | check notification list | |
description | There shall be a mechanism by which a given subscriber can check if he has received all sent notifications. | ||
real-world effect | Service consumer has an understanding of the notifications. | ||
function | name | request notification reissue | |
description | There shall be a mechanism by which a subscriber requests a notification reissue (due to not reception, lose, etc.) | ||
real-world effect | Service consumer receives a notification. |
Service Access and Use Conditions
TBD
Trace
service access and use conditions | legal constraints | 8.3.10: one aspect that is worth mentioning is related to the legal framework for data distribution. To really achieve all benefits from digital data distribution, all aspects related to copyright, use rights of data and liabilities need to be clearly stated. | |
---|---|---|---|
service policies | business policy | TBD | |
operational policy | TBD | ||
technical policy | TBD | ||
service consumption constraints | TBD |
Security Constraints
TBD
Trace
security constraints | authentication | Consumer side authentication: TBD Provider side authentication: Authentication is required |
---|---|---|
authorisation | ||
confidentiality | ||
integrity |
Quality of Service
TBD
Trace
quality of service | performance | capacity | |
---|---|---|---|
response time | <= 1 second | ||
reliability | availability | >= 99.95 % | |
recoverability | |||
security | confidentiality | ||
integrity | >= 99.999 % |
Quality of Data
WORKING
Trace
quality of data |
|
---|
Source of Information
WORKING
Trace
source of information | source | Data is received from the appropriate authorised originating sources, e.g. 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. |
---|
Service Validation Information
TBD
Trace
service validation information | prototyping | The service was prototyped in SESAR Sol34: An initial verification exercise has focused on the provision of Digital NOTAM in a SWIM compliant manner. This has addressed data origination, collection and provision aspects in the Digital NOTAM data chain, which is a key enabler for Digital Integrated Briefing. |
---|
Application Message Exchange Pattern
WORKING
Trace
application message exchange pattern |
---|
Service Behaviour
TBD
Trace
service behaviour | typical behaviour | 8.3.10: the AeronauticalInformationNotification service will only send updates to current features properties or new features. Thus, to properly interpret the data received, it is paramount that a previous call to appropriate service operation to obtain the data is performed. The AeronauticalInformationNotification service shall expose such an operation and provide to immediately start the notifications messages after its call. So the process will look like this: The consumer subscribes, the subscription is then moved to a latency state. Then the consumer retrieves the latest available baseline data, together with currently available notifications that apply to that baseline. At that moment, new data changes will be notified, the subscription moves to an active status. Scheduled Information. ... For retrieving the full data a call to the AeronauticalFeatureService will need to be performed Digital NOTAMs... the complete data change within the notification message 8.3.10: The diagram below depicts the service dynamic behaviour of both interfaces. |
---|
Service Monitoring
TBD
Trace
service monitoring | There is no expectation that a service monitoring mechanism is made available to service consumers. |
---|
Service Interfaces
TBD
Trace
service interfaces | interface | name | 8.3.10: AINSInterfacePull implements Publish/Subscribe Pull MEP. |
---|---|---|---|
description | 8.3.10: A synchronous call to obtain specific notifications that where published in the past. | ||
provider/consumer side | |||
interface | name | 8.3.10: AINSInterfacePush implements Publish/Subscribe via Push messages. | |
description | 8.3.10: This interfaces differs from the one described above only in one way. It implements Publish/Subscribe via push notifications instead of client triggered requests. Hence the interfaces are very similar. | ||
provider/consumer side | |||
interface | name | SNOW: The SNOWTAMPublisher service interface definition allows the consumer to subscribe or unsubscribe to the data, while the SNOWTAMSubscriber service interface definition allows the service provider to publish the message containing the data. | |
description | |||
provider/consumer side |
SWIM TI Profile and Interface Bindings
WORKING
Trace
SWIM TI profile and interface bindings | profile name | EUROCONTROL Specification for SWIM Technical Infrastructure Yellow Profile |
---|---|---|
profile version | 1.1 | |
selected service interface binding | WS_LIGHT | |
selected network interface binding | ||
supported optional requirements | AMQP 1.0 is used to publish messages (for the pub-sub MEP). This is explained in: https://reference.swim.aero/technical-infrastructure/guidance-for-pub-sub-push-implementation.html The OGC Web Feature Service 2.0 Interface Standard is used in the service's reuest-reply implementation. The standardised operations for a Basic WFS are implemented. The temporal extension (WFS-TE) is used to support advanced temporal filtering. The ISO 19143 - Geographic Information - Filter encoding specification is applied for spatial and logical operators. |
Service Interface Protocols and Data Format
TBD
Trace
service interface protocols and data format | transport / messaging protocols | |
---|---|---|
data format | This is captured at Service Message level (see below). |
Service Operations
TBD
Trace
Service operations | operation | operation name | |
---|---|---|---|
description | |||
messages | |||
operation | operation name | ||
description | |||
messages |
Service Messages
WORKING
Trace
service messages | message | name | AIXM Basic Message / AeronaticalFeatureCollection |
---|---|---|---|
description | The basic messages is a collection of features. The structure is explained in the EUROCONTROL Event Encoding Specification. The message serves the purpose of Digital NOTAM. | ||
type | Out | ||
data format | AIXM 5.1.1 | ||
message | name | ||
description | |||
type | |||
data format |
Information Definition (Minimum) and (Extended)
DRAFT
Trace
information definition | The service exposes a topic tree. The topics are based on the event scenarios found in the Digital NOTAM Specification (https://ext.eurocontrol.int/aixm_confluence/display/DNOTAM/Digital+NOTAM+Specification). The scenarios use features that are in the Aeronautical Information Exchange Model (AIXM) 5.1.1 and the AIXM Event Extension. See
|
---|
Filter Encoding
WORKING
Trace
filter encoding | The request-reply service interface supports filtering based on (subset of the) the operators defined in the OGC Filter Encoding 2.0 Encoding Standard (equivalent to ISO 19143 - Geographic Information - Filter encoding). The temporal extension (WFS-TE) is used to support advanced temporal filtering. The publish-subscribe service interface allows for the selection of topics. These can be organised around e.g. a specific aerodrome or airspace. The considerations on https://ext.eurocontrol.int/aixm_confluence/display/DNOTAM/General+Principles will help AISP decide which topic an event concerns. |
---|
Machine-Readable Service Interface Definition
TBD
Trace
machine-readable service interface definition | reference |
---|
Model View
TBD
Trace
model view | reference |
---|
Abbreviations and Acronyms
TBD
Trace
abbreviations and acronyms | abbreviation | code | SWIM |
---|---|---|---|
term | System Wide Information Management | ||
abbreviation | code | ||
term |