At the moment subscribing or unsubscribing to this service is only possible by contacting the DWD Aviation Customer Service. Contact details are found in the general part of the service description.
The necessary details regarding AMQP credentials and queue is contained in the subscription confirmation. The consumer needs to establish a consumer-client to consume the data from that queue.
At the moment subscribing or unsubscribing to this service is only possible by contacting the DWD Aviation Customer Service. Contact details are found in the general part of the service description.
The necessary details regarding AMQP credentials and queue is contained in the subscription confirmation. The consumer needs to establish a consumer-client to consume the data from that queue.
At the moment subscribing or unsubscribing to this service is only possible by contacting the DWD Aviation Customer Service. Contact details are found in the general part of the service description.
The necessary details regarding AMQP credentials and queue is contained in the subscription confirmation. The consumer needs to establish a consumer-client to consume the data from that queue.
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:
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.3Interface Messages.
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:
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.3Interface Messages.
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.3Interface Messages.
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.3Interface Messages.
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:
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.3Interface Messages.
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.3Interface Messages.
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.3Interface Messages.