Temporal Database Architecture for Document Mapping Reconstruction
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current computer systems lack the ability to effectively track and manage changes in relationships between documents over time, leading to memory resource consumption and latency issues when trying to store multiple versions of document mappings, which affects system performance and throughput.
Innovation Solution
A temporal database architecture is used to store data, allowing relationships between documents to be tracked and reconstructed by maintaining a change history log, reducing the need to store each version of the mapping and eliminating manual intervention for reconstructing previous mappings.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If each version of the mapping is saved as a new file, then the ability to track relationship changes between documents is improved, but memory resource consumption increases
Solution Approach 1:
The patent segments the mapping data into two parts: the current mapping data and the change history log. Instead of storing complete copies of every version, the system stores only the changes (differences) between versions in the change history log. This segmentation allows tracking of relationship changes while consuming less memory than storing full copies of each version.
Solution Approach 2:
The patent creates a virtual copy of previous mapping versions by reconstructing them from the current mapping data and the change history log. When a previous version is needed, the system copies the current mapping and applies the stored changes in reverse to reconstruct the historical version, avoiding the need to store actual copies of past versions in memory.
2Reliability
If manual intervention is used to determine previous mappings, then the ability to reconstruct historical relationships is improved, but system latency increases
Solution Approach 1:
The patent performs preliminary action by automatically recording all mapping changes in the change history log as they occur. This preliminary recording of changes eliminates the need for manual intervention later when reconstructing historical mappings. The system is prepared in advance with all necessary change information, enabling fast automated reconstruction of previous versions without human involvement.
Solution Approach 2:
The system performs self-service by automatically reconstructing previous mapping versions using the stored change history log. When a historical mapping is needed, the system autonomously retrieves the current mapping, applies the stored changes in reverse chronological order, and generates the historical version without requiring manual intervention. This self-service capability reduces system latency and eliminates human involvement in the reconstruction process.
3Adaptability or versatility
If the system manages a large number of documents with frequent mapping changes, then the document management capability is improved, but memory resources are quickly consumed
Solution Approach 1:
The patent segments mapping data storage into current mapping data and incremental change records. This segmentation allows the system to manage large numbers of documents with frequent changes efficiently, as only the changes (not entire mappings) are stored in the change history log, significantly reducing memory consumption compared to storing complete versions of all mappings.
Solution Approach 2:
The patent changes the parameter of data storage from storing complete mapping objects to storing only the differences (changes) between mappings. This parameter change in the storage approach allows the system to handle high volumes of document mappings and frequent updates without proportionally increasing memory resource consumption, as the change records are much smaller than full mapping copies.
Data Source
AI summary
A device is configured to receive a reconstruction request that identifies a time instance value and an identifier for a portion of a document. The device is further configured to identify a time window between a current time value and the time instance value and to identify entries within a change history log within the time window that are associated with the identifier for the portion of the document. The device is further configured to generate a reconstructed document mapping by undoing the changes to the document mapping based on the identified entries within the change history log that are within the time window and that are associated with the identifier for the portion of the document. The device is configured to undo the changes that were performed by the identified entries in a reverse chronological order. The device is further configured to output the reconstructed document mapping.