Transaction Store for Secure Distributed Data Updates
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing methods for updating distributed data stores are inefficient and lack security, as they often require transferring large amounts of data and may reveal sensitive information during the update process.
Innovation Solution
The use of a transaction store that includes cryptographic hashes and indicators of unchanged data to efficiently and securely update distributed data stores by identifying and applying differences between versions of the data, ensuring data integrity and security through minimal data transfer and encryption.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Quantity of substance
If traditional methods are used to update distributed data stores, then data can be updated, but large amounts of data must be transferred and security is compromised
Solution Approach 1:
The patent extracts only the necessary change information from the full data store by comparing versions and identifying differences. Instead of transferring the entire data store, only the delta (changes) is extracted and transferred, reducing data volume while maintaining security through cryptographic hashing of the extracted differences.
Solution Approach 2:
The patent introduces a transaction store as an intermediary component that mediates between the master data store and distributed replicas. The transaction store contains cryptographic hashes and difference indicators, serving as a secure intermediary that enables updates without direct exposure of the full data store, thus enhancing security while reducing transfer volume.
2Productivity
If traditional update methods are used, then data can be synchronized, but sensitive information is revealed during the update process
Solution Approach 1:
The patent extracts only the difference information between data versions for synchronization, excluding all unchanged data and sensitive information. By extracting only the delta and using cryptographic hashes, the system achieves fast synchronization without revealing sensitive data during the update process.
Solution Approach 2:
The patent creates a cryptographic copy (hash) of the data store version and uses this copy for comparison and update verification. The transaction store contains these cryptographic copies that enable synchronization verification without exposing the actual sensitive data, thus preventing information leakage while maintaining synchronization productivity.
3Reliability
If full data store transfer is used for updates, then all data is ensured to be updated, but the update process becomes inefficient
Solution Approach 1:
The patent segments the data store update process into two parts: (1) identifying differences between versions using cryptographic hashes, and (2) transferring only those differences. This segmentation ensures that all necessary data is updated (completeness) while minimizing the transfer volume (efficiency).
Solution Approach 2:
The patent applies partial action by transferring only the necessary difference information rather than the complete data store. The transaction store contains selective update information (partial action) that is sufficient to achieve complete updates at the distributed nodes, thereby improving efficiency without sacrificing update completeness.
Data Source
AI summary
Embodiments include systems and methods for updating a data store in a distributed data store system. In one embodiment, a previous version of a data store is compared to an updated version of the data store in order to create a transaction store. The transaction store may include a cryptographic hash indicative of the previous version of the data store and a cryptographic hash indicative of the updated version of the data store. The transaction store further indicates data differences between the previous and updated versions of the data stores. The transaction store may then be used to update data stores at other locations.