Portable Memory Interface Timeout Prevention via Dummy Blocks
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing memory module interfaces face challenges with bus timeouts during complex operations like security validation, which can abort legitimate read/write operations due to rigid timeout requirements, limiting the introduction of advanced functionality and preventing forward migration in removable memory development.
Innovation Solution
Incorporating dummy operations in read and write operations to manage bus timeouts, allowing the system to exceed standard timeout specifications by determining and sending sufficient dummy data blocks to prevent timeouts, thereby enabling more complex functions on legacy interfaces.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If rigorous timeout rules are implemented to assure robust operation, then system reliability is improved, but complex data processing operations cannot complete before timeout
Solution Approach 1:
The host initiates dummy write operations before the actual complex operation to pre-consume the timeout period. This preliminary action reserves time for the complex security validation or cryptographic operation to complete without triggering a timeout, while the dummy operations fill the bus bandwidth to prevent the timeout mechanism from activating.
Solution Approach 2:
Dummy data blocks serve as an intermediary mechanism between the host and the complex operation. These dummy blocks are transferred over the bus to consume time and bandwidth, acting as a mediator that prevents the timeout mechanism from interfering with the legitimate complex operation that requires more time than the standard timeout allows.
2Adaptability or versatility
If advanced functionality is designed into memory modules, then device capabilities are improved, but timeout rules cause operations to be aborted
Solution Approach 1:
The host performs preliminary dummy write operations to consume the timeout period before the advanced functionality (such as security validation or cryptographic processing) needs to complete. This allows the module to provide advanced capabilities without being constrained by the fixed timeout rules that would otherwise abort these complex operations.
Solution Approach 2:
The system changes the temporal parameters of bus operations by introducing dummy data transfers that extend the operation duration. This parameter change allows advanced functions that require more time to complete without modifying the fundamental timeout rules or hardware architecture.
3Reliability
If fixed timeout values are hard-wired into host hardware, then interface robustness is improved, but forward migration to complex operations is prevented
Solution Approach 1:
The host initiates dummy write operations in advance to consume the fixed timeout period, allowing complex operations to complete without being constrained by the hard-wired timeout values. This preliminary action works around the inflexible hardware timeout mechanism while maintaining interface robustness.
Solution Approach 2:
Dummy data blocks act as an intermediary that mediates between the fixed timeout hardware constraint and the complex operation requirements. These dummy transfers consume bus bandwidth and time without interfering with the actual complex operation, enabling forward migration to more sophisticated functions.
4Duration of action of moving object
If dummy operations are performed to prevent timeout, then operation completion is improved, but bus bandwidth is consumed
Solution Approach 1:
The dummy data blocks are extracted as separate, identifiable entities that are deliberately transferred to consume bus bandwidth and time. These dummy operations are distinct from the actual useful data transfers, allowing the system to separate the timeout prevention function from the primary data transfer function.
Solution Approach 2:
The dummy data blocks are discarded after serving their timeout prevention purpose. They are not retained or processed as meaningful data, but rather used temporarily to consume bus resources and then discarded, allowing the system to recover and proceed with the actual complex operation.
Data Source
AI summary
Methods and systems for working around the timeout limitations of physical interface standards for detachable modules. By use of dummy data blocks to keep the bus active, the bus timeout requirements (in either direction) can be spoofed, to thereby permit more complex processing operations to be performed that may exceed the bus timeout of a particular specification. A controller in the memory system deasserts the ready signal and holds the bus connecting the computer system in a “busy” state until the memory system is about to timeout. During a write operation, the controller receives dummy data blocks from the computer system before the write bus timeout period expires, causing the bus timeout period to be reset. During a read operation, the controller sends dummy data blocks to the computer system before the read bus timeout period expires, causing the bus timeout period to be reset.