Search NASASearch

Engineering topics

Rios, Joseph L.

Publications and source records attributed to Rios, Joseph L..

Small Unmanned Aircraft System Off Nominal Operations Reporting System Unmanned Aircraft System: Traffic Management Technical Capability Level 4 Implementation, Data Collection and Analysis

NASA performed research and development of technologies and requirements for traffic management of small Unmanned Aircraft Systems (UAS). In this effort, a small UAS off-nominal situation reporting system was developed to capture information from off-nominal situations to understand their nature and reduce occurrences. This Technical Memorandum (TM) describes the reporting system and analysis of 116 off-nominal situation reports from 352 small UAS operations, which were conducted at two flight test ranges in Summer 2019.

Jung, Jaewoo

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 Checkout: How UTM Confirmed Readiness of Flight Tests with UAS Service Suppliers

NASA collaborated with industry partners to develop and test the small Unmanned Aircraft System (sUAS) Traffic Management (UTM) research platform, a software prototype used for developing airspace integration requirements for sUAS operations. The lessons learned from these activities will help inform the Federal Aviation Administration (FAA) on what is needed to safely manage sUAS operations. A core component of the UTM platform is the UAS Service Supplier (USS), which acts as a communications bridge to meet the regulatory and operational requirements. As the UTM partners began USS flight tests, NASA found that it was difficult to get all USSs functioning at comparable quality levels to ensure successful flight tests. Also, NASA anticipated that the FAA would encounter similar challenges when they begin to register USSs for operational use. These realizations led to the development of USS Checkout, a set of processes and tools designed to increase flight test efficiency. We learned that a good USS Checkout process is balanced for simplicity versus test coverage, and is amenable to automation. We also learned that when USS Checkout is a USS prerequisite for flight tests, flight tests were more efficient and effective.

Smith, Irene Skupniewicz

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

Use of UAS Reports (UREPs) during TCL3 Field Testing

During the NASA Unmanned Aircraft System (UAS) Traffic Management (UTM) Project’s Technical Capability Level 3 (TCL3) demonstration, a service for stakeholders to share weather and aircraft observations was tested. The overall goal was to increase awareness of airspace and weather activity to increase a pilot’s ability to fly safely. To achieve this goal, a mechanism to share data was created, called “UAS Reports” or UREPs, which were generated by client systems and sent to a central data service. The data service provided subscriptions and allowed for data requests to share the reports that had been sent in by stakeholders. To execute this functionality, four FAA (Federal Aviation Administration)-designated UAS test sites performed UREP testing as part of TCL3. NASA provided the centralized service and test site partners flew missions and simulated activity at the test sites to generate data to send to the service. The loop was closed by having other clients (usually other small UAS operators) request those data from the service or subscribe to feeds from the service. Overall, the tests demonstrated the utility of such a service. In this report, the testing setup, data collection, and analysis of results are presented. The concept of UREPs has since been incorporated as a service within NASA’s Conflict Mitigation Model for UTM. The concept will continue to be tested in NASA’s TCL4 activities.

UTM

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

FAA/NASA UAS Traffic Management Pilot Program (UPP)

NASA Ames is leading ATM R&D organization. NASA started working on UTM in 2012, it's come a long way primarily due to close relationship with FAA and industry. We have a research transition team between FAA and NASA for UTM. We have a few other RTTs as well. UTM is a great example of collaborative innovation, and now it's reaching very exciting stage of UTM Pilot Project (UPP). NASA is supporting FAA and industry to make the UPP most productive and successful.

Johnson, Ronald D.

Unmanned Aircraft Systems (UAS) Traffic Management (UTM) National Campaign II

The Unmanned Aircraft System (UAS) Traffic Management (UTM) effort at NASA aims to enable access to low-altitude airspace for small UAS. This goal is being pursued partly through partnerships that NASA has developed with the UAS stakeholder community, the FAA, other government agencies, and the designated FAA UAS Test Sites. By partnering with the FAA UAS Test Sites, NASA's UTM project has performed a geographically diverse, simultaneous set of UAS operations at locations in six states. The demonstrations used an architecture that was developed by NASA in partnership with the FAA to safely coordinate such operations. These demonstrations-the second or 'Technical Capability Level (TCL 2)' National Campaign of UTM testing-was performed from May 15 through June 9, 2017. Multiple UAS operations occurred during the testing at sites located in Alaska, Nevada, Texas, North Dakota, Virginia, and New York with multiple organizations serving as UAS Service Suppliers and/or UAS Operators per the specifications provided by NASA. By engaging various members of the UAS community in development and operational roles, this campaign provided initial validation of different aspects of the UTM concept including: UAS Service Supplier technologies and procedures; geofencing technologies/conformance monitoring; ground-based surveillance/sense and avoid; airborne sense and avoid; communication, navigation, surveillance; and human factors related to UTM data creation and display. Additionally, measures of performance were defined and calculated from the flight data to establish quantitative bases for comparing flight test activities and to provide potential metrics that might be routinely monitored in future operational UTM systems.

Aweiss, Arwa S.

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.

A Formal Messaging Notation for Alaskan Aviation Data

Data exchange is an increasingly important aspect of the National Airspace System. While many data communication channels have become more capable of sending and receiving data at higher throughput rates, there is still a need to use communication channels efficiently with limited throughput. The limitation can be based on technological issues, financial considerations, or both. This paper provides a complete description of several important aviation weather data in Abstract Syntax Notation format. By doing so, data providers can take advantage of Abstract Syntax Notation's ability to encode data in a highly compressed format. When data such as pilot weather reports, surface weather observations, and various weather predictions are compressed in such a manner, it allows for the efficient use of throughput-limited communication channels. This paper provides details on the Abstract Syntax Notation One (ASN.1) implementation for Alaskan aviation data, and demonstrates its use on real-world aviation weather data samples as Alaska has sparse terrestrial data infrastructure and data are often sent via relatively costly satellite channels.

communications