service definitions

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 35 Next »

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-010Service 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-020Service definition languageThe 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

DRAFT


service definition identification

title

Service Definition for the Digital NOTAM Subscription and Request Service

edition

00.00.01

reference date

2023-02-09

Service Identification

DRAFT


service identification

service name

Digital NOTAM Subscription and Request Service

Service Abstract

DRAFT



service abstractThe Digital NOTAM Subscription and Request Service allows the service consumer to get aeronuatical 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 in which it is interested. 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 the various ATM systems.

Service Definition Provider

DRAFT


service definition provider

nameEUROCONTROL
abbreviated name
descriptionEUROCONTROL is an intergovernmental organisation with 41 Member and 2 Comprehensive Agreement States.

Geographical Extent of Information

DRAFT


geographical extent of information

Service Categories

DRAFT


service categories





category category name

regulated information exchange

value

AERONAUTICAL_INFORMATION_EXCHANGE

scheme

http://reference.swim.aero/information-services/service-categories/CodeRegulatedInformationExchangeType.html 

categorycategory nameinformation domain
valueAERONAUTICAL_INFORMATION
schemehttps://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
scheme

http://reference.swim.aero/information-services/service-categories/CodeStakeholderType.html 

category category nameintended service provider
valueAERONAUTICAL_INFORMATION_SERVICE_PROVIDER
schemehttp://reference.swim.aero/information-services/service-categories/CodeStakeholderType.html 
categorycategory nameservice type
valueAERONAUTICAL_INFORMATION_SUBSCRIPTION_SERVICE
scheme

http://reference.swim.aero/information-services/service-categories/CodeServiceType

(for the moment use https://ext.eurocontrol.int/swim_confluence/display/SCOI/Service+Categories+-+Service+Type).

categorycategory nameservice type
valueAERONAUTICAL_FEATURE_ACCESS_SERVICE
scheme

http://reference.swim.aero/information-services/service-categories/CodeServiceType

(for the moment use https://ext.eurocontrol.int/swim_confluence/display/SCOI/Service+Categories+-+Service+Type).

Service Standard Reference

DRAFT


service standard reference



referenceDigital NOTAM Specification (https://ext.eurocontrol.int/aixm_confluence/display/DNOTAM/Overview)
implemented optionsThe information scope offered by the service supports the requirements of the Digital NOTAM Specification.
deviations/additions

Operational Environment

DRAFT

operational environmentoperational needs

Air traffic management is defined 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". It is provided by the air traffic management system that, amongst other things, relies on the collaborative integration of information and services.

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 be notified when such aeronautical events occur.

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, enabling 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 complete list of these is available as a High level description of the service offer.

This service satisfies this need by offering 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 EUROCONTROL Digital NOTAM Specification 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. 

information exchange requirements

Service Functions

DRAFT

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


functionnamesubscription

descriptionThere shall be a mechanism to subscribe/unsubscribe
real-world effectService consumer subscribes to topics offered by the service.
functionnametopic selection
descriptionThere shall be filtering mechanisms to only subscribe to specific contents.
real-world effect
functionnamenotification
descriptionWhen new data is available, it shall be distributed to the subscribers.
real-world effectService consumer is notified when a change happens to a topic of interest.
functionnamecheck notification list
descriptionThere shall be a mechanism by which a given subscriber can check if he has received all sent notifications.
real-world effectService consumer has an understanding of the notifications.
functionnamerequest notification reissue
descriptionThere shall be a mechanism by which a subscriber requests a notification reissue (due to not reception, lose, etc.)
real-world effectService consumer receives a notification.

Service Access and Use Conditions

DRAFT


service access and use conditions



legal constraints



service policies

business policy


operational policy


technical policy


service consumption constraints



Security Constraints

DRAFT


security constraints



authentication

The service may offer unauthenticated/public use.

It shall ensure provider authentication in accordance with SWIM TIYP through X.509 certificate.

It shall ensure consumer authentication in accordance with SWIM TIYP through X.509 certificate or the use of a username/password (SASL).

authorisation

The service shall ensure that satisfactory authorisation is put in place according to SWIM-TIYP-0070.

confidentiality

The service ensures point-to-point confidentiality in accordance with SWIM TIYP through Transport Layer Security (TLS) 1.2 or above.

integrity

The service ensures point-to-point integrity in accordance with SWIM TIYP through Transport Layer Security (TLS) 1.2 or above.

Quality of Service

DRAFT


quality of service

performance

capacity


response time
reliability

availability


recoverabilityreliable enough to meet the user needs to be informed of hazards...
security

confidentiality

Confidentiality shall be shall be ensured using SWIM TIYP  bindings.

integrityIntegrity shall be shall be ensured using SWIM TIYP  bindings.

Quality of Data

DRAFT


quality of data

Source of Information

DRAFT


Service Validation Information

DRAFT


service validation information

prototyping

Application Message Exchange Pattern

DRAFT


application message exchange pattern

Service Behaviour

DRAFT


service behaviour

typical behaviour
The service behaviour is in accordance with the patterns detailed in Message Exchange Patterns: Identification Guidelines. The two interfaces have different behaviours.

PUBLISH_SUBSCRIBE

  • A request-reply handles the subscription.
  • An implementation of AMQP 1.0 handles the publication.

SYNCHRONOUS_REQUEST_REPLY

The OGC Web Feature Service 2.0 Interface Standard defines the basic behaviour.

Synchronous Request/Reply
  • The request message is sent from the service consumer to the service
  • The service consumer remains blocked while awaiting the reply
  • The service remains blocked while processing the reply
  • The AIXM Basic Message, the reply message, is sent from the service to the service consumer.

Service Monitoring

DRAFT


service monitoring

A service monitoring mechanism shall be made available to service consumers.

Service Interfaces

DRAFT


service interfaces

interfacename

Subscription


description



provider/consumer side
interfacenameDistribution
descriptionPushes messagees
provider/consumer side
interfacenameRequest Digital NOTAM qualified Event feature
description- builds AIXM Basic Message based on filters which are linked to the event feature.
provider/consumer side

SWIM TI Profile and Interface Bindings

DRAFT


Working notes

SAT 2023-01-30:


This needs to be split up. Dedicated entry per interface is needed.

SWIM TI profile and interface bindings





profile name

EUROCONTROL Specification for SWIM Technical Infrastructure Yellow Profile

profile version

1.1

selected service interface binding
selected network interface bindingShall use the network bindings of the SWIM TIYP. See 3.1.2 for the options: IPV4, etc.
supported optional requirements

PUBLISH_SUBSCRIBE

AMQP 1.0 is used to publish messages in the service's publish-subscribe implementation. This is explained in: https://reference.swim.aero/technical-infrastructure/guidance-for-pub-sub-push-implementation.html

SYNCHRONOUS_REQUEST_REPLY

The OGC Web Feature Service 2.0 Interface Standard is used in the service's request-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

DRAFT


service interface protocols and data format





transport / messaging protocols

Shall be in accordance with SWIM TIYP: TLS1.2 or later
data format

This is captured at Service Message level (see below).

Service Operations

DRAFT


Service operations







operation


operation name

subscribe operation - see if there is a standard that gives us a list of operation names.

description


messages


operation


operation name

request

description

Event features can be queried.

messages


Service Messages

DRAFT


service messages





message

name

AIXM Basic Message

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.

typeOut
data formatAIXM 5.1.1 including the event extension
message

name


description
type
data format

Information Definition (Minimum) and (Extended)

DRAFT


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.

The AIXMBasicMessage that is returned by the service shall contain an event feature and the related AIXM features.

See

Filter Encoding

DRAFT


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

DRAFT


machine-readable service interface definition

reference

Model View

WORKING

model view

reference

Abbreviations and Acronyms

DRAFT


abbreviations and acronyms


abbreviationcodeSWIM

termSystem Wide Information Management
abbreviationcode

term
  • No labels