CN101741830A - Method, system, client and server for realizing multi-client data synchronization - Google Patents
Method, system, client and server for realizing multi-client data synchronization Download PDFInfo
- Publication number
- CN101741830A CN101741830A CN200910110134A CN200910110134A CN101741830A CN 101741830 A CN101741830 A CN 101741830A CN 200910110134 A CN200910110134 A CN 200910110134A CN 200910110134 A CN200910110134 A CN 200910110134A CN 101741830 A CN101741830 A CN 101741830A
- Authority
- CN
- China
- Prior art keywords
- application data
- client
- type
- application
- server
- 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.)
- Pending
Links
Images
Landscapes
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The invention discloses a method for realizing multi-client data synchronization. The method comprises the following steps that: a client receives an application request of a user, and determines the type of application data requested by the application request; according to the type of the application data, the client reads a last updating time T1 when the application data of the type is updated from a server; and the client compares the T1 with a last updating time T2 of the application data, of the type, stored by the client, synchronizes the application data of the type according to a comparison result, and responds to the application request according to the synchronized application data of the type. Correspondingly, the invention also discloses a client, a server and a system for realizing the multi-client data synchronization. The method, the system, the client and the server can ensure the data synchronization among a plurality of clients, and simultaneously, save time, reduce the occupation space of a memory of the system, and improve the performance of the system.
Description
Technical field
The present invention relates to the communications field, relate in particular to a kind of method, system, client and server of realizing multi-client data synchronization.
Background technology
In the network connection mode, (Clint/Server, C/S) network of framework is the network that is different from the another kind of form of peer-to-peer network to client/server.In the C/S framework, server is a server, and client is the basis of network, and client relies on server to obtain needed Internet resources, and server provides network necessary resource for client.At present, the network of C/S framework has been played the part of very important role in existing the Internet, for people provide abundant service, and such as the address book management, chat record management or the like.
Because all there are data in client and server, it is synchronous that system need carry out data necessary.In the existing technology, each client guarantees that data sync mainly contains two kinds of schemes between system.A kind ofly be: when some clients had Data Update, server just sent a message to other clients, forced other client also to be done to upgrade to handle; The defective of this kind scheme is that other client may and be lost interest in to data updated, or does not need to be applied to data updated, can cause the loss of resource like this.Another kind of scheme is: when certain client needs application data, all need the data of access server at every turn.This kind scheme, therefore extremely consuming time because each all databases of access server all read lot of data at every turn, simultaneously, the internal memory and the performance of infringement system.
Summary of the invention
Problem to be solved by this invention is, a kind of method, system, server and client that realizes multi-client data synchronization is provided, can guarantees the data sync between the multi-client, save time simultaneously, systematic function is improved in the EMS memory occupation space of minimizing system.
In order to address the above problem, the embodiment of the invention discloses a kind of method that realizes multi-client data synchronization, this method comprises:
Client receives user's application request, determines the type of the application data that described application request is asked;
According to the type of described application data, described client reads the latest update time T 1 that the application data of described type is updated from server;
Described client is the final updating time T 2 of T1 and the application data of the described type of self storage relatively, according to result relatively, and the application data of synchronous described type, and, respond described application request according to the application data of the described type after synchronously.
Correspondingly, the embodiment of the invention also discloses a kind of client, comprising:
Receiving element is used to receive user's application request;
Determining unit, the type of the application data that is used for determining that described application request is asked;
Reading unit is used for the type according to described application data, reads the latest update time T 1 that the application data of described type is updated from server;
Comparing unit is used for the final updating time T 2 of application data of the described type of comparison T1 and described client self storage;
Lock unit is used for according to described comparing unit result relatively, the application data of synchronous described type;
Response unit is used for the application data according to the described type of described lock unit after synchronously, responds described application request.
Correspondingly, the embodiment of the invention also discloses a kind of server, comprising:
Memory cell is used to store all types of application datas, and stores client is upgraded operation to described all types of application data the latest update time;
Data synchronisation unit, the type that is used for the application data of asking according to client, the latest update time T 1 of the application data of the described type of described cell stores is sent to described client, and when T1 is later than the final updating time T 2 of application data of described type of described client stores, the application data of described type is sent to described client, so that the application data of the synchronous described type of described client.
Correspondingly, the embodiment of the invention also discloses a kind of system that realizes multi-client data synchronization, comprise server and at least two clients,
Described server is used to store all types of application datas, and stores client is upgraded operation to described all types of application data the latest update time; When described client has application request, send latest update time T 1 that application data that described application request asks is updated to described client, and when described client is carried out described application data synchronous, described application data is sent to described client;
Described client is used for the application request according to the user who receives, and determines the type of the application data that described application request is asked; From server, read the latest update time T 1 that the application data of described type is updated; The final updating time T 2 of T1 and the application data of the described type of self preserving relatively, the application data of synchronous described type, and, respond described application request according to the application data of the described type after synchronous.
The embodiment of the invention compared by the latest update time to the data type of client application, and do Synchronous Processing according to comparative result, make client obtain data as required, can guarantee data sync between multi-client, guarantee that each visit all can get access to latest data, save time simultaneously, reduce the EMS memory occupation space of system, improve systematic function.
Description of drawings
In order to be illustrated more clearly in embodiment of the invention technical scheme, the accompanying drawing of required use is done to introduce simply in will describing embodiment below, apparently, accompanying drawing in describing below only is some embodiments of the present invention, for those of ordinary skills, under the prerequisite of not paying creative work, can also obtain other accompanying drawing according to these accompanying drawings.
Fig. 1 is the structural representation of the embodiment of a kind of system that realizes multi-client data synchronization of the present invention;
Fig. 2 is the structural representation of the embodiment of a kind of server of the present invention;
Fig. 3 is the structural representation of the embodiment of a kind of client of the present invention;
Fig. 4 is the lock unit structural representation of the embodiment of a kind of client of the present invention;
Fig. 5 is the flow chart of the embodiment of a kind of method that realizes multi-client data synchronization of the present invention.
Embodiment
Below in conjunction with the accompanying drawing in the embodiment of the invention, the technical scheme in the embodiment of the invention is clearly and completely described, obviously, described embodiment only is the present invention's part embodiment, rather than whole embodiment.Based on the embodiment among the present invention, those of ordinary skills belong to the scope of protection of the invention not making the every other embodiment that is obtained under the creative work prerequisite.
With reference to Fig. 1, be the structural representation of the embodiment of a kind of system that realizes multi-client data synchronization of the present invention; As shown in Figure 1, described system comprises: server 20, and at least two clients 10 (because each client terminal structure is all basic identical, only client 1 has been made mark among the figure, in this explanation, N is a natural number among the figure, and the expression client can have a plurality of).
Described server 20 is used to store all types of application datas, and stores the latest update time that 10 pairs of described all types of application datas of client are upgraded operation; When described client 10 has application request, send latest update time T 1 that application data that described application request asks is updated to described client 10, and when described client 10 is carried out described application data synchronous, described application data is sent to described client 10;
In the specific implementation, because server 20 provides network necessary resource for client 10, therefore, there is mass data in the server 20, various data can be classified, the standard of its classification can be used employed application data according to each of client 10, such as, when described client 10 needed inquiry good friend address, the type of the application data that need use this moment can be address book managing application data class (Table A A); For another example, when described client 10 needed the inquiry chat record, the application data that needs to use can be divided into chat record managing application data class (table BB) or the like.
Particularly, described server 20 can be a database, and a table can be set in database, and described table can be established three fields, id, key, value.Wherein id represents from increasing field, promptly can be used for representing the sequence number of each operation, such as, client is designated as 1 when operating for the first time, and operation for the second time is designated as 2 or the like; Key represents the various classification of application data, and the form that every class application data can be shown is stored in the database, and key has promptly stored the table name of all kinds of tables, such as: stored the table name of address book managing application data table among the key, promptly represented with Table A A; Or the table name of chat record managing application data table, promptly represent or the like with table BB; What Value represented is the latest update time that all types of application datas is updated, such as, when client 10 has been upgraded application data among the Table A A, Value is composed the current time, be that the key value is in the record of " AA " in the database, corresponding Value value is the latest update time of " AA " class application data; Particularly, the table name of all types of application data in the described key field is corresponding one by one with the time value in the described value field, such as, the key value is the record of " AA ", a corresponding unique Value value, the key value is the record of " BB ", a corresponding unique Value value etc.Particularly, the corresponding relation of key and Value such as following table:
| ??Key | ??Value |
| ??AA | The latest update time that application data among the Table A A is updated |
| ??BB | The latest update time that application data among the table BB is updated |
| ??...... | ??...... |
Be understandable that, last table is only for giving an example, it has reflected the corresponding relation between key field and the Value field, application scenario at other can similarly be set, in the key field, may also have other application data sheet, as CC, then in its corresponding Value field, should be corresponding " the latest update time that the application data among the table CC is updated "; When the table name of the application data classification chart of storing in the key field changed, its corresponding Value field was done corresponding the variation, does not give unnecessary details at this.
Described client 10 is used for the application request according to the user who receives, and determines the type of the application data that described application request is asked; From server 20, read the latest update time T 1 that the application data of described type is updated; The final updating time T 2 of T1 and the application data of the described type of self preserving relatively, the application data of synchronous described type, and, respond described application request according to the application data of the described type after synchronous.
The embodiment of the invention compared by the latest update time to the data type of client application, and do Synchronous Processing according to comparative result, make client obtain data as required, can guarantee data sync between multi-client, guarantee that each visit all can get access to latest data, save time simultaneously, reduce the EMS memory occupation space of system, improve systematic function.
With reference to Fig. 2, be the structural representation of the embodiment of a kind of server of the present invention; Server embodiment illustrated in fig. 2 can be the server among the system shown in Figure 1 embodiment 20, and as shown in Figure 2, described server 20 comprises: memory cell 201 and data synchronisation unit 202.
Described memory cell 201 is used to store all types of application datas, and stores client is upgraded operation to described all types of application data the latest update time;
In the specific implementation, as previously mentioned, because server 20 provides network necessary resource for client 10, therefore, there is mass data in the server 20, can be with various data qualifications, the standard of its classification can be used employed application data according to each of client 10, such as, when described client 10 needed inquiry good friend address, the application data that need to use this moment can be divided into address book managing application data class (Table A A); For another example, when described client 10 needed the inquiry chat record, the application data that needs to use can be divided into chat record managing application data class (table BB) or the like.
Particularly, described server 20 can be a database, and a table can be set in database, and described table can be established three fields, id, key, value.Wherein id represents from increasing field, promptly can be used for representing the sequence number of each operation, such as, client is designated as 1 when operating for the first time, and operation for the second time is designated as 2 or the like; Key represents the various classification of application data, and the form that every class application data can be shown is stored in the database, and key has promptly stored the table name of all kinds of tables, such as: stored the table name of address book managing application data table among the key, promptly represented with Table A A; Or the table name of chat record managing application data table, promptly represent or the like with table BB; What Value represented is the latest update time that all types of application datas is updated, such as, when client 10 has been upgraded application data among the Table A A, Value is composed the current time, be that the key value is in the record of " AA " in the database, corresponding Value value is the latest update time of " AA " class application data; Particularly, the table name of all types of application data in the described key field is corresponding one by one with the time value in the described value field, such as, the key value is the record of " AA ", a corresponding unique Value value, the key value is the record of " BB ", a corresponding unique Value value etc.Particularly, the corresponding relation of key and Value such as following table:
| ??Key | ??Value |
| ??AA | The latest update time that application data among the Table A A is updated |
| ??BB | The latest update time that application data among the table BB is updated |
| ??...... | ??...... |
Be understandable that, last table is only for giving an example, it has reflected the corresponding relation between key field and the Value field, application scenario at other can similarly be set, in the key field, may also have other application data sheet, as CC, then in its corresponding Value field, should be corresponding " the latest update time that the application data among the table CC is updated "; When the table name of the application data classification chart of storing in the key field changed, its corresponding Value field was done corresponding the variation, does not give unnecessary details at this.
Accordingly, the table name that writes down in the key field for all types of application datas, application data in the table of each table name correspondence then is stored in the described memory cell 201, in addition, Value value in the Value field of the table name correspondence of all types of application data that writes down among the key, be stored in simultaneously in the described memory cell 201, its Value value shows under the table name in the described key field of its correspondence, the latest update time that the application data in the table is updated.
Described data synchronisation unit 202, the type that is used for the application data of asking according to client, the latest update time T 1 of the application data of the described type of described memory cell 201 storages is sent to described client, and when T1 is later than the final updating time T 2 of application data of described type of described client stores, the application data of described type is sent to described client, so that the application data of the synchronous described type of described client.
The embodiment of the invention can guarantee data sync between multi-client, guarantees that each visit all can get access to latest data, saves time simultaneously, reduces the EMS memory occupation space of system, improves systematic function.
With reference to Fig. 3, be the structural representation of the embodiment of a kind of client of the present invention; Client embodiment illustrated in fig. 3 can be the client among the system shown in Figure 1 embodiment 10, as shown in Figure 3, described client 10 comprises: receiving element 101, determining unit 102, reading unit 103, comparing unit 104, lock unit 105 and response unit 106.
Described receiving element 101 is used to receive user's application request;
Described determining unit 102, the type of the application data that is used for determining that described application request is asked;
Further as shown in Figure 3, described client 10 also comprises: memory cell 107.
Described memory cell 107 is used to store final updating time of all types of application datas and described all types of application data.In the specific implementation, be analogous to the mode classification of the application data in the server, also there is mass data in the client, can corresponding in the server to the mode classification of described application data, client also can be with various data qualifications, and the standard of its classification can be used employed application data according to each of client equally, such as, when the user need inquire about the good friend address, the application data that need to use this moment can be divided into address book managing application data class (Table A A); For another example, when described user need inquire about chat record, the application data that needs to use can be divided into chat record managing application data class (table BB) or the like.In addition, the application data in the client also can be stored with the form of table, and its mode is analogous to the storage mode of the application data in the server, does not give unnecessary details at this.
From the above, described receiving element 101 receives the application request of the inquiry good friend address of described user's transmission, described determining unit 102 determines that promptly this type of using the application data of being asked is: address book managing application data class, i.e. AA class application data.
Described reading unit 103 is used for the type according to described application data, reads the latest update time T 1 that the application data of described type is updated from server; In the specific implementation, after described determining unit 102 determines that this type of using used application data is AA, described reading unit 103 promptly from the memory cell 201 of server 20 the key value for reading the Value value of AA in the pairing Value field of record of " AA ", be the latest update time that AA class application data is updated, available T1 represents.
Described comparing unit 104 is used for the final updating time T 2 of application data of the described type of comparison T1 and described client self storage; Particularly, after described reading unit 103 reads T1, described T1 is sent to described comparing unit 104, described comparing unit 104 reads the final updating time T 2 of the application data of described type from memory cell 107, afterwards, described comparing unit 104 compares T1 and T2.
Described lock unit 105 is used for according to described comparing unit 104 result relatively, the application data of synchronous described type;
With reference to Fig. 4, be the lock unit structural representation of the embodiment of a kind of client of the present invention; As shown in Figure 4, described lock unit 105 comprises: first lock unit 51 and second lock unit 52.
Described first lock unit 51 is used for when T1 is later than T2, visits the application data of the described type of described server, upgrades the application data of the described type of described client according to the application data of the described type of described server, and gives T2 with the value of T1;
Described second lock unit 52, be used for as T1 during early than T2, the application data of described type of self storage is sent to described server, and give T1 in the described server with the value of T2, so that described server upgrades the application data of the described type of described server according to the application data of the described type of described client.
Described response unit 106 is used for the application data according to the described type of described lock unit 105 after synchronously, responds described application request.In the specific implementation, after the application data of described type was carried out synchronously through described first lock unit 51, described response unit 106 used the application data of the described type after the described renewal to go to respond described application request; After the application data of described type was carried out synchronously through described second lock unit 52, described response unit 106 used the application data of the described type of described memory cell 107 storages to respond described application request.
1 application table AA is an example with client, if after described comparing unit 104 comparisons, described T1 is later than T2, promptly show after the final updating time T 2 of the AA class application data that described client 1 self is stored, be carved with Data Update during the T1 of Table A A after T2, then described first lock unit 51 is promptly visited the application data of the described type of described server, upgrade the application data of the AA class in the memory cell 107 of described client 1 according to the application data of the described type of described server, give T2 with the value of T1, and respond described application request according to the application data of the AA class of the described client 1 after upgrading; If after described comparing unit 104 comparisons, described T1 is early than T2, the application data that shows the AA class of self storing in described client 1 is newer than the application data of the AA class in the described server, promptly need to upgrade the application data of AA class in the described server, then described second lock unit 52 sends to described server with the application data of the AA class that described client 1 self is stored, and give T1 in the described server with the value of T2, described server upgrades the application data of the AA class of described server according to the application data of the AA class of described client 1, and described client 1 responds described application request according to the application data of the AA class of self storage.
In addition, if client has been upgraded the data of table BB, the data of showing BB have been upgraded such as client 2 or other clients N, and described client 1 determines that this application can not use the application data of table BB, be that described client 1 his-and-hers watches BB does not have relevant application to handle, the renewal of then described client 1 his-and-hers watches BB is lost interest in, and his-and-hers watches BB is left intact.
The embodiment of the invention compared by the latest update time to the data type of client application; and do Synchronous Processing according to comparative result; make client obtain data as required; can guarantee data sync between multi-client; guarantee that each visit all can get access to latest data; save time simultaneously, the protection system internal memory improves systematic function.
With reference to Fig. 5, be the flow chart of the embodiment of a kind of method that realizes multi-client data synchronization of the present invention; As shown in Figure 5, described method comprises:
S101, client receives user's application request, determines the type of the application data that described application request is asked;
In the specific implementation, be analogous to the mode classification of the application data in the server, also there is mass data in the client, can corresponding in the server to the mode classification of described application data, client also can be with various data qualifications, and the standard of its classification can be used employed application data according to each of client equally, such as, when the user need inquire about the good friend address, the application data that need to use this moment can be divided into address book managing application data class (Table A A); For another example, when described user need inquire about chat record, the application data that needs to use can be divided into chat record managing application data class (table BB) or the like.In addition, the application data in the client also can be stored with the form of table, and its mode is analogous to the storage mode of the application data in the server, does not give unnecessary details at this.
From the above, described client receives the application request of the inquiry good friend address of user's transmission, determines that promptly this type of using the application data of being asked is: address book managing application data class, i.e. AA class application data.
S102, according to the type of described application data, described client reads the latest update time T 1 that the application data of described type is updated from server; In the specific implementation, the executive agent of described S102 can be the reading unit 103 of the embodiment of client 10 shown in Figure 3.Particularly, the type of the application data of being asked according to determined this application request of S101 is AA, then among the S102, the reading unit 103 of described client 10 promptly from the memory cell 201 of server 20 the key value for reading the Value value of AA in the pairing Value field of record of " AA ", be the latest update time that AA class application data is updated, available T1 represents.
S103, the final updating time T 2 of the application data of the described type of described client comparison T1 and self storage, according to the result of described comparison, the application data of synchronous described type, and, respond described application request according to the application data of the described type after synchronously.
In the specific implementation, the executive agent of described S103 can be comparing unit 104, the lock unit 105 of client embodiment illustrated in fig. 3 10, and response unit 106.Concrete, described S103 comprises:
If T1 is later than T2, the application data of the described type of the described server of described client-access, upgrade the application data of the described type of described client according to the application data of the described type of described server, give T2 with the value of T1, and respond described application request according to the application data of the described type of the described client after upgrading;
If T1 is early than T2, described client sends to described server with the application data of the described type that self stores, and give T1 in the described server with the value of T2, described server upgrades the application data of the described type of described server according to the application data of the described type of described client, and described client responds described application request according to the application data of the described type of self storage.
1 application table AA is an example with client, if after relatively, described T1 is later than T2, promptly show after the final updating time T 2 of the AA class application data that described client 1 self is stored, be carved with Data Update during the T1 of Table A A after T2, then described client is promptly visited the application data of the described type of described server, upgrade the application data of the AA class in the described client 1 according to the application data of the described type of described server, give T2 with the value of T1, and respond described application request according to the application data of the AA class of the described client 1 after upgrading; If after relatively, described T1 is early than T2, the application data that shows the AA class of self storing in described client 1 is newer than the application data of the AA class in the described server, promptly need to upgrade the application data of AA class in the described server, then described client 1 sends to described server with the application data of the AA class that self stores, and give T1 in the described server with the value of T2, described server upgrades the application data of the AA class of described server according to the application data of the AA class of described client 1, and described client 1 responds described application request according to the application data of the AA class of self storage.
In addition, if client has been upgraded the data of table BB, the data of showing BB have been upgraded such as client 2 or other clients N, and described client 1 determines that this application can not use the application data of table BB, be that described client 1 his-and-hers watches BB does not have relevant application to handle, the renewal of then described client 1 his-and-hers watches BB is lost interest in, and his-and-hers watches BB is left intact.
The embodiment of the invention compared by the latest update time to the data type of client application, and do Synchronous Processing according to comparative result, make client obtain data as required, can guarantee data sync between multi-client, guarantee that each visit all can get access to latest data, save time simultaneously, reduce the EMS memory occupation space of system, improve systematic function.
Above disclosed only is a kind of preferred embodiment of the present invention, certainly can not limit the present invention's interest field with this, one of ordinary skill in the art will appreciate that all or part of flow process that realizes the foregoing description, and, still belong to the scope that invention is contained according to the equivalent variations that claim of the present invention is done.
Claims (10)
1. method that realizes multi-client data synchronization is characterized in that:
Client receives user's application request, determines the type of the application data that described application request is asked;
According to the type of described application data, described client reads the latest update time T 1 that the application data of described type is updated from server;
Described client is the final updating time T 2 of T1 and the application data of the described type of self storage relatively, according to result relatively, and the application data of synchronous described type, and, respond described application request according to the application data of the described type after synchronously.
2. the method for claim 1 is characterized in that, described client reads the latest update time T 1 that the application data of described type is updated from server, comprising:
The server record client is upgraded the latest update time of operation to all types of application data of described server stores;
Described client reads the latest update time T 1 that the application data of described type is updated from the latest update time of the described all types of application data of described server record.
3. method as claimed in claim 2, it is characterized in that, the final updating time T 2 of the application data of the described type of described client comparison T1 and self storage, according to result relatively, the application data of synchronous described type, and, respond described application request according to the application data of the described type after synchronously, comprising:
If T1 is later than T2, the application data of the described type of the described server of described client-access, upgrade the application data of the described type of described client according to the application data of the described type of described server, give T2 with the value of T1, and respond described application request according to the application data of the described type of the described client after upgrading;
If T1 is early than T2, described client sends to described server with the application data of the described type that self stores, and give T1 in the described server with the value of T2, described server upgrades the application data of the described type of described server according to the application data of the described type of described client, and described client responds described application request according to the application data of the described type of self storage.
4. a client is characterized in that, comprising:
Receiving element is used to receive user's application request;
Determining unit, the type of the application data that is used for determining that described application request is asked;
Reading unit is used for the type according to described application data, reads the latest update time T 1 that the application data of described type is updated from server;
Comparing unit is used for the final updating time T 2 of application data of the described type of comparison T1 and described client self storage;
Lock unit is used for according to described comparing unit result relatively, the application data of synchronous described type;
Response unit is used for the application data according to the described type of described lock unit after synchronously, responds described application request.
5. client as claimed in claim 4 is characterized in that, described lock unit comprises:
First lock unit is used for when T1 is later than T2, visits the application data of the described type of described server, upgrades the application data of the described type of described client according to the application data of the described type of described server, and gives T2 with the value of T1;
Second lock unit, be used for as T1 during early than T2, the application data of described type of self storage is sent to described server, and give T1 in the described server with the value of T2, so that described server upgrades the application data of the described type of described server according to the application data of the described type of described client.
6. as claim 4 or 5 described clients, it is characterized in that described client also comprises:
Memory cell is used to store final updating time of all types of application datas and described all types of application data.
7. a server is characterized in that, comprising:
Memory cell is used to store all types of application datas, and stores client is upgraded operation to described all types of application data the latest update time;
Data synchronisation unit, the type that is used for the application data of asking according to client, the latest update time T 1 of the application data of the described type of described cell stores is sent to described client, and when T1 is later than the final updating time T 2 of application data of described type of described client stores, the application data of described type is sent to described client, so that the application data of the synchronous described type of described client.
8. a system that realizes multi-client data synchronization is characterized in that, comprises server and at least two clients,
Described server is used to store all types of application datas, and stores client is upgraded operation to described all types of application data the latest update time; When described client has application request, send latest update time T 1 that application data that described application request asks is updated to described client, and when described client is carried out described application data synchronous, described application data is sent to described client;
Described client is used for the application request according to the user who receives, and determines the type of the application data that described application request is asked; From server, read the latest update time T 1 that the application data of described type is updated; The final updating time T 2 of T1 and the application data of the described type of self preserving relatively, the application data of synchronous described type, and, respond described application request according to the application data of the described type after synchronous.
9. system as claimed in claim 8 is characterized in that, described server comprises:
Memory cell is used to store all types of application datas, and stores client is upgraded operation to described all types of application data the latest update time;
Data synchronisation unit, the type that is used for the application data of asking according to client, the latest update time T 1 of the application data of the described type of described cell stores is sent to described client, and when T1 is later than the final updating time T 2 of application data of described type of described client stores, the application data of described type is sent to described client, so that the application data of the synchronous described type of described client.
10. system as claimed in claim 9 is characterized in that, described client comprises:
Receiving element is used to receive user's application request;
Determining unit, the type of the application data that is used for determining that described application request is asked;
Reading unit is used for the type according to described application data, reads the latest update time T 1 that the application data of described type is updated from server;
Comparing unit is used for the final updating time T 2 of application data of the described type of comparison T1 and described client self storage;
Lock unit is used for according to described comparing unit result relatively, the application data of synchronous described type;
Response unit is used for the application data according to the described type of described lock unit after synchronously, responds described application request.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN200910110134A CN101741830A (en) | 2009-11-09 | 2009-11-09 | Method, system, client and server for realizing multi-client data synchronization |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN200910110134A CN101741830A (en) | 2009-11-09 | 2009-11-09 | Method, system, client and server for realizing multi-client data synchronization |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN101741830A true CN101741830A (en) | 2010-06-16 |
Family
ID=42464722
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN200910110134A Pending CN101741830A (en) | 2009-11-09 | 2009-11-09 | Method, system, client and server for realizing multi-client data synchronization |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN101741830A (en) |
Cited By (17)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102916993A (en) * | 2011-08-03 | 2013-02-06 | 腾讯科技（深圳）有限公司 | Network hard disk data updating method and device |
| CN103095765A (en) * | 2011-11-03 | 2013-05-08 | 陈璧超 | Peer-to-peer communication network and data content distributing method thereof and communication node thereof |
| CN103379159A (en) * | 2012-04-24 | 2013-10-30 | 阿里巴巴集团控股有限公司 | Distributed web site data synchronization method |
| CN103491113A (en) * | 2012-06-11 | 2014-01-01 | 腾讯科技（深圳）有限公司 | Synchronization method, device and system for information syndication files |
| CN103716370A (en) * | 2013-10-13 | 2014-04-09 | 北界创想（北京）软件有限公司 | Method and device for data synchronization between multiple clients |
| CN103812849A (en) * | 2012-11-15 | 2014-05-21 | 腾讯科技（深圳）有限公司 | Local cache updating method and system, client and server |
| CN103905441A (en) * | 2014-03-28 | 2014-07-02 | 广州华多网络科技有限公司 | Data acquisition method and device |
| CN104462536A (en) * | 2014-12-24 | 2015-03-25 | 北京奇艺世纪科技有限公司 | File access method and device |
| CN104702703A (en) * | 2015-03-30 | 2015-06-10 | 北京奇艺世纪科技有限公司 | Method and device for updating data |
| CN105100290A (en) * | 2015-09-30 | 2015-11-25 | 北京恒华伟业科技股份有限公司 | Data synchronization method and device |
| CN105577798A (en) * | 2015-12-25 | 2016-05-11 | 北京奇虎科技有限公司 | Method and device for updating and issuing data |
| CN106469158A (en) * | 2015-08-17 | 2017-03-01 | 杭州海康威视系统技术有限公司 | Method of data synchronization and device |
| US20170068570A1 (en) * | 2015-09-08 | 2017-03-09 | Apple Inc. | System for managing asset manager lifetimes |
| WO2017084520A1 (en) * | 2015-11-18 | 2017-05-26 | 阿里巴巴集团控股有限公司 | Method and apparatus for synchronizing data files in a cloud environment |
| CN106790535A (en) * | 2016-12-22 | 2017-05-31 | 深圳爱拼信息科技有限公司 | A kind of college entrance will table synchronous method and server |
| CN108388502A (en) * | 2018-01-18 | 2018-08-10 | 珠海金山网络游戏科技有限公司 | A kind of method and apparatus that multiterminal detection data merges |
| CN108563776A (en) * | 2018-04-24 | 2018-09-21 | 武汉斗鱼网络科技有限公司 | Off-line data acquisition methods and system, server and storage medium |
-
2009
- 2009-11-09 CN CN200910110134A patent/CN101741830A/en active Pending
Cited By (27)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102916993A (en) * | 2011-08-03 | 2013-02-06 | 腾讯科技（深圳）有限公司 | Network hard disk data updating method and device |
| CN103095765B (en) * | 2011-11-03 | 2015-06-17 | 陈璧超 | Peer-to-peer communication network and data content distributing method thereof and communication node thereof |
| CN103095765A (en) * | 2011-11-03 | 2013-05-08 | 陈璧超 | Peer-to-peer communication network and data content distributing method thereof and communication node thereof |
| CN103379159A (en) * | 2012-04-24 | 2013-10-30 | 阿里巴巴集团控股有限公司 | Distributed web site data synchronization method |
| CN103379159B (en) * | 2012-04-24 | 2016-06-22 | 阿里巴巴集团控股有限公司 | A kind of method that distributed Web station data synchronizes |
| CN103491113A (en) * | 2012-06-11 | 2014-01-01 | 腾讯科技（深圳）有限公司 | Synchronization method, device and system for information syndication files |
| CN103491113B (en) * | 2012-06-11 | 2018-06-08 | 腾讯科技（深圳）有限公司 | A kind of synchronous method, the apparatus and system of information fusion file |
| CN103812849B (en) * | 2012-11-15 | 2018-12-07 | 腾讯科技（深圳）有限公司 | A kind of local cache update method, system, client and server |
| CN103812849A (en) * | 2012-11-15 | 2014-05-21 | 腾讯科技（深圳）有限公司 | Local cache updating method and system, client and server |
| CN103716370B (en) * | 2013-10-13 | 2018-01-02 | 北界创想（北京）软件有限公司 | The method and apparatus that data syn-chronization is carried out between multiple client |
| CN103716370A (en) * | 2013-10-13 | 2014-04-09 | 北界创想（北京）软件有限公司 | Method and device for data synchronization between multiple clients |
| CN103905441A (en) * | 2014-03-28 | 2014-07-02 | 广州华多网络科技有限公司 | Data acquisition method and device |
| CN103905441B (en) * | 2014-03-28 | 2017-08-25 | 广州华多网络科技有限公司 | Data capture method and device |
| CN104462536B (en) * | 2014-12-24 | 2018-08-07 | 北京奇艺世纪科技有限公司 | A kind of file access method and device |
| CN104462536A (en) * | 2014-12-24 | 2015-03-25 | 北京奇艺世纪科技有限公司 | File access method and device |
| CN104702703A (en) * | 2015-03-30 | 2015-06-10 | 北京奇艺世纪科技有限公司 | Method and device for updating data |
| CN104702703B (en) * | 2015-03-30 | 2019-03-15 | 北京奇艺世纪科技有限公司 | A kind of data-updating method and device |
| CN106469158B (en) * | 2015-08-17 | 2019-10-08 | 杭州海康威视系统技术有限公司 | Method of data synchronization and device |
| CN106469158A (en) * | 2015-08-17 | 2017-03-01 | 杭州海康威视系统技术有限公司 | Method of data synchronization and device |
| US20170068570A1 (en) * | 2015-09-08 | 2017-03-09 | Apple Inc. | System for managing asset manager lifetimes |
| CN105100290A (en) * | 2015-09-30 | 2015-11-25 | 北京恒华伟业科技股份有限公司 | Data synchronization method and device |
| WO2017084520A1 (en) * | 2015-11-18 | 2017-05-26 | 阿里巴巴集团控股有限公司 | Method and apparatus for synchronizing data files in a cloud environment |
| CN105577798B (en) * | 2015-12-25 | 2019-03-05 | 北京奇虎科技有限公司 | Update the method and device of publication data |
| CN105577798A (en) * | 2015-12-25 | 2016-05-11 | 北京奇虎科技有限公司 | Method and device for updating and issuing data |
| CN106790535A (en) * | 2016-12-22 | 2017-05-31 | 深圳爱拼信息科技有限公司 | A kind of college entrance will table synchronous method and server |
| CN108388502A (en) * | 2018-01-18 | 2018-08-10 | 珠海金山网络游戏科技有限公司 | A kind of method and apparatus that multiterminal detection data merges |
| CN108563776A (en) * | 2018-04-24 | 2018-09-21 | 武汉斗鱼网络科技有限公司 | Off-line data acquisition methods and system, server and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN101741830A (en) | Method, system, client and server for realizing multi-client data synchronization | |
| CN104580226A (en) | Session data sharing system and method | |
| EA002931B1 (en) | Database synchronization and organization system and method | |
| CN108829720B (en) | Data processing method and device | |
| US20160026699A1 (en) | Method for Synchronization of UGC Master and Backup and System Thereof, and Computer Storage Medium | |
| CN109639773B (en) | Dynamically constructed distributed data cluster control system and method thereof | |
| CN106326239A (en) | Distributed file system and file meta-information management method thereof | |
| CN104750740A (en) | Data renewing method and device | |
| CN103607424A (en) | Server connection method and server system | |
| CN106339387B (en) | Increase the method for data synchronization and device of server in a kind of data-base cluster newly | |
| CN105608126A (en) | Method and apparatus for establishing secondary indexes for massive databases | |
| WO2016082594A1 (en) | Data update processing method and apparatus | |
| CN112069260A (en) | Data storage and account checking method and system | |
| CN103491137A (en) | Data synchronizing system and data synchronizing method | |
| CN114185991A (en) | Method and related device for realizing data synchronization based on distributed database | |
| CN106569929A (en) | Real-time data access method and system for monitoring system | |
| CN112069152B (en) | Database cluster upgrading method, device, equipment and storage medium | |
| EP3061011B1 (en) | Method for optimizing index, master database node and subscriber database node | |
| US9767023B2 (en) | Method of controlling data writing to persistent storage device | |
| CN113254463A (en) | List updating method, system and medium | |
| CN107885824A (en) | A kind of data read-write method and system | |
| CN111274004A (en) | Process instance management method and device and computer storage medium | |
| CN116701413A (en) | Main data processing method and device | |
| US20190065327A1 (en) | Efficient versioned object management | |
| CN112749172A (en) | Data synchronization method and system between cache and database |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| REG | Reference to a national code |
Ref country code: HK Ref legal event code: DE Ref document number: 1145235 Country of ref document: HK |
|
| ASS | Succession or assignment of patent right |
Owner name: SHENZHEN LONGSHI MEDIA CO., LTD. Free format text: FORMER OWNER: SHENZHEN TONGZHOU ELECTRONIC CO., LTD. Effective date: 20120424 |
|
| C41 | Transfer of patent application or patent right or utility model | ||
| COR | Change of bibliographic data |
Free format text: CORRECT: ADDRESS; FROM: 518129 SHENZHEN, GUANGDONG PROVINCE TO: 518057 SHENZHEN, GUANGDONG PROVINCE |
|
| TA01 | Transfer of patent application right |
Effective date of registration: 20120424 Address after: 518057 District, Guangdong, Nanshan District hi tech Zone, the North Zone of the Fifth Industrial Zone, rainbow science and technology building, A2-3 District, Applicant after: Shenzhen Longguan Media Co., Ltd. Address before: 518129 Rainbow Technology Building, North hi tech Zone, Nanshan District, Guangdong, Shenzhen Applicant before: Shenzhen Tongzhou Electronic Co., Ltd. |
|
| C12 | Rejection of a patent application after its publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20100616 |
|
| REG | Reference to a national code |
Ref country code: HK Ref legal event code: WD Ref document number: 1145235 Country of ref document: HK |