LGS Digital NOTAM Subscription and Request Service

Abstract

LGS 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 NOTAMsuch 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.

Categorisation

Service Type

SERVICE_DESCRIPTION

Life Cycle Stage

OPERATIONAL

Business Activity Type

INFORMATION_MANAGEMENT

Intended Consumer

AIRPORT_OPERATOR
CIVIL_AIR_NAVIGATION_SERVICE_PROVIDER
CIVIL_AIRSPACE_USER
MILITARY_AIR_NAVIGATION_SERVICE_PROVIDER
MILITARY_AIRSPACE_USER
NETWORK_MANAGER
PROVIDER_OF_DATA_SERVICES

Information Exchange Category

AERONAUTICAL_INFORMATION_EXCHANGE

Application Message Exchange Pattern

SYNCHRONOUS_REQUEST_REPLY
PUBLISH_SUBSCRIBE

Geospatial Categorisation Description

Latvian FIR including delegated airspace

Provider

Latvijas gaisa satiksme

Description

Latvijas gaisa satiksme (LGS)

Latvian air navigation service provider

Type

CIVIL_AIR_NAVIGATION_SERVICE_PROVIDER

Abbreviation

LGS

Point of Contact

Restricted

Contact Information

Restricted

Name

Operational Needs

Description

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.

Name

Information Exchange Requirements

Description

IER 1 - Digital NOTAM Exchange (A3SG-IER-05) (A3SG-IER-05 Digital NOTAM Data Exchange - Aeronautical SWIM Services - SWIM Confluence (atlassian.net))

Reference

https://swim-eurocontrol.atlassian.net/wiki/spaces/ASW/pages/60031194/A3SG-IER-05+Digital+NOTAM+Data+Exchange

A3SG-IER-05 Digital NOTAM Data Exchange - Aeronautical SWIM Services - SWIM Confluence (atlassian.net)

Name

Capabilities

Description

The service offers subscription and request capabilities to distribute aeronautical data based on event scenarios.

Name

Subscribe to event scenario

Description

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)

Real World Effect

Service consumer subscribes to information offered by the service. AMQP Queue Name is returned in the subscription response.

Name

Distribution

Description

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.

Real World Effect

Service consumer receives Digital NOTAM message when a change happens based on an event scenario. Distribution mechanism is AMQP 1.0 based Publish-Subscribe using AMQP Message Broker, which handles distribution to AMQP Queues.

Name

Request a Digital NOTAM

Description

The service consumer is able to request aeronautical information in the form of a Digital NOTAM through WFS GetFeature query.

Real World Effect

The service consumer receives data.

Performance

Response time

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 4 seconds- Medium Complexity filter criteria in an AIS Data Query, the average response time is less or equal to 5 seconds- High Complexity filter criteria in an AIS Data Query, the average response time is less or equal to 6 seconds- Very High Complexity filter criteria in an AIS Data Query, the average response time is less or equal to 8 seconds- Low complexity query parameters:-- (Dynamic) Feature Filter--- Validity - validTime--- Identifier--- Interpretation-- 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
Capacity

The service is designed to support at least 1 WFS request per second and at least 10 subscription request per second under normal operating conditions.

Reliability

Availability

The availability of the service is at least 99,975%.
Recoverability

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.

Security

Confidentiality

The service ensures confidentiality by using SWIM Technical Infrastructure (TI) Yellow Profile bindings.
Integrity

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).

Access

To access and use SWIM service, consumers must: 1.Register as a client in the LGS SWIM Client Portal https://swim-ais.lgs.lv. 2. Accept the Terms and Conditions as part of the registration process. 3. Generate an API password via the portal, which will be used for authentication and authorization when requesting the service.
Policy

LGS Digital NOTAM Subscription and Request Service 1.0.0 consumers may use data in order to integrate it in data products or facilitate their operations. Reselling data is prohibited.
Fair Use

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.
Authentication

The authentication mechanism follows WS-Light binding principles. The server is authenticated using an X.509 certificate over TLS. Clients authenticate using either HTTP Basic authentication methods over HTTPS. This ensures secure communication and client identity verification.
Authorisation

In order to consume the LGS Aeronautical Information Request Service 1.0.0, the Data Consumer must have the appropriate user roles granted via the SWIM Client Portal. Access to specific service operations is determined by these roles and the associated permissions.

Name

Service Desk Contact Form and Email

Customer Service for general information and service support.

Contact Information

https://ais.lgs.lv/feedback
[email protected]

Type

SELF_VALIDATION

Validation Steps

The validation process is part of software development methodology covered in an assessment and verification management plan. Validation Steps: * SQT (Software Quality Test) / FAT (Factory Acceptance Test) dry run * FAT (Factory Acceptance Test) * SAT (Site Acceptance Test). * Statement of compliance (SoC).

Validation Results

Validation and acceptance are concluded with reports as per each validation test step.

Evidence

Validation reports are available upon request. Due to the confidentiality status of the documents a non-disclosure agreement may be required.

ADM

AIS Data Maintenance
AIS

Aeronautical Information Service
AISP

Aeronautical Information Service Provider
AIXM

Aeronautical Information Exchange Model
AMQP

Advanced Message Queuing Protocol
ARES

Airspace Reservation
ATM

Air Traffic Management
B2B

Business to Business
CRUD

Create, Read, Update, Delete
FAT

Factory Acceptance Testing
FES

Filter Encoding Standard
HTTP

Hypertext Transport Protocol
HTTPS

Secure HTTP
ICAO

International Civil Aviation Organization
ICD

Interface Control Document
IER

Information Exchange Requirements
LGS

Latvijas Gaisa Satiksme
MEP

Message Exchange Pattern
mTLS

Mutual TLS
NOTAM

Notice To Air Missions
OGC

Open Geospatial Consortium
REST

Representational State Transfer
SASL

Simple Authentication and Security Layer
SAT

Site Acceptance Testing
SQT

System Quality Testing
SWIM

System-Wide Information Management
TI

Technical Infrastructure
TLS

Transport Layer Security
URL

Uniform Resource Locator
WFS

Web Feature Service
WFS-TE

Web Feature Service - Temporality Extension
WS

Web Service
XML

Extensible Markup Language

OGC Filter Encoding 2.0 Encoding Standard

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.
OGC Web Feature Service (WFS) Temporality Extension

Temporal filters based on WFS-TE supporting the following temporality use cases: 3,4,6,7,8.

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.

https://aixm.aero/page/aixm-51-511

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.

Duplicate subscriptions

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.

Normal Conditions

The Digital NOTAM Subscription and Request Service provides two interfaces: (1) a REST-based WFS interface supporting spatial and temporal queries compliant with WFS and WFS-TE standards, returning AIXM 5.1.1 encoded data; and (2) a subscription-distribution interface combining RESTful subscription management and AMQP 1.0-based message distribution. Consumers create subscriptions via REST, receive AMQP queue details in response. Upon data changes, messages are generated and pushed to AMQP queues according to subscription filters. Consumers retrieve and acknowledge messages from their queues. The Data Consumer sends requests compliant with the OGC Web Feature Service (WFS) and WFS Temporality Extension (WFS-TE) standards to the REST-based WFS Service. The service processes spatial and temporal queries and responds with aeronautical information encoded in AIXM 5.1.1 format. Clients are expected to construct requests using supported operators as defined in the applicable standards.
Technical messages

Implementation of PUBLISH_SUBSCRIBE using AMQP 1.0 protocol uses technical messages to inform the service consumer about:- creation, update or deletion of subscription
Error Handling

The service provides error responses according to the OGC OWS ExceptionReport standard for the WFS interface. Clients can expect structured and consistent error reporting indicating the outcome of each WFS request. For the Subscription interface, the service returns standard HTTP status codes along with error messages in the response body to indicate issues such as invalid requests, unauthorized access, or subscription conflicts.

Not available to consumer.

Digital NOTAM Subscription and Request Service Subscription Interface

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.

PROVIDER_SIDE
- subscribe
  
  This operation allows a service consumer to subscribe to event scenarios of interest.
  git
  Messages
  
  SubscriptionsRequest - REST POST
  
  IN
  
  SubscriptionsRequest - REST POST
  
  OUT
- unsubscribe
  
  This operation allows a service consumer to unsubscribe from event scenarios of interest.
  git
  Messages
  
  SubscriptionsRequest - REST DELETE
  
  IN
  
  SubscriptionsRequest - REST DELETE
  
  OUT
- pause
  
  This operation allows a service consumer to pause the subscription for a particular topic subscription.
  git
  Messages
  
  SubscriptionsRequest - REST PUT
  
  IN
  
  SubscriptionsRequest - REST PUT
  
  OUT
- resume
  
  This operation allows a service consumer to resume a subscription that had been paused.
  git
  Messages
  
  SubscriptionsRequest - REST PUT
  
  IN
  
  SubscriptionsRequest - REST PUT
  
  OUT
- getSubscriptions
  
  This operation allows a service consumer to obtain the list of subscriptions.
  git
  Messages
  
  SubscriptionsRequest - REST GET
  
  IN
  
  SubscriptionsRequest - REST POST
  
  OUT
- getSubscriptionDetails
  
  This operation allows a service consumer to obtain information on a specific subscription.
  git
  Messages
  
  SubcriptionDetailsRequest - REST GET
  
  IN
  
  SubcriptionDetailsReply - REST GET
  
  OUT
- getTopics
  
  This operation allows a service consumer to request the list of topics (which represent type of data, i.e. SWIM services) available for subscription
  git
  Messages
  
  TopicsRequest - REST GET
  
  IN
  
  TopicsReply - REST GET
  
  OUT
- getTopic
  
  This operation allows a service consumer to obtain information on a specific topic (filter criteria).
  git
  Messages
  
  GetTopicRequest - REST GET
  
  IN
  
  GetTopicReply - REST GET
  
  OUT
Endpoints

Restricted
- SWIM_TI_YP_1_1_WS_LIGHT
  
  The web service is bound to the REST architectural style.
- IPV4_UNICAST
  
  SWIM TI Yellow Profile specification
- SubscriptionRequest
  
  Request message to subscribe to an event scenario of interest.
- SubscriptionReply
  
  Reply message to a subscription request.
- UnsubscriptionRequest
  
  Request message to unsubscribe to an event scenario of interest.
- UnsubscriptionReply
  
  Reply message to an unsubscription request.
- PauseRequest
  
  Request message to pause a subscription.
- PauseReply
  
  Reply message to an pause request.
- ResumeRequest
  
  Request message to resume a subscription.
- ResumeReply
  
  Reply message to a resume request.
- GetSubscriptionsRequest
  
  Request message to get a list of subscriptions.
- GetSubscriptionsReply
  
  Reply message to a get subscriptions request.
- GetSubcriptionDetailsRequest
  
  Request message to get the details on a specific subscription.
- GetSubcriptionDetailsReply
  
  Reply message to a get subscription details request.
- GetTopicsRequest
  
  Request message to get a list of business topics (type of data, i.e. services) that are available for subscription.
- GetTopicsReply
  
  Reply message to a get topics request.
- GetTopicRequest
  
  Request message to get the details on a specific topic.
- GetTopicReply
  
  Reply message to a get topic request.
Digital NOTAM Subscription and Request Service Distribution Interface

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.

PROVIDER_SIDE
- publish
  
  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.
  git
Endpoints

Restricted
- SWIM_TI_YP_1_1_AMQP_MESSAGING
  
  The web service is bound to the AMQP 1.0 messaging protocol.
- IPV4_UNICAST
  
  SWIM TI Yellow Profile specification
Digital NOTAM Subscription and Request Service Request Interface

Allows the service consumer to request an AIXM Basic Message based on filters which are linked to the event feature.

PROVIDER_SIDE
- GetCapabilities
  
  The GetCapabilities operation generates a service metadata document describing a WFS service provided by a server.
  git
  Messages
  
  GetCapabilitiesRequest - REST Post
  
  IN
  
  GetCapabilitiesResponse - REST Response
  
  OUT
- GetFeature
  
  The GetFeature operation returns a selection of features from a data store.
  git
  Messages
  
  GetFeatureRequest - REST Post
  
  IN
  
  GetFeatureResponse - REST Response
  
  OUT
Endpoints

Restricted
- SWIM_TI_YP_1_1_WS_LIGHT
  
  EUROCONTROL Specification for SWIM Technical Infrastructure (TI) Yellow Profile
- IPV4_UNICAST
  
  SWIM TI Yellow Profile specification
- ExceptionReport
  
  ExceptionReport container for error messages according to the OGC OWS ExceptionReport standard. Used for reporting errors in all operations.

Appendix A: References

https://swim-eurocontrol.atlassian.net/wiki/spaces/ASW/pages/60031402/Digital+NOTAM+Subscription+and+Request+Service+-+Service+Definition

INFORMATION_DEFINITION

1.0
AppendixB: Information Definition for Digital NOTAM Subscription and RequestService

https://swim-eurocontrol.atlassian.net/wiki/spaces/ASW/pages/60031402/Digital+NOTAM+Subscription+and+Request+Service+-+Service+Definition

INFORMATION_DEFINITION

1.0
AppendixC: Operational Needs

https://swim-eurocontrol.atlassian.net/wiki/spaces/ASW/pages/60031402/Digital+NOTAM+Subscription+and+Request+Service+-+Service+Definition

SERVICE_BEHAVIOUR_DESCRIPTION

1.0

Title

Digital NOTAM Specification

Standard Type

SERVICE_STANDARD

Conformance Statement

Not applicable.

Version

1.0

Description

The information scope offered by the service supports the requirements of the Digital NOTAM Specification.

Reference

https://ext.eurocontrol.int/aixm_confluence/display/DNOTAM/Digital+NOTAM+Specification

Digital NOTAM Specification

Title

OGC Web Feature Service

Standard Type

SERVICE_STANDARD

Conformance Statement

The service is partially conform with the standard as per Technical Constraints section of the current service description.

Version

2.0

Description

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.

Title

OGC Web Feature Service - Temporal Extension (WFS-TE)

Standard Type

SERVICE_STANDARD

Conformance Statement

__TODO__CONFORMANCE_STATEMENT__

Version

3.0

Description

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.

Reference

https://portal.ogc.org/files/?artifact_id=58922

OGC 12-027r3

Title

XML

Standard Type

EUROCONTROL_SPECIFICATION_FOR_SWIM_TECHNICAL_INFRASTRUCTURE

Conformance Statement

The Service Interface Binding supports the Extensible Mark-up Language (XML) 1.0. (as per SWIM-TIYP-0029 requirement)

Version

1.0

Description

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.

Title

WS Light

Standard Type

EUROCONTROL_SPECIFICATION_FOR_SWIM_TECHNICAL_INFRASTRUCTURE

Conformance Statement

The Service Interface Binding supports WS Light.

Reference

url:standards.rest

REST (Representational State Transfer) is a set of constraints for designing and developing web-based systems that are scalable, reliable, and loosely coupled. REST APIs use HTTP methods (such as GET, POST, PUT, DELETE) to define actions that can be performed on resources. These methods align with CRUD (Create, Read, Update, Delete) operations, which are used to manipulate resources over the web.

Title

AMQP

Standard Type

EUROCONTROL_SPECIFICATION_FOR_SWIM_SERVICE_DESCRIPTION

Conformance Statement

The Service Interface Binding supports AMQP 1.0 (as per SWIM-TIYP-0036 requirement).

Version

1.0

Reference

https://docs.oasis-open.org/amqp/core/v1.0/amqp-core-complete-v1.0.pdf

OASIS Advanced Message Queuing Protocol (AMQP) Version 1.0

LGS Digital NOTAM Subscription and Request Service v 1.0.0

Categorisation

Provider