WO2022089384A1

WO2022089384A1 - Data synchronization method and device

Info

Publication number: WO2022089384A1
Application number: PCT/CN2021/126219
Authority: WO
Inventors: 钱夏欢; 蒋钟寅; 李丽; 王洋; 凌波
Original assignee: 华为技术有限公司
Priority date: 2020-10-31
Filing date: 2021-10-25
Publication date: 2022-05-05
Also published as: CN114531449A

Abstract

Provided by the present application are a data synchronization method and device, which can solve the problems of low efficiency and high device power consumption of existing data synchronization technology, improve data synchronization efficiency, and reduce device power consumption, and can be applied to a wireless communication system, such as a low-power Bluetooth communication system, a wireless fidelity system, etc. The method comprises: a first data synchronizer receives synchronization data from a second device, and sends the synchronization data to a first processor. A data synchronization function of a first device may be achieved by the first data synchronizer, so that even if the first processor is in a dormant state, the first data synchronizer may also receive the synchronization data from the second device in real time. Similarly, even if a second processor is in a dormant state, a second data synchronizer may also send the synchronization data to the first device. That is, the data synchronization function may be achieved by the data synchronizers, and the processors are not required to participate, so that the power consumption of the first device and the second device may be reduced, and the data synchronization efficiency may be improved.

Description

Data synchronization method and device

This application claims the priority of the Chinese patent application with the application number 202011198816.1 and the application name "Data Synchronization Method and Apparatus" filed with the State Intellectual Property Office on October 31, 2020, the entire contents of which are incorporated into this application by reference.

technical field

The present application relates to the field of data synchronization, and in particular, to a data synchronization method and device.

Background technique

Currently, data synchronization can be performed between devices to share data. For example, the mobile phone synchronizes the latest express information to the TV, or the TV synchronizes the latest episode viewing records to the mobile phone.

However, when synchronizing data between devices, an application processor (application processor, AP) of the device must be in a working state (ie, a wake-up state) to achieve data synchronization. This will cause the device to spend a lot of time frequently waking up the AP and establishing a communication connection between the devices when synchronizing data. Therefore, the existing data synchronization technology has the problems of low efficiency and high device power consumption.

SUMMARY OF THE INVENTION

The embodiments of the present application provide a data synchronization method and apparatus, which can solve the problems of low efficiency and high device power consumption of the existing data synchronization technology, thereby improving data synchronization efficiency and reducing device power consumption.

To achieve the above object, the application adopts the following technical solutions:

In a first aspect, a data synchronization method is provided. The method is applied to the first device. Wherein, the first device includes a first data synchronizer and a first processor. The method includes: the first data synchronizer receives synchronization data from the second device, and sends the synchronization data to the first processor.

Based on the data synchronization method described in the first aspect and the following second aspect, the data synchronization function of the first device can be completed by the first data synchronizer, and the data synchronization function of the second device can be completed by the second data synchronizer , that is, the data synchronization function can be completed by the data synchronizer without the involvement of the processor. In this way, even if the first processor is in a sleep state, the first data synchronizer can receive synchronization data from the second data synchronizer in real time, and even if the second processor is in a sleep state, the second data synchronizer can also Send synchronization data to the first device. Furthermore, the present application can reduce the power consumption of the first device and the second device, and improve the data synchronization efficiency.

In a possible design solution, the above-mentioned first data synchronizer receives the synchronization data from the second device, and sends the synchronization data to the first processor, which may include: when the first processor is in a dormant state, the first data synchronization is performed. The processor receives the synchronization data from the second device, and sends the synchronization data to the first processor when the first processor is in a working state. During the process of receiving the synchronization data sent by the second device, the first device receives the synchronization data from the second device by the first data synchronizer when the first processor is in a sleep state. In this way, the power consumption of the device can be further reduced, the use time of the device can be prolonged, and the user experience can be improved.

Optionally, the above-mentioned first data synchronizer sending synchronization data to the first processor may include: if the first data synchronizer detects that the first processor is in a working state, sending the first data synchronizer to the first processor Synchronous Data. In this way, when the first processor wakes up, the first data synchronizer can send the synchronization data to the first processor in time, thereby reducing the data synchronization time and further improving the data synchronization efficiency.

Or, optionally, the above-mentioned first data synchronizer sending synchronization data to the first processor may include: the first data synchronizer receiving a synchronization instruction from the first processor, and sending synchronization instructions to the first processor according to the synchronization instruction data. The synchronization instruction is used to obtain synchronization data from the second device. In this way, the first processor can send a synchronization instruction to the first data synchronizer, and then actively acquire the synchronization data from the second device from the first data synchronizer, thereby improving the reliability of data synchronization.

In another possible design solution, before the first data synchronizer sends the synchronization data to the first processor, the method described in the first aspect may further include: if the first data synchronizer detects that the first processor is in In the sleep state, the first data synchronizer actively wakes up the first processor. In this way, when the first processor sleeps, the first data synchronizer can actively wake up the first processor and send synchronization data to the first processor in a fast and timely manner, thereby further improving data synchronization efficiency.

In another possible design solution, the method described in the first aspect may further include: the first data synchronizer receives the subscription parameters from the first processor, and sends the subscription parameters to the second device. The subscription parameter is used by the first device to obtain synchronization data from the second device. In this way, the second device can provide synchronization data according to the requirements of the first device, that is, the first device can customize the synchronization data to reduce unnecessary data synchronization operations, thereby further improving data synchronization efficiency.

In another possible design solution, the method described in the first aspect may further include: the first processor outputs synchronization data, so that the first device can remind the user to check the synchronization data output by the first processor, so that the user can check the synchronization data according to the synchronization data. The data determines the next action to improve the user experience. For example, the first processor may control the display of the first device to display the synchronization data, or control the speaker of the first device to play the synchronization data.

In a second aspect, a data synchronization method is provided. The method is applied to the second device. Wherein, the second device includes a second data synchronizer and a second processor. The method includes: the second data synchronizer receives synchronization data from the second processor, and sends the synchronization data to the first device.

In a possible design solution, the above-mentioned second data synchronizer sending synchronization data to the first device may include: when the second processor is in a sleep state, the second data synchronizer sending synchronization data to the first device. In the process of sending the synchronization data to the first device by the second device, the second processor can enter the sleep state after sending the synchronization data to the second data synchronizer, and when the second processor is in the sleep state, the second processor is in the sleep state. The second data synchronizer sends synchronization data to the first device. In this way, the power consumption of the device can be further reduced, the use time of the device can be prolonged, and the user experience can be improved.

Optionally, the above-mentioned second data synchronizer sending synchronization data to the first device may include: the second data synchronizer sending synchronization data to the first device according to a subscription parameter. The subscription parameter is used by the first device to obtain synchronization data from the second device.

Further, before the second data synchronizer sends the synchronization data to the first device according to the subscription parameters, the method of the second aspect may further include: the second data synchronizer receives the subscription parameters from the first device.

Further, after the second data synchronizer receives the subscription parameters from the first device, the method described in the second aspect may further include: the second data synchronizer sends the subscription parameters to the second processor.

Further, before the second data synchronizer sends the subscription parameters to the second processor, the method described in the second aspect may further include: if the second data synchronizer stores synchronization data, the second data synchronizer sends the subscription parameters to the second processor according to the subscription parameters. The first device sends synchronization data. In this way, the second data synchronizer can send the synchronization data to the first device in time, thereby reducing the data synchronization time and further improving the data synchronization efficiency.

Further, before the second data synchronizer sends the subscription parameters to the second processor, the method described in the second aspect may further include one of the following: if the second processor is in a dormant state, the second data synchronizer wakes up the first two processors; or, if the second processor is in a dormant state, the second data synchronizer waits for the second processor to wake up. In this way, if the second data synchronizer actively wakes up the second processor, the second data synchronizer can send the subscription parameters to the second processor in time, so that the second device can timely feed back the synchronization data to the first device, and further Improve data synchronization efficiency. If the second data synchronizer waits for the second processor to wake up, the wake-up frequency of the second processor can be reduced, thereby further reducing the power consumption of the device.

In another possible design solution, the method described in the second aspect may further include: the second processor receives the subscription parameters from the second data synchronizer, obtains the synchronization data generated by the application according to the subscription parameters, and sends The second data synchronizer sends synchronization data. In this way, the second device can send the synchronization data generated by the application to the first device in time, so as to further improve the data synchronization efficiency.

In addition, for the technical effect of the data synchronization method described in the second aspect, reference may be made to the technical effect of the data synchronization method described in the first aspect, which will not be repeated here.

In a third aspect, a communication device is provided. The apparatus includes a first data synchronizer and a first processor. The first data synchronizer is configured to receive synchronization data from the second device and send the synchronization data to the first processor.

In a possible design solution, the first data synchronizer is configured to receive synchronization data from the second device when the first processor is in a sleep state, and send synchronization data to the first processor when the first processor is in a working state. Synchronous Data.

Optionally, the first data synchronizer is configured to send synchronization data to the first processor if it is detected that the first processor is in a working state.

Or, optionally, the first data synchronizer is configured to receive a synchronization instruction from the first processor, and send synchronization data to the first processor according to the synchronization instruction. The synchronization instruction is used to obtain synchronization data from the second device.

In another possible design solution, the first data synchronizer is further configured to actively wake up the first processor if it is detected that the first processor is in a sleep state before sending the synchronization data to the first processor.

In another possible design solution, the first data synchronizer is further configured to receive subscription parameters from the first processor and send the subscription parameters to the second device. Wherein, the subscription parameter is used for the communication apparatus described in the third aspect to acquire synchronization data from the second device.

In another possible design solution, the first processor is further configured to output synchronization data.

Optionally, the above-mentioned first data synchronizer may include a receiver and a transmitter. Wherein, the first data synchronizer is used to implement the sending function and the receiving function of the communication device described in the third aspect.

Optionally, the communication apparatus described in the third aspect may further include a memory, where the memory stores programs or instructions. When the first data synchronizer and the first processor execute the program or the instruction, the communication apparatus described in the third aspect can execute the data synchronization method described in the first aspect.

It should be noted that the communication device described in the third aspect may be terminal equipment or network equipment, or may be a chip (system) or other components or components that can be set in the terminal equipment or network equipment, or may include terminal equipment or a device of a network device, which is not limited in this application.

In addition, for the technical effect of the communication device described in the third aspect, reference may be made to the technical effect of the data synchronization method described in the first aspect, and details are not described herein again.

In a fourth aspect, a communication device is provided. The apparatus includes a second data synchronizer and a second processor. The second data synchronizer is configured to receive synchronization data from the second processor and send the synchronization data to the first device.

In a possible design solution, the second data synchronizer is configured to send synchronization data to the first device when the second processor is in a sleep state.

Optionally, the second data synchronizer is configured to send synchronization data to the first device according to the subscription parameter. Wherein, the subscription parameter is used by the first device to obtain synchronization data from the communication apparatus described in the fourth aspect.

Further, the second data synchronizer is further configured to receive the subscription parameters from the first device before sending the synchronization data to the first device according to the subscription parameters.

Further, the second data synchronizer is further configured to send the subscription parameters to the second processor after receiving the subscription parameters from the first device.

Further, the second data synchronizer is further configured to send the synchronization data to the first device according to the subscription parameters if synchronization data is stored before sending the subscription parameters to the second processor.

Further, the second data synchronizer is further configured to wake up the second processor if the second processor is in a dormant state before sending the subscription parameters to the second processor; or, the second data synchronizer is further configured to Before sending the subscription parameters to the second processor, if the second processor is in a dormant state, wait for the second processor to wake up.

In another possible design solution, the second processor is further configured to receive subscription parameters from the second data synchronizer, obtain synchronization data generated by the application according to the subscription parameters, and send synchronization data to the second data synchronizer data.

Optionally, the above-mentioned second data synchronizer may also be referred to as a transceiver. The transceiver may include a receiver and a transmitter. Wherein, the transceiver is used to implement the sending function and the receiving function of the communication device described in the fourth aspect.

Optionally, the communication apparatus described in the fourth aspect may further include a memory, where the memory stores programs or instructions. When the second data synchronizer and the second processor execute the program or instruction, the communication apparatus described in the fourth aspect can execute the data synchronization method described in the second aspect.

It should be noted that the communication device described in the fourth aspect may be terminal equipment or network equipment, or may be a chip (system) or other components or components that can be set in the terminal equipment or network equipment, or may include terminal equipment or a device of a network device, which is not limited in this application.

In addition, for the technical effect of the communication device described in the fourth aspect, reference may be made to the technical effect of the data synchronization method described in the second aspect, which will not be repeated here.

In a fifth aspect, a communication device is provided. The communication apparatus is configured to execute the data synchronization method described in any one of the implementation manners of the first aspect to the second aspect.

In this application, the communication device described in the fifth aspect may be the first device described in the first aspect or the second device described in the second aspect, or may be provided in the first device or the second device a chip (system) or other component or assembly, or an apparatus containing the first device or the second device.

It should be understood that the communication device described in the fifth aspect includes a corresponding module, unit, or means for implementing the data synchronization method described in any one of the first aspect and the second aspect. The module, unit, or means It can be realized by hardware, software, or by executing corresponding software by hardware. The hardware or software includes one or more modules or units for performing the functions involved in the above data synchronization method.

In addition, for the technical effect of the communication apparatus described in the fifth aspect, reference may be made to the technical effect of the data synchronization method described in any one of the first aspect to the second aspect, which will not be repeated here.

In a sixth aspect, a communication device is provided. The communication device includes: a processor, where the processor is configured to execute the data synchronization method described in any one of the possible implementation manners of the first aspect to the second aspect.

In a possible design solution, the communication apparatus described in the sixth aspect may further include a transceiver. The transceiver may be a transceiver circuit or an interface circuit. The transceiver can be used for the communication device described in the sixth aspect to communicate with other communication devices.

In a possible design solution, the communication apparatus described in the sixth aspect may further include a memory. The memory can be integrated with the processor, or it can be provided separately. The memory may be used to store the computer program and/or data involved in the data synchronization method described in any one of the first aspect to the second aspect.

In this application, the communication device described in the sixth aspect may be the first device in the first aspect or the second device in the second aspect, or a chip (system) that may be provided in the first device or the second device ) or other parts or assemblies, or apparatus comprising the first device or the second device.

In addition, for the technical effect of the communication apparatus described in the sixth aspect, reference may be made to the technical effect of the data synchronization method described in any one of the implementation manners of the first aspect to the second aspect, and details are not described herein again.

In a seventh aspect, a communication device is provided. The communication apparatus includes: a processor, which is coupled to the memory, and the processor is configured to execute a computer program stored in the memory, so that the communication apparatus executes any one of the possible implementations of the first aspect to the second aspect. data synchronization method.

In a possible design solution, the communication device according to the seventh aspect may further include a transceiver. The transceiver may be a transceiver circuit or an interface circuit. The transceiver can be used for the communication device described in the seventh aspect to communicate with other communication devices.

In this application, the communication apparatus described in the seventh aspect may be the first device in the first aspect or the second device in the second aspect, or may be a chip (system) provided in the first device or the second device ) or other parts or assemblies, or apparatus comprising the first device or the second device.

In addition, for the technical effect of the communication device described in the seventh aspect, reference may be made to the technical effect of the data synchronization method described in any one of the implementation manners of the first aspect to the second aspect, which will not be repeated here.

In an eighth aspect, a communication device is provided, comprising: a processor and a memory; the memory is used for storing a computer program, when the processor executes the computer program, so that the communication device executes the first to second aspects The data synchronization method described in any implementation manner of .

In a possible design solution, the communication apparatus described in the eighth aspect may further include a transceiver. The transceiver may be a transceiver circuit or an interface circuit. The transceiver can be used for the communication device described in the eighth aspect to communicate with other communication devices.

In this application, the communication apparatus described in the eighth aspect may be the first device in the first aspect or the second device in the second aspect, or a chip (system) that may be provided in the first device or the second device ) or other parts or assemblies, or apparatus comprising the first device or the second device.

In addition, for the technical effect of the communication device described in the eighth aspect, reference may be made to the technical effect of the data synchronization method described in any one of the implementation manners of the first aspect to the second aspect, which will not be repeated here.

In a ninth aspect, a communication device is provided, comprising: a processor; the processor is configured to be coupled to a memory, and after reading a computer program in the memory, execute the first to second aspects according to the computer program Any one of the data synchronization methods described in the implementation manner.

In a possible design solution, the communication device according to the ninth aspect may further include a transceiver. The transceiver may be a transceiver circuit or an interface circuit. The transceiver can be used for the communication device described in the ninth aspect to communicate with other communication devices.

In this application, the communication device described in the ninth aspect may be the first device in the first aspect or the second device in the second aspect, or a chip (system) that may be provided in the first device or the second device ) or other parts or assemblies, or apparatus comprising the first device or the second device.

In addition, for the technical effect of the communication apparatus described in the ninth aspect, reference may be made to the technical effect of the data synchronization method described in any one of the implementation manners of the first aspect to the second aspect, which will not be repeated here.

A tenth aspect provides a processor. The processor is configured to execute the data synchronization method described in any possible implementation manner of the first aspect to the second aspect.

In an eleventh aspect, a wireless communication system is provided. The wireless communication system includes the above-mentioned first device and second device.

A twelfth aspect provides a computer-readable storage medium, comprising: a computer program or an instruction; when the computer program or instruction is run on a computer, the computer is made to execute any one of the possible possibilities of the first aspect to the second aspect. The data synchronization method described in the implementation mode is implemented.

A thirteenth aspect provides a computer program product, comprising a computer program or instructions, when the computer program or instructions are run on a computer, the computer is made to execute any one of the possible implementations of the first aspect to the second aspect. The data synchronization method described above.

Description of drawings

1 is a schematic diagram of an application scenario and a flowchart of an existing data synchronization technology;

FIG. 2 is a schematic structural diagram of a wireless communication system according to an embodiment of the present application;

3 is a block diagram of a device system architecture provided by an embodiment of the present application;

FIG. 4 is a schematic diagram of a service framework of a device provided by an embodiment of the present application;

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

6 is a second schematic flowchart of a data synchronization method provided by an embodiment of the present application;

FIG. 7 is a schematic structural diagram 1 of a communication device provided by an embodiment of the present application;

FIG. 8 is a second schematic structural diagram of a communication device according to an embodiment of the present application;

FIG. 9 is a third schematic structural diagram of a communication apparatus according to an embodiment of the present application.

Detailed ways

First, the technical terms involved in the embodiments of the present application are introduced.

The Sensor Hub (SensorHub) is a microcontroller unit (MCU) that can control the sensors of the device in real time and process data from various sensors when the CPU of the device is in sleep state.

Bluetooth low energy (BLE) is a low-cost, short-range, interoperable wireless communication technology.

The application processor can process data update monitoring, data distribution processing and data presentation of the subscription service of the device.

In the process of implementing the embodiments of the present application, the inventors of the present application found that:

Taking the application scenario shown in FIG. 1 as an example, the mobile phone includes a first AP and a communication module, and the TV includes a second AP and a communication module. The first AP includes programs such as express programs, schedule programs, first content services, first distribution services, and first display modules, and the second AP includes video programs, second content services, second distribution services, and second display modules. and so on.

In the application scenario shown in Figure 1, the TV can synchronize the latest episode viewing records to the mobile phone (refer to steps 1 to 7 in Figure 1), or the mobile phone can also synchronize the latest express information to the TV (refer to Figure 1). Step 1-Step ⑦) in Step 1, Step 1-Step ⑦ can refer to Step 1-Step 7, and only step 1-Step 7 in the figure will be introduced in detail below.

Step 1, the second distribution service program sends the mobile phone the information that the video service can be provided (the information indicates that the TV can send the synchronization data generated by the video program) to the mobile phone through the communication module.

Step 2, the first distribution service program receives the video service information available from the TV, and sends the subscription video service information to the TV.

Step 3, after the TV receives the subscription video service information from the mobile phone, if the video program generates new video data (such as the video viewing progress, the episodes collected by the user, etc.), then these data are sent to the second as synchronous data. content service program.

Step 4: After receiving the synchronization data from the video program, the second content service program sends the synchronization data to the second distribution service program.

Step 5, the second distribution service program sends synchronization data to the mobile phone through the communication module.

Step 6, the first distribution service program receives the synchronization data from the TV.

Step 7, the first distribution service program sends the synchronization data to the first display module, so that the first display module displays the synchronization data.

It should be understood that in step 6, the mobile phone must be in a working state (ie, a wake-up state, for example, the user uses the mobile phone to wake up the first AP), so that the first distribution service program can receive the synchronization data from the TV to realize data synchronization. That is to say, when synchronizing data between the mobile phone and the TV, the AP of the mobile phone and the TV must be in a working state (ie, a wake-up state) to achieve data synchronization.

It can be further understood that the existing data synchronization technology has poor real-time performance, and usually requires the user to use the device and wake up the device before the device can perform data synchronization. Moreover, after the device wakes up, the communication connection between the device and the device needs to be re-established to transmit data, so the transmission speed is slow. Also, if the device frequently synchronizes data with the device, the AP will be woken up frequently, and the device consumes a lot of power.

In order to solve the problems of low data synchronization efficiency and high device power consumption in the existing data synchronization technology, the embodiments of the present application provide a data synchronization method and device to improve data synchronization efficiency and reduce device power consumption. It should be noted that the various defects existing in the technical solutions in the above-mentioned prior art are the results obtained by the inventor after careful practical research. Therefore, the discovery process of the above-mentioned problems and the solutions to the above-mentioned problems proposed in the following embodiments of the present application should be contributions made by the inventor to the present application in the process of realizing the present application.

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

The technical solutions of the embodiments of the present application can be applied to various wireless communication systems, such as low-power Bluetooth communication systems, wireless fidelity (WiFi) systems, and 4th generation (4G) mobile communication systems, such as long-term Evolution (long term evolution, LTE) systems, worldwide interoperability for microwave access (WiMAX) communication systems, fifth generation (5th generation, 5G) mobile communication systems, such as new radio (new radio, NR) systems , and future communication systems, such as the 6th generation (6G) mobile communication system, vehicle-to-everything (V2X) communication system, device-todevie (D2D) communication system, Internet of Vehicles communication system, etc.

This application will present various aspects, embodiments, or features around a system that may include a plurality of devices, components, modules, and the like. It is to be understood and appreciated that the various systems may include additional devices, components, modules, etc., and/or may not include all of the devices, components, modules, etc. discussed in connection with the figures. In addition, combinations of these schemes can also be used.

In addition, in the embodiments of the present application, words such as "exemplarily" and "for example" are used to represent examples, illustrations or illustrations. Any embodiment or design described in this application as "exemplary" should not be construed as preferred or advantageous over other embodiments or designs. Rather, the use of the word example is intended to present a concept in a concrete way.

In the embodiments of the present application, "information", "signal", "message", "channel", and "signaling" may sometimes be used interchangeably. It should be noted that, When not emphasizing their differences, their intended meanings are the same. "of", "corresponding, relevant" and "corresponding" can sometimes be used interchangeably. It should be pointed out that when the difference is not emphasized, the meanings they intend to express are the same.

In the embodiments of the present application, sometimes _a subscript such as W1 may be mistakenly written in a non-subscript form such as W1. When the difference is not emphasized, the meaning to be expressed is the same.

The system architecture and business scenarios described in the embodiments of the present application are for the purpose of illustrating the technical solutions of the embodiments of the present application more clearly, and do not constitute a limitation on the technical solutions provided by the embodiments of the present application. The evolution of the architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.

To facilitate understanding of the embodiments of the present application, firstly, a wireless communication system applicable to the embodiments of the present application is described in detail by taking the wireless communication system shown in FIG. 2 as an example. Exemplarily, FIG. 2 is a schematic structural diagram of a wireless communication system to which the data synchronization method provided by the embodiment of the present application is applied.

As shown in FIG. 2 , the wireless communication system may include a first device and a second device, and a communication connection exists between the first device and the second device.

Wherein, both the first device and the second device may be a terminal with a wireless transceiver function or a chip or a chip system that may be provided in the terminal. In practical applications, the first device and the second device may be: a mobile phone (mobile phone), a tablet computer (Pad), a computer with a wireless transceiver function, a virtual reality (virtual reality, VR) terminal device, an augmented reality (augmented reality) , AR) terminal equipment, wireless terminals in industrial control, wireless terminals in self-driving, wireless terminals in remote medical, wireless terminals in smart grid , wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, in-vehicle terminals, roadside units (RSUs) with terminal functions )Wait. Furthermore, the above-mentioned first device and second device may also be referred to as user equipment, access terminal, subscriber unit, subscriber station, mobile station, mobile station, remote station, remote terminal, mobile equipment, user terminal, terminal, wireless communication device, or user agent.

Since both the above-mentioned first device and the second device may be a terminal with a wireless transceiver function or a chip or a chip system that can be provided in the terminal, the above-mentioned first processor and the second processor may be: ARM (advanced) RISC machines) processors, X86 processors, or application processors, etc. For example, when the first device is a mobile phone and the second device is a TV, both the above-mentioned first processor and second processor may be APs.

The above-mentioned first data synchronizer and second data synchronizer may be: MCU, general-purpose processor, digital signal processor (digital signal processor, DSP), application specific integrated circuit (application specific integrated circuit, ASIC), ready-made programmable gate Field programmable gate array (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, coprocessors, etc. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. For example, when the first device is a mobile phone and the second device is a TV, both the above-mentioned first data synchronizer and second data synchronizer may be SensorHub.

Further, on the basis of the wireless communication system shown in FIG. 2 , when the above-mentioned first processor is an AP and the first data synchronizer is a SensorHub, for the system architecture of the first device, the embodiment of the present application also provides For a feasible implementation manner, please refer to FIG. 3 , which is a block diagram of a device system architecture provided by an embodiment of the present application. The device system architecture may include one or more of the following modules: AP, SensorHub, or bluetooth chip (BT chip).

The AP may include one or more of the following layers: an application layer (applications, APPs), an application framework layer (application framework), a hardware abstraction layer (hardware abstraction layer, HAL), or a kernel layer (kernel).

The SensorHub may include one or more of the following modules: a subscription service, a Bluetooth application (bluetooth application, BT APP), or a Bluetooth driver (bluetooth driver, BT driver).

The Bluetooth chip may include one or more of the following modules: a translation switch module or a scan filter module. The specific implementation of the conversion module and the scanning filter module can refer to the existing Bluetooth technology, which will not be repeated here.

Data communication can be performed between the AP and the Bluetooth chip through a universal asynchronous receiver transmitter (UART). Data communication between the SensorHub and the Bluetooth chip can be performed through a built-in integrated circuit (inter integrated circuit, I2C), or data communication can be performed through an improved inter integrated circuit (I3C).

Specifically, the application layer may include one or more of the following programs: bus service, smart life, express delivery, or video, etc.

The application framework layer may include one or more of the following framework modules: a Bluetooth framework (bluetooth framework, BT FW), a WiFi framework (WiFi framework, WiFi FW), or a sensor framework (sensor framework, Sensor FW), etc.

The hardware abstraction layer may include one or more of the following hardware abstraction modules: bluetooth hardware abstraction layer (BT HAL), WiFi hardware abstraction layer (WiFi HAL), or sensor hardware abstraction layer (sensor hardware abstraction layer) , Sensor HAL) and so on.

The kernel layer may include one or more of the following driver modules: a Bluetooth driver (bluetooth driver, BT driver), a WiFi driver (WiFi driver), or a sensor driver (Sensor driver).

In the embodiment of the present application, the program in the AP can generate various synchronous data. For example, the express program can generate synchronous data including the express delivery time, the express delivery address, the express delivery person, etc. The video program can generate the synchronous data including the name of the episode , episode progress, video synchronization data, etc. The bus service can obtain synchronization data generated by programs in the AP.

The bus service can also communicate data with SensorHub. For example, when the bus service needs to send synchronous data to SensorHub, the bus service can send the synchronous data to SensorHub by calling Sensor Driver, Sensor HAL, and Sensor FW in sequence. Or, for example, when SensorHub needs to send synchronous data to the bus service, SensorHub can sequentially call Sensor Driver, Sensor HAL, and Sensor FW to send the synchronous data to the bus service, thereby realizing the purpose of data communication between the bus service and SensorHub.

After the above SensorHub receives the data from the AP, it can send the data to other devices. For example, when SensorHub receives synchronous data from AP, SensorHub can control the Bluetooth chip to perform BLE scan and BLE broadcast to discover the second device. After discovering the second device, the first device may establish a communication connection with the second device (the communication connection may include: WiFi connection, Bluetooth connection, etc.), and then send the synchronization data to the second device. In addition, the aforementioned SensorHub can also receive data from other devices and send the data to the AP. For example, when SensorHub receives synchronization data from the second device, SensorHub can send the synchronization data to the AP. That is to say, SensorHub can communicate with other devices by controlling the Bluetooth chip.

Based on the functional description of the above bus service and SensorHub, it can be understood that in order to realize the function of sending the synchronization data to other devices, the bus service can send the synchronization data to SensorHub after obtaining the synchronization data generated by the program in the AP, and then This sync data is sent by SensorHub to other devices. Similarly, in order to realize the function of receiving synchronization data from other devices, SensorHub can receive synchronization data from other devices, and then forward it to the AP.

Optionally, when SensorHub receives data from the AP, the above-mentioned subscription service can save the data. When SensorHub receives data from other devices, the aforementioned subscription services can also save that data.

In some possible embodiments, the subscription service may also store the following subscription parameters. For the subscription parameter, reference may be made to the explanation of S402-3 in the following method embodiments, which will not be repeated here.

It should be noted that, the device system architecture provided by the above embodiments may be the device system architecture of the first device in the wireless communication system shown in FIG. 2, or the device system architecture of the second device, which is not limited in the embodiments of the present application .

Optionally, based on the device system architecture shown in FIG. 3 , an embodiment of the present application further provides a schematic diagram of a service framework of a device, please refer to FIG. 4 . The service framework may include one or more of the following modules: AP, SensorHub, or Bluetooth chip.

The AP may include one or more of the following programs: express delivery, video, smart life, or bus service. Specifically, the smart life may include the following sub-modules: a user experience (UX) display module, a content service (CS) module, and a distribution service (DS) module.

The SensorHub may include one or more of the following modules: an application management module, a communication management module, or a Board Support Package (BSP) module. Specifically, the application management module may include the following submodules: a notification (Notify) module and a data update (data update) module.

In this embodiment of the present application, the content service module may be used to detect and acquire the synchronization data generated by the program in the AP, and may also be used to send the synchronization data to the distribution service module. After receiving the synchronization data from the content service module, the distribution service module can send the synchronization data to the bus service.

The communication management module can be encapsulated with a communication protocol, which can be used to control the Bluetooth chip to perform BLE scanning and BLE broadcast, thereby realizing sending data to or receiving data from other devices.

The data update module may be used to store synchronization data from other devices, and may be used to store synchronization data from APs. The notification module may be used to send synchronization data to other devices, and may be used to send received synchronization data to the AP. Exemplarily, when SensorHub receives synchronous data from the bus service, it can store the synchronous data in the data update module, and then the notification module calls the communication management module and the board-level support package module to send the synchronous data to the second device. . When the SensorHub receives the synchronization data from the second device, the synchronization data can also be stored in the data update module, and then the notification module calls the communication management module and the board-level support package module to send the synchronization data to the bus service.

Optionally, after receiving the data from SensorHub, the AP can also output the data. For example, the user experience display module may control the display of the first device to display the data (eg, a notification bar pops up on the display interface), or control the speaker of the first device to play the data.

It should be noted that the communication connection between the first device and the second device is not limited to a Bluetooth connection, but may also be a WiFi connection, a fourth-generation mobile communication connection, a fifth-generation mobile communication connection, etc. Not limited. In addition, the internal connection mode of the first device and the second device is not limited to UART, I2C, or I3C, which is not limited in this embodiment of the present application.

It should also be noted that, for the parts not mentioned in the service framework in this embodiment, reference may be made to the corresponding content in the above-mentioned embodiment of the device system architecture, which will not be repeated here.

It should also be noted that, in the following data synchronization methods provided by the embodiments of the present application, in some possible embodiments, the steps performed by the first device may be performed by the second device, and the steps performed by the second device may be performed by the first device , that is, the first device and the second device in this embodiment of the present application have the same status, and they can be executed interchangeably when executing the method provided by this embodiment. Exemplarily, the first device may receive synchronization data sent by the second device, and may also send synchronization data to the second device.

It should be noted that the solutions in the embodiments of the present application may also be applied to other communication systems, and the corresponding names may also be replaced by the names of corresponding functions in other communication systems.

It should be understood that FIG. 2 is only a simplified schematic diagram for easy understanding, and the wireless communication system may further include other network devices and/or other terminal devices, which are not shown in FIG. 2 .

The data synchronization method provided by the embodiment of the present application will be described in detail below with reference to FIG. 5 to FIG. 6 .

FIG. 5 is a schematic flowchart 1 of a data synchronization method provided by an embodiment of the present application. The method is applied to the first device and the second device. The first device includes a first data synchronizer and a first processor, and the second device includes a second data synchronizer and a second processor.

As shown in Figure 5, the method includes the following steps S501-S503:

S501, the second processor sends synchronization data to the second data synchronizer, and the second data synchronizer receives the synchronization data from the second processor.

The synchronization data may include one or more of the following: schedule data, itinerary data, express data, video data, music data, album data, or data to be read, and the like.

Illustratively, the schedule data may include schedule time, schedule content, and the like. Trip data can include trip content, trip time, trip recommendations, and more. The express data may include express delivery time, express delivery address, express delivery person, and the like. Video data may include episode names, episode progress, videos, and the like. The music data may include playing records of music applications, music, and the like. Album data may include album previews, recently captured images, and the like. The data to be read may include an introduction to be read, a link to be read, and the like.

In addition, the above-mentioned schedule data, itinerary data, express data, video data, music data, album data, or data to be read may also include a device identification code. For example, the device identification code may include one or more of the following: a media access control (media access control, MAC) address of the device, an internet protocol (internet protocol, IP) address, or a device name, and the like. It should be understood that setting the device identification code in the synchronization data can enable the first device to remind the user which device sent the synchronization data when the first device outputs the synchronization data, so that the user can determine the next operation, thereby improving user experience.

It should be noted that the embodiments of the present application do not specifically limit schedule data, itinerary data, express data, video data, music data, album data, or data to be read.

S502, the second data synchronizer sends synchronization data to the first data synchronizer, and the first data synchronizer receives the synchronization data from the second data synchronizer.

Specifically, after the second data synchronizer receives the synchronization data from the second processor, the second data synchronizer may send the synchronization data to the first data synchronizer immediately or later. Therefore, the second processor does not have to send synchronization data to the first device in real time. Furthermore, in the process of the second data synchronizer sending the synchronization data to the first data synchronizer, the second processor may be in a dormant state or in a working state. In this way, during the process of the second data synchronizer sending synchronization data to the first data synchronizer, the second processor may choose to enter the sleep state to reduce the power consumption of the device, or process other data to improve the operation efficiency of the device.

In order to achieve the purpose of reducing the power consumption of the device, optionally, in the above S502, the second data synchronizer sends the synchronization data to the first data synchronizer, which may include the following steps:

S502-1, when the second processor is in a sleep state, the second data synchronizer sends synchronization data to the first data synchronizer.

The hibernation state may be that the second processor is in a low power consumption running state, for example, the second processor is in a state of standby, hibernation, or sleep. That is to say, the above-mentioned hibernation state may include: standby, hibernation, or sleep.

After the second data synchronizer receives the synchronization data from the second processor, the second data synchronizer may first confirm whether the second processor is in a sleep state. When confirming that the second processor is in the sleep state, the second data synchronizer sends synchronization data to the first data synchronizer.

The manner in which the second data synchronizer confirms the state of the second processor may be: after the second data synchronizer receives the synchronization data from the second processor and reaches a first time period (for example, 5 seconds), confirms The second processor is in a dormant state; or, when the second data synchronizer receives a dormancy message from the second processor, it can confirm that the second processor is in a dormant state; or, when the second data synchronizer receives a message from the second processor After synchronizing data of the second processor, send start dormancy information (used to instruct the second processor to enter the dormancy state) to the second processor, and confirm that the second processor is in the dormant state.

It should be noted that the manner in which the second processor enters the sleep state may be: after sending the synchronization data to the second data synchronizer for a second period of time, the second processor enters the sleep state; or after receiving the second data processor After sending the start dormancy information, the second processor enters a dormant state. It can be understood that the embodiment of the present application does not specifically limit the manner in which the second processor enters the sleep state.

It should be understood that when the second device sends the synchronization data to the first device, the second processor can enter the sleep state after sending the synchronization data to the second data synchronizer, and then the second data synchronizer synchronizes the first data with the second device. to send synchronization data. In this way, the power consumption of the device can be further reduced, the standby time of the device can be prolonged, the power consumption of the device can be reduced, and the user experience can be improved.

In addition, in some possible embodiments, in order to further reduce the power consumption of the device, the second data synchronizer may also send synchronization data to the first data synchronizer when the second processor is in an off state. That is to say, when the second processor is in a sleep state or a shutdown state, the second data synchronizer sends synchronization data to the first data synchronizer.

Similarly, when the first device receives the synchronization data sent by the second device, since the first data synchronizer receives the synchronization data from the second data synchronizer, the first processor does not need to receive the synchronization data in real time. Synchronous data sent by the second device. Furthermore, during the process that the first data synchronizer receives the synchronization data from the second data synchronizer, the first processor may be in a sleep state or in a working state. In this way, during the process of the first data synchronizer receiving the synchronization data from the second data synchronizer, the first processor may choose to enter the sleep state to reduce the power consumption of the device, or process other data to improve the operation efficiency of the device.

Further optionally, in order to achieve the purpose of reducing the power consumption of the device, in the above S502, the first data synchronizer receives the synchronization data from the second data synchronizer, which may include the following sub-steps:

S502-2, when the first processor is in a sleep state, the first data synchronizer receives synchronization data from the second data synchronizer.

Similar to S502-1, the above-mentioned sleep state may mean that the first processor is in a low power consumption running state, for example, the first processor is in a state of standby, hibernation, or sleep. That is to say, the above-mentioned hibernation state may include: standby, hibernation, or sleep.

It should be understood that, in the process of receiving the synchronization data sent by the second device, the first data synchronizer receives the synchronization data from the second data synchronizer when the first processor is in a sleep state. In this way, the power consumption of the device can be further reduced, the standby time of the device can be prolonged, the power consumption of the device can be reduced, and the user experience can be improved.

It should be added that, in some possible embodiments, in order to further reduce the power consumption of the device, the first data synchronizer may also receive synchronization data from the second data synchronizer when the first processor is in an off state. That is, when the first processor is in a sleep state or a shutdown state, the first data synchronizer receives synchronization data from the second data synchronizer.

Based on the steps shown in the above S502, it should also be understood that in the process of receiving the synchronization data sent by the second device, the first processor only needs to receive the synchronization data sent by the first data synchronizer, and the second processor only needs to receive the synchronization data sent by the first data synchronizer. The synchronization data needs to be sent to the second data synchronizer, so that the two processors do not need to be in a working state frequently, nor need to frequently establish a communication connection, and the local data transfer speed is faster. In this way, the embodiments of the present application can also improve the data synchronization efficiency between devices.

Optionally, in the above S502, the second data synchronizer sends the synchronization data to the first device, which may include the following sub-steps:

S502-3, the second data synchronizer sends synchronization data to the first device according to the subscription parameter.

The subscription parameter is used by the first device to obtain synchronization data from the second device.

The above-mentioned subscription parameters may include one or more of the following: a first device identification code, a second device identification code, or subscription information for synchronizing data.

For the above-mentioned first device identification code and second device identification code, reference may be made to the explanation of the device identification code in S501, which will not be repeated here.

The above-mentioned subscription information of the synchronization data is used to indicate the synchronization data to be acquired. For example, the subscription information of the synchronization data may indicate that one or more of the following data need to be acquired: schedule data, itinerary data, express data, video data, music data, album data, or data to be read, etc. This is not specifically limited. For specific explanations of schedule data, itinerary data, express data, video data, music data, album data, or data to be read, reference may be made to the corresponding records in S501 above, which will not be repeated here.

In the process of the first device requesting the second device to send synchronization data, for example, it is assumed that the subscription parameter includes the first device identification code and the subscription information of the synchronization data, and the subscription information of the synchronization data is used to indicate that the video needs to be acquired data, the second data synchronizer may send video data (for example, the name of the episode of the video the user watches, the progress of the episode, etc.) to the first device according to the subscription parameter.

It can be understood that, in the process of data synchronization between devices, a subscription relationship with each other needs to be established first. Taking the first device needing to acquire the synchronization data of the second device as an example, first, the first device sends indication information for instructing the second device to feed back the synchronization data to the second device. Then, the second device sends synchronization data to the first device according to the indication information. The indication information may be understood as the above-mentioned subscription parameter.

That is to say, the process of establishing a mutual subscription relationship between devices may be: the device requesting to synchronize data sends subscription parameters to the device requested to synchronize data. Exemplarily, in a process in which the first device requests the second device to send synchronization data, the first device may be understood as a device requesting synchronization data, and the second device may be understood as a device requested to synchronize data. Therefore, the process of establishing a subscription relationship between the first device and the second device is: the first device sends subscription parameters to the second device, and the second device receives the subscription parameters.

Further optionally, in S502-3, before the second data synchronizer sends synchronization data to the first device according to the subscription parameters, the data synchronization method shown in FIG. 5 may further include the following sub-steps:

S502-4, the second data synchronizer receives the subscription parameters from the first device.

Optionally, in S502-4, after the second data synchronizer receives the subscription parameters from the first device, the data synchronization method shown in FIG. 5 may further include the following sub-steps:

S502-5, the second data synchronizer sends subscription parameters to the second processor.

It should be understood that the two steps of S502-4 and S502-5 correspond to the process of establishing a subscription relationship between the first device and the second device.

Optionally, in S502-5, before the second data synchronizer sends the subscription parameters to the second processor, the data synchronization method shown in FIG. 5 may further include the following sub-steps:

S502-6, if the second data synchronizer stores synchronization data, the second data synchronizer sends the synchronization data stored by the second data synchronizer to the first device according to the subscription parameter.

Exemplarily, it is assumed that the subscription information of the synchronization data in the subscription parameter indicates that video data needs to be acquired, and the second data synchronizer just stores the video data. In this case, before sending the subscription parameter to the second processor, the second data synchronizer may first send the video data to the first device according to the subscription parameter.

It should be understood that this enables the second data synchronizer to send the synchronization data to the first device in time when the synchronization data is already stored, thereby reducing the data synchronization time and further improving the data synchronization efficiency.

Optionally, in S502-5, before the second data synchronizer sends subscription parameters to the second processor, the data synchronization method shown in Figure 5 can also include one of the following substeps S502-7, S502-8:

S502-7, if the second processor is in a sleep state, the second data synchronizer wakes up the second processor.

S502-8, if the second processor is in a dormant state, the second data synchronizer waits for the second processor to wake up.

In this way, if the second data synchronizer actively wakes up the second processor, the second data synchronizer can send the subscription parameters to the second processor in time, so that the second device can timely feed back the synchronization data to the first device, and further Improve data synchronization efficiency.

It should also be understood that if the second data synchronizer waits for the second processor to wake up, in the process of waiting for the second processor to wake up, the second data synchronizer can receive as much synchronization data as possible to increase the data volume of the synchronization data. and completeness. In addition, the wake-up frequency of the second processor can also be reduced, thereby reducing the number of times that the second processor receives synchronous data, so as to save the computing resources of the second processor, further reduce the power consumption of the device, and improve the overall efficiency of the device operation.

It should be noted that, in order to further improve the data synchronization efficiency, optionally, the data synchronization method shown in FIG. 5 may further include the following sub-steps:

S502-9: The second processor receives the subscription parameters from the second data synchronizer, acquires synchronization data generated by the application according to the subscription parameters, and sends the synchronization data to the second data synchronizer.

Exemplarily, assuming that the subscription information of the synchronization data in the subscription parameter indicates that video data needs to be acquired, the second processor may monitor whether the video application generates new video data after receiving the subscription parameter. If the video application program generates new video data, the second processor acquires the video data and sends it to the second data synchronizer as synchronization data.

In this way, the second device can send the synchronization data generated by the application program to the first device in time, thereby further improving the data synchronization efficiency.

In the embodiments of the present application, regarding the implementation of the process of establishing a subscription relationship based on subscription parameters in the above S502-3, S502-4, S502-5, S502-6, S502-7, S502-8, and S502-9, please refer to The following S604-S609 are not repeated here.

It should be noted that the foregoing S502-6 may be executed before S502-7 and S502-8, or may be executed after S502-7 and S502-8, which is not limited in this embodiment of the present application.

S503, the first data synchronizer sends synchronization data to the first processor, and the first processor receives the synchronization data from the first data synchronizer.

Because the first processor may be in a sleep state or in a working state during the process of receiving the synchronization data from the second data synchronizer by the first data synchronizer. Therefore, when the first data synchronizer sends synchronization data to the first processor, the first processor may be in a dormant state or may be in a working state.

It should be noted that the synchronization data from the first data synchronizer can only be received when the first processor is in a working state. Therefore, the first data synchronizer may first detect whether the first processor is in the working state, and send the synchronization data to the first processor when the first processor is in the working state.

In a possible design, in order to further improve the data synchronization efficiency, in the above S503, the first data synchronizer sends the synchronization data to the first processor, which may include the following sub-steps:

S503-1, if the first data synchronizer detects that the first processor is in a working state, the first data synchronizer sends synchronization data to the first processor.

It should be understood that when the first processor wakes up (including active wake-up and passive wake-up), the first data synchronizer can send synchronization data to the first processor in time, thereby reducing data synchronization time and improving data synchronization efficiency.

In another possible design, in order to solve the reliability problem in the data synchronization process, in the above S503, the first data synchronizer sends the synchronization data to the first processor, which may include the following sub-steps:

S503-2: The first data synchronizer receives a synchronization instruction from the first processor, and sends synchronization data to the first processor according to the synchronization instruction.

The synchronization instruction is used to obtain synchronization data from the second device.

In the process that the first device requests the second device to send synchronization data, since the first processor does not directly perceive whether the first data synchronizer has received the synchronization data from the second device, in order to ensure the reliability and stability of the first device to receive the synchronization data of the second device, the first processor can generate a synchronization instruction (an instruction instructing the first data synchronizer to feed back the synchronization data of the second device), and send the synchronization instruction to the first data synchronizer so as to receive the synchronization instruction in time. The synchronization data fed back by the first data synchronizer completes the data synchronization process as soon as possible.

It should be noted that, the manner in which the first processor generates the synchronization instruction may be to generate the synchronization instruction every time it wakes up. Or, in the working state, a synchronization instruction is generated at a third time period. This embodiment of the present application does not limit this.

In addition, the lengths of the first time period, the second time period, and the third time period may be the same or different, which are not limited in this embodiment of the present application.

It can be understood that the first processor can send a synchronization instruction to the first data synchronizer, and then actively acquire the synchronization data from the second device from the first data synchronizer, thereby improving the reliability of data synchronization.

It should be noted that the foregoing S503-1 may be executed before S503-2, or may be executed after S503-2, which is not limited in this embodiment of the present application.

Optionally, before S503, the data synchronization method shown in FIG. 5 may further include the following steps:

S503-3, if the first data synchronizer detects that the first processor is in a sleep state, the first data synchronizer actively wakes up the first processor.

It should be understood that when the first processor sleeps, the first data synchronizer can actively wake it up and send the synchronization data to the first processor in a fast and timely manner, thereby further improving data synchronization efficiency.

Optionally, the data synchronization method shown in FIG. 5 may also include the following steps:

S503-4, the first data synchronizer receives the subscription parameters from the first processor, and sends the subscription parameters to the second device.

It should be understood that the second device may provide synchronization data according to the requirements of the first device, that is, the first device may customize the synchronization data to reduce unnecessary data synchronization operations, thereby further improving data synchronization efficiency.

In the embodiment of the present application, regarding the implementation of the process of establishing a subscription relationship based on subscription parameters in the above S503-4, reference may be made to the following S601-S603, which will not be repeated here.

S503-5, the first processor outputs synchronization data.

Exemplarily, the first processor may control the display of the first device to display the synchronization data, or control the speaker of the first device to play the synchronization data. In this way, the first device can remind the user to check the synchronization data output by the first processor, so that the user can determine the next operation, thereby improving user experience.

Hereinafter, taking the wireless communication system shown in FIG. 2 as an example, the implementation process of the data synchronization method provided in the embodiment of the present application in practical application will be described in detail.

The system architectures of the first device and the second device can both be the device system architectures shown in FIG. 3 . Specifically, the first processor in the first device can be the first AP, and the first data synchronizer can be The first SensorHub, the second processor in the second device may be the second AP, and the second data synchronizer may be the second SensorHub. The first AP may include the first application and the first bus service, and the second AP may include the second application and the second bus service. Wherein, the first application program may be a program in the application program layer of the first AP (for example, a smart life, synchronization program, etc.), and the second application program may be a program in the application program layer of the second AP (for example, express, video, itinerary, etc.), which is not limited in this embodiment of the present application.

Exemplarily, FIG. 6 is a second schematic flowchart of a data synchronization method provided by an embodiment of the present application. The data synchronization method can be applied to the wireless communication system shown in FIG. 2 , and the data synchronization method shown in FIG. 5 can be implemented.

As shown in FIG. 6 , the data synchronization method includes a process of establishing a subscription relationship based on subscription parameters and a synchronization process of synchronizing data. Refer to the following S601-S609 and S610-S616 respectively:

S601, the first application sends subscription parameters to the first bus service.

In this embodiment of the present application, the first application may generate subscription parameters, and send the subscription parameters to the first bus service. The manner in which the first application generates the subscription parameters may be as follows:

First, the second device sends subscribeable program information to the first device. The subscribeable program information may represent one or more applications in the second device that may generate synchronization data. For example, if the second device has the following application programs that can generate synchronous data, namely: video, itinerary, and express delivery, the second device can send a message to the first device that characterizes "applications in the second device that can generate synchronous data" The program includes: video, itinerary, express" information (you can subscribe to program information).

Then, after the first device receives the subscribeable program data from the second device, the first application may output the subscribeable program data. Exemplarily, if the subscribeable program information represents "the application programs in the second device that can generate synchronous data include: video, itinerary, and express delivery", the first application program can control the display of the first device to display the text message "Please select to subscribe. The program of the second device: A. video, B. itinerary, C. express”, or control the speaker of the first device to play the sound message “Please answer the program of the second device that needs to be subscribed: video, itinerary, express”.

Finally, the first application may respond to the user operation, determine the application selected by the user according to the user operation, and generate subscription parameters according to the application selected by the user. For example, if the subscribable program information represents "application programs that can generate synchronized data in the second device include: video, itinerary, express delivery", and the application program selected by the user is "video", the first application program can generate a program including " Second device identification code, information indicating subscription video" information. The information indicating the subscription of the video indicates that the first device needs to obtain the video data of the second device, that is, the information indicating the subscription of the video may also be understood as the above-mentioned subscription information of the synchronization data.

In this way, the second device can send the application program that can provide synchronization data to the first device, and the first device can output the service capability of the second device (that is, subscribe to program information), so that the user can synchronize the feedback of the second device according to the needs. Data is customized to reduce unnecessary data synchronization operations, thereby further improving data synchronization efficiency.

S602, the first bus service receives the subscription parameter from the first application, and sends the subscription parameter to the first SensorHub.

Optionally, after receiving the subscription parameters, the first bus service may save the subscription parameters. In this way, in the subsequent data synchronization process, the first bus service can send a synchronization command to the first SensorHub according to the subscription parameter, so as to actively obtain synchronization data from the first SensorHub. For example, in a working state, the first bus service may periodically send a synchronization command to the first SensorHub to periodically obtain synchronization data from the first SensorHub.

Optionally, after the first bus service sends the subscription parameter to the first SensorHub, the first AP may enter a sleep state.

S603, the first SensorHub receives the subscription parameter from the first bus service, and sends the subscription parameter to the second SensorHub.

Optionally, after receiving the subscription parameters, the first SensorHub may save the subscription parameters.

S604, if the second SensorHub stores the synchronization data, the second SensorHub sends the synchronization data to the first SensorHub according to the subscription parameter.

Optionally, after receiving the subscription parameters, the second SensorHub may save the subscription parameters. In this way, in the subsequent data synchronization process, if the second SensorHub receives new synchronization data that needs to be sent to the first device, it can directly send the synchronization data to the first SensorHub according to the subscription parameters, without having to send the synchronization data to the first SensorHub again. The device sends subscription parameters, thereby reducing data synchronization steps and improving synchronization efficiency.

S605, if the second AP is in a dormant state, the second SensorHub waits for the second AP to wake up.

S606, if the second AP is in a dormant state, the second SensorHub sends a wake-up instruction to the second AP to actively wake up the second AP.

S607, when the second AP is in the working state, the second SensorHub sends the subscription parameter to the second bus service.

S608, the second bus service receives the subscription parameters from the second SensorHub, and sends the subscription parameters to the second application.

S609, the second application acquires the synchronization data generated by the second application according to the subscription parameter.

Optionally, after receiving the subscription parameters, the second bus service may save the subscription parameters. In this way, in the subsequent data synchronization process, the second bus service can send an acquisition instruction (used to instruct to acquire the synchronization data generated by the second application) to the second application according to the subscription parameter, so as to actively acquire from the second application Synchronous Data. For example, in a working state, the second bus service may periodically send an acquisition instruction to the second application to acquire synchronization data from the second application periodically.

The above-mentioned S601-S609 are the processes of establishing a subscription relationship based on subscription parameters, and the synchronization process of synchronizing data will be described in detail below.

As shown in FIG. 6 , the synchronization process of synchronizing data may include the following S610-S616:

S610, the second application sends synchronization data to the second bus service.

Optionally, after the second bus service sends the synchronization data, the second application can actively send the new synchronization data to the second bus service when generating new synchronization data, so that the newly generated synchronization data can be fed back to the second bus service in time. The first device improves data synchronization efficiency.

S611, the second bus service receives the synchronization data from the second application, and sends the synchronization data to the second SensorHub.

Optionally, after the second bus service sends synchronization data to the second SensorHub, the second AP may enter a sleep state.

S612, the second SensorHub receives the synchronization data from the second bus service, and sends the synchronization data to the first SensorHub.

S613, the first bus service sends a synchronization command to the first SensorHub.

The synchronization instruction is used to acquire synchronization data from the second device.

Further optionally, if the first SensorHub receives a synchronization instruction from the first bus service, it may send synchronization data to the first processor according to the synchronization instruction.

S614, if the first SensorHub detects that the first AP is in a working state, the first SensorHub sends synchronization data to the first bus service.

S615, the first bus service receives the synchronization data from the first SensorHub, and sends the synchronization data to the first application.

S616, the first application program outputs the synchronization data.

It can be understood that after the execution of the above S601-S609, since the second SensorHub, the second bus service and the second application have all received the subscription parameters from the first device, when the second device generates synchronous data subsequently, it can directly Feedback to the first device according to the subscription parameter, that is, a subscription relationship has been established between the first device and the second device based on the subscription parameter. That is to say, when data synchronization is performed between the first device and the second device, the above-mentioned S601-S609 are first performed, and after the subscription relationship between the first device and the second device is established, the second application of the second device follows. When new synchronization data is generated in the program, S610-S616 can be directly executed (it is not necessary to execute S601-S609 again) to efficiently synchronize data.

It should be noted that, for parts not mentioned in the data synchronization method embodiment shown in FIG. 6, reference may be made to the corresponding content in the data synchronization method embodiment shown in FIG. 5. For example, S604 may refer to S502-6, and S605 may refer to Refer to S502-8 for S606, refer to S502-7 for S609, refer to S502-9 for S609, refer to S503-2 for S613, refer to S503-1 for S614, etc., which will not be repeated here.

The beneficial effects of the above method embodiments are further described below in combination with practical application scenarios.

As shown in Table 1 below, Table 1 shows the power consumption of the mobile phone in the same test process of different scenarios and different modules in the laboratory. Among them, Table 1 is collected from a mobile phone of a certain brand with a broadcast cycle of 1 second and a scanning duty cycle of 10% (2.3 mA). The test time of the mobile phone of a certain brand is 10 minutes, an average of 6 seconds to receive a broadcast, and an average wake-up of a broadcast AP time 3.5 seconds.

Table 1

It can be seen that in different operating scenarios, the power consumption value of "AP power consumption increment" is much larger than that of "SensorHub power consumption increment". For example, in the scenario of "one broadcast per second on a mobile phone", the test time of the mobile phone is 10 minutes, and an average of 6 seconds to receive a broadcast, the average time to wake up the AP for one broadcast is 3.5 seconds, and the "machine power consumption" during this period is 34 mA , while the power consumption value of "AP power consumption increment" is 24.35 mA, and the power consumption value of "SensorHub power consumption increment" is only 0.008 mA.

Obviously, the method of "using the data synchronizer to complete the data synchronization function without the participation of the processor" can greatly reduce the power consumption of the device, and the device does not need to wake up the AP frequently, that is, the data synchronization method provided by the embodiment of the present application can reduce the power consumption of the device Power consumption when synchronizing data between devices. Furthermore, since the communication connection between the devices does not need to be re-established, and the data transmission speed between the AP and the SensorHub is fast, the method provided by the embodiment of the present application can also improve the data synchronization efficiency.

In addition, the calculation of the battery terminal current value of SensorHub can refer to the following formula:

Among them, in the actual application scenario, the operating voltage of the SensorHub can be 0.75V (volts), the operating current of the SensorHub can be 11 mA, the battery voltage can be 3.8V, and the empirical value of the transmission loss rate can be 0.58.

Therefore, according to the above formula, the battery terminal current value of SensorHub can be calculated to be 3.74 mA, while the operating current required by the existing data synchronization technology is 49 mA.

Furthermore, in practical applications, since SensorHub processes broadcast data for about 2ms (milliseconds) once, if 100 broadcast calculations are processed in 10min (minutes), the synchronized data is received/sent in real time by applying SensorHub (that is, applying the above Figure 5 or Figure 5). 6), the increased power consumption of the device is about: 3.74*(0.002*100/600)=0.001 mA.

If the existing data synchronization technology is used for data synchronization, since the operating current required by the existing data synchronization technology is 49 mA, when the existing data synchronization technology is applied, the increased power consumption of the device is about: 49* 3.74*(0.002*100/600)=0.016 mA.

Obviously, compared with the existing data synchronization technology, the embodiment of the present application can reduce the power consumption of the first device and the second device, and improve the data synchronization efficiency.

It should be understood that, based on the data synchronization method shown in any one of FIG. 5-FIG. 6, the data synchronization function of the first device can be completed by the first data synchronizer, and the data synchronization function of the second device can be completed by the second data synchronization function. Synchronizer to complete, that is, the data synchronization function can be completed by the data synchronizer, and does not require the participation of the processor. In this way, even if the first processor is in a sleep state, the first data synchronizer can receive synchronization data from the second data synchronizer in real time, and even if the second processor is in a sleep state, the second data synchronizer can also Send synchronization data to the first device. Furthermore, the embodiments of the present application can reduce the power consumption of the first device and the second device, and improve the data synchronization efficiency.

The data synchronization method provided by the embodiments of the present application has been described in detail above with reference to FIGS. 5 to 6 . A communication apparatus for executing the data synchronization method provided by the embodiments of the present application will be described in detail below with reference to FIGS. 7 to 9 .

Exemplarily, FIG. 7 is a first structural schematic diagram of a communication apparatus provided by an embodiment of the present application. As shown in FIG. 7 , the communication apparatus 700 includes: a first processor 701 and a first data synchronizer 702 . For convenience of description, FIG. 7 only shows the main components of the communication device.

In some embodiments, the communication apparatus 700 may be applied to the wireless communication system shown in FIG. 2 to perform the function of the first device in the data synchronization method shown in FIG. 5 or FIG. 6 .

The first data synchronizer 702 is configured to receive synchronization data from the second device and send the synchronization data to the first processor 701 .

In a possible design solution, the first data synchronizer 702 is configured to receive synchronization data from the second device when the first processor 701 is in a dormant state, and send synchronization data to the first device when the first processor 701 is in a working state. Processor 701 sends synchronization data.

Optionally, the first data synchronizer 702 is configured to send synchronization data to the first processor 701 if it is detected that the first processor 701 is in a working state.

Or, optionally, the first data synchronizer 702 is configured to receive a synchronization instruction from the first processor 701, and send synchronization data to the first processor 701 according to the synchronization instruction. The synchronization instruction is used to obtain synchronization data from the second device.

In another possible design solution, the first data synchronizer 702 is further configured to actively wake up the first processor if it is detected that the first processor 701 is in a sleep state before sending the synchronization data to the first processor 701 701.

In another possible design solution, the first data synchronizer 702 is further configured to receive the subscription parameters from the first processor 701 and send the subscription parameters to the second device. The subscription parameter is used for the communication apparatus 700 to obtain synchronization data from the second device.

In another possible design solution, the first processor 701 is further configured to output synchronization data.

Optionally, the first data synchronizer 702 may include a receiver and a transmitter (not shown in FIG. 7 ). The first data synchronizer 702 is used to implement the sending function and the receiving function of the communication device 700 .

Optionally, the communication apparatus 700 may further include a memory (not shown in FIG. 7 ), which stores programs or instructions. When the first processor 701 and the first data synchronizer 702 execute the program or instruction, the communication apparatus 700 can execute the function of the first device in the data synchronization method shown in any one of FIGS. 5-6 .

It should be understood that the first processor 701 involved in the communication apparatus 700 may be implemented by a processor or a processor-related circuit component, and may be a processor or a processing unit; the first data synchronizer 702 may be a transceiver or a transceiver-related circuit component The implementation can be a transceiver or a transceiver unit.

It should be noted that the communication device 700 may be a terminal device or a network device, or a chip (system) or other components or components that can be provided in the terminal device or the network device, or a device including the terminal device or the network device, This application does not limit this.

In addition, for the technical effect of the communication apparatus 700, reference may be made to the technical effect of the data synchronization method shown in any one of FIG. 5-FIG. 6, which will not be repeated here.

Exemplarily, FIG. 8 is a second schematic structural diagram of a communication apparatus provided by an embodiment of the present application. As shown in FIG. 8 , the communication apparatus 800 includes: a second processor 801 and a second data synchronizer 802 . For convenience of explanation, FIG. 8 only shows the main components of the communication device 800 .

In some embodiments, the communication apparatus 800 can be applied to the wireless communication system shown in FIG. 2 to perform the function of the second device in the data synchronization method shown in FIG. 5 or FIG. 6 .

The second data synchronizer 802 is configured to receive synchronization data from the second processor 801 and send the synchronization data to the first device.

In a possible design solution, the second data synchronizer 802 is configured to send synchronization data to the first device when the second processor 801 is in a sleep state.

Optionally, the second data synchronizer 802 is configured to send synchronization data to the first device according to the subscription parameters. The subscription parameter is used by the first device to obtain synchronization data from the communication apparatus 800 .

Further, the second data synchronizer 802 is further configured to receive the subscription parameters from the first device before sending the synchronization data to the first device according to the subscription parameters.

Further, the second data synchronizer 802 is further configured to send the subscription parameters to the second processor 801 after receiving the subscription parameters from the first device.

Further, the second data synchronizer 802 is further configured to send the synchronization data to the first device according to the subscription parameters if synchronization data is stored before sending the subscription parameters to the second processor 801 .

Further, the second data synchronizer 802 is further configured to wake up the second processor 801 if the second processor 801 is in a dormant state before sending the subscription parameters to the second processor 801; or, the second data synchronizer 802 is further configured to wait for the second processor 801 to wake up if the second processor 801 is in a dormant state before sending the subscription parameters to the second processor 801 .

In another possible design solution, the second processor 801 is further configured to receive the subscription parameters from the second data synchronizer 802, obtain the synchronization data generated by the application according to the subscription parameters, and send the data to the second data synchronizer. 802 Send synchronization data.

Optionally, the second data synchronizer 802 may also be referred to as a transceiver. The transceiver may include a receiver and a transmitter (not shown in Figure 8). The transceiver is used to implement the sending function and the receiving function of the communication device 800 .

Optionally, the communication device 800 may further include a memory (not shown in FIG. 8 ), which stores programs or instructions. When the second processor 801 and the second data synchronizer 802 execute the program or instruction, the communication apparatus 800 can perform the function of the second device in the data synchronization method shown in any one of FIGS. 5-6 .

It should be understood that the second processor 801 involved in the communication apparatus 800 may be implemented by a processor or a processor-related circuit component, and may be a processor or a processing unit; the second data synchronizer 802 may be a transceiver or a transceiver-related circuit component The implementation can be a transceiver or a transceiver unit.

It should be noted that the communication apparatus 800 may be a terminal device or a network device, or a chip (system) or other components or components that can be provided in the terminal device or the network device, or may be a device including the terminal device or the network device, This application does not limit this.

In addition, for the technical effect of the communication apparatus 800, reference may be made to the technical effect of the data synchronization method shown in any one of FIG. 5-FIG. 6, which will not be repeated here.

Exemplarily, FIG. 9 is a third schematic structural diagram of a communication apparatus provided by an embodiment of the present application. The communication device may be a terminal device or a network device, or may be a chip (system) or other components or assemblies that can be provided in the terminal device or the network device. As shown in FIG. 9 , the communication apparatus 900 may include a processor 901 . Optionally, the communication device 900 may further include a memory 902 and/or a transceiver 903 . Wherein, the processor 901 is coupled with the memory 902 and the transceiver 903, such as can be connected through a communication bus.

Each component of the communication device 900 will be described in detail below with reference to FIG. 9 :

The processor 901 is the control center of the communication device 900, which may be one processor or a general term for multiple processing elements. For example, the processor 901 is one or more central processing units (CPUs), may also be a specific integrated circuit (application specific integrated circuit, ASIC), or is configured to implement one or more of the embodiments of the present application An integrated circuit, such as: one or more microprocessors (digital signal processor, DSP), or, one or more field programmable gate array (field programmable gate array, FPGA).

Optionally, the processor 901 may execute various functions of the communication device 900 by running or executing software programs stored in the memory 902 and calling data stored in the memory 902 .

In a specific implementation, as an embodiment, the processor 901 may include one or more CPUs, such as CPU0 and CPU1 shown in FIG. 9 .

In a specific implementation, as an embodiment, the communication apparatus 900 may also include multiple processors, for example, the processor 901 and the processor 904 shown in FIG. 9 . Each of these processors can be a single-core processor (single-CPU) or a multi-core processor (multi-CPU). A processor herein may refer to one or more devices, circuits, and/or processing cores for processing data (eg, computer program instructions).

The memory 902 is used to store the software program for executing the solution of the present application, and is controlled and executed by the processor 901. For the specific implementation, reference may be made to the above method embodiments, which will not be repeated here.

Alternatively, memory 902 may be read-only memory (ROM) or other types of static storage devices that can store static information and instructions, random access memory (RAM), or other types of static storage devices that can store information and instructions. Other types of dynamic storage devices for instructions, which may also be electrically erasable programmable read-only memory (EEPROM), compact disc read-only memory (CD-ROM), or other optical disks storage, optical disc storage (including compact disc, laser disc, optical disc, digital versatile disc, blu-ray disc, etc.), magnetic disk storage medium or other magnetic storage device, or capable of carrying or storing desired program code in the form of instructions or data structures and any other medium that can be accessed by a computer, but is not limited thereto. The memory 902 may be integrated with the processor 901, or may exist independently, and be coupled to the processor 901 through an interface circuit (not shown in FIG. 9) of the communication device 900, which is not specifically limited in this embodiment of the present application.

The transceiver 903 is used for communication with other communication devices. For example, the communication apparatus 900 is a terminal device, and the transceiver 903 may be used to communicate with a network device or communicate with another terminal device. For another example, the communication apparatus 900 is a network device, and the transceiver 903 can be used to communicate with a terminal device or communicate with another network device.

Optionally, transceiver 903 may include a receiver and a transmitter (not shown separately in FIG. 9). Among them, the receiver is used to realize the receiving function, and the transmitter is used to realize the sending function.

Optionally, the transceiver 903 may be integrated with the processor 901, or may exist independently, and be coupled to the processor 901 through an interface circuit (not shown in FIG. 9 ) of the communication device 900, which is not made in this embodiment of the present application Specific restrictions.

It should be noted that the structure of the communication device 900 shown in FIG. 9 does not constitute a limitation on the communication device, and an actual communication device may include more or less components than those shown in the figure, or combine some components, or Different component arrangements.

In addition, for the technical effect of the communication apparatus 900, reference may be made to the technical effect of the data synchronization method described in the above method embodiments, and details are not described herein again.

An embodiment of the present application further provides a chip system, including: a processor, where the processor is coupled with a memory, the memory is used to store a program or an instruction, and when the program or instruction is executed by the processor, the The chip system implements the method in any of the foregoing method embodiments.

Optionally, the number of processors in the chip system may be one or more. The processor can be implemented by hardware or by software. When implemented in hardware, the processor may be a logic circuit, an integrated circuit, or the like. When implemented in software, the processor may be a general-purpose processor implemented by reading software codes stored in memory.

Optionally, there may also be one or more memories in the chip system. The memory may be integrated with the processor, or may be provided separately from the processor, which is not limited in this application. Exemplarily, the memory can be a non-transitory processor, such as a read-only memory ROM, which can be integrated with the processor on the same chip, or can be provided on different chips. The setting method of the processor is not particularly limited.

Exemplarily, the system-on-chip may be a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), or a system on chip (SoC), It can also be a central processing unit (CPU), a network processor (NP), a digital signal processing circuit (DSP), or a microcontroller (microcontroller). controller unit, MCU), it can also be a programmable logic device (PLD) or other integrated chips.

Embodiments of the present application provide a communication system. The communication system includes the above-mentioned first device and second device.

It should be understood that the processor in the embodiments of the present application 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 (eg, circuits), 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.

It should be understood that the term "and/or" in this document is only an association relationship to describe associated objects, indicating that there can be three kinds of relationships, for example, A and/or B, which can mean that A exists alone, and A and B exist at the same time , there are three cases of B alone, where A and B can be singular or plural. In addition, the character "/" in this document generally indicates that the related objects before and after are an "or" relationship, but may also indicate an "and/or" relationship, which can be understood with reference to the context.

In this application, "at least one" means one or more, and "plurality" means two or more. "At least one item(s) below" or similar expressions thereof refer to any combination of these items, including any combination of single item(s) or plural items(s). For example, at least one (a) of a, b, or c can represent: a, b, c, a-b, a-c, b-c, or a-b-c, where a, b, c may be single or multiple .

It should be understood that, in various embodiments of the present application, the size of the sequence numbers of the above-mentioned processes does not mean the sequence of execution, and the execution sequence of each process should be determined by its functions and internal logic, and should not be dealt with in the embodiments of the present application. implementation constitutes any limitation.

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, and 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 (ROM), 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 data synchronization method, characterized in that it is applied to a first device, the first device includes a first data synchronizer and a first processor, and the method includes:

the first data synchronizer receives synchronization data from the second device;

The first data synchronizer sends the synchronization data to the first processor.
The method according to claim 1, wherein sending the synchronization data to the first processor by the first data synchronizer comprises:

If the first data synchronizer detects that the first processor is in a working state, the first data synchronizer sends the synchronization data to the first processor.
The method according to claim 1, wherein sending the synchronization data to the first processor by the first data synchronizer comprises:

The first data synchronizer receives a synchronization instruction from the first processor; the synchronization instruction is used to obtain the synchronization data from the second device;

The first data synchronizer sends the synchronization data to the first processor according to the synchronization instruction.
The method according to any one of claims 1-3, wherein before the first data synchronizer sends the synchronization data to the first processor, the method further comprises:

If the first data synchronizer detects that the first processor is in a sleep state, the first data synchronizer actively wakes up the first processor.
The method according to any one of claims 1-4, wherein the method further comprises:

The first data synchronizer receives subscription parameters from the first processor; the subscription parameters are used by the first device to obtain the synchronization data from the second device;

The first data synchronizer sends the subscription parameter to the second device.
The method according to any one of claims 1-5, wherein the method further comprises:

The first processor outputs the synchronization data.
The method according to any one of claims 1-6, wherein the first data synchronizer receives synchronization data from the second device, comprising:

The first data synchronizer receives synchronization data from the second device while the first processor is in a sleep state.
A data synchronization method, characterized in that it is applied to a second device, the second device includes a second data synchronizer and a second processor, and the method includes:

the second data synchronizer receives synchronization data from the second processor;

The second data synchronizer sends the synchronization data to the first device.
The method according to claim 8, wherein the second data synchronizer sends the synchronization data to the first device, comprising:

The second data synchronizer sends the synchronization data to the first device according to a subscription parameter; the subscription parameter is used by the first device to obtain the synchronization data from the second device.
The method according to claim 9, wherein before the second data synchronizer sends the synchronization data to the first device according to a subscription parameter, the method further comprises:

The second data synchronizer receives the subscription parameters from the first device.
The method according to claim 10, wherein after the second data synchronizer receives the subscription parameter from the first device, the method further comprises:

The second data synchronizer sends the subscription parameters to the second processor.
The method of claim 11, before the second data synchronizer sends the subscription parameter to the second processor, the method further comprising:

If the second data synchronizer stores the synchronization data, the second data synchronizer sends the synchronization data to the first device according to the subscription parameter.
The method according to claim 11 or 12, wherein before the second data synchronizer sends the subscription parameter to the second processor, the method further comprises one of the following:

If the second processor is in a sleep state, the second data synchronizer wakes up the second processor; or,

If the second processor is in a sleep state, the second data synchronizer waits for the second processor to wake up.
The method according to any one of claims 9-13, wherein the method further comprises:

the second processor receives the subscription parameter from the second data synchronizer;

The second processor obtains the synchronization data generated by the application according to the subscription parameter;

The second processor sends the synchronization data to the second data synchronizer.
The method according to any one of claims 8-14, wherein the second data synchronizer sends the synchronization data to the first device, comprising:

When the second processor is in a sleep state, the second data synchronizer sends the synchronization data to the first device.
A communication device, characterized in that the device comprises a first data synchronizer and a first processor;

the first data synchronizer for receiving synchronization data from the second device;

The first data synchronizer is further configured to send the synchronization data to the first processor.
The apparatus according to claim 16, wherein the first data synchronizer is configured to send the synchronization data to the first processor if it is detected that the first processor is in a working state.
The apparatus according to claim 16, wherein the first data synchronizer is configured to receive a synchronization instruction from the first processor; the synchronization instruction is used to obtain all the data from the second device. the synchronization data;

The first data synchronizer is further configured to send the synchronization data to the first processor according to the synchronization instruction.
The apparatus according to any one of claims 16-18, wherein the first data synchronizer is further configured to, before sending the synchronization data to the first processor, if the synchronization data is detected If the first processor is in a dormant state, the first processor is actively woken up.
The apparatus according to any one of claims 16-19, wherein the first data synchronizer is further configured to receive subscription parameters from the first processor; the subscription parameters are used for the the apparatus obtains the synchronization data from the second device;

The first data synchronizer is further configured to send the subscription parameter to the second device.
The apparatus according to any one of claims 16-20, wherein the first processor is further configured to output the synchronization data.
The apparatus according to any one of claims 16-21, wherein the first data synchronizer is configured to receive synchronization data from the second device when the first processor is in a sleep state .
A communication device, characterized in that the device comprises a second data synchronizer and a second processor;

the second data synchronizer for receiving synchronization data from the second processor;

The second data synchronizer is further configured to send the synchronization data to the first device.
The apparatus according to claim 23, wherein the second data synchronizer is configured to send the synchronization data to the first device according to a subscription parameter; the subscription parameter is used for the first device to acquire the synchronization data from the device.
The apparatus according to claim 24, wherein the second data synchronizer is further configured to receive all data from the first device before sending the synchronization data to the first device according to subscription parameters. the subscription parameters.
The apparatus according to claim 25, wherein the second data synchronizer is further configured to send the subscription to the second processor after receiving the subscription parameter from the first device parameter.
The apparatus according to claim 26, wherein the second data synchronizer is further configured to, before sending the subscription parameters to the second processor, if the synchronization data is stored, Send the synchronization data to the first device using the subscription parameter.
The apparatus according to claim 26 or 27, wherein the second data synchronizer is further configured to, before sending the subscription parameter to the second processor, if the second processor is in sleep mode state, wake up the second processor; or,

The second data synchronizer is further configured to wait for the second processor to wake up if the second processor is in a dormant state before sending the subscription parameter to the second processor.
The apparatus according to any one of claims 24-28, wherein the second processor is further configured to receive a subscription parameter from the second data synchronizer;

The second processor is further configured to obtain the synchronization data generated by the application according to the subscription parameter;

The second processor is further configured to send the synchronization data to the second data synchronizer.
The apparatus according to any one of claims 23-29, wherein the second data synchronizer is configured to send the data to the first device when the second processor is in a sleep state Synchronous Data.
A communication device, characterized in that the communication device includes a processor and a transceiver, the transceiver is used for information interaction between the communication device and other communication devices, and the processor executes program instructions to execute The data synchronization method according to any one of claims 1-15.
A computer-readable storage medium, characterized in that the computer-readable storage medium comprises a computer program or instruction, which, when the computer program or instruction is executed on a computer, causes the computer to perform as in claims 1-15 Any one of the data synchronization methods.
A computer program product, characterized in that the computer program product comprises: a computer program or instruction, when the computer program or instruction is run on a computer, the computer is made to execute any one of claims 1-15 The described data synchronization method.