WO2022022546A1

WO2022022546A1 - Data synchronization method and device for mobile distributed system

Info

Publication number: WO2022022546A1
Application number: PCT/CN2021/108814
Authority: WO
Inventors: 陈刚; 刘钲
Original assignee: 华为技术有限公司
Priority date: 2020-07-31
Filing date: 2021-07-28
Publication date: 2022-02-03
Also published as: CN114095511A; CN114095511B

Abstract

The present application provides a data synchronization method and device for a mobile distributed system. The method can realize data synchronization of a mobile distributed system. The method comprises: a first device sending a first query request to a second device; the first device receiving a first synchronization message sent by the second device, wherein the first synchronization message carries first media asset change content of the second device, the first media asset change content comprising a first media asset that is changed and an action corresponding to the changing of the first media asset; and the first device generating a first synchronization record according to the first synchronization message, the first synchronization record comprising a first synchronization node, a first change list and a first device list, wherein the first synchronization node is used for recording first data synchronization information, the first change list records the first media asset that is changed during the first data synchronization and the action corresponding to the changing of the first media asset, and the first device list is used for recording a device on which the first data synchronization is carried out.

Description

A method and device for data synchronization in a mobile distributed system

This application claims the priority of the Chinese patent application filed on July 31, 2020 with the application number of 202010763598.5 and titled "A method and device for data synchronization of mobile distributed systems", the entire contents of which are by reference Incorporated in this application.

technical field

The present application relates to the field of terminals, and more particularly, to a method and device for data synchronization in a mobile distributed system.

Background technique

Mobile distributed system is a brand new distributed system, which is different from traditional distributed system. For example, the traditional distributed system is a master-slave mechanism, while the mobile distributed system is a peer-to-peer distributed system. The system member devices are equal, and there is no master-slave relationship; the traditional distributed system requires the system member devices to be online in real time, while the Mobile distributed systems do not require member devices to be online in real time. Because the structure and function of the mobile distributed system are different from those of the traditional distributed system, the data synchronization method of the traditional distributed system is not suitable for the mobile distributed system. Therefore, how to synchronize mobile distributed system data is an urgent problem to be solved.

SUMMARY OF THE INVENTION

The present application provides a method and device for data synchronization in a mobile distributed system, and the method realizes asynchronous synchronization of data between devices in a mobile distributed system.

A first aspect provides a method for data synchronization in a mobile distributed system, comprising: a first device sending a first query request to a second device, where the first query request is used to query whether there is media on the second device Asset change; the first device receives the first synchronization message sent by the second device, the first synchronization message is that the second device receives the first query request and determines that the first media asset is changed. sent by the first device, the first synchronization message carries the first media asset change content of the second device, and the first media asset change content includes the changed first media asset and the first media The action corresponding to the asset change; the first device generates a first synchronization record according to the first synchronization message, wherein the first synchronization record includes a first synchronization node, a first change list and a first device list. The first synchronization node is used to record the information of the first data synchronization, and the first change list is used to record the first media asset changed in the first data synchronization and the action corresponding to the change of the first media asset, The first device list is used to record the first data synchronization device.

In the method, the first device sends the first query request to the second device; after the second device receives the first query request and determines that the first media asset is changed, The first device sends the first synchronization message, and the first device generates a first synchronization record according to the first synchronization message, where the first synchronization record includes a first synchronization node, a first change list With the first device list, the asynchronous synchronization of the mobile distributed system is realized.

It should be understood that a media asset refers to files in various formats, such as audio, video, picture and other files, and the media asset may correspond to the metadata of the media asset, rather than the data of the media asset itself. For example, the file audio A, its media assets can be the metadata of the audio A (the storage location of the audio A, the size of the audio A, the owner of the audio A and other data attribute information).

The media asset change refers to the change of the media asset on the device, which may be a new media asset on the device, or a modification of the original media asset content on the device. If the second device has recorded audio A, the media asset change on the second device means that the second device has recorded audio A. Another example is that the second device has modified audio B, which is the original media asset of the second device. , the media asset change on the second device means that the second device modifies audio B.

With reference to the first aspect, in some implementations of the first aspect, the first synchronization node includes: a first synchronization node identifier, a first synchronization timestamp, a first parent synchronization node identifier, a first synchronization change content, and a first synchronization change content and a first synchronization node. One or more of a synchronization device, wherein the first synchronization node ID is used to identify the first data synchronization; the first change list includes: a first change list ID and the second device's The first media asset changes content; the first device list includes: the first device list ID and the device ID of the second device.

With reference to the first aspect, in some implementations of the first aspect, the first synchronization change content includes media asset change content of the second device, and the first synchronization device includes the device ID of the second device; or , the first synchronization change content includes the index of the first change list, the first synchronization device includes the index of the first device list, the index of the change list is used to find the first change list, the The index of the device list is used to look up the first device list; or, the first synchronization change content includes the index of the first media asset change content, and the first synchronization device includes the second device-related index. an index, where the index of the change list is used to look up the content of the first media asset change, and the index related to the second device is used to look up information related to the second device.

It should be understood that the information related to the second device may include one or more pieces of information such as the type of the second device, the name of the second device, and the storage size of the second device.

With reference to the first aspect, in some implementations of the first aspect, before the first device receives the first synchronization message sent by the second device, the method further includes: a media asset on the first device is changed , the first device adds a second change list, and the second change list includes the second change list ID and the content of the media asset change on the first device.

By adding a second change list to the first device when the media asset on the first device is changed, the second change list includes the second change list ID and the content of the media asset change on the first device. When the member device in the mobile distributed system leaves the backline state of the distributed system, the media asset changes on the device are still valid.

With reference to the first aspect, in some implementations of the first aspect, after the first device receives the first synchronization message sent by the second device, the method further includes: the first device according to the first synchronization message message, generate a second synchronization record, the second synchronization record includes the second synchronization node, the second change list and the second device list; the second synchronization node includes the second synchronization node ID, the second synchronization timestamp , one or more of the second parent synchronization node identifier, the second synchronization change content and the second synchronization device, the second synchronization node ID is used to identify the second data synchronization; in the second change list, add The content of the media asset of the second device is changed; the device ID of the second device is added to the second device list.

With reference to the first aspect, in some implementations of the first aspect, the method further includes: the first device sends a second query request to the second device, where the second query request is used to query the Whether there is a media asset change on the second device; the first device receives a second synchronization message sent by the second device, where the second synchronization message is that the second device receives the second query request, and Sent to the first device after judging that there is a second media asset change, the second synchronization message carries the second media asset change content of the second device, and the second media asset change content includes the changed content. The second media asset and the action corresponding to the change of the second media asset; the first device generates a third synchronization record according to the second synchronization message, and the third synchronization record includes a third synchronization node, a third modification A list and a third device list, the third synchronization node includes: a third synchronization node ID, a third synchronization time stamp, a third parent synchronization node identifier, a third synchronization change content, and one or more of the third synchronization device where the third synchronization node ID is used to identify three data synchronizations; the third change list includes a third change list ID, and the second media asset of the second device changes content; the third device list includes The third device list ID, and the device ID of the second device; remove the device ID of the second device in the first device list ID.

If the first device and the second device have performed multiple data synchronizations, only the device ID of the second device for the latest data synchronization is retained in the device list of the synchronization record, and the second device in the previous device list is deleted. The device ID of the first device and the second device can quickly find the status information of the data synchronization that has been performed before, and delete the device ID of the second device in the previous device list to save The storage space of the first device.

With reference to the first aspect, in some implementations of the first aspect, the device ID in the first device list is empty, and the first device list is deleted.

When the device ID in the first device list is empty, deleting the first device list can save the storage space of the first device.

With reference to the first aspect, in some implementations of the first aspect, when the first synchronization node is a root (Root) node, the root node and the first change list are deleted, and the root node and the root node are deleted. The adjacent sync node becomes the new root node.

It should be understood that the root node is a node created when the first device performs data synchronization with other devices in the mobile distributed system for the first time.

When the first synchronization node is a root (Root) node, deleting the root node and the first change list can save the storage space of the first device.

With reference to the first aspect, in some implementations of the first aspect, the third synchronization node is a top node, and a node between the top node and the root node is a middle node.

With reference to the first aspect, in some implementations of the first aspect, when the data synchronization process between the first device and the second device terminates abnormally, a temporary intermediate node is created, and the temporary intermediate node includes a temporary state identifier, the temporary intermediate node is used to save the synchronization data for which data synchronization is not completed.

With reference to the first aspect, in some implementations of the first aspect, the method further includes: when the first data is synchronized, the first device receives the first hash value sent by the second device, The first hash value is obtained by the hash operation performed by the second device according to the changed content of the first media asset, and the first synchronization message includes the first hash value; the first device Perform hash calculation according to the content of the first change list to obtain a second hash value; when the first device determines that the first hash value is equal to the second hash value, the first device It is determined that the current data synchronization is successful.

When the first device synchronizes the data of the second device, the correctness of the data synchronization is ensured by verifying the first hash value and the second hash value.

In a second aspect, a method for synchronizing data in a mobile distributed system is provided, including: a second device receiving a first query request sent by a first device, where the first query request is used to query whether the second device has changes to media assets;

The second device determines that the first media asset is changed according to the first query request, and sends a first synchronization message to the first device, where the first synchronization message carries the first media of the second device Asset change content, where the first media asset change content includes the changed first media asset and an action corresponding to the first media asset change.

With reference to the second aspect, in some implementations of the second aspect, before the second device receives the first query request sent by the first device, the method further includes:

The first media asset on the second device is changed, and the second device adds a first change list;

The method also includes:

The second device sends a third query request to the first device, where the third query request is used to query whether there is a media asset change on the first device;

The second device receives the first feedback message sent by the first device, where the first feedback message is that the first device receives the third query request and determines that there is no media on the first device Sent to the second device after the asset is changed, the first feedback message is used to identify that no media asset change has occurred on the first device;

The second device generates a first synchronization record according to the first feedback message and the first synchronization message, wherein the first synchronization record includes a first synchronization node, the first change list and a first device list, the first synchronization node is used to record the information of the first data synchronization, the first change list is used to record the media assets changed in the first data synchronization and the actions corresponding to the changes of the media assets, so The first device list is used to record the first data synchronization device.

With reference to the second aspect, in some implementations of the second aspect, the first synchronization node includes: a first synchronization node identifier, a first synchronization timestamp, a first parent synchronization node identifier, a first synchronization change content, and a first synchronization change content and a first synchronization node. One or more of a synchronization device, wherein the first synchronization node ID is used to identify the first data synchronization; the first change list includes: a first change list ID and the second device's The content of the media asset change; the first device list includes: the first device list ID and the device ID of the first device.

With reference to the second aspect, in some implementations of the second aspect, the first synchronization change content includes media asset change content of the second device, and the first synchronization device includes the device ID of the first device; or , the first synchronization change content includes the index of the first change list, the first synchronization device includes the index of the first device list, the index of the change list is used to find the first change list, the The index of the device list is used to find the first device list; or, the first synchronization change content includes an index of the media asset change content of the second device, and the first synchronization device includes The relevant index, the index of the media asset modification content of the second device is used to find the media asset modification content of the second device, and the index related to the first device is used to search for the media asset modification content related to the first device. information.

With reference to the second aspect, in some implementations of the second aspect, the second device determining, according to the first query request, that the first media asset is changed, including: the second device according to the first query The request and the synchronization record on the second device determine that the first media asset is changed; or, the second device determines that the first media asset is changed according to the first query request and the change list on the second device.

With reference to the second aspect, in some implementations of the second aspect, the first synchronization message includes a first hash value, and the first hash value is a change of the second device according to the first media asset The content is obtained by hashing.

In a third aspect, a device is provided, the device is a first device, and includes: a transceiver unit configured to send a first query request to a second device, where the first query request is used to query the second device Whether there is a media asset change;

The transceiver unit is further configured to receive a first synchronization message sent by the second device, where the first synchronization message is sent to the second device after receiving the first query request and judging that the first media asset has been changed. Sent by the first device, the first synchronization message carries the first media asset modification content of the second device, and the first media asset modification content includes the modified first media asset and the first media asset. an action corresponding to a media asset change; a processing unit, configured to generate a first synchronization record according to the first synchronization message, wherein the first synchronization record includes a first synchronization node, a first change list, and a first device list, The first synchronization node is used to record the information of the first data synchronization, and the first change list is used to record the first media asset changed in the first data synchronization and the action corresponding to the change of the first media asset , the first device list is used to record the first data synchronization device.

With reference to the third aspect, in some implementations of the third aspect, the first synchronization node includes: a first synchronization node identifier, a first synchronization timestamp, a first parent synchronization node identifier, a first synchronization change content, and a first synchronization change One or more of a synchronization device, wherein the first synchronization node ID is used to identify the first data synchronization; the first change list includes: a first change list ID and the second device's The first media asset changes content; the first device list includes: the first device list ID and the device ID of the second device.

With reference to the third aspect, in some implementations of the third aspect, the first synchronization change content includes first media asset change content of the second device, and the first synchronization device includes a device ID of the second device Or, the first synchronization change content includes an index of the first change list, the first synchronization device includes an index of the first device list, and the index of the change list is used to find the first change list, The index of the device list is used to look up the first device list; or, the first synchronization change content includes an index of the first media asset change content, and the first synchronization device includes a connection with the second device. A related index, where the index of the first media asset modification content is used to search for the first media asset modification content, and the index related to the second device is used to search for information related to the second device.

With reference to the third aspect, in some implementations of the third aspect, before the first device receives the first synchronization message sent by the second device, the media asset on the first device is changed, and the processing unit further Used for: adding a second change list, where the second change list includes the second change list ID and the content of the media asset change on the first device.

With reference to the third aspect, in some implementations of the third aspect, after the first device receives the first synchronization message sent by the second device, the processing unit is further configured to: the first device according to the first synchronization message A synchronization message to generate a second synchronization record, the second synchronization record includes the second synchronization node, the second change list and the second device list; the second synchronization node includes the second synchronization node ID, the second synchronization One or more of a timestamp, a second parent synchronization node ID, a second synchronization change content, and a second synchronization device, the second synchronization node ID is used to identify the second data synchronization; in the second change list , and the content of the media asset modification of the second device is added; the device ID of the second device is added to the second device list.

With reference to the third aspect, in some implementations of the third aspect, the transceiver unit is further configured to: send a second query request to the second device, where the second query request is used to query the second device whether there are any changes to the media assets;

Receive a second synchronization message sent by the second device, where the second synchronization message is sent to the first device after the second device receives the second query request and determines that the second media asset is changed The second synchronization message carries the second media asset change content of the second device, and the second media asset change content includes the changed second media asset and the action corresponding to the second media asset change ; the processing unit is further configured to: generate a third synchronization record according to the second synchronization message, the third synchronization record includes a third synchronization node, a third change list and a third device list, wherein the third synchronization record The three synchronization nodes include a third synchronization node ID, one or more of a third synchronization timestamp, a third parent synchronization node identifier, a third synchronization change content, and a third synchronization device, wherein the third synchronization node ID Used to identify three data synchronization; the third change list includes a third change list ID, the second media asset of the second device changes content; the third device list includes a third device list ID, and the second Device ID of the device;

The processing unit is further configured to: remove the device ID of the second device in the first device list ID.

With reference to the third aspect, in some implementations of the third aspect, the device ID in the first device list is empty, and the processing unit deletes the first device list.

With reference to the third aspect, in some implementations of the third aspect, when the first synchronization node is a root (Root) node, the root node and the first change list are deleted, and the root node and the root node are deleted. The adjacent sync node becomes the new root node.

With reference to the third aspect, in some implementations of the third aspect, the third synchronization node is a top (Top) node, and a node between the top node and the root node is a middle (middle) node.

With reference to the third aspect, in some implementations of the third aspect, when the data synchronization process between the first device and the second device terminates abnormally, the processing unit is further configured to: create a temporary intermediate node, so The temporary intermediate node includes a temporary state identifier, and the temporary intermediate node is used to store synchronization data for which data synchronization is not completed.

With reference to the third aspect, in some implementations of the third aspect, when the first data is synchronized, the transceiver unit is further configured to receive a first hash value sent by the second device, the first hash value The hash value is obtained by the hash operation performed by the second device according to the changed content of the first media asset, and the first synchronization message includes the first hash value;

The processing unit is further configured to perform hash calculation according to the content of the first change list to obtain a second hash value; when the processing unit determines that the first hash value is equal to the second hash value , the processing unit determines that the current data synchronization is successful.

In a fourth aspect, a device is provided, where the device is a second device, comprising: a transceiver unit configured to receive a first query request sent by the first device, where the first query request is used to query the second device Whether there is a media asset change on the server; the processing unit is configured to determine, according to the first query request, that there is a first media asset change, and send a first synchronization message to the first device, where the first synchronization message carries the The content of the first media asset change of the second device, where the content of the first media asset change includes the changed first media asset and an action corresponding to the change of the first media asset.

With reference to the fourth aspect, in some implementations of the fourth aspect, the first media asset on the second device is changed, and the processing unit is further configured to add a first change list; the transceiver unit is further used for: sending a third query request to the first device, where the third query request is used to query whether there is a media asset change on the first device;

Receive a first feedback message sent by the first device, where the first feedback message is sent to the sent by the second device, the first feedback message is used to identify that there is no media asset change on the first device; the processing unit is further configured to:

A first synchronization record is generated according to the first feedback message and the first synchronization message, wherein the first synchronization record includes a first synchronization node, the first change list and a first device list, the first synchronization record A synchronization node is used to record the information of the first data synchronization, the first change list is used to record the media assets changed in the first data synchronization and the actions corresponding to the changes of the media assets, the first device list A device for recording the first data synchronization.

With reference to the fourth aspect, in some implementations of the fourth aspect, the first synchronization node includes: a first synchronization node identifier, a first synchronization timestamp, a first parent synchronization node identifier, a first synchronization change content, and a first synchronization change content and a first synchronization node. One or more of a synchronization device, wherein the first synchronization node ID is used to identify the first data synchronization; the first change list includes: a first change list ID and the second device's The content of the media asset change; the first device list includes: the first device list ID and the device ID of the first device.

With reference to the fourth aspect, in some implementations of the fourth aspect, the first synchronization change content includes media asset change content of the second device, and the first synchronization device includes the device ID of the first device; or , the first synchronization change content includes the index of the first change list, the first synchronization device includes the index of the first device list, the index of the change list is used to find the first change list, the The index of the device list is used to find the first device list; or, the first synchronization change content includes an index of the media asset change content of the second device, and the first synchronization device includes The relevant index, the index of the media asset modification content of the second device is used to find the media asset modification content of the second device, and the index related to the first device is used to search for the media asset modification content related to the first device. information.

With reference to the fourth aspect, in some implementations of the fourth aspect, the processing unit is specifically configured to: determine that the first media asset is changed according to the first query request and the synchronization record on the second device; or, According to the first query request and the change list on the second device, it is determined that the first media asset is changed.

With reference to the fourth aspect, in some implementations of the fourth aspect, the first synchronization message includes a first hash value, and the first hash value is the content changed by the processing unit according to the first media asset obtained by hashing.

In a fifth aspect, an apparatus is provided, comprising a processor connected to a memory for storing a computer program, and the processor for executing the computer program stored in the memory to cause the The apparatus performs the method of the first aspect or any possible implementation of the first aspect, or the method of the second aspect or any possible implementation of the second aspect.

In a sixth aspect, a computer-readable storage medium is provided, and the computer-readable storage medium stores a computer program. When the computer program is executed, the first aspect or any possible implementation manner of the first aspect is realized. The method in , or the method in the second aspect or any possible implementation of the second aspect.

In a seventh aspect, a chip is provided, including a processor and an interface; the processor is configured to read instructions to execute the method in the first aspect or any possible implementation manner of the first aspect, or the second aspect or the first aspect. A method in any possible implementation manner of the second aspect.

Optionally, the chip may further include a memory in which instructions are stored, and the processor is configured to execute the instructions stored in the memory or other instructions.

In an eighth aspect, a mobile distributed system is provided, the system includes a device having functions for implementing the methods and various possible designs of the above-mentioned first aspect, and various methods and various possible designs for implementing the above-mentioned second aspect. functional device.

Description of drawings

1 is a schematic structural block diagram of an operating system according to an embodiment of the present application;

FIG. 2 is a schematic diagram of an application scenario of an embodiment of the present application;

FIG. 3a is a schematic diagram of a requirement for consistency of a distributed system according to an embodiment of the present application;

FIG. 3b is a schematic diagram of a requirement for consistency of a distributed system according to an embodiment of the present application;

FIG. 3c is a schematic diagram of a requirement for consistency of a distributed system according to an embodiment of the present application;

4a is a schematic block diagram of a synchronization record in an embodiment of the present application;

FIG. 4b is a schematic block diagram of a synchronization record according to an embodiment of the present application;

4c is a schematic block diagram of a synchronization record in an embodiment of the present application;

5a is a schematic block diagram of a synchronization record in an embodiment of the present application;

5b is a schematic block diagram of a synchronization record in an embodiment of the present application;

Fig. 5c is a schematic block diagram of a synchronization record according to an embodiment of the present application;

6a is a schematic block diagram of a synchronization record in an embodiment of the present application;

6b is a schematic block diagram of a synchronization record in an embodiment of the present application;

6c is a schematic block diagram of a synchronization record in an embodiment of the present application;

FIG. 7 is a schematic block diagram showing that device A and other devices have performed data synchronization and device B and other devices have performed data synchronization according to an embodiment of the present application;

8 is a schematic block diagram of a device B in an embodiment of the present application when a media asset is changed;

9 is a schematic flowchart of a method for data synchronization in a mobile distributed system according to an embodiment of the present application;

10 is a schematic flowchart of a method for data synchronization in a mobile distributed system according to an embodiment of the present application;

11 is a schematic block diagram of data synchronization between device A and device B according to an embodiment of the present application;

12 is a schematic block diagram of a device A in an embodiment of the present application when a media asset is changed;

13 is a schematic flowchart of a method for data synchronization in a mobile distributed system according to an embodiment of the present application;

14 is a schematic flowchart of a method for data synchronization in a mobile distributed system according to an embodiment of the present application;

15 is a schematic block diagram of data synchronization between device A and device B according to an embodiment of the present application;

FIG. 16 is a schematic block diagram of a device B in an embodiment of the present application when a media asset is changed;

17 is a schematic flowchart of a method for data synchronization in a mobile distributed system according to an embodiment of the present application;

18 is a schematic block diagram of data synchronization between device A and device B according to an embodiment of the present application;

19 is a schematic block diagram of a stateful data synchronization structure of a mobile distributed system according to an embodiment of the present application;

FIG. 20 shows a schematic block diagram of an apparatus according to an embodiment of the present application;

FIG. 21 is a schematic structural diagram of a terminal device provided by this application.

detailed description

The technical solutions in the present application will be described below with reference to the accompanying drawings.

For a better understanding of the present application, the terms appearing in the present application are first described below.

Operating System (OS): A computer program that manages computer hardware and software resources. The operating system handles basic tasks such as managing and configuring memory, prioritizing the supply and demand of system resources, controlling input and output devices, operating the network, and managing the file system. The operating system also provides an interface for the user to interact with the system. Common operating systems include: iOS operating system, Android operating system and Microsoft Windows series operating systems, among which, iOS operating system is a handheld device operating system developed by Apple, and Android operating system is a free and open source Linux-based operating system. code for the operating system. Primarily used on mobile devices such as smartphones and tablets, the Microsoft Windows family of operating systems is a graphical operating system based on MS-DOS, which Microsoft designed for IBM machines.

The following takes the Android operating system as an example to briefly describe the operating system architecture. As shown in FIG. 1 , FIG. 1 shows a schematic block diagram of an Android operating system. Like other operating systems, the Android operating system adopts a layered architecture. The layered architecture divides the software into several layers, and each layer has a clear role and division of labor. Layers communicate with each other through software interfaces. In some embodiments, the Android system is divided into four layers, which are, from top to bottom, an application layer, an application framework layer, an Android runtime (Android runtime) and a system library, and a kernel layer.

The application layer can include a series of application packages.

As shown in Figure 2, the application package can include applications such as camera, gallery, calendar, call, map, navigation, WLAN, Bluetooth, music, video, short message and so on.

The application framework layer provides an application programming interface (application programming interface, API) and a programming framework for applications in the application layer. The application framework layer includes some predefined functions.

As shown in Figure 2, the application framework layer may include window managers, content providers, view systems, telephony managers, resource managers, notification managers, and the like.

A window manager is used to manage window programs. The window manager can get the size of the display screen, determine whether there is a status bar, lock the screen, take screenshots, etc.

Content providers are used to store and retrieve data and make these data accessible to applications. The data may include video, images, audio, calls made and received, browsing history and bookmarks, phone book, etc.

The view system includes visual controls, such as controls for displaying text, controls for displaying pictures, and so on. View systems can be used to build applications. A display interface can consist of one or more views. For example, the display interface including the short message notification icon may include a view for displaying text and a view for displaying pictures.

The phone manager is used to provide the communication functions of the device. For example, the management of call status (including connecting, hanging up, etc.).

The resource manager provides various resources for the application, such as localization strings, icons, pictures, layout files, video files and so on.

The notification manager enables applications to display notification information in the status bar, which can be used to convey notification-type messages, and can disappear automatically after a brief pause without user interaction. For example, the notification manager is used to notify download completion, message reminders, etc. The notification manager can also display notifications in the status bar at the top of the system in the form of graphs or scroll bar text, such as notifications of applications running in the background, and notifications that appear on the screen in the form of dialog windows. For example, text information is prompted in the status bar, a prompt sound is issued, the electronic device vibrates, and the indicator light flashes.

Android Runtime includes core libraries and a virtual machine. Android runtime is responsible for scheduling and management of the Android system.

The core library consists of two parts: one is the function functions that the java language needs to call, and the other is the core library of Android.

The application layer and the application framework layer run in virtual machines. The virtual machine executes the java files of the application layer and the application framework layer as binary files. The virtual machine is used to perform functions such as object lifecycle management, stack management, thread management, safety and exception management, and garbage collection.

A system library can include multiple functional modules. For example: surface manager (surface manager), media library (Media Libraries), 3D graphics processing library (eg: OpenGL ES), 2D graphics engine (eg: SGL), etc.

The Surface Manager is used to manage the display subsystem and provides a fusion of 2D and 3D layers for multiple applications.

The media library supports playback and recording of a variety of commonly used audio and video formats, as well as still image files. The media library can support a variety of audio and video encoding formats, such as: MPEG4, H.264, MP3, AAC, AMR, JPG, PNG, etc.

The 3D graphics processing library is used to implement 3D graphics drawing, image rendering, compositing, and layer processing.

2D graphics engine is a drawing engine for 2D drawing.

Database: A computer software system that stores and manages data according to the data structure, and generally has basic functions such as storage, interception, security assurance, and backup. The database is a warehouse for storing data. It has a large storage space and can store millions, tens of millions, and hundreds of millions of data. The data in the database is stored according to certain rules, and there are many sources of data, such as travel records, consumption records, web pages browsed, messages sent, and so on.

Metadata is stored in the database. Metadata is the data describing the data (data about data), also known as intermediary data and relay data, mainly describing the information of the data properties, such as describing the content of the data, covering Information such as scope, quality, management methods, data owners, and data provision methods are the bridge between data and data users. Metadata is information about the organization of data, data domains and their relationships. In short, metadata is data about data. The metadata can be various attribute information of the data, such as the name of the data, the size of the data, the data type of the data, the length of the data, the fields of the data, the location of the data, the owner of the data, and the like.

It should be understood that the data synchronization in the embodiments of the present application refers to the synchronization of metadata, that is, the attribute information of the data that is synchronously changed between devices, such as the storage location and other information, and the specific data may not be synchronized.

The kernel layer is the layer between hardware and software. The kernel layer contains at least display drivers, camera drivers, audio drivers, and sensor drivers.

The technical solutions of the embodiments of the present application can be applied to various communication systems, for example: global system for mobile communications (GSM) system, code division multiple access (CDMA) system, wideband code division multiple access (wideband code division multiple access, WCDMA) system, general packet radio service (general packet radio service, GPRS), long term evolution (long term evolution, LTE) system, LTE frequency division duplex (frequency division duplex, FDD) system, LTE Time division duplex (TDD), universal mobile telecommunication system (UMTS), worldwide interoperability for microwave access (WiMAX) communication system, 5th generation (5G) system or new radio (NR), in addition, it can also be applied to use subsequent evolution systems, such as the sixth-generation 6G communication system, or even the more advanced seventh-generation 7G communication system.

The terminal equipment in the embodiments of the present application may also be referred to as: user equipment (user equipment, UE), mobile station (mobile station, MS), mobile terminal (mobile terminal, MT), access terminal, subscriber unit, subscriber station, Mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user equipment, etc.

The terminal device can be a wireless terminal or a wired terminal, and the wireless terminal can be a device that provides voice and/or other service data connectivity to the user, a handheld device with wireless connection function, or other processing device connected to a wireless modem. A wireless terminal may communicate with one or more core networks via a Radio Access Network (RAN), and the wireless terminal may be a mobile terminal such as a mobile phone (or "cellular" phone) and a computer with a mobile terminal Mobile devices, which may be portable, pocket-sized, hand-held, computer-embedded, or vehicle-mounted, for example, exchange language and/or data with the wireless access network. For example, Personal Communication Service (PCS) phones, cordless phones, Session Initiation Protocol (SIP) phones, Wireless Local Loop (WLL) stations, Personal Digital Assistants (Personal Digital Assistants), PDA) and other devices. A wireless terminal may also be referred to as a system, a subscriber unit, a subscriber station, a mobile station, a mobile station, a remote station, a remote terminal, a connection Access Terminal, User Terminal, User Agent, User Device or User Equipment, mobile internet device (MID), wearable device, virtual reality (virtual reality) reality, VR) equipment, augmented reality (AR) equipment, wireless terminals in industrial control, wireless terminals in self-driving, wireless terminals in remote medical surgery , wireless terminal in smart grid, wireless terminal in transportation safety, wireless terminal in smart city, wireless terminal in smart home, in-vehicle equipment, wearable equipment, terminal equipment in a 5G network, or terminal equipment in a future evolved public land mobile network (public land mobile network, PLMN), etc., which are not limited in the embodiments of the present application.

As an example and not a limitation, in the embodiments of this application, a wearable device may also be referred to as a wearable smart device, which is a general term for intelligently designing daily wearable devices and developing wearable devices using wearable technology, such as glasses, Gloves, watches, clothing and shoes, etc. A wearable device is a portable device that is worn directly on the body or integrated into the user's clothing or accessories. Wearable device is not only a hardware device, but also realizes powerful functions through software support, data interaction, and cloud interaction. In a broad sense, wearable smart devices include full-featured, large-scale, complete or partial functions without relying on smart phones, such as smart watches or smart glasses, and only focus on a certain type of application function, which needs to cooperate with other devices such as smart phones. Use, such as all kinds of smart bracelets, smart jewelry, etc. for physical sign monitoring.

In addition, in the embodiments of the present application, the terminal device may also be a terminal device in an Internet of Things (IoT) system. IoT is an important part of the future development of information technology, and its main technical feature is that items pass through communication technology Connect with the network, so as to realize the intelligent network of human-machine interconnection and interconnection of things.

The various terminal devices described above, if they are located on the vehicle (for example, placed in the vehicle or installed in the vehicle), can be considered as on-board terminal equipment. For example, the on-board terminal equipment is also called on-board unit (OBU). ).

In this embodiment of the present application, the terminal device may further include a relay (relay). Alternatively, it can be understood that any device capable of data communication with the base station can be regarded as a terminal device.

An application scenario of the embodiment of the present application is introduced below. FIG. 2 shows a schematic diagram of an application scenario 100 of the embodiment of the present application. In FIG. 2 , a terminal device 110 , a terminal device 120 , a terminal device 130 , and a terminal device 140 are included. The terminal device 110, the terminal device 120, the terminal device 130 and the terminal device 140 constitute a mobile distributed system.

The terminal device in FIG. 2 may be a smart phone, a notebook computer, or other terminal devices such as a vehicle-mounted computer, and the terminal device included in the mobile distributed system shown in FIG. 1 may be the above-mentioned various forms of terminal devices .

It should be understood that the mobile distributed system shown in FIG. 2 may also include more terminal devices. The embodiments of the present application are not shown one by one in the drawings.

The mobile distributed system has the following characteristics:

The mobile distributed system is distributed in a peer-to-peer structure, and the member devices of the system are equal, and there is no master-slave relationship;

The mobile distributed system is composed of smart terminal devices such as mobile phones, watches, TVs, car machines, and stereos. These terminal devices are member devices of the mobile distributed system;

The mobile distributed system is a loose system, which does not require the real-time online of system member devices;

The application, service, data and other resources of the mobile distributed system are scattered and deployed on different system member devices; the resources available to the system member devices include local resources and distributed resources, and each member device maintains the synchronization of system data information;

When the member devices of the mobile distributed system are online, the online member devices can share local resources (applications, services, data and other resources of the device) to other member devices in the mobile distributed system; use of distributed resources (mobile applications, services, data and other resources of other member devices in the distributed system);

When the member device of the mobile distributed system is offline, the user of the offline member device can still use the local resources of the offline device (such as the application, service, data and other resources of the device);

After the member devices of the mobile distributed system are back online, the re-connected member devices can share the local resources to other member devices in the mobile distributed system according to the local data resource status (the local data resource status is the change of the local data resources recorded locally). , and other member devices of the distributed system can also share data resources to the re-online member devices according to the local data resource status of other member devices;

The member devices of the mobile distributed system interact through distributed middleware, wherein the distributed middleware is used to realize the interaction between the member devices of the distributed system, such as wireless network, to realize the consistency of local data resources and distributed data resources, Availability of local data resources and distributed data resources, resource availability/fault tolerance under the full state (online/offline) of member devices.

Among them, consistency, availability and partition fault tolerance are the requirements for data synchronization of distributed systems (traditional distributed systems and mobile distributed systems). The following are respectively introduced:

Partition Tolerance: Most distributed systems are spread across multiple subnetworks. Each subnet is called a partition. Partition fault tolerance means that there will be a loss of connection between intervals, and communication may fail.

Consistency means that a read followed by a write must return this value. Figure 3 specifically illustrates the requirements for consistency. In Figure 3, G1 and G2 are respectively two servers of a distributed system. In Figure 3a, a record in the distributed system is v0, and the user initiates a write operation to G1 to change it to v1. Next, the user's read operation will get v1, as shown in Figure 3a.

It is possible for the user to initiate a read operation to G2. Since the value of G2 has not changed, v0 is returned. The results of the G1 and G2 read operations are inconsistent, which does not satisfy the consistency, as shown in Figure 3b.

In order to make G2 also change to v1, when G1 writes, let G1 send a message to G2, requesting that G2 also change to v1. In this way, when the user initiates a read operation to G2, v1 can also be obtained, as shown in Figure 3c.

Availability means that as long as a user's request is received, the server must respond. The user can choose to initiate a read operation to G1 or G2. No matter which server it is, as long as it receives a request, it must tell the user whether it is v0 or v1, otherwise the availability will not be satisfied.

It should be understood that the devices included in the mobile distributed system may be movable terminal devices, and may also include fixed and immovable terminal devices. The mobile distributed system can also be called a peer-to-peer distributed system according to its structural characteristics.

Traditional distributed systems are generally master-slave structures; traditional distributed systems consist of multiple servers; traditional distributed systems require system member devices to be online in real time. It can be seen that the mobile distributed system is different from the traditional distributed system.

Traditional distributed system data synchronization generally adopts two standardized data synchronization protocols, namely Raft protocol and Paxos protocol. The Raft protocol is a classic distributed consensus algorithm, a strong leader-type algorithm. Each node has three states: "master node", "candidate node", and "slave node", which can be transformed between the three states. The client can only write data from the master node and read data from the node. Its throughput is basically the throughput of the leader, and it cannot resist attacks by nodes maliciously tampering with data. The Raft protocol only supports the distributed master-slave structure, supports distributed consistency and availability, supports partition fault tolerance in the connected state, and does not provide local services in the disconnected state. The mobile distributed system is distributed in a peer-to-peer structure, and requires member devices to be available even when they are offline. Therefore, Raft does not meet the demands of keeping local resources available and valid when the member devices of the mobile distributed system are offline.

The Paxos protocol algorithm can provide different types of consensus algorithms for different occasions. The Paxos protocol compares each data request to a proposal. Each proposal has an independent number. The proposal will be forwarded to the submitter (Proposer) for submission. The proposal must be accepted by the voting committee (Quorum) to take effect. The nodes in the voting committee are called Acceptors. The roles are divided into proposers and acceptors (allowing to hold multiple positions): proposers propose proposals, and the proposal information includes proposal number and proposed value; acceptors can accept the proposal after receiving it. If a proposal is accepted by a majority of the acceptors, the proposal is said to be chosen. Paxos supports peer-to-peer structure distribution, but does not support asynchronous synchronization. After members come back online, they must maintain data consistency with the distributed system unconditionally. After the member devices of the mobile distributed system are back online, they are required to be able to upload local data resources and local data resource status, such as photos taken when the mobile phone is disconnected from the network, edited pictures and other information can be shared with other member devices after accessing the system. Therefore, Paxos does not meet the requirements of maintaining the consistency of local data resources and the validity/fault tolerance of local data resources when the member devices of the mobile distributed system come back online.

The improved method of Paxos fast Paxos, multi Paxos provides a master-slave distributed system, which partially supports asynchronous synchronization (the asynchronous synchronization mentioned here refers to data synchronization not real-time synchronization), similar to Raft, does not support peer-to-peer structure distribution, does not satisfy The demand for keeping local resources available and local resources valid when the member devices of the mobile distributed system are offline, and does not consider the case of partition fault tolerance.

In view of this, the present application proposes a method and terminal device for data synchronization of a mobile distributed system, and the method is used to realize data synchronization of a mobile distributed system.

The target data processed by the mobile distributed operating system data synchronization method mainly includes synchronization records. Among them, the synchronization record (Synchronous recording) includes the synchronization node, the change list (Change list), and the device list (device list). Synchronization records can be stored in databases, file systems, memory, etc.

Synchronization node: A synchronization record node is formed each time the data is synchronized in batches. A synchronization record includes a synchronization node. The synchronization node includes a synchronization node identifier (Identity Document, ID) (hereinafter referred to as the synchronization node ID, which is used to identify this data synchronization, which is different from data synchronization at other times), a synchronization timestamp (the occurrence time of this data synchronization), The ID of the parent synchronization node (the synchronization ID of the last data synchronization), the content changed in this synchronization, and the device to be synchronized this time.

Change list: record the content of each media asset change. Once generated, it cannot be changed. The change of the media asset can be the change of the media asset of the device itself. For example, if device A records audio A, the change list on device A will record the device. A records audio A; the change of the media asset can also be a change of the media asset of the device that is synchronizing. For example, if device A synchronizes data with device B, and device B creates audio B, the change list on device A will record the audio B; the change list includes a change list ID and media asset change content, wherein the media asset change content includes a changed media asset and an action corresponding to the media asset change. The change list ID is used to identify the current media asset change, which is different from media asset changes at other times. Media assets refer to files in various formats on the device, such as audio, video, and image files. Actions corresponding to media assets can be regular operation logs such as creation, modification, deletion, and movement (creation, modification, deletion, and movement are all logs), or change operation logs of extended attributes, such as modification of file size. Operational logs, or other types of logs such as changes to file access permissions. The change list can also include attribute information of the changed content. For example, if the changed content is to create picture A, the changed content also includes various attribute information such as the size, format, storage path, author, and creation time of the picture A. A change list is a list of recorded media asset changes that exist on each device itself, and the change list can be stored in a database, file system, memory, etc.

Device list: record the device or node for this data synchronization. The device list can include: device list ID and device ID. The device list ID is used to identify the device list of this data synchronization, which is different from the device list of other time data synchronization. The device ID is used to identify the device, and the device ID of different devices is different.

The operations performed on the synchronization record include four types of operations: top (TOP) node update, root (Root) node update, device list deletion, and temporary middle (Middle) node creation.

TOP node update: When new data synchronization occurs, a new TOP node is created, and the original TOP node is transformed into an intermediate node. The TOP node update process is specifically described below with reference to FIG. 4 . As shown in Figure 4, when device D performs batch data synchronization for the first time, a root Root node is created. When a new data synchronization occurs, a TOP node is created. The node between the TOP node and the Root node is an intermediate node.

If device D performs data synchronization with device A at the first moment, for example, this data synchronization is the first data synchronization performed by device D, and the content of synchronization is to synchronize file A on device A. Then device D creates a Root node, as shown in Figure 4a.

The Root node includes the following information:

Sync ID: S _X ;

Timestamp: the first moment;

Synchronization parent ID: null; the synchronization parent ID refers to the synchronization node identifier of the adjacent last data synchronization of this data synchronization. Because this data synchronization is the first data synchronization performed by device D, the synchronization parent ID is Is empty.

The content of this synchronization change: the index of file A;

The device to be synchronized this time: the index of device A.

For example, if device D performs data synchronization with device B at the second moment, exemplarily, this data synchronization is the second data synchronization performed by device D, and the content of synchronization is to synchronize file B on device B. Then device D creates a new TOP node, as shown in Figure 4b.

The new TOP node includes the following information:

Sync ID: S _y ;

Timestamp: second moment;

Sync Parent ID: S _x ;

The content of this synchronization change: the index of file B;

The device to be synchronized this time: the index of device B.

For example, if device D performs data synchronization with device C at the third moment, exemplarily, this data synchronization is the second data synchronization performed by device D, and the content of synchronization is to synchronize file C on device C. Then the device D creates a new TOP node, and the original TOP node S _y is transformed into an intermediate node, as shown in Figure 4c.

The new TOP node includes the following information:

Sync ID: S _y+1 ;

Timestamp: the third moment;

Sync Parent ID: S _y ;

The content of this synchronization change: the index of file C;

The device to be synchronized this time: the index of device C.

It should be understood that, in the synchronization node list including this synchronization change content, the attribute information of this synchronization change content can also be recorded. For example, if the synchronization content this time is to create picture A, the change content also includes the size and format of the picture A, Storage path and other attribute information.

It should also be understood that the specific content of this synchronization change may be recorded in the content of the synchronization change this time, and the identification ID of the device synchronized this time may be recorded in the device synchronized this time.

It should also be understood that what is recorded in the content of this synchronization change and the device to be synchronized this time can be the index of the change list and the index of the device list, and the corresponding data synchronization can be found according to the index of the change list and the index of the device list. list of changes and devices. If the content of this synchronization change is a pointer to the storage location of the change list, the pointer can point to the change list, and the device to be synchronized this time can be a pointer to the storage location of the device list, and this pointer can point to the device list.

It should also be understood that the index of the content of this synchronization change can be recorded in the content of this synchronization change, the index related to the device of this synchronization can be recorded in the device of this synchronization, and the index of the content of this synchronization change can be used to find this time. When the content of the secondary media asset is changed, the index related to the device to be synchronized this time is used to search for information related to the device to be synchronized this time.

Device List node deletion: If the device in the intermediate node device list is reduced to zero, the current device list can be deleted.

The following is a detailed description of the device list deletion process with reference to FIG. 5 . As shown in Figure 5, the mobile distributed system includes device A, device B, device C, and device D. Device A has performed data synchronization with other devices included in the mobile distributed system. In the synchronization record on device A, data has been synchronized. A sync node, change list, and device list are created, as shown in Figure 5a, where the sync node includes:

Root node S _X ,

The list of changes corresponding to the Root node S _X includes:

changelist id: C _x ;

The device list corresponding to the Root node includes:

Device List ID: D _x ;

intermediate node S _y ,

The change list corresponding to the intermediate node S _y includes:

Changelist ID: _Cy ;

The device list corresponding to the intermediate node S _y includes:

Device List ID: D _y ,

Device ID: Device D;

Top node S _y+1 ,

The list of changes corresponding to the Top node S _y+1 includes:

change list id: C _y+1 ;

The device list corresponding to the Top node S _y+1 includes:

Device List ID: D _y+1 ,

Device ID: Device B and Device C.

At present, when the data of device D changes, device D needs to synchronize data with device A. A new top node S _y+2 will be generated in the synchronization record on device A, and the original top node S _y+1 will be transformed into an intermediate node.

The list of changes corresponding to the Top node S _y+2 includes:

change list id: C _y+2 ;

The device list corresponding to the Top node S _y+2 includes:

Device List ID: D _y+2 ,

Device ID: Device D.

After device A and device D complete this data synchronization, the device D in the device list D _y corresponding to the intermediate node S _y can be deleted, as shown in FIG. This will help device A to determine the content of the previous data synchronization faster when synchronizing data with device D next time, and the information about data synchronization between device A and device D will be recorded in the change list, so delete device list D Device D in _y will not have any effect on data synchronization by intermediate node Sy.

After the device D in the device list _Dy is deleted, the device in the device list _Dy is reduced to zero, and the current device list Dy can be deleted, as shown in Figure 5c.

Root node update: The device in the root node device list is reduced to zero, the root node is deleted, and the adjacent intermediate node becomes the new root node.

The root node update process is specifically described below with reference to FIG. 6 . As shown in Figure 6, the mobile distributed system includes device A, device B, device C, and device D. Device A has performed data synchronization with other devices included in the mobile distributed system. In the synchronization record on device A, data has been synchronized. A sync node, change list, and device list are created, as shown in Figure 6a, where the sync node includes:

Root node S _X ,

The list of changes corresponding to the Root node S _X includes:

changelist id: C _x ;

The device list corresponding to the Root node includes:

Device List ID: D _x ;

Device ID: Device D;

intermediate node S _y ,

The change list corresponding to the intermediate node S _y includes:

Changelist ID: _Cy ;

The device list corresponding to the intermediate node S _y includes:

Device List ID: D _y ,

Device ID: Device B;

Top node S _y+1 ,

The list of changes corresponding to the Top node S _y+1 includes:

change list id: C _y+1 ;

The device list corresponding to the Top node S _y+1 includes:

Device List ID: D _y+1 ,

Device ID: Device C.

At present, when the data of device D changes, device D needs to synchronize data with device A. A new top node S _y+2 will be generated in the synchronization record on device A, and the original top node S _y+1 will be transformed into an intermediate node, and the top node The list of changes corresponding to S _y+2 includes:

change list id: C _y+2 ;

The device list corresponding to the Top node S _y+2 includes:

Device List ID: D _y+2 ,

Device ID: Device D.

After the device A and the device D complete this data synchronization, the device _D in the device list _Dx corresponding to the root node Sx can be deleted, as shown in FIG. 6b. When the device D in the device list _Dx is deleted, the device in the device list _Dx is reduced to zero, the root node _Sx can be deleted, and the adjacent intermediate node _Sy is the new root node, as shown in Figure 6c, where, Deleting the root node only deletes the ID of the root node, but the contents included in the root node, such as the synchronization timestamp, the synchronization parent ID, the content changed in this synchronization, and the devices synchronized this time, are still retained.

Temporary intermediate node creation: The data synchronization process terminates abnormally, and a temporary intermediate node is created. The abnormal termination of the data synchronization process can be caused by an error in the synchronization data, and the data synchronization process is terminated; When the data synchronization process is abnormally terminated, the TOP node that originally performed data synchronization can be marked as a temporary intermediate node. The temporary intermediate node contains a temporary status identifier. The temporary intermediate node is used to save the synchronization data that has not completed data synchronization. When the data synchronization is completed again After that, the temporary intermediate node can be deleted.

Hereinafter, the stateful data synchronization method of the mobile distributed system of the present application will be described by taking the data synchronization between two devices as an example.

The first embodiment mainly describes how to synchronize data between device A and device B when there is no data change in device A in the mobile distributed system and data change in device B.

The mobile distributed system includes device A and device B, device A has performed data synchronization with other devices included in the mobile distributed system, and device B has also performed data synchronization with other devices included in the mobile distributed system. As shown in FIG. 7 , FIG. 7 is a schematic block diagram showing that device A and other devices have performed data synchronization and device B and other devices have performed data synchronization according to an embodiment of the present application.

Multiple sync nodes, multiple change lists, and multiple device lists have been created in the sync record on device A, such as:

Root node S _X , the change list corresponding to the Root node S _X includes: change list ID: C _x ; the device list corresponding to the synchronization record of the Root node includes: device list ID: D _x ;

For the intermediate node S _y , the change list corresponding to the intermediate node S _y includes: change list ID: C _y ; the device list corresponding to the synchronization record of the intermediate node includes: device list ID: D _y ;

Top node S _y+1 , the change list corresponding to the synchronization record of Top node S _y+1 includes: change list ID: C _y+1 ; the device list corresponding to the synchronization record of Top node S _y+1 includes: device list ID: D _y+1 , device ID: device D (the device ID being device D indicates that the current data synchronization is the data of device A synchronized with device D).

Multiple sync nodes, multiple change lists, and multiple device lists have been created in the sync record on device B, such as:

Root node S _X , the change list corresponding to the Root node S _X includes: change list ID: C _x ; the device list corresponding to the Root node includes: device list ID: D _x ;

For the intermediate node S _y , the change list corresponding to the intermediate node S _y includes: change list ID: C _y ; the device list corresponding to the intermediate node includes: device list ID: D _y ;

Top node S _y+1 , the change list corresponding to Top node S _y+1 includes: change list ID: C _y+1 ; the device list corresponding to the synchronization record of Top node S _y+1 includes: device list ID: D _{y+ 1.} Device ID: device D (device ID is device D, indicating that this data synchronization is the data of device B synchronized with device D).

When device B changes media assets, such as device B downloads audio B, device B adds a new change list to the change list, such as a new change list ID: C _y+2 , the content of the change list C _y+2 is to download audio B. Specifically, as shown in FIG. 8 , FIG. 8 is a schematic block diagram of a device B in an embodiment of the present application when a media asset is changed.

It should be understood that the device B can be a data change that occurs when it leaves the mobile distributed system, or it can be a data change that occurs when it is in the mobile distributed system. In the mobile distributed system, that is, device B does not leave the mobile distributed system. For a distributed system, for example, a user builds a mobile distributed system in a home, the mobile distributed system includes terminal equipment 1, terminal equipment 2 and terminal equipment 3, and being located in the mobile distributed system means that the terminal equipment is located in the home.

A method for synchronizing data in a mobile distributed system provided by the present application will be described in detail below with reference to FIG. 9 . FIG. 9 is a schematic flowchart of a method 200 for synchronizing data in a mobile distributed system according to an embodiment of the present application. The method 200 may It is applied in the scenario shown in FIG. 1 , and of course can also be applied in other scenarios, which is not limited in this embodiment of the present application.

It should also be understood that, in the embodiments of the present application, the method is described by taking the device A (as the first device) and the device B (as the second device) as the execution subjects of the execution method as examples. As an example but not a limitation, the execution body of the method may also be a chip, a chip system, or a processor, etc. applied to the device A and the device B.

As shown in FIG. 9, the method 200 shown in FIG. 9 may include S201 to S206. Each step in the method 200 will be described in detail below with reference to FIG. 9 .

S201 , the media asset of the device B is changed, and the device B adds a first change list, and the first change list includes the first change list ID and the content of the media asset change on the device B.

S202: Device A sends a first query request to device B, where the first query request is used to query whether there is a media asset change on device B.

S203, the device B receives the first query request sent by the device A.

S204, the device B determines that the first media asset is changed according to the first query request, and sends a first synchronization message to the device A, where the first synchronization message carries the content of the first media asset change of the device B, and the first synchronization message carries the content of the first media asset change of the device B. A media asset change content includes the changed first media asset and an action corresponding to the first media asset change. For example, the first synchronization message includes device B downloading audio B, or the first media asset carried in the first synchronization message is changed. The content is: download audio B, and the first synchronization message may also carry metadata of the content of the first media asset change, that is, the metadata of audio B. Wherein, the changed first media asset is audio B, and the action corresponding to the first media asset change is download.

S205: Device A receives the first synchronization message sent by device B.

S206, the device A generates a first synchronization record according to the first synchronization message, where the first synchronization record includes a first synchronization node, a first change list and a first device list, and the first synchronization node is used to record the first synchronization node. Information of data synchronization, the first change list is used to record the first media asset changed in the first data synchronization and the action corresponding to the change of the first media asset, the first device list is used to record the first data Synchronized devices.

It should be understood that the first data synchronization can be understood as the process of generating the first synchronization record after the device A receives the first synchronization message, which is a data synchronization.

Send the first query request to the device B through the device A; the device B sends the first synchronization message to the device A after receiving the first query request and judging that the first media asset is changed, and the device A According to the first synchronization message, a first synchronization record is generated, wherein the first synchronization record includes a first synchronization node, a first change list and a first device list, which realizes the asynchronous synchronization of the mobile distributed system.

It should be understood that when device A sends a first query request to device B, device B can also send a third query request to device A. The following describes in detail a method for data synchronization of a mobile distributed system provided by the present application in conjunction with FIG. 10 , FIG. 10 is a schematic flowchart of a method 300 for data synchronization in a mobile distributed system according to an embodiment of the present application. The method 300 can be applied to the scenario shown in FIG. 1 , and of course can also be applied to other scenarios. The embodiment is not limited here.

It should also be understood that, in the embodiments of the present application, the method is described by taking the device A and the device B as the execution subjects of the execution method as an example. As an example but not a limitation, the execution body of the method may also be a chip, a chip system, or a processor, etc. applied to the device A and the device B.

As shown in FIG. 10 , the method 300 shown in FIG. 10 may include S301 to S306. Each step in the method 300 will be described in detail below with reference to FIG. 10 .

S301 (that is, S201), the media asset of device B is changed, and device B adds a first change list, and the first change list includes the first change list ID and the content of the media asset change on device B.

S302 , the device B sends a third query request to the device A, where the third query request is used to query whether there is a media asset change on the device A.

S303, the device A receives the third query request sent by the device B.

S304, the device A determines that there is no media asset change according to the third query request, and sends a first feedback message to the device B, where the first feedback message is used to inform the device B that there is no media asset change on the device A.

S305, the device B receives the first feedback message sent by the device A.

S306, the device B generates a first synchronization record (which can be understood as the first synchronization record on the device B) according to the first feedback message and the first synchronization message, wherein the first synchronization message is the message sent by the device B to the device B. The first synchronization message sent by device A, the first synchronization message carries the first media asset modification content of device B, and the first media asset modification content includes the modified first media asset and the first media asset modification corresponding The first synchronization record includes a first synchronization node, a first change list and a first device list, the first synchronization node is used for the information of the first data synchronization; the first change list is used to record the first data synchronization The media asset that has changed and the action corresponding to the change of the media asset, the first change list is the first change list newly added by device B in S301. At this time, since there is no media asset change on device A, the first change list is The update list will not add new content; the first device list is used to record the device for this data synchronization.

It should be understood that the first data synchronization can be understood as the process of generating the first synchronization record on the device B after the device B receives the first feedback message, which is a data synchronization.

The process of generating the first synchronization record by device A and device B will be specifically described below with reference to FIG. 11 . FIG. 11 is a schematic block diagram of data synchronization between device A and device B according to an embodiment of the present application.

In Figure 11, the device on the left is Device A, the first synchronization node is generated on Device A, the first synchronization node is the Top node, the original Top node Sy+ ₁ becomes an intermediate node, and the Top node includes one or more of the following information : the first synchronization node identifier S _y+2 , the first synchronization timestamp at the Mth time, the first parent synchronization node identifier S _y+1 , the first synchronization change content, and the first synchronization device.

Optionally, the first synchronization change content includes the media asset change content of the device B, and the first synchronization device includes the device ID of the device B; or, the first synchronization change content includes the index of the first change list, the The first synchronization device includes an index of the device A list, the index of the change list is used to find the first change list, and the index of the device list is used to find the device A list; Or, the first synchronization change content includes the The index of the changed content of the first media asset, the first synchronization device includes an index related to the device B, the index of the change list is used to find the changed content of the first media asset, and the index related to the device B is used to find the content related to the device B. Information about the device B.

It should be understood that the information related to the device B may include one or more pieces of information such as the type of the device B, the name of the device B, and the storage size of the device B.

Device A creates a first changelist, the first changelist includes the first changelist ID: C _y+2 , and device B downloads audio B.

Device A creates a first device list, and the first device list includes first device list ID: _Dy+2 , device ID: device B.

Device A synchronizes the metadata corresponding to the change list in the database according to the change state information of the synchronization record. The metadata is metadata of the audio B downloaded by the device B, such as attribute information such as the storage location of the downloaded audio B, the download time, and the size of the audio B. The metadata of audio B downloaded by device B may be that when device A and device B perform data synchronization, device B transmits the metadata of audio B downloaded by device B to device A.

The device on the right is device B. For device B, device A has no data update, but device B has its own media asset update, and device A synchronizes the content of device B's media asset update, and generates the first synchronization on device B. Node, the first synchronization node is the Top node, the original Top node Sy+ ₁ becomes an intermediate node, and the Top node includes one or more of the following information: the first synchronization node identifier Sy+ ₂ , the first synchronization timestamp at the Mth time , the first parent synchronization node identifier S _y+1 , the first synchronization change content and the first synchronization device.

Device B is in the first change list C _y+2 and does not make any changes.

Device B creates a first device list, and the first device list includes first device list ID: _Dy+2 , device ID: device A.

It should be understood that, in the embodiments of the present application, only the device A and the device B perform data synchronization as an example, and the device A or the device B may also send a query message to all other online devices in the mobile distributed system.

The second embodiment mainly describes how to synchronize data between device A and device B when device A in the mobile distributed system has a media asset change and device B has a media asset change, and the process of device B having a media asset change can refer to the figure. 8 to understand.

Before the device A receives the first synchronization message sent by the device B, the media assets on the device A are changed. For example, if the device A creates a picture A, the device A adds a second change list, and the second change list includes the first change list. 2. Change list ID: C _y+2 and the content of the media asset change on the device A: create a picture A, as shown in FIG. 12 , which is a schematic block diagram of the device A in the embodiment of the present application when the media asset is changed.

A method for synchronizing data in a mobile distributed system provided by the present application will be described in detail below with reference to FIG. 13 . FIG. 13 is a schematic flowchart of a method 400 for synchronizing data in a mobile distributed system according to an embodiment of the present application. The method 400 may It is applied in the scenario shown in FIG. 1 , and of course can also be applied in other scenarios, which is not limited in this embodiment of the present application.

As shown in FIG. 13 , the method 400 shown in FIG. 13 may include S401 to S407 . Each step in the method 400 will be described in detail below with reference to FIG. 13 .

S401 (ie, S201, S301), the media asset of device B is changed, and device B adds a first change list, and the first change list includes the first change list ID and the content of the media asset change on device B

S402 , the media asset of the device A is changed, and the device A adds a second modification list, and the second modification list includes the second modification list ID and the media asset modification content on the device A.

The sequence of S401 and S402 is not limited here.

S403: Device A sends a first query request to device B, where the first query request is used to query whether there is a media asset change on device B.

S404, the device B receives the first query request sent by the device A.

S405, the device B determines that the first media asset is changed according to the first query request, and sends a first synchronization message to the device A, where the first synchronization message carries the content of the first media asset change of the device B, and the first synchronization message carries the content of the first media asset change of the device B. A media asset change content includes the changed first media asset and an action corresponding to the first media asset change. For example, the first synchronization message carries the media asset change content of device B: download audio B, the first synchronization message can also carry The first media asset alters the metadata of the content.

S406: Device A receives the first synchronization message sent by device B.

S407, the device A generates a second synchronization record according to the first synchronization message, where the second synchronization record includes a second synchronization node, a second change list and a second device list; the second synchronization node includes a second synchronization node ID, One or more of the second synchronization timestamp, the second parent synchronization node ID, the second synchronization change content, and the second synchronization device, the second synchronization node ID is used to identify the second data synchronization; in the second change list , add the media asset modification content of the device B; add the device ID of the device B in the second device list.

Device A has previously generated a second change list due to a media asset change. Therefore, after synchronizing data with device B, device A adds the media asset change content of device B to the second change list.

A method for synchronizing data in a mobile distributed system provided by the present application will be described in detail below with reference to FIG. 14 . FIG. 14 is a schematic flowchart of a method 500 for synchronizing data in a mobile distributed system according to an embodiment of the present application. The method 500 may It is applied in the scenario shown in FIG. 1 , and of course can also be applied in other scenarios, which is not limited in this embodiment of the present application.

As shown in FIG. 14, the method 500 shown in FIG. 14 may include S501 to S505. Each step in the method 500 will be described in detail below with reference to FIG. 14 .

S501 (ie, S201, S302, S401), the media assets of device B are changed, and device B adds a first change list, and the first change list includes the change list ID and the content of the media asset changes on device B.

S502 (ie, S402 ), the media assets of device A are changed, and device A adds a second change list, and the second change list includes the second change list ID and the content of media asset changes on device A.

The sequence of S501 and S502 is not limited here.

S503 , the device B sends a fourth query request to the device A, where the fourth query request is used to query whether there is a media asset change on the device A.

S504, the device A receives the fourth query request sent by the device B.

S505, the device A determines that the first media asset is changed according to the fourth query request, and sends a third synchronization message to the device B, where the third synchronization message carries the content of the first media asset change of the device A, and the first media asset is changed. A media asset change content includes the first media asset changed on device A and the action corresponding to the first media asset change. For example, the third synchronization message includes the media asset change content of device A: create picture A, the third synchronization message The metadata of the content of the first media asset change may also be carried.

S506, the device B receives the third synchronization message sent by the device A.

S507, the device B generates a second synchronization record (the second synchronization record on the device B) according to the third synchronization message, and the second synchronization record includes the second synchronization node, the first change list and the second device list; The second synchronization node includes a second synchronization node ID, one or more of a second synchronization timestamp, a second parent synchronization node identifier, a second synchronization change content, and a second synchronization device, and the second synchronization node ID is used for Identifies the second data synchronization; in the second modification list, adds the media asset modification content of the first device; and adds the device ID of the first device in the second device list.

The process of generating synchronization records by device A and device B will be specifically described below with reference to FIG. 15 . FIG. 15 is a schematic block diagram of data synchronization between device A and device B according to an embodiment of the present application.

In Figure 15, the device on the left is device A, a new synchronization node is generated on device A, the new synchronization node is the Top node, the original Top node S _y+1 becomes an intermediate node, and the Top node includes one or more of the following information : the synchronization node identifier S _y+2 , the M-th time of the synchronization timestamp, the parent synchronization node identifier S _y+1 , the synchronization change content and the synchronization device.

The device A adds the content of the media asset change of the device B in the change list C _y+2 . For example, the content of the change list includes: the device A creates a picture A and the device B downloads the audio B.

Device A creates a device list, and the device list includes device list ID: D _y+2 , device ID: device B.

Device A synchronizes the metadata corresponding to the change list in the database according to the change state information of the synchronization record.

The device on the right is device B. For device B, device A has media asset updates, and a new synchronization node is generated on device B. The new synchronization node is the Top node, and the original Top node S _y+1 becomes an intermediate node. The node includes one or more of the following information: synchronization node identifier S _y+2 , synchronization timestamp M-th time, parent synchronization node identifier S _y+1 , synchronization change content and synchronization device.

The device B adds the content of the media asset change of the device A in the change list C _y+2 . For example, the content of the change list includes: the device A creates a picture A and the device B downloads the audio B.

Device B creates a device list, and the device list includes device A list ID: D _y+2 , device ID: device A.

The third embodiment mainly describes that after device A and device B in the mobile distributed system have performed data synchronization, because the media assets of device B are changed (such as when device B changes data again, such as when device B downloads audio C, Device B adds a new change list to the change list, such as adding a new change list ID: C _y+3 , the content of the change list C _y+3 is to download audio C, as shown in Figure 16) When data synchronization is required, the device How to synchronize data between A and device B.

The following describes a method for synchronizing data in a mobile distributed system provided by the present application in detail with reference to FIG. 17 . FIG. 17 is a schematic flowchart of a method 600 for synchronizing data in a mobile distributed system according to an embodiment of the present application. The method 600 may It is applied in the scenario shown in FIG. 1 , and of course can also be applied in other scenarios, which is not limited in this embodiment of the present application.

As shown in FIG. 17 , the method 600 shown in FIG. 17 may include S601 to S606. Each step in the method 600 will be described in detail below with reference to FIG. 17 .

S601 , a media asset of the device B is changed, and the device B adds a third change list, and the third change list includes the change list ID and the content of the media asset change on the device B.

S602: Device A sends a second query request to device B, where the second query request is used to query whether there is a media asset change on device B.

S603, the device B receives the second query request sent by the device A.

S604, the device B determines that there is a second media asset change according to the second query request, and sends a second synchronization message to the device A, where the second synchronization message carries the content of the second media asset change of the device B, the first The second media asset change content includes the changed second media asset and the action corresponding to the second media asset change. For example, the second synchronization message includes device B downloading audio B, and the second synchronization message can also carry the second media asset change content. metadata.

S605: Device A receives the second synchronization message sent by device B.

S606: Device A generates a third synchronization record according to the second synchronization message, where the third synchronization record includes a third synchronization node, a third change list and a third device list, where the third synchronization node includes: a third synchronization node ID, one or more of the third synchronization timestamp, the third parent synchronization node identifier, the third synchronization change content and the third synchronization device, wherein the third synchronization node ID is used to identify the three data synchronization; the third modification The list includes a third change list ID, and the second media asset of the second device changes content; the third device list includes a third device list ID, and a device ID of the second device.

S607, the device A removes the device ID of the device B in the first device list ID.

It should be understood that the above method 600 describes how device A and device B have already performed data synchronization once. When the media assets of device B are updated again, how device A synchronizes device B. Similarly, device B will also synchronize the data of device A, but only There is no media asset update on device A, device B will generate a new synchronization record, the new synchronization record includes the new node, the third change list and the device list, device B removes the device of device A in the first device list ID ID, the specific details can refer to the process of device A, which will not be repeated here.

The process of generating the third synchronization record by device A and device B will be specifically described below with reference to FIG. 18 . FIG. 18 is a schematic block diagram of data synchronization between device A and device B according to an embodiment of the present application.

In Fig. 18, the device on the left is device A, a third synchronization node is generated on device A, the third synchronization node is the Top node, the original Top node S _y+2 becomes an intermediate node, and the Top node includes one of the following information or Multiple: third synchronization node identification S _y+3 , third synchronization timestamp M+1 th time, third parent synchronization node identification S _y+2 , third synchronization change content and third synchronization device.

Device A creates a third changelist that includes the third changelist ID: C _y+3 , and device B downloads audio C.

Device A creates a third device list, and the third device list includes device A list ID: _Dy+3 , device ID: device B.

The device A removes the device ID of the device B in the first device list ID. Device A synchronizes the metadata corresponding to the change list in the database according to the change state information of the synchronization record.

The device on the right is device B. For device B, device A has no data update, but device B has its own media asset update, and device A synchronizes the content of device B's media asset update, and generates a new synchronization node on device B , the new synchronization node is the Top node, the original Top node S _y+2 becomes an intermediate node, and the Top node includes one or more of the following information: the synchronization node identifier S _y+3 , the synchronization timestamp at the M+1th time, the parent The synchronization node identifies S _y+2 , synchronizes changes, and synchronizes equipment.

In this change list C _y+3 , no changes are made.

Device B creates a device list, and the device list includes device list ID: D _y+3 , device ID: device A.

The device B removes the device ID of the device A in the fourth device list ID. Device B synchronizes the metadata corresponding to the change list in the database according to the change state information of the third synchronization record.

The above embodiments specifically describe how the terminal device performs data synchronization in the mobile distributed system. When the terminal device performs data synchronization, data security needs to be considered, and the synchronized data cannot be arbitrarily tampered with. The embodiment of the present application also proposes a method for data synchronization of a mobile distributed system, which realizes the block chaining and state encryption of log data, and ensures that the log data is tamper-proof.

The embodiments of the present application mainly implement the block chaining and state encryption of log data according to a hash algorithm, so as to ensure that the log data is tamper-proof. For a clearer understanding of the embodiments of the present application, the hash algorithm is briefly described below.

A hash algorithm is a mapping rule that maps a binary string of arbitrary length to a fixed-length binary string. We call it a hash algorithm, also known as a hash algorithm, and the binary value obtained after mapping the original data called the hash value. The main features of the hash algorithm:

1. The original data cannot be reversely derived from the hash value, which is one-way computational and extremely difficult to reverse;

2. Sensitive to input data, even if only one Bit is changed, the final hash value is completely different, which has an avalanche effect;

3. The probability of hash collision is extremely small, the hash factor Key is different, and the probability of the calculated hash value is the same is extremely small.

FIG. 19 is a schematic block diagram of a stateful data synchronization structure of a mobile distributed system according to an embodiment of the present application. When different devices synchronize data, the device whose data is changed will perform a hash operation on the content of each change in the change list to obtain a first hash value, and send the first hash value to the device performing data synchronization , the data synchronization device performs hash calculation according to the synchronized change list to obtain a second hash value. If the first hash value is equal to the second hash value, it means that the current data synchronization is successful, otherwise it is unsuccessful. A specific description will be given with reference to FIG. 19 .

For a clearer understanding of the embodiments of the present application, the parameters in FIG. 19 are explained first.

As shown in Figure 19, C1 is the parent node of C2;

F _CN : Indicates the content of the change list header;

F _LN : Indicates the node content of the change list, such as deleting pictures, deleting music, creating pictures, etc.;

Nouce: A one-time random number, generated by the application node, that is, the device generated by the data change, the Nouce will be encrypted and transmitted to the receiving node, usually when the connection is established for the first time, the application node will pass the Nouce to the receiving node. Among them, the receiving node is a device for data synchronization;

H _CN : Change the hash value of the list header, which is generated independently by each node and is not transmitted.

H _LN : Change the hash value of each change record in the list, apply for node generation, clear text transmission, and receive node verification;

Change log: Every time the content is changed.

The node shown in Figure 19 can be regarded as a request node, where C1 is the parent node of C2. On the request node, the hash value of the change list header of the parent node C1 is calculated according to formula (1):

H _c1 =HASH(F _C1 ,Nouce) (1)

The hash value of the change record L1 is calculated according to formula (2):

H _L1 =HASH(H _C1 ,F _L1 ) (2)

The hash value of the change record L2 is calculated according to formula (3):

H _L2 =HASH(H _C1 ,H _L1 ,F _L2 ) (3)

The hash value of the change record L3 is calculated according to formula (4):

H _L3 =HASH(H _C1 ,H _L2 ,F _L3 ) (4)

The hash value of the change record L4 is calculated according to formula (5):

H _L4 =HASH(H _C1 ,H _L3 ,F _L4 ) (5)

The hash value of the change record L5 is calculated according to formula (6):

H _L5 = HASH (H _C1 , H _L4 , F _L5 ) (6)

Wherein, the hash factor of _each change record LN in the node C1 change list is the hash value of the header of the C1 change list, the hash value of the last change record LN _-1 , and the change content of _LN .

The hash value of the change list header of the child node C2 is calculated according to formula (7):

H _c2 = HASH(H _C1 , H _L5 , F _C2 ) (7)

Wherein, H _L5 in the formula (7) is the last node of the C1 node.

The hash value of the change record L6 in the change list of the child node C2 is calculated according to formula (8):

H _L6 =HASH(H _C2 ,F _L6 ) (8)

The hash value of the change record L7 is calculated according to formula (9):

H _L7 =HASH(H _C1 ,H _L6 ,F _L7 ) (9)

Wherein, the hash factor of _each change record LN in the node C2 change list is the hash value of the C2 change list header, the hash value of the last change record LN _-1 , and the change content of _LN .

The requesting node performs node-by-node synchronization status, synchronization content and system key hash for the synchronization data block, and the requesting node calculates the value of each data synchronization change.

And pass it to the receiving node. When the receiving node parses the synchronized data, a protection mechanism is introduced in the change list node, and the hash is obtained through the pre-hash of the parent node and the content of the parent node.

compare

and

if

equal

Indicates that the synchronization content is correct and data synchronization can be performed; if

not equal to

Indicates that the content of the synchronization is wrong and needs to be re-synchronized.

It should be understood that the embodiments of the present application shown in FIG. 19 can be combined with the embodiments of the present application shown in FIGS. 4 to 19 , that is, a verification mechanism is introduced during data synchronization in a distributed system to ensure the reliability and security of synchronized data. sex.

A method for data synchronization of a mobile distributed system according to an embodiment of the present application has been described in detail above with reference to FIG. 1 to FIG. 19 . Hereinafter, the device according to the embodiment of the present application will be described in detail with reference to FIG. 20 to FIG. 21 .

FIG. 20 shows a schematic block diagram of an apparatus 800 according to an embodiment of the present application.

In some embodiments, the apparatus 700 may be a terminal device, or may be a chip or a circuit, for example, a chip or a circuit that can be provided in the terminal device.

In some embodiments, the apparatus 700 may be an access network device, or may be a chip or a circuit, for example, a chip or a circuit that may be provided in the access network device.

In some embodiments, the apparatus 700 may be a core network device, or may be a chip or a circuit, for example, a chip or a circuit that may be provided in the core network device.

In a possible manner, the apparatus 700 may include a processing unit 710 (ie, an example of a processor) and a transceiver unit 730 . In some possible implementations, the processing unit 710 may also be referred to as a determination unit. In some possible implementations, the transceiver unit 730 may include a receiving unit and a sending unit.

In an implementation manner, the transceiver unit 730 may be implemented by a transceiver or a transceiver-related circuit or an interface circuit.

In one implementation, the apparatus may further include a storage unit 720 . In a possible manner, the storage unit 720 is used to store instructions. In one implementation, the storage unit may also be used to store data or information. The storage unit 720 may be implemented by a memory.

In some possible designs, the processing unit 710 is configured to execute the instructions stored in the storage unit 720, so that the apparatus 700 implements the steps performed by the terminal device in the above method. Alternatively, the processing unit 710 can be used to call the data of the storage unit 720, so that the apparatus 700 can implement the steps performed by the terminal device in the above method.

In some possible designs, the processing unit 710 is configured to execute the instructions stored in the storage unit 720, so that the apparatus 700 implements the steps performed by the access network device in the above method. Alternatively, the processing unit 710 may be configured to call the data of the storage unit 720, so that the apparatus 700 implements the steps performed by the access network device in the above method.

For example, the processing unit 710, the storage unit 720, and the transceiver unit 730 can communicate with each other through an internal connection path to transmit control and/or data signals. For example, the storage unit 720 is used to store a computer program, and the processing unit 710 can be used to call and run the computer program from the storage unit 720 to control the transceiver unit 730 to receive signals and/or send signals to complete the above method. Steps for terminal equipment or access network equipment. The storage unit 720 may be integrated in the processing unit 710 , or may be provided separately from the processing unit 710 .

Optionally, if the apparatus 700 is a terminal device (eg, a smart phone, or a notebook computer), the transceiver unit 730 includes a receiver and a transmitter. The receiver and the transmitter may be the same or different physical entities. When they are the same physical entity, they can be collectively referred to as transceivers.

When the apparatus 700 is a terminal device, the transceiver unit 730 can be a sending unit or a transmitter when sending information, the transceiver unit 730 can be a receiving unit or a receiver when receiving information, and the transceiver unit can be a transceiver, the transceiver, The transmitter or receiver may be a radio frequency circuit, and when the device includes a storage unit, the storage unit is used to store computer instructions, the processor is communicatively connected to the memory, and the processor executes the computer instructions stored in the memory, so that the device can perform the method 200 , method 500 or method 600 . The processor may be a general-purpose central processing unit (CPU), a microprocessor, or an application specific integrated circuit (ASIC).

Optionally, if the device 700 is a chip or a circuit, the transceiver unit 730 includes an input interface and an output interface.

When the device 700 is a chip, the transceiver unit 730 may be an input and/or output interface, a pin or a circuit, or the like. The processing unit 710 can execute computer-executable instructions stored in the storage unit, so that the apparatus can perform the method 200 , the method 500 or the method 600 . Optionally, the storage unit is a storage unit in the chip, such as a register, a cache, etc., and the storage unit may also be a storage unit in the terminal located outside the chip, such as a read-only memory (Read Only Memory). Only Memory, ROM) or other types of static storage devices that can store static information and instructions, random access memory (Random Access Memory, RAM), etc.

As an implementation manner, the function of the transceiver unit 730 can be considered to be implemented by a transceiver circuit or a dedicated chip for transceiver. The processing unit 710 can be considered to be implemented by a dedicated processing chip, a processing circuit, a processing unit or a general-purpose chip.

As another implementation manner, a general-purpose computer may be used to implement the communication device (for example, a terminal device, or an access network device) provided in this embodiment of the present application. The program codes that will implement the functions of the processing unit 710 and the transceiver unit 730 are stored in the storage unit 720 , and the general processing unit implements the functions of the processing unit 710 and the transceiver unit 730 by executing the codes in the storage unit 720 .

In some embodiments, the apparatus 700 may be the first device, or a chip or circuit provided in the first device. When the apparatus 700 is the first device, or is provided in a chip or circuit of the first device, the transceiver unit 730 is configured to send a first query request to the second device, where the first query request is used to query the second device Whether there is a media asset change; the transceiver unit 730 is further configured to receive the first synchronization message sent by the second device, the first synchronization message is that the second device receives the first query request and determines that there is a Sent to the first device after the first media asset is changed, the first synchronization message carries the first media asset change content of the second device, and the first media asset change content includes the changed first media asset. The action corresponding to the change of the media asset and the first media asset; the processing unit 710 is configured to generate a first synchronization record according to the first synchronization message, wherein the first synchronization record includes a first synchronization node, a first synchronization A change list and a first device list, the first synchronization node is used to record the information of the first data synchronization, and the first change list is used to record the first media assets that have been changed in the first data synchronization and the The action corresponding to the change of the first media asset, and the first device list is used to record the device for which the first data is synchronized.

In an implementation manner, the first synchronization node includes: one or more of a first synchronization node identifier, a first synchronization timestamp, a first parent synchronization node identifier, a first synchronization change content, and a first synchronization device , wherein the first synchronization node ID is used to identify the first data synchronization; the first change list includes: the first change list ID and the first media asset change content of the second device; the The first device list includes: the first device list ID and the device ID of the second device.

In an implementation manner, the first synchronization change content includes the first media asset change content of the second device, and the first synchronization device includes the device ID of the second device; or, the first synchronization change The content includes an index of the first change list, the first synchronization device includes an index of the first device list, the index of the change list is used to find the first change list, and the index of the device list is used to find the first device list; or, the first synchronization change content includes an index of the first media asset change content, the first synchronization device includes an index related to a second device, the first media The index of the asset modification content is used to search for the first media asset modification content, and the index related to the second device is used to search for information related to the second device.

In an implementation manner, before the first device receives the first synchronization message sent by the second device, the media asset on the first device is changed, and the processing unit 710 is further configured to: add a second change list, the second change list includes a second change list ID and media asset changes on the first device.

In an implementation manner, after the first device receives the first synchronization message sent by the second device, the processing unit 710 is further configured to: the first device generates a second synchronization message according to the first synchronization message record, the second synchronization record includes the second synchronization node, the second change list and the second device list; the second synchronization node includes the second synchronization node ID, the second synchronization timestamp, the second parent synchronization node One or more of the identifier, the second synchronization change content, and the second synchronization device, the second synchronization node ID is used to identify the second data synchronization; in the second change list, add the media assets of the second device Change the content; add the device ID of the second device to the second device list.

In an implementation manner, the transceiver unit 730 is further configured to: send a second query request to the second device, where the second query request is used to query whether there is a media asset change on the second device; receive The second synchronization message sent by the second device, where the second synchronization message is sent to the first device after the second device receives the second query request and determines that the second media asset is changed , the second synchronization message carries the second media asset change content of the second device, and the second media asset change content includes the changed second media asset and the action corresponding to the second media asset change; The processing unit 710 is further configured to: generate a third synchronization record according to the second synchronization message, where the third synchronization record includes a third synchronization node, a third change list and a third device list, wherein the third synchronization record is The three synchronization nodes include a third synchronization node ID, one or more of a third synchronization timestamp, a third parent synchronization node identifier, a third synchronization change content, and a third synchronization device, wherein the third synchronization node ID Used to identify three data synchronization; the third change list includes a third change list ID, the second media asset of the second device changes content; the third device list includes a third device list ID, and the second Device ID of the device;

In an implementation manner, the device ID in the first device list is empty, and the processing unit deletes the first device list.

In an implementation manner, when the first synchronization node is a root (Root) node, the root node and the first change list are deleted, and the synchronization node adjacent to the root node becomes a new root node .

In an implementation manner, the third synchronization node is a top node, and a node between the top node and the root node is a middle node.

In an implementation manner, when the data synchronization process between the first device and the second device terminates abnormally, the processing unit 710 is further configured to: create a temporary intermediate node, where the temporary intermediate node includes a temporary state identifier, the temporary intermediate node is used to save the synchronization data for which data synchronization is not completed.

In an implementation manner, when the first data is synchronized, the transceiver unit 730 is further configured to receive a first hash value sent by the second device, where the first hash value is the second hash value Obtained from the hash operation performed by the device according to the content of the first media asset change, the first synchronization message includes the first hash value; the processing unit 710 is further configured to perform the change according to the content of the first change list Hash calculation to obtain a second hash value; when the processing unit determines that the first hash value is equal to the second hash value, the processing unit determines that the current data synchronization is successful.

When the apparatus 700 is configured in or is itself the first device, each module or unit in the apparatus 700 can be used to perform each action or processing process performed by the device A in the above method. Here, in order to avoid redundant description, the detailed description thereof is omitted. .

In some embodiments, the apparatus 700 may be the second device, or a chip or circuit provided in the second device. When the apparatus 700 is the second device, or is provided in a chip or circuit of the second device, the transceiver unit 730 is configured to receive a first query request sent by the first device, where the first query request is used to query the second device Whether there is a media asset change on the server; the processing unit 710 is configured to determine, according to the first query request, that there is a first media asset change, and send a first synchronization message to the first device, where the first synchronization message carries the The content of the first media asset change of the second device, where the content of the first media asset change includes the changed first media asset and an action corresponding to the change of the first media asset.

In an implementation manner, when the first media asset on the second device is changed, the processing unit 710 is further configured to add a first change list; the transceiver unit 730 is further configured to: send a message to the The first device sends a third query request, where the third query request is used to query whether there is a media asset change on the first device; and receives a first feedback message sent by the first device, where the first feedback message is Sent by the first device to the second device after receiving the third query request and judging that there is no media asset change on the first device, the first feedback message is used to identify the first No media asset change has occurred on the device; the processing unit 710 is further configured to: generate a first synchronization record according to the first feedback message and the first synchronization message, where the first synchronization record includes the first synchronization node, the first change list and the first device list, the first synchronization node is used to record the information of the first data synchronization, and the first change list is used to record the changed media in the first data synchronization The asset is an action corresponding to the change of the media asset, and the first device list is used to record the device for which the first data is synchronized.

In an implementation manner, the first synchronization node includes: one or more of a first synchronization node identifier, a first synchronization timestamp, a first parent synchronization node identifier, a first synchronization change content, and a first synchronization device , wherein the first synchronization node ID is used to identify the first data synchronization; the first change list includes: the first change list ID and the content of the media asset change of the second device; the first change list The device list includes: a first device list ID and a device ID of the first device.

In an implementation manner, the first synchronization change content includes the media asset change content of the second device, and the first synchronization device includes the device ID of the first device; or, in the first synchronization change content Including the index of the first change list, the first synchronization device includes the index of the first device list, the index of the change list is used to find the first change list, and the index of the device list is used to find the A first device list; or, the first synchronization change content includes an index of the media asset change content of the second device, the first synchronization device includes an index related to the first device, and the second device The index of the modified content of the media asset is used to look up the modified content of the media asset of the second device, and the index related to the first device is used to look up the information related to the first device.

In an implementation manner, the processing unit 710 is specifically configured to: determine that the first media asset is changed according to the first query request and the synchronization record on the second device; or, according to the first query request and the synchronization record on the second device The change list on the second device determines that the first media asset is changed.

In an implementation manner, the first synchronization message includes a first hash value, and the first hash value is obtained by the processing unit performing a hash operation according to the changed content of the first media asset.

When the apparatus 700 is configured in or itself is the second device, each module or unit in the apparatus 700 can be used to perform each action or processing process performed by the device B in the above method. Here, in order to avoid redundant description, the detailed description thereof is omitted. .

FIG. 21 is a schematic structural diagram of a terminal device 800 provided by this application. The terminal device 800 may perform the actions performed by the first device and the second device in the foregoing method embodiments.

For convenience of explanation, FIG. 21 shows only the main components of the terminal device. As shown in FIG. 21 , the terminal device 800 includes a processor, a memory, a control circuit, an antenna, and an input and output device.

The processor is mainly used to process communication protocols and communication data, and to control the entire terminal device, execute software programs, and process data of the software programs, for example, for supporting the terminal device to execute the above-mentioned transmission precoding matrix instruction method embodiment. the described action. The memory is mainly used to store software programs and data, such as the codebook described in the above embodiments. The control circuit is mainly used for the conversion of the baseband signal and the radio frequency signal and the processing of the radio frequency signal. The control circuit together with the antenna can also be called a transceiver, which is mainly used to send and receive radio frequency signals in the form of electromagnetic waves. Input and output devices, such as touch screens, display screens, and keyboards, are mainly used to receive data input by users and output data to users.

When the terminal device is powered on, the processor can read the software program in the storage unit, interpret and execute the instructions of the software program, and process the data of the software program. When data needs to be sent wirelessly, the processor performs baseband processing on the data to be sent, and outputs the baseband signal to the radio frequency circuit. The radio frequency circuit performs radio frequency processing on the baseband signal and sends the radio frequency signal through the antenna in the form of electromagnetic waves. When data is sent to the terminal device, the radio frequency circuit receives the radio frequency signal through the antenna, converts the radio frequency signal into a baseband signal, and outputs the baseband signal to the processor, which converts the baseband signal into data and processes the data.

Those skilled in the art can understand that, for the convenience of description, FIG. 21 only shows one memory and one processor. In an actual terminal device, there may be multiple processors and memories. The memory may also be referred to as a storage medium or a storage device, etc., which is not limited in this embodiment of the present application.

For example, the processor may include a baseband processor and a central processing unit. The baseband processor is mainly used to process communication protocols and communication data. The central processing unit is mainly used to control the entire terminal device, execute software programs, and process software programs. data. The processor in FIG. 21 integrates the functions of the baseband processor and the central processing unit. Those skilled in the art can understand that the baseband processor and the central processing unit may also be independent processors, interconnected by technologies such as a bus. Those skilled in the art can understand that a terminal device may include multiple baseband processors to adapt to different network standards, a terminal device may include multiple central processors to enhance its processing capability, and various components of the terminal device may be connected through various buses. The baseband processor may also be expressed as a baseband processing circuit or a baseband processing chip. The central processing unit can also be expressed as a central processing circuit or a central processing chip. The function of processing the communication protocol and communication data may be built in the processor, or may be stored in the storage unit in the form of a software program, and the processor executes the software program to realize the baseband processing function.

Exemplarily, in this embodiment of the present application, an antenna and a control circuit with a transceiver function may be regarded as the transceiver unit 810 of the terminal device 800 , and a processor with a processing function may be regarded as the processing unit 820 of the terminal device 800 . As shown in FIG. 21 , the terminal device 800 includes a transceiver unit 810 and a processing unit 820 . The transceiving unit may also be referred to as a transceiver, a transceiver, a transceiving device, or the like. Optionally, the device for implementing the receiving function in the transceiver unit 810 may be regarded as a receiving unit, and the device for implementing the transmitting function in the transceiver unit 810 may be regarded as a transmitting unit, that is, the transceiver unit includes a receiving unit and a transmitting unit. Exemplarily, the receiving unit may also be referred to as a receiver, a receiver, a receiving circuit, and the like, and the transmitting unit may be referred to as a transmitter, a transmitter, or a transmitting circuit, or the like.

It should be understood that, in this embodiment of the present application, the processor may be a central processing unit (central processing unit, CPU), and the processor may also be other general-purpose processors, digital signal processors (digital signal processors, DSP), dedicated integrated Circuit (application specific integrated circuit, ASIC), off-the-shelf programmable gate array (field programmable gate array, FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.

It should also be understood that the memory in the embodiments of the present application may be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. The non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically programmable Erase programmable read-only memory (electrically EPROM, EEPROM) or flash memory. Volatile memory may be random access memory (RAM), which acts as an external cache. By way of example and not limitation, many forms of random access memory (RAM) are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (DRAM) Access memory (synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous connection dynamic random access memory Fetch memory (synchlink DRAM, SLDRAM) and direct memory bus random access memory (direct rambus RAM, DR RAM).

The above embodiments may be implemented in whole or in part by software, hardware, firmware or any other combination. When implemented in software, the above-described embodiments may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions or computer programs. When the computer instructions or computer programs are loaded or executed on a computer, all or part of the processes or functions described in the embodiments of the present application are generated. The computer may be a general purpose computer, special purpose computer, computer network, or other programmable device. The computer instructions may be stored in or transmitted from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions may be downloaded from a website site, computer, server or data center Transmission to another website site, computer, server or data center by wire (eg, infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server, a data center, or the like that contains one or more sets of available media. The usable media may be magnetic media (eg, floppy disks, hard disks, magnetic tapes), optical media (eg, DVDs), or semiconductor media. The semiconductor medium may be a solid state drive.

Embodiments of the present application further provide a computer-readable medium on which a computer program is stored, and when the computer program is executed by a computer, implements the steps performed by the first device or the steps performed by the second device in any of the foregoing embodiments .

Embodiments of the present application further provide a computer program product, which, when executed by a computer, implements the steps performed by the first device or the steps performed by the second device in any of the foregoing embodiments.

An embodiment of the present application also provides a system chip, where the system chip includes: a communication unit and a processing unit. The processing unit may, for example, be a processor. The communication unit may be, for example, a communication interface, an input/output interface, a pin or a circuit, or the like. The processing unit can execute computer instructions, so that the chip in the communication apparatus executes the steps performed by the first device or the steps performed by the second device provided in the foregoing embodiments of the present application.

Optionally, the computer instructions are stored in a storage unit.

According to the method provided by the embodiment of the present application, the embodiment of the present application further provides a communication system, which includes the aforementioned first device and the second device.

Each embodiment in this application can be used independently or in combination, which is not limited here.

Additionally, various aspects or features of the present application may be implemented as a method, apparatus, or article of manufacture using standard programming and/or engineering techniques. The term "article of manufacture" as used in this application encompasses a computer program accessible from any computer readable device, carrier or medium. For example, computer readable media may include, but are not limited to: magnetic storage devices (eg, hard disks, floppy disks, or magnetic tapes, etc.), optical disks (eg, compact discs (CDs), digital versatile discs (DVDs) etc.), smart cards and flash memory devices (eg, erasable programmable read-only memory (EPROM), card, stick or key drives, etc.). Additionally, various storage media described herein can represent one or more devices and/or other machine-readable media for storing information. The term "machine-readable medium" may include, but is not limited to, wireless channels and various other media capable of storing, containing, and/or carrying instructions and/or data.

It should be understood that "and/or", which describes the relationship between related objects, means that there can be three kinds of relationships, for example, A and/or B, which can mean that A exists alone, A and B exist at the same time, and B exists alone. condition. The character "/" generally indicates that the associated objects are an "or" relationship. "At least one" refers to one or more than one; "at least one of A and B", similar to "A and/or B", describes the association relationship of associated objects, indicating that there can be three kinds of relationships, for example, A and B At least one of the three cases can represent: A exists alone, A and B exist simultaneously, and B exists alone.

Those of ordinary skill in the art can realize that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Skilled artisans may implement the described functionality using different methods for each particular application, but such implementations should not be considered beyond the scope of this application.

Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working process of the above-described systems, devices and units may refer to the corresponding processes in the foregoing method embodiments, which will not be repeated here.

In the several embodiments provided in this application, it should be understood that the disclosed system, apparatus and method may be implemented in other manners. For example, the apparatus embodiments described above are only illustrative. For example, the division of the units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored, or not implemented. On the other hand, the shown or discussed mutual coupling or direct coupling or communication connection may be through some interfaces, indirect coupling or communication connection of devices or units, and may be in electrical, mechanical or other forms.

The units described as separate components may or may not be physically separated, and components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution in this embodiment.

In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically alone, or two or more units may be integrated into one unit.

The functions, if implemented in the form of software functional units and sold or used as independent products, may be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application can be embodied in the form of a software product in essence, or the part that contributes to the prior art or the part of the technical solution. The computer software product is stored in a storage medium, including Several instructions are used to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), magnetic disk or optical disk and other media that can store program codes .

The above are only specific embodiments of the present application, but the protection scope of the present application is not limited to this. should be covered within the scope of protection of this application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims.

Claims

A method for data synchronization in a mobile distributed system, comprising:

The first device sends a first query request to the second device, where the first query request is used to query whether there is a media asset change on the second device;

The first device receives the first synchronization message sent by the second device, where the first synchronization message is sent to the first device by the second device after receiving the first query request and judging that the first media asset is changed. Sent by the device, the first synchronization message carries the first media asset change content of the second device, and the first media asset change content includes the changed first media asset and the first media asset change corresponding Actions;

The first device generates a first synchronization record according to the first synchronization message, wherein the first synchronization record includes a first synchronization node, a first change list and a first device list, and the first synchronization node uses For recording the information of the first data synchronization, the first change list is used to record the first media asset changed in the first data synchronization and the action corresponding to the change of the first media asset, and the first device list A device for recording the first data synchronization.
The method of claim 1, wherein:

The first synchronization node includes: one or more of a first synchronization node identification, a first synchronization timestamp, a first parent synchronization node identification ID, a first synchronization change content, and a first synchronization device, wherein the first synchronization node The synchronization node ID is used to identify the first data synchronization;

The first change list includes: a first change list ID and the first media asset change content of the second device;

The first device list includes: a first device list ID and a device ID of the second device.
The method according to claim 2, wherein the first synchronization change content comprises a first media asset change content of a second device, and the first synchronization device includes a device ID of the second device; or,

The first synchronization change content includes an index of a first change list, the first synchronization device includes an index of a first device list, and the index of the change list is used to find the first change list, the device The index of the list is used to look up the first device list; or,

The first synchronization change content includes an index of the first media asset change content, the first synchronization device includes an index related to the second device, and the index of the first media asset change content is used to find the index of the first media asset change content. The first media asset changes content, and the index related to the second device is used to search for information related to the second device.
The method according to claim 1, wherein before the first device receives the first synchronization message sent by the second device, the method further comprises:

When the media asset on the first device is changed, the first device adds a second change list, and the second change list includes the second change list ID and the content of the media asset change on the first device.
The method according to claim 4, wherein after the first device receives the first synchronization message sent by the second device, the method further comprises:

The first device generates a second synchronization record according to the first synchronization message, where the second synchronization record includes a second synchronization node, the second change list and a second device list;

The second synchronization node includes a second synchronization node ID, one or more of a second synchronization time stamp, a second parent synchronization node identifier, a second synchronization change content, and a second synchronization device, and the second synchronization node ID for identifying the second data synchronization;

In the second modification list, add the media asset modification content of the second device;

The device ID of the second device is added to the second device list.
The method according to any one of claims 2 to 5, wherein the method further comprises:

The first device sends a second query request to the second device, where the second query request is used to query whether there is a media asset change on the second device;

The first device receives the second synchronization message sent by the second device, where the second synchronization message is that the second device receives the second query request and determines that the second media asset is changed and then sends the message to the second device. sent by the first device, the second synchronization message carries the second media asset change content of the second device, and the second media asset change content includes the changed second media asset and the second media Actions corresponding to asset changes;

The first device generates a third synchronization record according to the second synchronization message, where the third synchronization record includes a third synchronization node, a third change list and a third device list,

The third synchronization node includes one or more of a third synchronization node ID, a third synchronization timestamp, a third parent synchronization node identifier, a third synchronization change content, and a third synchronization device, wherein the third synchronization node The three synchronization node ID is used to identify the three data synchronization;

The third change list includes a third change list ID, and the second media asset of the second device changes the content;

The third device list includes a third device list ID, and the device ID of the second device;

The device ID of the second device in the first device list ID is removed.
The method according to claim 6, wherein the device ID in the first device list is empty, and the first device list is deleted.
The method according to claim 7, wherein when the first synchronization node is a root (Root) node, delete the root node and the first change list, and synchronize with the neighbors of the root node The node becomes the new root node.
The method according to any one of claims 6 to 8, wherein the third synchronization node is a top (Top) node, and a node between the top node and the root node is a middle (middle) node node.
The method according to any one of claims 1 to 8, wherein when a data synchronization process between the first device and the second device is abnormally terminated, a temporary intermediate node is created, and the temporary intermediate node It contains a temporary state identifier, and the temporary intermediate node is used to save the synchronization data for which data synchronization has not been completed.
The method according to any one of claims 1 to 10, wherein the method further comprises:

When the first data is synchronized, the first device receives a first hash value sent by the second device, where the first hash value is the content modified by the second device according to the first media asset Obtained by the performed hash operation, the first synchronization message includes the first hash value;

The first device performs hash calculation according to the content of the first change list to obtain a second hash value;

When the first device determines that the first hash value is equal to the second hash value, the first device determines that the current data synchronization is successful.
A method for data synchronization in a mobile distributed system, comprising:

The second device receives a first query request sent by the first device, where the first query request is used to query whether there is a media asset change on the second device;

The second device determines that the first media asset is changed according to the first query request, and sends a first synchronization message to the first device, where the first synchronization message carries the first media of the second device Asset change content, where the first media asset change content includes the changed first media asset and an action corresponding to the first media asset change.
The method according to claim 12, wherein before the second device receives the first query request sent by the first device, the method further comprises:

The first media asset on the second device is changed, and the second device adds a first change list;

The method also includes:

The second device sends a third query request to the first device, where the third query request is used to query whether there is a media asset change on the first device;

The second device receives a first feedback message sent by the first device, where the first feedback message is that the first device receives the third query request and determines that there is no media on the first device Sent to the second device after the asset is changed, the first feedback message is used to identify that no media asset change has occurred on the first device;

The second device generates a first synchronization record according to the first feedback message and the first synchronization message, wherein the first synchronization record includes a first synchronization node, the first change list and a first device list, the first synchronization node is used to record the information of the first data synchronization, the first change list is used to record the media assets changed in the first data synchronization and the actions corresponding to the changes of the media assets, so The first device list is used to record the first data synchronization device.
The method of claim 13, wherein:

The first synchronization node includes one or more of a first synchronization node identifier, a first synchronization timestamp, a first parent synchronization node identifier, a first synchronization change content, and a first synchronization device, wherein the first synchronization The node ID is used to identify the first data synchronization;

The first change list includes: a first change list ID and the content of the media asset change of the second device;

The first device list includes: a first device list ID and a device ID of the first device.
The method according to claim 14, wherein the first synchronization change content includes media asset change content of the second device, and the first synchronization device includes a device ID of the first device; or,

The first synchronization change content includes an index of a first change list, the first synchronization device includes an index of a first device list, and the index of the change list is used to find the first change list, the device The index of the list is used to look up the first device list; or,

The first synchronization change content includes an index of the second device's media asset change content, the first synchronization device includes an index related to the first device, and the second device's media asset change content index and the index related to the first device is used to search for information related to the first device.
The method according to any one of claims 12 to 15, wherein the second device determines, according to the first query request, that there is a change in the first media asset, comprising:

The second device determines that there is a first media asset change according to the first query request and the synchronization record on the second device; or,

The second device determines that the first media asset is changed according to the first query request and the change list on the second device.
The method according to any one of claims 12 to 16, wherein,

The first synchronization message includes a first hash value, and the first hash value is obtained by the second device performing a hash operation according to the changed content of the first media asset.
A device, the device is a first device, characterized in that it includes:

a transceiver unit, configured to send a first query request to the second device, where the first query request is used to query whether there is a media asset change on the second device;

The transceiver unit is further configured to receive a first synchronization message sent by the second device, where the first synchronization message is sent to the second device after receiving the first query request and judging that the first media asset has been changed. Sent by the first device, the first synchronization message carries the first media asset modification content of the second device, and the first media asset modification content includes the modified first media asset and the first media asset. Actions corresponding to media asset changes;

The processing unit is configured to generate a first synchronization record according to the first synchronization message, wherein the first synchronization record includes a first synchronization node, a first change list and a first device list, and the first synchronization node uses For recording the information of the first data synchronization, the first change list is used to record the first media asset changed in the first data synchronization and the action corresponding to the change of the first media asset, and the first device list A device for recording the first data synchronization.
The first device of claim 18, wherein:

The first synchronization node includes one or more of a first synchronization node identifier, a first synchronization timestamp, a first parent synchronization node identifier, a first synchronization change content, and a first synchronization device, wherein the first synchronization The node ID is used to identify the first data synchronization;

The first change list includes: a first change list ID and the first media asset change content of the second device;

The first device list includes: a first device list ID and a device ID of the second device.
The first device according to claim 19, wherein the first synchronization change content includes a first media asset change content of the second device, and the first synchronization device includes a device ID of the second device; or,

The first synchronization change content includes an index of a first change list, the first synchronization device includes an index of a first device list, and the index of the change list is used to find the first change list, the device The index of the list is used to look up the first device list; or,

The first synchronization change content includes an index of the first media asset change content, the first synchronization device includes an index related to the second device, and the index of the first media asset change content is used to find the index of the first media asset change content. The first media asset changes content, and the index related to the second device is used to search for information related to the second device.
The first device according to claim 18, wherein before the first device receives the first synchronization message sent by the second device, the media asset on the first device is changed, and the processing unit further uses At:

A second change list is added, and the second change list includes the second change list ID and the content of the media asset change on the first device.
The first device according to claim 21, wherein after the first device receives the first synchronization message sent by the second device, the processing unit is further configured to:

The first device generates a second synchronization record according to the first synchronization message, where the second synchronization record includes a second synchronization node, the second change list and a second device list;

The second synchronization node includes a second synchronization node ID, one or more of a second synchronization time stamp, a second parent synchronization node identifier, a second synchronization change content, and a second synchronization device, and the second synchronization node ID for identifying the second data synchronization;

In the second modification list, add the media asset modification content of the second device;

The device ID of the second device is added to the second device list.
The first device according to any one of claims 19 to 22, wherein,

The transceiver unit is also used for:

sending a second query request to the second device, where the second query request is used to query whether there is a media asset change on the second device;

Receive a second synchronization message sent by the second device, where the second synchronization message is sent to the first device after the second device receives the second query request and determines that the second media asset is changed The second synchronization message carries the second media asset change content of the second device, and the second media asset change content includes the changed second media asset and the action corresponding to the second media asset change ;

The processing unit is further configured to: generate a third synchronization record according to the second synchronization message, where the third synchronization record includes a third synchronization node, a third change list and a third device list,

The third synchronization node includes one or more of a third synchronization node ID, a third synchronization timestamp, a third parent synchronization node identifier, a third synchronization change content, and a third synchronization device, wherein the The third synchronization node ID is used to identify three data synchronizations;

The third change list includes a third change list ID, and the second media asset of the second device changes the content;

The third device list includes a third device list ID and a device ID of the second device;

The processing unit is further configured to: remove the device ID of the second device in the first device list ID.
The first device according to claim 23, wherein the device ID in the first device list is empty, and the processing unit deletes the first device list.
The first device according to claim 24, wherein, when the first synchronization node is a root (Root) node, the root node and the first change list are deleted, which are the same as the root node. The neighbor sync node becomes the new root node.
The first device according to any one of claims 23 to 25, wherein the third synchronization node is a top (Top) node, and a node between the top node and the root node is an intermediate ( middle) node.
The first device according to any one of claims 18 to 26, wherein when a data synchronization process between the first device and the second device is terminated abnormally, the processing unit is further configured to:

Create a temporary intermediate node, where the temporary intermediate node includes a temporary state identifier, and the temporary intermediate node is used to save synchronization data for which data synchronization has not been completed.
The first device according to any one of claims 18 to 27, characterized in that,

When the first data is synchronized, the transceiver unit is further configured to receive a first hash value sent by the second device, where the first hash value is the second device according to the first media asset The first synchronization message includes the first hash value obtained from the hash operation performed on the changed content;

The processing unit is further configured to perform hash calculation according to the content of the first change list to obtain a second hash value;

When the processing unit determines that the first hash value is equal to the second hash value, the processing unit determines that the current data synchronization is successful.
A device, the device is a second device, characterized in that it includes:

a transceiver unit, configured to receive a first query request sent by a first device, where the first query request is used to query whether there is a media asset change on the second device;

a processing unit, configured to determine, according to the first query request, that there is a first media asset change, and send a first synchronization message to the first device, where the first synchronization message carries the first media of the second device Asset change content, where the first media asset change content includes the changed first media asset and an action corresponding to the first media asset change.
The second device of claim 29, wherein:

The first media asset on the second device is changed, and the processing unit is further configured to add a first change list;

The transceiver unit is also used for:

sending a third query request to the first device, where the third query request is used to query whether there is a media asset change on the first device;

Receive a first feedback message sent by the first device, where the first feedback message is sent to the sent by the second device, the first feedback message is used to identify that no media asset change has occurred on the first device;

The processing unit is also used to:

A first synchronization record is generated according to the first feedback message and the first synchronization message, wherein the first synchronization record includes a first synchronization node, the first change list and a first device list, the first synchronization record A synchronization node is used to record the information of the first data synchronization, the first change list is used to record the media assets changed in the first data synchronization and the actions corresponding to the changes of the media assets, the first device list A device for recording the first data synchronization.
The second device of claim 30, wherein:

The first synchronization node includes one or more of a first synchronization node identifier, a first synchronization timestamp, a first parent synchronization node identifier, a first synchronization change content, and a first synchronization device, wherein the first synchronization The node ID is used to identify the first data synchronization;

The first change list includes: a first change list ID and the content of the media asset change of the second device;

The first device list includes: a first device list ID and a device ID of the first device.
The second device according to claim 31, wherein the first synchronization change content includes media asset change content of the second device, and the first synchronization device includes a device ID of the first device; or,

The first synchronization change content includes an index of a first change list, the first synchronization device includes an index of a first device list, and the index of the change list is used to find the first change list, the device The index of the list is used to look up the first device list; or,

The first synchronization change content includes an index of the second device's media asset change content, the first synchronization device includes an index related to the first device, and the second device's media asset change content index The index related to the first device is used to search for the content of the media asset modification of the first device, and the index related to the first device is used to search the information related to the first device.
The second device according to any one of claims 30 to 32, wherein the processing unit is specifically configured to:

According to the first query request and the synchronization record on the second device, it is determined that the first media asset has changed; or,

According to the first query request and the change list on the second device, it is determined that the first media asset is changed.
The second device according to any one of claims 30 to 32, wherein,

The first synchronization message includes a first hash value, and the first hash value is obtained by the processing unit performing a hash operation according to the content of the first media asset change.
A distributed system for data synchronization, characterized in that the distributed system includes the first device according to any one of claims 18 to 28 and the first device according to any one of claims 29 to 34 Second equipment.
A communication device comprising a processor connected to a memory for storing a computer program, the processor for executing the computer program stored in the memory to cause the device to perform as claimed in the claims The method of any one of 1 to 11, or the method of any one of 12 to 17.
A computer-readable storage medium, characterized in that the computer-readable storage medium stores a computer program, when the computer program is executed, the method according to any one of claims 1 to 11 is implemented, or The method of any one of 12 to 17.
A chip, characterized in that it includes a processor and an interface;

The processor is adapted to read instructions to perform the method of any one of claims 1 to 11, or the method of any one of 12 to 17.