CN1852137A - Method for realizing synchronization of client end data and server end data - Google Patents
Method for realizing synchronization of client end data and server end data Download PDFInfo
- Publication number
- CN1852137A CN1852137A CN 200510085054 CN200510085054A CN1852137A CN 1852137 A CN1852137 A CN 1852137A CN 200510085054 CN200510085054 CN 200510085054 CN 200510085054 A CN200510085054 A CN 200510085054A CN 1852137 A CN1852137 A CN 1852137A
- Authority
- CN
- China
- Prior art keywords
- data
- client
- identification information
- server end
- deletion
- 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 method sets up first created id information for first data at server end, and sets up second created id information for second data at client end. When carrying out synchronous operation, the method compares the first created id information with the second created id information; and if they are different, the method synchronizes the second data at client end with the first data at server end. Through adding data such as version numbers of records, types of operations, and version numbers of lists to create id information so as to raise efficiency of synchronizing data, improve operation experience at client end, and reduce interactive data quantity between client end and server. The method realizes synchronization scheme of combining partial synchronization and complete deletion.
Description
Technical field
The present invention relates to the communications field, relate in particular to a kind of method that realizes local data and server data sync.
Background technology
The Internet provides abundant service for people, such as the address book management, and the chat record management.The characteristics of these services are based on client/server section (C/S) model, the user is by client and server interaction, client terminal quantity is huge, client needs to beam back data and handle request to server continually, performance requirement to server is very high, under the situation of low bandwidth or high latency, situation can be worsened, and the performance issue of generation may cause application availability and user's efficient to descend significantly.In order to improve the performance of client operation, current a lot of system has adopted in client deployment code and data, carries out and visit data in this locality, passes through local data cache, minimizing to the data in server amount, and then improves the performance and the practicality of system from client transmissions.
Because all there are data in client or server, it is synchronous that system need carry out data necessary.Such as: in chat tool, the user carries out address book in client and safeguards, add associated person information, revise contact number, delete the contact person, revise the data of client behind system's modification server data again, because these operations may be carried out in a plurality of clients, the data of each client and server data may be inconsistent, and the data that cause client operation are not the problems of latest data.
The scheme of prior art 1 is to download synchronization scenario fully, and the user at first downloads all data of this user the correlation table from server before client is operated local data base at every turn, finish synchronously, carries out attended operation then.It is general bigger that but the shortcoming of this scheme is the data volume of tables of data, frequently complete data download, and efficient is low, has a strong impact on server performance, has with the target of the raising performance of local data scheme and conflicts, and is unavailable in the big system of data volume.
The scheme of prior art 2 is to be responsible for Synchronous Processing by Database Systems, and which table of system definition needs to get final product synchronously, and the row level of database and row level detect and guarantee synchronously.But this scheme needs client to possess local data base, and the operational outfit of client is required than higher.
Summary of the invention
The invention provides a kind of method that realizes client data and server end data sync, exist client data and server end data to be difficult to synchronously in order to solve in the prior art, and client data and server end data sync scheme complicated problems comparatively.
The inventive method comprises:
A kind of client data and synchronous method of server end data of realizing, it is characterized in that, for being provided with first, server end first data generate identification information, for being provided with second, client second data generate identification information, when carrying out simultaneous operation, relatively first generate identification information and second and generate identification information, when both have when inequality sync client second data.
Described generation identification information is a versions of data number.
Described generation identification information is the last rise times of data.
Described generation identification information is the last simultaneous operation time.
Described sync client second data are for server end sends to client with packing data.
Described packing data form is extend markup language (XML) form.
Described first data and second data can have a plurality of respectively, corresponding a plurality of first generate identification information and a plurality of second generation identification information respectively.
It is inequality that the described first generation identification information and second generates identification information, and it is all inequality inequality with part to comprise that the first generation identification information and second generates identification information.
Described method, generate identification information and second and generate the identification information part when inequality when described first, before first data are not carried out the reality deletion, described sync client second data manipulation is second data that the only synchronous first generation identification information and second generates identification information part inequality.
Described method generates identification information and second and generates the identification information part when inequality when described first, and after first data were carried out reality deletion, described sync client second data manipulation was synchronous all client second data.
Described method generates identification information and second to generate identification information whole when inequality when described first, and described sync client second data manipulation is all client second data synchronously.
Described all client second data manipulations synchronously are after client is deleted local data, again Download Server end first data.
Described server end and client are by HTTP(Hypertext Transport Protocol), Simple Object Access Protocol (SOAP), session initiation protocol (SIP) or XML configuration access agreement protocol communications such as (XCAP).
Described method comprises that also described client initiates the step of synchronization request, carries second in the described synchronization request and generates identification information.
Described method comprises that also described server end receives the step of described synchronization request, and according to the second generation identification information that carries in the described synchronization request, makes comparisons with the first generation identification information.
Described generation identification information is with the form setting.
Described method, when the described first generation identification information was identical with the second generation identification information, server end returns to described client did not have the Data Update notice.
Described server end is provided with the first data manipulation type identification, identifies the content of the last operation of first data.
Described method during sync client second data, is carried out corresponding operation according to the last action type of first data.
Described method is during sync client second data, if the action type of first data is newly-increased, then judge in client whether first data exist, if exist, then at first deletion, newly-increased again first data, if there is no, then directly newly-increased first data.
Described method is during sync client second data, if the action type of first data is to revise, then judge in client whether first data exist, if exist, then at first deletion, and then newly-increased first data, if there is no, then newly-increased these first data.
Described method during sync client second data, if the action type of first data is deletions, then judges in client whether first data exist, if exist then deletion.
Described method, when carrying out the data deletion action, first data side only retouching operation be designated deletion sign, described first data of actual deletion.
Described method, the regular clear operation of server are designated first data of deletion sign, described first data of actual deletion.
A kind of client data and synchronous system of server end data of realizing comprises the client and server end, and described server end stores first data, described client stores have need with second data of server end data sync; It is characterized in that:
Described client is provided with the second processing logic unit, and this second Logical processing unit is initiated data synchronization request according to client second data mode to server end;
Described server end is provided with the first processing logic unit, and this first Logical processing unit receives data synchronization request, and described synchronization request is responded.
In the described synchronization request, carry the second generation information of client second data, the described first processing logic unit is according to the described second generation information, judge whether consistent with the first generation information of server end first data, if inconsistent, then the Control Server end carries out client data simultaneous operation.
Described client and server end are by HTTP(Hypertext Transport Protocol), Simple Object Access Protocol (SOAP), session initiation protocol (SIP) or XML configuration access agreement protocol communications such as (XCAP).
Beneficial effect of the present invention is as follows:
The present invention generates identification information by the data such as version number that increase the version number, action type and the data that write down, improved data synchronization efficiency, improved the operating experience of client, reduced the interaction data amount of client and server, realized that part is synchronous and deleted the synchronization scenario that combines fully.
Description of drawings
Fig. 1 is a schematic network structure of the present invention;
Fig. 2 is the initialized schematic flow sheet of the embodiment of the invention 1 local data;
Fig. 3 is the embodiment of the invention 2 client query operating process schematic diagrames;
Fig. 4 is the embodiment of the invention 3 newly-increased record schematic flow sheets;
Fig. 5 is the embodiment of the invention 4 amendment record schematic flow sheets;
Fig. 6 is the embodiment of the invention 5 deletion record schematic flow sheets.
Embodiment
Below in conjunction with Figure of description the specific embodiment of the invention is described.
In the communications field, how sync client end data and server end data, be the work of a complexity, the present invention is provided with the generation identification information respectively for client data and server end data, this generates identification information, write down the key element that has the rise time of these data, by this identification information, can make comparisons to client data and server end data, and judge according to result relatively whether client data is consistent with the server end data, be whether client data and server end data are synchronous,, then carry out the corresponding synchronous operation if asynchronous.
The generation identification information that is adopted among the present invention can be that the rise time of data stabs, and the version number of data, last simultaneous operation time etc. can embody the mark of data rise time.
When needs simultaneous operation, compare the generation identification information of client data and the generation identification information of server end, if both are identical, illustrate that client data and server end data have been synchronous, do not need to carry out again simultaneous operation, when both have when inequality, illustrate that client data is asynchronous with the server end data, difference to some extent on the rise time at this time should be as the criterion the sync client end data with the server end data.
Above-mentioned generation identification information, can be corresponding to data, also can be corresponding to a plurality of data, when client and server end data during more than one, the generation identification information of each data correspondence can be organized in the form, carry the generation identification information of all data with the form of a form or a file.
System configuration of the present invention is affixed one's name to relevant treatment logic and data as shown in Figure 1 in the client and server end.
Among the present invention program, be provided with the client process logical block in client, this client logic processing unit is initiated data synchronization request according to the client data state to server end.
Be provided with the server-side processes logical block at server end, this server end Logical processing unit receives the data synchronization request that the client process logical block sends, and described synchronization request is responded.
The client and server end adopts the HTTP/SOAP/SIP/XCAP agreement, initiatively initiates synchronization request by client, comprises the generation identification information of client data in the request.After server end receives this request, should generate identification information and server end data to client data and generate identification information and compare, if identical then return without any the notice of upgrading.If inequality, then inquire about the data of all different generation identification information correspondences, then the packing data of upgrading is become the XML form, send to client by protocol entity.
When the client and server end has several data respectively, when relatively generating identification information, just there is multiple comparative result:
1, the generation identification information of client data is all identical with the generation identification information of server end data, and this situation explanation client data is complete synchronous with the server end data, unnecessaryly carries out simultaneous operation again.
2, the generation identification information of client data is identical with the generation identification information part of server end data, part is different, this situation may be that client data has part to be and the server end data sync, a part is then asynchronous with the server end data in addition, at this moment needs client data is carried out simultaneous operation.
Operation under this kind situation also can be divided into following several:
A, a sync client end data generate those different data of identification information with the server end data, refuse simultaneous operation for generating the identical data of identification information, can save Internet resources like this;
B, all client datas synchronously can be after client be deleted local data, again Download Server end first data.
3, the generation identification information of client data is all different with the generation identification information of server end data, and this situation might be that client data is not for a long time done simultaneous operation, need carry out whole simultaneous operations to client data.
In the solution of the present invention, also a data action type sign is set, identifies the content of the last operation of server end data, when client is carried out data sync at server end, operate accordingly according to this data manipulation type identification, specifically can be as described below:
If the action type of server end data is newly-increased, then judge newly-increased data whether to exist in client, if exist, then at first deletion, newly-increased again these data, if there is no, then directly newly-increased these data.
If the action type of server end data is to revise, then judge in client whether these modification data exist, if exist, then at first deletion, and then newly-increased these modification data, if there is no, then newly-increased this revised data.
If the action type of server end data is deletions, then judge in client whether this deleted data exists, if exist then delete this data.
When carrying out the data deletion action, can only be that operation mark is revised as the deletion sign in the server end data side, unactual these data of deletion.The regular clear operation of server is designated the server end data of deletion sign, actual these data of deletion.
Call log and address book with certain system is example as client data and server end data below, carries out related description, and the data of client are shown in table (), wherein version number and last complete lock in time to generate identification information as data.
We make following regulation to version number:
Version number: be a unique identification, this sign can be the progressive whole number value, also can be concrete time value (YYYYMMDDHHMMSS), is a sign that increases progressively.
Record version this shop: be used for identifying each bar record.
Total version number: a kind of data of each user have a total version number, and total version number is more than or equal to certain record version this shop of the last user data of revising.When last operation is a deletion action, belong to greater than situation.
Table (one)
| The user | Call log version number | Call log last lock in time fully | Address book version number | Address book last lock in time fully | ... |
| AAA | 3 | 20050627090909 | 4 | 20050627101010 | ... |
| BBB | 5 | 20050627080808 | 6 | 20050627070707 | ... |
Under this kind situation, the server end data have following characteristics: all corresponding record version this shop of each record and an action type of certain data of user, every kind of data of user have a total version number, the server record real deletion time of last time.When the total version number of server end user data during greater than the total version number of client user's data, if the last lock in time fully of client is less than (the real deletion: remove the record of those modes of operation for deletion in server of real deletion time of the last time of server end, real deletion is only regularly carried out at server end), then client must be carried out once fully synchronously.
It is as follows to carry out fully synchronous reason: it all is pseudo-deletion (pseudo-deletion: write down and only delete in local data file that the user operates deletion record, in server, also exist, just the action type of these records has been set to deletion, these type of data are unavailable, server can be deleted by regularly carrying out in fact), the only first setting operation type of server has only been deleted record in client for deletion.Because the user may install the client login system on multiple computers, and the pseudo-deletion record on the server can not forever be preserved, so need carry out real deletion every a period of time (such as 1 month), but after the server deletion, local data base on possible this user's certain computer is not deletion also, so real deletion back just must be fully synchronously once on the server.
Also out of Memory can be used in the embodiment of the invention, following setting can be done respectively.
Total version number data of table (two) server end.
Table (three) is a server end call log table.
Table (four) is the server-side system allocation list.
| The user | Call log version number | Address book version number | ... |
| AAA | 3 | 4 | ... |
| BBB | 5 | 6 | ... |
Table (two)
| The user | Daily record ID | ... | Record version this shop | |
| AAA | ||||
| 1 | ... | 2 | Newly-increased | |
| AAA | 2 | ... | 3 | Revise |
| BBB | 3 | ... | 5 | Revise |
| BBB | 4 | ... | 4 | Newly-increased |
| BBB | 5 | ... | 3 | Deletion |
Table (three)
| System | The real deletion time of last time | ... | |
| -1 | 20050628000101 | ... |
Table (four)
The synchronization processing method of user's various operations (inquiry, increase, revise, deletion) is described below, so that call log or individual address book be maintained as the example explanation.
Embodiment 1: the initialization local data file.
The user lands from client, FTP client FTP judges that each local data file does not exist or file corruption when unavailable, client is created new data file automatically, download the initialization that related data is finished the client terminal local data from server then, as shown in Figure 2, be the initialized schematic flow sheet of client data of the present invention, as can be seen from Figure 2, it mainly may further comprise the steps:
S11, user initiate the application of game server by client;
S12, server carry out the legitimacy authentication to the user, return some information of user, and client is presented to user's (such as some exercisable feature lists, some data of individual subscriber).
S13, user be at the client operation call log, and client judges at first whether the call log local file exists or whether damage.
If the S14 file exists and also do not damage, client is just according to inquiry described below, increase, modification, deletion handling process service data.If data file does not exist, then create file.If data file is damaged, create new file again after then deletion has damaged file.
S15, client are initiated data synchronization request, and the total version number of local data is 0.
S16, server judge that local total version number equals 0, then reads the call log record in the client server.
S17, return complete sync id, user's all-calls log record and total version number.
The action type of every record that S18, client analysis are returned as for newly-increased and modification type, then increases a record at local data file, if be deletion, then needn't in local number file, increase this record, upgrade the total version number of local data, metered call daily record complete lock in time.
Embodiment 2: query note.
As shown in Figure 3, be query manipulation schematic flow sheet of the present invention, as can be seen from Fig. 3, it mainly may further comprise the steps:
S21, user initiate the application of query call daily record by client, and then client need at first to judge whether the initialization local data file, and is then synchronous according to the initialization flow process if desired, walks the S28 step then.
Local total version number and complete lock in time of last time are provided during the application of S22 client.
S23, server are judged the total version number of data on total version of local number and the server, if both equate that illustrate that then data are synchronous, it is successful synchronously to return client, is not with user data.Walk the S28 step then.If greater than the total version number of local data, illustrate that then data are nonsynchronous.
If S24 then must carry out once fully synchronously less than the real deletion time of the last time of server end last lock in time fully.Otherwise the processing below continuing.
S25, server side take out the record of version number greater than the total version number of local data, and these records need synchronously.
S26, returning part sync id must simultaneous call log record and total version numbers.
S27, client are analyzed the action type of every record, as for newly-increased type, then increase a record at local data file; If for revising, if there is this record in local number file, then deletion is increased to file to the recorded content that returns then earlier, if there is not this record in local data file, then the recorded content that returns is increased to file; If be deletion, then delete this record of local number file; Client is upgraded local total version number.
S28, client are fetched data from local data file.
Embodiment 3: increase record.
As shown in Figure 4, be the schematic flow sheet of the newly-increased record of the present invention, as can be seen from Fig. 4, it mainly may further comprise the steps:
S31, user increase the contact person by client in address book, then client need at first to judge whether the initialization local data file, and be then synchronous according to the initialization flow process if desired, handles below continuing then.
Local total version number, complete lock in time of last time, adding information of contact person are provided when S32, client application.
If this record of S33 exists, then think to increase newly successfully, continue the S35 processing in step, if there is no or delete, then carry out the S34 step.
S34, server insert newly-increased record, if the then change action type of having deleted is upgraded this record version this shop and the total version number of update service device side for newly-increased.
If S35 then must carry out once fully synchronously less than the real deletion time of the last time of server end last lock in time fully.Otherwise the processing below continuing.
S36, server side take out the record of version number greater than the total version number of local data, and these records need synchronously.
S37, returning part sync id must simultaneous call log record and total version numbers.
S38, client are analyzed the action type of every record, as for newly-increased type, then increase a record at local data file; If for revising, if there is this record in local number file, then deletion is increased to file to the recorded content that returns then earlier, if there is not this record in local data file, then the recorded content that returns is increased to file; If be deletion, then delete this record of local number file; Client is upgraded local total version number.
Embodiment 4: amendment record.
As shown in Figure 5, be the schematic flow sheet of amendment record of the present invention, as can be seen from Fig. 5, it mainly may further comprise the steps:
S41, user are by client modified address contact person in this, and then client need at first to judge whether the initialization local data file, and is then synchronous according to the initialization flow process if desired, handles below continuing then.
Provide local total version number, complete lock in time of last time, contact person to revise information when S42, client application.
S43, if there is no or delete, then carry out the S45 step; If this record exists, then continue the S44 processing in step.
S44, this record of server update, upgrading the action type that changes record is to revise, and upgrades this record version this shop and the total version number of server side.
If S45 then must carry out once fully synchronously less than the real deletion time of the last time of server end last lock in time fully.Otherwise the processing below continuing.
S46, server side take out the record of version number greater than the total version number of local data, and these records need synchronously.
S47, returning part sync id, address book contact person record that must be synchronous and total version number.
S48, client are analyzed the action type of every record, as for newly-increased type, then increase a record at local data file; If for revising, if there is this record in local number file, then deletion is increased to file to the recorded content that returns then earlier, if there is not this record in local data file, then the recorded content that returns is increased to file; If be deletion, then delete this record of local number file; Client is upgraded local total version number.
Embodiment 5: deletion record.
As shown in Figure 6, be the schematic flow sheet of deletion record of the present invention, as can be seen from Fig. 6, it mainly may further comprise the steps:
S51, user are by contact person in the client deletion address book, and then client need at first to judge whether the initialization local data file, and is then synchronous according to the initialization flow process if desired, handles below continuing then.
Local total version number, complete lock in time of last time, contact person to be deleted are provided when S52, client application.
S53, if there is no or delete, then carry out the S55 step; If this record exists, then continue the S54 processing in step.
S54, being operating as of this record of server update are deleted, and upgrade this record version this shop and the total version number of server end.
If S55 then must carry out once fully synchronously less than the real deletion time of the last time of server end last lock in time fully.Otherwise the processing below continuing.
S56, server side take out the record of version number greater than the total version number of local data, and these records need synchronously.
S57, returning part sync id, address book contact person record that must be synchronous and total version number.
S58, client are analyzed the action type of every record, as for newly-increased type, then increase a record at local data file; If for revising, if there is this record in local number file, then deletion is increased to file to the recorded content that returns then earlier, if there is not this record in local data file, then the recorded content that returns is increased to file; If be deletion, then delete this record of local number file; Client is upgraded local total version number.
Data such as version number, action type and the versions of data of the present invention by increasing record number generate identification information, realized that part is synchronous and deleted the synchronization scenario that combines fully, improved data synchronization efficiency, improve the operating experience of client, reduced the interaction data amount of client and server.
Obviously, those skilled in the art can carry out various changes and modification to the present invention and not break away from the spirit and scope of the present invention.Like this, if of the present invention these are revised and modification belongs within the scope of claim of the present invention and equivalent technologies thereof, then the present invention also is intended to comprise these changes and modification interior.
Claims (27)
1, a kind of client data and synchronous method of server end data of realizing, it is characterized in that, for being provided with first, server end first data generate identification information, for being provided with second, client second data generate identification information, when carrying out simultaneous operation, relatively first generate identification information and second and generate identification information, when both have when inequality sync client second data.
2, the method for claim 1 is characterized in that, described generation identification information is a versions of data number.
3, the method for claim 1 is characterized in that, described generation identification information is the last rise times of data.
4, the method for claim 1 is characterized in that, described generation identification information is the last simultaneous operation time.
5, the method for claim 1 is characterized in that, described sync client second data are for server end sends to client with packing data.
6, method as claimed in claim 5 is characterized in that, described packing data form is extend markup language (XML) form.
7, the method for claim 1 is characterized in that, described first data and second data can have a plurality of respectively, corresponding a plurality of first generates identification information and a plurality of second generation identification information respectively.
8, method as claimed in claim 7 is characterized in that, it is inequality that the described first generation identification information and second generates identification information, and it is all inequality inequality with part to comprise that the first generation identification information and second generates identification information.
9, method as claimed in claim 8, it is characterized in that, generate identification information and second and generate the identification information part when inequality when described first, before first data are not carried out the reality deletion, described sync client second data manipulation is second data that the only synchronous first generation identification information and second generates identification information part inequality.
10, method as claimed in claim 8, it is characterized in that, generate identification information and second and generate the identification information part when inequality when described first, carry out after reality delete in first data, described sync client second data manipulation is synchronous all client second data.
11, method as claimed in claim 8 is characterized in that, generates identification information and second to generate identification information whole when inequality when described first, and described sync client second data manipulation is all client second data synchronously.
As claim 10 or 11 described methods, it is characterized in that 12, all client second data manipulations synchronously are after client is deleted local data, again Download Server end first data.
13, the method for claim 1 is characterized in that, described server end is communicated by letter by HTTP(Hypertext Transport Protocol), Simple Object Access Protocol (SOAP), session initiation protocol (SIP) or XML configuration access agreement (XCAP) with client.
14, the method for claim 1 is characterized in that, also comprises the step of described client initiation synchronization request, carries second in the described synchronization request and generates identification information.
15, method as claimed in claim 14 is characterized in that, comprises that also described server end receives the step of described synchronization request, and according to the second generation identification information that carries in the described synchronization request, makes comparisons with the first generation identification information.
16, the method for claim 1 is characterized in that, described generation identification information is with the form setting.
17, the method for claim 1 is characterized in that, when the described first generation identification information was identical with the second generation identification information, server end returns to described client did not have the Data Update notice.
18, the method for claim 1 is characterized in that, described server end is provided with the first data manipulation type identification, identifies the content of the last operation of first data.
19, method as claimed in claim 18 is characterized in that, during sync client second data, carries out corresponding operation according to the last action type of first data.
20, method as claimed in claim 19, it is characterized in that, during sync client second data, if the action type of first data is newly-increased, then judge in client whether first data exist, if exist, then at first deletion, newly-increased again first data, if there is no, then directly newly-increased first data.
21, method as claimed in claim 19, it is characterized in that, during sync client second data, if the action type of first data is to revise, then judge in client whether first data exist, if exist, then at first deletion, and then newly-increased first data, if there is no, then newly-increased these first data.
22, method as claimed in claim 19 is characterized in that, during sync client second data, if the action type of first data is deletions, then judges in client whether first data exist, if exist then deletion.
23, method as claimed in claim 22 is characterized in that, when carrying out the data deletion action, first data side only retouching operation be designated deletion sign, described first data of actual deletion.
24, method as claimed in claim 21 is characterized in that, the regular clear operation of server is designated first data of deletion sign, described first data of actual deletion.
25, a kind of client data and synchronous system of server end data of realizing comprises the client and server end, and described server end stores first data, described client stores have need with second data of server end data sync; It is characterized in that:
Described client is provided with the second processing logic unit, and this second Logical processing unit is initiated data synchronization request according to client second data mode to server end;
Described server end is provided with the first processing logic unit, and this first Logical processing unit receives data synchronization request, and described synchronization request is responded.
26, system as claimed in claim 25, it is characterized in that, in the described synchronization request, carry the second generation information of client second data, the described first processing logic unit is according to the described second generation information, whether judge consistently with the first generation information of server end first data, if inconsistent, then the Control Server end carries out client data simultaneous operation.
27, as claim 25 or 26 described systems, it is characterized in that, described client and server end are by HTTP(Hypertext Transport Protocol), Simple Object Access Protocol (SOAP), session initiation protocol (SIP) or XML configuration access agreement (XCAP) communication.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN 200510085054 CN1852137A (en) | 2005-07-20 | 2005-07-20 | Method for realizing synchronization of client end data and server end data |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN 200510085054 CN1852137A (en) | 2005-07-20 | 2005-07-20 | Method for realizing synchronization of client end data and server end data |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN1852137A true CN1852137A (en) | 2006-10-25 |
Family
ID=37133607
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN 200510085054 Pending CN1852137A (en) | 2005-07-20 | 2005-07-20 | Method for realizing synchronization of client end data and server end data |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN1852137A (en) |
Cited By (23)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2009049524A1 (en) * | 2007-10-12 | 2009-04-23 | Huawei Technologies Co., Ltd. | A data synchronization method, system and device |
| CN101192229B (en) * | 2006-12-01 | 2010-09-22 | 阿里巴巴集团控股有限公司 | Data synchronization method and system |
| CN101309291B (en) * | 2008-05-30 | 2011-04-20 | 中兴通讯股份有限公司 | Tool and method for terminal data maintenance |
| CN101447874B (en) * | 2008-12-25 | 2011-07-20 | 华为终端有限公司 | Data synchronization method, client and server |
| CN101321193B (en) * | 2008-07-23 | 2011-08-31 | 中兴通讯股份有限公司 | Synchronization method for dynamic contents distribution business, user terminal and server |
| CN102591901A (en) * | 2010-11-23 | 2012-07-18 | 三星电子株式会社 | Apparatus and method for synchronizing data in connected devices |
| CN102968345A (en) * | 2012-10-29 | 2013-03-13 | 北京奇虎科技有限公司 | Note real-time synchronizing method and device |
| CN102968347A (en) * | 2012-10-29 | 2013-03-13 | 北京奇虎科技有限公司 | Method for synchronizing browser memo in real time and browser realizing memo real-time synchronization |
| CN101426026B (en) * | 2008-09-17 | 2013-07-03 | 北京六维世纪网络技术有限公司 | Method and system for data synchronization between multiple servers |
| CN104035814A (en) * | 2013-03-07 | 2014-09-10 | 联想(北京)有限公司 | Data processing method and electronic device |
| CN104065676A (en) * | 2013-03-19 | 2014-09-24 | 联想(北京)有限公司 | File synchronization method and file synchronization equipment |
| CN104580454A (en) * | 2014-12-31 | 2015-04-29 | 乐视网信息技术（北京）股份有限公司 | Data synchronizing method, device and system |
| CN104753990A (en) * | 2013-12-27 | 2015-07-01 | 中国移动通信集团公司 | Data synchronization method, device and system |
| CN104881766A (en) * | 2015-05-07 | 2015-09-02 | 北京京东尚科信息技术有限公司 | Distributed storage data processing method, device, and system |
| CN105069161A (en) * | 2015-08-26 | 2015-11-18 | 浪潮软件股份有限公司 | Data interaction method and data interaction device |
| CN105187475A (en) * | 2015-06-09 | 2015-12-23 | 深圳市金蝶友商电子商务服务有限公司 | Method and system for data synchronization |
| CN105592118A (en) * | 2014-10-23 | 2016-05-18 | 阿里巴巴集团控股有限公司 | Method, system and server for synchronizing user application data |
| CN106886548A (en) * | 2016-08-03 | 2017-06-23 | 阿里巴巴集团控股有限公司 | Data query method and device |
| CN108228100A (en) * | 2017-12-27 | 2018-06-29 | 郑州云海信息技术有限公司 | A kind of data safety processing method and system based on mass storage system (MSS) |
| CN110557441A (en) * | 2016-03-01 | 2019-12-10 | 张君 | Data interaction method and system for client and server in online and offline states |
| CN110769061A (en) * | 2019-10-24 | 2020-02-07 | 华为技术有限公司 | Data synchronization method and equipment |
| CN111083038A (en) * | 2019-10-23 | 2020-04-28 | 上海盈联电信科技有限公司 | Enterprise management online instant messaging system and method |
| CN112527763A (en) * | 2019-09-19 | 2021-03-19 | 深圳艾派网络科技股份有限公司 | Method and system for updating text format data |
-
2005
- 2005-07-20 CN CN 200510085054 patent/CN1852137A/en active Pending
Cited By (32)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101192229B (en) * | 2006-12-01 | 2010-09-22 | 阿里巴巴集团控股有限公司 | Data synchronization method and system |
| US8489548B2 (en) | 2007-10-12 | 2013-07-16 | Huawei Technologies Co., Ltd. | Method, system, and device for data synchronization |
| WO2009049524A1 (en) * | 2007-10-12 | 2009-04-23 | Huawei Technologies Co., Ltd. | A data synchronization method, system and device |
| CN101309291B (en) * | 2008-05-30 | 2011-04-20 | 中兴通讯股份有限公司 | Tool and method for terminal data maintenance |
| CN101321193B (en) * | 2008-07-23 | 2011-08-31 | 中兴通讯股份有限公司 | Synchronization method for dynamic contents distribution business, user terminal and server |
| CN101426026B (en) * | 2008-09-17 | 2013-07-03 | 北京六维世纪网络技术有限公司 | Method and system for data synchronization between multiple servers |
| CN101447874B (en) * | 2008-12-25 | 2011-07-20 | 华为终端有限公司 | Data synchronization method, client and server |
| CN102591901A (en) * | 2010-11-23 | 2012-07-18 | 三星电子株式会社 | Apparatus and method for synchronizing data in connected devices |
| CN102591901B (en) * | 2010-11-23 | 2017-09-01 | 三星电子株式会社 | Apparatus and method for the data in the equipment of synchronized links |
| CN102968345B (en) * | 2012-10-29 | 2015-11-25 | 北京奇虎科技有限公司 | Note real-time synchronization method and device |
| CN102968347B (en) * | 2012-10-29 | 2017-03-08 | 北京奇虎科技有限公司 | The method of browser note real-time synchronization and the browser realizing note real-time synchronization |
| CN102968345A (en) * | 2012-10-29 | 2013-03-13 | 北京奇虎科技有限公司 | Note real-time synchronizing method and device |
| CN102968347A (en) * | 2012-10-29 | 2013-03-13 | 北京奇虎科技有限公司 | Method for synchronizing browser memo in real time and browser realizing memo real-time synchronization |
| CN104035814A (en) * | 2013-03-07 | 2014-09-10 | 联想(北京)有限公司 | Data processing method and electronic device |
| CN104065676A (en) * | 2013-03-19 | 2014-09-24 | 联想(北京)有限公司 | File synchronization method and file synchronization equipment |
| CN104753990A (en) * | 2013-12-27 | 2015-07-01 | 中国移动通信集团公司 | Data synchronization method, device and system |
| CN104753990B (en) * | 2013-12-27 | 2018-11-16 | 中国移动通信集团公司 | A kind of method of data synchronization, device and system |
| CN105592118A (en) * | 2014-10-23 | 2016-05-18 | 阿里巴巴集团控股有限公司 | Method, system and server for synchronizing user application data |
| CN105592118B (en) * | 2014-10-23 | 2018-11-13 | 阿里巴巴集团控股有限公司 | Synchronous user applies method, system and the server-side of data |
| CN104580454A (en) * | 2014-12-31 | 2015-04-29 | 乐视网信息技术（北京）股份有限公司 | Data synchronizing method, device and system |
| CN104881766A (en) * | 2015-05-07 | 2015-09-02 | 北京京东尚科信息技术有限公司 | Distributed storage data processing method, device, and system |
| CN105187475A (en) * | 2015-06-09 | 2015-12-23 | 深圳市金蝶友商电子商务服务有限公司 | Method and system for data synchronization |
| CN105187475B (en) * | 2015-06-09 | 2018-10-12 | 深圳金蝶账无忧网络科技有限公司 | The method and system that data synchronize |
| CN105069161A (en) * | 2015-08-26 | 2015-11-18 | 浪潮软件股份有限公司 | Data interaction method and data interaction device |
| CN110557441A (en) * | 2016-03-01 | 2019-12-10 | 张君 | Data interaction method and system for client and server in online and offline states |
| CN110557441B (en) * | 2016-03-01 | 2022-02-22 | 张君 | Data interaction method and system for client and server in online and offline states |
| CN106886548A (en) * | 2016-08-03 | 2017-06-23 | 阿里巴巴集团控股有限公司 | Data query method and device |
| CN108228100A (en) * | 2017-12-27 | 2018-06-29 | 郑州云海信息技术有限公司 | A kind of data safety processing method and system based on mass storage system (MSS) |
| CN112527763A (en) * | 2019-09-19 | 2021-03-19 | 深圳艾派网络科技股份有限公司 | Method and system for updating text format data |
| CN111083038A (en) * | 2019-10-23 | 2020-04-28 | 上海盈联电信科技有限公司 | Enterprise management online instant messaging system and method |
| CN110769061A (en) * | 2019-10-24 | 2020-02-07 | 华为技术有限公司 | Data synchronization method and equipment |
| WO2021077912A1 (en) * | 2019-10-24 | 2021-04-29 | 华为技术有限公司 | Data synchronization method and device |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN1852137A (en) | Method for realizing synchronization of client end data and server end data | |
| CN101064630A (en) | Data synchronization method and system | |
| CN1291313C (en) | System and method for the automatic installation and configuration of an operating system | |
| CN1852101A (en) | Parallel downloading method and terminal | |
| CN1157978C (en) | Apparatus and method for managing mobile phone agent | |
| CN1133308C (en) | Radio communication system and method for changing displaying speech of radio user's device | |
| CN1545048A (en) | Method for implementing tree storage and access by two-dimensional table | |
| CN1852538A (en) | Method and apparatus for monitoring and updating software in apparatus management | |
| CN1773456A (en) | Automatic mounting system and method for printer driving program | |
| CN1866854A (en) | Method for updating and recovering terminal device data in device management | |
| CN101076032A (en) | Method and system for transmitting information | |
| CN1852309A (en) | Data synchronizing processing method and its client end | |
| CN1670730A (en) | Newest version content file management device and its recording medium | |
| CN1229944A (en) | System and method for reducing footprint of preloaded classes | |
| CN101079755A (en) | Configuration method of network element management system | |
| CN1874233A (en) | System and method for sending message of broadcast | |
| CN1859388A (en) | Dynamic content transfer method and personalized engine and dynamic content transmitting system | |
| CN1848761A (en) | Software assembly parameter configuration method and system and terminal equipment thereof | |
| CN101042649A (en) | Configuring information processing method and arrangement, and platform system | |
| CN1852261A (en) | Method for maintenance of neighbor entry | |
| CN1858782A (en) | Method and device for forming user group based on user service data | |
| CN1913692A (en) | Method for loading equipment software according to allocation | |
| CN1886976A (en) | Method, software and apparatus for performing actions on a wireless device using action lists and versioning | |
| CN1617496A (en) | Method for automaticall updating configuration for next generation network terminal | |
| CN1549130A (en) | Method of document synchronization |
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: 20061025 |