Longitudinal Position Data Error Correction Using Hamming Codes
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Tape storage systems face challenges in tolerating errors in longitudinal position (LPOS) data, which can lead to Stop Write conditions due to single bit errors, and existing solutions like Reed-Solomon parity or base-14 checksums increase word length and do not provide effective error correction.
Innovation Solution
The method encodes data into even and odd LPOS words, generates syndrome bits to detect errors, and uses a shortened extended Hamming code to correct single-bit errors and detect double-bit errors without increasing the LPOS word length, employing a (26,20) code capable of correcting single errors and detecting multiple errors.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If Reed-Solomon parity symbols are appended to LPOS words for error correction, then error correction capability is improved, but LPOS word length increases and synchronization problems occur
Solution Approach 1:
The LPOS word is segmented into even and odd components, with separate error correction handling for each type. This allows the use of compact (26,20) Hamming codes on segmented data rather than requiring longer Reed-Solomon codes on the entire LPOS word, thereby maintaining error correction capability while avoiding length increase and synchronization issues.
Solution Approach 2:
The invention changes the error correction code parameters from Reed-Solomon (which would require longer word length) to Hamming (26,20) codes that operate within the existing LPOS word length constraints. This parameter change enables error correction without increasing word length or causing synchronization problems.
2Reliability
If base-14 checksum is added to LPOS words for error detection, then error detection capability is improved, but LPOS word length increases and error correction is not provided
Solution Approach 1:
The LPOS word structure is segmented into even and odd types, each processed with (26,20) Hamming codes. This segmentation enables the system to provide both error detection and correction within the existing word length, rather than adding separate checksum fields that would increase length.
Solution Approach 2:
The invention changes from using base-14 checksums (which only detect errors and increase length) to using (26,20) Hamming codes that provide both detection and correction within the same length constraints, thereby improving capability without the length penalty.
3Reliability
If a single bit error occurs in LPOS data on a single channel, then system reliability deteriorates due to Stop Write condition, but adding error correction increases complexity
Solution Approach 1:
The error correction mechanism is segmented into simple (26,20) Hamming code operations on even and odd LPOS words separately. This segmentation reduces overall system complexity compared to implementing a single complex Reed-Solomon decoder, while still providing the reliability needed to prevent Stop Write conditions.
Solution Approach 2:
The invention uses simpler, less resource-intensive Hamming (26,20) codes instead of more complex Reed-Solomon codes. These simpler codes act as 'cheaper' error correction mechanisms that provide sufficient protection against single-bit errors without the high complexity overhead, enabling continued operation after errors.
Data Source
AI summary
A method and apparatus for providing error correction capability to longitudinal position data are disclosed. Initially, data are encoded via a set of even LPOS words and a set of odd LPOS words. The encoded data are then decoded by generating a set of syndrome bits for each of the LPOS words. A determination is then made as to whether or not there is an error within one of the LPOS words based on its corresponding syndrome bits.