SATA Data FIS Error Feedback for Noise Interference Recovery
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The SATA interface lacks a protection mechanism for data FIS during noise interference, leading to potential system halts due to data errors and incorrect control commands, as data FIS is not resent, causing errors and increased data sets to be sent.
Innovation Solution
A method utilizing the ATA/ATAPI error feedback mechanism to detect CRC errors and misinterpreted primitives, modifying CDB contents, and adjusting data lengths to ensure correct transmission, and generating error CRC codes to request retransmission of FIS, thereby preventing system halts.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Speed
If data FIS is transmitted without protection mechanism during noise interference, then transmission speed is maintained, but system reliability deteriorates due to potential system halts and incorrect control commands
Solution Approach 1:
The patent implements an error feedback mechanism where the receiving device detects CRC errors in data FIS and sends error notifications back to the sending device. This feedback loop enables the sending device to retransmit corrupted data, thereby maintaining system reliability without significantly impacting transmission speed. The mechanism specifically monitors CRC fields and triggers retransmission only when errors are detected, rather than protecting all transmissions uniformly.
Solution Approach 2:
The patent applies preliminary error detection by checking CRC fields before processing data FIS content. The receiving device performs CRC verification in advance to identify corrupted packets, preventing incorrect data from being processed or control commands from being misinterpreted. This preliminary action filters out noise-interfered data before it can cause system halts or incorrect operations.
2Reliability
If error detection and correction mechanisms are implemented for data FIS, then system stability is improved, but device complexity increases
Solution Approach 1:
The patent extracts the error protection mechanism specifically for data FIS transmissions, separating it from other FIS types. Only data FIS packets undergo CRC verification and potential retransmission, while other FIS types maintain their original transmission protocols. This selective approach improves system stability for critical data transmissions without adding complexity to the entire SATA interface system.
Solution Approach 2:
The patent applies error protection locally to data FIS transmissions rather than uniformly across all FIS types. The CRC verification and retransmission mechanism is activated specifically when data FIS is detected and CRC errors are present, providing targeted protection where needed while leaving other transmissions unchanged, thus minimizing added complexity.
3Reliability
If retransmission mechanism is activated for all FIS types, then error protection is improved, but transmission efficiency deteriorates due to increased retransmission overhead
Solution Approach 1:
The patent implements partial error protection by activating retransmission only for data FIS packets with detected CRC errors, rather than for all FIS types. This partial action approach provides necessary error protection for critical data transmissions while avoiding unnecessary retransmissions that would reduce overall transmission efficiency. The mechanism selectively applies protection based on FIS type and error presence.
Solution Approach 2:
The patent changes the error protection parameter dynamically based on FIS type and error detection results. For data FIS with CRC errors, the system activates retransmission; for other cases, it maintains normal transmission flow. This parameter change approach ensures error protection is applied only when necessary, balancing reliability improvement with transmission efficiency preservation.
Data Source
AI summary
A method for processing noise interference in a serial AT Attachment (SATA) interface. The method includes the steps of detecting whether there is an error in CRC (Cyclic Redundancy Check) checksum or whether an R_ERR primitive (reception error primitive) is received, detecting whether a FIS (Frame Information Structure) is a data type if there is any error and returning back to error state detecting step if there is no any error, detecting whether the FIS is a ATAPI packet command CDB (Command Descriptor Block) when the FIS is the data format, and writing a special tag to the CDB and returning back to the error detecting step.