Graphical Data Coding for Safe UAV Communication
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current methods for safely transferring information signals in critical systems, such as those used in airborne systems, are costly and require all entities in the communication chain to be safety-approved, which is not feasible or economical, especially with the introduction of Unmanned Aerial Vehicles (UAVs), and do not easily detect communication errors without relying on safety-approved equipment.
Innovation Solution
A method involving the representation of information as graphical segments, transmission through a non-safety-approved entity, and verification of data integrity by detecting corruption through checksums or picture coding, allowing for safe communication without requiring all entities to be safety-approved, and enabling easy detection of errors by displaying graphical segments and taking appropriate actions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional safety-approved equipment is used for all entities in the communication chain, then system safety and reliability are ensured, but development cost and system complexity increase significantly
Solution Approach 1:
The communication system is segmented into safety-critical entities (first and second entities) and non-safety-critical entities (third entity). Only the entities that directly handle critical functions require safety approval, while intermediate transmission entities can use commercial-off-the-shelf equipment. This segmentation allows the system to maintain safety where needed while reducing complexity and cost in non-critical areas.
Solution Approach 2:
A data coding unit is introduced as an intermediary component within the safety-approved entities. This coding unit transforms data into a format that enables error detection without requiring the entire communication chain to be safety-approved. The intermediary coding mechanism protects the critical data flow while allowing non-safety-approved equipment to handle transmission.
2Reliability
If traditional safety-approved equipment is used for all entities in the communication chain, then communication error detection capability is ensured, but development cost increases significantly
Solution Approach 1:
The invention replaces expensive safety-approved equipment in non-critical positions with cheap commercial-off-the-shelf equipment. The third entity (transferring entity) uses standard, inexpensive hardware and software while the safety-critical first and second entities maintain proper certification. This substitution reduces development cost while preserving error detection capability through the data coding mechanism.
Solution Approach 2:
The invention substitutes physical safety-approved hardware with a software-based data coding and verification system. Instead of requiring all hardware components to be safety-certified, the system uses algorithmic error detection (checksums, parity bits, or picture coding) to maintain reliability. This substitution dramatically reduces development cost while preserving error detection capability.
3Ease of manufacture
If commercial-off-the-shelf products are used in the communication chain, then cost is reduced, but the ability to detect communication errors deteriorates
Solution Approach 1:
Error detection capabilities are built into the data coding unit before data transmission occurs. The coding unit pre-processes the data by adding error-detecting codes (such as checksums, parity bits, or picture coding structures) that enable the receiving entity to verify data integrity. This preliminary action ensures that even though commercial-off-the-shelf products are used, error detection capability is maintained through预先 embedded verification mechanisms.
Data Source
AI summary
A method of detecting communications errors by coding messages as pictures. A communications method useable to safely communicate a message or a signal from a first safety approved entity to a second safety approved entity via a third, non-safety approved entity including 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.