Ensaio 2

Modelagem de Processos - Autorização de Voo por Provedores

O processo habitual de autorização de voo por provedores deve seguir o seguinte fluxo:

0 - Fluxo.png

Fluxo de Autorização e Ativação de  Voo


Autorização de Voo

O processo de Autorização de Voo (P1) é a primeira etapa do desconflito estratégico de uma operação com drone. O processo começa com um pedido do operador. Esse pedido deve seguir um padrão (ainda não definido), e esse padrão deve ser validado pelo provedor USS. Após, o provedor deve realizar a checagem de desconflito estratégico, e por fim cadastrar o novo voo no ECO-UTM. Caso alguma checagem falhe, o provedor deve notificar o operador dessa falha. É permitido, porém não obrigatório, que o USS sugira alternativas para o operador em casos de rejeição.

1 - Autorização de Voo (1).png

P1 - Autorização de Voo

1.1 - Desconflito Estratégico (1).png

P1.1 - Desconflito Estratégico


Ativação de Voo

Após ter seu voo aprovado, o operador deve solicitar a ativação do voo instantes antes de sua execução. Nessa etapa, o provedor deve garantir que a autorização de voo continua válida, e que as condições de voo (condições ainda não definidas) permitem a realização segura do voo. Após a checagem, o USS notifica o operador que ele pode inicar a operação. 

Então, o provedor aguarda notificação do operador sobre o encerramento da operação. Recebendo a notificação, o operador deve encerrar o plano de voo no ECO-UTM.

2 - Ativação de voo (3).png

P2 - Ativação de Voo


Mudanças Dinâmicas


No período entre a autorização e a ativação, pode ocorrer mudanças nas condições do espaço aéreo, como uma nova restrição ou um novo voo com maior prioridade. Nesses casos, é de suma importância que o USS notifique o operador dessa atualização, para evitar frustrações do operador na hora da ativação do voo.

3 - Mudanças Dinâmicas (1).png

P3 - Mudanças Dinâmicas


Emergência

WIP

Briefing: BR-UTM Field Test 2

Document Version: 1.2 Date: June 16, 2025

1. Introduction & Vision

The BR-UTM Field Test 1 successfully validated the foundational capabilities of our Discovery and Synchronization Service (DSS), based on the InterUSS platform. Participants demonstrated the ability to perform basic strategic deconfliction of Operational Intent References (OIRs) and deconfliction from static Constraints.

This Second Field Test will expand upon that foundation, introducing critical new capabilities to validate the complete, end-to-end operational lifecycle. The vision is to simulate a real-world operational environment where multiple UAS Service Suppliers (USS) coordinate flights, and operators conduct live drone operations based on these coordinated intents.

1.1. New Features for Validation

This test will validate all previously tested features, plus the following crucial additions:

2. Core Objectives

The primary goals of this field test are to:

  1. Validate End-to-End OIR Lifecycle: Demonstrate the complete process of creating, strategically deconflicting, activating, and closing out OIRs in a multi-USS environment.

  2. Verify Secure Inter-USS Coordination: Ensure all participants can successfully implement and use the specified authentication protocols for all DSS and peer-to-peer USS interactions.

  3. Test Advanced Strategic Deconfliction: Validate the system's ability to manage and resolve conflicts between multiple OIRs, including those with different priorities.

  4. Demonstrate OIR Activation: Ensure that the transition of an OIR to its "activated" state is correctly propagated and managed by all relevant USSs.

  5. Validate Priority Handling: Successfully manage the introduction of a high-priority OIR, requiring other active or planned operations to be modified or cleared.

  6. Integrate Remote ID Services: Demonstrate that USSs can support the provision of Remote ID data for active flights to authorized entities.

  7. Conduct Live Flight Operations: Have operators fly drones based on successfully coordinated and activated OIRs, proving the link between the digital UTM system and real-world flight.

3. Technical Architecture & Protocols

The core of the technical architecture remains the DECEA-provided Discovery and Synchronization Service (DSS), which is an implementation of the InterUSS Platform.

3.1. Authentication

Authentication is mandatory for all inter-USS and DSS API calls. The process is detailed in the workshop documentation [Desconflito][Autenticação] Roteiro Etapa 1.

3.2. Governing Standards

This field test will adhere to the following international standards, which form the basis of the technical and operational protocols:

4. Participant Roles & Responsibilities

Participants can choose to act in one or both of the following roles:

5. Test Scenarios

The field test will be structured around a series of progressively complex scenarios.

Scenario 1: Nominal Coordination and Flight Activation

Scenario 2: Strategic Deconfliction with a Constraint

Scenario 3: Inter-USS Deconfliction & Negotiation

Scenario 4: Priority Operation (Pre-Flight)

Scenario 5: In-Flight Contingency - Dynamic Constraint

6. Operational Safety Considerations

To ensure the safety of all participants and the public, the following operational rules are mandatory for all live flights during the test.

7. Getting Started & Prerequisites

All participants must complete the following steps to be ready for the field test:

  1. Register Participation: Formally register your organization and declare your intended role(s).

  2. Review Documentation: Thoroughly read the API documentation at https://github.com/dp-icea/Protocols.

  3. Implement Authentication: Implement the JWT-based authentication client and server logic. You will be provided with API keys and the public key.

  4. Implement OIR Activation: Ensure your system correctly handles the Accepted, Activated, and Ended states of an OIR.

  5. Provide Endpoints: USS Providers must supply the base URL for their publicly accessible API so it can be registered in the DSS for peer-to-peer communication.

  6. Prepare for Flight: Operators must have their drones, ground control stations, and Remote ID broadcast modules ready for operation.

  7. Synchronize Time Servers: All USS and operator systems must synchronize their clocks with DECEA’s official NTP (Network Time Protocol) server, to be provided. Accurate, synchronized time is critical for the correct sequencing of operations, conflict detection, and logging.

We look forward to your participation in this critical test to advance the future of aviation in Brazil.