Graphical Data Segments for Safe UAV Communication
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In safety-critical systems like airborne equipment, using non-safety approved entities for communication poses risks of data corruption, especially in applications where erroneous information can lead to severe consequences, such as UAV control, due to the high costs associated with developing software to meet stringent standards like RTCA/DO-178B.
Innovation Solution
A communication method that represents information as graphical segments, allowing detection of corruption by converting data into graphical forms like pixels, lines, or polygons, enabling the sender to verify integrity and take appropriate actions, such as discontinuing communication, to ensure safe data transfer even through non-safety approved entities.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional safety-approved equipment and Class A/B software are used for communication in safety-critical systems, then system reliability and safety are improved, but development cost and device complexity increase significantly
Solution Approach 1:
The patent introduces a non-safety-approved entity as an intermediary communication channel between safety-approved entities. This intermediary uses graphical segment representation to transmit data, allowing safe communication through an otherwise unsafe path by verifying data integrity through graphical reconstruction and comparison
Solution Approach 2:
The patent creates graphical segment representations (visual copies) of the original data to be transmitted. These graphical segments serve as verifiable copies that can be reconstructed and compared to detect corruption, enabling safety verification without requiring the entire communication system to be safety-approved
2Reliability
If Class A or B software is used to ensure safe information flow, then communication reliability is improved, but development cost increases approximately three times compared to Class D software
Solution Approach 1:
The patent employs non-safety-approved, low-cost entities for the communication function. By using graphical segment verification instead of requiring safety-approved hardware/software throughout the chain, the system can utilize inexpensive COTS products while maintaining safety through the verification mechanism
Solution Approach 2:
The graphical segment representation acts as an intermediary verification layer that allows cheap, non-safety-approved communication entities to be used safely. The verification process through graphical reconstruction and comparison provides the necessary safety assurance without requiring expensive safety-approved components
3Device complexity
If non-safety approved entities are used for communication, then development cost and device complexity are reduced, but data corruption risk and reliability worsen
Solution Approach 1:
The patent divides the data into graphical segments for transmission. Each segment can be independently verified through reconstruction and comparison, allowing detection of corruption in individual segments without compromising the entire data set. This segmentation enables use of simple, non-safety-approved entities while maintaining overall data integrity
Solution Approach 2:
The patent implements a feedback verification mechanism where the receiving entity reconstructs graphical segments from received data and compares them with expected segments. This feedback loop detects corruption and triggers appropriate actions, ensuring data integrity even when using unreliable non-safety-approved communication entities
Data Source
Figure 1
Figure 2
Figure 3a
AI summary
A method of detecting communications errors by coding messages as pictures is provided. Also provided is a communications method useable to safely communicate a message or a signal from a first safety approved entity (210) to a second safety approved entity (230) via a third, non-safety approved entity (220), comprising that each command is sent with the aid of a command message from the first to the second entity, an acknowledge message from the second to the first entity, and a go-ahead message from the first to the second entity.