BookingConflicts

Interface role

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

Figure 21 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 22 in Section 2.4.7.2 depicts the information exchange flow for the Local Airspace Structure 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: ASMtoASM 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

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
Processing Consideration
Behaviour
Interface Binding Description

N/A

Interface Provision Side
TI Primitive Message Exchange Pattern
Service Interface Binding
Network Interface Binding