4-Bit Block Header Encoding for Reliable 128b/132b Data Buses
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing line coding schemes, such as 8b/10b and 64b/66b, face challenges in error detection and correction, particularly in ensuring reliable data recovery over physical media, as they lack efficient mechanisms for single-bit and double-bit error handling in block headers.
Innovation Solution
The implementation of a 128b/132b line coding scheme with a 4-bit block header that employs a hamming distance of at least four between data and control block headers, enabling single-bit error correction and double-bit error detection, ensuring reliable data recovery by differentiating between data and control messages.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If existing line coding schemes (8b/10b, 64b/66b) are used, then data transmission is achieved, but error detection and correction capabilities are insufficient
Solution Approach 1:
The patent applies preliminary action by pre-defining specific bit patterns for block headers (00 for data blocks, 11 for control blocks) and establishing Hamming distance rules in advance. This allows the receiver to detect and correct errors without complex real-time processing, as the error correction logic is built into the predetermined header structure
Solution Approach 2:
The patent applies local quality by focusing error correction efforts specifically on the block header portion of the data stream rather than the entire data stream. By applying Hamming distance constraints only to the header bits (particularly the second and fourth bits), the system achieves reliable error detection with minimal additional complexity
2Reliability
If block headers are used to define data and control messages, then message differentiation is achieved, but error detection capability is insufficient
Solution Approach 1:
The patent applies asymmetry by using non-complementary bit patterns (00 and 11) for data and control block headers instead of complementary patterns (01 and 10). This asymmetric choice creates inherent Hamming distance between the two header types, enabling the receiver to not only differentiate between data and control messages but also detect single-bit errors that would otherwise be indistinguishable from valid header variations
Solution Approach 2:
The patent establishes predetermined header patterns (00 for data, 11 for control) and Hamming distance rules before transmission. This preliminary structuring allows the receiver to use simple comparison logic against these known patterns to detect errors and differentiate message types without requiring complex real-time analysis
3Reliability
If Hamming distance of at least four is implemented between block header types, then single-bit error correction and double-bit error detection are enabled, but header design complexity increases
Solution Approach 1:
The patent applies local quality by concentrating Hamming distance constraints on specific header bits (particularly the second and fourth bits) rather than requiring all header bits to contribute equally to error correction. This localized approach achieves the required Hamming distance of at least four between data and control block headers while keeping the overall header structure simple and manageable
Solution Approach 2:
The patent applies parameter changes by carefully selecting specific bit values in the header (using 00 and 11 patterns) to achieve the desired Hamming distance. By changing the parameter values of specific header bits rather than increasing the overall header length or complexity, the system achieves robust error correction capability with minimal structural changes
Data Source
AI summary
Techniques for encoding data are described herein. The method includes receiving a block payload at a physical layer to be transmitted via a data bus. The method includes establishing a block header comprising an arrangement of bits, the block header defining two block header types, wherein a hamming distance between block header types is at least four.