Data Synchronization Server Using Version Identification
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing data synchronization methods in weak networking games face issues with slow synchronization speed, poor security due to client-generated assets, and inability to ensure data consistency between clients and servers, especially when multiple clients synchronize data simultaneously or repeatedly.
Innovation Solution
A data synchronization method that receives a data synchronization request from a client, determines if the current version identification of the asset is the latest, and if so, generates a changed target asset and a target version identification. This method sends status update prompts to the client to update the asset change information list, ensuring that the server calculates and generates the changed asset, enhancing security and consistency.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the client uploads full assets every time data is synchronized, then the server can store complete asset information, but the data synchronization speed becomes slow due to large data volume
Solution Approach 1:
The patent segments the asset data transmission by dividing full assets into asset change information lists that only contain modified portions. Instead of uploading complete asset packages, the system transmits only the necessary change data (additions, deletions, modifications), significantly reducing transmission volume while maintaining data completeness on the server side.
Solution Approach 2:
The patent extracts only the essential change information from the full assets. The asset change information list contains only the necessary modification details (asset IDs, change types, new values) rather than complete asset packages, allowing the server to reconstruct full asset information by applying these extracted changes to existing data.
2Productivity
If the client generates changed full assets locally, then the client can prepare synchronization data in advance, but data security deteriorates because client-generated data can be easily tampered with
Solution Approach 1:
The patent introduces an intermediary verification mechanism where the server validates the asset change information lists received from clients. The server checks whether the changes are legitimate and consistent with server-side records, acting as a mediator that allows efficient client-side preparation while preventing unauthorized tampering through server-side verification and approval.
Solution Approach 2:
The patent implements a feedback loop where the server responds to client synchronization requests with validation results. If the asset change information is legitimate, the server processes it and confirms acceptance; if tampered with or inconsistent, the server rejects it and provides feedback, enabling the client to correct issues. This feedback mechanism maintains security while allowing efficient preprocessing.
3Ease of manufacture
If timestamps are used as version numbers for data synchronization requests, then the implementation is simple, but the sequential order of multiple simultaneous synchronization operations cannot be identified, leading to data consistency errors
Solution Approach 1:
The patent changes the version identification parameter from simple timestamps to a composite identifier that includes both timestamp and request sequence number. This parameter transformation allows the system to maintain implementation simplicity while resolving the ambiguity of simultaneous requests, as each request receives a unique version ID that reflects both its time of creation and its position in the submission sequence.
Data Source
AI summary
The present disclosure provides a data synchronization method and a server, the method including: receiving a data synchronization request submitted by a client, determining whether a current version identification of a to-be-changed asset in the data synchronization request is a latest version identification; if yes, changing the to-be-changed asset according to an asset change information list in the data synchronization request to generate a changed target asset; generating a target version identification according to the current version identification and the changed target asset; sending status update prompt information to the client according to the target version identification to prompt the client to update the asset change information list; where the current version identification is a target version identification generated when data synchronization is performed on the to-be-changed asset last time. The method of the present disclosure improves the speed and security of data synchronization, and can ensure data consistency.