CN101064630A - Data synchronization method and system - Google Patents
Data synchronization method and system Download PDFInfo
- Publication number
- CN101064630A CN101064630A CN 200610076027 CN200610076027A CN101064630A CN 101064630 A CN101064630 A CN 101064630A CN 200610076027 CN200610076027 CN 200610076027 CN 200610076027 A CN200610076027 A CN 200610076027A CN 101064630 A CN101064630 A CN 101064630A
- Authority
- CN
- China
- Prior art keywords
- data
- client
- record
- server
- version number
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Abstract
The invention discloses a data synchronization method which is used in data synchronization between client and server. It includes: the user data recording is set with recording version number which is increased by degrees as operation sequence; the client takes the maximum recording version number of local-storage user data recording as the overall recording version number of client data; when client logs on server, the client sends data synchronization request to server, with said overall recording version number of client data; server judges whether said overall recording version number of client data is the same with overall recording version number of user data, when they are different, server sends data recording whose recording version number is bigger than overall recording version number of client data to client for data synchronization. The invention also discloses a corresponding data synchronization system. The invention can realize real time data synchronization between client and server efficiently.
Description
Technical field
The present invention relates to data sync, relate in particular to a kind of method of data synchronization and system based on client/server model.
Background technology
The internet provides abundant service for people, such as the address book management, and the chat record management.The characteristics of these services are based on client/server (C/S) model, and the user is by client and server interaction.Because client terminal quantity is huge, client needs to beam back data and process request to server continually, performance requirement to server is very high, in the situation of low bandwidth or high latency, situation can be worsened, and the performance issue of generation may cause application availability and user's efficient to descend significantly.In order to improve the performance of client operation, current a lot of system has adopted in client deployment code and data, carries out and visit data in this locality, passes through local data cache, the data volume of minimizing from the client transmissions to the server, and then performance and the practicality of raising system.All there are data in this processing mode client and server, and it is synchronous that system need carry out data necessary.Such as: in chat tool, the user carries out address book in client and safeguards, add associated person information, revise contact number, delete contact person etc., revise the data of client behind system's modification server data again, these operations may be carried out in a plurality of clients, like this, the data of each client and server data may be inconsistent, and the data that cause client operation are not the problems of latest data.
The synchronization scenario of prior art one:
Download synchronization scenario fully, the user at first downloads all data of correlation table from server before client operates local data base at every turn, finish synchronously, carries out then attended operation.
The shortcoming of prior art one:
The data volume of tables of data is general bigger, frequent data download fully, and efficient is low, has a strong impact on server performance, has with the target of local data scheme raising performance and conflicts, and is unavailable in the big system of data volume.
The synchronization scenario of prior art two:
Database Systems are responsible for Synchronous Processing, and which table of system definition needs to get final product synchronously, and the row level of database and row level detect and guarantee synchronously.
The shortcoming of prior art two:
This scheme needs client to possess local data base, and the operational outfit of client is required than higher.
Summary of the invention
The invention provides a kind of method of data synchronization, in order to solve the problem low and that server and client device are had relatively high expectations of data synchronization efficiency between the client and server that exists in the prior art.
According to method provided by the invention, the present invention provides a kind of corresponding data synchronization system in addition.
The inventive method comprises: to the user data record record version this shop that setting increases progressively according to operating sequence; The dominant record version number that the user data that client is stored this locality records is as the total version number of client data; The dominant record version number that this user data that server is stored this locality records is as the total version number of this user data;
When accessing server by customer end, carry out the following step:
A, user end to server are initiated data synchronization request, carry the total version number of described client data;
B, server judge whether the total version number of described client data is identical with the total version number of this user data, when both are inequality, server sends to client with the record version this shop of this locality storage this user's data record greater than the total version number of client data, carries out data sync.
Also comprise before the described steps A: client judges whether local data file exists or damage; When local data file does not exist or damaged, create new data file;
In the described steps A, described user end to server is initiated data synchronization request, and carrying the total version number of client data is 0;
Among the described step B, server sends to described client with whole user data records of this user of this locality storage, carries out the data Complete Synchronization and records the Complete Synchronization time.
According to said method of the present invention, also comprise described accessing server by customer end after, initiate the data recording operation request to described server, carry action type information;
Described server is carried out corresponding operating according to the action type of request to the user data record, and the total version number of this user data that stores in return object information and the current server;
Described client is carried out corresponding operating to the local user data record, and the total version number of renewal client data is the total version number of this user data that server returns.
According to said method of the present invention, when described user end to server is initiated newly-increased data record request, carry action type and be newly-increased record;
Described server increases a user data record newly, and the record version this shop of this newly-increased record is set; The total version number of this user data of update server end storage; And obtain the address information of this client, return newly-increased record operating result and upgrade after the total version number of this user data;
The newly-increased corresponding user data record of described client, and the total version number of renewal client data is the total version number of this user data that server returns.
According to said method of the present invention, when described user end to server was initiated the delete data record request, carrying action type was deletion record;
Described server arranges deleted marker, upgrades its record version this shop the user data record of request deletion; The total version number of this user data of update server end storage; And obtain the address information of this client, return the deletion record operating result and upgrade after the total version number of this user data;
The local corresponding user data record of the real deletion of described client, and the total version number of renewal client data is the total version number of this user data that server returns.
According to said method of the present invention, described server is regularly carried out real deletion action, the local user data record that deleted marker is arranged of deletion; And the last corresponding time of carrying out real deletion action of record.
According to said method of the present invention, when accessing server by customer end was initiated data synchronization request, described server was also judged the time whether the Complete Synchronization time of this client carry out real deletion action early than the last time; If so, this user's of this locality storage total data record is sent to this client, carry out the data Complete Synchronization, and carry the total version number of this user data.
According to said method of the present invention, when described user end to server was initiated the Update Table record request, carrying action type was amendment record;
The user data record that described server is revised request carries out earlier real deletion, and the data record of a newly-increased correspondence arranges the record version this shop that this increases record newly again; The total version number of this user data of update server end storage; And obtain the address information of this client, return the amendment record operating result and upgrade after the total version number of this user data;
Described client is revised local corresponding user data record, and the total version number of renewal client data is the total version number of this user data that server returns.
According to said method of the present invention, when the user has two or more accessing server by customer end simultaneously, and the data recording operation request that server is initiated according to one of them client, after user data record operated, obtain the address information of listed all the other clients, send to all the other clients with the data record of variation and the total version number of this user data after the variation have taken place;
Described all the other clients are carried out corresponding operating to the local user data record respectively, and the total version number of client data of the local storage of renewal is the total version number of this user data that server returns.
Described record version this shop is the progressive whole number value, or is the correspondent time of current concrete time of expression.
The invention provides a kind of data synchronous system, comprise client and server, described client includes the synchronization request performance element, is used for initiating data synchronization request to server, carries the total version number of client data; The total version number of described client data is the dominant record version number of client terminal local storage user data record;
Described server includes synchronous judgement performance element, be used to receive the data synchronization request of client, judge whether the total version number of described client data is identical with the total version number of this user data, the total version number of described this user data is the dominant record version number of this user data record of server stores; When both were inequality, server sent to client with the record version this shop of this locality storage this user's data record greater than the total version number of client data, carries out data sync.
Described client also comprises the first data recording operation unit, initiates the data recording operation request to described server, carries action type information; After receiving the operation result information and the total version number of this user data that server returns, the local user data record is carried out corresponding operating, and to upgrade the total version number of client data be the total version number of this user data that server returns;
Described server also comprises the second data recording operation unit, according to the action type of client-requested corresponding operating is carried out in the user data record, and the total version number of this user data that stores in client return object information and the current server.
The described second data recording operation unit comprises:
The record operation executing module is carried out corresponding operating according to the action type of client-requested to the user data record;
Record version this shop generation module generates the new record version this shop that increases progressively to operated user data record;
The total version updating sending module of user data, the dominant record version number that this user data that this locality is stored records is as the total version number of this user data and send to client.
Beneficial effect of the present invention is as follows:
(1) the present invention adopts the user data record record version this shop that setting increases progressively according to operating sequence; The dominant record version number that the user data that client is stored this locality records is as the total version number of client data; The dominant record version number that this user data that server is stored this locality records is as the total version number of this user data; When accessing server by customer end, user end to server is initiated data synchronization request, carries the total version number of client data; Judge by server whether the total version number of client data is identical with the total version number of this user data, when both are not identical, server sends to client with the record version this shop of this locality storage data record greater than this user of the total version number of client data, and it is synchronous to carry out data.Like this, the synchronous amount of data only is the difference part between client and the server, and synchronous data volume is little, has reduced interaction data amount and the interaction times of client and server, has improved data synchronization efficiency.
(2) two or more accessing server by customer end is arranged simultaneously as the user, and the data recording operation request that server is initiated according to one of them client, after user data record operated, obtain the address information of listed all the other clients, send to all the other clients with the data record of variation and the total version number of this user data after the variation have taken place; All the other clients are carried out corresponding operating to the local user data record respectively, and the total version number of client data of the local storage of renewal is the total version number of this user data that server returns.Like this, a plurality of client datas of same user are realized real-time synchronization, guaranteed accuracy and the integrality of each client data.
Description of drawings
Fig. 1 is the Signalling exchange flow chart of embodiment of the invention accessing server by customer end;
Fig. 2 is for asking to Add User data record signaling process figure after the embodiment of the invention accessing server by customer end;
Fig. 3 is a system configuration schematic diagram of the present invention.
Embodiment
Method of data synchronization provided by the invention is applied to the data sync between the client and server.Below in conjunction with accompanying drawing the inventive method is described in detail.
At server end, for each user sets up one or more user data tables, storage user's user data record.Between server and client, what needs were synchronous is this user's user data.
In server, record version this shop for a correspondence of each bar recording setting of each user data of users, this record version this shop is set to a progressive whole number value according to the operating sequence to the user data record, or be set to time corresponding and stab, as YYYYMMDDHHMMSS, the expression current record operating time for certain the year in such a month, and on such a day the some time divide certain second, with this record version this shop as this data record.
In server, the corresponding total version number of this user data of server end of each user data of users.Adopt record version this shop corresponding to operated the last item user data record as this user's the total version number of server end user data; Be server with the dominant record version number of the user record of this locality storage as the total version number of this user data.If adopt timestamp as record version this shop, then the total version number of server end user data is nearest timestamp.
The present invention also handles in two steps to the user data record of needs deletions: the first step, and the user data of needs deletion is recorded in server end delete flag is set, be called pseudo-deletion; In second step, server is regularly carried out real deletion action, and the record that is provided with delete flag is really deleted from this locality.
Server end also needs to store some corresponding management information in order to realize management and the data sync to each user.For example:
(1) at the complete synchronous recording table of server end storage user, as shown in table 1 below:
Table 1:
| User's name | The last Complete Synchronization time |
| AAA | 20050627090909 |
| BBB | 20050627110906 |
| ZZZ | 20050627132308 |
(2) at the total version number of server end storaging user data record sheet, as shown in table 2 below:
Table 2:
| User's name | The total version number of this user data of server end |
| AAA | 3 |
| BBB | 4 |
| ZZZ | 20 |
The total version number of user data in the table 2 also can be timestamp, and when the user data record has been carried out operation, carries out corresponding change.For example, when server is revised the user record data of user AAA, then the record version this shop of this record must change into one and supposes that greater than 3 integer value the record version this shop of this record becomes 4, and then user AAA also becomes 4 in the total version number of the current data of server end.
(3) storage user's call log table in server, as shown in table 3 below:
Table 3:
| User's name | The daily record sign | The record version this shop of user data | |
| AAA | |||
| 1 | 2 | Newly-increased | |
| AAA | 2 | 3 | Revise |
| BBB | 3 | 5 | Revise |
| BBB | 4 | 4 | Newly-increased |
| BBB | 5 | 3 | Deletion |
In the table 3, the record version this shop of user data to same user, can not exist two records to have identical record version this shop; But, can have identical record version this shop for different users.Be that 3 user data is made amendment such as the user AAA in the table 3 request to oneself record version this shop; User BBB request is that 3 user data is deleted to oneself record version this shop; Although two the record version this shop of data record all is 3, owing to be the data that belong to different user, therefore, can have identical record version this shop.
(4) storage client log-on message table in server, as shown in table 4 below:
Table 4:
| User's name | Client ip | The client end slogan |
| AAA | 192.168.11.110 | 5060 |
| BBB | 192.168.23.173 | 3089 |
| ZZZ | 192.168.19.181 | 4080 |
In server, also store the last time that user data is carried out real deletion action, when complete lock in time of client early than the last time of carrying out real deletion action of server, then must carry out once fully synchronously: promptly delete the client data file client, rebulid new data file, whole record data of this user of storing in the server are all sent to this subscription client.
When subscription client first behind the logon server, server sends to this client with this user's of this locality storage whole user data and the corresponding total version number of user data; Client is stored user data in this locality, and the total version number of user data that server is sent realizes the data Complete Synchronization first as the total version number of local client data.
When client again behind the logon server, initiatively initiate data synchronization request to server, carry the total version number of client data of local storage; Server compares the total version number of this user data of the total version number of the client data that receives and server stores, if both are identical, represents that this user's data are synchronous; If the total version number of client data is littler, represent that then the client and server end data is asynchronous, server sends to this client with the record version this shop of this locality storage greater than this user's of the total version number of client data record data, and it is synchronous to carry out data.
Take individual address address book synchronously as example, the concrete steps flow chart comprises as shown in Figure 1:
1, the user initiates the application of logon server by client;
2, server carries out the legitimacy authentication to the user, after authentication is passed through, and record client ip address and port numbers, and return corresponding information, present to user's (as: some exercisable feature lists, some data of individual subscriber etc.) by client;
3, client judges at first whether individual client's end communication book file exists or whether damage; If file does not exist or damages, then execution in step 4; Otherwise, direct execution in step 5;
If 4 files do not exist, then create file, and the total version number of client data is set is 0; If file corruption, then deletion creates new file after having damaged file again, and the total version number of client data is set is 0; If file exists and do not damage, continue step 5;
5, client is initiated data synchronization request, carries the total version number information of client data;
If 6 servers are judged the total version number of client data and are equaled 0, then read user communication book data in the server, carry out fully synchronously;
If server is judged the total version number of client data greater than 0, whether the last lock in time fully of then further judging this user data is early than the last real deletion time of server end, if then must carry out fully synchronously; Otherwise server is selected the record of this user communication book data record version number greater than the total version number of client data of carrying in the synchronization request, sends to client; If there be not the respective record of data record version number in the server, represent that then data are synchronous greater than the total version number of client data;
7, server returns the user's who obtains in sync id, the step 6 address book record and the total version number of this user data of users of server end to client;
8, client analyzes according to sync id whether needs carry out synchronous fully or partly synchronous; Fully synchronously, then delete the client data file if desired, build new data file again, and write down complete lock in time;
If only need Partial synchronization, then the action type of synchronous record correspondence is carried out respective handling as required; If action type then increases a respective record in client for newly-increased type; If action type is then deleted earlier corresponding record for revising type in the client data file, increase then a record; If action type is then carried out record deletion for the deletion type in the client data file; And the total version number of renewal client data is the total version number of user data that server end returns.
Above flow process realizes that data are synchronous during for accessing server by customer end.Behind accessing server by customer end, client can be initiated the data recording operation application to server, carries the moral conduct type information, and for example: the user end to server request increases record, deletion record or amendment record newly; Server is operated corresponding record according to action type after receiving the recording operation request of client initiation, and the total version number of user data after return object information and the renewal.
If the user has two or more accessing server by customer end simultaneously, the data recording operation request that server is initiated according to one of them client, after user data record operated, obtain the address information of listed all the other clients, send to all the other clients with the data record of variation and the total version number of this user data after the variation have taken place; All the other clients are carried out corresponding operating to local user data record respectively, and the total version number of client data that upgrades local storage is the total version number of this user data that server returns, and realize that data are synchronous.
As shown in Figure 2, when asking to increase record newly in address book for user's client 1, realize the synchronous flow chart of data by server, concrete steps comprise:
1, the user increases by a contact person by client 1 in address book, and the client query local data is judged not have this record, initiates newly-increased record application to server;
If 2 and 3 servers are judged this record and do not existed, then increase a user data record newly; The action type of this record is set to increase newly, and the record version this shop of this record is set, and the total version number of this user data of update server end;
If server is judged this record and is existed, to carry out data synchronous with server because client is in when login, then this nearest action type that is recorded in server end should be the deletion type, in this case, the action type that server will record changes to newly-increased, the record version this shop of this record is set, and this user's of update server end the total version number of data;
4, server obtains the IP address and the port numbers of client 1, and return object information and this user are in the total version number of the user data of server end;
5, client 1 increases corresponding record newly in this locality;
6, client 1 is upgraded the total version number of user data that the total version number of client data that stores this locality is the server end transmission.
If the record that server will increase newly has joined in the address book of other logging on client of user simultaneously, then need other clients of having logined of user are carried out data sync, concrete steps comprise:
4 ', server obtains the IP address and the port numbers of listed other client 2, sends synchronous updating message, notice client 2 newly-increased records, and carry the total version number of this user data of server end;
5 ' client 2 is newly-increased corresponding record in this locality;
The total version number of client data that 6 ' client 2 is upgraded local storage is the total version number of user data that server end sends.
According to said method provided by the invention, the present invention provides a kind of corresponding data synchronization system in addition, and its structural representation comprises as shown in Figure 3: comprise client and server, wherein:
Client includes the synchronization request performance element, is used for initiating data synchronization request to server, carries the total version number of client data; The total version number of described client data is the dominant record version number of client terminal local storage user data record;
Server includes synchronous judgement performance element, be used to receive the data synchronization request of client, judge whether the total version number of described client data is identical with the total version number of this user data, the total version number of described this user data is the dominant record version number of this user data record of server stores; When both were inequality, server sent to client with the record version this shop of this locality storage this user's data record greater than the total version number of client data, carries out data sync.
Described client also comprises the first data recording operation unit, initiates the data recording operation request to server, carries action type information; After receiving the operation result information and the total version number of this user data that server returns, the local user data record is carried out corresponding operating, and to upgrade the total version number of client data be the total version number of this user data that server returns;
Server also comprises the second data recording operation unit, according to the action type of client-requested corresponding operating is carried out in the user data record, and the total version number of this user data that stores in client return object information and the current server.
The second data recording operation unit further comprises:
The record operation executing module is carried out corresponding operating according to the action type of client-requested to the user data record;
Record version this shop generation module generates the new record version this shop that increases progressively to operated user data record;
The total version updating sending module of user data, the dominant record version number that this user data that this locality is stored records is as the total version number of this user data and send to client.
In sum, the present invention is by in the accessing server by customer end process, initiatively initiate data synchronization request by client, the record version this shop that server is only stored this locality sends to client, like this greater than this user's of the total version number of client data data record, the synchronous amount of data only is the difference part between client and the server, synchronous data volume is little, has reduced interaction data amount and the interaction times of client and server, has improved data synchronization efficiency.
Behind the accessing server by customer end, can initiate the data recording operation request, as newly-increased data, deleted data and modification data, server and client side's data are upgraded synchronously.And when the user has two or more accessing server by customer end simultaneously, and the data recording operation request that server is initiated according to one of them client, after user data record operated, by obtaining the address information of listed all the other clients, with having taken place, the data record of variation and the total version number of this user data after the variation send to all the other clients; All the other clients are carried out corresponding operating to the local user data record respectively, and the total version number of client data of the local storage of renewal is the total version number of this user data that server returns.Like this, a plurality of client datas of same user are realized real-time synchronization, guaranteed accuracy and the integrality of each client data.
Obviously, those skilled in the art can carry out various changes and modification to the present invention and not break away from the spirit and scope of the present invention.Like this, if of the present invention these are revised and modification belongs within the scope of claim of the present invention and equivalent technologies thereof, then the present invention also is intended to comprise these changes and modification interior.
Claims (13)
1, a kind of method of data synchronization, the data that are applied between the client and server are synchronous, it is characterized in that, comprising: to the user data record record version this shop that setting increases progressively according to operating sequence; The dominant record version number that the user data that client is stored this locality records is as the total version number of client data; The dominant record version number that this user data that server is stored this locality records is as the total version number of this user data;
When accessing server by customer end, carry out the following step:
A, user end to server are initiated data synchronization request, carry the total version number of described client data;
B, server judge whether the total version number of described client data is identical with the total version number of this user data, when both are inequality, server sends to client with the record version this shop of this locality storage this user's data record greater than the total version number of client data, carries out data sync.
2, the method for claim 1 is characterized in that, also comprises before the described steps A: client judges whether local data file exists or damage; When local data file does not exist or damaged, create new data file;
In the described steps A, described user end to server is initiated data synchronization request, and carrying the total version number of client data is 0;
Among the described step B, server sends to described client with whole user data records of this user of this locality storage, carries out the data Complete Synchronization and records the Complete Synchronization time.
3, method as claimed in claim 2 is characterized in that, also comprise described accessing server by customer end after, initiate the data recording operation request to described server, carry action type information;
Described server is carried out corresponding operating according to the action type of request to the user data record, and the total version number of this user data that stores in return object information and the current server;
Described client is carried out corresponding operating to the local user data record, and the total version number of renewal client data is the total version number of this user data that server returns.
4, method as claimed in claim 3 is characterized in that, when described user end to server is initiated newly-increased data record request, carries action type and is newly-increased record;
Described server increases a user data record newly, and the record version this shop of this newly-increased record is set; The total version number of this user data of update server end storage; And obtain the address information of this client, return newly-increased record operating result and upgrade after the total version number of this user data;
The newly-increased corresponding user data record of described client, and the total version number of renewal client data is the total version number of this user data that server returns.
5, method as claimed in claim 3 is characterized in that, when described user end to server was initiated the delete data record request, carrying action type was deletion record;
Described server arranges deleted marker, upgrades its record version this shop the user data record of request deletion; The total version number of this user data of update server end storage; And obtain the address information of this client, return the deletion record operating result and upgrade after the total version number of this user data;
The local corresponding user data record of the real deletion of described client, and the total version number of renewal client data is the total version number of this user data that server returns.
6, method as claimed in claim 5 is characterized in that, described server is regularly carried out real deletion action, the local user data record that deleted marker is arranged of deletion; And the last corresponding time of carrying out real deletion action of record.
7, method as claimed in claim 6 is characterized in that, when accessing server by customer end was initiated data synchronization request, described server was also judged the time whether the Complete Synchronization time of this client carry out real deletion action early than the last time; If so, this user's of this locality storage total data record is sent to this client, carry out the data Complete Synchronization, and carry the total version number of this user data.
8, method as claimed in claim 3 is characterized in that, when described user end to server initiated to revise data record request, carrying action type was amendment record;
The user data record that described server is revised request carries out earlier real deletion, and the data record of a newly-increased correspondence arranges the record version this shop that this increases record newly again; The total version number of this user data of update server end storage; And obtain the address information of this client, return the amendment record operating result and upgrade after the total version number of this user data;
Described client is revised local corresponding user data record, and the total version number of renewal client data is the total version number of this user data that server returns.
9, as the described method of any claim of claim 1-8, it is characterized in that, when the user has two or more accessing server by customer end simultaneously, and the data recording operation request that server is initiated according to one of them client, after user data record operated, obtain the address information of listed all the other clients, send to all the other clients the data record of variation and the total version number of this user data after the variation have taken place;
Described all the other clients are carried out corresponding operating to the local user data record respectively, and the total version number of client data of the local storage of renewal is the total version number of this user data that server returns.
As the described method of any claim of claim 1-8, it is characterized in that 10, described record version this shop is the progressive whole number value, or be the correspondent time of current concrete time of expression.
11, a kind of data synchronous system comprises client and server, it is characterized in that:
Described client includes the synchronization request performance element, is used for initiating data synchronization request to server, carries the total version number of client data; The total version number of described client data is the dominant record version number of client terminal local storage user data record;
Described server includes synchronous judgement performance element, be used to receive the data synchronization request of client, judge whether the total version number of described client data is identical with the total version number of this user data, the total version number of described this user data is the dominant record version number of this user data record of server stores; When both were inequality, server sent to client with the record version this shop of this locality storage this user's data record greater than the total version number of client data, carries out data sync.
12, data synchronous system as claimed in claim 11 is characterized in that, described client also comprises the first data recording operation unit, initiates the data recording operation request to described server, carries action type information; After receiving the operation result information and the total version number of this user data that server returns, the local user data record is carried out corresponding operating, and to upgrade the total version number of client data be the total version number of this user data that server returns;
Described server also comprises the second data recording operation unit, according to the action type of client-requested corresponding operating is carried out in the user data record, and the total version number of this user data that stores in client return object information and the current server.
13, data synchronous system as claimed in claim 12 is characterized in that, the described second data recording operation unit comprises:
The record operation executing module is carried out corresponding operating according to the action type of client-requested to the user data record;
Record version this shop generation module generates the new record version this shop that increases progressively to operated user data record;
The total version updating sending module of user data, the dominant record version number that this user data that this locality is stored records is as the total version number of this user data and send to client.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2006100760274A CN101064630B (en) | 2006-04-24 | 2006-04-24 | Data synchronization method and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2006100760274A CN101064630B (en) | 2006-04-24 | 2006-04-24 | Data synchronization method and system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN101064630A true CN101064630A (en) | 2007-10-31 |
| CN101064630B CN101064630B (en) | 2011-09-21 |
Family
ID=38965374
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN2006100760274A Active CN101064630B (en) | 2006-04-24 | 2006-04-24 | Data synchronization method and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN101064630B (en) |
Cited By (60)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101902613A (en) * | 2010-07-21 | 2010-12-01 | 中兴通讯股份有限公司 | Information synchronization method and system, set top box and server in IPTV (Internet Protocol Television) system |
| CN102063494A (en) * | 2010-12-31 | 2011-05-18 | 青岛海信网络科技股份有限公司 | Database synchronizing method and device |
| CN102130929A (en) * | 2010-01-20 | 2011-07-20 | 金蝶软件（中国）有限公司 | Method and device for updating client testing server and testing server |
| CN102231881A (en) * | 2011-07-05 | 2011-11-02 | 广州市动景计算机科技有限公司 | Method, server and system for processing user data of mobile terminal |
| CN102325367A (en) * | 2011-09-29 | 2012-01-18 | 用友软件股份有限公司 | Data packet synchronizing device and method for client application |
| CN102546208A (en) * | 2010-12-13 | 2012-07-04 | 北大方正集团有限公司 | Device management method, system and device management server |
| CN102571923A (en) * | 2011-12-13 | 2012-07-11 | 中国电子科技集团公司第十五研究所 | Data synchronization system and method |
| CN102591901A (en) * | 2010-11-23 | 2012-07-18 | 三星电子株式会社 | Apparatus and method for synchronizing data in connected devices |
| CN101794297B (en) * | 2010-01-15 | 2012-07-25 | 北京中创信测科技股份有限公司 | Method and system for processing information data |
| CN102904887A (en) * | 2012-09-26 | 2013-01-30 | 东软集团股份有限公司 | Method and system for data synchronization of Web client and server |
| CN103136200A (en) * | 2011-11-22 | 2013-06-05 | 中兴通讯股份有限公司 | Data updating information obtaining method and device and data synchronization method and device |
| CN103152390A (en) * | 2013-02-04 | 2013-06-12 | 华为技术有限公司 | Method and device and nodes and system for node configuration of distributed storage system |
| CN103392330A (en) * | 2011-03-10 | 2013-11-13 | 阿玛得斯两合公司 | System and method for session synchronization with independent external systems |
| WO2013177925A1 (en) * | 2012-05-28 | 2013-12-05 | 腾讯科技（深圳）有限公司 | Data synchronization method, system and device |
| CN103532920A (en) * | 2012-07-06 | 2014-01-22 | 腾讯科技（深圳）有限公司 | Cookie update method and cookie update system |
| CN103595707A (en) * | 2013-10-17 | 2014-02-19 | 广东电网公司茂名供电局 | Automatic file network synchronization method based on SVN |
| CN103685191A (en) * | 2012-09-18 | 2014-03-26 | 英业达科技有限公司 | Data synchronizing system and method |
| CN103716370A (en) * | 2013-10-13 | 2014-04-09 | 北界创想（北京）软件有限公司 | Method and device for data synchronization between multiple clients |
| CN103793400A (en) * | 2012-10-30 | 2014-05-14 | 金蝶软件（中国）有限公司 | Method and device for batch adjustment of data tables |
| WO2014101889A1 (en) * | 2012-12-31 | 2014-07-03 | 华为技术有限公司 | Data synchronization method and device |
| CN103986773A (en) * | 2014-05-26 | 2014-08-13 | 北京奇艺世纪科技有限公司 | Data request response method and device |
| CN103997525A (en) * | 2014-05-21 | 2014-08-20 | 北京紫光天禾软件系统技术有限公司 | Distributed data synchronization method and system |
| CN104009979A (en) * | 2014-05-12 | 2014-08-27 | 刘喆 | Method for data transmission |
| CN104158897A (en) * | 2014-08-25 | 2014-11-19 | 曙光信息产业股份有限公司 | Updating method of file layout in distributed file system |
| CN104158870A (en) * | 2014-08-07 | 2014-11-19 | 刘喆 | Data transmission method and system |
| CN104270303A (en) * | 2014-09-29 | 2015-01-07 | 中国农业银行股份有限公司宿迁分行 | Automatic data information sending method and system |
| CN104462477A (en) * | 2014-12-18 | 2015-03-25 | 深圳市科漫达智能管理科技有限公司 | Data synchronizing method, device and system based on timestamp |
| CN104468707A (en) * | 2014-10-27 | 2015-03-25 | 刘喆 | Data transmitting method and system |
| CN104580425A (en) * | 2014-12-26 | 2015-04-29 | 北京中交兴路车联网科技有限公司 | Client data synchronization method and system |
| CN104580522A (en) * | 2015-01-30 | 2015-04-29 | 宁波凯智信息科技有限公司 | Client-server data synchronization method and system |
| CN104902021A (en) * | 2015-05-25 | 2015-09-09 | 北京嘀嘀无限科技发展有限公司 | Method and device for synchronizing information |
| CN104951454A (en) * | 2014-03-27 | 2015-09-30 | 河南省中科物联网有限公司 | File full life cycle tracking and controlling method |
| WO2015169055A1 (en) * | 2014-05-07 | 2015-11-12 | 中兴通讯股份有限公司 | Responding/requesting method and device for user subscription information |
| CN105635074A (en) * | 2014-11-06 | 2016-06-01 | 中兴通讯股份有限公司 | Method, server, client and system for realizing data synchronization |
| CN105653544A (en) * | 2014-11-12 | 2016-06-08 | 联想(北京)有限公司 | Information processing device and method |
| CN105718542A (en) * | 2016-01-18 | 2016-06-29 | 厦门雅迅网络股份有限公司 | Data cache and updating method and system |
| CN106230927A (en) * | 2016-07-29 | 2016-12-14 | 努比亚技术有限公司 | Contact person's synchronous method, Apparatus and system |
| CN103560906B (en) * | 2013-10-22 | 2017-01-25 | 珠海多玩信息技术有限公司 | Data replication method and device |
| CN106657170A (en) * | 2015-10-28 | 2017-05-10 | 阿里巴巴集团控股有限公司 | Data synchronization method and device |
| CN106708842A (en) * | 2015-11-12 | 2017-05-24 | 阿里巴巴集团控股有限公司 | Data loading method for application system, database and application system |
| CN106878362A (en) * | 2015-12-11 | 2017-06-20 | 展讯通信（上海）有限公司 | A kind of client, system and method for beta version more new system |
| WO2017114111A1 (en) * | 2015-12-31 | 2017-07-06 | 语联网（武汉）信息技术有限公司 | Asynchronous data synchronization method for distributed system |
| CN107682431A (en) * | 2017-09-28 | 2018-02-09 | 成都路行通信息技术有限公司 | A kind of more data synchronization between devices optimization methods and system |
| CN107704607A (en) * | 2017-10-17 | 2018-02-16 | 武汉楚鼎信息技术有限公司 | A kind of method of database in phase |
| CN107783824A (en) * | 2016-08-25 | 2018-03-09 | 北京京东尚科信息技术有限公司 | A kind of method and service terminal device for controlling intelligent home device |
| CN107819870A (en) * | 2017-11-21 | 2018-03-20 | 广州视睿电子科技有限公司 | Increment pulling data method, apparatus, storage medium, terminal device and server |
| CN107870571A (en) * | 2016-09-26 | 2018-04-03 | 北京京东尚科信息技术有限公司 | Control the method, apparatus and smart machine of smart machine |
| CN107911434A (en) * | 2017-11-10 | 2018-04-13 | 浪潮软件集团有限公司 | Tobacco data synchronization system and method |
| CN108073595A (en) * | 2016-11-10 | 2018-05-25 | 北京国双科技有限公司 | It is a kind of to realize data update and the method and device of snapshot in olap database |
| CN108259562A (en) * | 2017-12-11 | 2018-07-06 | 杭州品茗安控信息技术股份有限公司 | A kind of method of data synchronization and device based on multi-endpoint |
| CN108696443A (en) * | 2018-04-28 | 2018-10-23 | 北京五八信息技术有限公司 | A kind of method, apparatus, equipment and storage medium that terminal data synchronizes |
| CN109194711A (en) * | 2018-07-27 | 2019-01-11 | 腾讯科技（深圳）有限公司 | A kind of synchronous method of organizational structure, client, server-side and medium |
| CN109768910A (en) * | 2017-11-09 | 2019-05-17 | 腾讯科技（深圳）有限公司 | Information processing method, relevant apparatus, equipment and system |
| CN110557441A (en) * | 2016-03-01 | 2019-12-10 | 张君 | Data interaction method and system for client and server in online and offline states |
| CN110769061A (en) * | 2019-10-24 | 2020-02-07 | 华为技术有限公司 | Data synchronization method and equipment |
| CN111309747A (en) * | 2020-02-18 | 2020-06-19 | 京东数字科技控股有限公司 | Data synchronization method, system and device |
| CN112463882A (en) * | 2020-11-20 | 2021-03-09 | 广东省安心加科技有限公司 | Data synchronization method, cloud platform and edge terminal |
| CN113641764A (en) * | 2021-08-31 | 2021-11-12 | 江苏中科云墨数字科技有限公司 | Data synchronization implementation method based on digital twinning |
| CN113778480A (en) * | 2021-07-28 | 2021-12-10 | 赤子城网络技术（北京）有限公司 | Data updating method and device in weak networking environment, electronic equipment and storage medium |
| CN114760320A (en) * | 2020-12-29 | 2022-07-15 | 广州视源电子科技股份有限公司 | Data synchronization method and system for client and middlebox server and client |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102571935B (en) * | 2011-12-23 | 2015-11-25 | 华为技术有限公司 | A kind of method of transfer of data, client, server and system |
Family Cites Families (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP2001075785A (en) * | 1999-09-09 | 2001-03-23 | Nec Corp | Data updating system |
| US6694335B1 (en) * | 1999-10-04 | 2004-02-17 | Microsoft Corporation | Method, computer readable medium, and system for monitoring the state of a collection of resources |
| CN1259625C (en) * | 2001-08-24 | 2006-06-14 | 前程无忧网络信息技术（北京）有限公司 | Synchronous updating personnel resume database method based on internet |
| CN1249596C (en) * | 2002-09-03 | 2006-04-05 | 鸿富锦精密工业（深圳）有限公司 | Non Structured data synchronous system and method |
-
2006
- 2006-04-24 CN CN2006100760274A patent/CN101064630B/en active Active
Cited By (90)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101794297B (en) * | 2010-01-15 | 2012-07-25 | 北京中创信测科技股份有限公司 | Method and system for processing information data |
| CN102130929A (en) * | 2010-01-20 | 2011-07-20 | 金蝶软件（中国）有限公司 | Method and device for updating client testing server and testing server |
| CN101902613A (en) * | 2010-07-21 | 2010-12-01 | 中兴通讯股份有限公司 | Information synchronization method and system, set top box and server in IPTV (Internet Protocol Television) system |
| CN101902613B (en) * | 2010-07-21 | 2014-06-04 | 中兴通讯股份有限公司 | Information synchronization method and system, set top box and server in IPTV (Internet Protocol Television) system |
| CN102591901B (en) * | 2010-11-23 | 2017-09-01 | 三星电子株式会社 | Apparatus and method for the data in the equipment of synchronized links |
| CN102591901A (en) * | 2010-11-23 | 2012-07-18 | 三星电子株式会社 | Apparatus and method for synchronizing data in connected devices |
| CN102546208A (en) * | 2010-12-13 | 2012-07-04 | 北大方正集团有限公司 | Device management method, system and device management server |
| CN102063494A (en) * | 2010-12-31 | 2011-05-18 | 青岛海信网络科技股份有限公司 | Database synchronizing method and device |
| CN103392330B (en) * | 2011-03-10 | 2017-09-26 | 阿玛得斯两合公司 | For the system and method with independent external system session synchronization |
| CN103392330A (en) * | 2011-03-10 | 2013-11-13 | 阿玛得斯两合公司 | System and method for session synchronization with independent external systems |
| CN102231881B (en) * | 2011-07-05 | 2015-07-15 | 广州市动景计算机科技有限公司 | Method, server and system for processing user data of mobile terminal |
| CN102231881A (en) * | 2011-07-05 | 2011-11-02 | 广州市动景计算机科技有限公司 | Method, server and system for processing user data of mobile terminal |
| CN102325367A (en) * | 2011-09-29 | 2012-01-18 | 用友软件股份有限公司 | Data packet synchronizing device and method for client application |
| CN102325367B (en) * | 2011-09-29 | 2013-09-11 | 用友软件股份有限公司 | Data packet synchronizing device and method for client application |
| CN103136200A (en) * | 2011-11-22 | 2013-06-05 | 中兴通讯股份有限公司 | Data updating information obtaining method and device and data synchronization method and device |
| CN103136200B (en) * | 2011-11-22 | 2018-02-02 | 中兴通讯股份有限公司 | Data fresh information acquisition methods, device and method of data synchronization, device |
| CN102571923A (en) * | 2011-12-13 | 2012-07-11 | 中国电子科技集团公司第十五研究所 | Data synchronization system and method |
| CN103457905A (en) * | 2012-05-28 | 2013-12-18 | 腾讯科技（深圳）有限公司 | Data synchronizing method, data synchronizing system and data synchronizing device |
| WO2013177925A1 (en) * | 2012-05-28 | 2013-12-05 | 腾讯科技（深圳）有限公司 | Data synchronization method, system and device |
| US20150081633A1 (en) * | 2012-05-28 | 2015-03-19 | Tencent Technology (Shenzhen) Company Limited | Data synchronization method and device |
| CN103457905B (en) * | 2012-05-28 | 2015-09-09 | 腾讯科技（深圳）有限公司 | Method of data synchronization, system and equipment |
| CN103532920A (en) * | 2012-07-06 | 2014-01-22 | 腾讯科技（深圳）有限公司 | Cookie update method and cookie update system |
| CN103532920B (en) * | 2012-07-06 | 2018-01-23 | 腾讯科技（深圳）有限公司 | Cookie update methods and cookie more new systems |
| CN103685191A (en) * | 2012-09-18 | 2014-03-26 | 英业达科技有限公司 | Data synchronizing system and method |
| CN103685191B (en) * | 2012-09-18 | 2017-02-01 | 英业达科技有限公司 | Data synchronizing system and method |
| CN102904887A (en) * | 2012-09-26 | 2013-01-30 | 东软集团股份有限公司 | Method and system for data synchronization of Web client and server |
| CN103793400A (en) * | 2012-10-30 | 2014-05-14 | 金蝶软件（中国）有限公司 | Method and device for batch adjustment of data tables |
| WO2014101889A1 (en) * | 2012-12-31 | 2014-07-03 | 华为技术有限公司 | Data synchronization method and device |
| CN103152390A (en) * | 2013-02-04 | 2013-06-12 | 华为技术有限公司 | Method and device and nodes and system for node configuration of distributed storage system |
| CN103152390B (en) * | 2013-02-04 | 2016-03-30 | 华为技术有限公司 | The node configuration method of distributed memory system, device, node and system |
| CN103716370A (en) * | 2013-10-13 | 2014-04-09 | 北界创想（北京）软件有限公司 | Method and device for data synchronization between multiple clients |
| CN103595707A (en) * | 2013-10-17 | 2014-02-19 | 广东电网公司茂名供电局 | Automatic file network synchronization method based on SVN |
| CN103560906B (en) * | 2013-10-22 | 2017-01-25 | 珠海多玩信息技术有限公司 | Data replication method and device |
| CN104951454A (en) * | 2014-03-27 | 2015-09-30 | 河南省中科物联网有限公司 | File full life cycle tracking and controlling method |
| WO2015169055A1 (en) * | 2014-05-07 | 2015-11-12 | 中兴通讯股份有限公司 | Responding/requesting method and device for user subscription information |
| CN105101197A (en) * | 2014-05-07 | 2015-11-25 | 中兴通讯股份有限公司 | User contract-signing information response and request method and device |
| CN104009979A (en) * | 2014-05-12 | 2014-08-27 | 刘喆 | Method for data transmission |
| CN103997525B (en) * | 2014-05-21 | 2017-10-20 | 北京天禾元创软件股份有限公司 | A kind of Distributed Data Synchronization method and system |
| CN103997525A (en) * | 2014-05-21 | 2014-08-20 | 北京紫光天禾软件系统技术有限公司 | Distributed data synchronization method and system |
| CN103986773A (en) * | 2014-05-26 | 2014-08-13 | 北京奇艺世纪科技有限公司 | Data request response method and device |
| CN104158870A (en) * | 2014-08-07 | 2014-11-19 | 刘喆 | Data transmission method and system |
| CN104158897A (en) * | 2014-08-25 | 2014-11-19 | 曙光信息产业股份有限公司 | Updating method of file layout in distributed file system |
| CN104158897B (en) * | 2014-08-25 | 2017-06-23 | 曙光信息产业股份有限公司 | The update method of file layout in a kind of distributed file system |
| CN104270303A (en) * | 2014-09-29 | 2015-01-07 | 中国农业银行股份有限公司宿迁分行 | Automatic data information sending method and system |
| CN104468707A (en) * | 2014-10-27 | 2015-03-25 | 刘喆 | Data transmitting method and system |
| CN105635074A (en) * | 2014-11-06 | 2016-06-01 | 中兴通讯股份有限公司 | Method, server, client and system for realizing data synchronization |
| CN105653544A (en) * | 2014-11-12 | 2016-06-08 | 联想(北京)有限公司 | Information processing device and method |
| CN105653544B (en) * | 2014-11-12 | 2019-06-25 | 联想(北京)有限公司 | A kind of information processing unit and method |
| CN104462477B (en) * | 2014-12-18 | 2018-03-30 | 深圳市科漫达智能管理科技有限公司 | The method, apparatus and system of data syn-chronization based on timestamp |
| CN104462477A (en) * | 2014-12-18 | 2015-03-25 | 深圳市科漫达智能管理科技有限公司 | Data synchronizing method, device and system based on timestamp |
| CN104580425A (en) * | 2014-12-26 | 2015-04-29 | 北京中交兴路车联网科技有限公司 | Client data synchronization method and system |
| CN104580522A (en) * | 2015-01-30 | 2015-04-29 | 宁波凯智信息科技有限公司 | Client-server data synchronization method and system |
| CN104902021A (en) * | 2015-05-25 | 2015-09-09 | 北京嘀嘀无限科技发展有限公司 | Method and device for synchronizing information |
| CN104902021B (en) * | 2015-05-25 | 2018-07-20 | 北京嘀嘀无限科技发展有限公司 | The method and device of synchronizing information |
| CN106657170A (en) * | 2015-10-28 | 2017-05-10 | 阿里巴巴集团控股有限公司 | Data synchronization method and device |
| CN106657170B (en) * | 2015-10-28 | 2021-03-30 | 斑马智行网络(香港)有限公司 | Data synchronization method and device |
| CN106708842A (en) * | 2015-11-12 | 2017-05-24 | 阿里巴巴集团控股有限公司 | Data loading method for application system, database and application system |
| CN106708842B (en) * | 2015-11-12 | 2021-02-09 | 创新先进技术有限公司 | Method for loading data by application system, database and application system |
| CN106878362A (en) * | 2015-12-11 | 2017-06-20 | 展讯通信（上海）有限公司 | A kind of client, system and method for beta version more new system |
| WO2017114111A1 (en) * | 2015-12-31 | 2017-07-06 | 语联网（武汉）信息技术有限公司 | Asynchronous data synchronization method for distributed system |
| CN105718542A (en) * | 2016-01-18 | 2016-06-29 | 厦门雅迅网络股份有限公司 | Data cache and updating method and system |
| CN110557441A (en) * | 2016-03-01 | 2019-12-10 | 张君 | Data interaction method and system for client and server in online and offline states |
| CN110557441B (en) * | 2016-03-01 | 2022-02-22 | 张君 | Data interaction method and system for client and server in online and offline states |
| CN110572437A (en) * | 2016-03-01 | 2019-12-13 | 张君 | Data interaction method and system for client and server in online and offline states |
| CN106230927A (en) * | 2016-07-29 | 2016-12-14 | 努比亚技术有限公司 | Contact person's synchronous method, Apparatus and system |
| CN107783824B (en) * | 2016-08-25 | 2020-07-31 | 北京京东尚科信息技术有限公司 | Method for controlling intelligent household equipment and server device |
| CN107783824A (en) * | 2016-08-25 | 2018-03-09 | 北京京东尚科信息技术有限公司 | A kind of method and service terminal device for controlling intelligent home device |
| CN107870571A (en) * | 2016-09-26 | 2018-04-03 | 北京京东尚科信息技术有限公司 | Control the method, apparatus and smart machine of smart machine |
| CN108073595A (en) * | 2016-11-10 | 2018-05-25 | 北京国双科技有限公司 | It is a kind of to realize data update and the method and device of snapshot in olap database |
| CN108073595B (en) * | 2016-11-10 | 2020-09-18 | 北京国双科技有限公司 | Method and device for realizing data updating and snapshot in OLAP database |
| CN107682431A (en) * | 2017-09-28 | 2018-02-09 | 成都路行通信息技术有限公司 | A kind of more data synchronization between devices optimization methods and system |
| CN107704607A (en) * | 2017-10-17 | 2018-02-16 | 武汉楚鼎信息技术有限公司 | A kind of method of database in phase |
| CN109768910A (en) * | 2017-11-09 | 2019-05-17 | 腾讯科技（深圳）有限公司 | Information processing method, relevant apparatus, equipment and system |
| CN109768910B (en) * | 2017-11-09 | 2021-06-25 | 腾讯科技（深圳）有限公司 | Information processing method, related device, equipment and system |
| CN107911434A (en) * | 2017-11-10 | 2018-04-13 | 浪潮软件集团有限公司 | Tobacco data synchronization system and method |
| CN107819870A (en) * | 2017-11-21 | 2018-03-20 | 广州视睿电子科技有限公司 | Increment pulling data method, apparatus, storage medium, terminal device and server |
| CN108259562A (en) * | 2017-12-11 | 2018-07-06 | 杭州品茗安控信息技术股份有限公司 | A kind of method of data synchronization and device based on multi-endpoint |
| CN108259562B (en) * | 2017-12-11 | 2022-02-25 | 杭州品茗安控信息技术股份有限公司 | Data synchronization method and device based on multiple endpoints |
| CN108696443A (en) * | 2018-04-28 | 2018-10-23 | 北京五八信息技术有限公司 | A kind of method, apparatus, equipment and storage medium that terminal data synchronizes |
| CN109194711A (en) * | 2018-07-27 | 2019-01-11 | 腾讯科技（深圳）有限公司 | A kind of synchronous method of organizational structure, client, server-side and medium |
| CN109194711B (en) * | 2018-07-27 | 2020-12-15 | 腾讯科技（深圳）有限公司 | Synchronization method, client, server and medium for organization architecture |
| CN110769061A (en) * | 2019-10-24 | 2020-02-07 | 华为技术有限公司 | Data synchronization method and equipment |
| CN111309747A (en) * | 2020-02-18 | 2020-06-19 | 京东数字科技控股有限公司 | Data synchronization method, system and device |
| CN112463882A (en) * | 2020-11-20 | 2021-03-09 | 广东省安心加科技有限公司 | Data synchronization method, cloud platform and edge terminal |
| CN114760320A (en) * | 2020-12-29 | 2022-07-15 | 广州视源电子科技股份有限公司 | Data synchronization method and system for client and middlebox server and client |
| CN114760320B (en) * | 2020-12-29 | 2023-09-12 | 广州视源电子科技股份有限公司 | Data synchronization method and system for client and middle server and client |
| CN113778480A (en) * | 2021-07-28 | 2021-12-10 | 赤子城网络技术（北京）有限公司 | Data updating method and device in weak networking environment, electronic equipment and storage medium |
| CN113778480B (en) * | 2021-07-28 | 2024-01-30 | 赤子城网络技术（北京）有限公司 | Data updating method and device in weak networking environment, electronic equipment and storage medium |
| CN113641764A (en) * | 2021-08-31 | 2021-11-12 | 江苏中科云墨数字科技有限公司 | Data synchronization implementation method based on digital twinning |
| CN113641764B (en) * | 2021-08-31 | 2024-03-19 | 江苏中科云墨数字科技有限公司 | Data synchronization realization method based on digital twin |
Also Published As
| Publication number | Publication date |
|---|---|
| CN101064630B (en) | 2011-09-21 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN101064630A (en) | Data synchronization method and system | |
| CN1852309A (en) | Data synchronizing processing method and its client end | |
| CN1852137A (en) | Method for realizing synchronization of client end data and server end data | |
| CN1146821C (en) | Data bank query method and system to users | |
| CN1874233A (en) | System and method for sending message of broadcast | |
| CN1852538A (en) | Method and apparatus for monitoring and updating software in apparatus management | |
| CN101068156A (en) | Conflict processing method and conflict processing server when data synchronization | |
| CN101079721A (en) | A method and system for broadcasting buffered advertisement in polling mode under the network living broadcast environment | |
| CN1492656A (en) | Method, device and system for sharing applied program conversation information on multichannels | |
| CN1763713A (en) | Mobile terminal software edition updating method | |
| CN1878301A (en) | Video monitoring data storage managing method and system | |
| CN101059799A (en) | Method for introducing regular file into data base | |
| CN1808426A (en) | Universal file search system and method | |
| CN1472963A (en) | Distributive video interactive system and its data recording and accessing method | |
| CN101076032A (en) | Method and system for transmitting information | |
| CN1731878A (en) | Method for carrying out protection on user information in mobile terminal | |
| CN1947442A (en) | Method for providing information of telephone number owner using wire/wireless communication terminal and system for implementing the same | |
| CN101056275A (en) | A setting method for group message receiving mode in the instant communication system | |
| CN1852261A (en) | Method for maintenance of neighbor entry | |
| CN101075990A (en) | Method for issuing instant telecommunication software and instant telecommunication server | |
| CN1886976A (en) | Method, software and apparatus for performing actions on a wireless device using action lists and versioning | |
| CN1866854A (en) | Method for updating and recovering terminal device data in device management | |
| CN1825321A (en) | Searching method, holding method and searching system for dictionary-like data | |
| CN101079722A (en) | A reporting method, system and device of network living broadcast advertisement | |
| CN1798032A (en) | Method and system for implementing message subscription through Internet |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant |