Instant Messaging Key-Value Data Release Mechanism
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In instant messaging, existing methods for releasing key-value data either waste network bandwidth by pulling full data each time a user logs in or inefficiently transfer updated data due to serial number-based mechanisms, where only minor changes require the transfer of large amounts of data.
Innovation Solution
A method and system that utilize a request packet containing a full-amount pulling timestamp, an increased-amount pulling timestamp, and a data-altering serial number to select a pre-set data releasing mechanism, allowing the server to release either full or increased key-value data, or none, ensuring data consistency and reducing bandwidth waste by only transferring modified data.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If full amount key-value data is pulled from the server each time the client logs in, then data consistency between client and server is ensured, but network bandwidth is enormously wasted
Solution Approach 1:
The patent extracts only the necessary portion of data (incremental changes) from the full key-value data set. By using version timestamps and change logs, the system identifies and transfers only the data that has been modified since the last synchronization, rather than transferring the entire data set. This resolves the contradiction by maintaining data consistency through selective data transfer while minimizing network bandwidth consumption.
Solution Approach 2:
The patent segments the key-value data into versioned portions, dividing the data synchronization process into incremental updates rather than a single full transfer. Each data change is tracked with a version timestamp, allowing the system to segment the transfer into small, targeted increments. This segmentation approach ensures consistency by systematically updating each segment while reducing overall bandwidth usage compared to transferring the complete data set repeatedly.
2Loss of energy
If serial number is added to key-value data to track changes, then network bandwidth waste is reduced, but network bandwidth usage rate becomes very low when large amounts of data need to be transferred due to minor changes
Solution Approach 1:
The patent uses version timestamps as a parameter change mechanism to track data modifications. Instead of relying solely on serial numbers, the system increments version timestamps when key-value data changes occur. This parameter change approach allows the system to efficiently identify modified data segments and transfer only those portions, improving bandwidth usage rate by accurately matching the transfer size to the actual data changes rather than transferring entire data sets based on serial number comparisons.
3Reliability
If full amount key-value data is transferred even when only minor changes occur, then data consistency is maintained, but network bandwidth is wasted due to transferring unnecessary data
Solution Approach 1:
The patent extracts only the modified key-value data segments from the complete data set by comparing version timestamps. When the client logs in, it sends its current version timestamp to the server, and the server identifies and transfers only the data that has changed since that timestamp. This extraction principle maintains data consistency by ensuring all changes are captured while dramatically reducing the volume of data transferred compared to sending the full data set.
Solution Approach 2:
The patent applies partial action by transferring only the necessary portion of data (the incremental changes) rather than the complete data set. The system performs a partial synchronization based on version timestamps, transferring exactly the amount of data needed to maintain consistency without the excess of transferring unchanged data. This partial action approach resolves the contradiction by achieving the minimum necessary data transfer volume while ensuring data consistency.
Data Source
AI summary
Methods, servers, clients, and systems for releasing instant messaging key-value data are provided. A server receives a request packet for pulling key-value data sent from a client during a login. The request packet at least contains a full-amount pulling time-stamp, an increased-amount pulling time-stamp, and a data-altering serial number. The server selects a pre-set data releasing mechanism according to parameters contained in the request packet, to release full amount key-value data to the client or to release increased amount key-value data to the client, or not to release the key-value data, such that, according to a returned result from the server, the client updates local cache data to display to a user.