WO2018219178A1

WO2018219178A1 - Data synchronization method and apparatus, server, and storage medium

Info

Publication number: WO2018219178A1
Application number: PCT/CN2018/087867
Authority: WO
Inventors: 林立安; 刘金; 谢世营; 陆居洪
Original assignee: Oppo广东移动通信有限公司
Priority date: 2017-05-27
Filing date: 2018-05-22
Publication date: 2018-12-06
Also published as: CN107172169A

Abstract

A data synchronization method and apparatus, a server, and a storage medium. The data synchronization method comprises: obtaining data version identifiers of data to be synchronized of multiple pieces of user equipment under a current account when a data synchronization request is received; determining the latest data version identifier from the multiple obtained data version identifiers; obtaining the data to be synchronized from a source device corresponding to the latest data version identifier under the current account; and updating the data to be synchronized on a server.

Description

Data synchronization method, device, server and storage medium

This application claims the priority of the Chinese Patent Application filed on May 27, 2017, the Chinese Patent Office, Application No. 201710392634.X, entitled "Data Synchronization Method, Apparatus, Server, and Storage Medium", the entire contents of which are incorporated by reference. Combined in this application.

Technical field

The present application relates to the field of communications technologies, and in particular, to a data synchronization method, apparatus, server, and storage medium.

Background technique

In recent years, with the development of communication technology and the rapid update of digital device hardware performance, more and more users have multiple digital devices. For example, the same user can have an office PC, a home entertainment PC, a smartphone, and even a tablet.

On the other hand, there is a growing need for users to use the same file on multiple different devices. For example, users need to implement editing of the same file on different devices. In order to improve the security of operations on the same file between multiple user devices, it is necessary to synchronize the operations of the same file on different devices to the server.

Summary of the invention

The embodiment of the present application provides a data synchronization method, device, server, and storage medium, which can improve the timeliness of data synchronization.

In a first aspect, an embodiment of the present application provides a data synchronization method, including:

When receiving the data synchronization request, acquiring a data version identifier of the to-be-synchronized data of the plurality of user equipments in the current account, where the plurality of user equipments are devices that establish a data synchronization mechanism with the server;

Determining the latest data version identifier from the obtained plurality of data version identifiers;

Obtaining the to-be-synchronized data from the source device corresponding to the latest data version identifier in the current account;

The data to be synchronized on the server is updated.

In a second aspect, the embodiment of the present application further provides a data synchronization apparatus, including:

a first acquiring module, configured to acquire, when receiving a data synchronization request, a data version identifier of the data to be synchronized of the plurality of user equipments in the current account, where the multiple user equipments are devices that establish a data synchronization mechanism with the server;

a first determining module, configured to determine a latest data version identifier from the obtained multiple data version identifiers;

a second acquiring module, configured to acquire the to-be-synchronized data from a source device corresponding to the latest data version identifier in the current account;

a synchronization module, configured to update the to-be-synchronized data on the server.

In a third aspect, the embodiment of the present application further provides a server, including a memory storing executable program code and a processor coupled to the memory, wherein the processor invokes the executable program code to implement the following steps:

When receiving the data synchronization request, acquiring a data version identifier of the data to be synchronized of the plurality of user equipments in the current account, where the multiple user equipments are devices that establish a data synchronization mechanism with the server;

Obtaining the to-be-synchronized data from a source device corresponding to the latest data version identifier in the current account;

The to-be-synchronized data on the server is updated.

In a fourth aspect, the embodiment of the present application further provides a storage medium, where the storage medium stores a plurality of instructions, and the instruction is adapted to be loaded by a processor to execute the data synchronization method.

DRAWINGS

In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings used in the description of the embodiments will be briefly described below. Obviously, the drawings in the following description are only some embodiments of the present application, and those skilled in the art can obtain other drawings according to the drawings without any creative work.

FIG. 1 is a schematic flowchart diagram of a data synchronization method provided by an embodiment of the present application.

FIG. 2 is another schematic flowchart of a data synchronization method provided by an embodiment of the present application.

FIG. 3 is still another schematic flowchart of a data synchronization method provided by an embodiment of the present application.

FIG. 4 is a schematic diagram of an application scenario of a data synchronization method according to an embodiment of the present application.

FIG. 5 is a schematic diagram of another application scenario of the data synchronization method provided by the embodiment of the present application.

FIG. 6 is a schematic diagram of still another application scenario of the data synchronization method provided by the embodiment of the present application.

FIG. 7 is a schematic structural diagram of a data synchronization apparatus according to an embodiment of the present application.

FIG. 8 is another schematic structural diagram of a data synchronization apparatus according to an embodiment of the present application.

FIG. 9 is still another schematic structural diagram of a data synchronization apparatus according to an embodiment of the present application.

FIG. 10 is a schematic diagram of still another structure of a data synchronization apparatus according to an embodiment of the present application.

FIG. 11 is a schematic structural diagram of a server provided by an embodiment of the present application.

FIG. 12 is another schematic structural diagram of a server provided by an embodiment of the present application.

detailed description

The technical solutions in the embodiments of the present application will be clearly and completely described in the following with reference to the accompanying drawings in the embodiments. It is apparent that the described embodiments are only a part of the embodiments of the present application, and not all of them. All other embodiments obtained by a person skilled in the art based on the embodiments of the present application without creative efforts are within the scope of the present application.

The terms "first", "second", "third", etc. (if present) in the specification and claims of the present application and the above figures are used to distinguish similar objects, and are not necessarily used to describe a particular order. Or prioritization. It should be understood that the objects so described are interchangeable where appropriate. Moreover, the terms "comprising" and "having" and "the" are intended For example, a process, method, or apparatus, computer device, system that comprises a series of modules or units, is not necessarily limited to those steps or modules or units that are clearly listed, and may include steps that are not explicitly listed Or modules or units may also include other steps or modules or units inherent to such processes, methods, apparatus, computer devices or systems.

An embodiment of the present application provides a data synchronization method, including:

The to-be-synchronized data on the server is updated.

In some embodiments, after the step of updating the data to be synchronized on the server, the data synchronization method further includes:

Determining, by the target device, a device whose data version identifier in the plurality of user devices is different from the data version identifier of the source device;

Pushing data update information to the target device.

In some embodiments, the data version identifier includes a timestamp, and the step of determining the latest data version identifier from the obtained plurality of data version identifiers includes:

Checking the obtained multiple timestamps to determine a timestamp that meets the preset condition;

The latest data version identifier is determined based on the timestamp that meets the preset conditions.

Obtaining a timestamp of the to-be-synchronized data on the server;

The timestamp of the data to be synchronized on the server is modified to the current time.

Extracting the timestamp of each data version identifier from multiple data version identifiers;

Determining a timestamp closest to the current time from the extracted plurality of timestamps;

The data version identifier corresponding to the timestamp closest to the current time is determined as the latest data version identifier.

In some embodiments, when the data synchronization request is received, the step of acquiring data version identifiers of the plurality of user equipments includes:

Generating a data synchronization request every preset period;

Obtaining data version identifiers of the plurality of user equipments according to the data synchronization request.

A data synchronization method that can be applied to a server. As shown in FIG. 1, the data synchronization method may include the following steps:

S110. Acquire, when receiving the data synchronization request, a data version identifier of the to-be-synchronized data of the multiple user equipments in the current account, where the multiple user equipments are devices that establish a data synchronization mechanism with the server.

In some embodiments, when the server receives the data synchronization request, the plurality of user devices that establish a data synchronization mechanism with the server under the account that the current user has logged in acquires the data version identifier of the data to be synchronized of the plurality of user devices. The plurality of user devices include, but are not limited to, electronic devices such as smart phones, tablet computers, and personal PCs.

The data to be synchronized may include one or more of an album, an address book, a call record, a short message, a browser record, a note, and the like.

The data synchronization request is used to complete data synchronization between the server and multiple user devices of the current user. It can be understood that the current user is the user to which the account currently logged in on the server belongs. The data synchronization request may be sent by one of the multiple user equipments to the server, or may be initiated by the server. For example, whenever data on one of the plurality of user devices changes, the device automatically sends a data synchronization request to the server. For another example, whenever the time reaches the preset timing, the server initiates a data synchronization request and processes the data synchronization request.

The data synchronization mechanism is used to establish a data synchronization relationship between the plurality of user equipments and the server. That is, whenever the data on one of the plurality of user devices changes, the corresponding modification is also performed on the server; or each time the data on the server is changed, the corresponding information is also performed on the multiple user devices. Modifications.

A data version identifier is preset in each of the plurality of user devices and on the server. The data version identifier is used to record a version of the data on the device to compare the difference between the data on the device and the data on the server. For example, the data version identifier can include the version number of the data. The higher the version number of the data, the shorter the time the data was last updated from the current time. Wherein, the version number of the data can be associated with the time when the data was changed. The data version number is different when the data on the same device changes at different times. The data version number is different when the same type of data on different devices changes at different times. Whenever a device synchronizes data with the server, it updates the data version identifier on the device and the server.

Among them, a unified data version identifier can be set for all data on each device, that is, one device has only one data version identifier. It is also possible to set the data version identifier separately for different types of data on each device. For example, a data version identifier is set for the communication data, a data version identifier is set for the album data, and a data version identifier is set for other data. At this point, whenever data synchronization occurs on the server, only the type data that has changed is synchronized.

Referring to FIG. 4, a server and a plurality of electronic devices A, B, C, and D form a data synchronization system. Devices A, B, C, and D all establish communication with the server. A data version identifier is set on each device and the server, and the data version identifier may include a time stamp. This timestamp can be the time when a device last synchronized data with the server.

It should be noted that in the above data synchronization system, the user can operate on data on any of the devices A, B, C, and D, but cannot directly operate on the data on the server. This operation includes, but is not limited to, adding, deleting, modifying, accessing files, and the like.

In some embodiments, a user may log into a personal account in the server via a personal PC (or other device) and operate on files in the personal account. This operation is considered as a user's operation on a personal PC (or other device), and the personal PC (or other device) is understood as a device in the data synchronization system.

In some embodiments, as shown in FIG. 2, when receiving the data synchronization request, acquiring the data version identifiers of the plurality of user equipments may include the following steps:

S111. Generate a data synchronization request every preset period.

S112. Acquire a data version identifier of multiple user equipments according to the data synchronization request.

In some embodiments, timing can be set on the server, and whenever the time reaches the timing, the server automatically triggers a data synchronization operation. For example, the user can set the server to automatically perform data synchronization operations at 8 am every day. Then, during the running of the server, the timing system continuously determines whether the current time is the preset time. If it is a preset time, the server's timing system automatically generates a data synchronization request. The processor of the server receives the data synchronization request, and acquires a data version identifier of the plurality of user equipments according to the data synchronization request.

It should be noted that the above timing synchronization operation is only an example. In some embodiments, the user can set a preset period on the server. The server automatically generates a data synchronization request every time the preset period is interrupted, and then acquires the data version identifiers of the plurality of user equipments according to the data synchronization request. For example, the preset period can be 10 minutes. Then, the server automatically generates a data synchronization request every 10 minutes, and performs data synchronization operation.

S120. Determine a latest data version identifier from the obtained multiple data version identifiers.

In some embodiments, after the server obtains the data version identifiers of the plurality of user devices, the latest data version identifier is determined from the plurality of data version identifiers. The latest data version identifier indicates that in the above data synchronization system, the data on the device corresponding to the latest data version identifier is the latest.

For example, the user has performed operations on the data on the device A, and then has performed operations on the data on the device B. Finally, the data on the device C has been operated. Thereafter, none of the devices A, B, C, and D are operated. When a device has been operated, the data on device C is the latest data, and the data version corresponding to device C is identified as the latest data version identifier.

In some embodiments, as shown in FIG. 2, the data version identifier may include a timestamp, and determining the latest data version identifier from the obtained plurality of data version identifiers may include the following steps:

S121. Extract respective timestamps from multiple data version identifiers.

S122. Determine, from the extracted multiple timestamps, a timestamp that is closest to the current time.

S123: Determine the data version identifier corresponding to the timestamp closest to the current time as the latest data version identifier.

The data version identifier may include a timestamp, where the timestamp may be the time when a device last synchronized data with the server. For example, the last time that device A synchronizes data with the server is 8:00 am on February 10, 2017, the time stamp in the data version identifier of device A may be 201702100800.

After the server obtains the data version identifiers of the multiple user devices, the time stamp of each data version identifier is extracted from the multiple data version identifiers. Then, the time represented by the extracted timestamp is compared with the current time, so that the timestamp closest to the current time is determined, and the data version identifier corresponding to the timestamp is determined as the latest data version identifier.

For example, if the time represented by the time stamp 201702140800 in the data version identifier of the device D is closest to the current time, the time stamp may be determined to be the timestamp closest to the current time. Subsequently, the data version identification of device D is determined to be the latest data version identification.

In some embodiments, the server may check the extracted multiple timestamps to determine a timestamp that meets the preset condition from the extracted plurality of timestamps. The preset condition may be a condition such as a format set in advance for the time stamp.

For example, the preset condition can limit the length of the timestamp to 12 digits. Because the server or multiple user devices may have errors during the update and management of the timestamp, or an error occurs during the data transmission between the server and the user device, the timestamp format extracted by the server is not Eligible, for example, the extracted timestamp is not 12 digits.

After verifying the extracted multiple timestamps, the server determines the latest data version identifier according to the timestamp that meets the preset condition. For example, the timestamp closest to the current time is determined from the timestamps that meet the preset conditions, and then the data version identifier corresponding to the timestamp is determined as the latest data version identifier.

S130. Acquire the to-be-synchronized data from the source device corresponding to the latest data version identifier.

S140. Update the to-be-synchronized data on the server.

In some embodiments, after the server determines the latest data version identifier, the data to be synchronized can be obtained from the source device corresponding to the latest data version identifier, and the data to be synchronized on the server is updated.

The source device is a device corresponding to the latest data version identifier among the plurality of user equipments. When a device has only one data version identifier, the data to be synchronized is all data on the source device. When different types of data on a device have different data version identifiers, the data to be synchronized is the type data that has changed on the source device.

Among them, the user account on the server can remain logged in. After the server obtains the data to be synchronized, the data to be synchronized is stored in the file directory under the current user account, and the data synchronization between the server and the source device can be completed.

In some embodiments, as shown in FIG. 3, after the data to be synchronized is stored in the server, the data synchronization method may further include the following steps:

S150. Obtain a timestamp of the to-be-synchronized data on the server.

S160. Modify a timestamp of the data to be synchronized on the server to a current time.

In some embodiments, after the server completes the data synchronization, the timestamp of the data to be synchronized on the server may be updated.

Wherein, when data on one of the plurality of user devices changes, the device may send a data synchronization request to the server. After the server completes data synchronization with the device, the timestamp in the data version identifier of the server itself is changed to the current time. At the same time, the server can also send a timestamp modification instruction to the device. After receiving the timestamp modification instruction, the device modifies the timestamp in the data version identifier of the data to the current time according to the instruction. At this point, the timestamp update in the data version ID of the server and source device is complete.

S170. Determine a target device, where the target device is a device whose data version identifier is different from the data version identifier of the source device.

S180. Push data update information to the target device.

In some embodiments, after the server completes data synchronization with the source device, data synchronization with the remaining devices can be further completed.

After the server completes the data synchronization, the target device can be determined. The target device is a device in which the data version identifier of the plurality of user devices is different from the data version identifier of the source device. For example, in the devices A, B, C, and D, the device D is the source device, and the data version identifiers of the devices A, B, and C are different from the data version identifiers of the device D, and the target device includes the devices A and B. C.

The server can determine the target device by using the timestamp in the data version identifier. For example, if the device D is the source device and the time stamp in the data version identifier of the device A, B, and C is different from the time stamp in the data version identifier of the device D, the devices A, B, and C may be determined as the target device.

After the server determines the target device, it pushes data update information to the target device. The data update information is used to enable the target device to acquire the data to be synchronized from the server. After receiving the data update information pushed by the server, the target device acquires the data to be synchronized from the server to complete data synchronization on the target device. Further, after the target device completes the data synchronization, the timestamp in the data version identifier may be updated, and the timestamp is modified to be the timestamp in the data version identifier of the server.

Referring to FIG. 5, the data synchronization process in the data synchronization system can be divided into two stages: server data synchronization and target device data synchronization. In the server data synchronization phase, the server receives the data synchronization request sent by the source device, or receives the data synchronization request generated by the server itself, and then acquires the data to be synchronized from the source device, and then performs data update on the server.

In the target device data synchronization phase, the target device receives the data update information pushed by the server, and then the target device acquires the data to be synchronized from the server, and then performs data update on the target device.

Referring to FIG. 6, after the data synchronization is completed between the server and the target device, the data on the server, the source device, and the target device are consistent, and the data version identifiers on the server, the source device, and the target device are also consistent. The timestamps in the data version identifiers on the server, the source device, and the target device are consistent.

In the specific implementation, the present application is not limited by the execution order of the various steps described, and some steps may be performed in other orders or simultaneously without conflict.

For example, when the server receives the album synchronization request sent by the user's mobile phone, the album version identifiers on the respective devices are respectively obtained from the mobile phone, the tablet computer, and the personal computer. Subsequently, the latest version identifier is determined from the obtained plurality of album version identifiers. For example, if the album version of the mobile phone is identified as the latest version identifier, the photos to be synchronized are acquired from the mobile phone, and then the photos to be synchronized are stored to the server. Further, after completing the synchronization on the server side, the server may separately send the photos to be synchronized to the tablet computer and the personal computer. Subsequently, the tablet and the personal computer store the received photos separately.

For another example, when the server receives the address book synchronization request sent by the user's mobile phone, the server obtains the address book version identifier on each device from the mobile phone, the tablet computer, and the personal computer. Subsequently, the latest version identifier is determined from the obtained plurality of address book version identifiers. For example, if the address book version of the mobile phone is identified as the latest version identifier, the address book information to be synchronized is obtained from the mobile terminal, and then the address book information to be synchronized is stored in the server. Further, after completing the synchronization on the server side, the server may separately send the address book information to be synchronized to the tablet computer or the personal computer. Subsequently, the tablet computer and the personal computer respectively store the received address book information.

As can be seen from the above, the data synchronization method provided by the embodiment of the present application, when receiving the data synchronization request, acquires the data version identifier of the data to be synchronized of the plurality of user equipments in the current account; and determines from the obtained multiple data version identifiers. The latest data version identifier is obtained; the source device corresponding to the latest data version identifier is obtained from the current account, and the to-be-synchronized data on the server is updated. When receiving the data synchronization request, the solution obtains the data version identifiers of the plurality of user equipments, and determines the latest data version identifier, and then obtains the data to be synchronized and updates the data from the source device corresponding to the latest data version identifier. The data update in multiple user devices can be synchronized to the server in time, thereby improving the timeliness of server data synchronization.

The embodiment of the present application provides a data synchronization apparatus, including:

In some embodiments, the data synchronization device further includes:

a second determining module, configured to determine a target device, where the target device is a device whose data version identifier is different from the data version identifier of the source device in the multiple user devices;

a pushing module, configured to push data update information to the target device.

In some embodiments, the data version identifier includes a timestamp, and the first determining module includes:

a verification submodule, configured to check the obtained multiple timestamps to determine a timestamp that meets a preset condition;

The determining submodule is configured to determine the latest data version identifier according to the timestamp that meets the preset condition.

In some embodiments, the data synchronization device further includes:

a third obtaining module, configured to acquire a timestamp of the to-be-synchronized data on the server;

And a modifying module, configured to modify a timestamp of the to-be-synchronized data on the server to a current time.

In some embodiments, the data version identifier includes a timestamp, and the first determining module is configured to:

In some embodiments, the first obtaining module is configured to:

Generating a data synchronization request every preset period;

The embodiment of the present application further provides a data synchronization device, which can be applied to a server. As shown in FIG. 7, the data synchronization apparatus 200 includes a first acquisition module 201, a first determination module 202, a second acquisition module 203, and a synchronization module 204.

The first obtaining module 201 is configured to acquire, when receiving the data synchronization request, a data version identifier of the data to be synchronized of the plurality of user equipments in the current account, where the multiple user equipments are devices that establish a data synchronization mechanism with the server.

In some embodiments, when the first obtaining module 201 receives the data synchronization request, the plurality of user devices that establish a data synchronization mechanism with the server under the account that the current user has logged in acquire the data to be synchronized of the plurality of user devices. Data version identifier. The plurality of user devices include, but are not limited to, electronic devices such as smart phones, tablet computers, and personal PCs.

In some embodiments, a user may log into a personal account in the server via a personal PC (or other device) and operate on files in the personal account. This operation is considered as a user's operation on a personal PC (or other device), and is not an operation on the server, which is understood as a device in a data synchronization system.

In some embodiments, the first obtaining module 201 is configured to:

Generating a data synchronization request every preset period;

Acquiring data version identifiers of multiple user equipments according to the data synchronization request.

In some embodiments, timing can be set on the server, and whenever the time reaches the timing, the server automatically triggers a data synchronization operation. For example, the user can set the server to automatically perform data synchronization operations at 8 am every day. When the server is running, the first obtaining module 201 continuously determines whether the current time is the preset time. If the time is preset, the first obtaining module 201 automatically generates a data synchronization request, and acquires the data version identifiers of the plurality of user equipments according to the data synchronization request.

It should be noted that the above timing synchronization operation is only an example. In some embodiments, the user can set a preset period on the server. The first obtaining module 201 automatically generates a data synchronization request, and then acquires the data version identifiers of the plurality of user equipments according to the data synchronization request. For example, the preset period can be 10 minutes. Then, the first obtaining module 201 automatically generates a data synchronization request every 10 minutes, and performs a data synchronization operation.

The first determining module 202 is configured to determine the latest data version identifier from the obtained multiple data version identifiers.

In some embodiments, after the first obtaining module 201 acquires the data version identifiers of the plurality of user devices, the first determining module 202 determines the latest data version identifier from the plurality of data version identifiers. The latest data version identifier indicates that in the above data synchronization system, the data on the device corresponding to the latest data version identifier is the latest.

For example, the data synchronization system is composed of a server, devices A, B, C, and D. The user performs operations on the data on the device A, and then performs operations on the data on the device B, and finally performs data on the device C. After the operation, and the device A, B, C, and D are not operated, the data on the device C is the latest data, and the data version corresponding to the device C is the latest data version identifier.

In some embodiments, as shown in FIG. 8 , the data version identifier may include a time stamp, and the first determining module 202 includes: an extraction submodule 2021 , a verification submodule 2022 , and a determination submodule 2023 .

The extraction sub-module 2021 is configured to extract a respective timestamp from the plurality of data version identifiers;

The verification sub-module 2022 is configured to check the extracted multiple timestamps to determine a timestamp that meets a preset condition;

The determining sub-module 2023 is configured to determine a latest data version identifier according to a timestamp that meets a preset condition.

After the first obtaining module 201 obtains the data version identifiers of the plurality of user devices, the time stamps of the respective data version identifiers may be extracted from the plurality of data version identifiers. Then, the verification sub-module 2021 verifies the extracted multiple timestamps to determine a timestamp that meets the preset condition. The determining sub-module 2023 determines the latest data version identifier based on the timestamp that meets the preset condition.

The verification sub-module 2022 can check the extracted multiple timestamps to determine a timestamp that meets the preset condition from the extracted multiple timestamps. The preset condition may be a condition such as a format set in advance for the time stamp.

After the verification sub-module 2022 verifies the extracted multiple timestamps, the determination sub-module 2023 determines the latest data version identifier according to the timestamp that meets the preset condition. For example, the timestamp closest to the current time is determined from the timestamps that meet the preset conditions, and then the data version identifier corresponding to the timestamp is determined as the latest data version identifier.

In some embodiments, when the first determining module 202 determines the latest data version identifier from the obtained multiple data version identifiers, the following steps are performed:

The second obtaining module 203 is configured to acquire the to-be-synchronized data from the source device corresponding to the latest data version identifier.

The synchronization module 204 is configured to update the to-be-synchronized data on the server.

In some embodiments, after the first determining module 202 determines the latest data version identifier, the second obtaining module 203 can obtain the data to be synchronized from the source device corresponding to the latest data version identifier, and the synchronization module 204 will be on the server. The data to be synchronized is updated.

Among them, the user account on the server can remain logged in. After the second obtaining module 203 obtains the data to be synchronized, the synchronization module 204 stores the data to be synchronized into the file directory under the current user account, and the data synchronization between the server and the source device can be completed.

In some embodiments, as shown in FIG. 9, the data synchronization apparatus 200 further includes: a third acquisition module 205, a modification module 206.

The third obtaining module 205 is configured to acquire a timestamp of the to-be-synchronized data on the server.

The modification module 206 is configured to modify a timestamp of the data to be synchronized on the server to a current time.

In some embodiments, after the synchronization module 204 completes the data synchronization, the third obtaining module 205 acquires the timestamp of the data to be synchronized on the server, and the modification module 206 can update the timestamp of the data to be synchronized on the server.

Wherein, when data on one of the plurality of user devices changes, the device may send a data synchronization request to the server. After the synchronization module 204 completes the data synchronization with the device, the modification module 206 modifies the timestamp in the data version identifier of the server itself to the current time. At the same time, the modification module 206 can also send a timestamp modification instruction to the device. After receiving the timestamp modification instruction, the device modifies the timestamp in the data version identifier of the data to the current time according to the instruction. At this point, the timestamp update in the data version ID of the server and source device is complete.

In some embodiments, as shown in FIG. 10, the data synchronization apparatus 200 further includes: a second determination module 207, a push module 208.

The second determining module 207 is configured to determine a target device, where the target device is a device whose data version identifier is different from the data version identifier of the source device.

The pushing module 208 is configured to push data update information to the target device.

After the synchronization module 204 completes the data synchronization, the second determining module 207 can determine the target device. The target device is a device in which the data version identifier of the plurality of user devices is different from the data version identifier of the source device. For example, in the devices A, B, C, and D, the device D is the source device, and the data version identifiers of the devices A, B, and C are different from the data version identifiers of the device D, and the target device includes the devices A and B. C.

The second determining module 207 can determine the target device by using a timestamp in the data version identifier. For example, if the device D is the source device and the time stamp in the data version identifier of the device A, B, and C is different from the time stamp in the data version identifier of the device D, the devices A, B, and C may be determined as the target device.

After the second determining module 207 determines the target device, the pushing module 208 pushes the data update information to the target device. The data update information is used to cause the target device to acquire the data to be synchronized from the server. After receiving the data update information pushed by the server, the target device acquires the data to be synchronized from the server to complete data synchronization on the target device. Further, after the target device completes data synchronization, the timestamp in the data version identifier may be updated, and the timestamp is modified to be a timestamp in the data version identifier of the server.

In the specific implementation, each of the above modules may be implemented as a separate entity, or may be implemented in any combination as one or several entities.

For example, when the server receives the album synchronization request sent by the user's mobile phone, the first obtaining module 201 obtains the album version identifiers on the respective devices from the mobile phone, the tablet computer, and the personal computer. Subsequently, the first determining module 202 determines the latest version identifier from the obtained plurality of album version identifiers. For example, the album version of the mobile phone is identified as the latest version identifier, and the second obtaining module 203 obtains the photos to be synchronized from the mobile terminal, and then the synchronization module 204 stores the photos to be synchronized to the server. Further, after completing the synchronization on the server side, the server may separately send the photos to be synchronized to the tablet computer and the personal computer. Subsequently, the tablet and the personal computer store the received photos separately.

For example, when the server receives the address book synchronization request sent by the user's mobile phone, the first obtaining module 201 obtains the address book version identifiers on the respective devices from the mobile phone, the tablet computer, and the personal computer. Subsequently, the first determining module 202 determines the latest version identifier from the obtained plurality of address book version identifiers. For example, the address book version of the mobile phone is identified as the latest version identifier, and the second obtaining module 203 obtains the address book information to be synchronized from the mobile phone end, and then the synchronization module 204 stores the address book information to be synchronized to the server. Further, after completing the synchronization on the server side, the server may separately send the address book information to be synchronized to the tablet computer or the personal computer. Subsequently, the tablet computer and the personal computer respectively store the received address book information.

As can be seen from the above, the data synchronization apparatus 200 provided by the embodiment of the present application obtains the data version identifier of the data to be synchronized of the plurality of user equipments in the current account when the first synchronization module 201 receives the data synchronization request; the first determining module 202: The latest data version identifier is determined from the obtained multiple data version identifiers; the second obtaining module 203 obtains the to-be-synchronized data from the source device corresponding to the latest data version identifier in the current account; the synchronization module 204 The data to be synchronized on the server is updated. When receiving the data synchronization request, the solution obtains the data version identifiers of the plurality of user equipments, and determines the latest data version identifier, and then obtains the data to be synchronized and updates the data from the source device corresponding to the latest data version identifier. The data update in multiple user devices can be synchronized to the server in time, thereby improving the timeliness of server data synchronization.

The embodiment of the present application further relates to a server, which may be a server located on a network, or may be a computer device such as a personal PC.

As shown in FIG. 11, the server 300 includes a memory 301 and a processor 302. The memory 301 is connected to the processor 302.

Therein, the memory 301 has one or more computer readable storage media. Memory 301 can be used to store applications and data. The application stored in the memory 301 contains executable program code. Applications can form various functional modules. The processor 302 executes various functional applications and data processing by running an application stored in the memory 301. The memory 301 can mainly include a storage program area and a storage data area. The storage program area may store an operating system, an application required for at least one function, and the like, and the storage data area may store data created by the server 300 or exchanged with other electronic devices.

The processor 302 is a control center of the server 300, and connects various parts of the entire server 300 by various interfaces and lines, executes the server 300 by running or executing an application stored in the memory 301, and calling data stored in the memory 301. The various functions and processing data are used to monitor the server 300 as a whole. The processor 302 can include one or more processing cores.

In this embodiment, the processor 302 in the server 300 can load the executable program code corresponding to the process of one or more applications into the memory 301 according to the following instructions, and is stored and stored by the processor 302. The application in memory 301, thereby implementing various functions:

The data to be synchronized on the server is updated.

In some embodiments, the data version identifier includes a timestamp, and when determining the latest data version identifier from the obtained plurality of data version identifiers, the processor 302 is configured to perform the following steps: A check is made to determine a timestamp that meets the preset condition; the latest data version identifier is determined based on the timestamp that meets the preset condition.

In some embodiments, after storing the data to be synchronized to the server, the processor 302 is further configured to: obtain a timestamp of the data to be synchronized on the server; a timestamp of the data to be synchronized on the server Change to the current time.

In some embodiments, after storing the data to be synchronized to the server, the processor 302 is further configured to: determine a target device, where the target device identifies a data version different from the source device in the plurality of user devices. The identified device; pushes data update information to the target device.

In some embodiments, the data version identifier includes a timestamp, and when determining the latest data version identifier from the obtained plurality of data version identifiers, the processor 302 is configured to perform the following steps: extracting from the plurality of data version identifiers a timestamp of each data version identifier; determining a timestamp that is closest to the current time from the extracted plurality of timestamps; determining a data version identifier corresponding to the timestamp closest to the current time as the latest data version identifier .

In some embodiments, when the data synchronization request is received, the data version identifiers of the plurality of user equipments are acquired, and the processor 302 is configured to: generate a data synchronization request every preset period; according to the data synchronization request Get the data version identifier of multiple user devices.

In some embodiments, as shown in FIG. 12, the server 300 further includes a communication unit 303. The communication unit 303 is connected to the processor 302. The communication unit 303 can communicate with the network device or other electronic devices through the network to complete the information transmission and reception between the server 300 and the network device or other electronic devices. For example, the communication unit 303 can communicate with other servers or electronic devices such as smart phones, tablets, and the like through a network.

In the foregoing embodiments, the descriptions of the various embodiments are different, and the details are not described in detail in the specific embodiments. For details, refer to the foregoing detailed description of the data synchronization method, and details are not described herein.

The embodiment of the present application further provides a storage medium, where the storage medium stores a plurality of instructions, and the instructions are adapted to be loaded by a processor to execute the data synchronization method described in any of the foregoing embodiments.

It should be noted that those skilled in the art can understand that all or part of the steps of the foregoing embodiments can be completed by a program to instruct related hardware, and the program can be stored in a computer readable storage medium and stored. The medium may include: a read only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, and the like.

The data synchronization method, the device, the server, and the storage medium provided by the embodiments of the present application are described in detail. The principles and implementation manners of the application are described in the specific examples. The description of the above embodiments is only used to help understand The method of the present application and its core idea. In the meantime, those skilled in the art will be able to change the specific embodiments and the scope of the application according to the idea of the present application. In the above, the content of the specification should not be construed as limiting the present application.

Claims

A data synchronization method includes:

When receiving the data synchronization request, acquiring a data version identifier of the data to be synchronized of the plurality of user equipments in the current account, where the multiple user equipments are devices that establish a data synchronization mechanism with the server;

Determining the latest data version identifier from the obtained plurality of data version identifiers;

Obtaining the to-be-synchronized data from a source device corresponding to the latest data version identifier in the current account;

The to-be-synchronized data on the server is updated.
The data synchronization method according to claim 1, wherein after the step of updating the data to be synchronized on the server, the data synchronization method further comprises:

Determining, by the target device, a device whose data version identifier in the plurality of user devices is different from the data version identifier of the source device;

Pushing data update information to the target device.
The data synchronization method according to claim 1, wherein the data version identifier comprises a timestamp, and the step of determining the latest data version identifier from the obtained plurality of data version identifiers comprises:

Checking the obtained multiple timestamps to determine a timestamp that meets the preset condition;

The latest data version identifier is determined based on the timestamp that meets the preset conditions.
The data synchronization method according to claim 3, wherein after the step of updating the data to be synchronized on the server, the data synchronization method further comprises:

Obtaining a timestamp of the to-be-synchronized data on the server;

The timestamp of the data to be synchronized on the server is modified to the current time.
The data synchronization method according to claim 1, wherein the data version identifier comprises a timestamp, and the step of determining the latest data version identifier from the obtained plurality of data version identifiers comprises:

Extracting the timestamp of each data version identifier from multiple data version identifiers;

Determining a timestamp closest to the current time from the extracted plurality of timestamps;

The data version identifier corresponding to the timestamp closest to the current time is determined as the latest data version identifier.
The data synchronization method according to claim 1, wherein the step of acquiring the data version identifiers of the plurality of user equipments when the data synchronization request is received comprises:

Generating a data synchronization request every preset period;

Obtaining data version identifiers of the plurality of user equipments according to the data synchronization request.
A data synchronization device comprising:

a first acquiring module, configured to acquire, when receiving a data synchronization request, a data version identifier of the data to be synchronized of the plurality of user equipments in the current account, where the multiple user equipments are devices that establish a data synchronization mechanism with the server;

a first determining module, configured to determine a latest data version identifier from the obtained multiple data version identifiers;

a second acquiring module, configured to acquire the to-be-synchronized data from a source device corresponding to the latest data version identifier in the current account;

a synchronization module, configured to update the to-be-synchronized data on the server.
The data synchronization device of claim 7, wherein the data synchronization device further comprises:

a second determining module, configured to determine a target device, where the target device is a device whose data version identifier is different from the data version identifier of the source device in the multiple user devices;

a pushing module, configured to push data update information to the target device.
The data synchronization device of claim 7, wherein the data version identifier comprises a time stamp, and the first determining module comprises:

a verification submodule, configured to check the obtained multiple timestamps to determine a timestamp that meets a preset condition;

The determining submodule is configured to determine the latest data version identifier according to the timestamp that meets the preset condition.
The data synchronization device of claim 9, wherein the data synchronization device further comprises:

a third obtaining module, configured to acquire a timestamp of the to-be-synchronized data on the server;

And a modifying module, configured to modify a timestamp of the to-be-synchronized data on the server to a current time.
The data synchronization device according to claim 7, wherein the data version identifier includes a time stamp, and the first determining module is configured to:

Extracting the timestamp of each data version identifier from multiple data version identifiers;

Determining a timestamp closest to the current time from the extracted plurality of timestamps;

The data version identifier corresponding to the timestamp closest to the current time is determined as the latest data version identifier.
The data synchronization device of claim 7, wherein the first acquisition module is configured to:

Generating a data synchronization request every preset period;

Obtaining data version identifiers of the plurality of user equipments according to the data synchronization request.
A server comprising a memory storing executable program code and a processor coupled to the memory, wherein the processor calls the executable program code to implement the following steps:

When receiving the data synchronization request, acquiring a data version identifier of the data to be synchronized of the plurality of user equipments in the current account, where the multiple user equipments are devices that establish a data synchronization mechanism with the server;

Determining the latest data version identifier from the obtained plurality of data version identifiers;

Obtaining the to-be-synchronized data from a source device corresponding to the latest data version identifier in the current account;

The to-be-synchronized data on the server is updated.
The server according to claim 13, wherein after the data to be synchronized on the server is updated, the processor calls the executable program code to further implement the following steps:

Determining, by the target device, a device whose data version identifier in the plurality of user devices is different from the data version identifier of the source device;

Pushing data update information to the target device.
The server according to claim 13, wherein the data version identifier includes a time stamp, and the processor calls the executable program code when determining the latest data version identifier from the obtained plurality of data version identifiers Implement the following steps:

Checking the obtained multiple timestamps to determine a timestamp that meets the preset condition;

The latest data version identifier is determined based on the timestamp that meets the preset conditions.
The server according to claim 15, wherein after the data to be synchronized on the server is updated, the processor calls the executable program code to further implement the following steps:

Obtaining a timestamp of the to-be-synchronized data on the server;

The timestamp of the data to be synchronized on the server is modified to the current time.
The server according to claim 13, wherein the data version identifier includes a time stamp, and the processor calls the executable program code when determining the latest data version identifier from the obtained plurality of data version identifiers Implement the following steps:

Extracting the timestamp of each data version identifier from multiple data version identifiers;

Determining a timestamp closest to the current time from the extracted plurality of timestamps;

The data version identifier corresponding to the timestamp closest to the current time is determined as the latest data version identifier.
The server according to claim 13, wherein when the data version identification of the plurality of user devices is acquired when the data synchronization request is received, the processor calls the executable program code to implement the following steps:

Generating a data synchronization request every preset period;

Obtaining data version identifiers of the plurality of user equipments according to the data synchronization request.
A storage medium having stored therein a plurality of instructions adapted to be loaded by a processor to perform the data synchronization method of any one of claims 1 to 6.