Bluetooth Synchronization Method, System, Bluetooth Device and Computer Readable Storage Medium

Abstract

The present application provides a Bluetooth synchronization method, system, Bluetooth device, and computer-readable storage medium, which relate to the field of communication technologies. When applied to a slave device, it includes: generating a target data packet according to a synchronization event, wherein the header of the target data packet has identification information of a data type, and the identification information is information for a master device to which the slave device is communicatively connected to determine whether to forward; sending the target data packet to the master device for the master device to forward protocol data based on the target data packet; and executing the synchronization event according to the received protocol data. When applied to a master device, it includes: receiving the target data packet sent from the slave device; parsing the target data packet to obtain protocol data and a time stamp corresponding to the protocol data when the identification information is successfully verified; and forwarding the protocol data to the corresponding slave device based on the time stamp. It effectively reduces the bandwidth occupied when Bluetooth devices use other links for synchronization and ensures the normal use of Bluetooth communication.

Description

Technical Field

[0001] This application relates to the field of communication technologies, and in particular, to a Bluetooth synchronization method, system, Bluetooth device, and computer-readable storage medium. Background Art

[0002] Currently, there are more and more Bluetooth audio products, and various Bluetooth audio devices, such as TWS earphones, wireless MICs, and wireless speakers, are being used more and more widely. When there are multiple audio devices, it is necessary to synchronize the multiple audio devices so that the multiple audio devices can play or process the corresponding audio data synchronously. For example, two wireless earphones need to play local prompt sounds simultaneously.

[0003] In the communication mode of classic Bluetooth, communication is usually carried out through a private link, but the private link needs to be kept connected at all times. When the synchronization requests are not frequent, the bandwidth load of Bluetooth is relatively large; in the communication mode of the new generation of Bluetooth audio technology standards, the master device of Bluetooth can be connected to each slave device for unified control, but corresponding protocols need to be set to define the specific control method during control, and it is impossible to perform synchronous control for all situations. When encountering undefined control situations, a private link will also be established for communication. That is, in the current Bluetooth synchronization methods, synchronization needs to be carried out through a private link. When a private link is established temporarily for synchronization, it takes a long time, resulting in low efficiency of Bluetooth communication. When a private link is maintained for synchronization, data packets need to be sent and received periodically. In most cases, there is no data transmission in the data packets, resulting in a large overhead when maintaining a private link for synchronization, a large bandwidth load during Bluetooth communication, and in some low-latency demand scenarios, maintaining a private link will cause packet loss and other phenomena during normal Bluetooth communication. Therefore, in the current synchronization methods, the synchronization efficiency is low, which is likely to have an adverse impact on the normal data transmission of Bluetooth and affect the normal use of Bluetooth communication. Summary of the Invention

[0004] In view of this, the purpose of the embodiments of this application is to provide a Bluetooth synchronization method, system, Bluetooth device, and computer-readable storage medium to improve the problem that Bluetooth synchronization in the existing technology affects the normal use of Bluetooth communication.

[0005] To solve the above problems, in a first aspect, the embodiments of this application provide a Bluetooth synchronization method, which is applied to a slave device. The method includes:

[0006] Generating a target data packet according to a synchronization event, where the header of the target data packet has identification information of a data type, and the identification information is information for a master device to which the slave device is communicatively connected to determine whether to forward.

[0007] Send the target data packet to the master device for the master device to forward protocol data based on the target data packet;

[0008] Execute the synchronization event according to the received protocol data.

[0009] In the above implementation process, when the slave device needs to perform event synchronization, it can generate a target data packet that identifies the data type according to the synchronized event, so as to send the target data packet to the master device for a synchronization request, and receive the protocol data forwarded by the master device based on the target data packet, so as to execute the corresponding Bluetooth protocol according to the protocol data, and thus execute the synchronization event. By identifying the data type, events in various different situations can be marked as a unified data type, so that the synchronized data packet can be directly sent through the original Bluetooth link between the slave device and the master device, and the protocol data can be received, without the need to separately set up a private link to send and receive the data packet and the protocol data, thus effectively reducing the bandwidth occupied during event synchronization of Bluetooth communication, reducing the overhead load of Bluetooth communication, and also improving the efficiency and accuracy when multiple slave devices perform event synchronization, so that Bluetooth communication can be used normally during event synchronization.

[0010] Optionally, the generating the target data packet according to the synchronization event includes:

[0011] Determine the protocol data of the synchronization event in the target layer, where the target layer is any one of multiple protocol layers;

[0012] Put the corresponding timestamp into the protocol data to generate an initial data packet, where the timestamp is the time information corresponding to the unified clock source of the master device and the slave device;

[0013] Set identification information in the header of the initial data packet according to the data type of the initial data packet to obtain the target data packet.

[0014] In the above implementation process, since corresponding protocol data is required when executing an event for the slave device to perform corresponding operations and processing based on the protocol data, it is possible to determine the protocol data corresponding to the synchronization event in multiple types of protocol layers of the slave device. To improve the accuracy of the execution time during event synchronization, the time information corresponding to the unified clock source of the master device and the slave device can also be placed in the protocol data, which can combine the execution protocol of the synchronization event with the forwarding time limit to generate an initial data packet and mark it at the head of the data packet to identify that the initial data packet is the data type corresponding to the synchronization event, thereby generating the target data packet corresponding to the synchronization event. Through the identification of the data type, the target data packet can be directly transmitted on the original Bluetooth link between the slave device and the master device without setting up a separate private link for transmission, which is beneficial for the master device to perform corresponding parsing and processing of the target data packet and will not have an adverse impact on the processing of other data normally transmitted in Bluetooth communication.

[0015] Optionally, executing the synchronization event according to the received protocol data includes:

[0016] Parsing the received protocol data based on the target layer to obtain the protocol type and synchronization time of the synchronization event;

[0017] Determining whether the preparation duration corresponding to the protocol type is less than the interval duration, where the interval duration is the time period between the current first time of the slave device determined based on a timer and the synchronization time;

[0018] When the preparation duration is less than the interval duration, prepare based on the protocol type and execute the protocol type of the synchronization event at the synchronization time.

[0019] In the above implementation process, since the slave device needs to perform corresponding preparation processing according to the specific situation of the protocol before executing the protocol, after receiving the protocol data, the slave device can first perform parsing to obtain the corresponding protocol type and synchronization time, determine the preparation duration corresponding to the protocol operation according to the protocol type, and compare the size of the interval duration between the current first time of the slave device and the synchronization time with the preparation duration. When the preparation duration is less than the interval duration, it means that there is enough time for preparation between the current time and the synchronization time, so preparation can be carried out according to the protocol type to execute the corresponding protocol type at the synchronization time, thereby realizing the synchronous execution processing of the synchronization event. It can judge whether to execute the synchronization event according to time, effectively reducing the situation where the synchronization event is delayed for processing.

[0020] In a second aspect, an embodiment of the present application further provides a Bluetooth synchronization method applied to a master device, and the method includes:

[0021] Receive the target data packet sent from the slave device, where the header of the target data packet has identification information of the data type, and the identification information is the information for the master device to determine whether to forward;

[0022] When the identification information is successfully verified, parse the target data packet to obtain the protocol data and the timestamp corresponding to the protocol data;

[0023] Based on the timestamp, forward the protocol data to the corresponding slave device.

[0024] In the above implementation process, after receiving the target data packet with identification information in the header, the master device can verify the identification information. When the verification is successful, it parses the target data packet to obtain the protocol data and the corresponding timestamp, and then forwards the protocol data accordingly based on the timestamp. It can quickly parse and forward the target data packet according to the identification information in the target data packet. When receiving the target data packet and forwarding the protocol data, it can directly receive and forward through the original Bluetooth link between the slave device and the master device, without separately setting up a private link to receive and forward the data packet and the protocol data, effectively reducing the bandwidth occupied during the event synchronization of Bluetooth communication, reducing the overhead load of Bluetooth communication, and also improving the efficiency and accuracy of forwarding when multiple slave devices respond to the synchronization request, so that Bluetooth communication can be used normally during event synchronization.

[0025] Optionally, the step of, when the identification information is successfully verified, parsing the target data packet to obtain the protocol data and the timestamp corresponding to the protocol data includes:

[0026] Determine the corresponding data type according to the identification information in the header of the target data packet;

[0027] When the data type is the target type, the identification information is successfully verified, and determine the target layer corresponding to the target data packet, where the target layer is any one of multiple protocol layers;

[0028] Parse the target data packet in the target layer to obtain the protocol data and the corresponding timestamp.

[0029] In the above implementation process, verification can be performed first based on the identification information to verify whether the data type in the identification information is a preset target type. If so, it indicates that the target data packet is a data packet of a synchronization event. The target layer for forwarding processing can be determined based on the target data packet, so that data can be processed at a unified protocol layer in the slave device and the master device, improving the generality and unity of data processing. In the target layer, the master device only needs to parse the target data packet to obtain the protocol data and timestamp corresponding to the synchronization event, without processing the specific protocol content of the protocol data therein. It can directly determine whether the target data packet is related to the synchronization event based on the identification information and perform effective processing in the corresponding target layer, enabling the target data packet to be distinguished from other data during normal Bluetooth communication and not causing an adverse impact on the processing of other data normally transmitted in Bluetooth communication. This realizes directly processing the synchronization event on the original Bluetooth link between the slave device and the master device without setting up a separate private link for transmission, improving the efficiency and accuracy of the master device in correspondingly parsing and processing the target data packet.

[0030] Optionally, forwarding the protocol data to the corresponding slave device based on the timestamp includes:

[0031] Determine whether the current second time of the master device is less than the set time in the timestamp;

[0032] When the second time is less than the set time, forward the protocol data to the corresponding slave device through the target layer.

[0033] In the above implementation process, the timestamp can be a relevant time period for limiting the time of forwarding processing and can include the set time at the end of execution. To improve the real-time performance and effectiveness of forwarding, the master device also compares the current second time with the set time. When the second time is less than the set time, it indicates that the current second time is before the set time at the end of execution and the forwarding operation has not timed out, and forwarding processing can be performed in the corresponding target layer. By judging the time node of forwarding, forwarding processing can be performed within an effective time period, thereby reducing the adverse impact on forwarding caused by unstable Bluetooth communication and other situations, ensuring the real-time performance and effectiveness of forwarding, and reducing the delay during Bluetooth synchronization.

[0034] Optionally, forwarding the protocol data to the corresponding slave device through the target layer includes:

[0035] Through the target layer, determine the forwarding range and forwarding form according to the forwarding requirements, where the forwarding range includes one or more channel groups, each channel group includes one or more of the slave devices, and the forwarding form includes unicast form or broadcast form;

[0036] Forward the protocol data to the corresponding slave device through the target layer based on the forwarding range and the forwarding form.

[0037] In the above implementation process, the range and form for forwarding can be determined based on the corresponding tunneling requirements on different protocol layers, so as to forward the protocol data to the corresponding slave device according to the corresponding method. It can perform corresponding forwarding according to the type of protocol layer, as well as the actual situation or user requirements in the slave device or the master device, effectively optimizing the effect during forwarding.

[0038] In a third aspect, an embodiment of the present application further provides a Bluetooth synchronization method, and the method includes:

[0039] Through the slave device, generate a target data packet according to a synchronization event, and send the target data packet to the master device for the master device to forward protocol data based on the target data packet; wherein, the header of the target data packet has identification information of the data type, and the identification information is information for the master device to which the slave device is communicatively connected to determine whether to forward.

[0040] Through the master device, receive the target data packet sent from the slave device; when the identification information is successfully verified, parse the target data packet to obtain the protocol data and the time stamp corresponding to the protocol data; based on the time stamp, forward the protocol data to the corresponding slave device.

[0041] Through the slave device, execute the synchronization event according to the received protocol data.

[0042] In a fourth aspect, an embodiment of the present application further provides a Bluetooth synchronization system, and the system includes: a slave device and a master device, and the slave device and the master device are communicatively connected based on a Bluetooth link;

[0043] The slave device is configured to generate a target data packet according to a synchronization event; send the target data packet to the master device for the master device to forward protocol data based on the target data packet; wherein, the header of the target data packet has identification information of the data type, and the identification information is information for the master device to which the slave device is communicatively connected to determine whether to forward.

[0044] The master device is configured to receive the target data packet sent from the slave device; when the identification information is successfully verified, parse the target data packet to obtain the protocol data and the time stamp corresponding to the protocol data; based on the time stamp, forward the protocol data to the corresponding slave device.

[0045] The slave device is further configured to execute the synchronization event according to the received protocol data.

[0046] In a fifth aspect, an embodiment of the present application further provides a Bluetooth device, which includes a memory and a processor. Program instructions are stored in the memory. When the processor reads and runs the program instructions, the steps in any implementation manner of the above Bluetooth synchronization method are executed.

[0047] In a sixth aspect, an embodiment of the present application further provides a computer-readable storage medium. Computer program instructions are stored in the readable storage medium. When the computer program instructions are read and run by a processor, the steps in any implementation manner of the above Bluetooth synchronization method are executed.

[0048] In summary, the present application provides a Bluetooth synchronization method, system, Bluetooth device, and computer-readable storage medium. By identifying and parsing the data packets of synchronization events, synchronization processing can be performed in the original Bluetooth link without separately setting up a private link for synchronization processing. Thus, the bandwidth occupied during event synchronization of Bluetooth communication is effectively reduced, the overhead load of Bluetooth communication is decreased, and the efficiency and accuracy during event synchronization are improved, enabling Bluetooth communication to be normally used during event synchronization. BRIEF DESCRIPTION OF THE DRAWINGS

[0049] To more clearly illustrate the technical solutions of the embodiments of the present application, the following briefly introduces the drawings required to be used in the embodiments of the present application. It should be understood that the following drawings only show some embodiments of the present application and should not be regarded as limiting the scope. For those of ordinary skill in the art, other related drawings can be obtained based on these drawings without creative efforts.

[0050] Figure 1 It is a block diagram of a Bluetooth device provided by an embodiment of the present application;

[0051] Figure 2 It is a structural diagram of a Bluetooth synchronization system provided by an embodiment of the present application;

[0052] Figure 3 It is a flowchart of a Bluetooth synchronization method provided by an embodiment of the present application;

[0053] Figure 4 It is a flowchart of a Bluetooth synchronization method applied to a slave device provided by an embodiment of the present application;

[0054] Figure 5 It is a detailed flowchart of step S410 provided by an embodiment of the present application;

[0055] Figure 6 It is a detailed flowchart of step S430 provided by an embodiment of the present application;

[0056] Figure 7 It is a schematic flowchart of a Bluetooth method applied to a master device provided by an embodiment of the present application;

[0057] Figure 8 It is a detailed flowchart of step S520 provided by an embodiment of the present application;

[0058] Figure 9 It is a detailed flowchart of step S530 provided by an embodiment of the present application;

[0059] Figure 10 It is a detailed flowchart of step S5302 provided by an embodiment of the present application.

[0060] Icons: 100 - Bluetooth device; 111 - Memory; 112 - Storage controller; 113 - Processor; 114 - Peripheral interface; 115 - Input / output unit; 116 - Display unit; 210 - Master device; 220 - Slave device. Detailed implementation manners

[0061] Next, the technical solutions in the embodiments of the present application will be clearly and completely described with reference to the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, rather than all the embodiments. All other embodiments obtained by those of ordinary skill in the art based on the embodiments of the present application without creative efforts shall fall within the protection scope of the embodiments of the present application.

[0062] In the communication mode of classic Bluetooth, a private link needs to be maintained between the master device and the slave device to perform synchronization processing through this private link. However, when maintaining the private link for synchronization, it is necessary to periodically send and receive data packets. In most cases, there is no data transmission in the data packets, resulting in a large overhead when maintaining the private link for synchronization and a large bandwidth load during Bluetooth communication. Moreover, in some low-latency demand scenarios, maintaining the private link will cause packet loss and other phenomena during normal Bluetooth communication. In the prior art, various methods are used to reduce the bandwidth of this private link, such as temporarily establishing it when synchronization processing is required, etc. However, when temporarily establishing a private link for synchronization, it takes a long time, resulting in low efficiency of Bluetooth communication.

[0063] In the communication mode of LE audio (the new generation of Bluetooth audio technology standard), although the master device of Bluetooth can be connected to multiple slave devices and uniformly controlled according to the methods defined in the Bluetooth protocol, when controlling, the corresponding Bluetooth protocol needs to be set to define the specific control method. When Bluetooth devices are in use, users often have various different requirements and operations, and it is impossible to synchronously control all requirements and operations during control. Therefore, when encountering undefined control situations, a private link will also be established for communication.

[0064] Therefore, in the current Bluetooth synchronization methods, synchronization needs to be carried out through a private link, resulting in a large bandwidth load during Bluetooth communication and low efficiency during synchronization, which is likely to have an adverse impact on the normal data transmission of Bluetooth and affect the normal use of Bluetooth communication.

[0065] To solve the above problems, on the one hand, the embodiments of the present application provide a Bluetooth synchronization method, which is applied to Bluetooth devices. The Bluetooth devices may include the master device and slave devices of Bluetooth. The slave devices may be various types of audio devices such as headphones and speakers, and the master device may be an electronic device with logical computing functions such as a server, a personal computer (PC), a tablet computer, a smart phone, and a personal digital assistant (PDA). It can directly perform synchronization processing through the original link during Bluetooth communication between the master device and the slave device, without the need to separately set up a private link for synchronization processing.

[0066] Optionally, please refer to Figure 1 , Figure 1 which is a block diagram of a Bluetooth device provided by the embodiments of the present application. The Bluetooth device 100 may include a memory 111, a storage controller 112, a processor 113, a peripheral interface 114, an input / output unit 115, and a display unit 116. Those of ordinary skill in the art can understand that Figure 1 the structure shown is only schematic and does not limit the structure of the Bluetooth device 100. For example, the Bluetooth device 100 may also include more or fewer components than those shown in Figure 1 , or have a different configuration from that shown in Figure 1 .

[0067] The above-mentioned memory 111, storage controller 112, processor 113, peripheral interface 114, input / output unit 115, and display unit 116 are directly or indirectly electrically connected to each other to achieve data transmission or interaction. For example, these components may be electrically connected to each other through one or more communication buses or signal lines. The above-mentioned processor 113 is used to execute the executable module stored in the memory.

[0068] Among them, the memory 111 can be, but is not limited to, random access memory (RAM), read only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), etc. Among them, the memory 111 is used to store programs. After receiving an execution instruction, the processor 113 executes the program. The method executed by the Bluetooth device 100 defined by the process disclosed in any embodiment of the embodiments of the present application can be applied to or implemented by the processor 113.

[0069] The above-mentioned processor 113 may be an integrated circuit chip with signal processing capabilities. The above-mentioned processor 113 may be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), etc.; it may also be a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components. It can implement or execute the various methods, steps, and logic block diagrams disclosed in the embodiments of the present application. The general-purpose processor may be a microprocessor or any conventional processor, etc.

[0070] The above-mentioned peripheral interface 114 couples various input / output devices to the processor 113 and the memory 111. In some embodiments, the peripheral interface 114, the processor 113, and the memory controller 112 may be implemented on a single chip. In some other instances, they may be implemented by separate chips respectively.

[0071] The above-mentioned input / output unit 115 is used to provide input data to the user. The input / output unit 115 can be, but is not limited to, a mouse, a keyboard, etc.

[0072] Optionally, when the Bluetooth device 100 is the master device of Bluetooth, the above display unit 116 provides an interaction interface (such as a user operation interface) between the Bluetooth device 100 and the user or is used to display image data for the user to refer to. In this embodiment, the display unit may be a liquid crystal display or a touch display. If it is a touch display, it may be a capacitive touch screen or a resistive touch screen that supports single-point and multi-point touch operations, etc. Supporting single-point and multi-point touch operations means that the touch display can sense touch operations generated simultaneously at one or more positions on the touch display and hand over the sensed touch operations to the processor for calculation and processing. In the embodiment of the present application, the display unit 116 may display the names, quantities, and various data transmitted and received by the slave devices connected to the master device.

[0073] Optionally, when the Bluetooth device 100 is a slave device of Bluetooth, the Bluetooth device 100 may further include various units such as a speaker and a microphone.

[0074] Optionally, please refer to Figure 2 , Figure 2 FIG. is a schematic structural diagram of a Bluetooth synchronization system provided by an embodiment of the present application. The Bluetooth synchronization system may include a master device 210 and a slave device 220. Among them, the master device 210 is communicatively connected to one or more slave devices 220 (only two are shown in the figure) based on a Bluetooth link.

[0075] The slave device 220 is configured to generate a target data packet according to a synchronization event; send the target data packet to the master device 210 for the master device 210 to forward protocol data based on the target data packet; wherein, the header of the target data packet has identification information of the data type, and the identification information is information for the master device 210 communicatively connected to the slave device 220 to determine whether to forward.

[0076] The master device 210 is configured to receive the target data packet sent from the slave device 220; when the identification information verification is successful, parse the target data packet to obtain the protocol data and the timestamp corresponding to the protocol data; based on the timestamp, forward the protocol data to the corresponding slave device 220.

[0077] The slave device 220 is further configured to execute a synchronization event according to the received protocol data.

[0078] In an optional embodiment, the slave device 220 is further configured to determine the protocol data of the synchronization event in the target layer, where the target layer is any one of multiple protocol layers; put the corresponding timestamp into the protocol data to generate an initial data packet, where the timestamp is the time information corresponding to the unified clock source of the master device 210 and the slave device 220; set identification information in the header of the initial data packet according to the data type of the initial data packet to obtain the target data packet.

[0079] In an alternative embodiment, the master device 210 is further configured to determine the corresponding data type according to the identification information in the header of the target data packet; when the data type is the target type, the identification information is successfully verified, and the target layer corresponding to the target data packet is determined, where the target layer is any one of multiple protocol layers; the target data packet is parsed in the target layer to obtain protocol data and the corresponding timestamp.

[0080] In an alternative embodiment, the master device 210 is further configured to determine whether the current second time of the master device 210 is less than the set time in the timestamp; when the second time is less than the set time, the protocol data is forwarded to the corresponding slave device 220 through the target layer.

[0081] In an alternative embodiment, the master device 210 is further configured to determine the forwarding range and forwarding form according to the forwarding requirements through the target layer, where the forwarding range includes one or more channel groups, and each channel group includes one or more slave devices 220, and the forwarding form includes unicast form or broadcast form; based on the forwarding range and forwarding form, the protocol data is forwarded to the corresponding slave device 220 through the target layer.

[0082] In an alternative embodiment, the slave device 220 is further configured to parse the received protocol data based on the target layer to obtain the protocol type and synchronization time of the synchronization event; determine whether the preparation duration corresponding to the protocol type is less than the interval duration, where the interval duration is the time period between the current first time of the slave device 220 determined based on the timer and the synchronization time; when the preparation duration is less than the interval duration, preparation is performed based on the protocol type, and the protocol type of the synchronization event is executed at the synchronization time.

[0083] It should be noted that the master device 210 can be Bluetooth communication-connected to one or more slave devices 220 to form a Piconet (referring to a micro network composed of various electrical appliances equipped with Bluetooth units within a small range, that is, Bluetooth modules embedded in various electrical appliances supporting Bluetooth technology). During the synchronization process, any one of the slave devices 220 triggered by the user among the multiple slave devices 220 can generate and send the corresponding target data packet, and only the other slave devices 220 need to execute the corresponding synchronization event according to the received protocol data, so as to achieve the synchronization process among the multiple slave devices 220.

[0084] Please refer to Figure 3 , Figure 3 which is a schematic flowchart of a Bluetooth synchronization method provided by an embodiment of the present application. The method may include steps S310-S330.

[0085] Step S310: The slave device generates a target data packet according to a synchronization event and sends the target data packet to the master device for the master device to forward protocol data based on the target data packet.

[0086] Among them, the header of the target data packet has identification information of the data type, and the identification information is information for the master device to which the slave device is communicatively connected to determine whether to forward.

[0087] Step S320: The master device receives the target data packet sent from the slave device; when the identification information is successfully verified, the target data packet is parsed to obtain protocol data and the timestamp corresponding to the protocol data; based on the timestamp, the protocol data is forwarded to the corresponding slave device.

[0088] Step S330: The slave device executes a synchronization event according to the received protocol data.

[0089] In Figure 3 the illustrated embodiment, by identifying the data type of the data packet of the synchronization event through the slave device, a corresponding target data packet can be generated. By verifying the identification information of the target data packet through the master device, the corresponding data type can be obtained, and based on the data type and the timestamp, the protocol data is forwarded to achieve event synchronization among multiple slave devices.

[0090] Please refer to Figure 4 , Figure 4 which is a schematic flowchart of a Bluetooth synchronization method applied to a slave device provided by an embodiment of the present application. The method may include steps S410 - S430.

[0091] Step S410: Generate a target data packet according to a synchronization event.

[0092] Among them, the header of the target data packet has identification information of the data type, and the identification information is information for the master device to which the slave device is communicatively connected to determine whether to forward. When a certain slave device has a synchronization requirement, a corresponding target data packet can be generated according to the synchronization event to be synchronized, and the information of the data type is marked in the header of the target data packet.

[0093] Exemplarily, the synchronization event may be an event of synchronously playing a certain prompt sound, multi - device synchronous playback, microphone synchronous switching control, etc. in various different situations.

[0094] Step S420: Send the target data packet to the master device for the master device to forward protocol data based on the target data packet.

[0095] Among them, the slave device can directly transmit the target data packet through the original Bluetooth link for normal Bluetooth communication with the master device for the master device to process based on the target data packet and forward the protocol data.

[0096] Step S430, execute a synchronization event according to the received protocol data.

[0097] Among them, the slave device receives the protocol data forwarded by the master device according to the target data packet, and executes the corresponding synchronization event according to the protocol data.

[0098] In Figure 4 In the illustrated embodiment, the slave device can directly send the synchronized data packet over the original Bluetooth link between the slave device and the master device, and receive the protocol data, without the need to separately set up a private link to send and receive the data packet and the protocol data, thereby effectively reducing the bandwidth occupied during the event synchronization of Bluetooth communication, reducing the overhead load of Bluetooth communication, and also improving the efficiency and accuracy when multiple slave devices perform event synchronization, so that Bluetooth communication can be used normally during event synchronization.

[0099] Optionally, please refer to Figure 5 , Figure 5 which is a detailed flowchart of step S410 provided by an embodiment of the present application. Step S410 may further include steps S4101-S4103.

[0100] Step S4101, determine the protocol data of the synchronization event in the target layer.

[0101] Among them, in order to improve the generality during Bluetooth synchronization, the target layer for processing data in the slave device can be any one of multiple different types of protocol layers, such as any one of multiple types of protocol layers such as the control layer, the host protocol layer, and the application layer of the software, that is, any one of multiple protocol layers such as the controller layer, the host layer, or the APP layer that can implement data processing or forwarding. There is no restriction on the implemented protocol layer, and the user can select a protocol layer with less bandwidth occupation for processing according to the actual situation and their own needs, which can be applicable to Bluetooth devices of multiple different types, models, and Bluetooth protocols. Since events have different situations and different synchronization events have different protocols, therefore, in multiple types of target layers of the slave device, the protocol data corresponding to the current synchronization event can be determined as the payload part of the data packet, so that the slave device can perform corresponding operations and processing according to the protocol data.

[0102] Step S4102, put the corresponding timestamp into the protocol data to generate an initial data packet.

[0103] Among them, the timestamp is the time information corresponding to the unified clock source of the master device and the slave device. Different target layers can determine different unified clock sources based on aspects such as efficiency, synchronization accuracy, and application universality. Optionally, the master device and the slave device can use the same unified clock source to implement a unified timing system. Exemplarily, when the target layer is the control layer or the host protocol layer, the unified clock source can be the Bluetooth clock of the master device. When the target layer is the application layer, the unified clock source can be the world clock. In some usage scenarios, the master device and the slave device can also use different clock sources respectively. To save space, short timestamps can be adopted to convert the time of the master device and the slave device into a unified clock moment to unify the time and obtain the time information corresponding to the unified clock source. By improving the time accuracy between devices, the accuracy of controlling multiple slave devices and synchronizing multiple slave device events can be improved. The slave device can obtain the timestamp and put the corresponding timestamp into the protocol data, and combine the execution protocol of the synchronization event with the forwarding time limit to obtain the initial data packet.

[0104] Optionally, when the unified clock source is the Bluetooth clock of the master device, the accuracy of the Bluetooth clock of the master device can be set to 0.5 us.

[0105] Step S4103, set identification information in the header of the initial data packet according to the data type of the initial data packet to obtain the target data packet.

[0106] Among them, the data packet of the synchronization event can be set to the ECHO (reply) type. Therefore, the slave device can identify the identification information of the ECHO type in the header of the initial data packet in the target layer to obtain the target data packet with identification information that can represent the synchronization event.

[0107] Optionally, the identification information can be various information such as the number or code of the ECHO data type.

[0108] In Figure 5 the shown embodiment, through the identification of the data type by the slave device, the target data packet can be directly transmitted on the original Bluetooth link between the slave device and the master device without setting a separate private link for transmission, which is beneficial for the master device to correspondingly parse and process the target data packet and will not have an adverse impact on the processing of other data normally transmitted in Bluetooth communication.

[0109] Optionally, please refer to Figure 6 , Figure 6 which is a detailed process schematic diagram of a step S430 provided by an embodiment of the present application. Step S430 may further include steps S4301-S4303.

[0110] Step S4301: Parse the received protocol data based on the target layer to obtain the protocol type of the synchronization event and the synchronization time.

[0111] Among them, when the slave device receives the forwarded protocol data, it can parse the protocol data in the corresponding target layer to obtain the protocol type when executing the synchronization event and the synchronization time when executing, that is, Action Type and Action Time.

[0112] Optionally, the protocol data may also include the data corresponding to the protocol type, that is, Action Date. For example, when playing a prompt tone, the Action Date may include relevant information such as the number of the played prompt tone.

[0113] Step S4302: Determine whether the preparation duration corresponding to the protocol type is less than the interval duration.

[0114] Among them, the interval duration is the time period between the current first time of the slave device determined based on the timer and the synchronization time. Since the slave device needs to perform corresponding preparation processing according to the specific situation of the protocol before executing the protocol, the slave device can compare the preparation duration before executing the protocol type with the interval duration to determine whether there is enough time to execute the protocol type.

[0115] Step S4303: When the preparation duration is less than the interval duration, perform preparation based on the protocol type and execute the protocol type of the synchronization event at the synchronization time.

[0116] Among them, if the preparation duration is less than the interval duration, it means that there is enough time for preparation between the current time and the synchronization time. Then the slave device can perform preparation according to the protocol type and distribute it to the corresponding module (a certain APP, the protocol of the host, or a certain module of the controller) to execute the corresponding protocol type at the synchronization time, so as to achieve the synchronous execution processing of the synchronization event.

[0117] Exemplarily, when the protocol type is to play a prompt tone, within the preparation duration, in the database of the prompt tone, the corresponding prompt tone can be searched according to the number of the prompt tone to synchronously play the prompt tone at the synchronization time.

[0118] Optionally, when the preparation duration is greater than the interval duration, it means that there is not enough time for preparation between the current time and the synchronization event. In order to reduce the situation where the synchronization event is delayed in execution, the slave device can abandon the execution processing of the synchronization event to avoid adverse situations such as inconsistent audio played among multiple slave devices.

[0119] At Figure 6In the illustrated embodiment, it is possible to determine whether to execute a synchronization event according to time, effectively reducing the situation where the synchronization event is delayed in processing.

[0120] Please refer to Figure 7 , Figure 7 which is a schematic flowchart of a Bluetooth method applied to a master device provided by an embodiment of the present application. The method may include steps S510 - S530.

[0121] Step S510, receive a target data packet sent from a slave device.

[0122] Among them, the master device can receive the target data packet sent from the slave device. The header of the target data packet has identification information of the data type for the master device to determine whether to forward according to the identification information.

[0123] Optionally, when the master device receives the target data packet, the data is received through the original Bluetooth link between the master device and the slave device.

[0124] Step S520, when the identification information verification is successful, parse the target data packet to obtain protocol data and a time stamp corresponding to the protocol data.

[0125] Among them, the master device can verify according to the data type represented in the identification information to verify whether the target data packet is data of a synchronization event or audio data normally transmitted during Bluetooth communication. When the verification is successful, it indicates that the target data packet is related data of a synchronization event, and the master device can parse the target data packet to obtain the corresponding protocol data and time stamp.

[0126] Step S530, forward the protocol data to the corresponding slave device based on the time stamp.

[0127] Among them, in order to improve the real - time performance and effectiveness during forwarding, the master device can make a judgment according to the time stamp to forward the protocol data accordingly.

[0128] In Figure 7 the illustrated embodiment, it is possible to quickly parse and forward - process the target data packet according to the identification information in the target data packet. When receiving the target data packet and forwarding the protocol data, it is possible to directly receive and forward through the original Bluetooth link between the slave device and the master device, without separately setting up a private link to receive and forward the data packet and the protocol data, effectively reducing the bandwidth occupied during the event synchronization of Bluetooth communication, reducing the overhead load of Bluetooth communication, and also being able to improve the efficiency and accuracy of forwarding when multiple slave devices respond to a synchronization request, so that Bluetooth communication can be used normally during event synchronization.

[0129] Optionally, please refer to Figure 8 ,Figure 8 This is a detailed process schematic diagram of step S520 provided by an embodiment of the present application. Steps S5201 - S5203 may also be included in step S520.

[0130] Step S5201: Determine the corresponding data type according to the identification information in the header of the target data packet.

[0131] Among them, after receiving the target data packet, the master device can directly determine the data type of the target data packet according to the identification information in the header of the data packet.

[0132] Step S5202: When the data type is the target type, the identification information is verified successfully, and the target layer corresponding to the target data packet is determined.

[0133] Among them, the target type may be the data type of ECHO. When the master device checks that the data type is the same as the target type, the identification information is verified successfully, indicating that the target data packet is related data of a synchronization event. The master device can determine the target layer corresponding to the template data packet to process the target data packet. The target layer can be any one of multiple different types of protocol layers, such as any one of a control layer, a host protocol layer, an application layer of software, etc., that is, any one of multiple protocol layers such as the controller layer, the host layer, or the APP layer that can implement data processing or forwarding.

[0134] Optionally, in order to improve the data processing efficiency, the target layer in the master device can be unified with the target layer in the slave device. For example, when the slave device generates a target data packet in the control layer, the master device also processes the target data packet in the control layer, etc., so as to uniformly process data using the same protocol layer in multiple Bluetooth devices.

[0135] Step S5203: Parse the target data packet in the target layer to obtain protocol data and the corresponding timestamp.

[0136] Among them, in the target layer, the master device only needs to parse the target data packet to obtain the protocol data and timestamp corresponding to the synchronization event, without processing the specific protocol content of the protocol data therein.

[0137] In Figure 8In the illustrated embodiment, it is possible to directly determine whether the target data packet is related to a synchronization event based on the identification information, and effectively process it in the corresponding target layer, enabling the target data packet to be distinguished from other data during normal Bluetooth communication and not adversely affecting the processing of other data transmitted normally in Bluetooth communication. This realizes directly processing the synchronization event on the original Bluetooth link between the slave device and the master device, without the need to set up a separate private link for transmission, improving the efficiency and accuracy of the master device in correspondingly parsing and processing the target data packet.

[0138] Optionally, please refer to Figure 9 , Figure 9 which is a detailed flowchart of step S530 provided by an embodiment of the present application. Step S530 may further include steps S5301 - S5302.

[0139] Step S5301, determine whether the current second time of the master device is less than the set time in the time stamp.

[0140] Among them, the time stamp can limit the relevant time period for forwarding processing and can be set as the set time point at the end of execution, that is, Timeout. The master device can compare the current second time with the set time to determine whether the current time is out of time, thereby improving the real-time performance and effectiveness during forwarding.

[0141] Step S5302, when the second time is less than the set time, forward the protocol data to the corresponding slave device through the target layer.

[0142] Among them, when the second time is less than the set time, it indicates that the current second time is before the set time at the end of execution, and the forwarding operation is not out of time, and the forwarding process can be carried out in the corresponding target layer.

[0143] Optionally, when the second time is greater than the set time, it indicates that the current second time is outside the set time at the end of execution, and the forwarding operation is out of time. In order to reduce the problem of synchronization delay caused by delayed forwarding due to unstable Bluetooth communication and other situations, in the case of timeout, the master device can stop the forwarding process.

[0144] In Figure 9 the illustrated embodiment, by judging the time node of forwarding, it is possible to perform forwarding processing within an effective time period to ensure the real-time performance and effectiveness of forwarding and reduce the delay situation during Bluetooth synchronization.

[0145] Optionally, please refer to Figure 10 , Figure 10 which is a detailed flowchart of step S5302 provided by an embodiment of the present application. Step S5302 may further include steps S53021 - S53022.

[0146] Step S53021: Determine the forwarding scope and forwarding form according to the forwarding requirements through the target layer.

[0147] Among them, the forwarding scope may include one or more channel groups, each channel group includes one or more slave devices, and the forwarding form includes unicast form or broadcast form.

[0148] Optionally, the channel group may be various different channel groups such as CIG (Connected Isochronous Groups, logical transport channel group) or BIG (Broadcast Isochronous Groups, periodic broadcast channel group), and one channel group may include one or more slave devices. For example, the forwarding scope may be to select all slave devices in a certain BIG group, and the forwarding form may be to forward in the form of broadcast.

[0149] Step S53022: Forward the protocol data to the corresponding slave device through the target layer based on the forwarding scope and forwarding form.

[0150] Among them, the target layer may select the slave devices in the corresponding channel group as the receiving targets according to the forwarding scope and forwarding form, and forward the protocol data in unicast or broadcast mode.

[0151] Optionally, when the target layer is the control layer, the control layer may also determine the channel group connected to the master device and forward the protocol data to the output queue corresponding to the channel group through the control layer. The protocol data can be directly forwarded to the output queue of the Bluetooth link corresponding to the channel group, so as to be able to notify the members of the channel group as soon as possible, and quickly forward the protocol data to the slave devices in the channel group, which can improve the efficiency during forwarding.

[0152] Optionally, when the target layer is the host protocol layer, the host protocol layer may obtain the corresponding forwarding requirements according to the target data packet or the instructions in the master device to determine the corresponding forwarding scope and forwarding form, so as to forward the protocol data to the corresponding slave device.

[0153] Optionally, when the target layer is the application layer of software, the application layer can select different Bluetooth services for connecting to the master device through similar timing content, such as the data type and timeout time of ECHO contained in the protocol data. For example, it can select communication methods such as classic Bluetooth or the new generation of Bluetooth, and can also select services of other protocols such as WiFi for forwarding timing synchronization. A time server can be used for unified timing services during forwarding, such as the world clock. The application layer can see more connections and services, and can process and forward data more widely and flexibly. Moreover, the application layer of software includes but is not limited to the above content, and may also be a protocol layer of a certain intermediate custom level. The application layer can include different protocol layers corresponding to different types of software that can implement data processing and forwarding, so that different manufacturers and users can use a variety of application software to achieve synchronization functions on various types of terminals.

[0154] In Figure 10 the illustrated embodiment, it is possible to perform corresponding forwarding according to the type of the protocol layer and the actual situation or user requirements in the slave device or the master device, effectively optimizing the effect during forwarding.

[0155] The embodiment of the present application also provides a computer-readable storage medium. Computer program instructions are stored in the readable storage medium. When the computer program instructions are read and run by a processor, the steps in any one of the Bluetooth synchronization methods provided in this embodiment are executed.

[0156] In summary, the embodiment of the present application provides a Bluetooth synchronization method, system, Bluetooth device, and computer-readable storage medium. By identifying and parsing the data packets of synchronization events, it is possible to perform synchronization processing in the original Bluetooth link without separately setting up a private link for synchronization processing, thereby effectively reducing the bandwidth occupied during event synchronization of Bluetooth communication, reducing the overhead load of Bluetooth communication, and improving the efficiency and accuracy during event synchronization, so that Bluetooth communication can be normally used during event synchronization.

[0157] In several embodiments provided by the present application, it should be understood that the disclosed device can also be implemented in other ways. The device embodiments described above are merely illustrative. For example, the block diagrams in the drawings show the possible architectures, functions, and operations of the devices according to multiple embodiments of the present application. In this regard, each block in the block diagram can represent a module, a program segment, or a part of code, and the module, program segment, or part of code contains one or more executable instructions for implementing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the blocks may occur in a different order from that marked in the drawings. For example, two consecutive blocks can actually be executed substantially in parallel, and they can sometimes be executed in the reverse order, depending on the functions involved. It should also be noted that each block in the block diagram, as well as the combination of block diagrams, can be implemented by a dedicated hardware-based system for performing the specified functions or actions, or can be implemented by a combination of dedicated hardware and computer instructions.

[0158] In addition, in each embodiment of the present application, the functional modules can be integrated together to form an independent part, or each module can exist alone, or two or more modules can be integrated to form an independent part.

[0159] If the described functions are implemented in the form of software functional modules and sold or used as an independent product, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, in essence, or the part that contributes to the prior art, or a part of this technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions for causing a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in various embodiments of the present application. The aforementioned storage medium includes: USB flash drives, mobile hard disks, read-only memories (ROMs), random access memories (RAMs), magnetic disks, or optical discs, etc., which can store program codes.

[0160] The above description is only for the embodiments of the present application and is not intended to limit the protection scope of the present application. For those skilled in the art, the present application can have various changes and modifications. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principle of the present application shall be included in the protection scope of the present application. It should be noted that similar reference numerals and letters represent similar items in the following drawings. Therefore, once an item is defined in one drawing, it does not need to be further defined and explained in subsequent drawings.

[0161] As described above, this is only the specific implementation manner of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art within the technical scope disclosed by the present application can easily think of changes or substitutions, which should all be covered within the protection scope of the present application.

[0162] It should be noted that in this text, relational terms such as "first" and "second" are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any actual relationship or order between these entities or operations. Moreover, the term "comprising", "including" or any other variant thereof is intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements not only includes those elements, but also includes other elements not expressly listed, or further includes elements inherent to such process, method, article or device. Without further limitations, the elements defined by the statement "including..." do not exclude the existence of additional identical elements in the process, method, article or device including the said elements.

Claims

1. A Bluetooth synchronization method, characterized in that, applied to a slave device, the method includes: generating a target data packet according to a synchronization event, wherein the header of the target data packet has identification information of a data type, and the identification information is information for a master device to which the slave device is communicatively connected to determine whether to forward; sending the target data packet to the master device for the master device to forward protocol data based on the target data packet; executing the synchronization event according to the received protocol data; wherein, generating the target data packet according to the synchronization event includes: determining the protocol data of the synchronization event in a target layer, where the target layer is any one of multiple protocol layers; putting a corresponding timestamp into the protocol data to generate an initial data packet, where the timestamp is time information corresponding to a unified clock source of the master device and the slave device; setting identification information in the header of the initial data packet according to the data type of the initial data packet to identify that the initial data packet is of the data type corresponding to the synchronization event, and generating the target data packet corresponding to the synchronization event.

2. The method according to claim 1, characterized in that, executing the synchronization event according to the received protocol data includes: parsing the received protocol data based on the target layer to obtain a protocol type and a synchronization time of the synchronization event; determining whether a preparation duration corresponding to the protocol type is less than an interval duration, where the interval duration is a time period between a current first time of the slave device determined based on a timer and the synchronization time; when the preparation duration is less than the interval duration, preparing based on the protocol type and executing the protocol type of the synchronization event at the synchronization time.

3. A Bluetooth synchronization method, characterized in that, applied to a master device, the method includes: receiving a target data packet sent from a slave device, wherein the header of the target data packet has identification information of a data type, and the identification information is information for the master device to determine whether to forward; when the identification information is verified successfully, parsing the target data packet to obtain protocol data and a timestamp corresponding to the protocol data; forwarding the protocol data to the corresponding slave device based on the timestamp; wherein, when the identification information is verified successfully, parsing the target data packet to obtain protocol data and a timestamp corresponding to the protocol data includes: determining a corresponding data type according to the identification information in the header of the target data packet; when the data type is a target type, the identification information is verified successfully, indicating that the target data packet is a data packet of a synchronization event, determining a target layer corresponding to the target data packet, where the target layer is any one of multiple protocol layers; parsing the target data packet in the target layer to obtain the protocol data and the corresponding timestamp.

4. The method according to claim 3, characterized in that, Forwarding the protocol data to the corresponding slave device based on the timestamp includes: Determining whether the current second time of the master device is less than the set time in the timestamp; When the second time is less than the set time, forwarding the protocol data to the corresponding slave device through the target layer.

5. The method according to claim 4, wherein, Forwarding the protocol data to the corresponding slave device through the target layer includes: Determining a forwarding range and a forwarding form according to forwarding requirements through the target layer, wherein the forwarding range includes one or more channel groups, each channel group includes one or more of the slave devices, and the forwarding form includes a unicast form or a broadcast form; Forwarding the protocol data to the corresponding slave device based on the forwarding range and the forwarding form through the target layer.

6. A Bluetooth synchronization method, wherein, The method includes: Generating a target data packet by a slave device according to a synchronization event, and sending the target data packet to a master device for the master device to forward protocol data based on the target data packet; wherein, the header of the target data packet has identification information of a data type, and the identification information is information for the master device to which the slave device is communicatively connected to determine whether to forward; wherein, generating a target data packet by a slave device according to a synchronization event includes: determining the protocol data of the synchronization event in a target layer, where the target layer is any one of multiple protocol layers; putting a corresponding timestamp into the protocol data to generate an initial data packet, where the timestamp is time information corresponding to a unified clock source of the master device and the slave device; setting identification information in the header of the initial data packet according to the data type of the initial data packet to identify that the initial data packet is the data type corresponding to the synchronization event, and generating the target data packet corresponding to the synchronization event; Receiving, by the master device, the target data packet sent by the slave device; when the identification information is successfully verified, parsing the target data packet to obtain protocol data and the timestamp corresponding to the protocol data; forwarding the protocol data to the corresponding slave device based on the timestamp; wherein, receiving, by the master device, the target data packet sent by the slave device and, when the identification information is successfully verified, parsing the target data packet to obtain protocol data and the timestamp corresponding to the protocol data includes: determining the corresponding data type according to the identification information in the header of the target data packet; when the data type is a target type, the identification information is successfully verified, indicating that the target data packet is a data packet of the synchronization event, determining the target layer corresponding to the target data packet, where the target layer is any one of multiple protocol layers; parsing the target data packet in the target layer to obtain the protocol data and the corresponding timestamp; Executing the synchronization event according to the received protocol data by the slave device.

7. A Bluetooth synchronization system, wherein, The system includes: a slave device and a master device, and the slave device and the master device are communicatively connected based on a Bluetooth link; The slave device is configured to generate a target data packet according to a synchronization event; send the target data packet to the master device for the master device to forward protocol data based on the target data packet; wherein, the header of the target data packet has identification information of a data type, and the identification information is information for the master device to which the slave device is communicatively connected to determine whether to forward; Specifically, the slave device is configured to: determine the protocol data of the synchronization event in a target layer, where the target layer is any one of multiple protocol layers; put a corresponding timestamp into the protocol data to generate an initial data packet, where the timestamp is time information corresponding to a unified clock source of the master device and the slave device; set identification information in the header of the initial data packet according to the data type of the initial data packet to identify that the initial data packet is of the data type corresponding to the synchronization event, and generate the target data packet corresponding to the synchronization event; The master device is configured to receive the target data packet sent from the slave device; when the identification information is successfully verified, parse the target data packet to obtain the protocol data and the timestamp corresponding to the protocol data; and forward the protocol data to the corresponding slave device based on the timestamp; Specifically, the master device is configured to: determine the corresponding data type according to the identification information in the header of the target data packet; when the data type is a target type, the identification information is successfully verified, indicating that the target data packet is a data packet of the synchronization event, and determine the target layer corresponding to the target data packet, where the target layer is any one of multiple protocol layers; parse the target data packet in the target layer to obtain the protocol data and the corresponding timestamp; The slave device is further configured to execute the synchronization event according to the received protocol data.

8. A Bluetooth device, characterized in that, the Bluetooth device includes a memory and a processor, and program instructions are stored in the memory, and when the processor runs the program instructions, the steps in the method according to any one of claims 1-5 are executed.

9. A computer-readable storage medium, characterized in that, computer program instructions are stored in the readable storage medium, and when the computer program instructions are run by a processor, the steps in the method according to any one of claims 1-5 are executed.

Images