Bus Protection via Copy Data and Error Detection Code
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing methods for protecting buses are inadequate when multiple protocols are used, as protocol conversion can change the data to be protected, making it difficult to ensure bus security.
Innovation Solution
The solution involves a semiconductor device configuration with a master interface that generates a copy of the request data and an error detection code, which is transmitted alongside the original data through a bus with a protocol conversion unit. The slave interface performs error detection and verification by converting the data between protocols, ensuring accurate data transmission even after protocol conversion.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If protocol conversion is performed in the bus, then multiple protocols can be supported, but the data to be protected changes making bus protection difficult
Solution Approach 1:
The patent creates a copy of the request data (CRQ) alongside the original request data (RQ). This copy is used for error detection without being modified by protocol conversion, allowing the same error detection mechanism to work across different protocols. The copy serves as an immutable reference that preserves the original data structure for verification purposes.
Solution Approach 2:
The error detection code (EDC) is generated in advance based on the original request data before protocol conversion occurs. By performing the error detection preparation beforehand, the system ensures that the EDC remains valid even after the data undergoes protocol conversion, eliminating the need to regenerate EDC at each conversion stage.
2Reliability
If error detection code is regenerated at each protocol conversion, then error detection accuracy is maintained, but device complexity and processing time increase
Solution Approach 1:
Instead of regenerating the error detection code at each protocol conversion, the system uses a copy of the original request data that preserves the initial data structure. This copy allows the EDC to be generated once and reused across multiple protocol conversions, significantly reducing computational complexity while maintaining detection accuracy.
Solution Approach 2:
The single generated EDC serves multiple functions across different protocol conversions. The same error detection code can be used to verify data integrity regardless of how many times protocol conversion occurs, making the error detection mechanism universal rather than requiring separate mechanisms for each conversion stage.
3Adaptability or versatility
If protocol conversion is performed, then bus compatibility is improved, but data transmission errors may occur
Solution Approach 1:
The system implements a feedback mechanism where the error detection code is compared against the copied request data after protocol conversion. This feedback loop detects any discrepancies caused by protocol conversion errors or data corruption, allowing the system to identify and respond to transmission errors while maintaining compatibility.
Solution Approach 2:
The copy of the request data serves as a reference that remains unchanged during protocol conversion. By comparing the converted data against this immutable copy, the system can detect errors introduced during protocol conversion without compromising the flexibility and compatibility of the bus system.
Data Source
Figure 1A
Figure 1B
Figure 2
AI summary
The master interface generates copy data by copying the first data, and generates an error detection code based on the copy data. The protocol conversion unit generates the second data by converting the first data from the first protocol to the second protocol. The slave interface detects errors in the copy data based on the error detection code. The slave interface also generates the first verification data by performing a conversion from one of the first protocol or the second protocol to the other for one of the second data or copy data. In addition, the slave interface compares the second verification data with the first verification data, using the other of the second data or copy as the second verification data.