Frame Buffer SID Bits for Data Corruption Source Identification
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing data storage systems face challenges in detecting and isolating the source of data corruption during data transmission, as corruption can go unnoticed until data is written to disk, making it difficult to analyze and correct, especially in complex hierarchical environments.
Innovation Solution
A system comprising an array controller and frame buffer that performs data integrity checks, logs errors, and uses Source Identifier (SID) fields to flag and persistently store the source of corruption, enabling asynchronous notification and progressive CRC checksums to identify and isolate corruption sources.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If conventional data integrity check mechanisms are used, then data corruption detection is achieved, but the source of corruption cannot be identified
Solution Approach 1:
The patent segments the data transmission path into multiple hierarchical levels (controller layers, buffers, channels) and assigns unique Source Identifier bits to each segment. When corruption is detected, the corresponding SID bit indicates which segment is faulty, enabling precise source identification without compromising detection accuracy.
Solution Approach 2:
The patent introduces Source Identifier bits as intermediary markers embedded in data structures at multiple levels. These SID bits act as mediators between the data and the corruption source, providing a direct link that preserves source information while allowing conventional integrity checks to function.
2Reliability
If complex sequence of steps is used to analyze data corruption source, then corruption cause can be eliminated, but analysis time increases
Solution Approach 1:
The patent performs preliminary action by pre-embedding Source Identifier bits at multiple hierarchical levels during data transmission. This advance preparation eliminates the need for complex post-hoc analysis sequences, as the corruption source is already marked and identifiable when corruption occurs.
Solution Approach 2:
The patent implements feedback mechanisms where CRC checksums and SID bits provide immediate information about data integrity and corruption source. This feedback loop eliminates the need for time-consuming sequential analysis by directly indicating the problematic segment.
3Loss of information
If persistent storage of corruption indicators is implemented, then field analysis is assisted, but storage space is consumed
Solution Approach 1:
The patent applies local quality by storing persistence indicators only at specific hierarchical levels where corruption occurs, rather than universally throughout the entire data path. This selective persistence approach preserves necessary field analysis information while minimizing storage space consumption.
Solution Approach 2:
The patent extracts only the essential persistence indicator information (SID bits and persistence indicators) from the full data structure and stores these minimal elements in non-volatile memory. This extraction approach maintains necessary analysis capabilities while significantly reducing storage requirements compared to storing complete data histories.
4Productivity
If multiple hierarchical entities are involved in data transmission, then data processing capability is improved, but corruption detection complexity increases
Solution Approach 1:
The patent segments the complex hierarchical data transmission system into discrete levels, each with its own CRC checksum and Source Identifier bits. This segmentation transforms the complex corruption detection problem into multiple simpler, independent checks, making the overall system more manageable despite the hierarchical structure.
Data Source
AI summary
An apparatus comprising an array controller and a frame buffer. The array controller may be configured to read/write data to/from a drive array in response to one or more input/output requests. The frame buffer may be implemented within the array controller and may be configured to perform (i) a first data integrity check to determine a first type of data error and (ii) a second data integrity check to determine a second type of data error. The frame buffer may log occurrences of the first type of error and the second type of error in a field transmitted with the data. The field may be used to determine a source of possible corruption of the data.