Poison Data Pattern Checksum Encoding for Memory Error Detection
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing memory systems face inefficiencies in storing data and its associated checksums, particularly when dealing with 'poison data' that requires additional indicators, leading to increased memory space usage and complexity.
Innovation Solution
A method where a controller incorporates a poison data indicator into the checksum data within memory devices, using a poison data pattern to indicate whether data is erroneous or corrupted, thereby reducing memory space requirements and simplifying storage by combining the indicator with the checksum.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a separate poison data indicator is stored with the data, then error detection capability is improved, but memory space usage increases
Solution Approach 1:
The patent combines the poison data indicator with the checksum data by performing a bitwise XOR operation between the poison indicator and the checksum. This merging allows both the error detection capability (through the poison indicator) and memory space efficiency (by eliminating separate storage) to be achieved simultaneously. The combined value is stored in the checksum location, and during read operations, the poison indicator can be recovered by XORing the stored checksum with the recalculated checksum.
2Reliability
If a separate poison data indicator is stored with the data, then error detection capability is improved, but device complexity increases
Solution Approach 1:
The patent merges the poison data indicator into the existing checksum structure, eliminating the need for separate storage locations and reducing the overall storage structure complexity. The bitwise XOR operation provides a simple mathematical mechanism to combine and separate the indicator from the checksum without requiring complex data structures or additional management logic.
Solution Approach 2:
The checksum field is given multiple functions: it continues to provide traditional checksum error detection while simultaneously encoding the poison data indicator. This multi-functionality eliminates the need for dedicated poison indicator storage, thereby reducing device complexity while maintaining enhanced error detection capabilities.
3Quantity of substance
If traditional checksum storage is used, then memory space is saved, but poison data indication capability is lost
Solution Approach 1:
The patent changes the parameter representation by encoding the poison data indicator within the checksum value itself using bitwise XOR operations. Instead of using separate storage, the poison indicator information is transformed and embedded within the existing checksum parameter, thereby maintaining memory space efficiency while gaining poison data indication capability.
Data Source
AI summary
Systems, apparatuses, and methods related to modified checksum data using a poison data indictor. An example method can include receiving a first set of bits including data and a second set of at least one bit indicating whether the first set of bits includes one or more erroneous or corrupted bits. A first checksum can be generated that is associated with the first set of bits. A second checksum can be generated using the first checksum and the second set of at least one bit. The first set of bits and the second checksum can be written to an array of a memory device. A comparison of the first checksum and the second checksum can indicate whether the first set of bits includes the at least one or more erroneous or corrupted bits.