This document aims at providing the description of the drone aeronautical information management SWIM service. The drone aeronautical information management service provided by ENAIRE CISP is responsible for distributing updated UAS geographical zones (UGZs) to USSPs so that they can provide geo-awareness service to their UAS operators. Drone aeronautical information management Service is also responsible for distributing the U-space airspace volumes as well as the dynamic airspace reconfigurations (DAR) applicable to any of the U-space airspace volumes already in the system.
This Service Description defines and describes the interfaces provided by the Drone Aeronautical Information Management service provided by ENAIRE CISP when there is a deviation comparing to the EUROCAE ED-318 standard regarding the extended properties modification as well as the extension of the restriction conditions. These interfaces are defined and described in terms of protocol, endpoints, security, and data, so that the full information not covered by EUROCAE ED-318 standard is fully presented.
ENAIRE is the leading air navigation and aeronautical information service provider in Spain. ENAIRE is the fourth most important European air traffic manager and is in a clear commitment to the Single Sky initiative. The company manages the Spanish airspace over a territory of 2.19 MN square kilometres. and provides air traffic services to 2.1 million flights to and from four continents (Europe, America, Asia and Africa), carrying 300 million passengers each year. Through five control centres, 21 control towers and a comprehensive network of aeronautical infrastructure and equipment, ENAIRE provides en-route, approach and aerodrome ATC services, as well as flight information, alerts and consulting services. ENAIRE is the communications, navigation and surveillance service provider across the whole of the Spanish airspace and at airports in Aena network.
", "type": [ "CIVIL_AIR_NAVIGATION_SERVICE_PROVIDER" ] }, "serviceCategorisation": { "businessActivityType": [ "AIRSPACE_ORGANISATION_AND_MANAGEMENT", "INFORMATION_MANAGEMENT" ], "intendedConsumer": [ "AERONAUTICAL_INFORMATION_SERVICE_PROVIDER", "AIR_TRAFFIC_SERVICE_PROVIDER", "AIRSIDE_GROUND_HANDLER", "CIVIL_AIR_NAVIGATION_SERVICE_PROVIDER", "PROVIDER_OF_DATA_SERVICES" ], "informationCategory": [ "AERONAUTICAL_INFORMATION_EXCHANGE" ], "applicationMessageExchangePattern": [ { "name": "Request-Response" }, { "name": "Publish-Subscribe" } ], "geospatialCategorisation": { "fir": [ "EUR", "AFI" ] }, "lifeCycle": [ { "lifeCycleStage": "PROSPECTIVE" } ] }, "generalDescription": { "operationalEnvironment": { "operationalNeeds": [ { "name": "UAS Zones Provision", "description": "According to Implementing Regulation (EU) 2021/664 in its article 5, the Common Information Service Provider (CISP) shall make all UAS geographical zones (UGZ) relevant to the U-space airspace available to U-space Service Providers (USSPs) and competent authorities. The UAS geographical zones (UGZs) include the static and dynamic airspace restrictions defined by the relevant authorities along with the U-space airspace.
The Drone Aeronautical Information Management (DAIM) service supports the retrieval and the management of the subscription to the service through the capabilities presented in Capabilities section. Thus, throughout this service, USSPs can provide up to date data to UAS operator regarding to the UAS geographical zones (UGZs) so that they can plan their operations knowing all the possible restrictions within the U-space airspace.
Retrieve all available UAS Zone information from a particular moment when initiating or recovering from a shutdown.
" }, { "name": "Subscriptions", "description": "Allows to manage (activate, pause, or delete) subscriptions regarding UAS zone information updates.
" }, { "name": "Data update", "description": "Receive all UAS zone information updates for a region of interest according to active subscriptions.
" } ] }, "functionality": [ { "name": "Initial update", "description": "Retrieve all available UAS Zone information from a particular moment when initiating or recovering from a shutdown.
", "realWorldEffect": "The system can get all the information that needs regarding the UAS Zones." }, { "name": "Subscriptions", "description": "Allows to manage (activate, pause, or delete) subscriptions regarding UAS zone information updates.
", "realWorldEffect": "The system activates and start to receive the UAS Zone information in the framework of the subscription. " }, { "name": "Data update", "description": "Receive all UAS zone information updates for a region of interest according to active subscriptions.
", "realWorldEffect": "The client receives the updates regarding the UAS Zones in its active subscriptions." } ], "accessAndUseConditions": [ { "name": "Conditions of Service Provision", "type": "OTHER", "description": "This specification has been developed under ENAIRE U-space system definition. It is maintained by ENAIRE in line with ENAIRE’s definition and description standards.
ENAIRE is the main provider of air navigation and aeronautical information services in Spain. As a state-owned company of the Ministry of Transport and Sustainable Mobility, ENAIRE manages Spanish airspace, provides en-route and approach air traffic services to aircraft throughout Spanish airspace, aerodrome control services in 21 airports, as well as flight information, alert, and guidance services. ENAIRE is also the provider of communications, navigation, and surveillance services throughout Spanish airspace and in the airports of the Aena network. Moreover, all the services provided by ENAIRE are attached to ENAIRE’s services access and use conditions, including the legal constraints, service policies and the service consumption constraints. For further information, please contact ENAIRE at info@enaire.es.
Refer to EUROCAE ED-318 Section 3.2.1. for performance-of-service requirements.
" } ], "reliability": [ { "name": "Reliability", "description": "The retrieval interface requires a network that conforms to the “IPv4 unicast” network interface binding specification as described in EUROCONTROL Specification for SWIM TI YP, which ensures the reliability of the information exchange.
The publication interface requires a network that conforms to the “IPv4 unicast” network interface binding specification as described in EUROCONTROL Specification for SWIM TI YP, which ensures the reliability of the information exchange.
The retrieval interface requires conformance with requirement specified in the “WS-Light” service interface binding specification as described in EUROCONTROL Specification for SWIM TI UP. This binding specification provides requirements for the transport of information using HTTP over TLS, which ensures the integrity and confidentiality of the information.
The publication interface requires conformance with requirement specified in the “AMQP Messaging” service interface binding specification as described in EUROCONTROL Specification for SWIM TI YP. This binding specification provides requirements for the transport of information including requirements for the use of AMQP 1.0 over TLS, which ensures the integrity and confidentiality of the information.
" } ] }, "dateInOperation": "2026-05-01", "validation": [ { "type": "SELF_VALIDATION", "description": { "validationSteps": "The service was validated following the steps consolidated in Test Procedure SRS and Test Procedure SRD, property of ENAIRE.\r\nFor further details, please contact with ENAIRE.", "validationResults": "The service adheres to pre-defined validation rules.", "evidence": "The report with the actual results is property of ENAIRE.\r\nFor further details, please contact with ENAIRE." } } ], "abbreviations": [ { "name": "AIM", "description": "Aeronautical Information Management
\r\n" }, { "name": "AIS", "description": "Aeronautical Information Service
\r\n" }, { "name": "AMC", "description": "Acceptable Means of Compliance
\r\n" }, { "name": "API", "description": "Application Programming Interface
\r\n" } ] }, "informationDescription": { "informationDefinition": { "reference": [ { "description": "For more information, get in contact in the following e-mail
\r\n", "url": "https://enairecisp.enaire.es" } ] } }, "technicalDescription": { "technicalConstraint": [ { "name": "Security Constraints", "description": "The Drone Aeronautical Information Management Service (DAIM) applies authentication methods along with security process such as Transport Layer Security (TLS) version 1.2 or later in accordance with EUROCONTROL Specification for SWIM Technical Infrastructure (TI) Yellow Profile.
As EUROCONTROL Specification for SWIM Technical Infrastructure (TI) Yellow Profile states, the certifications used in the authentication process cannot be self-signed certifications and they shall use a X.509 certificate. Moreover, it is important to note that all the endpoints are using secured protocols and therefore, the standard secure port must be used.
This service provides two kinds of interfaces:
-
RESTful API: this kind of interface requires OAuth2.0 authorisation and authentication methods as well as OAuth2.0 extension methods for authentication. It is highly recommended to use OpenID Connect (OICD) when OAuth2.0 extension is required for authentication. For further information, please refer to EUROCAE ED-318 standard ([12.]).
-
AMQPS messaging: the user shall authenticate to the broker using user and password authentication to subscribe to the interface and receive the updated information. For further information, please refer to EUROCAE ED-318 standard ([12.]).
The U-Hub Health Status Service described in Specification for Health status SWIM service - U-HUB ([8.]) is provided as a heartbeat service to periodically check the status of the DAIM service – among others – and determine whether it is available.
\r\n", "reference": { "description": "Specification document where the service for the monitoring of DAIM services is described.
\r\n", "url": "https://pending.enaire.es" } }, "behaviour": [ { "name": "Getting an initial baseline of UAS Geographical Zone Information and then receive updates ensuring there are no information gaps between the initial baseline and the updates.", "description": "The consumer invokes the Srv_UHUB_DAIM_Data_Initial_Update interface – the retrieval interface – to receive an initial baseline of UAS Geographical Zone information for a period and a region of interest. Having an initial baseline, the consumer can invoke the Srv_UHUB_DAIM_Subscription interface – the subscription interface – to create a subscription. The provider will create a resource to manage the subscription in PAUSED status and a queue where it will make available to the user updates to the UAS Geographical Zone Information through the Evt_UHUB_DAIM_Data_Update interface – the publication interface. Once the subscription resource is created, the consumer will be able to delete it at any time by unsubscribing through the subscription interface.
To activate the subscription, the consumer will request to resume the subscription through the subscription interface to the provider, who will change the subscription status to ACTIVE, indicating that updates of UAS Geographical Zone information will start to be delivered via the publication interface. The subscription can be paused again by the consumer or the provider due to different reasons through the subscription interface.
The update event is carried out only when the subscription process state is ACTIVE. Thus, the USSP receives any update regarding to the following data models:
-UAS zones: it represents the volumes where specific restrictions apply.
-U-space airspace: it represents the volume where the Implementing Regulation (EU) 2021/664 ([9.]) applies.
-Dynamic airspace reconfiguration: it represents the volumes within the U-space airspace that require to be deactivated due to ATM requirements. It could affect the whole U-space airspace if required.
To ensure there are no information gaps between the retrieval of the initial baseline and the reception of updates via the publication interface once the subscription is active, is expected that the consumer invokes the retrieval interface again, specifying in the period of intertest the time provided in the initial retrieval.
In the case there has been an interruption (for example: connectivity lost, or the subscription has been paused by the provider), is expected that the consumer invokes the subscription interface to resume the subscription and start getting updates again, after the connection to the queue is re-established.
To ensure that updates since the last time the system was known to be working properly are not lost, is expected that the consumer invokes the retrieval interface specifying the time since when recovery is required.
This standard covers UAS geographical zones data defined in Article 15 of the Implementing Regulation (EU) 2019/947.
", "standardType": "SERVICE_STANDARD", "conformanceStatement": "The service described here conforms with this standard referenced here: ED-318.", "reference": { "url": "https://www.eurocae.net/product/ed-318-technical-specification-for-geographical-zones-and-u-space-data-provision-and-exchange/" } } ] }, "serviceInterface": [ { "name": "Srv_UHUB_DAIM_Data_Initial_Update", "description": "This interface allows the consumer to retrieve all the UAS zones available as well as an update after performing the subscription process, as EUROCAE ED-318 ([12.]) standard states.
", "provisionSide": "PROVIDER_SIDE", "operations": [ { "name": "Retrieve UAS zones", "description": "This interface allows the consumer to retrieve all the UAS zones available as well as an update after performing the subscription process, as EUROCAE ED-318 ([12.]) standard states.
", "messages": [ { "name": "Request message", "direction": "OUT" }, { "name": "Successful response message", "direction": "OUT" }, { "name": "Error response message", "direction": "OUT" } ] } ], "serviceInterfaceBinding": { "name": "SWIM_TI_YP_4_3_WS_LIGHT" }, "networkInterfaceBinding": { "name": "The service shall use the network bindings of the SWIM TIYP." }, "messageExchangePattern": "REQUEST_REPLY" }, { "name": "Srv_UHUB_DAIM_Subscription", "description": "This interface allows the consumer to manage the subscription to DAIM service. All the endpoints available within this interface follows the SWIM TI Profile and interface bindings defined hereafter.
", "provisionSide": "PROVIDER_SIDE", "operations": [ { "name": "Subscribe", "description": "This interface allows the consumer to manage the subscription to DAIM service. All the endpoints available within this interface follows the SWIM TI Profile and interface bindings defined hereafter.
", "messages": [ { "name": "Request message", "direction": "OUT" }, { "name": "Successful response message", "direction": "OUT" }, { "name": "Error response message", "direction": "OUT" } ] }, { "name": "Resume", "description": "This interface allows the consumer to resume the subscription to DAIM service.
", "messages": [ { "name": "Request message", "direction": "OUT" }, { "name": "Successful response message", "direction": "OUT" }, { "name": "Error response message", "direction": "OUT" } ] }, { "name": "Unsubscribe", "description": "This interface allows the consumer to unsubscribe the subscription to DAIM service.
", "messages": [ { "name": "Successful response message", "direction": "OUT" }, { "name": "Error response message", "direction": "OUT" } ] }, { "name": "Pause", "description": "This interface allows the consumer to pause the subscription to DAIM service.
", "messages": [ { "name": "Request message", "direction": "OUT" }, { "name": "Successful response message", "direction": "OUT" }, { "name": "Error response message", "direction": "OUT" } ] } ], "messageExchangePattern": "REQUEST_REPLY" }, { "name": "Evt_UHUB_DAIM_Data_Update", "description": "This interface provides the updates to the consumer regarding to the UAS zones as per EUROCAE ED-318 standard ([12.]) claims.
", "provisionSide": "PROVIDER_SIDE", "operations": [ { "name": "Update UAS Zones", "description": "This operation provides the updates to the consumer regarding to the UAS zones as per EUROCAE ED-318 standard ([12.]) claims.
", "messages": [ { "name": "Message", "direction": "OUT" } ] } ], "messageExchangePattern": "FIRE_AND_FORGET" } ] } }