Encoded Diagnostics for Functional Safety Systems
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current functional safety systems face challenges in accurately detecting and responding to faults and timeouts in complex systems, particularly in environments prone to interference, where bit flips or software overwrites can occur due to bugs, memory issues, or malicious attacks, leading to potential unsafe operational states.
Innovation Solution
A method involving a safety module that stores and encodes state information as unique codewords with minimum hamming distances, allowing for the detection of mismatches and outputting safety messages based on matches or mismatches between stored and valid codewords, thereby triggering fault recovery processes and maintaining functional safety.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional fault detection methods are used in functional safety systems, then the system structure remains simple, but the system becomes vulnerable to bit flips and software overwrites that can lead to unsafe operational states
Solution Approach 1:
The system pre-calculates and stores valid codewords for all possible system states before operation. These codewords are generated using encoding functions that incorporate checksums or error-detecting codes, allowing the system to quickly validate received safety messages against a known set of valid states without complex real-time analysis
Solution Approach 2:
An encoding layer is introduced as an intermediary between the safety controller and the safety message transmission. This encoding layer transforms system states into validated codewords and implements validation logic that detects bit flips and overwrites by comparing received messages against the pre-calculated valid codeword set, shielding the core safety system from interference
2Measurement precision
If the system implements comprehensive fault detection and validation, then the error rate in safety messages decreases, but the processing time and computational overhead increase
Solution Approach 1:
The system pre-computes and stores all valid codewords corresponding to legitimate system states during system initialization or configuration phase. This preliminary action creates a lookup table of valid states that enables O(1) constant-time validation during operation, avoiding complex real-time computations
Solution Approach 2:
The validation mechanism changes from continuous monitoring with complex analysis to discrete state validation using pre-defined codewords. By transforming the validation problem into a simple matching operation against pre-calculated valid states, the system achieves high precision fault detection with minimal processing time
3Reliability
If the system uses simple state representation, then the memory requirements are low, but the system cannot detect bit flips or software overwrites
Solution Approach 1:
The system segments the state representation into multiple components: the actual system state parameters and redundant validation bits (checksums or error-detecting code bits). This segmentation allows the addition of detection capability while keeping the base state representation compact, with the overhead limited to the redundant bits only
Solution Approach 2:
The system creates compact copies of state information in the form of valid codewords that are stored in memory. These codewords serve as reference copies that enable validation without requiring storage of the entire system state history or complex validation algorithms, achieving detection capability with minimal memory overhead
Data Source
AI summary
A method includes, storing a set of valid codewords including: a first valid functional codeword representing a functional state of a controller subsystem; a first valid fault codeword representing a fault state of the controller subsystem and characterized by a minimum hamming distance from the first valid functional codeword; a second valid functional codeword representing a functional state of a controller; and a second valid fault codeword representing a fault state of the controller; in response to detecting functional operation of the controller subsystem, storing the first valid functional codeword in a first memory; in response to detecting a match between contents of the first memory and the first valid functional codeword, outputting the second valid functional codeword; in response to detecting a mismatch between contents of the first memory and every codeword in the first set of valid codewords, outputting the second valid fault codeword.