CN103716370A - Method and device for data synchronization between multiple clients - Google Patents

Method and device for data synchronization between multiple clients Download PDF

Info

Publication number
CN103716370A
CN103716370A CN201310476939.0A CN201310476939A CN103716370A CN 103716370 A CN103716370 A CN 103716370A CN 201310476939 A CN201310476939 A CN 201310476939A CN 103716370 A CN103716370 A CN 103716370A
Authority
CN
China
Prior art keywords
client
change
data
server
collection
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
Application number
CN201310476939.0A
Other languages
Chinese (zh)
Other versions
CN103716370B (en
Inventor
薛鹏飞
郑伟
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Northern Boundary Of Imagination (beijing) Software Co Ltd
Original Assignee
Northern Boundary Of Imagination (beijing) Software Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Northern Boundary Of Imagination (beijing) Software Co Ltd filed Critical Northern Boundary Of Imagination (beijing) Software Co Ltd
Priority to CN201310476939.0A priority Critical patent/CN103716370B/en
Publication of CN103716370A publication Critical patent/CN103716370A/en
Application granted granted Critical
Publication of CN103716370B publication Critical patent/CN103716370B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Landscapes

  • Information Transfer Between Computers (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

The invention provides a method and device for data synchronization between multiple clients, and relates to the field of internet. The method comprises the steps that a server receives change sets generated by clients; the clients comprises data composed of a number of elements; the clients generate the change sets which respectively comprise a data change record after each time of data change; the clients comprise a first client and a second client, and the change sets comprise a first change set generated by the first client and a second change set generated by the second client; and when the first change set and the second change set comprise the change of different elements in the data, the server carries out data synchronization on the first client and the second client according to the first change set and the second change set. According to the embodiment of the invention, accurate data synchronization between the clients can be realized.

Description

Between a plurality of clients, carry out the synchronous method and apparatus of data
Technical field
The present invention relates to internet arena, particularly a kind of synchronous method of data of carrying out between a plurality of clients.
Background technology
The simultaneous techniques of network account can make user when the client by different logs in same network account, gets identical data.
Between different clients, carry out data when synchronous, need to transmit or Delete superfluous file by enterprising style of writing part in different clients, finally make the data in a plurality of clients be consistent, when the content in a plurality of clients all changes, easily there is timing error, for example, have two clients all to add same new application, so the data in these two clients are synchronized to after the 3rd client, in the 3rd client, may occur two these identical application; Or a plurality of clients are carried out respectively different operating, carry out when synchronous, cannot obtaining according to different operations unified synchronized result.
For a plurality of clients in prior art, cannot obtain the problem of unified synchronized result, the solution not had at present.
Summary of the invention
The embodiment of the present invention provides a kind of synchronous method and apparatus of data that carries out between a plurality of clients, and to realize, between each client, data are synchronous accurately.
The present invention to achieve these goals, a kind of synchronous method of data of carrying out between a plurality of clients is provided, comprise: server receives the change collection that client generates, wherein, client comprises the data that consist of a plurality of elements, client generates the change collection that comprises this secondary data change record after each data change, and client comprises the first client and the second client, and change collection comprises that the first change collection of the first client generation and the second change that the second client generates collect; In the first change collection and the second change collection comprise data during the more change of different elements, it is synchronous that server carries out data according to the first change collection and second change set pair the first client and the second client.
In one embodiment, said method also comprises: server is determined the order that generates the first change collection and the second change collection; When the first change collection and the second change concentrate comprise data in during difference more the becoming of identity element, server according to order after change set pair the first client and the second client to carry out data synchronous.
In one embodiment, on server for data after changing arrange version number.
In one embodiment, after each data change, version number once increases progressively.
In one embodiment, server is the client backup image file that carries out data change, and image file is the copy of client current data.
The present invention to achieve these goals, a kind of synchronous device of data that carries out between a plurality of clients is also provided, receiver module, the change collection generating for receiving client, wherein, client comprises the data that consist of a plurality of elements, and client generates the change collection that comprises this secondary data change record after each data change, client comprises the first client and the second client, and change collection comprises the second change collection that the first change collects and the second client generates that the first client generates; The first synchronization module, when comprising the more change to the different elements of data when the first change collection and the second change collection, according to the first change collection and second, changing set pair the first client and the second client, to carry out data synchronous.
In one embodiment, said apparatus also comprises: processing module, for determining the order that generates the first change collection and the second change collection; The second synchronization module, while comprising difference more the becoming of data identity element for concentrating when the first change collection and the second change, according to sequentially after change set pair the first client and the second client to carry out data synchronous.
In one embodiment, said apparatus also comprises: module is set, is used to data after changing that version number is set.
In one embodiment, after each data change, version number once increases progressively.
In one embodiment, said apparatus also comprises: backup module, be used to the client backup image file that carries out data change, and image file is the copy of client current data.
It is synchronous that the present invention carries out data by all clients of change set pair of each client, realizes that data are synchronous accurately.
Accompanying drawing explanation
Accompanying drawing described herein is used to provide a further understanding of the present invention, forms the application's a part, does not form limitation of the invention.In the accompanying drawings:
Fig. 1 is the flow chart that carries out the synchronous method of data 100 between a plurality of clients that the invention process exemplifies;
Fig. 2 A is the flow chart that carries out the synchronous method of data 200 between different clients shown in first preferred embodiment of the invention;
Fig. 2 B is the first schematic diagram shown in first preferred embodiment of the invention;
Fig. 2 C is the second schematic diagram shown in first preferred embodiment of the invention;
Fig. 2 D is the 3rd schematic diagram shown in first preferred embodiment of the invention;
Fig. 2 E is the 4th schematic diagram shown in first preferred embodiment of the invention;
Fig. 2 F is the 5th schematic diagram shown in first preferred embodiment of the invention;
Fig. 3 A is a kind of flow chart that data in a plurality of clients is carried out to synchronous method shown in second preferred embodiment of the invention;
Fig. 3 B is the first schematic diagram shown in second preferred embodiment of the invention;
Fig. 3 C is the second schematic diagram shown in second preferred embodiment of the invention;
Fig. 3 D is the 3rd schematic diagram shown in second preferred embodiment of the invention;
Fig. 3 E is that the another kind shown in second preferred embodiment of the invention carries out the flow chart of synchronous method to the data in a plurality of clients;
Fig. 3 F is the 4th schematic diagram shown in second preferred embodiment of the invention;
Fig. 3 G is the 5th schematic diagram shown in second preferred embodiment of the invention;
Fig. 3 H is the 6th schematic diagram shown in second preferred embodiment of the invention;
Fig. 4 is the structured flowchart that carries out the synchronous device of data 400 between a plurality of clients that the invention process exemplifies;
Fig. 5 is the structured flowchart that carries out the synchronous device of data 500 between a plurality of clients shown in first preferred embodiment of the invention; And
Fig. 6 is the structured flowchart that carries out the synchronous device of data 600 between a plurality of clients shown in second preferred embodiment of the invention.
Embodiment
For making the object, technical solutions and advantages of the present invention clearer, below in conjunction with accompanying drawing, the embodiment of the present invention is described in further detail.At this, schematic description and description of the present invention is used for explaining the present invention, but not as a limitation of the invention.
Referring now to accompanying drawing, the present invention is described in further detail.The present invention can realize in many different forms, should not be understood to only limit to the embodiment that set forth in this place.These embodiment only provide as example, to understand completely of the present invention for those skilled in the art provide.
The embodiment of the present invention provides a kind of synchronous method of data of carrying out between a plurality of clients, and Fig. 1 is the flow chart that carries out the synchronous method of data 100 between a plurality of clients that the invention process exemplifies.
What first the present embodiment take two clients is synchronously example, and the synchronous method between a plurality of clients is described, if any two clients can obtain unified synchronized result, all clients can obtain unified synchronized result.
The executive agent of the method can be a station server, and as shown in Figure 1, the method comprises the following steps:
Step 110, server receives the change collection that client generates.
Client comprises the data that consist of a plurality of elements, each element can be application, file or a link etc., by adding element, delete element or adjust the modes such as position of element, can carry out data change, client generates the change collection that comprises this secondary data change record after each data change.
Client comprises the first client and the second client, and change collection comprises the second change collection that the first change collects and the second client generates that the first client generates." first " in the present embodiment and " second " are not the restrictions to quantity, but as the differentiation between a plurality of clients, the first client can be client 11, the second client can be client 12, below when a data change, the example of one the first change collection being generated by client 11, client 11 is empty set in the data of initial condition, data are after changing (a, b, c, d), now, a, b, c, d are respectively the element in data, and the first change collection of generation is as follows:
Figure BDA0000394992230000051
From this change collection, can find out, client 11 has been added element a, and the previous above of element a is None, and element a's does not have other data above, the attribute properties of element a can arrange according to demand, is other attributes other properties in the present embodiment.In the present embodiment, for element a, b, c, d are provided with attribute, but persons skilled in the art should be understood that, data have the multiple mode that is divided into element, so element may not set a property yet.
Client 11 has also been added element b, element c and element d, the previous of element b is element a, the previous of element c is element b, the previous of element d is element c, be that data after client 11 more becomes are (a, b, c, d), by change, collect the data that can draw after changing, in like manner, the data by after changing also can show that the change of this secondary data change collects.
In specific embodiment, on server, can also version number be set for data after changing, version number can realize by calling counter, data on server often once change when synchronous, version number once increases progressively automatically, and for example initial condition version number is 0, and the data on server are at every turn after changing, version number adds 1, and the client that this time synchronizeed with server is set to have identical version number with server after synchronous.
Preferably, server can be for carrying out the image file of a version of client backup of data change after each data change, client by with server on image file contrast, can generate more easily change collection.For example: the version of client 11 is the data trnascription by presetting form poke corresponding to the image file on server.
Step 120, in the first change collection and the second change collection comprise for data during the more change of different elements, it is synchronous that server carries out data according to the first change collection and second change set pair the first client and the second client.
For example, the first change collection deletes the element a in (a, b, c, d), and the second change collection deletes the element d in (a, b, c, d), due to for element different, the first change collection and the second change collect and comprise the change to different elements; If the first change collection changes to element e by the element a in (a, b, c, d), the second change collection changes to element f by the element a in (a, b, c, d), owing to all element a being changed, the first change collection and the second change collection comprise the different change to identity element.
If two clients have produced change collection, when carrying out synchronous between client, first the change collection of first client is synchronized on server, server obtains data (X) after changing, then the change collection of second client is synchronized on server, server obtains data (X+Y) after changing, and last server is synchronized to each client by data after changing (X+Y).The concrete method of synchronization refers to hereinafter to be described.
Step 130, server is determined the order that generates the first change collection and the second change collection, in the first change collection and the second change collection comprise data during difference more the becoming of identity element, according to order after change set pair the first client and the second client to carry out data synchronous.
Under some particular case, two clients may be carried out different more changes to identity element, for example the element a in 11 pairs of data of client changes, data (a, b) are changed to (c, b), and client 12 also changes the element a in data, when data (a, b) are changed to (d, b), now need first to determine that two clients generate the order of change collection, according to order after change collection carry out synchronously.
The order of determining change collection can be according to acquisition time or the rise time of each change collection, for example client 11 is understood t1 writing time when generating change collection, client 12 is meeting t2 writing time when generating change collection, after judging the sequencing of t1 and t2, according to setting in advance, in order after change collection carry out synchronously.For example t1 is 2013/1/1/0:1, and t2 is 2013/1/1/0:31, and t1 is 0: 1 morning of on January 1st, 2013, and t2 is 0: 31 morning of on January 1st, 2013, because the order of t2 is after t1, according to change collection corresponding to t2, carries out synchronously.
In one case, in time two between subsynchronous, a client has too much secondary data change to data, according to the situation of data change repeatedly, generate a change collection, the time of change collection be the last time that generates after changing change collection, and for example client 11 comprises respectively at t11 and t12(t12>t11) two times have added a and b, and first of this client 11 the change collects and is:
Figure BDA0000394992230000071
The time that generation change integrates is as t12.
Equally, client 12 comprises respectively at t21 and t22(t22>t21) two times have added c and d, and second of this client 12 the change collection is:
Figure BDA0000394992230000072
The time that generation change integrates is as t21.
Specifically data schematically as follows synchronously: under initial condition, the version number of server, client 11 and client 12 is 0, client 11 and client 12 produce respectively change collection, server first with client 11(or with the image file of client 11) synchronize, after this subsynchronous end, server and client side 11 version number is upgraded to 1, and the version number of client 12 is still 0; Then server is that client 12 carries out synchronously, after this subsynchronous end, server and client side 12 version number is upgraded to 2, the version number of client 11 is still 1, finally by the content synchronization on server to client 11, because this sync client 12 does not generate new change collection, it is the not variation of data on server, so the version number of server can not add 1, now the version number of client 12 is also upgraded to 2, to be consistent with service end.
Version number can guarantee the change accurately of each version, for example, from initial condition, the hyposynchronous change of server first integrates as x, the second hyposynchronous change integrates as y, if a certain client is not carried out synchronously according to primary change collection x, and only according to secondary change collection y, carry out synchronously, the data in this client are inaccurate.By being set, version number can address this problem, for example server is 1 carrying out synchronous rear version number for the first time, carry out for the second time synchronous after version number be upgraded to 2, the version number that has carried out first hyposynchronous each client is 1, by the version number of synchronous client, be not still 0, lower, when subsynchronous, according to the version number of this client, can determine this client data disappearance so.In this case, can replace the data in this client by server current data, to guarantee the consistent of each client data.
Fig. 2 A is the flow chart that carries out the synchronous method of data 200 between different clients shown in first preferred embodiment of the invention.
The present embodiment has been described operating procedure when client is synchronizeed with server for the first time.If client is to synchronize with server for the first time, the data of directly obtaining when synchronous from server add to legacy data in client after.The present embodiment is with three clients: client 21, client 22 and client 23, and server 24 is example, to carrying out the synchronous method of data between server 24 and different clients, be described, as shown in Figure 2 A, the method comprising the steps of 210 to step 250.
Step 210, client 21 is synchronizeed with server 24.
Under initial condition, on client 21, client 22, client 23 and server 24, all there is no data, as shown in Figure 2 B, in client 21, comprise after changing data (a, b, c), in client 22, comprise data (d, e, f), in client 23, comprise data (g, h, i), be that the change collection that client 21 produces is increase element a, element b, element c, the change collection that client 22 produces is for increasing element d, element e, element f, and the change collection that client 23 produces is for increasing element g, element h, element i.Before the data of these changes being carried out synchronously, the version number of client 21, client 22, client 23 and server 24 is 0, after data in client 21 (or client 21 image file on server 24) are synchronized on server 24, on server 24, comprise data (a, b, c), now the version number of server 24 and client 21 is upgraded to 1, and client 22 and client 23 version numbers are still 0.
Step 220, client 22 is synchronizeed with server 24.
As shown in Figure 2 C, in client 21, comprise data (a, b, c), in client 22, comprise data (d, e, f), in client 23, comprise data (g, h, i).Before synchronous, on server 24, comprise data (a, b, c), and the version number of server 24 is 1.After geodata and services device in client 22 24 is carried out synchronously, be that server 24 increases element d, element e, element f on legacy data, and the data after increasing are synchronized to client 22, in server 24 and client 22, comprise data (a, b, c, d, e, f), now, because client 21 has only participated in synchronous for the first time, and that client 22 and server 24 have participated in is synchronous for the second time, so the version number of client 21 is still 1, the version number of server 24 and client 22 is upgraded to 2, and the version number of client 23 is still 0.
Step 230, client 23 is synchronizeed with server 24.
As shown in Figure 2 D, in client 21, comprise data (a, b, c), in client 22, comprise data (a, b, c, d, e, f), in client 23, comprise data (g, h, i).Before synchronous, on server 24, comprise data (a, b, c, d, e, f), now the version number of server 24 is 2, after geodata and services device in client 23 24 is synchronous, in server 24 and client 23, comprise data (a, b, c, d, e, f, g, h, i), now the version number of client 21 is still 1, and the version number of client 22 is 2, and the version number of server 24 and client 23 is upgraded to 3.
Step 240, server 24 is synchronizeed with client 22.
As shown in Figure 2 E, in client 21, comprise data (a, b, c), in client 22, comprise data (a, b, c, d, e, f), in client 23, comprise data (a, b, c, d, e, f, g, h, i).Before once synchronous on carrying out, on server 24, comprise data (a, b, c, d, e, f, g, h, i), data on server 24 are synchronized in client 22, in client 22, data also comprise (a, b, c, d, e, f, g, h, i), now, the version number of server 24, client 22 and client 23 is 3, and the version number of client 21 is still 1.
Step 250, server 24 is synchronizeed with client 21.
As shown in Figure 2 F, in client 21, comprise data (a, b, c), on client 22, client 23 and server 24, include data (a, b, c, d, e, f, g, h, i).After data on server 24 are synchronized in client 21, in client 21, also comprise data (a, b, c, d, e, f, g, h, i), now, the data on client 21, client 22, client 23 and server 24 are identical, and version number is 3.
So far, the data of these a plurality of clients are synchronous just all completes.
In a upper embodiment, the change of each client is all for different data, in another embodiment, successively same data are carried out to different changes and can cause diverse synchronous effect, the present embodiment will change data by two kinds of different orders, and carry out synchronous, take client 31, client 32 and server 33 is below example, be elaborated, Fig. 3 A is a kind of flow chart that data in a plurality of clients is carried out to synchronous method shown in second preferred embodiment of the invention.
As shown in Figure 3A, the method comprising the steps of 310A is to step 330A.
Step 310A, client 31 is synchronizeed with server 33.
Under initial condition, the data on client 31, client 32 and server 33 are (a, b), and version number is 0, synchronous before, client 31 first changes to element c by element b, the data change of client 31 is (a, c); Client 32 changes to element d by element b again, and add element e, the content alteration that is client 32 is (a, d, e), after client 31 is synchronizeed with server 33, as shown in Figure 3 B, data in server 33 and client 31 are all (a, c), and the version number of server 33 and client 31 rises to 1, and the version number of client 32 is still 0.
Step 320A, client 32 is synchronizeed with server 33.
As shown in Figure 3 C, in client 31, comprise data (a, c), in client 32, comprise data (a, d, e), client 32 is synchronizeed with server 33, same data on 32 pairs of servers 33 of client 31 and client have been carried out different changes, client 31 changes to element c by element b, client 32 changes to element d by element b, according to setting in advance, what different clients changed the change of same data later is as the criterion, therefore now to the change of element b, the change with client 32 is as the criterion, after server 33 is synchronizeed with client 32, in server 33 and client 32, comprise data (a, d, e), now the version number of server 33 and client 32 is upgraded to 2, the version number of client 31 is still 1.
Step 330A, server 33 is synchronizeed with client 31.
As shown in Figure 3 D, before this is subsynchronous, comprise data (a, c) in client 31, comprise data (a, d, e) on server 33, after server 33 is synchronizeed with client 31, the data change of client 31 is (a, d, e), and the version number of client 31 is upgraded to 2.
Fig. 3 E is that the another kind shown in second preferred embodiment of the invention carries out the flow chart of synchronous method to the data in a plurality of clients.As shown in Fig. 3 E, comprise the steps:
Step 310E, client 31 is synchronizeed with server 33.
Under initial condition, the data on client 31, client 32 and server 33 are (a, b), and version number is 0, synchronous before, client 32 first changes to element d by element b, and adds element e; Client 31 changes to element c by element b again, after client 31 is synchronizeed with server 33, as shown in Fig. 3 F, the data that comprise in server 33 and client 31 are all (a, c), the version number of server 33 and client 31 rises to 1, and the data of client 32 are constant, and version number is still 0.
Step 320E, client 32 is synchronizeed with server 33.
As shown in Fig. 3 G, in client 31, comprise data (a, c), in client 32, comprise data (a, d, e), client 32 is synchronizeed with server 33, same data on 32 pairs of servers 33 of client 31 and client have been carried out different changes, client 31 changes to element c by element b, client 32 changes to element d by element b, due to being as the criterion that different clients changes the change of same data later, therefore to the change of element b, the change with client 31 is as the criterion, after server 33 is synchronizeed with client 32, in server 33 and client 32, comprise data (a, c, e), now the version number of server 33 and client 32 is upgraded to 2, the version number of client 31 is still 1.
Step 330E, server 33 is synchronizeed with client 31.
As shown in Fig. 3 H, synchronous before, in client 31, comprise data (a, c), on server 33, comprise data (a, c, e), after server 33 is synchronizeed with client 31, client 31 also comprises the data identical with server (a, c, e), and now the version number of client 31 is upgraded to 2.
Embodiment according to shown in Fig. 3 A and Fig. 3 E, can find out, the different order collecting by change can cause diverse synchronous effect.
The embodiment of the present invention also provides a kind of synchronous device of data that carries out between a plurality of clients.This device can be arranged in server, to realize, carries out the synchronous method of data between a plurality of clients.
Fig. 4 is the structured flowchart that carries out the synchronous device of data 400 between a plurality of clients that the invention process exemplifies, and as shown in Figure 4, this device 400 comprises receiver module 402 and the first synchronization module 404.
The change collection that receiver module 402 generates for receiving client, wherein, client comprises the data that consist of a plurality of elements, client generates the change collection that comprises this secondary data change record after each data change, client comprises the first client and the second client, and change collection comprises the second change collection that the first change collects and the second client generates that the first client generates;
The first synchronization module 404 is when comprising the more change to the different elements of data when the first change collection and the second change collection, according to the first change collection and second, changing set pair the first client and the second client, to carry out data synchronous.
Fig. 5 is the structured flowchart that carries out the synchronous device of data 500 between a plurality of clients shown in first preferred embodiment of the invention, and as shown in Figure 5, this device 500 also comprises processing module 502 and the second synchronization module 504 on the basis of device 400.
Processing module 502 is for determining the order that generates the first change collection and the second change collection.
When the second synchronization module 504 comprises difference more the becoming of data identity element for concentrating when the first change collection and the second change, according to sequentially after change set pair the first client and the second client to carry out data synchronous.
Fig. 6 is the structured flowchart that carries out the synchronous device of data 600 between a plurality of clients shown in second preferred embodiment of the invention, and as shown in Figure 6, this device 600 also comprises module 602 is set on the basis of device 400.
Module 602 is set is used to data after changing that version number is set.
Those skilled in the art can also further recognize, unit and the algorithm steps of each example of describing in conjunction with embodiment disclosed herein, can realize with electronic hardware, computer software or the combination of the two, for the interchangeability of hardware and software is clearly described, composition and the step of each example described according to function in the above description in general manner.These functions are carried out with hardware or software mode actually, depend on application-specific and the design constraint of technical scheme.Those skilled in the art can specifically should be used for realizing described function with distinct methods to each, but this realization should not thought and exceeds scope of the present invention.
The software module that the method for describing in conjunction with embodiment disclosed herein or the step of algorithm can use hardware, processor to carry out, or the combination of the two is implemented.Software module can be placed in the storage medium of any other form known in random asccess memory (RAM), internal memory, read-only memory (ROM), electrically programmable ROM, electrically erasable ROM, register, hard disk, moveable magnetic disc, CD-ROM or technical field.
Above embodiment; object of the present invention, technical scheme and beneficial effect are further described; institute is understood that; these are only the specific embodiment of the present invention; the protection range being not intended to limit the present invention; within the spirit and principles in the present invention all, any modification of making, be equal to replacement, improvement etc., within all should being included in protection scope of the present invention.

Claims (10)

1. between a plurality of clients, carry out the synchronous method of data, it is characterized in that, comprising:
Server receives the change collection that described client generates, wherein, described client comprises the data that consist of a plurality of elements, described client generates the described change collection that comprises this secondary data change record after each data change, described client comprises the first client and the second client, and described change collection comprises the second change collection that the first change collects and described the second client generates that described the first client generates;
In described the first change collection and described the second change collection comprise described data during the more change of different elements, described server changes described in set pair the first client and described the second client according to described the first change collection and described second, and to carry out data synchronous.
2. method according to claim 1, is characterized in that, described method also comprises:
Described server is determined the order that generates described the first change collection and described the second change collection;
When described the first change collection and described the second change concentrate comprise described data in during difference more the becoming of identity element, described server according to sequentially after change set pair described in the first client and described the second client to carry out data synchronous.
3. method according to claim 1, is characterized in that, on described server for data after changing arrange version number.
4. method according to claim 3, is characterized in that, after each data change, described version number once increases progressively.
5. method according to claim 1, is characterized in that, described server is the client backup image file that carries out data change, and described image file is the copy of described client current data.
6. between a plurality of clients, carry out the synchronous device of data, it is characterized in that, comprising:
Receiver module, the change collection generating for receiving described client, wherein, described client comprises the data that consist of a plurality of elements, described client generates the described change collection that comprises this secondary data change record after each data change, described client comprises the first client and the second client, and described change collection comprises the second change collection that the first change collects and described the second client generates that described the first client generates;
The first synchronization module, when comprising the more change to the different elements of described data when described the first change collection and described the second change collection, according to described the first change, collect and described second change described in set pair the first client and described the second client to carry out data synchronous.
7. device according to claim 6, is characterized in that, also comprises:
Processing module, for determining the order that generates described the first change collection and described the second change collection;
The second synchronization module, while comprising difference more the becoming of described data identity element for concentrating when described the first change collection and described the second change, according to sequentially after change set pair described in the first client and described the second client to carry out data synchronous.
8. device according to claim 6, is characterized in that, also comprises:
Module is set, is used to data after changing that version number is set.
9. device according to claim 8, is characterized in that, after each data change, described version number once increases progressively.
10. device according to claim 6, is characterized in that, also comprises:
Backup module, is used to the client backup image file that carries out data change, and described image file is the copy of described client current data.
CN201310476939.0A 2013-10-13 2013-10-13 The method and apparatus that data syn-chronization is carried out between multiple client Active CN103716370B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201310476939.0A CN103716370B (en) 2013-10-13 2013-10-13 The method and apparatus that data syn-chronization is carried out between multiple client

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201310476939.0A CN103716370B (en) 2013-10-13 2013-10-13 The method and apparatus that data syn-chronization is carried out between multiple client

Publications (2)

Publication Number Publication Date
CN103716370A true CN103716370A (en) 2014-04-09
CN103716370B CN103716370B (en) 2018-01-02

Family

ID=50408942

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201310476939.0A Active CN103716370B (en) 2013-10-13 2013-10-13 The method and apparatus that data syn-chronization is carried out between multiple client

Country Status (1)

Country Link
CN (1) CN103716370B (en)

Cited By (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104967660A (en) * 2015-05-11 2015-10-07 华中科技大学 Network performance improving method oriented to multi-cloud architecture
CN106055353A (en) * 2016-05-23 2016-10-26 北京小米移动软件有限公司 Data update method and apparatus
CN106296365A (en) * 2016-08-19 2017-01-04 北京三快在线科技有限公司 A kind of purchase operates sharing method and device
CN106713392A (en) * 2015-11-13 2017-05-24 阿里巴巴集团控股有限公司 Data synchronization method, device and system
CN106779936A (en) * 2016-12-08 2017-05-31 上海携程国际旅行社有限公司 Firm Order system and Firm Order method
CN107172169A (en) * 2017-05-27 2017-09-15 广东欧珀移动通信有限公司 Method of data synchronization, device, server and storage medium
CN109614442A (en) * 2018-11-02 2019-04-12 东软集团股份有限公司 Data synchronous data listing maintenance, device, storage medium and electronic equipment
CN111901420A (en) * 2020-07-28 2020-11-06 深圳市康冠科技股份有限公司 Data synchronization method, device and system
CN112685346A (en) * 2020-12-29 2021-04-20 中电科航空电子有限公司 Multi-device data synchronization method based on ARINC429 bus

Citations (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040153576A1 (en) * 2001-06-30 2004-08-05 Uwe Hansmann System and method for a caching mechanism for a central synchronization server
CN101064630A (en) * 2006-04-24 2007-10-31 华为技术有限公司 Data synchronization method and system
CN101127869A (en) * 2007-09-20 2008-02-20 中兴通讯股份有限公司 An update and transmission method for electronic service guidance content information
CN101582908A (en) * 2009-06-30 2009-11-18 杭州华三通信技术有限公司 Parameter configuration method and equipment
CN101621398A (en) * 2008-06-30 2010-01-06 中兴通讯股份有限公司 Client/server system and method for automatic multi-client synchronous configuration thereof
CN101741830A (en) * 2009-11-09 2010-06-16 深圳市同洲电子股份有限公司 Method, system, client and server for realizing multi-client data synchronization
CN102089760A (en) * 2008-03-04 2011-06-08 苹果公司 Synchronization server process
CN103259824A (en) * 2012-02-21 2013-08-21 深圳市腾讯计算机系统有限公司 Method and device for synchronizing data route in distributed data storage system

Patent Citations (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040153576A1 (en) * 2001-06-30 2004-08-05 Uwe Hansmann System and method for a caching mechanism for a central synchronization server
CN101064630A (en) * 2006-04-24 2007-10-31 华为技术有限公司 Data synchronization method and system
CN101127869A (en) * 2007-09-20 2008-02-20 中兴通讯股份有限公司 An update and transmission method for electronic service guidance content information
CN102089760A (en) * 2008-03-04 2011-06-08 苹果公司 Synchronization server process
CN101621398A (en) * 2008-06-30 2010-01-06 中兴通讯股份有限公司 Client/server system and method for automatic multi-client synchronous configuration thereof
CN101582908A (en) * 2009-06-30 2009-11-18 杭州华三通信技术有限公司 Parameter configuration method and equipment
CN101741830A (en) * 2009-11-09 2010-06-16 深圳市同洲电子股份有限公司 Method, system, client and server for realizing multi-client data synchronization
CN103259824A (en) * 2012-02-21 2013-08-21 深圳市腾讯计算机系统有限公司 Method and device for synchronizing data route in distributed data storage system

Cited By (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104967660A (en) * 2015-05-11 2015-10-07 华中科技大学 Network performance improving method oriented to multi-cloud architecture
CN104967660B (en) * 2015-05-11 2018-01-05 华中科技大学 A kind of network performance method for improving towards more cloud frameworks
CN106713392A (en) * 2015-11-13 2017-05-24 阿里巴巴集团控股有限公司 Data synchronization method, device and system
CN106713392B (en) * 2015-11-13 2020-10-27 阿里巴巴集团控股有限公司 Data synchronization method, device and system
CN106055353A (en) * 2016-05-23 2016-10-26 北京小米移动软件有限公司 Data update method and apparatus
CN106055353B (en) * 2016-05-23 2019-03-29 北京小米移动软件有限公司 Data-updating method and device
CN106296365A (en) * 2016-08-19 2017-01-04 北京三快在线科技有限公司 A kind of purchase operates sharing method and device
CN106779936A (en) * 2016-12-08 2017-05-31 上海携程国际旅行社有限公司 Firm Order system and Firm Order method
CN106779936B (en) * 2016-12-08 2020-09-22 上海携程国际旅行社有限公司 Order verification system and order verification method
CN107172169A (en) * 2017-05-27 2017-09-15 广东欧珀移动通信有限公司 Method of data synchronization, device, server and storage medium
WO2018219178A1 (en) * 2017-05-27 2018-12-06 Oppo广东移动通信有限公司 Data synchronization method and apparatus, server, and storage medium
CN109614442A (en) * 2018-11-02 2019-04-12 东软集团股份有限公司 Data synchronous data listing maintenance, device, storage medium and electronic equipment
CN111901420A (en) * 2020-07-28 2020-11-06 深圳市康冠科技股份有限公司 Data synchronization method, device and system
CN112685346A (en) * 2020-12-29 2021-04-20 中电科航空电子有限公司 Multi-device data synchronization method based on ARINC429 bus
CN112685346B (en) * 2020-12-29 2023-03-14 中电科航空电子有限公司 Multi-device data synchronization method based on ARINC429 bus

Also Published As

Publication number Publication date
CN103716370B (en) 2018-01-02

Similar Documents

Publication Publication Date Title
CN103716370A (en) Method and device for data synchronization between multiple clients
CN109739810B (en) File synchronization method, server, client and device with storage function
CN109542613A (en) Distribution method, device and the storage medium of service dispatch in a kind of CDN node
CN105490854B (en) Real-time logs collection method, system and application server cluster
CN102857578B (en) A kind of file uploading method of network hard disc, system and net dish client
CN103324696B (en) A kind of data log collection and statistical analysis system and method
CN108196787B (en) Quota management method of cluster storage system and cluster storage system
CN104348859B (en) File synchronisation method, device, server, terminal and system
CN105488210B (en) A kind of batch data matching process and device
CN108595522A (en) A kind of increment synchronization method, apparatus and system
CN110572464A (en) Bottom layer resource state synchronization method and device, cloud platform system and storage medium
CN105959078B (en) A kind of cluster method for synchronizing time, cluster and clock synchronization system
CN105979277A (en) File transfer method and electronic equipment
CN113766282A (en) Live video processing method and device
CN111193622B (en) Asymmetric configuration management method, device and equipment and readable storage medium
CN102594874B (en) Synchronization processing method and device
CN111064776A (en) Method and device for generating blocks in block chain and storage medium
CN105991744B (en) Method and apparatus for synchronizing user application data
CN106156044B (en) Database switching method and device
US20140222771A1 (en) Management device and management method
US9286365B2 (en) Data synchronizing system and method thereof
CN109005246B (en) Data synchronization method, device and system
CN108874856B (en) Page generation system, method and server
CN111130915B (en) Data reconciliation method based on network configuration data
CN112217712A (en) Message multi-terminal synchronization method and client

Legal Events

Date Code Title Description
C06 Publication
PB01 Publication
C10 Entry into substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant