Engineering PapersSearch

Engineering topics

Venkatesan, Priya

Publications and source records attributed to Venkatesan, Priya.

UAS Service Supplier Network Performance

This report summarizes the performance of Unmanned Aircraft System (UAS) Service Suppliers (USS) in the Technical Capability Level 4 (TCL4) flight test performed by NASA and its partners in support of the UAS Traffic Management (UTM) concept. TCL4 is the final in a series of TCL demonstrations of a traffic management system for small UAS (sUAS). All demonstrations have been executed in collaboration with industry partners. The [FAA 2018] UTM Concept of Operations document describes UTM as:...the manner in which the FAA will support operations for predominantly sUAS operating in low altitude airspace. UTM utilizes industry’s ability to supply services under FAA’s regulatory authority where these services do not currently exist. It is a community-based traffic management system, where the Operators are responsible for the coordination, execution, and management of operations, with rules of the road established by FAA. UTM is designed to support the demand and expectations for a broad spectrum of operations with ever-increasing complexity and risk. UTM should be considered a collection of services rather than a monolithic application. The following section describes the architecture at a high level. For further insight, the FAA’s concept document [FAA 2018] or NASA’s earlier concept publication [NASA 2016] should be consulted.

Rios, Joseph L.

UAS Service Supplier Specification

Within the Unmanned Aircraft Systems (UAS) Traffic Management (UTM) system, the UAS Service Supplier (USS) is a key component. The USS serves several functions. At a high level, those include the following: Bridging communication between UAS Operators and Flight Information Management System (FIMS) Supporting planning of UAS operations Assisting strategic deconfliction of the UTM airspace Providing information support to UAS Operators during operations Helping UAS Operators meet their formal requirements This document provides the minimum set of requirements for a USS. In order to be recognized as a USS within UTM, successful demonstration of satisfying the requirements described herein will be a prerequisite. To ensure various desired qualities (security, fairness, availability, efficiency, maintainability, etc.), this specification relies on references to existing public specifications whenever possible.

Rios, Joseph L.

UAS Service Supplier Framework for Authentication and Authorization

The Unmanned Aircraft Systems (UAS) Traffic Management (UTM) Service Supplier (USS) Framework for Authentication and Authorization (UFAA) is the basis for secure and confident data exchanges between the Flight Information Management System (FIMS) and the USS Network and within the USS Network itself. UFAA is built upon the OAuth 2.0 approach to federated authorization, with details supplied by various Internet Engineering Task Force (IETF) Request for Comment documents (RFCs). Whenever possible, a specific standard is used to support a design decision within UFAA, and when an applicable standard is not found/used, the technical decision is explained as much as possible. This document describes UFAA in detail. It is intended to serve as a reference for other key UTM documents and should be useful to many UTM stakeholders. This is an informative document. The requirements stated or implied in this document will need to be fully vetted and reviewed by appropriate stakeholders before becoming operational. It is highly encouraged that in any design decisions for future applicable standards that are counter to or missing from the decisions presented herein be justified in that future standard.

UTM

Remote ID for Rapid Assessment of Flight and Vehicle Information

The ability to rapidly identify UAS (Unmanned Aircraft Systems) in the field has emerged as a critical need for the integration of small UASs into the national airspace and counter-UAS operations. This paper proposes an architecture for rapid retrieval of UAS information leveraging NASA's current Unmanned Aircraft System (UAS) Traffic Management (UTM) system. The proposed architecture utilizes UTM components: FIMS (Flight Information Management System), USS (UAS Service Supplier), and vehicle registration and model database in order to provide assessment of the UAS reported in the field including the ability to distinguish between participating and non- participating UTM actors. Detailed system descriptions are provided and preliminary results from field tests conducted during UTM TCL (Technical Capability Level) 3 are discussed. It is found that 94 percent of the remote ID look-ups were successful. The average time of a look-up is found to be 1.2 seconds. Failure cases are examined and recommendations on next steps to advance UAS remote identification are provided.

USS (UAS Service Supplier)

Remote ID for Rapid Assessment of Flight and Vehicle Information

The ability to rapidly identify UAS in the field has emerged as a critical need for the integration of small UASs into the national airspace and counter-uas operations. This paper proposes an architecture for rapid retrieval of UAS information leveraging NASA's current Unmanned Aircraft System (UAS) Traffic Management (UTM) system. The proposed architecture utilizes UTM components: FIMS (Flight Information Management System), USS (UAS Service Supplier), and vehicle registration and model database in order to provide assessment of the UAS reported in the field including the ability to distinguish between participating and non- participating UTM actors. Detailed system descriptions are provided and preliminary results from field tests conducted during UTM TCL (Technical Capability Level) 3 are discussed. It is found that 94% of the remote ID look-ups were successful. The average time of a look-up is found to be 1.2 seconds. Failure cases are examined and recommendations on next steps to advance UAS remote identification are provided.

Ishihara, Abraham K.

UTM UAS Service Supplier Development: Sprint 2 Toward Technical Capability Level 4

NASA's UAS Traffic Management (UTM) Project has been tasked with developing concepts and initial implementations for integrating and managing small unmanned aircraft systems (UAS) into the low altitude airspace. To accomplish this task, the UTM Project planned a phased approach based on four Technical Capability Levels (TCLs). As of this writing, TCL4 is currently in development for a late Spring 2019 flight demonstration. This TCL is focused on operations in an urban environment and includes the handling of high density environments, large-scale off-nominal conditions, vehicle-to-vehicle communications, detect-and-avoid technologies, communication requirements, public safety operations, airspace restrictions, and other related goals. Through research and testing to date, NASA has developed an architecture for UTM that depends on commercial entities collaboratively providing services that are traditionally provided by the Air Navigation Service Provider (ANSP) in manned aviation. A key component of this architecture is the UAS Service Supplier (USS), which acts as a communications bridge between UAS operators and the ANSP when necessary. In addition, the collection of USSs form a USS Network to collaboratively manage the airspace through the sharing of data and the adherence to a standard or set of standards required to participate in this USS Network. This document provides a record of the second of four planned steps in the development of interoperable USSs that will ultimately support TCL4 flight testing and formalization of the overall UTM concept. To develop these USSs and their underlying specifications, NASA has planned a series of "Sprints" to work with industry partners in implementing the features and develop proposed specifications for USSs in order to to participate in TCL4. This report describes Sprint Two. In this Sprint, there was a major theme with four goals. The theme was the development and testing of a new USS discovery system, to better enable USSs to find and communicate with each other. The goals supporting this theme were: participants needed to implement and exercise the discovery service for USS-USS communications; USSs needed to demonstrate strategic deconfliction through operation sharing; the systems were to use discovery to aid in handling off-nominal operations; and finally, there was an investigation of an initial off-nominal reporting capability.

software engineering

UTM UAS Serivce Supplier Development: Sprint 1 Toward Technical Capability Level 4

NASA's UAS Traffic Management (UTM) Project has been tasked with developing concepts and initial implementations for integrating and managing small unmanned aircraft systems (UAS) into the low altitude airspace. To accomplish this task, the Project planned a phased approach based on four Technical Capability Levels (TCLs). As of this writing, TCL4 is currently in development for a late Spring 2019 flight demonstration. This TCL is focused on operations in an urban environment and includes the handling of high density and large-scale off-nominal conditions, vehicle-to-vehicle communications, detect-and-avoid technologies, communication requirements, public safety operations, airspace restrictions, and other related goals. Through research and testing to date, NASA has developed an architecture for UTM that depends on commercial entities collaboratively providing services that are traditionally provided by the Air Navigation Service Provider(ANSP) in manned aviation. A key component of this architecture is the UAS Service Supplier (USS), which acts as a communications bridge between UAS operators and the ANSP when necessary. In addition, the collection of USSs form a USS Network to collaboratively manage the airspace through the sharing of data and the adherence to a standard or set of standards required to participate in this USS Network. This document provides a record of the first step in the development of interoperable USSs that will ultimately support TCL4 flight testing and formalization of the overall UTM concept. To develop these USSs and the underlying specifications for them, NASA has planned a series of "Sprints" to work with industry partners in implementing the features and proposed specifications for USSs to participate in TCL4. This report describes Sprint One. In this Sprint, the focus was on establishing a baseline for the Application Programming Interfaces (APIs) and their associated data models. In addition, the concept of UAS Volume Reservations (UVR) (areas that impose restrictions on sUAS that are allowed to operate) was tested. NASA provided the specifications and iterated on them with partners while implementers developed to those specifications. NASA then tested each partner's implementation to ensure compatibility with all other implementers. This process helped all stakeholders gain confidence that the foundation for future Sprints was solid.

UAS service supplier

UTM TCL2 Software Requirements

The Unmanned Aircraft Systems (UAS) Traffic Management (UTM) Technical Capability Level (TCL) 2 software implements the UTM TCL 2 software requirements described herein. These software requirements are linked to the higher level UTM TCL 2 System Requirements. Each successive TCL implements additional UTM functionality, enabling additional use cases. TCL 2 demonstrated how to enable expanded multiple operations by implementing automation for beyond visual line-of-sight, tracking operations, and operations flying over sparsely populated areas.

Smith, Irene S.

NASA UAS Traffic Management National Campaign Operations across Six UAS Test Sites

NASA's Unmanned Aircraft Systems Traffic Management research aims to develop policies, procedures, requirements, and other artifacts to inform the implementation of a future system that enables small drones to access the low altitude airspace. In this endeavor, NASA conducted a geographically diverse flight test in conjunction with the FAA's six unmanned aircraft systems Test Sites. A control center at NASA Ames Research Center autonomously managed the airspace for all participants in eight states as they flew operations (both real and simulated). The system allowed for common situational awareness across all stakeholders, kept traffic procedurally separated, offered messages to inform the participants of activity relevant to their operations. Over the 3- hour test, 102 flight operations connected to the central research platform with 17 different vehicle types and 8 distinct software client implementations while seamlessly interacting with simulated traffic.

UTM