SWIM_TI_YP_1_0_AMQP_MESSAGING

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

Operation to transmit the ArrivalSequence message to the service consumer

To process the input of a manual linkage/unlinkage request of a flight plan with a track.

To process the input of a control input command, to allow either:
• Take control of the flight,
• Transfer control of the flight,
• Delegate control of the flight to the sector where the flight is geographically located,
• Hand-over propose/accept.

To process the input of an entry flightlevel for the coordination between internal sectors or with the external upstream partner.

To process the input of a transfer flightlevel for the coordination between internal sectors or with the external downstream partner.

The operation allows to:
• Skip and cancel-skip of an internal sector,
• Bypass and cancel-bypass of the 1st downstream internal sector,
• Delegate the flight to another internal sector,
• Change the next downstream internal sector into the pre-ferred one.

The operation allows performing coordination changes related to the entry of the sector performing the request. The operation applies to both internal and external entry coordination.
Changes to the following items can be requested, or negotiated:
• NFL & NSFL (as also possible with requestNFL – see section 3.6.4)
• Departure level (indicates the initial cleared level for departure flights out of an internal aerodrome)
• ETO (Estimated Time Over)
• COP (Coordination Point)
• PSSR (Present SSR Code)
• DCT-to point (including intermediate point if required)
• Accepting Frequency
• Speed
• Heading

The operation allows performing coordination changes related to the exit of the sector performing the request. The operation applies to both internal and external exit coordination.
Changes to the following items can be requested, or negotiated:
• TFL & TSFL (as also possible with requestTFL – see section 3.6.5)
• ETO (Estimated Time Over)
• COP (Coordination Point)
• PSSR (Present SSR Code)
• DCT-to point (including intermediate point if required)
• Transferring Frequency
• Speed
• Heading

The operation allows performing a departure clearance (for a flight departing from an internal aerodrome). For example, a TWR sector can perform this action, or eventually a higher sector that has to deliver the departure clearance.
Items available in the departure clearance are kept limited for the first phase and include:
• Departure level (indicates the initial cleared level for departure flights out of an internal aerodrome)
• Take-off time
• PSSR (Present SSR Code)
• Accepting Frequency
• SID
• Departure runway