Scope of the Document

The present version of the document focuses on the e-Reporting safety function meant to provide surveillance information:

• generated by a UAS (either from the unmanned aircraft (UA) itself or its remote pilot station (RPS)),

• at destination of other UAS and/or U-space services².

As such, this document covers solutions for safety purposes only (e.g., hazards de-confliction), not for security purposes (e.g., law enforcement, homeland protection, general public privacy).

Solutions compliant with the specification contained in this document could be used for:

• Operations within EASA Open, Specific or Certified categories

• Operations conducted in visual line of sight (VLOS) and beyond visual line of sight (BVLOS)

• Operations conducted in Very Low Level (VLL)

The following are considered out of the scope of this document:

• Specification of Direct Remote Identification for security purposes (e.g., law enforcement, homeland protection, general public privacy), as requested in the open category by European Commission Delegated Regulation (EU) 2020/639 [Ref 3]; this specification is covered by ASD-STAN [Ref 17] and derived from ASTM F3411-19 [Ref 19]

• Specification of Network Identification for security purposes, as specified by European Commission Delegated Regulation (EU) 2020/639; this specification may be derived in Europe from ASTM F3411-19 [Ref 19]

• Specification of U-space Services, incl. Network Identification and other related services (e.g., Traffic Information and Conformance Monitoring)

• Solutions for other users than UAS (e.g., fix or mobile obstacles, manned aircraft operating in VLL airspace) although they could possibly be equipped with a solution compliant with the specification contained in this document

NOTE: Some of the data elements transmitted by the e-Reporting function for safety purposes may be common with data elements transmitted by the Network Identification functions for security purposes. This document leaves the opportunity for those manufacturers who would prefer to merge both functions to do so. Classes of e-Reporting systems/devices along with data elements recommended to support the different U-space services are discussed later in this document.

NOTE: At the time of the drafting of this document, U-space Services and related systems (incl. Network Identification add-on devices) are not yet regulated. Changes might occur as necessary in the future as technologies mature, systems and services are deployed and regulations evolve.

The document is structured as follows:

CHAPTER 1 “GENERAL” of this document provides information required to understand the need for the equipment characteristics and tests defined in the remaining chapters. It describes typical equipment applications and operational objectives and is the basis for the performance criteria stated in CHAPTER 2 to CHAPTER 4. Definitions essential to proper understanding of this document are also provided in CHAPTER 1.

CHAPTER 2 “GENERAL DESIGN REQUIREMENTS” contains general design requirements.

CHAPTER 3 “MINIMUM PERFORMANCE SPECIFICATION UNDER STANDARD CONDITIONS” contains the minimum performance specification for the equipment, defining performance under standard operating conditions.

CHAPTER 4 “MINIMUM PERFORMANCE SPECIFICATION UNDER ENVIRONMENTAL TEST CONDITIONS” prescribes the environmental test conditions, which provide a laboratory means of determining the overall performance characteristics of the equipment under conditions representative of those, which may be encountered in actual operations.

CHAPTER 5 “TEST PROCEDURES” describes recommended test procedures for demonstrating compliance with CHAPTER 3 and CHAPTER 4.

CHAPTER 6 “INSTALLED EQUIPMENT PERFORMANCE” specifies the performance required from the installed equipment. Ground and flight tests for the installed equipment are included when performance cannot be adequately determined through testing under standard test conditions.

APPENDIX A, “OPERATIONAL SERVICES AND ENVIRONMENT DESCRIPTION (OSED)”, describes the operational environment as well as U-space services.

APPENDIX B, “SAFETY AND PERFORMANCE REQUIREMENTS (SPR)”, is a placeholder for a future Safety and Performance Requirements (SPR) section.

APPENDIX C, “INTEROPERABILITY REQUIREMENTS (INTEROP)”, is a placeholder for a future Interoperability Requirements (INTEROP) section.

APPENDIX D, “INSTALLATION REQUIREMENTS”, is a placeholder for a future section detailing installation requirements.

APPENDIX E, “CANDIDATE TECHNOLOGIES” will be completed as different candidate technologies mature and/or are mandated.

APPENDIX F, “INFORMATION AND USAGE” provides a summary of mandatory and optional information aimed at supporting the different U-space services.

APPENDIX G, “INFORMATION SOURCES” provides a summary of possible sources of the different information to build the e-Reporting dataset.

APPENDIX H, “[PRELIMINARY] PROTOCOL SPECIFICATION – NETWORK” provides a [preliminary] protocol specification for the transmission of e-Reporting data elements to the U-space supporting infrastructure³ over LTE for instance. A Vehicle-to-Vehicle (V2V) protocol specification will be dealt with later for the deployment of Detect and Avoid (DAA) Services.

Operational performance standards for functions or components that refer to equipment capabilities that exceed the stated minimum requirements are identified as optional features.

The word ‘equipment’ as used in this document includes all components and units necessary for the system to properly perform its intended function(s). For example, the ’equipment’ may include antennas, transceivers, batteries, GNSS receivers, or processing units. In the case of this example, all the foregoing components and units comprise the ’equipment’. It should not be inferred from this example that each e- Reporting system/device design will necessarily include all the foregoing components or units. This will depend on the specific design chosen by the manufacturer.

This MOPS applies to a specific defined function. The equipment may have additional features related to that function for which there are no specified minimum performance requirements. Equipment may also have additional functions for which other MOPS or European Technical Standard Orders (ETSO) may be applicable or, it may contain additional functions not defined by any MOPS or ETSO, and non ETSO function guidance may be applicable.

² Similar concepts to U-space in Europe exist worldwide such as UAS Traffic Management (UTM) in the US or Flight Information and Notification System (FINS) in the UK.

³ The supporting infrastructure encompasses all technologies, assets and systems (e.g., antennas, radios, networks, etc.) that will provide information exchange among U-space actors.