Transaction Packet Routing Without ECRC Recalculation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In shared infrastructure systems, modifying packet integrity checks like ECRC at intermediate points can lead to corruption, especially when different protocols are used, and existing solutions struggle to maintain data integrity during routing and address modifications.
Innovation Solution
A method that inserts additional routing information at predetermined bit positions in transaction packets without altering the ECRC value, allowing for flexible routing while reinstating the original bit values, thereby preserving data integrity across the infrastructure.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If additional routing information is added to transaction packets at intermediate infrastructure points, then routing flexibility and protocol adaptability are improved, but packet integrity (ECRC) may be corrupted
Solution Approach 1:
The packet structure is segmented into fixed portions (original fields with predetermined bit values) and variable portions (additional routing information). This segmentation allows the packet to carry extended routing information while preserving the integrity of the original ECRC-calculated fields.
Solution Approach 2:
Predetermined bit values are established in advance at specific positions where additional routing information will be inserted. This preliminary setup allows intermediate infrastructure points to add routing information without needing to recalculate the ECRC, as the predetermined values are already accounted for in the original ECRC calculation.
2Reliability
If ECRC is recalculated at intermediate points to maintain integrity, then packet reliability is improved, but system complexity and potential for error increase
Solution Approach 1:
The problem of ECRC recalculation is extracted and eliminated by using predetermined bit values. Instead of recalculating ECRC at intermediate points (which adds complexity and potential for error), the system extracts only the necessary routing information from the packet while leaving the ECRC intact.
Solution Approach 2:
The original ECRC value serves itself by being valid for both the original packet contents and the extended packet with additional routing information. The predetermined bit values are designed so that the original ECRC calculation remains valid, eliminating the need for intermediate ECRC recalculation.
3Ease of operation
If packet modifications are made for routing purposes, then routing functionality is improved, but data integrity may be compromised
Solution Approach 1:
Different portions of the packet are assigned different qualities/functions. The predetermined bit positions are designated specifically for additional routing information, while other portions maintain their original integrity-checking properties. This local differentiation allows routing modifications without compromising overall data integrity.
Data Source
AI summary
Additional routing information is added to a transaction packet without recalculating an ECRC by inserting the additional routing information at predetermined bit positions in the transaction packet known to have predetermined bit values. The modified transaction packet can then be routed using the additional routing information. The predetermined bit values can subsequently be reinstated at the predetermined bit positions in the packet.