The Flight Status Data Publication Interface allows a consumer to obtain updates of the ADS-C exchanges of the flights he is interested in. It provides two ways of doing so: By creating an endpoint from which a consumer can listen to updates of flights matching certain filtering criteria defined in a subscription created through the Flight Status Subscription Management Interface. In which case he will receive in its subscription response the endpoint address created specifically for his subscription. The dynamic endpoint created for a specific subscription is labelled by /<address> in this document, the specific value taken by the <address> placeholder is resolved in runtime and provided in the subscription response. By defining a number of preconfigured static endpoints where predefined filters are already applied. These preconfigured static endpoints do not require the creation of a specific subscription by the consumer, they are created in design-time by the service provider and are readily available for any consumer, subject to authorization verification. These static endpoints are labelled by /<predefinedSubscription> in this document, the specific values taken by these endpoints is defined by the service provider during design-time.
Operations
This operation allows the service provider to publish flight status updates to service consumers based on their subscriptions. By creating an endpoint from which a consumer can listen to updates of flights matching certain filtering criteria defined in a subscription created through the Flight Status Subscription Management Interface. In which case he will receive in its subscription response the endpoint address created specifically for his subscription. The dynamic endpoint created for a specific subscription is labelled by /<address> in this document, the specific value taken by the <address> placeholder is resolved in runtime and provided in the subscription response.
By defining a number of preconfigured static endpoints where predefined filters are already applied. These preconfigured static endpoints do not require the creation of a specific subscription by the consumer, they are created in design-time by the service provider and are readily available for any consumer, subject to authorization verification. These static endpoints are labelled by /<predefinedSubscription> in this document, the specific values taken by these endpoints is defined by the service provider during design-time.
Service Interface Binding
The AMQP_MESSAGING Interface Binding as detailed in the EUROCONTROL Specification for SWIM Technical Infrastructure Yellow Profile, edition 1.1
Network Interface Binding
The service shall use the network bindings of the SWIM TIYP. AMQP 1.0 shall be used to distribute messages as explained in the Publish/Subscribe Push MEP: Implementation Guidance: https://reference.swim.aero/technical-infrastructure/guidance-for-pub-s…