CN103002010B - A kind of data-updating method based on incremental data, device and system - Google Patents

Abstract

The invention discloses a method, device and system for updating data. The system includes an upload data processing device, a download data processing device and a server, and the current version of data is stored in the upload data processing device and the download data processing device. , the upload data processing device is used to generate incremental data according to the data before updating and the data after updating, and send the incremental data to the server, wherein the incremental data refers to the difference between the data after updating and the data before updating Changed data; the server receives and saves the incremental data, and sends the incremental data to the download data processing device; the download data processing device is used to receive incremental data from the server, and according to the data to be updated stored by the download data processing device The data and the delta data produce updated data. The invention can reduce the network bandwidth occupied by data updating, and improve the updating speed, efficiency and real-time performance.

Description

A method, device and system for updating data based on incremental data

technical field

The invention belongs to the field of communication, in particular to the transmission of digital information, in particular to a method and device for updating data based on incremental data.

Background technique

In the computing architecture implemented by the network communication system, it is often necessary to transmit and store different versions of data between different computing entities. For example, when the user changes the favorites of the browser of his personal computer (PC), different versions of the favorites will be generated every time the change is made. In emerging computing application fields that need to be synchronized by the server and the client, it is usually required to transmit data between the client and the server, and store and update data in each computing entity in real time, such as the information of the favorites. Several scenarios of synchronizing and updating data in the prior art are exemplarily described below.

FIG. 1 is a schematic diagram of a scenario of synchronizing data among multiple clients in the prior art. The scenario is: the same user can log in to different clients (such as a mobile phone and a PC), and each client is connected to a server for data sharing and synchronization. When the user changes certain data, such as favorites, when logging into one of the clients (such as a PC), an updated version of the favorites will be stored on the client. When the user can log in another client next time to use this updated favorites, the client first transmits the updated favorites to the server, and when the user logs in another client, the server will send the updated favorites to the server. The updated favorites are sent to another client (such as a mobile phone) currently logged in by the user. In this scenario, even if the data of a client changes slightly, the entire updated data (or a full amount of updated data) needs to be transmitted between the client and the server. For data that needs to be updated frequently or data with a huge amount of data, it will undoubtedly greatly occupy network bandwidth and consume a lot of resources.

Fig. 2 is a schematic diagram of a scenario of synchronizing data between master and slave servers in the prior art. In this scenario, the data sharing network includes a master server and a slave server. When a piece of data in the master server changes, the master server needs to transmit the entire updated data to the slave server. The data is, for example, a file, or part of data in the file. Similarly, in this scenario, the amount of data update is not distinguished, but the entire updated data is directly transmitted between the master and slave servers.

It can be seen that a more resource-intensive data update method is extremely needed in the prior art to reduce bandwidth occupation and resource consumption caused by data update.

Contents of the invention

In view of the above problems, the present invention is proposed to provide a data update method and device based on incremental data that overcomes the above problems or at least partially solves the above problems.

According to one aspect of the present invention, a method for sharing updated data by a data processing device is provided, the data processing device stores data before updating and data after updating, and can exchange data with a server, the method includes The following steps: the data processing device generates incremental data according to the data before updating and the data after updating, and sends the incremental data to the server, so that the server can share the updated data with other data processing devices connected to the server. The data, wherein the incremental data refers to the data of the change of the updated data relative to the data before the update.

The present invention also proposes a server-based data update method, the server can exchange data with several data processing devices, the method includes the following steps: the server receives data from a data processing device, and saves the data in the In the server, the data includes incremental data, and the incremental data refers to the data of the data after the update in the data processing device relative to the data before the update; the server sends at least a part of the stored data to another A data processing device, the other data processing device generates updated data based on its data to be updated and received data.

The present invention also proposes a method for acquiring updated data, which is applied to a data processing device, wherein the data processing device stores data to be updated, and can exchange data with a server, the method comprising: the data processing device Receive data from the server, the data includes incremental data; the data processing device generates updated data according to the data to be updated stored by it and the received data, wherein the incremental data refers to The data of the change of the updated data with respect to the data before the update. The present invention also proposes a data processing device for sharing updated data. The data processing device stores data before updating and data after updating, and can exchange data with a server. The data processing device includes: incremental The data generation module is used to generate incremental data according to the data before updating and the data after updating, wherein the incremental data refers to the data of the data after updating relative to the data before updating; the communication module is used to Data is sent to the server, the data including the incremental data. The present invention also proposes a data processing device for receiving update data, the data processing device stores data to be updated, and can exchange data with a server, the data processing device includes: a communication module, used for The server receives data, and the data includes incremental data, and the incremental data refers to the data of the data after the update relative to the data before the update; the data update module is used to update the data according to the acquired data The data for produces updated data. The present invention also proposes a server for providing data update service, the server can exchange data with several data processing devices, the server includes: a communication module for receiving data from a data processing device, the data includes Quantitative data, the incremental data refers to the data of the change of the updated data relative to the data before the update; the data storage module is used to save the data received from the data processing device.

The present invention also proposes a system for updating data, including an upload data processing device, a download data processing device, and a server. Data are stored in the upload data processing device and the download data processing device, and both can communicate with the server. Data exchange, characterized in that: the uploaded data processing device is used to generate incremental data according to the data before updating and the data after updating, wherein the incremental data refers to the change of the data after updating relative to the data before updating The upload data processing device is also used to send the data to the server; the server receives and saves the data, and sends at least a part of the data to the download data processing device; the download data processing The device is used for receiving the data from the server, and generating updated data according to the data to be updated and the received data. According to the data update method and system of the present invention, based on incremental data, since the amount of incremental data is less than the full amount of updated data, it can greatly reduce the network bandwidth occupied by data update, improve the update speed, efficiency and real-time.

The above description is only an overview of the technical solution of the present invention. In order to better understand the technical means of the present invention, it can be implemented according to the contents of the description, and in order to make the above and other purposes, features and advantages of the present invention more obvious and understandable , the specific embodiments of the present invention are enumerated below.

Description of drawings

Various other advantages and benefits will become apparent to those of ordinary skill in the art upon reading the following detailed description of the preferred embodiment. The drawings are only for the purpose of illustrating a preferred embodiment and are not to be considered as limiting the invention. Also throughout the drawings, the same reference numerals are used to designate the same parts. In the attached picture:

FIG. 1 is a schematic diagram of a scenario of synchronizing data between multiple clients in the prior art;

FIG. 2 is a schematic diagram of a scenario of synchronizing data between master and slave servers in the prior art;

Fig. 3 is the flow chart of basic steps of the data update method based on incremental data of the present invention;

FIG. 4 is a schematic diagram of a scenario of a method for updating data based on incremental data according to the first embodiment of the present invention;

Fig. 5 is the flow chart of the data update method based on incremental data of the first embodiment of the present invention;

FIG. 6 is a schematic structural diagram of a data update system based on incremental data according to the first embodiment of the present invention;

FIG. 7 is a flow chart of a method for updating data based on incremental data according to the second embodiment of the present invention;

FIG. 8 is a schematic structural diagram of a data update system based on incremental data according to a second embodiment of the present invention.

detailed description

Exemplary embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. Although exemplary embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure may be embodied in various forms and should not be limited by the embodiments set forth herein. Rather, these embodiments are provided for more thorough understanding of the present disclosure and to fully convey the scope of the present disclosure to those skilled in the art.

The present invention proposes a new data update method and corresponding device. The method and device of the present invention are suitable for any data processing equipment with data processing capabilities, including fixed or mobile data processing equipment, such as personal computers (PCs), Servers, PDAs, Smartphones, etc.

Assuming that a data processing device stores a data file, the data file may need to be continuously updated, hereinafter referred to as data. In order to avoid transmitting the entire updated data used to replace the data before the update when the data is updated, the concept of "incremental data" is proposed in the present invention.

Before explaining "incremental data", we first define the concept of "full data" in the present invention. We define full data as: data that can update the data to be updated without relying on the data to be updated. That is to say, as long as the full amount of data is transmitted to the data processing device and replaced by the data to be updated, the data update is completed without any other operations. It can be seen that the data update method in the prior art is actually a method of directly using the full amount of updated data to replace the data to be updated to obtain the full amount of updated data. For example, the data to be updated is a favorite, and the favorite includes multiple favorite items. Then, a full amount of updated data is a new favorite different from the original favorite. The new collection may contain some items in the original collection, or may not contain the items in the original collection at all, as long as the new collection replaces the original collection, the data update is completed. The advantage of using the full amount of updated data for data update is that it does not need to consider the data content of the original data, and no matter what type of data it is, the data update can be performed directly. However, as mentioned earlier, its disadvantage is that the amount of data transmission is large, which wastes system resources.

Therefore, the present invention proposes a data update method, device and system based on "incremental data", and the "incremental data" proposed by the present invention refers to the data after updating relative to the data before updating. The so-called change represents the difference between the updated data and the data before the update. That is to say, incremental data is data obtained by performing certain operations on the data before updating and the data after updating. The specific operation to be used can be determined according to the type of data.

If both the data before updating and the data after updating are numbers, the operation method can be a simple mathematical operation. For example, when the data before updating is 2 and the data after updating is 3, the incremental data may be equal to the data after updating minus the data before updating, that is, the incremental data is =3−2=1.

If both the data before updating and the data after updating are favorites, the calculation method may be a comparison algorithm. For example, the pre-update favorites include "URL 1", "URL 2", "URL 3", while the updated favorites include "URL 1", "URL 2", "URL 3" and "URL 4" , then the incremental data is obtained as "URL 4" through comparison and calculation.

Of course, the above examples are all cases where the data type is relatively simple, and the present invention can be extended to any data type, as long as there is an appropriate calculation method between the data before updating and the data after updating, it can be increased by this calculation method. Quantitative data.

In current network communications, for data processing equipment and data transmission systems, the most widely used data are divided into two types, one is descriptive data, and the other is binary data. Descriptive data is data that describes information in a language that can be understood by humans, and is suitable for human-computer interaction, such as natural language data, hypertext language data (such as HTML, XML, and Json, etc.) and high-level programming languages (C language, Javascript, etc.) etc.), program code data, etc. For the descriptive data, the present invention can select the calculation method according to the existing data format, or set a special data label in the existing data format, so as to facilitate the calculation. For example, for data in XML format, incremental data can be calculated based on existing tags in the XML file, or special tags for incremental data calculation can be defined by yourself.

For example, the code for the following XML that needs to be updated is:

The XML code for the updated full amount of data is:

Then the incremental data can be

{0114, creattime, Rep, 2010.08.21},

Among them, "0114" indicates the id of the data before updating, creattime indicates the tag name under the id, Rep indicates "replacement", and 2010.08.21 indicates the replacement content.

It can be seen that when updating descriptive data, incremental data can also be descriptive data used to describe the amount of change. Generally speaking, the data volume of incremental data will be much smaller than that of the full updated data. Especially for the case where the data before the update is huge and the amount of change is not too large.

In another case, both the data before updating and the data after updating are binary data. Binary data here refers to data suitable for storage and transmission of data processing equipment. Binary data is universal, stable, and does not need to be used for different applications. Secondary development, such as various computer files (including pictures, videos), compiled program codes, etc.

In the prior art, there are already some calculation methods for comparing general binary data. The present invention can directly adopt the calculation method in the prior art, and those skilled in the art can also design a calculation method specially used for incremental data of a specific data type by making adaptive changes to known algorithms.

It should be noted that the calculation method used in the present invention is preferably a reversible algorithm.

Based on the above-mentioned principle about incremental data, the data update method for data processing equipment of the present invention includes the following two basic steps, as shown in FIG. 3 .

(1) sending the incremental data generated by the data before updating and the data after updating to a data processing device;

(2) In the data processing apparatus, updated data is formed from the data to be updated and the incremental data.

How to generate incremental data has been described above. When using the present invention to update data, it is also necessary to generate updated data according to the data to be updated and the incremental data. That is to say, the present invention also needs to generate a full amount of updated data, and make the generated full amount of updated data replace the data to be updated.

According to the present invention, the process of generating updated data can be the inverse operation of generating incremental data. When the calculation method for generating incremental data is a reversible algorithm, a full amount of updated data can be generated based on the data to be updated and the incremental data. Data made possible. For example, for the pure mathematical operation in the previous example, if the data before the update is 2 and the data after the update is 3, the data to be updated is the same as the data before the update, which is also 2, and the algorithm for calculating the incremental data is after the update The data before the update is subtracted from the data before the update, that is, the incremental data is =3-2=1, then, the algorithm for generating the full amount of updated data is the inverse operation of the above algorithm, that is, the data to be updated plus the incremental data, That is, the updated data is =2+1=3.

For descriptive incremental data, the inverse operation may be parsing the descriptive incremental data to generate updated data. For example, for the descriptive incremental data {0114, creattime, Rep, 2010.08.21}, it can be parsed as replacing the value of the tag creattime in ID 0114 with 2010.08.21.

Similarly, for binary data, the inverse algorithm of the aforementioned algorithm for calculating incremental data for binary data may be used to generate updated data from the data to be updated and the incremental data. In order to make the object, technical solution and advantages of the present invention clearer, the present invention will be further described in detail below in conjunction with specific embodiments and with reference to the accompanying drawings.

<First embodiment>

Fig. 4 is a schematic diagram of a scenario of a method for updating data based on incremental data according to the first embodiment of the present invention. It can be seen from FIG. 4 that the method of the first embodiment is similar to the system architecture of the method shown in FIG. 1 . This embodiment implements a method for synchronizing data between clients, where the clients include an upload client and a download client, both of which can exchange data with a server.

The upload client refers to a client for transmitting data to the server, and the download client refers to a client for downloading data from the server.

In order to distinguish the data after each update, and for the convenience of description, the concept of version is used here. In the present invention, the original data and each update based on the original data correspond to a version. Versions are indicated by version numbers. For example, the version number of the original data may be set to 1.0.0.0, the version number of the data updated for the first time is 1.0.0.1, the version number of the data updated for the second time is 1.0.0.2, and so on. According to the present invention, the original data can also be empty data.

Fig. 5 is a flow chart of the method for updating data based on incremental data according to the first embodiment of the present invention. As shown in Figure 5. The method of the present invention comprises three steps:

First, the upload client generates incremental data according to the data before updating and the data after updating, and uploads the incremental data to the server;

Next, the server receives the incremental data transmitted by the upload client, and saves the incremental data on the server;

Finally, the server sends the incremental data to the download client, and the download client generates updated data according to the data to be updated and the incremental data.

The premise that the above method can be realized is that the uploading client stores the data before updating and the data after updating, and the downloading client stores the data to be updated, and the data to be updated can be empty. In addition, only incremental data may be saved in the server, or a full amount of updated data may be saved at the same time.

According to the present invention, both the uploading client and the downloading client may be any client capable of exchanging data with the server, and the number thereof is not limited.

According to the present invention, when the incremental data is sent to the download client connected to the server, the incremental data can be sent according to the preset, the preset can be a certain rule, and the rule can be an automatic forwarding rule or a By request rules.

The automatic forwarding rule is, for example: once the server receives the incremental data uploaded by the uploading client, it will send a data update notification to all connected clients, asking whether it needs to update the data, when any client When returning to receive update data, send incremental data to the client. For another example, once the server receives the incremental data uploaded by the uploading client, it sends the incremental data to all other clients of the same user. Of course, the automatic forwarding rules can also have other settings, such as timing query and sending, or once the client is connected to the server, then query and send, and so on.

The rule of request is that the server sends incremental data according to the client's request. That is to say, the server sends incremental data to the requesting client only when it receives a data update request.

The architecture of the data updating system in the first embodiment is shown in FIG. 6 , where 1 is a server, and 2 to 5 are clients. The server includes a communication module and a data storage module, and the client includes a communication module and a data update module. The communication module of the server 1 can exchange data with the communication modules of the clients 2-5. The clients 2-5 can be used as uploading clients or downloading clients respectively, or can be used as both uploading clients and downloading clients at the same time.

When used as an upload client, the data updating module is used to generate incremental data according to the data before updating and the data after updating; the communication module is used to send the data including the incremental data to the server.

When used as a download client, the communication module is used to receive data from the server, the data includes incremental data, and the data update module is used to generate updated data according to the data to be updated saved by the client and the received data .

In this embodiment, the data update module of each client can generate incremental data according to the data before updating and the data after updating, and can also generate updated data according to the data to be updated and the incremental data. The communication module can be used for both uploading data and downloading data. When any one of the clients 2-5 generates incremental data and sends the data including the incremental data to server 1 through its communication module, the client acts as the upload client for this update; when the client When any client in terminals 2-5 downloads data from the server through its communication module, this client is the download client for this update.

The data storage module of the server is used for storing the incremental data uploaded by the uploading client. According to an embodiment of the present invention, when the server saves the incremental data, it also saves version information of the incremental data, such as a version number.

On the one hand, the communication module of the server is used to receive incremental data from the upload client, and on the other hand, it is also used to send the incremental data to any download client that needs to update the data according to certain rules, so that the download client The terminal is updated according to the incremental data. The rules are as mentioned above, and will not be repeated here.

The number of clients shown in FIG. 5 is four, but this is only an illustrative situation. As mentioned above, the present invention does not limit the number of clients.

<Second Embodiment>

Fig. 7 is a flow chart of a data update method based on incremental data according to the second embodiment of the present invention.

As mentioned above, the first embodiment describes the process of performing a data update according to the data update method of the present invention. The second embodiment implements multiple updates based on incremental data on the basis of the first embodiment.

For the incremental data generated after multiple updates, since it is calculated multiple times on the basis of the original data, the data redundancy problem may be serious. In this case, continuing to use incremental data updates may not be able to achieve relatively better results. Therefore, in the second embodiment, a first threshold is set in the server, and when the number of versions of the data reaches the first threshold, the server requires the upload client to send the latest version of the full amount of updated data to the server, and save the full amount of updated data on the server.

According to a specific implementation manner of the present invention, version information of the entire amount of updated data is also saved on the server at the same time. For the full amount of updated data and incremental data in the same update, they can share a version number.

For example, if the server sets the first threshold to 20, and the server stores data of the following versions,

1.0.0.0 original

1.0.0.1 added

1.0.0.2 added

...

1.0.0.18 added

1.0.0.19 added (up to version 20)

(Wherein, "original" means original data, "increment" means incremental data, and there may be no original data)

At this time, the server requires the uploading client that sends the incremental data of version 1.0.0.19 to also send the full amount of updated data of version 1.0.0.19 to the server. Therefore, the following versions of data are saved in the server:

1.0.0.0 original

1.0.0.1 added

1.0.0.2 added

...

1.0.0.18 added

1.0.0.19 added

1.0.0.19 full

(Wherein, "full" means the full amount of updated data).

According to other embodiments of the present invention, the upload client may also decide whether to upload the full amount of updated data to the server.

As mentioned above, the incremental data is saved in the server, and after multiple updates, the original data and multiple versions of the incremental data based on the original data are saved in the server. Usually, limited by hardware conditions or based on system resource considerations, for a certain data (such as a piece of software or a file), the number of data versions that can be stored on the server cannot be infinite. Therefore, another upper limit may also be set for the number of data versions on the server, which is referred to as a second threshold here. According to this embodiment of the present invention, when the number of data versions on the server reaches the second threshold, older versions of data must be deleted so as to keep the number of data versions not more than the second threshold.

According to a specific implementation manner of the present invention, the second threshold is greater than the first threshold. And, when deleting earlier versions of data, at least one full amount of updated data or original data is retained. More preferably, when there are multiple full amounts of updated data, at least the full amount of updated data of the version closest to the current version is retained.

For example, if the second threshold is 30, then the version operation process according to the second threshold will be described with reference to the following example. Assume that the following versions of data are saved in the server:

1.0.0.0 original

1.0.0.1 added

1.0.0.2 added

...

1.0.0.18 added

1.0.0.19 added

1.0.0.19 full

1.0.0.20 added

...

1.0.0.28 added

At this time, when the client updates the data to the server again, thereby saving the new data version 1.0.0.29 in the server, the version number of the data reaches the second threshold 30. Thus the server deletes the earlier version 1.0.0.0. The data versions 1.0.0.1 to 1.0.0.29 stored on the server include at least one full amount of data, for example, version 1.0.0.19 full in this example.

new version update

In the second embodiment, there may be original data, multiple versions of incremental data on the server, or at least one full amount of updated data transmitted by the upload server. In this case, the data update method of the present invention can be further optimized. For the client, its version update operation can be described as follows:

If the following versions of data exist on the server:

1.0.0.0 original

1.0.0.1 added

1.0.0.2 added

...

1.0.0.18 added

1.0.0.19 added

1.0.0.19 full

1.0.0.20 added

1.0.0.21 added

1.0.0.22 added

1.0.0.23 added

According to an embodiment of the present invention, each time a client requests the server for updating data, the server sends the latest version of the updating data to the client. The updated data of the latest version may be incremental data, or may be full updated data. According to a preferred embodiment of the present invention, when there are incremental data of the same version and full updated data, the server sends the full updated data to the client.

According to a preferred embodiment of the present invention, when the client requests the server to update data, it will attach version information of the data to be updated on the client, such as a version number. At this time, the server can compare the version number with all data version numbers on the server to determine which versions of data to send to the client.

In this case, it is more preferable that when there is updated data higher than the full amount of the current version of the client on the server, the server only selects the updated data of the full amount of the version and the updated data of the version higher than the full amount. The incremental data of the updated data is sent; more preferably, when there is more than one full amount of updated data higher than the client version on the server, the server only selects the highest version of the full amount of updated data and Incremental data of a version higher than the full amount of updated data is sent.

For example, in the example given above,

(1) When the current data version of the client (that is, the data version sent to the server with the request) is "1.0.0.22", the server can only send to the client:

1.0.0.23 added

(2) When the current data version of the client (that is, the data version sent to the server with the request) is "1.0.0.18", the server can send to the client:

1.0.0.19 added

1.0.0.20 added

1.0.0.21 added

1.0.0.22 added

1.0.0.23 added

It is also possible to send:

1.0.0.19 full

1.0.0.20 added

1.0.0.21 added

1.0.0.22 added

1.0.0.23 added.

At this point, the server can make a choice, usually based on the amount of data sent, and choose the one with the smallest amount of data to send. In this example, generally speaking, the full amount of updated data is greater than the incremental data of the same version. At this time, the amount of data sent by the former method is smaller, so you can choose to send it by the former method.

(3) When the current data version of the client (that is, the data version sent to the server with the request) is "1.0.0.1", the server can send to the client:

1.0.0.2 added

...

1.0.0.19 added

1.0.0.20 added

1.0.0.21 added

1.0.0.22 added

1.0.0.23 added

It is also possible to just send:

1.0.0.19 full

1.0.0.20 added

1.0.0.21 added

1.0.0.22 added

1.0.0.23 added

At this time, since the former method needs to send more versions of the incremental data, the amount of data sent may be larger than the latter method, and the server can choose the latter method to send.

However, what is described above is only an example, and when a specific transmission method is selected, specific settings may be made according to actual conditions. For example, in the above-mentioned case (2), although the data volume when the current update is sent in the previous method is smaller. However, if the next update or the next update is taken into consideration and the total amount of sent data is taken into consideration, the second method can also be selected.

version recovery

According to the second embodiment of the present invention, when multiple versions of data are stored on the server, the client can also request "version recovery" from the server. The so-called version recovery means that the client requests to restore the data of the specified version from the server.

When the client sends a version restoration request to the server, it also attaches the version information to be restored, such as a version number. At this point, the server chooses to send at least one full amount of data and incremental data based on the full amount of data to the client by checking the version of the data stored thereon.

For example, when the client requests to restore version 1.0.0.21 data from the server, and the server stores:

1.0.0.0 original

1.0.0.1 added

1.0.0.2 added

...

1.0.0.18 added

1.0.0.19 added

1.0.0.19 full

1.0.0.20 added

1.0.0.21 added

1.0.0.22 added

1.0.0.23 added

At this point, the server may choose to send the client a

1.0.0.0 original

1.0.0.1 added

1.0.0.2 added

...

1.0.0.19 added

1.0.0.20 added

1.0.0.21 added,

You can also choose to send the client

1.0.0.19 full

1.0.0.20 added

1.0.0.21 added.

According to a preferred implementation manner, the server may decide which way to send the data according to the amount of data to be sent. In this example, if the latter data volume is smaller, you can choose to send only the full data of version 1.0.0190 and the incremental data of versions 1.0.0.20 and 1.0.0.21.

FIG. 8 shows a system architecture diagram of a data updating method according to a second embodiment of the present invention. As shown in Fig. 8, the basic structure is similar to that of the first embodiment.

However, the server in the second embodiment also includes a threshold control module, which is used to set the first threshold and the second threshold, and according to the first threshold, control the communication module to send an update to upload the full amount to the upload server According to the instruction of the later data, and according to the second threshold, control the data storage module of the server to delete the data of the earlier version, so that the stored data version is not more than the second threshold.

Moreover, the threshold control module is also used to control which versions of data the communication module sends to the download client. The specific control method is as described above, and will not be repeated here.

The algorithms and displays presented herein are not inherently related to any particular computer, virtual system, or other device. Various generic systems can also be used with the teachings based on this. The structure required to construct such a system is apparent from the above description. Furthermore, the present invention is not specific to any particular programming language. It should be understood that various programming languages can be used to implement the content of the present invention described herein, and the above description of specific languages is for disclosing the best mode of the present invention.

In the description provided herein, numerous specific details are set forth. However, it is understood that embodiments of the invention may be practiced without these specific details. In some instances, well-known methods, structures and techniques have not been shown in detail in order not to obscure the understanding of this description.

Similarly, it should be appreciated that in the foregoing description of exemplary embodiments of the invention, in order to streamline this disclosure and to facilitate an understanding of one or more of the various inventive aspects, various features of the invention are sometimes grouped together in a single embodiment, figure, or its description. This method of disclosure, however, is not to be interpreted as reflecting an intention that the claimed invention requires more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive aspects lie in less than all features of a single foregoing disclosed embodiment. Thus, the claims following the Detailed Description are hereby expressly incorporated into this Detailed Description, with each claim standing on its own as a separate embodiment of this invention.

Those skilled in the art can understand that the modules in the device in the embodiment can be adaptively changed and arranged in one or more devices different from the embodiment. Modules or units or components in the embodiments may be combined into one module or unit or component, and furthermore may be divided into a plurality of sub-modules or sub-units or sub-assemblies. All features disclosed in this specification (including accompanying claims, abstract and drawings) and any method or method so disclosed may be used in any combination, except that at least some of such features and/or processes or units are mutually exclusive. All processes or units of equipment are combined. Each feature disclosed in this specification (including accompanying claims, abstract and drawings) may be replaced by alternative features serving the same, equivalent or similar purpose, unless expressly stated otherwise.

Furthermore, those skilled in the art will understand that although some embodiments described herein include some features included in other embodiments but not others, combinations of features from different embodiments are meant to be within the scope of the invention. and form different embodiments. For example, in the following claims, any of the claimed embodiments may be used in any combination.

The various component embodiments of the present invention may be implemented in hardware, or in software modules running on one or more processors, or in a combination thereof. Those skilled in the art should understand that a microprocessor or a digital signal processor (DSP) may be used in practice to implement some or all functions of some or all components in the device according to the embodiments of the present invention. The present invention can also be implemented as an apparatus or an apparatus program (for example, a computer program and a computer program product) for performing a part or all of the methods described herein. Such a program for realizing the present invention may be stored on a computer-readable medium, or may be in the form of one or more signals. Such a signal may be downloaded from an Internet site, or provided on a carrier signal, or provided in any other form.

It should be noted that the above-mentioned embodiments illustrate rather than limit the invention, and that those skilled in the art will be able to design alternative embodiments without departing from the scope of the appended claims. In the claims, any reference signs placed between parentheses shall not be construed as limiting the claim. The word "comprising" does not exclude the presence of elements or steps not listed in a claim. The word "a" or "an" preceding an element does not exclude the presence of a plurality of such elements. The invention can be implemented by means of hardware comprising several distinct elements, and by means of a suitably programmed computer. In a unit claim enumerating several means, several of these means can be embodied by one and the same item of hardware. The use of the words first, second, and third, etc. does not indicate any order. These words can be interpreted as names.

Claims (9)

1., by a method for data processing equipment Share update data, described data processing equipment storage has the data before renewal With update after data, and data exchange can be carried out with a server, the method comprises the steps:

Described data processing equipment is according to the data before updating and the data genaration incremental data after updating, and by this incremental data It is sent to this server, in order to this server number after this renewal shared by other data processing equipments being connected to server According to, wherein said incremental data refers to the data relative to the change of the data before updating of the data after updating；

Wherein, described data processing equipment is client；When the number of versions of data reaches first threshold, this server requirement Upload client and the data after the renewal of the full dose of latest edition are sent to this server, preserve this full dose on that server Renewal after data；When the versions of data quantity on described server reaches Second Threshold, delete the data of older version, To keep the number of versions of data to be not more than this Second Threshold；When user end to server asks more new data every time, server The more new data of latest edition is sent to this client, the renewal that more new data is incremental data or full dose of this latest edition After data.

2. as claimed in claim 1 by the method for data processing equipment Share update data, described incremental data is by right Data before described renewal and the data after renewal calculate and obtain.

3. the method obtaining more new data, is applied in data processing equipment, preserves and need in described data processing equipment The data updated, and it can carry out data exchange with a server, the method includes:

Described data processing equipment receives data from described server, and described data include incremental data；Wherein, described data Processing means is client；When the number of versions of data reaches first threshold, this server requirement uploads client by up-to-date Data after the renewal of the full dose of version are sent to this server, preserve the data after the renewal of this full dose on that server； When the versions of data quantity on described server reaches Second Threshold, delete the data of older version, to keep versions of data Number be not more than this Second Threshold；When user end to server asks more new data every time, server is by latest edition more New data is sent to this client, the data after the renewal that more new data is incremental data or full dose of this latest edition；

The data to be updated that described data processing equipment preserves according to it produce, with received data, the data being updated over.

The method obtaining more new data the most as claimed in claim 3, before described data processing equipment obtains described data, Described data processing equipment sends the request of a more new data to described server.

The method obtaining more new data the most as claimed in claim 4, the request of described more new data includes that these data process The version information of the data to be updated preserved in device.

The method obtaining more new data the most as claimed in claim 4, the request of described more new data includes required data The version information of version.

7. a data processing equipment, for Share update data, described data processing equipment storage have the data before renewal and Data after renewal, and data exchange can be carried out with a server, this data processing equipment includes:

Incremental data generation module, for according to the data genaration incremental data after the data before updating and renewal, wherein said Incremental data refers to the data relative to the change of the data before updating of the data after updating；

Communication module, is used for transmitting data to described server, and described data include this incremental data；Wherein, described data Processing means is client；When the number of versions of data reaches first threshold, this server requirement uploads client by up-to-date Data after the renewal of the full dose of version are sent to this server, preserve the data after the renewal of this full dose on that server； When the versions of data quantity on described server reaches Second Threshold, delete the data of older version, to keep versions of data Number be not more than this Second Threshold；When user end to server asks more new data every time, server is by latest edition more New data is sent to this client, the data after the renewal that more new data is incremental data or full dose of this latest edition.

8. a data processing equipment, is used for receiving more new data, and described data processing equipment storage has data to be updated, and Can carry out data exchange with a server, this data processing equipment includes:

Communication module, for receiving data from described server, described data include that incremental data, described incremental data refer to more Data after Xin are relative to the data of the change of the data before updating；

Wherein, described data processing equipment is client；When the number of versions of data reaches first threshold, this server requirement Upload client and the data after the renewal of the full dose of latest edition are sent to this server, preserve this full dose on that server Renewal after data；When the versions of data quantity on described server reaches Second Threshold, delete the data of older version, To keep the number of versions of data to be not more than this Second Threshold；When user end to server asks more new data every time, server The more new data of latest edition is sent to this client, the renewal that more new data is incremental data or full dose of this latest edition After data；

Data update module, for producing, with the data got, the data being updated over according to these data to be updated.

9. for carrying out a system for data renewal, including uploading data processing equipment, downloading data processing equipment and service Device, described in upload data processing equipment and download in data processing equipment and preserve data, and all can carry out with this server Data exchange, it is characterised in that:

Described data processing equipment of uploading is for according to the data genaration incremental data after the data before updating and renewal, Qi Zhongsuo State incremental data and refer to the data of change relative to the data before updating of the data after updating, described in upload data processing equipment It is additionally operable to transmit data to this server；

Described server receives and preserves these data, and the described download data that are sent at least partially in these data is processed Device；

Wherein, upload data processing equipment, download data processing equipment is client；When the number of versions of data reaches the first threshold During value, this server requirement is uploaded client and the data after the renewal of the full dose of latest edition is sent to this server, at this The data after the renewal of this full dose are preserved on server；When the versions of data quantity on described server reaches Second Threshold, Delete the data of older version, to keep the number of versions of data to be not more than this Second Threshold；User end to server please every time When seeking more new data, the more new data of latest edition is sent to this client by server, and the more new data of this latest edition is Data after the renewal of incremental data or full dose；

Described download data processing equipment is for receiving described data from described server, and connects with this according to data to be updated The data received produce the data being updated over.