Portable Storage Device Remote Update via No-Operation Byte Delay
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Portable storage devices installed in identification card sockets face challenges in updating data while being accessed by hosting devices, as existing technologies do not effectively manage communication delays to allow for complete data updates before access, leading to potential errors and interface resets.
Innovation Solution
The solution involves prolonging communication with the hosting device by responding with no-operation procedure bytes and manipulating operation and timing parameters to delay data access, allowing for maximum time to update the data through an independent update interface before making it available via the identification card interface.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If communication with the hosting device is maintained at normal speed, then data access is efficient, but the portable storage device cannot complete data updates before the hosting device accesses the data
Solution Approach 1:
The system performs preliminary actions by delaying the hosting device's data access until the data update is complete. The portable storage device sends no-operation procedure bytes and manipulates timing parameters to postpone the hosting device's access, ensuring that the data is fully updated before the hosting device attempts to read it, thus preventing data access errors.
Solution Approach 2:
The system dynamically adjusts the communication timing between the portable storage device and the hosting device. By manipulating operation and timing parameters, the portable storage device can flexibly control the pace of data access, slowing down the communication just enough to allow data updates to complete while maintaining overall system functionality.
2Reliability
If data access is delayed to allow updates, then data integrity is maintained, but communication time is extended
Solution Approach 1:
The system uses periodic no-operation procedure bytes to maintain communication while delaying data access. Instead of a continuous delay, the portable storage device sends periodic no-operation bytes that keep the communication channel active and prevent timeout, while simultaneously stalling the data access until the update is complete.
Solution Approach 2:
The no-operation procedure bytes act as an intermediary mechanism. They serve as a placeholder that maintains the communication protocol's expected flow and prevents the hosting device from timing out, while effectively pausing the actual data access operation until the data update is finished.
3Productivity
If the hosting device accesses data immediately, then communication is efficient, but data update errors occur
Solution Approach 1:
The portable storage device provides feedback to the hosting device through no-operation procedure bytes and timing parameter adjustments. This feedback mechanism signals to the hosting device that data is not yet ready for access, preventing the hosting device from attempting to read incomplete or corrupted data, thus avoiding access errors while maintaining communication efficiency.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A method of remotely updating a portable storage device, comprising: a) Delaying an access to an identification card interface of a portable storage device communicating with a hosting device by acknowledging with one or more consecutive no operation procedure byte to commands issued by said hosting device. The portable storage device is installed in an identification card socket. b) Updating the portable storage device with new data through an updating device connected to an update interface of the portable storage device during the access of said hosting device to the identification card interface. c) Providing the new data to the hosting device through the identification card interface after the new data is updated in the portable storage device.