Cloud Data Sync via Portable Storage and Hash Verification
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional network-based data transfer techniques struggle with migrating large volumes of data to cloud computing platforms due to bandwidth limitations and the need to lock user data during the transfer process, which can lead to prolonged access restrictions.
Innovation Solution
A method involving the use of an intermediate portable storage device to transfer data from local storage to cloud storage, allowing users to modify data during transfer and synchronize changes using hash values to ensure data integrity and reduce network traffic.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Quantity of substance
If conventional network-based data transfer techniques are used to migrate large volumes of data to cloud computing platforms, then data migration can be performed, but network bandwidth is excessively utilized and data transfer is cumbersome
Solution Approach 1:
The patent creates a copy of the data set on a portable storage device before transferring to the cloud. This copy is then used to restore previously deleted or modified data objects, eliminating the need to re-upload the entire data set to the cloud, thereby significantly reducing network bandwidth consumption for data migration.
Solution Approach 2:
The system performs preliminary actions by copying data to a portable storage device and indexing data objects before actual cloud migration. This preliminary copying allows the system to determine which data objects need to be restored or updated, optimizing the subsequent cloud transfer process and reducing overall bandwidth usage.
2Reliability
If data is locked during the transfer process to ensure integrity, then data consistency is maintained, but user access to data is restricted for prolonged periods
Solution Approach 1:
The patent implements dynamic data access control where data objects are locked only during critical transfer operations and unlocked afterward. This allows users to access data immediately after migration completes, eliminating prolonged access restrictions while maintaining consistency during the transfer process through controlled locking mechanisms.
Solution Approach 2:
The system uses feedback mechanisms to track data transfer status and automatically manage locking/unlocking of data objects. When transfer completes successfully, the system receives feedback and releases locks, allowing immediate user access. This feedback-driven approach ensures data consistency during transfer while minimizing access restriction time.
3Quantity of substance
If the entire data set is uploaded to the cloud to ensure completeness, then data completeness is achieved, but network traffic and transfer time are maximized
Solution Approach 1:
The patent creates a copy of the data set on portable storage before cloud migration. This copy serves as a reference to determine which data objects were deleted or modified locally, allowing the system to upload only those specific objects to the cloud rather than the entire data set, significantly reducing transfer time while maintaining completeness.
Solution Approach 2:
The system extracts and identifies only the specific data objects that need to be uploaded to the cloud based on comparisons with the portable storage copy. This extraction approach eliminates unnecessary transfer of unchanged data, reducing network traffic and transfer time while ensuring all necessary data is uploaded for completeness.
Data Source
Figure 1A~1C
Figure 2
Figure 3
AI summary
Embodiments described herein are directed to enabling a user to modify data stored locally during a data migration process in which the user's data is being transferred to the cloud. For instance, a synchronization service requests the user's device (e.g., a client-based server) to provide a hash value for each data object maintained thereby (including modified data objects) and compares the hash values to hash values generated for the data uploaded to the cloud. If a hash value provided by the server does not match any of the hash values generated for the uploaded data, this means that the data object associated with the unmatched hash value has been modified since the initiation of the data transfer process. The synchronization service receives the modified data object from the server and uploads it to the cloud, thereby synchronizing the data uploaded to the cloud with the data locally-maintained by the server.