UAS Data Collection Device for Reliable Information Management

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The integration of Unmanned Aircraft Systems (UAS) into the National Airspace System (NAS) faces challenges due to the lack of uniform and reliable data collection and management, leading to hazardous misleading information and inefficiencies in regulatory compliance and safety assessments.

Innovation Solution

The UDC System, comprising UDC Devices, Clients, and Services, is designed to uniformly collect and manage data from disparate UAS systems, ensuring consistent formatting, storage, and reliability, adapting to various UAS operations and requirements through a defined architecture and service hierarchy.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Quantity of substance

If data is collected from disparate UAS systems using different formats and protocols, then the quantity of data collected increases, but data reliability and consistency deteriorate

Engineering Contradiction:
Improvequantity of dataVSAvoiddata reliability
Core Design Contradiction:
Quantity of substanceVSReliability

Solution Approach 1:

The patent introduces a data collection device as an intermediary component that receives data from multiple disparate UAS systems and translates/normalizes it into a uniform format. This mediator device includes data collection modules, translation modules, and storage modules that work together to convert diverse data sources into consistent, reliable data without losing information quantity.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent implements homogeneity by standardizing data formats across all UAS systems. The data collection device applies uniform data structures, naming conventions, and validation rules to all incoming data, transforming heterogeneous data from different sources into homogeneous, consistent data that maintains reliability while preserving the quantity of information from multiple systems.

Inventive Principle:
Principle #33Homogeneity

2Adaptability or versatility

If multiple data collection methods are used to accommodate various UAS operations, then adaptability increases, but system complexity increases

Engineering Contradiction:
ImproveadaptabilityVSAvoidsystem complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The data collection device is designed with universal multi-functionality to handle various UAS operations including BVLOS, OOVF, and package delivery. The system incorporates multiple data collection modules that can adapt to different operational requirements, sensor types, and data formats through a unified architecture, allowing one system to serve multiple purposes without proportionally increasing complexity.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The patent segments the data collection system into modular functional components: data collection modules for different UAS operations, translation modules for format conversion, validation modules for quality control, and storage modules. This segmentation allows the system to maintain adaptability for various operations while managing complexity through organized, independent modules that can be configured based on specific operational needs.

Inventive Principle:
Principle #1Segmentation

3Measurement precision

If comprehensive data is collected from all UAS subsystems, then measurement precision improves, but data management difficulty increases

Engineering Contradiction:
Improvemeasurement precisionVSAvoiddata management difficulty
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The patent implements feedback mechanisms through validation modules that continuously monitor incoming data from all UAS subsystems. The system validates data quality, checks for consistency, and provides feedback for correction or rejection of problematic data. This feedback loop ensures measurement precision is maintained across all collected data while automating the management of comprehensive data sets, reducing manual intervention requirements.

Inventive Principle:
Principle #23Feedback

4Speed

If real-time data processing is implemented for safety assessments, then response time improves, but computational resource requirements increase

Engineering Contradiction:
Improveresponse timeVSAvoidcomputational resource requirements
Core Design Contradiction:
SpeedVSUse of energy by moving object

Solution Approach 1:

The patent applies partial action by implementing real-time processing only for critical safety-related data parameters that require immediate assessment, while allowing non-critical data to be processed asynchronously or in batches. This approach maintains fast response times for safety assessments by focusing computational resources on essential real-time requirements rather than processing all collected data at maximum speed, thereby reducing overall computational resource requirements.

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentUS11847923B2Robust techniques for the collection and management of data from data sources in an unmanned aircraft systems (UAS) operations environment
Publication Date: 2023.12.19 THE GOVERNMENT OF THE UNITED STATES OF AMERICA AS REPRESENTED BY THE ADMINISTATOR OF THE FEDERAL AVIATION ADMINISTATION
  • US11847923B2 patent drawing
  • US11847923B2 patent drawing
  • US11847923B2 patent drawing

AI summary

Robust techniques for the collection, storage, and processing of data from disparate UAS data sources in an unmanned aircraft systems (UAS) operations environment. A data-agnostic platform hosts a plurality of clients and client services. Baseline configurations and customizations are input to configure the platform for collection, retention, and/or processing of the data, and the client services are automatically configured based in part on those baseline configurations and customizations. Client services are logically arranged within each device memory as a plurality of operational groupings with a predetermined sequence order and a predetermined priority and executed according to the predetermined sequence order and predetermined priority. Data from the data sources is translated into customized data based at least, in part, on the configuration information, and validated for storage. Validated data may be analyzed according to prescribed functions and formulas and/or reported out according to a preferred format, based on the configuration information.