CONSUMER_SIDE

The complete API description is available on MetSafe user portal accessible through a Token.  An access Token can be requested at [email protected].

Operations

Retrieve objects in GeoJSON inside a 4D Bounding Box.

Idempotent
NON_IDEMPOTENT
Synchronous
SYNCHRONOUS
TI Protocol Methods
Yellow Profile
Operation Message
Processing Consideration
Behaviour
Interface Binding Description

OGC:WFS2.0.0

WFS documentation can be found at:
https://docs.geoserver.org/latest/en/user/services/wfs/index.html

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

The ADT DNES is compliant to the Open Geospatial Consortium (OGC) Web Feature Service Temporality Extension (WFS-TE) specification, OGC 12-027r3 and the corresponding Web Feature Service (WFS) version 2.0.0 specification. For a machine- and human-readable interface description, please refer to the GetCapabilities.

Operations

A detailed description of supported operations is provided in the machine-readable WFSS capabilities document.

Idempotent
NON_IDEMPOTENT
Synchronous
ASYNCHRONOUS
Behaviour
Interface Binding Description

Both HTTP GET requests with key-value pairs as query parameters and HTTP POST requests with XML encoding of the requests, following the provisions in the WFS specification are supported.

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

The complete API description is available on MetSafe user portal accessible through a Token.  An access Token can be requested at [email protected].

Operations
Behaviour
Interface Binding Description

OGC:WFS2.0.0

WFS documentation can be found at:
https://docs.geoserver.org/latest/en/user/services/wfs/index.html

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

Publication Interface

Operations

Operation that allows the provider to publish an Arrival Sequence message to a subscribed consumer.

Idempotent
NON_IDEMPOTENT
Synchronous
ASYNCHRONOUS
Precondition
The consumer needs to be subscribed and connected to the queue.
TI Protocol Methods
transfer
Operation Message

Operation that allows the provider to publish an Arrival Sequence message to a subscribed consumer.

Idempotent
NON_IDEMPOTENT
Synchronous
ASYNCHRONOUS
Precondition
The consumer needs to be subscribed and connected to the queue.
TI Protocol Methods
transfer
Operation Message
Interface Binding Description

- Mutual Server-Client authentication will be performed via TLS using X.509 certificates.

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

Interface role

The Airspace Status interface enables the retrieval of activation data held within the ASM Support System by External Users.

An activation refers to the specific state of an airspace 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 users of host ASM Support System to see in real time the status of the airspace managed by another, foreign ASM Support System.

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

Information Exchange Flow

Figure 31 in Section 2.4.10.2 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: ASMtoASM 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

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 Users.                             

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

N/A

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

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 27 in Section 2.4.9.1 provides an overview of the Airspace negotiation interface

Information Exchange Flow

Figure 28 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: ASMtoASM 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

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

ASM-INTF-NEG-060: The queryBookingProposalList operation shall receive and process the BookingProposalListRequest 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.

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

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

N/A

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

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 24 in Section 2.4.8.1 provides an overview of the Mission interface.

Information Exchange Flow

Figure 25 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: ASMtoASM 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

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

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

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

ASM-INTF-MIS-110: If the mission list 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.

 

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

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

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 18 in Section 2.4.6.1 provides an overview of the Booking interface

Information Exchange Flow

Figure 19 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: ASMtoASM 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

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

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

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

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

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

N/A

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

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 15 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 16 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: ASMtoASM 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

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.

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

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 ActivityDataListRequest message from an External User.

ASM-INTF-LAS-070: If the activity data list 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.

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