CN101325478A - Method and system for data synchronization - Google Patents
Method and system for data synchronization Download PDFInfo
- Publication number
- CN101325478A CN101325478A CNA2008101180186A CN200810118018A CN101325478A CN 101325478 A CN101325478 A CN 101325478A CN A2008101180186 A CNA2008101180186 A CN A2008101180186A CN 200810118018 A CN200810118018 A CN 200810118018A CN 101325478 A CN101325478 A CN 101325478A
- Authority
- CN
- China
- Prior art keywords
- data
- terminal
- recording section
- time
- synchronous
- 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 Transfer Between Computers (AREA)
Abstract
The invention discloses a data synchronizing method for synchronization backup of data of a first terminal to a second terminal. The method includes the following steps: storing the data of the first terminal as a format including a data information part and a data synchronization recording part; obtaining operating data queue including data to be synchronized by comparing the data information part and the data synchronization recording part of the first terminal data; transmitting the data to be synchronized to the second terminal; judging whether the synchronization is successful according to the reversion information of the second terminal, and updating the data synchronization recording part if the synchronization is successful, otherwise not updating the data synchronization recording part. The invention discloses a data synchronizing system that can implement the method.
Description
Technical field
The present invention relates to a kind of method of data synchronization and system, particularly a kind of method and system of between first terminal and second terminal, carrying out data sync.
Background technology
Along with fast development of information technology, in the people's work life process, produced in a large number and carried out the canned data data by electronic equipment.And because the loss of data phenomenon that a variety of causes such as faulty operation, device damage, device upgrade cause happens occasionally, therefore, how effectively preserving the important electron information material becomes the problem that presses for solution.
Simultaneous techniques is the effective technology that addresses this problem.The major technique means that it adopts are that data sync is kept at two terminals, and in a number formulary according to the data of changing the opposing party synchronously after changing and being preserved.Existing data sync realizes in the following manner: at first, send terminal and send request to receiving terminal, to start simultaneous session.In response to this request, receiving terminal is carried out checking and is handled to determine whether that allowing to send terminal conducts interviews.If finish checking, send terminal and then treat to carry out after synchronous total data, receiving terminal receive data corresponding backup operation (comprising increase, renewal or the deletion of data) to the receiving terminal transmission, then operating result is returned to the transmission terminal.More than described the ordinary circumstance of simultaneous operation, still, in synchronizing process,, may cause the non-normal termination of simultaneous session owing to inside or external environmental factor (for example the data transmission network problem or the system failure).In this case, then must in the further Synchronous Processing after fault is got rid of, transmit all data once more, be included in the previous Synchronous Processing and sending successful data in synchronization between terminal and the receiving terminal.The lock in time that this has prolonged between receiving terminal and the transmission terminal, may produce the network over loading that causes by reprocessing simultaneously.
Publication number is that the Chinese patent application of CN 1681248A discloses a solution at above problem.According to the disclosed method for synchronous of this patent application, before beginning synchronously for treating that the data in synchronization item distributes ordinal number in certain sequence, and monitoring is treated data in synchronization item sum and is sent the number of having finished the data in synchronization item between terminal and the receiving terminal in synchronizing process, if simultaneous session is by non-normal termination in the data synchronization process, the ordinal number of the data item that is transmitting when then storage stops.In conjunction with above parameter, when re-executing data sync, the data item that is transmitting in the time of can be from non-normal termination continues to send data to receiving terminal.
The weak point of above method is, in the data sync of carrying out again, can only continue to transmit point of interruption data afterwards.In fact, in the process of data sync, other abnormal conditions except the simultaneous session non-normal termination may appear also.For example, the situation of a certain item number according to synchronization failure also may appear under the situation that simultaneous session does not stop, be receiving terminal for sending the answer message that synchrodata that terminal sends provides synchronization failure, perhaps behind the simultaneous session non-normal termination to begin synchronously before next time the user for last time successful data in synchronization change or the like once more.Above-mentioned technology obviously can not solve the data that caused by above abnormal conditions and omit problem.
Publication number is that the Chinese patent application of CN 101075864A discloses another kind of data sync and processing method.According to this method, it in data synchronization process the data allocations identify label, it is by sending that terminal provides or provided by receiving terminal that the newly-built flag bit that is comprised in this identify label is used to distinguish identify label, and the action type field that is comprised is used to distinguish these data to be data to be updated or to treat deleted data.Like this,, stab the modification time that whether is later than receiving terminal in conjunction with the modification time that relatively sends terminal and stab, can learn the synchronous situation that sends the every data of terminal, thereby realize the accurate synchronization of data by investigating this newly-built flag bit, action type field.
But, in the deterministic process of this method, need in conjunction with a plurality of parameters that send terminal and receiving terminal, take a plurality of steps to carry out the judgement of data sync state, so processing procedure being comparatively complicated, consume system resources is more.
Summary of the invention
For addressing the above problem, the objective of the invention is to propose a kind of method and system that is used for data sync, so that can identify the synchronous regime of data and judge and the synchronizing process of data is controlled, thereby realize the accurate synchronization of data by simple mode.
For realizing above purpose, the invention provides a kind of method that is used for the data sync of first terminal is backuped to the data sync of second terminal, may further comprise the steps: with the storage of described first terminal is the form that comprises data message part and data sync recording section; Described data message part by more described first terminal data and data sync recording section obtain and comprise the operating data formation for the treatment of synchrodata; To the described synchrodata for the treatment of of described second terminal transmission; Whether the return information judgment data according to described second terminal is successful synchronously; And if described data sync recording section is then upgraded in success synchronously, otherwise then do not upgrade described data sync recording section.
Preferably, described data message comprises that partly data directory, data content and user change the time of data for the last time; Described data sync recording section comprises the last successful lock in time of data directory and data, and the described data message partial data index of wherein same item number certificate is identical with the data directory of described data sync recording section.
Preferably, the described step of obtaining the operating data formation further may further comprise the steps: whether judgment data has data message part and data sync recording section simultaneously, if data only have the data message part and do not have the data sync recording section, then this item number certificate is not synchronous as yet newly-increased data; If data only have the data sync recording section and do not have the data message part, then this item number certificate is not synchronous as yet deleted data; If data have data message part and data sync recording section simultaneously, then whether the last data change time of judgment data information portion branch record is later than the last successful lock in time of data sync recording portion branch record, if, then this item number certificate is as yet not synchronous modification data, if not, then this item number certificate is successful data in synchronization.
Preferably, the step of upgrading described data sync recording section further comprises: the return information of described second terminal of receiving when described first terminal represent described newly-increased data in second terminal by success synchronously the time, described first terminal is that data increase the data sync record, and the time that will receive the described second terminal return information is as the last successful lock in time in the data sync record.
Preferably, the step of upgrading described data sync recording section further comprises: the return information of described second terminal of receiving when described first terminal represent described deleted data in second terminal by success synchronously the time, described first terminal will be deleted described data synchronization recording section.
Preferably, the step of upgrading described data sync recording section further comprises: the return information of described second terminal of receiving when described first terminal represent described modification data in second terminal by success synchronously the time, described first terminal is revised as the last successful lock in time in the data sync recording section of described data the time of receiving the described second terminal return information.
The present invention also provides a kind of data synchronous system that is used for the data sync of first terminal is backuped to second terminal, comprise: synchronization control module, the storage that is used for described first terminal is the form that comprises data message part and data sync recording section, data message part by more described first terminal data and data sync recording section obtain and comprise the operating data formation for the treatment of synchrodata, and it is whether successful synchronously according to the return information judgment data of described second terminal, if described data sync recording section is then upgraded in success synchronously, otherwise does not then upgrade described data sync recording section; And data transmission module, be used for to the described synchrodata for the treatment of of described second terminal transmission.
Preferably, described system further comprises data management module, be used for user data is managed, the user can by this module to data increase, operation such as deletion and modification.
Preferably, described system further comprises data encapsulation/parsing module, is used for the described synchrodata for the treatment of is encapsulated or resolves.
Preferably, described synchronization control module is carried out following operation when obtaining described operating data formation: whether judgment data has data message partly and the data sync recording section simultaneously, if data only have data message part and do not have the data sync recording section, then with this item number according to put into described operating data formation as not synchronous as yet newly-increased data; If data only have the data sync recording section and do not have the data message part, then with this item number according to put into described operating data formation as not synchronous as yet deleted data; If data have data message part and data sync recording section simultaneously, then whether the last data change time of judgment data information portion branch record is later than the last successful lock in time of data sync recording portion branch record, if, then with this item number according to putting into described operating data formation as not synchronous as yet modification data.
Preferably, described synchronization control module is carried out following operation when upgrading described data sync recording section: when described first terminal return information that receive, described second terminal represents that described newly-increased data are when second terminal is synchronous by success, described first terminal is that data increase the data sync record, and the time that will receive the described second terminal return information is as the last successful lock in time in the data sync record; Represent described deleted data when second terminal is synchronous by success when described first terminal return information that receive, described second terminal, described first terminal will be deleted described data synchronization recording section; Represent described modification data when second terminal is synchronous by success when described first terminal return information that receive, described second terminal, described first terminal is revised as the last successful lock in time in the data sync recording section of described data the time of receiving the described second terminal return information.
When first terminal is a portable terminal, and the transmission of data because the disposal ability of portable terminal is limited, takies less system resource when being undertaken by mobile communications network when therefore especially needing Synchronous Processing.Therefore, method for synchronous of the present invention and system are particularly suitable for using in the data synchronization process of portable terminal.
Description of drawings
Fig. 1 is the flow chart according to the method for data synchronization of a preferred embodiment of the present invention; And
Fig. 2 is the schematic diagram according to the data synchronous system of a preferred embodiment of the present invention.
Embodiment
In order to make the purpose, technical solutions and advantages of the present invention clearer, in conjunction with the preferred embodiments of the invention system and method for the present invention is described in further detail hereinafter with reference to accompanying drawing.
In brief, data synchronization is exactly that the data that send terminal and receiving terminal are consistent.In actual applications, comparatively commonly between the client and server end, carry out data synchronization.For the sake of simplicity, hereinafter will be with client as sending terminal, server end is that example describes as receiving terminal.But it will be appreciated by persons skilled in the art that at server end as sending terminal, client is as using method and system of the present invention equally under the situation of receiving terminal.Similarly, described transmission terminal and receiving terminal also can be other-end, for example two personal computers are carried out data synchronization as sending terminal and receiving terminal respectively.
In addition, according to one embodiment of the invention, described client can be portable terminal, for example mobile phone or PDA (Personal Digital Assistant, personal digital assistant).Utilize method of the present invention, can realize data sync between portable terminal and the server by mobile communications network.
As previously mentioned, in the data synchronization process, various abnormal conditions may occur, the user changed or the like for successful data in synchronization the non-normal termination, receiving terminal that comprises the simultaneous session that causes owing to the communication network reason once more to begin before synchronously next time after synchrodata that terminal sends provided the answer message of synchronization failure or simultaneous session non-normal termination for sending.At above problem, the present invention has adopted the treatment mechanism of in synchronizing process mark and the every data sync state of real time modifying.Concrete grammar is for to come the every data synchronization state of mark (promptly by defining some variablees in synchronizing process, successful data in synchronization information and data in synchronization information not as yet), and according to the next corresponding change data synchronization status indication of the operation acknowledge information of every item number certificate, further to use in the synchronizing process.By adopting above-mentioned treatment mechanism, can under the situation of at utmost avoiding data to repeat to transmit, guarantee that user data can not go out active or omission because of above-mentioned abnormal conditions in synchronizing process.
According to a preferred embodiment of the invention, change time by definition of data and realize the record of data sync state lock in time.Specifically, pending synchronous user data (UserData) being stored with the data structure shown in the table 1, is that every item number writes down (DataSyncLog) according to increasing data sync simultaneously, and the data structure of data sync record is as shown in table 2.
Thus, the every item number stored of client is according to generally including two parts content: data message part and data sync recording section.As shown in table 1, data message partly comprises the time of changing this item number certificate with every item number according to unique corresponding data directory, data content and user for the last time; Data sync recording section (as shown in table 2) comprises the data directory corresponding to this item number certificate, and the last successful lock in time of this item number certificate.Wherein the change that the user carried out comprises increase, modification or deleted data.Need to prove that every item number is according to the unique data directory of correspondence, promptly identical according to, the data index value in the table 1 with data index value in the table 2 for same item number.
Table 1: the data structure of data message part (UserData)
| Domain name | Implication |
| dataId | Data directory |
| data | Data content |
| dataTime | The last data change time |
Table 2: the data structure of data sync recording section (DataSyncLog)
| Domain name | Implication |
| dataId | Data directory |
| syncDate | Last successful lock in time |
By adopting above mechanism, can learn which data item is synchronous in client and server end success.Below will describe its specific implementation method.
According to the present invention, in data synchronization process, the synchronous situation that adopts the variable information immediate updating to come identification data.With this preferred embodiment is example, if the user increases by an item number certificate in client, then this item number comprises in these clauses and subclauses that according to being stored in client as clauses and subclauses with the data structure shown in the table 1 data directory, data content and user increase the concrete time of this item number certificate.When these newly-increased data at server end by success synchronously the time, server end is with the return data synchronous answer message of success, after waiting to receive this answer message, the data sync record that client has data structure shown in the table 2 for this item number according to increase, and will receive the last successful lock in time of the time of server end answer message as this item number certificate.
If the user makes amendment to a certain item number certificate in client, then partly replace former data content with new data content at the data message of this item number certificate, upgrade the concrete time of this item number certificate of user's modification simultaneously.When the data of this modification at server end by success synchronously the time, server end is with the return data synchronous answer message of success, after waiting to receive this answer message, client will be revised as the time of receiving server end answer message the last successful lock in time in the data sync recording section of this item number certificate.
If the user deletes a certain item number certificate in client, then delete the data message part of this item number certificate.When the deletion of this item number certificate at server end by success synchronously the time, the answer message that server end is successfully deleted return data, wait to receive this answer message after, client will be deleted the synchronous recording part of this item number certificate.
Like this, when needs carried out data sync, client can be learnt as yet not in server end success data in synchronization by the data of being stored are retrieved.Described retrieval comprises the newly-increased data of retrieval, retrieval modification data and retrieval deleted data.
Retrieval is newly-increased/deleted data: whether exist in the client retrieves data sync recording section with the data message part in the corresponding clauses and subclauses of each clauses and subclauses (Item).If find to exist by retrieval only to be contained in the data message part and not to be included in clauses and subclauses in the data sync recording section, then with this item number according to as not synchronous as yet newly-increased storage in treating isochronous queue.If find to exist by retrieval only to be contained in the data sync recording section and not to be included in clauses and subclauses in the data message part, then this item number treated in the isochronous queue according to being stored in as not synchronous as yet need deleted data.
Data are revised in retrieval: for the data that are present in simultaneously in data message part and the data sync recording section, client compares the last data change time (being recorded in the data message part) of each data with last success lock in time (being recorded in the data sync recording section), if the last data change time of a certain data is later than last successful lock in time, then with this item number according to as not synchronous as yet modification storage in treating isochronous queue.Obviously, the data change time, need not to carry out subsynchronous to it in being about to the simultaneous operation of carrying out corresponding to successful data in synchronization early than the clauses and subclauses of last successful lock in time again for the last time.
Can realize that by above data sync record control method data are in the backed up in synchronization process safe.That is, the data of the synchronous increase of success, data sync record of then corresponding increase; The data of the synchronous modification of success are then upgraded the data sync record of this item number according to correspondence; The data of the synchronous entry deletion of success are then deleted the data sync record of this item number according to correspondence.For an item number certificate, only under the situation of receiving the synchronous return information of success that server end sends, just can upgrade data sync record corresponding to this item number certificate, if client is not received the return information of server end, perhaps return information is represented synchronization failure, will can not upgrade the data sync record.When carrying out simultaneous operation next time, all will be retrieved out by successful data in synchronization as yet and proceed synchronous renewal, thereby guarantee the safety of user data.According to technical scheme of the present invention, the judgement that the synchronous regime of specified data only needs to carry out limited number of time in client can be finished, and deterministic process is very simple, and need not to communicate with server end in deterministic process, can finish in that client is single-ended.
In addition, because the transmittability of network is limited,, once transmit all data with being not easy when treating data in synchronization more for a long time.According to one embodiment of the invention, can will data be transmitted be divided into a plurality of parts according to the transfer capability of network and transmit respectively.Preferably, can use the SyncML agreement as synchronous standard agreement, according to the SyncML agreement to the user data transmission of packing.When the compressed package that will comprise a plurality of data when client is sent to server end, server end is at first resolved this compressed package, respectively a plurality of data are wherein carried out synchronously then, will and return to client for the packing of the return information of each bar data after finishing synchronously.Client decompresses to the return information compressed package, carries out corresponding operating subsequently.
Describe according to the data transferring method preferred embodiment of the invention, that be used for data sync between client and the server end hereinafter with reference to Fig. 1.
At first, at step S101, user end to server is initiated the data sync initialization request, starts simultaneous session thus.In response to this request, server is carried out checking and is handled to determine whether to allow the client-access server.
If finish checking, then at step S102, client is obtained the operating data formation by retrieval.Particularly, client compares with the data sync recording section the data message of every data part, will only have the data message part and the data that do not have a data sync recording section as not synchronous as yet newly-increased storage in treating isochronous queue; To only have the data sync recording section and do not have the data message partial data and be stored in as not synchronous as yet deleted data and treat in the isochronous queue; The data that are later than last successful lock in time the last data change time as not synchronous as yet modification storage in treating isochronous queue.
When search complete and obtain the operating data formation after, at step S103, client judges whether to exist treats data in synchronization.In fact, in actual application, the data that may have a current storage of client have all successfully backuped to the situations of server end in last once simultaneous operation.In this case, the synchrodata for the treatment of that is comprised in the operating data formation by step S102 acquisition may be zero, and can stop the simultaneous session process this moment.Therefore, if judging not exist at step S103 treats synchrodata, EP (end of program) then, otherwise, then enter step S104.
At step S104, the user end to server end transmits treats data in synchronization.When data are divided into a plurality of parts and transmit, at each part execution in step S103-S107 respectively.
At step S105, whether client is successful synchronously at server end according to the feedback judgment data of server end.At the data that client sent, server end will carry out synchronously one by one, that is, utilize the data item update that is received before to be stored in the data of server end.Because the data directory that every data are all corresponding unique, so server end can be realized the renewal of data easily correspondingly.At the synchronous situation of every item number certificate, server end will send return information to client.Whether client can successful synchronously according to the answer judgment data of server end.Under the situation that can not receive the server end return information, will be defaulted as synchronization failure.
If the data sync recording section corresponding to described data is then upgraded in data sync success, client in step S106, the data that will send in step S107 remove from treat the synchrodata formation then.Next, program will be returned step S103, treat data in synchronization to judge whether also to exist, if having, then treat synchrodata execution in step S103-S107 at next part; If total data all finishes synchronously (promptly in step S103 judge learn not exist treat data in synchronization), EP (end of program) then.
If in step S105, judge some failure of data synchronization, then do not upgrade data sync recording section, directly enter step S107, the data that sent are removed from treat the synchrodata formation corresponding to these data, return step S103 then, continue to handle next part and treat synchrodata.Treat total data finish synchronously the back EP (end of program).By above step as can be seen, in data synchronization process of the present invention, can not cause the termination of whole synchronizing process owing to some data synchronization failure.When the situation of a certain failure of data synchronization occurring, this item number will be skipped according to proceeding the synchronous of follow-up data by system.For the data of synchronization failure, will in synchronizing process next time, be retrieved out and carry out again synchronously.
Need to prove that the step (step S107) that the data that sent are removed also can judge whether that synchronous success (being step S105) carries out before from treat the synchrodata formation.
According to said method of the present invention, can be in synchronizing process the every data synchronization state of real-time mark, when guaranteeing next simultaneous operation thus, all will be retrieved out by successful data in synchronization as yet and proceed synchronous renewal, and successful data in synchronization can be by not subsynchronous again, thereby fully avoid the transmission that repeats of data when guaranteeing secure user data.
Hereinafter with reference to Fig. 2 to according to the preferred embodiment of the invention, be used for that data synchronization system describes between client and the server end.
As shown in Figure 2, data synchronous system 100 according to the present invention comprises data management module 10, synchronization control module 20, data encapsulation/parsing module 30 and data transmission module 40.Wherein, data management module 10 module for being used for user data is managed, the user can by this module to data increase, operations such as deletion and modification.Synchronization control module 20 is the Logic control module of data sync transmission, be used for controlling the execution of each step of synchronizing process, promptly, obtain the operating data formation according to data mode information, according to receiving terminal feedback information judgment data whether synchronously successfully, and according to judged result to upgrade or do not upgrade described data mode information.Data encapsulation/parsing module 30 is used for being responsible for the encapsulation and the parsing of synchrodata, and the standard agreement of encapsulation can adopt the SyncML agreement.Data transmission module 40 is used for data are transmitted, and receives replying from server end.
Can learn in conjunction with description above about the specific implementation of each functions of modules, not repeat them here for the inventive method.Need to prove that system shown in Figure 2 only is a preferred embodiment of the present invention, certain module wherein can omit according to actual needs.According to another embodiment of the invention, under the situation of encapsulation that do not need data are packed, can omitted data encapsulation/parsing module 30.
Though below invention has been described in conjunction with the preferred embodiments, but it should be appreciated by those skilled in the art, method and system of the present invention is not limited to the embodiment described in the embodiment, under the situation that does not deviate from the spirit and scope of the invention that limits by appended claims, can make various modifications, increase and replacement to the present invention.
Claims (18)
1. the method for a data sync is used for the data sync of first terminal is backuped to second terminal, may further comprise the steps:
With the storage of described first terminal is the form that comprises data message part and data sync recording section;
Described data message part by more described first terminal data and data sync recording section obtain and comprise the operating data formation for the treatment of synchrodata;
To the described synchrodata for the treatment of of described second terminal transmission;
Whether the return information judgment data according to described second terminal is successful synchronously; And
If described data sync recording section is then upgraded in success synchronously, otherwise does not then upgrade described data sync recording section.
2. the method for claim 1, wherein after obtaining described operating data formation, further judge whether to exist and treat synchrodata, if then transmit the described synchrodata for the treatment of.
3. any described method in the claim as described above wherein, behind DTD, will be transmitted data and remove from treat the synchrodata formation.
4. any described method in the claim as described above, wherein, described data message comprises that partly data directory, data content and user change the time of data for the last time; Described data sync recording section comprises the last successful lock in time of data directory and data, and the described data message partial data index of wherein same item number certificate is identical with the data directory of described data sync recording section.
5. any described method in the claim as described above, wherein, described operating data formation comprises not synchronous as yet newly-increased data, not synchronous deleted data and not synchronous as yet modification data as yet.
6. method as claimed in claim 5, wherein, the described step of obtaining the operating data formation further may further comprise the steps:
Whether judgment data has data message part and data sync recording section simultaneously, if data only have the data message part and do not have the data sync recording section, then this item number certificate is not synchronous as yet newly-increased data; If data only have the data sync recording section and do not have the data message part, then this item number certificate is not synchronous as yet deleted data;
If data have data message part and data sync recording section simultaneously, then whether the last data change time of judgment data information portion branch record is later than the last successful lock in time of data sync recording portion branch record, if, then this item number certificate is as yet not synchronous modification data, if not, then this item number certificate is successful data in synchronization.
7. any described method in the claim as described above, wherein, the step of upgrading described data sync recording section further comprises: the return information of described second terminal of receiving when described first terminal represent described newly-increased data in second terminal by success synchronously the time, described first terminal is that data increase the data sync record, and the time that will receive the described second terminal return information is as the last successful lock in time in the data sync record.
8. any described method in the claim as described above, wherein, the step of upgrading described data sync recording section further comprises: the return information of described second terminal of receiving when described first terminal represent described deleted data in second terminal by success synchronously the time, described first terminal will be deleted described data synchronization recording section.
9. any described method in the claim as described above, wherein, the step of upgrading described data sync recording section further comprises: the return information of described second terminal of receiving when described first terminal represent described modification data in second terminal by success synchronously the time, described first terminal is revised as the last successful lock in time in the data sync recording section of described data the time of receiving the described second terminal return information.
10. any described method in the claim as described above, wherein, represent that at the return information of described second terminal that described first terminal is received described modification data are under the situation of second terminal synchronizes failure, perhaps described first terminal is not received under the situation of return information of described second terminal, will do not upgraded described data sync recording section.
11. any described method in the claim as described above, wherein, described operating data formation can be divided into a plurality of parts, and each part is carried out respectively synchronously.
12. any described method in the claim as described above, wherein, described first terminal is a portable terminal, and described transfer of data is undertaken by mobile communications network.
13. a data synchronous system is used for the data sync of first terminal is backuped to second terminal, comprising:
Synchronization control module (20), the storage that is used for described first terminal is the form that comprises data message part and data sync recording section, data message part by more described first terminal data and data sync recording section obtain and comprise the operating data formation for the treatment of synchrodata, and it is whether successful synchronously according to the return information judgment data of described second terminal, if described data sync recording section is then upgraded in success synchronously, otherwise does not then upgrade described data sync recording section; And
Data transmission module (40) is used for to the described synchrodata for the treatment of of described second terminal transmission.
14. system as claimed in claim 13 further comprises:
Data management module (10) is used for user data is managed, the user can by this module to data increase, operation such as deletion and modification.
15., further comprise as claim 13 or 14 described systems:
Data encapsulation/parsing module (30) is used for the described synchrodata for the treatment of is encapsulated or resolves.
16. any described system in the claim as described above, wherein, described synchronization control module (20) is carried out following the operation when obtaining described operating data formation:
Whether judgment data has data message part and data sync recording section simultaneously, if data only have data message partly and do not have a data sync recording section, then with this item number according to put into described operating data formation as not synchronous as yet newly-increased data; If data only have the data sync recording section and do not have the data message part, then with this item number according to put into described operating data formation as not synchronous as yet deleted data;
If data have data message part and data sync recording section simultaneously, then whether the last data change time of judgment data information portion branch record is later than the last successful lock in time of data sync recording portion branch record, if, then with this item number according to putting into described operating data formation as not synchronous as yet modification data.
17. any described system in the claim as described above, wherein, described synchronization control module (20) is carried out following the operation when upgrading described data sync recording section:
When described first terminal return information that receive, described second terminal represents that described newly-increased data are when second terminal is synchronous by success, described first terminal is that data increase the data sync record, and the time that will receive the described second terminal return information is as the last successful lock in time in the data sync record;
Represent described deleted data when second terminal is synchronous by success when described first terminal return information that receive, described second terminal, described first terminal will be deleted described data synchronization recording section;
Represent described modification data when second terminal is synchronous by success when described first terminal return information that receive, described second terminal, described first terminal is revised as the last successful lock in time in the data sync recording section of described data the time of receiving the described second terminal return information.
18. any described system in the claim as described above, wherein, described first terminal is a portable terminal, and described transfer of data is undertaken by mobile communications network.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNA2008101180186A CN101325478A (en) | 2008-08-06 | 2008-08-06 | Method and system for data synchronization |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNA2008101180186A CN101325478A (en) | 2008-08-06 | 2008-08-06 | Method and system for data synchronization |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN101325478A true CN101325478A (en) | 2008-12-17 |
Family
ID=40188833
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CNA2008101180186A Pending CN101325478A (en) | 2008-08-06 | 2008-08-06 | Method and system for data synchronization |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN101325478A (en) |
Cited By (16)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102469062A (en) * | 2010-10-29 | 2012-05-23 | 北大方正集团有限公司 | Data distributing method and device |
| CN102780837A (en) * | 2012-07-13 | 2012-11-14 | 成都东方盛行电子有限责任公司 | Method for intelligently synchronizing generic edition platform cloud disc file and media resource system |
| CN103136200A (en) * | 2011-11-22 | 2013-06-05 | 中兴通讯股份有限公司 | Data updating information obtaining method and device and data synchronization method and device |
| CN103338124A (en) * | 2013-07-12 | 2013-10-02 | 华为技术有限公司 | Abnormal chain scission processing method, device and system |
| CN103581879A (en) * | 2012-07-31 | 2014-02-12 | 中国电信股份有限公司 | Method and system for performing data transmission between terminal and user identification card |
| CN103685361A (en) * | 2012-09-06 | 2014-03-26 | 中国移动通信集团公司 | Data synchronization method and system, and terminal |
| CN104092673A (en) * | 2014-06-27 | 2014-10-08 | 中国人民解放军第二军医大学 | System and method for achieving safe one-way data transmission between networks |
| CN104917819A (en) * | 2015-04-29 | 2015-09-16 | 努比亚技术有限公司 | Method and system for achieving data synchronization |
| CN105339892A (en) * | 2013-06-18 | 2016-02-17 | 汤姆逊许可公司 | Local network and method of updating a device in a local network |
| CN105373435A (en) * | 2015-11-16 | 2016-03-02 | 深圳还是威健康科技有限公司 | Data synchronous processing method and terminal |
| CN105407146A (en) * | 2015-10-27 | 2016-03-16 | 成都艾克尔特医疗科技有限公司 | Data synchronization method from wristband to APP to server |
| CN105677885A (en) * | 2016-01-14 | 2016-06-15 | 大连陆海科技股份有限公司 | Receiving and sending device and method and synchronizing system for achieving shipping industry data synchronization |
| CN105827699A (en) * | 2016-03-16 | 2016-08-03 | 心动网络股份有限公司 | Data synchronization method |
| CN107145572A (en) * | 2017-05-05 | 2017-09-08 | 广东欧珀移动通信有限公司 | Data processing method, device, computer equipment and storage medium |
| CN108846045A (en) * | 2018-05-30 | 2018-11-20 | 四川斐讯信息技术有限公司 | A kind of storage method and system of Intelligent water cup drinking-water data |
| CN110365797A (en) * | 2016-06-03 | 2019-10-22 | 青岛海信移动通信技术股份有限公司 | A kind of synchronous method and device of contact information |
-
2008
- 2008-08-06 CN CNA2008101180186A patent/CN101325478A/en active Pending
Cited By (31)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102469062B (en) * | 2010-10-29 | 2014-05-07 | 北大方正集团有限公司 | Data distributing method and device |
| CN102469062A (en) * | 2010-10-29 | 2012-05-23 | 北大方正集团有限公司 | Data distributing method and device |
| CN103136200B (en) * | 2011-11-22 | 2018-02-02 | 中兴通讯股份有限公司 | Data fresh information acquisition methods, device and method of data synchronization, device |
| CN103136200A (en) * | 2011-11-22 | 2013-06-05 | 中兴通讯股份有限公司 | Data updating information obtaining method and device and data synchronization method and device |
| CN102780837B (en) * | 2012-07-13 | 2015-11-11 | 成都东方盛行电子有限责任公司 | The method of general editing platform cloud dish file and media resource system intelligent synchronization |
| CN102780837A (en) * | 2012-07-13 | 2012-11-14 | 成都东方盛行电子有限责任公司 | Method for intelligently synchronizing generic edition platform cloud disc file and media resource system |
| CN103581879A (en) * | 2012-07-31 | 2014-02-12 | 中国电信股份有限公司 | Method and system for performing data transmission between terminal and user identification card |
| CN103685361A (en) * | 2012-09-06 | 2014-03-26 | 中国移动通信集团公司 | Data synchronization method and system, and terminal |
| CN103685361B (en) * | 2012-09-06 | 2017-03-22 | 中国移动通信集团公司 | Data synchronization method and system, and terminal |
| CN105339892A (en) * | 2013-06-18 | 2016-02-17 | 汤姆逊许可公司 | Local network and method of updating a device in a local network |
| CN103338124A (en) * | 2013-07-12 | 2013-10-02 | 华为技术有限公司 | Abnormal chain scission processing method, device and system |
| CN103338124B (en) * | 2013-07-12 | 2016-12-28 | 华为技术有限公司 | The processing method of abnormal chain scission, device and system |
| CN104092673A (en) * | 2014-06-27 | 2014-10-08 | 中国人民解放军第二军医大学 | System and method for achieving safe one-way data transmission between networks |
| CN104917819B (en) * | 2015-04-29 | 2019-01-01 | 努比亚技术有限公司 | A kind of method and system for realizing that data are synchronous |
| CN104917819A (en) * | 2015-04-29 | 2015-09-16 | 努比亚技术有限公司 | Method and system for achieving data synchronization |
| CN105407146B (en) * | 2015-10-27 | 2018-07-20 | 成都云卫康医疗科技有限公司 | It is a kind of from bracelet to APP again to the method for data synchronization of server |
| CN105407146A (en) * | 2015-10-27 | 2016-03-16 | 成都艾克尔特医疗科技有限公司 | Data synchronization method from wristband to APP to server |
| CN105373435B (en) * | 2015-11-16 | 2019-09-20 | 深圳市元征科技股份有限公司 | A kind of method and terminal of data synchronization processing |
| CN105373435A (en) * | 2015-11-16 | 2016-03-02 | 深圳还是威健康科技有限公司 | Data synchronous processing method and terminal |
| CN105677885A (en) * | 2016-01-14 | 2016-06-15 | 大连陆海科技股份有限公司 | Receiving and sending device and method and synchronizing system for achieving shipping industry data synchronization |
| CN105827699A (en) * | 2016-03-16 | 2016-08-03 | 心动网络股份有限公司 | Data synchronization method |
| CN110460660A (en) * | 2016-06-03 | 2019-11-15 | 青岛海信移动通信技术股份有限公司 | A kind of synchronous method and device of contact information |
| CN110365797A (en) * | 2016-06-03 | 2019-10-22 | 青岛海信移动通信技术股份有限公司 | A kind of synchronous method and device of contact information |
| CN110474972A (en) * | 2016-06-03 | 2019-11-19 | 青岛海信移动通信技术股份有限公司 | A kind of synchronous method and device of contact information |
| CN110365797B (en) * | 2016-06-03 | 2022-03-18 | 青岛海信移动通信技术股份有限公司 | Method and device for synchronizing contact information |
| CN110460660B (en) * | 2016-06-03 | 2022-05-10 | 青岛海信移动通信技术股份有限公司 | Method and device for synchronizing contact information |
| CN110474972B (en) * | 2016-06-03 | 2022-07-08 | 青岛海信移动通信技术股份有限公司 | Method and device for synchronizing contact information |
| CN107145572A (en) * | 2017-05-05 | 2017-09-08 | 广东欧珀移动通信有限公司 | Data processing method, device, computer equipment and storage medium |
| CN107145572B (en) * | 2017-05-05 | 2020-12-18 | Oppo广东移动通信有限公司 | Data processing method and device, computer equipment and storage medium |
| CN108846045A (en) * | 2018-05-30 | 2018-11-20 | 四川斐讯信息技术有限公司 | A kind of storage method and system of Intelligent water cup drinking-water data |
| CN108846045B (en) * | 2018-05-30 | 2022-10-18 | 杭州吉吉知识产权运营有限公司 | Storage method and system for drinking water data of intelligent water cup |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN101325478A (en) | Method and system for data synchronization | |
| CN100472445C (en) | Configuring load application method and system of communication apparatus | |
| CN102355426B (en) | Method for transmitting off-line file and system | |
| JP4829316B2 (en) | Method, apparatus, and system for synchronizing data in response to an interrupted synchronization process | |
| CN101754221B (en) | Data transmission method between heterogeneous systems and data transmission system | |
| CN103297459B (en) | The synchronization system of application configuration information, access server, client and method | |
| CN111190747A (en) | Message loss detection method and device for message queue | |
| CN104468521B (en) | Online moving method, device and system | |
| CN100403696C (en) | Storage management method and system for realizing data collocation between network element and network management | |
| CN102263667B (en) | Network management system and network management processing method | |
| KR20080068110A (en) | A method for processing data synchronization and client terminal, server and data synchronization system thereof | |
| CN103440142A (en) | GPRS (General Packet Radio Service)-based remote upgrade and dynamic loading method | |
| KR100728076B1 (en) | Method, device and system for synchronizing of data providing for the handling of an interrupted synchronization process | |
| CN106713391A (en) | Session information sharing method and sharing system | |
| CN103457802A (en) | Information transmission system and method | |
| CN103581846B (en) | A kind of user's business card update method and system | |
| CN100512140C (en) | A method and device for controlling the configuration of configuration parameter set of the remote device | |
| CN104660616A (en) | Conversation remaining server side and conversation processing method thereof | |
| CN101388792A (en) | Single board plug-and-use processing method, device and telecommunication system | |
| CN108011870A (en) | A kind of remote software online upgrading information automatic identification management method | |
| CN101702732A (en) | Document synchronous method and document synchronous system | |
| CN104243483A (en) | Message processing method and message processing equipment | |
| CN110912766A (en) | Communication network multi-plane data consistency checking method | |
| CN115776175A (en) | Dispatching automation data acquisition method and system based on security access area | |
| CN102238036A (en) | User session backup handover method and system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C12 | Rejection of a patent application after its publication | ||
| RJ01 | Rejection of invention patent application after publication |
Open date: 20081217 |