Client-Aborted Message Handling on Data Bus
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing data bus systems face challenges in reliably indicating a client-aborted message without causing message integrity errors or increasing bandwidth usage, as conventional methods like using a fixed FCS value or modifying status registers can lead to misinterpretation or unnecessary overhead.
Innovation Solution
Modifying the frame check sequence (FCS) value to create a unique 'bad' FCS by applying mathematical operations such as ones complement or exclusive OR on the good FCS, ensuring clear indication of a client-aborted message without additional message overhead.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If a fixed and known FCS value is used to indicate a client-aborted message, then the indication method is simple, but there is a likelihood that a good message's FCS will be the same as the fixed abort value, causing misinterpretation
Solution Approach 1:
The patent changes the FCS parameter from a fixed value to a modified value derived from the original FCS through mathematical operations (ones complement, XOR with 0xFF, or XOR with 0xAA). This transformation ensures the aborted message indicator is reliably distinguishable from valid FCS values while maintaining a systematic approach.
2Reliability
If a status register bit is set to indicate client-aborted message, then the indication is clear, but the status register must be read in another message or added as payload, decreasing bus bandwidth and adding overhead
Solution Approach 1:
The patent merges the abort indication function with the existing FCS field that is already part of every message. By encoding the abort status within the FCS itself through mathematical transformation, the system eliminates the need for separate status registers or additional payload bytes, thereby maintaining bus bandwidth efficiency while providing clear abort indication.
Data Source
AI summary
A data bus and message handling method provide a definitive means of indicating a client-aborted message for data bus systems which employ a message protocol that requires each message conveyed between a client device and an originating device to automatically and atomically include a frame check sequence (FCS). When a message is not to be client-aborted, a ‘good’ FCS is generated by a first method, typically based on the message's data content. However, when a message is to be client-aborted, the FCS is generated by a second method which requires modifying the good FCS value to create a ‘bad’ FCS, preferably using a mathematical means that preserves the uniqueness of the bad FCS to a high degree.