Data Retrieval via Reference Search Segmentation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Data retrieval in field conditions is inefficient due to slow data transmission links, especially when large amounts of data are involved, as existing solutions often result in excessive data transfer when data is updated fragmentarily, leading to the creation of new segments and increased data transmission.
Innovation Solution
The method involves utilizing stored reference search results on both the requesting and responding sides, where the requesting side indicates specific reference searches, and the responding side transmits only changes to these search results, reducing the amount of data transmitted and avoiding the need for full data replication on both sides.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If data is segmented and stored on server-side and client-side, then data transmission efficiency is improved for slow links, but when data is updated fragmentarily, new segments are created and the whole data is sent, resulting in bigger data transmission
Solution Approach 1:
The patent segments data into multiple segments with identifiers, allowing the system to work with individual segments rather than treating data as a single block. This enables selective transmission of only modified segments while maintaining the benefits of segmentation for efficient storage and retrieval.
Solution Approach 2:
The patent extracts only the modified portions of data (changed segments) from the complete dataset and transmits only these extracted changes to the client. This avoids transmitting the entire dataset when only partial updates occur, directly resolving the contradiction between maintaining segmentation benefits and avoiding excessive data transmission.
2Reliability
If the client requests data segments from the server, then the client receives up-to-date data, but the transmission takes a lot of time over slow links
Solution Approach 1:
The server extracts and transmits only the specific changed segments that the client needs to update, rather than transmitting complete datasets or unnecessary data. This extraction approach maintains data freshness by sending updated segments while minimizing transmission time over slow links by excluding unchanged data.
Solution Approach 2:
The system performs preliminary actions by maintaining segment identifiers and change information on both server and client sides, enabling the client to request only specific updated segments rather than discovering changes through full data retrieval. This preliminary preparation reduces transmission time while ensuring data freshness.
3Reliability
If new segments are created when data is updated, then data freshness is maintained, but the amount of data to be transmitted increases
Solution Approach 1:
Instead of creating and transmitting entirely new segments when data is updated, the system extracts only the specific changes or differences from the original segments and transmits these extracted modifications. This maintains data freshness while significantly reducing the volume of transmitted data compared to sending complete new segments.
Solution Approach 2:
The system changes the parameter of data transmission from transmitting complete segment data to transmitting only change information or differences. This parameter change in transmission strategy maintains data freshness by updating segments with changes while reducing transmission volume by not sending redundant unchanged portions.
4Speed
If the client contains a replicate of the whole data storage, then data retrieval is fast, but memory usage increases and synchronization becomes complex
Solution Approach 1:
The patent segments the complete data storage into multiple smaller segments, allowing the client to store and manage only relevant segments locally rather than maintaining a complete replicate. This segmentation approach provides fast retrieval for accessed segments while reducing overall storage requirements and simplifying synchronization by working with individual segments rather than complete datasets.
Solution Approach 2:
Instead of requiring the client to have a complete replicate of all data storage (excessive action), the system implements partial replication where the client stores only the segments it needs or has accessed. This partial approach maintains fast retrieval speed for available segments while reducing storage complexity and synchronization overhead.
Data Source
AI summary
To facilitate obtaining up-to-date data over a slow connection, reference search results are stored on a requesting side and on a responding side, and only changes to reference searches are transmitted. To achieve this, the requesting side indicates in a data request an applicable reference search or reference searches to be used, and the responding side retrieves up-to-date data, compares it with search results of corresponding applicable reference search(es) and sends only changes to the requesting side.