CONSUMER_SIDE

TI Primitive Message Exchange Pattern

FIRE_AND_FORGET

Service Interface Binding

The definition of these messages can be found in Section 2.7.3 Interface Messages.

Network Interface Binding

IPV4_UNICAST

AirspaceStatus

Interface role

The Airspace Status interface enables External Users (service consumers) to retrieve activation data on the status of airspace in the ASM system in real time.

An activation refers to the specific state of an airspace structure at the current time and until a specified end time. The end time of an activation is subject to change, it may be shortened or extended.

This interface allows consumers to see in real time the status of the airspace managed by the ASM Support System. The activation data provided contains the information known by the ASM system including the start time of the current activation state and the expected end time. Within the ASM system, the actual end time may be changed during the tactical phase. The changes to the current activation state are communicated immediately. The current activation state can be supplemented with the planned airspace usage information available from the Booking Interface in section 2.4.6, thus allowing visibility of the latest planned upcoming activations and deactivations within the ASM system.

This interface is treated as safety critical when used via the publish-subscribe mechanism detailed in the Publication Interface section 2.4.3. Under such use it requires that the External User acknowledges receipt and understanding of the activation data allowing the ASM system to detect in cases that a change in status is not received and processed by the External User. In contrast to the other interfaces defined in this service, subscribing to activation data will cause the current activation state to be automatically fully published to the subscriber. This ensures the initial state is always transmitted to External Users subscribing to activation data and also ensures that the initial state is acknowledged.

Figure 32 in Section 2.4.10.1 provides an overview of the Airspace status interface.

Information Exchange Flow

Figure 33 in Section 2.4.10.3 depicts the Airspace status interface information exchange flow.

Interface Functions

The interface performs the following function:

- Requesting Activations - Allows access to the activation data held within the ASM Support System by External Users.

ASM-INTF-STAT-010: ASM Service shall be supported by the Airspace Status interface to manage the retrieval of activation data held within the ASM Support System by external users.

ASM-INTF-STAT-020: The AirspaceStatus interface shall support the following operation:

- queryActivationList

Operations

queryActivationList

ASM-INTF-STAT-030: The queryActivationList operation shall receive and process the FilteredRequest message from an External User.

ASM-INTF-STAT-040: If the activation list request is valid, the queryActivationList operation shall transmit the matching activation data in the ActivationListReply message to the requesting External User.

ASM-INTF-STAT-050: If for any reason the request is not valid, the queryActivationList operation shall transmit an appropriate error in the ActivationListReply message to the requesting External User.

ASM-INTF-STAT-055: The queryActivationList operation shall accept any combination of the

following filters in the FilteredRequest message:

ActivityIDFilter
AirspaceIDFilter
ChangePeriodFilter
InterestedIntervalFilter
AndFilter

ASM-INTF-STAT-060: The External User shall only make use of data returned in an ActivationListReply for non-safety critical information purposes.

ASM-INTF-STAT-070: The External User shall make use of the AMQP service for safety-relevant purposes.

ASM-INTF-STAT-080: The External User should acknowledge receipt of any valid ActivationNotification published onto an AMQP queue, by publishing an AcknowledgementReceiptRequest message onto the AMQP queue referenced in the ActivationNotification message.

ASM-INTF-STAT-090: The ASM Support System shall select an appropriate value for Activation acknowledgement-time and ensure that this value is appropriately documented for use by service consumers.

Note: The definition of these messages can be found in section 2.7.3 Interface Messages.

Idempotent

NON_IDEMPOTENT

Synchronous

ASYNCHRONOUS

TI Protocol Methods

Refer to Section 2.5 Technologies

Operation Message

Processing Consideration

Behaviour

Interface Binding Description

N/A

Interface Provision Side

TI Primitive Message Exchange Pattern

Service Interface Binding

Network Interface Binding

The definition of these messages can be found in Section 2.7.3 Interface Messages.

AirspaceNegotiation

Interface role

The Airspace Negotiation interface enables the retrieval and handling of proposals held within the ASM Support System by External Users.

A proposal refers to a specific reservation and effectively re-defines a subset of the reservation data. The Negotiation interface enables a proposal to be accepted or rejected as per the actions accessible through the service.

The Negotiation interface allows users managing the airspace to make proposals to booking requests introduced by foreign airspace requesters. The proposals could address the FLs, times, or even different area. These proposals could be accepted or rejected.

Figure 29 in Section 2.4.9.1 provides an overview of the Airspace negotiation interface

Information Exchange Flow

Figure 30 in Section 2.4.9.2 depicts the Airspace negotiation interface information exchange flow.

Interface Functions

The interface performs the following functions:

- Creating a Proposal - introduces a new Proposal into the ASM Support System.

- Requesting Proposal List - allows access to the Proposal information from within the ASM Support System to allow for CDM processes.

- Handling Proposals – accepts or rejects the Proposal

ASM-INTF-NEG-010: ASM Service should be supported by the Airspace Negotiation interface to manage the reservations.

ASM-INTF-NEG-020: The AirspaceNegotiation interface shall support the following operations:

- createBookingProposal,

- queryBookingProposalList

- handleBookingProposal

Operations

createBookingProposal

ASM-INTF-NEG-030: The createBookingProposal operation shall receive and process the BookingProposalRequest message from an External User.

ASM-INTF-NEG-040: If the proposal is valid, the createBookingProposal operation shall transmit the newly created proposal in the BookingProposalReply message to the requesting External Users.

ASM-INTF-NEG-050: If for any reason the request or the resulting proposal is not valid, the createBookingPrposal operation shall transmit an appropriate error in the BookingProposalReply message to the requesting External Users.

Note: The definition of these messages can be found in section 2.7.3 Interface Messages.

Idempotent

NON_IDEMPOTENT

Synchronous

ASYNCHRONOUS

TI Protocol Methods

Refer to Section 2.5 Technologies

Operation Message

Processing Consideration

The definition of these messages can be found in Section 2.7.3 Interface Messages.

queryBookingProposalList

ASM-INTF-NEG-060: The queryBookingProposalList operation shall receive and process the FilteredRequest message from an External Users.

ASM-INTF-NEG-070: If the proposal list request is valid, the queryBookingProposalList operation shall transmit the list of proposals in the BookingProposalListReply message to the requesting External Users.

ASM-INTF-NEG-080: If for any reason the request is not valid, the queryBookingProposalList operation shall transmit an appropriate error in the BookingProposalListReply message to the requesting External Users.

ASM-INTF-NEG-085: The queryBookingProposalList operation shall accept any combination of the following filters in the FilteredRequest message:

ActivityIDFilter
ChangePeriodFilter
InterestedIntervalFilter
AndFilter

Note: The definition of these messages can be found in section 2.7.3 Interface Messages.

Idempotent

NON_IDEMPOTENT

Synchronous

ASYNCHRONOUS

TI Protocol Methods

Refer to Section 2.5 Technologies

Operation Message

Processing Consideration

The definition of these messages can be found in Section 2.7.3 Interface Messages.

handleBookingProposal

ASM-INTF-NEG-090: The handleBookingProposal operation shall receive and process the HandleBookingProposalRequest message from an External User.

ASM-INTF-NEG-100: If the request is valid, the handleBookingProposal operation shall perform the requested action.

ASM-INTF-NEG-110: If for any reason the request is not valid, the updateBooking operation shall transmit an appropriate error in the HandleBookingProposalReply message to the requesting External User.

ASM-INTF-NEG-120: A HandleBookingProposalRequest should be rejected by the service if the user performing the update does not have the appropriate actions matching their update.

Note: The definition of these messages can be found in section 2.7.3 Interface Messages.

Idempotent

NON_IDEMPOTENT

Synchronous

ASYNCHRONOUS

TI Protocol Methods

Refer to Section 2.5 Technologies

Operation Message

Processing Consideration

Behaviour

Interface Binding Description

N/A

Interface Provision Side

TI Primitive Message Exchange Pattern

Service Interface Binding

Network Interface Binding

The definition of these can be found in Section 2.7.3 Interface Messages.

Mission

Interface role

The Mission interface allows for the creation, modification and retrieval of missions held within the ASM Support System by External Users. This interface allows exchange of mission information between host and foreign ASM Support Systems.

Figure 26 in Section 2.4.8.1 provides an overview of the Mission interface.

Information Exchange Flow

Figure 27 in Section 2.4.8.2 depicts the Mission interface information exchange flow

Interface Functions

The interface performs the following functions:

- Creating a Mission - introduces a new Mission into the ASM Support System to be approved to be incorporated into the plan.

- Updating a Mission - updates an existing Mission in the ASM Support System potentially as a result of a CDM process or simply to update the plan to reflect real world changes to planned activities

- Requesting Missions - allows access to the Missions information from within the ASM Support System to allow for CDM processes.

ASM-INTF-MIS-010: ASM Service should be supported by the Mission interface to manage the exchange of mission information.

ASM-INTF-MIS-020: The Mission interface shall support the following operation:

- createMission,

- updateMission,

- queryMissionList

Operations

createMission

ASM-INTF-MIS-030: The createMission operation shall receive and process the MissionCreationRequest message from an External User.

ASM-INTF-MIS-040: If the mission is valid, the createMission operation shall transmit the newly created mission in the MissionReply message to the requesting External Users.

ASM-INTF-MIS-050: If for any reason the request or the resulting mission is not valid, the createMission operation shall transmit an appropriate error in the MissionReply message to the requesting External Users.

Note: The definition of these can be found in section 2.7.3 Interface Messages.

Idempotent

NON_IDEMPOTENT

Synchronous

ASYNCHRONOUS

TI Protocol Methods

Refer to Section 2.5 Technologies

Operation Message

Processing Consideration

The definition of these can be found in Section 2.7.3 Interface Messages.

updateMission

ASM-INTF-MIS-060: The updateMission operation shall receive and process the MissionUpdateRequest message from an External User.

ASM-INTF-MIS-070: If the mission update is valid, the updateMission operation shall transmit the updated mission in the MissionReply message to the requesting External Users.

ASM-INTF-MIS-080: If for any reason the request or the resulting updated mission is not valid, the updateMission operation shall transmit an appropriate error in the MissionReply message to the requesting External Users.

ASM-INTF-MIS-090: A MissionUpdateRequest should be rejected by the service if the user performing the update does not have the appropriate actions matching their update.

Note: The definition of these can be found in section 2.7.3 Interface Messages.

Idempotent

NON_IDEMPOTENT

Synchronous

ASYNCHRONOUS

TI Protocol Methods

Refer to Section 2.5 Technologies

Operation Message

Processing Consideration

The definition of these messages can be found in Section 2.7.3 Interface Messages.

queryMissionList

ASM-INTF-MIS-100: The queryMissionList operation shall receive and process the FilteredRequest message from an External User.

ASM-INTF-MIS-110: If the request is valid, the queryMissionList operation shall transmit the list of missions in the MissionListReply message to the requesting External Users.

ASM-INTF-MIS-120: If for any reason the request is not valid, the queryMissionList operation shall transmit an appropriate error in the MissionListReply message to the requesting External Users.

ASM-INTF-MIS-130: The queryMissionList operation shall accept any combination of the following filters in the FilteredRequest message:

MissionIDFilter
ActivityIDFilter
ChangePeriodFilter
InterestedIntervalFilter
AndFilter

Note: The definition of these messages can be found in section 2.7.3 Interface Messages.

Idempotent

NON_IDEMPOTENT

Synchronous

ASYNCHRONOUS

TI Protocol Methods

Refer to Section 2.5 Technologies

Operation Message

Processing Consideration

Behaviour

Interface Binding Description

N/A

Interface Provision Side

TI Primitive Message Exchange Pattern

Service Interface Binding

Network Interface Binding

The definition of these messages can be found in Section 2.7.3 Interface Messages.

BookingConflicts

Interface role

Requesting Conflict List allows access to the Booking conflict information from within the ASM Support System to enhance CDM processes.

Figure 23 in Section 2.4.7.1 provides an overview of the Booking conflicts interface

The elements in the data model are described in full detail in section 2.7.3 Interface Messages.

Information Exchange Flow

Figure 24 in Section 2.4.7.2 depicts the information exchange flow for the Booking Conflicts interface.

Interface Functions

The interface performs the following functions:

- Requesting booking conflict data – allows access to booking conflict data from within the ASM Support System

ASM-INTF-CON-010: ASM Service should be supported by the Booking Conflicts interface to manage booking conflicts.

ASM-INTF-CON-020: The Booking Conflicts interface shall support the following operation:

- queryConflictList

Operations

queryConflictList

This operation is intended to introduce a query for the list of conflicts between bookings in the ASM Support System in response to a request from an External User. As a result, the list of conflicts between bookings is either transmitted to the External User or not, and an appropriate error message is transmitted to the External User.

ASM-INTF-CON-030: The queryConflictList operation shall receive and process the FilteredRequest message from an External User.

ASM-INTF-CON-040: The queryConflictList operation shall validate the FilteredRequest message against the following criteria which must be met:

- All mandatory data for the FilteredRequest message are provided

ASM-INTF-CON-050: If the request is valid, the queryConflictList operation shall transmit the list of conflicts in the BookingConflictListReply message to the requesting External User.

ASM-INTF-CON-060: If the request is not valid, the queryConflictList operation shall transmit an appropriate error in the BookingConflictListReply message to the requesting External User.

ASM-INTF-CON-070: The queryConflictList operation shall accept any combination of the following filters in the FilteredRequest:

- ActivityIDFilter

- AndFilter

Note: The definition of these messages can be found in section 2.7.3 Interface Messages.

Idempotent

NON_IDEMPOTENT

Synchronous

ASYNCHRONOUS

TI Protocol Methods

Refer to Section 2.5 Technologies

Operation Message

Processing Consideration

Behaviour

Interface Binding Description

N/A

Interface Provision Side

TI Primitive Message Exchange Pattern

Service Interface Binding

Network Interface Binding

The definition of these messages can be found in section 2.7.3 Interface Messages.

Booking

Interface role

Booking is an interface that enables the creation, modification and retrieval of bookings, including details of conflicts between different bookings within the ASM Support System by External Users. The interface allows for continuous updates in real time of Booking information among authorised ASM Support Systems/External Users in order to enhance cross border coordination based on the most recent information.

The interface also enables booking of airspace structures across national borders; airspace users are able to book foreign airspace using their local ASM Support System. The process of a foreign booking follows the ASM process defined in dedicated LoAs between States.

The creation and modification of bookings is supported through the provision of ‘Actions’ by the interface. The Actions describe the allowed modifications that a user may take on a specific booking. Actions are subject to change based on the state of a booking and the current time.

Figure 20 in Section 2.4.6.1 provides an overview of the Booking interface

Information Exchange Flow

Figure 21 in Section 2.4.6.2 depicts the Booking interface information exchange flow

Interface Functions

The interface performs the following functions:

- Creating a Booking introduces a new Booking into the ASM Support System to be approved to be incorporated into the plan.

- Updating a Booking updates an existing Booking in the ASM Support System potentially as a result of a CDM process or simply to update the plan to reflect changes to planned activities.

- Requesting Booking List allows access to the Booking information from within the ASM Support System to allow for CDM processes.

- Requesting Actions allows access to the Actions that can performed by the actor. Identifying where they may contribute to the CDM process within the ASM Support System and which Airspace Reservation they can update to better inform the plan.

- Requesting History allows access to the history of all actions that have been performed on a Booking.

ASM-INTF-ARES-010: ASM Service shall be supported by the Booking interface to manage the reservations

ASM-INTF-ARES-020: The Booking interface shall implement synchronous Request-Reply application message exchange pattern.

ASM-INTF-ARES-030: The Booking interface shall support the following operations:

- createBooking,

- updateBooking,

- queryBookingList

- queryActionList

- queryBookingHistoryList

Operations

createBooking

This operation is intended to introduce a new booking in the ASM Support System in response to a request from an External User. As a result, the new booking is either created in the local ASM Support System and the External User is notified, or the booking is not created and an appropriate error message is transmitted to the External User.

Associated messages

ASM-INTF-ARES-040: The createBooking operation shall receive and process the BookingCreationRequest message from an External User.

ASM-INTF-ARES-050: The createBooking operation shall validate the BookingCreationRequest message against the following criteria which must be met:

- All mandatory data for the BookingCreationRequest message are provided

- The booking ID must be null/not set

- The start date and time of all AirspaceReservations must be in the future

- The end date and time of an AirspaceReservation must be after its start date and time

- The External User must have permission to book the airspace structures as defined by the ActivityData.

- The entire booked period must be within the life time of all booked airspace structures

- The booked flight levels must be within or equal to the flight level bounds of the airspace structures

- The booked lower flight level of an airspace structure must be below the booked upper flight level of the airspace structure

- The selected responsible unit must be common to all booked airspace structures as defined by the ActivityData.

ASM-INTF-ARES-060: If the booking is valid, the createBooking operation shall transmit the newly created booking in the BookingReply message to the requesting External User.

ASM-INTF-ARES-070: If the request or the resulting booking is not valid, the createBooking operation shall transmit an appropriate error in the BookingReply message to the requesting External User.

Note: The definition of these messages can be found in section 2.7.3 Interface Messages.

Idempotent

NON_IDEMPOTENT

Synchronous

ASYNCHRONOUS

TI Protocol Methods

Refer to Section 2.5 Technologies

Operation Message

Processing Consideration

The definition of these messages can be found in Section 2.7.3 Interface Messages.

updateBooking

This operation is intended to introduce updates to an existing booking in the ASM Support System in response to a request from an External User. As a result, the booking is either updated in the local ASM Support System and the External User is notified, or the booking is not updated and an appropriate error message is transmitted to the External User.

Associated messages

ASM-INTF-ARES-080: The updateBooking operation shall receive and process the BookingUpdateRequest message from an External User.

ASM-INTF-ARES-090: The updateBooking operation shall validate the BookingUpdateRequest message against the following criteria which must be met:

- All mandatory data for the BookingUpdateRequest message are provided

- The booking ID must be set

- The lastChangeTime in the booking must match that held by the service

- The start date and time of all AirspaceReservations must be in the future; if the booking is active the start dates and times must match the original start dates and times and the end time should be in the future

- The end date and time of an AirspaceReservation must be after its start date and time

- The External User must have permission to book the airspace structures as defined by the ActivityData

- The entire booked period must be within the life time of all booked airspace structures

- The booked flight levels must be within or equal to the flight level bounds of the airspace structures

- The booked lower flight level of an airspace structure must be below the booked upper flight level of the airspace structure

- The selected responsible unit must be common to all booked airspace structures as defined by the ActivityData

ASM-INTF-ARES-100: If the booking update is valid, the updateBooking operation shall transmit the updated booking in the BookingReply message to the requesting External User.

ASM-INTF-ARES-110: If the request or the resulting updated booking is not valid, the updateBooking operation shall transmit an appropriate error in the BookingReply message to the requesting External User.

ASM-INTF-ARES-120: An updateBookingRequest should be rejected by the service if the user performing the update does not have the appropriate actions matching their update.

Note: The definition of these messages can be found in section 2.7.3 Interface Messages.

Idempotent

NON_IDEMPOTENT

Synchronous

ASYNCHRONOUS

TI Protocol Methods

Refer to Section 2.5 Technologies

Operation Message

Processing Consideration

The definition of these messages can be found in Section 2.7.3 Interface Messages.

queryBookingList

This operation is intended to introduce a query for the list of bookings in the ASM Support System in response to a request from an External User. As a result, the list of bookings is either transmitted to the External User or not, and an appropriate error message is transmitted to the External User.

Associated messages

ASM-INTF-ARES-130: The queryBookingList operation shall receive and process the FilteredRequest message from an External User.

ASM-INTF-ARES-140: The queryBookingList operation shall validate the FilteredRequest message against the following criteria which must be met:

- All mandatory data for FilteredRequest message are provided

ASM-INTF-ARES-150: If the request is valid, the queryBookingList operation shall transmit the filtered list of bookings in the BookingListReply message to the requesting External User.

ASM-INTF-ARES-160: If the request is not valid, the queryBookingList operation shall transmit an appropriate error in the BookingListReply message to the requesting External User.

ASM-INTF-ARES-170: The queryBookingList operation shall accept any combination of the following filters in the FilteredRequest message:

- ActivityIDFilter

- ChangePeriodFilter

- InterestedIntervalFilter

- AndFilter

ASM-INTF-ARES-180: The queryBookingList operation should accept any combination of the following filters in the FilteredRequest message:

- AirspaceIDFilter

- GeometryFilter

- MissionIDFilter

Note: The definition of these messages can be found in section 2.7.3 Interface Messages.

Idempotent

NON_IDEMPOTENT

Synchronous

ASYNCHRONOUS

TI Protocol Methods

Refer to Section 2.5 Technologies

Operation Message

Processing Consideration

The definition of these messages can be found in Section 2.7.3 Interface Messages.

queryActionList

This operation is intended to introduce a query for the list of actions in the ASM Support System in response to a request from an External User. As a result, the list of actions is either transmitted to the External User or not, and an appropriate error message is transmitted to the External User.

Associated messages

ASM-INTF-ARES-190: The queryActionList operation shall receive and process the FilteredRequest message from an External User.

ASM-INTF-ARES-200: The queryActionList operation shall validate the FilteredRequest message against the following criteria which must be met:

- All mandatory data for the FilteredRequest message are provided

ASM-INTF-ARES-210: If the request is valid, the queryActionList operation shall transmit the list of actions in the BookingActionListReply message to the requesting External User.

ASM-INTF-ARES-220: If the request is not valid, the queryActionList operation shall transmit an appropriate error in the BookingActionListReply message to the requesting External User.

ASM-INTF-ARES-230: The queryActionList operation shall accept the following filter in the FilteredRequest:

- ActivityIDFilter

Note: The definition of these messages can be found in section 2.7.3 Interface Messages.

Idempotent

NON_IDEMPOTENT

Synchronous

ASYNCHRONOUS

TI Protocol Methods

Refer to Section 2.5 Technologies

Operation Message

Processing Consideration

The definition of these messages can be found in Section 2.7.3 Interface Messages.

queryBookingHistoryList

This operation is intended to introduce a query for the list of history of actions performed on a booking in the ASM Support System in response to a request from an External User. As a result, the list of history of actions performed on a booking is either transmitted to the External User or not, and an appropriate error message is transmitted to the External User.

Associated messages

ASM-INTF-ARES-240: The queryBookingHistoryList operation shall receive and process the FilteredRequest message from an External User.

ASM-INTF-ARES-250: The queryBookingHistoryList operation shall validate the FilteredRequest message against the following criteria which must be met:

- All mandatory data for the FilteredRequest message are provided

ASM-INTF-ARES-260: If the request is valid, the queryBookingHistoryList operation shall transmit the complete list of history of actions performed on a booking in the BookingHistoryListReply message to the requesting External User.

ASM-INTF-ARES-270: If the request is not valid, the queryBookingHistoryList operation shall transmit an appropriate error in the BookingHistoryListReply message to the requesting External User.

ASM-INTF-ARES-280: The queryBookingHistoryList operation shall accept the following filter in the FilteredRequest message:

- ActivityIDFilter

Note: The definition of these messages can be found in section 2.7.3 Interface Messages.

Idempotent

NON_IDEMPOTENT

Synchronous

ASYNCHRONOUS

TI Protocol Methods

Refer to Section 2.5 Technologies

Operation Message

Processing Consideration

Behaviour

Interface Binding Description

N/A

Interface Provision Side

TI Primitive Message Exchange Pattern

Service Interface Binding

Network Interface Binding

The definition of these messages can be found in section 2.7.3 Interface Messages.

LocalAirspaceStructure

Interface role

The Local Airspace Structure interface allows for retrieval of airspace structures and activity data from within the ASM Support System by External Users.

Local ASM Support Systems maintain a local data base that contains national airspace structures. The interface allows External Users to obtain the definitions of the airspace structures, provided by the providing system in accordance with the provider requirements, as well as activity data, in order to follow their status and the reservations associated to them.

Figure 17 in Section 2.4.5.1 provides an overview of the Local Airspace Structure interface

The elements in the data model are described in full detail in section 2.7.3 Interface Messages.

Information Exchange Flow

Figure 18 in Section 2.4.5.2 depicts the information exchange flow for the Local Airspace Structure interface.

Interface Functions

The interface performs the following functions:

- Requesting Static Data - allows access to static data from within the ASM Support System

- Requesting Activity Data – allows access to activity data from within the ASM Support System

ASM-INTF-LAS-010: ASM Service shall be supported by the Local Airspace Structure interface to manage the access to local airspace static and activity data.

ASM-INTF-LAS-020: The LocalAirspaceStructure interface shall support the following operations:

retrieveAirspace
queryActivityDataList

Operations

queryAirspace

This operation is intended to manage the access to static data from the ASM Support System.

Associated messages

ASM-INTF-LAS-030: The queryAirspaceList operation shall receive and process the FilteredRequest message from an External User.

ASM-INTF-LAS-040: If the request is valid, the queryAirspaceList operation shall transmit the matching static data in the AirspaceListReply message to the requesting External User.

ASM-INTF-LAS-050: If for any reason the request is not valid, the queryAirspaceList operation shall transmit an appropriate error in the AirspaceListReply message to the requesting External User.

ASM-INTF-LAS-055: The queryAirspaceList operation shall accept any combination of the

following filters in the FilteredRequest message:

AirspaceIDFilter
AirspaceNameFilter
AirspaceTypeFilter
GeometryFilter
AndFilter
ChangePeriodFilter
InterestedIntervalFilter

Note: The definition of these messages can be found in section 2.7.3 Interface Messages.

Idempotent

NON_IDEMPOTENT

Synchronous

ASYNCHRONOUS

TI Protocol Methods

Refer to Section 2.5 Technologies

Operation Message

Processing Consideration

The definition of these messages can be found in Section 2.7.3 Interface Messages.

queryActivityDataList

This operation is intended to manage the access to activity data from the ASM Support System.

ASM-INTF-LAS-060: The queryActivityDataList operation shall receive and process the FilteredRequest message from an External User.

ASM-INTF-LAS-070: If the request is valid, the queryActivityDataList operation shall transmit the matching activity data list in the ActivityDataListReply message to the requesting External User.

ASM-INTF-LAS-080: If for any reason the request is not valid, the queryActivityDataList operation shall transmit an appropriate error in the ActivityDataListReply message to the requesting External User.

ASM-INTF-LAS-085: The queryActivityDataList operation shall accept any combination of

the following filters in the FilteredRequest message:

AirspaceIDFilter

Note: The definition of these messages can be found in section 2.7.3 Interface Messages.

Idempotent

NON_IDEMPOTENT

Synchronous

ASYNCHRONOUS

TI Protocol Methods

Refer to Section 2.5 Technologies

Operation Message

Processing Consideration

Behaviour

Interface Binding Description

N/A

Interface Provision Side

TI Primitive Message Exchange Pattern

Service Interface Binding

Network Interface Binding

The definition of these messages can be found in Section 2.7.3 Interface Messages.

LongTermPlanning

Interface role

The Long Term Planning interface allows for the creation, modification and retrieval of long term planning data held within the ASM Support System. It is not foreseen that one ASM Support System may create long term planning in another ASM Support System and so the creation and update mechanisms may be limited to External Users acting as a user of the ASM Support System under the External ASM User - ASM Support System use of the service case.

Figure 14 in Section 2.4.4.1 provides an overview of the Long Term Planning interface

Information Exchange Flow

Figure 15 in Section 2.4.4.2 depicts the information exchange flow for the Long Term Planning interface.

Interface Functions

The interface performs the following functions:

- Creating an Event - introduces a new Event into the ASM Support System

- Updating an Event - updates an existing Event in the ASM Support System

- Requesting a List of Events - allows access to the Event information from within the ASM Support System

ASM-INTF-LTPL-010: ASM Service should be supported by the Long Term Planning interface to manage the events.

ASM-INTF-LTPL-020: The Long Term Planning interface shall support the following operations:

- createEvent,

- updateEvent,

- queryEventList.

Operations

createEvent

This operation is intended to introduce a new Event into the ASM Support System.

Associated messages

ASM-INTF-LTPL-030: The createEvent operation shall receive and process the EventCreationRequest message from an External User.

ASM-INTF-LTPL-040: If the event request is valid, the createEvent operation shall transmit the newly created event in the EventReply message to the requesting External Users.

ASM-INTF-LTPL-050: If for any reason the request or the resulting event is not valid, the createEvent operation shall transmit an appropriate error in the EventReply message to the requesting External Users.

Note: The definition of these messages can be found in section 2.7.3 Interface Messages.

Idempotent

NON_IDEMPOTENT

Synchronous

ASYNCHRONOUS

TI Protocol Methods

Refer to Section 2.5 Technologies

Operation Message

Processing Consideration

The definition of these messages can be found in section 2.7.3 Interface Messages.

updateEvent

This operation is intended to update an existing Event in the ASM Support System.

Associated messages

ASM-INTF-LTPL-060: The updateEvent operation shall receive and process the EventUpdateRequest message from an External Users.

ASM-INTF-LTPL-070: If the event update is valid, the updateEvent operation shall transmit the updated event in the EventReply message to the requesting External User.

ASM-INTF-LTPL-080: If for any reason the request or the resulting updated event is not valid, the updateEvent operation shall transmit an appropriate error in the EventReply message to the requesting External User.

Note: The definition of these messages can be found in section 2.7.3 Interface Messages.

Idempotent

NON_IDEMPOTENT

Synchronous

ASYNCHRONOUS

TI Protocol Methods

Refer to Section 2.5 Technologies

Operation Message

Processing Consideration

The definition of these messages can be found in section 2.7.3 Interface Messages.

queryEventList

This operation is intended to allow access to the Event information from within the ASM Support System.

Associated messages

ASM-INTF-LTPL-090: The queryEventList operation shall receive and process the FilteredRequest message from an External User.

ASM-INTF-LTPL-100: If the request is valid, the queryEventList operation shall transmit the matching list of events in the EventListReply message to the requesting External User.

ASM-INTF-LTPL-110: If for any reason the request is not valid, the queryEventList operation shall transmit an appropriate error in the EventListReply message to the requesting External User.

ASM-INTF-LTPL-120: The queryEventList operation shall accept any combination of the

following filters in the FilteredRequest message:

ActivityIDFilter
ChangePeriodFilter
InterestedIntervalFilter
AndFilter

Note: The definition of these messages can be found in section 2.7.3 Interface Messages.

Idempotent

NON_IDEMPOTENT

Synchronous

ASYNCHRONOUS

TI Protocol Methods

Refer to Section 2.5 Technologies

Operation Message

Processing Consideration

Behaviour

Interface Binding Description

N/A

Interface Provision Side

TI Primitive Message Exchange Pattern

Service Interface Binding

Network Interface Binding

The definition of this message can be found in Section 2.7.3 Interface Messages.

Publication

Interface role

The Publication interface enables the management of updates based on subscriptions by External Users. External Users are able to receive notifications of updates of the information of their interest generated by the ASM Support Systems. Each interface applies filtering options in order to ensure data provision aligned with the requirements of the External User.

This interface publishes the data that would otherwise be directly requested from other interfaces. As such the data coming via this interface is contained within the notification messages defined in section 2.7.3 Interface Messages and containing data items described by each of the other interfaces. As a result, this interface does not define its own data model.

Information Exchange Flow

The following diagram presents the information exchange flow for the Publication interface. The diagram shows a change occurring within the ASM Support System, the changed data being passed to the Publication interface which applies the filters related to each subscription and the relevant data being published to subscribed consumers.

Figure 12 in Section 2.4.3.2 depicts the Publication interface information exchange flow

Interface Functions

The interface performs the following function:

Notifying a change in the data according to the subscription topics that have been subscribed to.

ASM-INTF-PUB-010: ASM Service shall be supported by the Publication interface to manage the updates.

ASM-INTF-PUB-020: The Publication interface shall support the following operations:

- notifyStaticData

- notifyActivityData

- notifyBooking

- notifyBookingAction

- notifyBookingConflict

- notifyActivation

ASM-INTF-PUB-025: The Publication interface should support the following operations:

- notifyMission

- notifyProposal

- notifyEvent

ASM-INTF-PUB-030: Any data item considered for publication shall be published if:

- the data item was of interest to the subscriber before the change according to the filter defined at the time of subscription, or

- the data item is of interest to the subscriber post the change according to the filter defined at the time of subscription.

ASM-INTF-PUB-040: All notifications shall contain the full definition of the changed data item.

Operations

notifyStaticData

This operation is intended to notify an External User of a change in the definition of static data.

Associated messages

ASM-INTF-PUB-050: Any change to the definition of static data within the ASM Support System shall be considered for publication via an AirspaceNotification message.

Note: The definition of this message can be found in section 2.7.3 Interface Messages.

Idempotent

NON_IDEMPOTENT

Synchronous

ASYNCHRONOUS

TI Protocol Methods

Refer to Section 2.5 Technologies

Operation Message

Processing Consideration

The definition of this message can be found in Section 2.7.3 Interface Messages

notifyActivityData

This operation is intended to notify an External User of a change in the definition of activity data.

Associated messages

ASM-INTF-PUB-060: Any change to the definition of activity data within the ASM Support System shall be considered for publication via an ActivityDataNotification message.

Note: The definition of this message can be found in section 2.7.3 Interface Messages.

Idempotent

NON_IDEMPOTENT

Synchronous

ASYNCHRONOUS

TI Protocol Methods

Refer to Section 2.5 Technologies

Operation Message

Processing Consideration

The definition of this message can be found in Section 2.7.3 Interface Messages.

notifyBooking

This operation is intended to notify an External User of a change in the definition of an existing booking.

Associated messages

ASM-INTF-PUB-070: Any change to the definition of a booking within the ASM Support System shall be considered for publication via a BookingNotification message.

Note: The definition of this message can be found in section 2.7.3 Interface Messages.

Idempotent

NON_IDEMPOTENT

Synchronous

ASYNCHRONOUS

TI Protocol Methods

Refer to Section 2.5 Technologies

Operation Message

Processing Consideration

The definition of this message can be found in section 2.7.3 Interface Messages.

notifyBookingAction

This operation is intended to notify an External User of an action that has been performed to an existing booking.

Associated messages

ASM-INTF-PUB-080: Any change to the definition of action data within the ASM Support System shall be considered for publication via a BookingActionNotification message.

Note: The definition of this message can be found in section 2.7.3 Interface Messages.

Idempotent

NON_IDEMPOTENT

Synchronous

ASYNCHRONOUS

TI Protocol Methods

Refer to Section 2.5 Technologies

Operation Message

Processing Consideration

The definition of this message can be found in section 2.7.3 Interface Messages.

notifyBookingConflict

This operation is intended to notify an External User of conflict data related to an existing booking.

Associated messages

ASM-INTF-PUB-090: Any change to the definition of booking conflict data within the ASM Support System shall be considered for publication via a BookingConflictNotification message.

Note: The definition of this message can be found in section 2.7.3 Interface Messages.

Idempotent

NON_IDEMPOTENT

Synchronous

ASYNCHRONOUS

TI Protocol Methods

Refer to Section 2.5 Technologies

Operation Message

Processing Consideration

The definition of this message can be found in section 2.7.3 Interface Messages.

notifyMission

This operation is intended to notify an External User of a change in the definition of mission data.

Associated messagews

ASM-INTF-PUB-100: Any change to the definition of mission data within the ASM Support System shall be considered for publication via a MissionNotification message.

Note: The definition of this message can be found in section 2.7.3 Interface Messages.

Idempotent

NON_IDEMPOTENT

Synchronous

ASYNCHRONOUS

TI Protocol Methods

Refer to Section 2.5 Technologies

Operation Message

Processing Consideration

The definition of this message can be found in Section 2.7.3 Interface Messages.

notifyProposal

This operation is intended to notify an External User of a change in the definition of proposal data.

Associated messages

ASM-INTF-PUB-110: Any change to the definition of proposal data within the ASM Support System shall be considered for publication via a BookingProposalNotification message.

Note: The definition of this message can be found in section 2.7.3 Interface Messages.

Idempotent

NON_IDEMPOTENT

Synchronous

ASYNCHRONOUS

TI Protocol Methods

Refer to Section 2.5 Technologies

Operation Message

Processing Consideration

The definition of this message can be found in Section 2.7.3 Interface Messages.

notifyEvent

This operation is intended to notify an External User of a change in the definition of event data.

Associated messages

ASM-INTF-PUB-120: Any change to the definition of event data within the ASM Support System shall be considered for publication via an EventNotification message.

Note: The definition of this message can be found in section 2.7.3 Interface Messages.

Idempotent

NON_IDEMPOTENT

Synchronous

ASYNCHRONOUS

TI Protocol Methods

Refer to Section 2.5 Technologies

Operation Message

Processing Consideration

The definition of this message can be found in Section 2.7.3 Interface Messages.

notifyActivation

This operation is intended to notify an External User of a change in the definition of activation data.

Associated messages

ASM-INTF-PUB-130: Any change to the definition of activation data within the ASM Support System shall be considered for publication via an ActivationNotification message.

Note: The definition of this message can be found in section 2.7.3 Interface Messages.

Idempotent

NON_IDEMPOTENT

Synchronous

ASYNCHRONOUS

TI Protocol Methods

Refer to Section 2.5 Technologies

Operation Message

Processing Consideration

Behaviour

Interface Binding Description

N/A

Interface Provision Side

TI Primitive Message Exchange Pattern

Service Interface Binding

Network Interface Binding

Nominal and unexpected behaviour

ArrivalSequenceInformationSubscriber

DSNA Arrival Sequence Service - Data distribution interface

Operations

publishArrivalSequence

Operation to transmit the ArrivalSequence message to the service consumer

Idempotent

NON_IDEMPOTENT

Synchronous

ASYNCHRONOUS

Precondition

To have a valid certificate and a valid subscription reference

TI Protocol Methods

AMQPS: AMQP 1.0 / TLS 1.2 / TCP / IPv4

Operation Message

ArrivalSequence

Processing Consideration

n.a

communicateException

Operation to inform the service consumer about problems occurring, at service run-time, on provider side.

Idempotent

NON_IDEMPOTENT

Synchronous

ASYNCHRONOUS

Precondition

To have a valid certificate and a valid subscription reference

TI Protocol Methods

AMQPS: AMQP 1.0 / TLS 1.2 / TCP / IPv4

Operation Message

ProviderException

Processing Consideration

n.a

Endpoints

Operational

operational network address

Url

amqps://eaman.swim.dsna.fr:5671

Pre-Operational

pre-operational network address

Url

amqps://eaman.preops.swim.dsna.fr:5671

Behaviour

Interface Binding Description

AMQPS: AMQP 1.0 / TLS 1.2 / TCP / IPv4

Interface Provision Side

Service Interface Binding

Network Interface Binding