This deliverable describes the GOF2.0 information exchange services documented at conceptual level, following SWIM principles, which could be used to implement U-space airspace, following guidance material to (EU 664/2021). For each service specification there is a separate document. These documents are embedded in this document, which acts as bucket. As a preview, the data model of each service specification is copied into this document.
The service specifications are a baseline, built on experience from previous projects and the GOF2.0 project execution.
They have been updated based on D2.2, with better understanding gained in integration and trials. Updates were performed in agreement between the GOF2.0 project partners, which could be considered a governance body for the project execution time.
This deliverable describes the GOF2.0 information exchange services documented at conceptual level, following SWIM principles, which could be used to implement U-space airspace, following guidance material to (EU 664/2021).
For each service specification there is a separate document. These documents are embedded in this document, which acts as bucket. As a preview, the data model of each service specification is copied into this document.
The service specifications are a baseline, built on experience from previous projects and the GOF2.0 project execution.
This specification introduces a service of a Common Information Service (CIS) which ensures
interoperability and hence transparent and reliable information flow between the stakeholders in an operational U-space environment. In accordance with ICAO SWIM, represents an Information Exchange Service.
Specifically, this document describes, in a logical, technology-independent manner, the Traffic/Telemetry service, a Position report Submission Sub-Service and Surveillance Data Service which accepts and carries surveillance data from a number of data sources to a Tracking Service which, in turn, provides a common situational picture to its consumers via this service.
Sources include, but are not limited to, primary and secondary radar and other drone detection
services, on-board position telemetry services, and tracking service,
Consumers include, but are not limited to monitoring and traffic information services, tracking
services, and display systems.
This specification introduces a service of a Common Information Service (CIS) which ensures interoperability and hence transparent and reliable information flow between the stakeholders in an operational U-space environment. In accordance with ICAO SWIM, represents an Information Exchange Service.
This document describes one of these Bridge Services, the Operation Plan Exchange service in a logical, technology-independent manner.
This specification introduces a service of a Common Information Service (CIS) which ensures
interoperability and hence transparent and reliable information flow between the stakeholders in an operational U-space environment. In accordance with ICAO SWIM, represents an Information Exchange Service.
This document describes one of these Bridge Services, the Geozones Exchange service in a logical, technology-independent manner.
This specification introduces a service of a Common Information Service (CIS) which ensures interoperability and hence transparent and reliable information flow between the stakeholders in an operational U-space environment. In accordance with ICAO SWIM, represents an Information Exchange Service.
This document describes one of these Bridge Services, the Registration service in a logical, technologyindependent manner.
This specification introduces an information exchange service which ensures interoperability and hence transparent and reliable information flow between the stakeholders in an operational U-space environment.
In accordance with ICAO SWIM, this document describes one of these Bridge Services, the Operational Message Exchange service in a logical, technology-independent manner.
This specification introduces a service of a Common Information Service (CIS) which ensures interoperability and hence transparent and reliable information flow between the stakeholders in an operational U-space environment. In accordance with ICAO SWIM, represents an Information Exchange Service.
This document describes one of these Bridge Services, the Traffic Conformance Monitoring Exchange service in a logical, technology-independent manner.
The Network Coverage service provides information about current and expected data connectivity conditions along a flight route or in a geographical area of interest.
It provides information where connectivity conditions are or are not good enough for safe and reliable data connectivity that adheres to a certain service level, provided by individual communication service providers.
Provided connectivity conditions are provided in terms of quality and performance of network and C2 link data communication between drones and ground stations, as well as coverage information for cellular networks. Targeted service consumers include aviation organisations, drone operators and end users.
This specification introduces a service of a Common Information Service (CIS) which ensures
interoperability and hence transparent and reliable information flow between the stakeholders in an operational U-space environment. In accordance with ICAO SWIM, represents an Information Exchange Service.
This document describes one of these Bridge Services, the Drone Flight Exchange service in a logical, technology-independent manner.
This specification introduces a Supplementary data service which ensures appropriate weather data is accessible in a reliable manner to all stakeholders within the U-space environment. In accordance with ICAO SWIM, this document describes one of these supplementary data Services, the Weather data service in a logical, technology-independent manner.
This deliverable provides an overview of the GOF2.0 design and architecture. It serves as the architectural interoperability blueprint for the actual demonstrations. Information exchange services based on SWIM Standards within the defined Architecture are identified and the actual realisation of the blueprint for an example trial is laid out.
This deliverable the GOF2.0 describes information exchange services documented at conceptual level, following SWIM principles. For each service specification there is a separate document embedded describing the data model. Currently, the following information exchange services are available:
• Traffic/Telemetry (Appendix A)
• Operation Plan (Appendix B)
• Geozones (Appendix C)
• Registration (Appendix D)
• Operational Message (Appendix E)
• Traffic Conformance Monitoring (Appendix F)
• Network Coverage (Appendix G)
The service specifications are a baseline, built on experience from previous projects and the initial project phase of GOF2.0. The deliverable will be updated with better understanding gained in technical integration and validation exercises (Q3 2022).
Cookie | Duration | Description |
---|---|---|
cookielawinfo-checbox-analytics | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics". |
cookielawinfo-checbox-functional | 11 months | The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional". |
cookielawinfo-checbox-others | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other. |
cookielawinfo-checkbox-necessary | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary". |
cookielawinfo-checkbox-performance | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance". |
viewed_cookie_policy | 11 months | The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data. |