Arrival Sequence Service 1.02
Current JSON Original JSON

Abstract

The Commission Implementing Regulation (EU) No 716/2014 requires the upgrade of existing AMAN to provide connection with cooperative En-Route Air Traffic Service Units (ATSU) to coordinate the actions to be taken by the cooperative ATSUs to make the correct time adjustment to flights under their control, in order to get the best and most efficient arriving flight sequence at the relevant airports based on AMAN arriving planning tool. 

Service Type
SWIM_DEFINITION
Lifecycle Stage
PROSPECTIVE
Business Activity Type
AERODROME_OPERATION
Intended Consumer
CIVIL_AIRSPACE_USER
Information Exchange Category
COOPERATIVE_NETWORK_INFORMATION_EXCHANGE
Application Message Exchange Pattern
PUBLISH_SUBSCRIBE_WITH_PUSH_MECHANISM
In-Operation Date
22-Mar-2020
Provider
EUROCONTROL

EUROCONTROL is an intergovernmental organisation with 41 Member and 2 Comprehensive Agreement States.

Point of Contact
Arrival Management Information_US

SESAR Identifier: IER-5.6.4-IERS-0032-0010
Issuer: Arrival Management
Intended Addressess: Stakeholder ATSU
Information Element: Arrival Management Information (IE-5.6.4-0032-0032)

Upstream Arrival Sequence information

A satellite airport which is a “nearby” airport having a departing flight to the concerned destination airport is informed of the arrival sequence of the destination airport.

MAX_DELIVERY_TIME

The 'MAX_DELIVERY_TIME' is the maximum allowed difference between the time of reception of a message at the consuming interface and the time of publication from the providing interface. As this includes the time absorbed on the network layer, the provider has to offer an appropriate network performance and has to define a minimum network performance on the consuming side as a precondition. The MAX_DELIVERY_TIME shall be equal or lower than 10 seconds.

MIN_AVAILABILITY

The Arrivial SequenceProvider shall provide a value for MIN_AVAILABILITY parameter defined as the ratio between total time that the service is available and a given interval of time (e.g. 1 month, 1 year).

SERVICE_RESTART_TIME

Upon service restart the Arrival Sequence provider shall ensure that the service functionality is available within 'SERVICE_RESTART_TIME'. The ArrivialSequenceProvider shall provide a value for the SERVICE_RESTART_TIME parameter.

SUBSCRIPTION_TIME_TO_LIVE

Upon ArrivalSequenceConsumer unavailability the ArrivalSequenceProvider shall keep the subscription active within 'SUBSCRIPTION_TIME_TO_LIVE'. The ArrivialSequenceProvider shall provide a value for the "SUBSCRIPTION_TIME_TO_LIVE" parameter. This parameter is defined as the time within which the ArrivalSequenceProvider shall retain the subscription even if the ArrivalSequenceConsumer get disconnected.

MESSAGE_TTL

For each ArrivalSequenceConsumer, the ArrivalSequenceProvider shall retain a not yet consumed (or delivered) ArrivalSequence message for at least MESSAGE_TTL period of time. MESSAGE_TTL indicates the message 'time to leave', i.e. the amount of time a message yet to be consumed is retained by the provider if such message has not been consumed yet by the service consumer. The ArrivalSequenceProvider shall provide a value for the MESSAGE_TTL parameter. The MESSAGE_TTL represents the time a given ArrivalSequence message must be kept by the ArrivalSequenceProvider if not consumed or delivered to the ArrivalSequenceConsumer before discarding.

MAX_CONSUMER_NUMBER

The service provider shall define the MAX_CONSUMER_NUMBER parameter, which represents the maximum supported concurrent consumers of the service.

Common UTC time source

The systems providing or consuming the service shall be synchronised to a common UTC time-source.

SELF_VALIDATION
Validation

Service providers claiming to have developed service instances which comply with the Arrival Sequence Service Performance Standard need to demonstrate this towards the consumers of the service instance. This can be achieved by verifying that the service formally fulfils the requirements of this standard and/or by validating or testing activities, which prove whether the expected behaviour and outcome of the service is achieved.

summary
ATSU

Air Traffic Service Unit

AMAN

Arrival Management

SWIM

System Wide Information Management

AIRM

ATM Information Reference Model

Information
The ArrivalSequenceProvider shall offer technical functions to the consumer to continuously monitor the service availability.
ArrivalSequenceInformationPublisherREST

REST Subscription Interface. This interface is one of the two implementation alternatives of the ArrivalSequenceInformationPublisher interface.

PROVIDER_SIDE
SWIM_TI_YP_1_0_WS_LIGHT
IPV4_UNICAST
SYNCHRONOUS_REQUEST_RESPONSE
Operations

Mutual Server-Client authentication will be performed via TLS using X.509 certificates.

ArrivalSequenceInformationPublisherSOAP

WS SOAP Subscription Interface. This interface is one of the two implementation alternatives of the ArrivalSequenceInformationPublisher interface.

PROVIDER_SIDE
SWIM_TI_YP_1_0_WS_SOAP
IPV4_UNICAST
SYNCHRONOUS_REQUEST_RESPONSE
Operations

Mutual Server-Client authentication will be performed via TLS using X.509 certificates.

ArrivalSequenceInformationSubscriber

Publication Interface

CONSUMER_SIDE
SWIM_TI_YP_1_0_AMQP_MESSAGING
IPV4_UNICAST
FIRE_AND_FORGET
Operations
publishArrivalSequence

Operation that allows the provider to publish an Arrival Sequence message to a subscribed consumer.

Idempotent
NON_IDEMPOTENT
Synchronous
ASYNCHRONOUS
Precondition
The consumer needs to be subscribed and connected to the queue.
TI Protocol Methods
transfer
Operation Message
arrivalSequence
communicateException

Operation that allows the provider to publish an Arrival Sequence message to a subscribed consumer.

Idempotent
NON_IDEMPOTENT
Synchronous
ASYNCHRONOUS
Precondition
The consumer needs to be subscribed and connected to the queue.
TI Protocol Methods
transfer
Operation Message
providerException

- Mutual Server-Client authentication will be performed via TLS using X.509 certificates.

References
Arrival Sequence Service Performance Standard

Standardised SWIM service design for an AMAN Sequence Service. This standardised service design follows the specification documents for service descriptions as provided by EUROCONTROL. Together with them, it can be used as a basis to implement SWIM Service instances.

Revision Save Date
Mon, 09/11/2023 - 14:49
Schema version
v0.0.3d