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
Processing Consideration