Unified Error Handling Architecture for High-Speed Transmission Interfaces
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current high-speed interface transmission products lack an effective mechanism to integrate error recovery across different interfaces, leading to device deadlocks and user inconvenience due to the absence of proper debugging and reporting mechanisms.
Innovation Solution
An error handling method is introduced where a controller in the transmission interface detects errors at both direct and indirect interfaces, reports errors to the host when necessary, and attempts to handle errors at the indirect interface without the host's knowledge, ensuring the system returns to a normal status by reporting error events appropriately.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If individual error recovery mechanisms are used for each high-speed interface, then each interface can handle its own errors independently, but the command master cannot integrate these mechanisms leading to device deadlocks and timeouts
Solution Approach 1:
The patent merges multiple individual error recovery mechanisms into a unified error handling architecture. The command master now integrates error handling for both direct interfaces (DI) and indirect interfaces (II), consolidating previously scattered error recovery capabilities into a centralized system that prevents deadlocks and provides unified reporting.
Solution Approach 2:
The command master acts as an intermediary between the direct interface and indirect interface error handling mechanisms. It receives error information from both interface types, processes them through a unified error handling flow, and coordinates the recovery process, thereby integrating previously independent error recovery mechanisms.
2Ease of operation
If errors at indirect interface are handled automatically without host discovery, then system operation remains seamless, but complex errors may go unresolved causing deadlocks
Solution Approach 1:
The system applies partial error handling at the indirect interface level - automatically handling certain error types without host involvement while maintaining the capability to escalate complex errors. This partial automation preserves seamless operation for routine errors while ensuring reliability for complex situations.
Solution Approach 2:
The unified error handling mechanism implements feedback loops where error handling results are monitored and reported back to the command master. This allows the system to determine when automatic handling was successful and when escalation to the host is necessary, balancing seamless operation with reliable error resolution.
3Reliability
If all errors are reported to the host, then proper debugging and reporting are achieved, but system responsiveness and seamless operation are reduced
Solution Approach 1:
The error handling system applies different quality levels of error reporting based on the interface type and error severity. Direct interface errors are handled with one level of reporting rigor, while indirect interface errors receive differentiated treatment based on their nature, allowing the system to maintain responsiveness while ensuring accurate reporting where necessary.
Solution Approach 2:
The system changes the parameter of error reporting behavior based on error characteristics. Rather than uniformly reporting all errors to the host, the unified error handling mechanism adjusts reporting parameters dynamically - suppressing routine errors, escalating critical errors, and providing selective reporting based on error type, interface type, and system state.
Data Source
AI summary
An error handling method for a transmission interface connecting between a first device and a second device for performing data transmission between the first device and the second device, wherein a connection type between the transmission interface and the first device is a direct interface (DI) and the connection type between the transmission interface and the second device is an indirect interface (II), and the error handling method comprises: when an error is detected at the direct interface, reporting an error event to a host of the first device; when an error is detected at the indirect interface, attempting to handle the error without letting the host discover it; and when the error detected at the indirect interface is determined as unable to be solved, reporting another error event to the host.