CN118119005A

CN118119005A - Data synchronization method and related product

Info

Publication number: CN118119005A
Application number: CN202211533160.3A
Authority: CN
Inventors: 张友坤
Original assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Current assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Priority date: 2022-11-30
Filing date: 2022-11-30
Publication date: 2024-05-31

Abstract

The embodiment of the application discloses a data synchronization method and related products, wherein the method comprises the following steps: determining whether a target time slot overlaps with a communication time slot of a terminal device, wherein the target time slot is a time slot for carrying out data synchronization between the first Bluetooth device and a second Bluetooth device, and the communication time slot is a time slot for the terminal device to send communication data to the first Bluetooth device; and when the target time slot and the communication period are not overlapped, performing data synchronization with the second Bluetooth device in the target time slot. The application can solve the problems of the prior art that the communication load and the equipment function of the terminal equipment and the earphone end are increased.

Description

Data synchronization method and related product

Technical Field

The application relates to the technical field of communication, in particular to a data synchronization method and related products.

Background

With the development of Bluetooth (Bluetooth) technology, wireless audio sharing is increasingly used. For example, audio sharing between a truly wireless stereo (True Wireless Stereo, TWS) and a terminal device (e.g., a cell phone), etc. The TWS enables at least two Bluetooth devices (such as Bluetooth headphones) to completely abandon the connecting wire, and stereo sound of the terminal device can be played by adopting Bluetooth connection.

Two bluetooth headsets are split in the TWS into a master headset (TWS MASTER) and a slave headset (TWS slave). The master earphone refers to an earphone capable of receiving audio data transmitted from the terminal device and forwarding the audio data to the slave earphone. The slave earphone refers to an earphone capable of receiving or listening to audio data transmitted by the terminal device. The TWS enables the audio data transmitted by the terminal equipment to be synchronously played in the master earphone and the slave earphone, and further achieves the stereo effect.

However, in practice it is found that: the earphone end does not know the specific time slot of the terminal device for transmitting the audio data, and in order to ensure that the transmitted data is not lost, the earphone end usually opens the receiver to receive the audio data transmitted by the terminal device when the earphone end is idle. If data interaction is needed between the master earphone and the slave earphone, the master earphone sends data to the slave earphone in a sending time slot of the terminal device, and the terminal device also sends audio data to the master earphone at the moment. In this case, the main earphone may lose the audio data, and the terminal device needs to transmit the audio data to the main earphone again, which may cause the terminal device to have a certain retransmission rate. In practical application, the retransmission rate is relatively high, which requires that the retransmission times of the terminal device are relatively high, so that the communication load and the device power consumption of the terminal device and the earphone end can be increased.

Disclosure of Invention

The embodiment of the application discloses a data synchronization method and related products, which can solve the problems of increasing the communication load and the equipment function of terminal equipment and earphone ends in the prior art.

In a first aspect, the present application provides a data synchronization method, the method comprising:

Determining whether a target time slot overlaps with a communication time slot of a terminal device, wherein the target time slot is a time slot for carrying out data synchronization between the first Bluetooth device and a second Bluetooth device, and the communication time slot is a time slot for the terminal device to send communication data to the first Bluetooth device;

and when the target time slot and the communication period are not overlapped, performing data synchronization with the second Bluetooth device in the target time slot.

In a second aspect, the present application provides a data synchronization apparatus, the apparatus comprising:

a determining module, configured to determine whether a target time slot overlaps with a communication period of a terminal device, where the target time slot is a period for performing data synchronization between the first bluetooth device and a second bluetooth device, and the communication period is a period for the terminal device to send communication data to the first bluetooth device;

and the synchronization module is used for carrying out data synchronization with the second Bluetooth device in the target time slot when the target time slot and the communication time period are not overlapped.

In a third aspect, the present application provides a bluetooth device, the terminal device comprising: a memory and a processor coupled with the memory; the memory is used for storing instructions, and the processor is used for executing the instructions; wherein the processor, when executing the instructions, implements a method as provided in the first aspect above.

In a fourth aspect, the present application provides a computer readable storage medium storing a computer program which when executed by a processor implements the method as provided in the first aspect above.

In a fifth aspect, the present application provides a computer program product comprising a computer program which, when executed by a processor, implements the method as provided in the first aspect above.

Compared with the prior art, the application has at least the following beneficial effects:

In the embodiment of the application, a first Bluetooth device determines whether a target time slot overlaps with a communication time slot of a terminal device, wherein the target time slot is a time slot for carrying out data synchronization between the first Bluetooth device and a second Bluetooth device, and the communication time slot is a time slot for the terminal device to send communication data to the first Bluetooth device; and when the target time slot and the communication period are not overlapped, performing data synchronization with the second Bluetooth device in the target time slot. It can be seen that the present application can perform data synchronization with the second bluetooth device in the target time slot when it is determined that the communication period of the target time slot and the terminal device does not overlap. Therefore, the data synchronization between the Bluetooth devices and the data transmission of the terminal devices are staggered in the time domain, so that the retransmission rate of the data between the Bluetooth devices and the retransmission rate of the terminal device side are reduced, and the respective communication load and the respective device power consumption of the Bluetooth devices and the terminal devices are further reduced. The problems that communication load and equipment power consumption of terminal equipment and earphone ends are increased in the prior art are solved.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are needed in the embodiments will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.

Fig. 1 is a schematic diagram of a device slot communication according to an embodiment of the present application.

Fig. 2 is a schematic diagram of an antenna in a bluetooth headset according to an embodiment of the present application.

Fig. 3 is a schematic diagram illustrating an improvement of bluetooth headset communication according to an embodiment of the present application.

Fig. 4 (a) to fig. 4 (d) are schematic diagrams of several bluetooth data transmission provided in the embodiments of the present application.

Fig. 5 (a) and fig. 5 (b) are schematic diagrams of another two bluetooth data transmissions according to an embodiment of the present application.

Fig. 6 (a) to 6 (c) are schematic diagrams of formats of several frame data according to embodiments of the present application.

Fig. 7 (a) and fig. 7 (b) are schematic diagrams of another two bluetooth data transmissions according to an embodiment of the present application.

Fig. 8 is a schematic structural diagram of a data synchronization system according to an embodiment of the present application.

Fig. 9 is a flow chart of a data synchronization method according to an embodiment of the present application.

Fig. 10 is a flowchart of another data synchronization method according to an embodiment of the present application.

Fig. 11 is a schematic diagram of another device slot communication provided in an embodiment of the present application.

Fig. 12 is a flowchart of another data synchronization method according to an embodiment of the present application.

Fig. 13 is a schematic diagram of a data transmission collision according to an embodiment of the present application.

Fig. 14 is a schematic diagram of a collision occurrence cycle adjustment according to an embodiment of the present application.

Fig. 15 is a schematic structural diagram of a data synchronization device according to an embodiment of the present application.

Fig. 16 is a schematic structural diagram of another data synchronization device according to an embodiment of the present application.

Fig. 17 is a schematic structural diagram of a bluetooth device according to an embodiment of the present application.

Detailed Description

The following description of the embodiments of the present application will be made clearly and completely with reference to the accompanying drawings, in which it is apparent that the embodiments described are only some embodiments of the present application, but not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the application without making any inventive effort, are intended to be within the scope of the application.

It should be noted that the terms "comprising" and "having" and any variations thereof in the embodiments of the present application and the accompanying drawings are intended to cover non-exclusive inclusions. For example, a process, method, system, article, or apparatus that comprises a list of steps or elements is not limited to only those listed steps or elements but may include other steps or elements not listed or inherent to such process, method, article, or apparatus.

The applicant has also found in the course of proposing the present application that: in the TWS, no matter the master earphone or the slave earphone, the earphone end does not know in which time slot the terminal device sends data, and typically, the receiver is turned on to synchronize the frame data of the terminal device when idle. If data interaction is needed between the master earphone and the slave earphone, the physical layer of Bluetooth is occupied, and the master earphone transmits synchronous data to the slave earphone in a transmission time slot of the terminal equipment. At this time, the terminal device also transmits frame data to the master earphone, so that the master earphone and the slave earphone lose the frame data. In order to ensure complete transmission of data, the terminal equipment needs to retransmit the frame data, and specifically, the frame data can be retransmitted after data synchronization is completed between the master earphone and the slave earphone. Thus, during operation of the TWS headset, the terminal device may have a certain retransmission rate.

For example, please refer to fig. 1, which is a schematic diagram illustrating a device slot communication according to an embodiment of the present application. Fig. 1 specifically shows a schematic diagram of slot communication of each of the master earphone, the slave earphone and the terminal device, and only 15 slots are shown as an example in the figure, but the application is not limited thereto. Where TX in the figure represents the transmit time slot and RX represents the receive time slot. The audio in the terminal event is shown to mean that the terminal device needs to send audio data to the master earphone in the current time slot. Synchronization in the events of the illustrated earphone refers to that data synchronization needs to be performed between the master earphone and the slave earphone in the current time slot. In practical applications, there is also data interaction between the master earphone and the slave earphone, such as data of synchronous playing progress, residual electric quantity, playing volume, etc. In general, communication between master and slave headphones is initiated by the master headphone, and the master headphone needs to send synchronization data in its own sending time slot when performing data synchronization, so that the slave headphone can only receive the synchronization data. If the terminal device also transmits frame data at this time, data transmission collision may be caused, so that the master earphone may lose the frame data transmitted by the terminal device, and the master earphone may not reply to the terminal device with an acknowledgement message, where the acknowledgement message is used to indicate that the master earphone has received the frame data transmitted by the terminal device. For example, in fig. 1, the terminal device and the master earphone in the 4 th time slot and the 14 th time slot both send data at the same time, and at this time, data transmission collision occurs, which results in data loss. It can be seen that the need for communication between the master and slave headphones is a fundamental cause of reducing the retransmission rate of data transmissions between the master headphones and the terminal device.

And experiments prove that when various TWS earphones are tested in a shielding room with clean frequency spectrum to play audio data, the retransmission rate of terminal equipment (such as a mobile phone) is shown in the following table 1:

TABLE 1

Mobile phone model	TWS earphone model	Data encoding method	Retransmission rate
				OPPO Find X3 pro	Airpods pro	AAC	8.90％
OPPO Find X3 pro	Airpods pro	SBC	9.80％
				OPPO Find X3 pro	OPPO Enco x2	AAC	15.60％
OPPO Find X3 pro	OPPO Enco x2	SBC	12.30％
				OPPO Find X3 pro	OPPO Enco x2	LHDC	13.30％
OPPO Find X3 pro	OPPO Enco Air2 pro	AAC	8.10％
				OPPO Find X3 pro	OPPO Enco Air2 pro	SBC	8.50％

As can be seen from table 1 above, even in the case where the communication environment and the air interface quality are good, the retransmission rate due to the data transmission collision is still relatively high. The high retransmission rate means that the number of retransmission times of the main device when transmitting useful data is more, so that the communication load of the self radio frequency system can be increased, the power consumption of the device is increased, more transmission time slots are occupied in the time domain, and the data transmission time length is prolonged.

It will be appreciated that since the terminal device or bluetooth device (e.g., a handset) is typically integrated on the same chip in ISM band with both wireless fidelity (WIRELESS FIDELITY, WIFI) and bluetooth, the same radio frequency system is shared. WiiFi and bluetooth are operated by time division when simultaneously started, and the priority of bluetooth is higher than the priority of WiFi. When the Bluetooth has data transmission, the physical layer of the radio frequency system is occupied, and after the Bluetooth data transmission is finished, the physical layer (i.e. the communication link) is returned to the WiFi. When there is data retransmission in bluetooth, more time slots are additionally occupied, so that the service time of WiFi is shorter, and the delay and throughput of WiFi become worse, so that the performance of WiFi is deteriorated. Due to the poor performance of the WiFi, the system cannot acquire corresponding communication data from the internet in time, and thus, a problem of blocking of services such as online audio and video occurs.

In order to solve the above problems, the present application provides a data synchronization method and related products. First, some bluetooth-related embodiments of the present application are described.

Bluetooth communication

Bluetooth technology provides that each pair of devices must have a master device and a slave device to communicate when bluetooth communication is performed between them. In bluetooth communication, the master device needs to find the peripheral slave devices, initiate pairing, and establish a communication link with the slave devices. After successful chaining, data can be received and transmitted between the master device and the slave device. A master device may communicate bluetooth with a plurality of slave devices at the same time, the number of slave devices being not limited, for example, typically 7. Each bluetooth communication enabled device (may be referred to as a bluetooth device for short) may switch roles between a master device and a slave device, typically operating in a slave device mode, waiting for communication links to be established with other master devices. When the service is actually needed, the device can be switched to the main device to initiate the call to other devices. When each bluetooth device initiates a call with the master device, it needs to know the pairing information of the other device, such as bluetooth address, pairing password, personal identification number (Personal identification number, PIN), etc. After pairing is completed, a call can be directly initiated to the opposite device.

When the master device initiates a call, it needs to search for slave devices (such as other bluetooth devices with bluetooth function turned on) whose periphery is in the range that can be searched. After the slave device is found, the master device may pair with the slave device, for example, input a PIN code of the slave device. After pairing is completed, the slave device records trust information of the master device, such as Bluetooth address and pairing password of the master device. Accordingly, the master device may initiate a call to the slave device. It will be appreciated that there is no need to re-pair the paired bluetooth devices at the next call. Also, the paired slave device may initiate a communication link with the master device, but a bluetooth module serving as a data communication will not typically initiate a call.

After successful link establishment, the Bluetooth devices at the master end and the slave end can carry out bidirectional data communication/transmission. In a communication state, both the master and slave devices may initiate a disconnect request to disconnect the bluetooth link between them.

In bluetooth-based data transmission applications, one-to-one serial data communication is one of the common applications. Each bluetooth device is pre-configured with pairing information between two bluetooth devices (a master device and a slave device) before leaving the factory, specifically, for example, the master device is pre-configured with pairing information such as a bluetooth address, a pairing password, a PIN code and the like of the slave device. When the master and slave devices are powered on, the communication link between the master and slave devices can be automatically established, and data transmission is performed through the serial port, so that no extra peripheral circuit intervention is needed.

In one-to-one serial data communication, there may be two operating states of the slave device. The first is a silent state, in which case the slave device communicates with the designated master device and cannot be found by other bluetooth devices. The second is the development state, in which case the slave device can communicate with the designated master device and can be searched by other bluetooth devices to establish a communication link between them.

It should be noted that, the bluetooth device of the present application refers to a device having bluetooth function, such as a mobile phone, a personal notebook, a watch, an earphone, or other terminal devices having bluetooth function. For convenience of description, the present application describes a bluetooth device and a terminal device separately, which are different from each other. Herein, the bluetooth device according to the present application refers to a device having a bluetooth function and supporting data synchronization with other bluetooth devices, such as a bluetooth audio playing device, etc. The bluetooth audio playback device includes, but is not limited to, a bluetooth headset, bluetooth speaker, or other bluetooth playback device, for example. The terminal device of the present application refers to a device with bluetooth communication function, which may include, but is not limited to, a smart phone (such as an Android phone, an IOS phone, etc.), a personal computer, a tablet computer, a palm computer, an electronic reader, a Mobile internet device (MID, mobile INTERNET DEVICES), a wearable smart device, etc. The following description of the present application uses bluetooth devices as bluetooth headphones for illustration of related content, but the present application is not limited thereto.

(II) TWS

The TWS divides the Bluetooth headset into a master headset and a slave headset. The roles of the two earphones in each pair of Bluetooth earphones can be freely switched between the master earphone and the slave earphone, and the negotiation of the roles can be determined according to the running state of the equipment. For example, the initial role setting of the bluetooth headset may be determined according to the parity of its bluetooth address, such as the default odd address being the master headset and the even address being the slave headset. For another example, the Bluetooth headset may also be determined according to an Input/Output (IO) state of the headset, for example, when the IO state is used for indicating that a level value of the IO interface is a high level by default, the Bluetooth headset is a main headset; in contrast, the bluetooth headset is a slave headset or the like.

In practical application, the application does not limit the respective functions of the master earphone and the slave earphone. For example, the main earphone has the following functions: support communication with a terminal device; supporting management of state information of the self, such as connection state, pairing state, playing state, pause state or other state information of the self equipment and other equipment; the decision right of the Bluetooth protocol and the system is provided, such as the master earphone decides which protocol to use for communication; input of microphone (mic) signals in voice calls, and the like.

The slave earphone has the following functions: receiving information forwarded by a main earphone; or monitor the communication link between the master earphone and the terminal device to obtain some necessary information, such as audio data sent by the terminal device, etc. In order to obtain the experience effect of binaural stereo, the slave earphone is usually operated to passively receive information forwarded by the master earphone, or monitor a communication link between the terminal device and the master earphone, and not communicate with the terminal device. But the slave earphone can communicate with the master earphone and require role switching according to own needs.

In the audio playing process, the master earphone and the slave earphone need to interact with some data (such as the current playing progress, the information of the buffer status, the volume adjustment, the noise reduction status and the like) so as to realize the data synchronization of the master earphone and the slave earphone. Therefore, a private communication protocol is established between the master earphone and the slave earphone, and the Bluetooth radio frequency system is shared on the physical layer of the protocol to carry out data transmission. In practical applications, because the structure of the bluetooth headset is relatively small, a set of radio frequency systems (such as antennas) is usually designed, so that the wireless communication between the TWS headset (i.e. the bluetooth headset) and the wireless communication between the main headset and the terminal device need to share the physical layer, i.e. share the communication link or channel, in a time division manner, such as a time division duplex (Time Division Duplexing, TDD) operation mode.

(III) antenna

An antenna is a device for transmitting or receiving electromagnetic waves, and can be divided into a transmitting antenna and a receiving antenna according to functions, and can be also referred to as a transmitter and a receiver, respectively. The function of the transmitting antenna is to effectively convert the energy of the high-frequency current of the transmitter (or the guided wave in the waveguide system) into electromagnetic wave energy in space, and the function of the receiving antenna is opposite to that of the transmitting antenna, which is not described herein. Thus, the antenna may actually be a transducer. The TWS earphone can transmit data in space by utilizing an antenna and adopting a radio wave mode so as to realize wireless transmission of the data.

It is understood that the antenna needs to have a certain length in order to radiate electromagnetic waves into the air. For example, a single dipole antenna is used, the length of which is approximately one quarter of the operating wavelength. Bluetooth communication is adopted in TWS headphones, the working frequency Band of the Bluetooth communication is the Industrial SCIENTIFIC MEDICAL Band (ISM) frequency Band, and the antenna length is about 30 mm. The setting position of the antenna in the bluetooth headset is not limited. For example, please refer to fig. 2, which shows a schematic diagram of an antenna in a bluetooth headset. As in fig. 2, the gray area represents the antenna 201 in the bluetooth headset. As shown, the antenna may cover the outer area 202 of the earphone pole, and the length of the antenna is not limited, and may be set according to practical requirements. Typically, the length of the antenna needs to be less than the length of the earphone pole.

Communication improvement of Bluetooth earphone

In classical bluetooth protocols, audio data are transmitted point-to-point, and before new generation bluetooth Audio (LE Audio) is introduced, the terminal device supports a headset connection. While there are various communication modes between the bluetooth headset and the terminal device, please refer to fig. 3, which is a schematic diagram illustrating an improvement of the bluetooth headset communication according to an embodiment of the present application. Fig. 3 shows a development iteration scheme of the fifth generation bluetooth headset communication, and the following description is provided.

In the first generation scheme, the terminal equipment and the main earphone establish a classical Bluetooth link, and the terminal equipment sends the audio data of the left and right channels to the main earphone together. After the master earphone receives one frame/packet of data, the audio data is completely forwarded to the slave earphone, and finally the master earphone and the slave earphone respectively play the audio data of the left channel and the right channel correspondingly.

In the second generation scheme, after the pairing of the TWS earphone is completed, the terminal equipment and the master earphone directly establish a Bluetooth communication link, and after the master earphone receives the audio data sent by the terminal equipment, the master earphone forwards the data of one channel in the audio data to the slave earphone through a private communication protocol. Optionally, when the terminal device is a specific device, for example, a device supporting the system platform of the high-pass 845 and above versions, the master earphone may convert the single link into double links through the private communication protocol, and at this time, each communication link is established between the master earphone and the terminal device and between the master earphone and the terminal device. Then, the terminal device can individually transmit the left and right audio data corresponding to each other to the master and slave headphones, respectively. Finally, the master earphone and the slave earphone respectively play the audio data of the left channel and the right channel correspondingly.

In the third generation scheme, it belongs to the transition scheme. On the basis of the first and second generation schemes, the master earphone may forward half of the audio data to the slave earphone, e.g. half of the left channel audio data, etc.

In the fourth generation scheme, after the pairing of the TWS earphone is completed, the terminal equipment and the master earphone establish a Bluetooth communication link, and share the communication password to the slave earphone. The slave earphone uses the communication password to monitor the audio data transmitted between the terminal device and the master earphone. Since the slave earphone cannot communicate with the terminal device during monitoring, retransmission and error correction of data cannot be performed, and there is a possibility of losing data. If the slave earphone loses part of the data in the process of monitoring, the master earphone can be requested to forward the part of the data through a private communication protocol. Finally, the master earphone and the slave earphone respectively play the audio data of the left channel and the right channel correspondingly.

In the fifth generation of scheme, with development of bluetooth protocol, a communication link can be established between the terminal device and the master earphone and between the terminal device and the master earphone respectively, and audio data of respective left and right channels can be separately transmitted through bluetooth low energy (Bluetooth Low Energy, BLE). Accordingly, the master earphone and the slave earphone can receive and play the audio data of the left and right channels corresponding to each other.

Currently, the main stream of bluetooth communication schemes on the market is the fourth generation scheme, and a mode of monitoring from a headset is adopted. The process of transmitting audio data by the terminal device to the master earphone is discontinuous in the time domain. In general, a frame of data sent by the terminal device has longer playing duration corresponding to the earphone end. The terminal device can intermittently transmit data to the main earphone through bluetooth. The working mode of bluetooth is TDD mode, in which the uplink transmission and downlink transmission both adopt the same frequency band, so that the time slot requirement of master-slave two-end equipment transmission is implemented in bluetooth protocol, specifically, for example, the terminal equipment can be used as master equipment to transmit in even time slot, and the bluetooth earphone can be used as slave equipment to transmit in odd time slot.

Fig. 4 (a) to fig. 4 (d) are schematic diagrams of several bluetooth data transmission provided in the embodiments of the present application. Fig. 4 (a) specifically shows a schematic diagram of bluetooth data transmission by a master device and a slave device. As in fig. 4 (a), the master and the slave communicate using a bluetooth protocol (i.e., TDD mode of operation) that provides for the master to start transmitting data in even slots and the slave to start transmitting data in odd slots. K in the figure represents the kth slot, k+1 represents the kth+1 slot, k+8 represents the kth+8 slot, k is an even number. The sending duration or the sending end time of each frame of data will be determined according to the size of each frame of data, for example, four time slots are occupied by the master device for sending the third frame of data in the figure. The duration of each time slot is not limited, and may be set according to the actual requirements of the system, for example, 625 microseconds (us), etc.

Fig. 4 (b) specifically shows a schematic diagram of bluetooth data transmission by one master device and two slave devices. As shown in fig. 4 (b), for convenience of understanding, data reception and transmission for each device are shown to be split into two paths. Wherein the number on each frame of data indicates the target slave device to which the frame of data is to be transmitted, for example, the number 1 on the master device in the figure indicates that the frame of data is transmitted to the slave device 1. Accordingly, the number of frame data on the master device is 2, representing the transmission of that frame data to the slave device 2.

Fig. 4 (c) specifically shows a schematic diagram of bluetooth data transmission by three possible bluetooth devices. As shown in fig. 4 (c), the working frequencies of the bluetooth devices in each time slot are different, but the working frequencies used in transmitting the same frame data are the same, for example, in the data transmission displays of the second path and the third path, the first frame data occupies 3 time slots and 5 time slots respectively, but the working frequencies used in transmitting the frame data are the same. In the figure, f (k) represents the operating frequency used by the kth slot, f (k+1) represents the operating frequency used by the kth+1 slot, and. In practical applications, the bluetooth device may be a master device or a slave device, which is not limited by the present application.

Fig. 4 (d) specifically shows a schematic diagram of the operating frequency when the master device and the slave device perform bluetooth data transmission. As shown in fig. 4 (d), the operating frequency used when the master device and the slave device transmit the same frame data is the same for the same frame data, that is, the transmission and reception frequencies of the master device and the slave device for the same frame data are the same. The white boxes in the drawing represent received frame data, and the black boxes represent transmitted frame data.

In practical applications, the channel of bluetooth communication is unreliable, and interference and multipath effects easily occur, resulting in loss of the number of receiving ends. In order to ensure the reliability of data transmission, the bluetooth protocol specifies error correction and retransmission schemes to ensure that the receiving end does not lose data. For example, schemes have forward error correction (Forward Error Correction, FEC) at 1/3 rate, FEC at 2/3 rate, automatic Repeat-reQuest (ARQ) for data, etc. When bluetooth data is transmitted, after the slave device correctly receives the data, it needs to reply an acknowledgement message (Acknoledgment, ACK) to the master device, where the acknowledgement message is used to feed back that the master device successfully receives the current data. Otherwise, if the slave device loses data due to interference or the like during receiving, a Negative-acknowledgement (NACK) message is replied to the master device, and the NACK message is used for feeding back that the slave device fails to receive the current data. The master device automatically retransmits the current data to the slave device when receiving the negative acknowledgement message or not receiving any acknowledgement message until receiving the acknowledgement message of the slave device.

For example, please refer to fig. 5 (a) and fig. 5 (b) for another two kinds of bluetooth data transmission according to an embodiment of the present application. As shown in fig. 5 (a), after the master device sends a frame of data to the slave device, the slave device checks the check code carried in the frame of data. After the verification is successful, actively replying an ACK message to the master device to wait for the master device to transmit the next frame of data. Wherein, a white frame in fig. 5 (a) represents an ACK message and a black frame represents frame data. The application is not limited to specific embodiments of the check, and may include, for example, but not limited to, cyclic redundancy check (Cyclic Redundancy Check, CRC), integrity check (MESSAGE INTEGRITY CHECK, MIC), header error check (Header Error Check, HEC), and the like.

In fig. 5 (b), the slave device actively replies a NACK message to the master device when the check fails. And when the master device receives the NACK message or does not receive any ACK message, the master device automatically retransmits the current frame data until the end of receiving the ACK message of the slave device. Fig. 5 (b) illustrates 4 retransmission frame data, but is not limited thereto; the gray boxes in the figure represent NACK messages, the white boxes represent ACK messages, and the black boxes represent frame data.

Fig. 6 (a) to 6 (c) are schematic diagrams illustrating formats of several frame data according to embodiments of the present application. Fig. 6 (a) specifically shows a schematic diagram of a possible format of frame data. As in fig. 6 (a), the format of the frame data includes the following fields: an access code (access code), a header field (haeder), a guard interval (guard), a synchronization sequence (sync), a data payload (ENHANCED DATA RATE payload), and a payload trailer (trailer). The number of bits/bit occupied by each field in the drawing is not limited, and can be set according to actual requirements. For example, the access code may occupy 68 or 72 bits (bits), which means that the receiving end uses it to identify the received frame data. The header field includes information for link control, such as bluetooth address, PIN code, etc. of the receiving end. The guard interval is used to represent the time between the end of the header field to the head of the sync sequence, which may fluctuate over 4.75 us-5.25 us. The synchronization sequence is used for data synchronization. The data payload is used to carry the specific content of the frame data. The load tail is the tail of the data load, typically 0.

Fig. 6 (b) specifically shows a schematic diagram of the format of an access code. As in fig. 6 (b), the format of the access code includes the following subfields: a preamble (preamble) and a synchronization word (sync word), and optionally a tail section (trailer). The number of bits/bit number occupied by each subfield is not limited, and can be set according to actual requirements. For example, the preamble may occupy 4 bits, playing a role in synchronization; the syncword is a 64bit codeword and the tail is a 4bit additional syncword.

Fig. 6 (c) specifically shows a format diagram of a header field. As in fig. 6 (c), the header field includes the following subfields: logical transport address (lt_addr), data type (type), flow control bit (flow), acknowledgement indication (ARQN), sequence number (SEQN), and Header Error Check (HEC). The number of bits/bit number occupied by each subfield is not limited, and can be set according to actual requirements. For example, the logical transport address occupies 3 bits and is used to represent the address of the slave device that the master device needs to transmit. The data type indicates the type of frame data. The flow control bit is used for flow control during Asynchronous Connectionless Link (ACL) logic transfer. The acknowledgement indication is used to indicate/tell the correct transmission of the frame data, and may be a valid acknowledgement of an ACK message or an invalid acknowledgement of a NACK message. The sequence number is the sequence number of the frame data, and a sequence code pattern is provided for arranging the order of the frame data. The header error check is a check code consisting of 8bit words, and plays a role in data check.

Taking the slave device as a TWS earphone as an example, in the monitoring process of the TWS earphone, the master and slave earphones can reply an ACK message to the terminal device after receiving correct frame data, so as to wait for the terminal device to send the next frame data. Therefore, the receiving time slot and the transmitting time slot of the slave earphone are required to be consistent with those of the master earphone, so that frame data transmitted by the terminal equipment can not be missed, and the data can not be lost to the greatest extent.

For example, please refer to fig. 7 (a) and fig. 7 (b) for another two kinds of bluetooth data transmission according to an embodiment of the present application. Fig. 7 (a) specifically illustrates a schematic diagram of a possible timeslot communication between TWS headphones. As shown in fig. 7 (a), after the master and slave headphones are opened, a bluetooth link between them is established. And then the master earphone establishes a communication link with the terminal equipment, and the master earphone shares the communication password between the master earphone and the terminal equipment to the slave earphone through a private communication protocol. The slave earphone enters a monitoring mode according to the password, and monitors all frame data transmitted between the master earphone and the terminal equipment. And the receiving time slot of the slave earphone needs to be consistent with the receiving time slot of the master earphone, so that the data loss of the slave earphone is avoided. After the slave earphone finishes the verification of the frame data, a first ACK message is returned to the master earphone in the current time slot for receiving the frame data, and the first ACK message is used for indicating that the slave earphone completely receives the current frame data. Accordingly, the master earphone replies a second ACK message to the terminal device in the next time slot, wherein the second frame data is used for indicating that the master earphone completely receives the current frame data. The terminal device, when adjusting the transmission time slot, does not know the transmission time slot of the terminal device from the headset, which would turn on the receiver for detection at the beginning of each odd time slot. If the slave earphone detects the access code of the frame data, the receiver is utilized to continuously receive the frame data until the data reception is finished. Otherwise, if the slave earphone does not detect the access code within the preset specified time, the receiver is turned off to save the functions of the device. Wherein RX in the drawing represents a reception slot in which a receiver is turned on to receive frame data; TX denotes a reception slot in which a transmitter is turned on to transmit frame data.

Fig. 7 (b) specifically shows a data transmission schematic of a master earphone. As shown in fig. 7 (b), the master earphone reserves some time in the receiving slot of each frame of data to receive the ACK message replied from the slave earphone, and the reserved time is shown as a dashed line box in the figure. Accordingly, after receiving the ACK message replied from the headset, the master headset replies the ACK message to the terminal device in the next time slot, where the ACK message is shown as a white box in the illustration. The black boxes in the figure represent frame data.

Next, a system embodiment to which the present application relates is described. Fig. 8 is a schematic structural diagram of a data synchronization system according to an embodiment of the present application. The system as shown in fig. 8 includes: a first bluetooth device 100, a second bluetooth device 200, and a terminal device 300. The network communication can be carried out between any two devices in the system according to actual requirements. The first bluetooth device 100 and the second bluetooth device 200 in the present application refer to two bluetooth devices that are different from each other, and the bluetooth devices refer to devices that have bluetooth functions and support data synchronization with other bluetooth devices, which may include, for example, but not limited to, devices such as a bluetooth headset, a bluetooth speaker, or other bluetooth playback devices, etc. The first bluetooth device 100 and the second bluetooth device 200 are illustrated as bluetooth headphones, but are not limited thereto.

The terminal device 300 of the present application is also bluetooth capable and may include, but is not limited to, devices such as smart phones (e.g., android phones, IOS phones, etc.), personal computers, tablet computers, palmtop computers, electronic readers, audio/video players, mobile internet devices (MID, mobile INTERNET DEVICES), wearable smart devices, etc.

Next, an embodiment of the method according to the present application will be described. Fig. 9 is a flowchart of a data synchronization method according to an embodiment of the present application. The method as shown in fig. 9 is applied to the first bluetooth device 100, and includes the following implementation steps:

s901, determining whether a target time slot overlaps with a communication time slot of a terminal device, wherein the target time slot is a time slot for carrying out data synchronization between the first Bluetooth device and the second Bluetooth device, and the communication time slot is a time slot for the terminal device to send communication data to the first Bluetooth device.

The target time slot of the present application refers to a time slot or period used when the first bluetooth device 100 performs data synchronization with the second bluetooth device 200. The communication period of the present application refers to a period used for data transmission between the terminal device 300 and the first bluetooth device 100, and specifically may be a period used for the terminal device 300 to transmit communication data to the first bluetooth device 100, etc., which is not limited by the present application. The present application is not limited to the specific embodiment of step S901, and two specific embodiments are given below by way of example.

In one possible embodiment, the present application may determine whether there is an overlap in the time domain (i.e., instant) between the target time slot and the communication period by detecting communication data transmitted by the terminal device in the first sub-slot of the target time slot. Specifically, when the communication data sent by the terminal device is detected in the first sub-slot of the target slot, the present application can determine that the target slot overlaps with the communication period, and the first bluetooth device 100 normally continues to receive the communication data sent by the terminal device 300 in the target slot. On the contrary, when the communication data sent by the terminal device is not detected in the first sub-slot of the target slot, the present application can determine that the target slot does not overlap with the communication period, and continue to execute step S902.

In another possible embodiment, the present application may determine whether there is a temporal overlap of the target time slot and the communication period by detecting whether the target time slot and/or the communication period corresponds to being within the last target period of the collision occurrence period. Specifically, the present application may determine that there is an overlap between the target time slot and the communication period in the last target period in the collision occurrence period when it is detected that the target time slot and/or the communication period corresponds to the last target period in the collision occurrence period, in which the first bluetooth device 100 normally receives the communication data transmitted by the terminal device 300. On the contrary, when detecting that the target time slot and/or the communication period is not located in the last target period in the collision occurrence period, the present application can determine that there is no overlap between the target time slot and the communication period, and continue to execute step S902.

The collision occurrence period in the present application refers to a period in which a collision occurs between data transmission of the first bluetooth device 100 and data transmission of the terminal device 300. The target period may correspond to a data transmission period of the terminal device 300 or a data synchronization period between the first bluetooth device 100 and the second bluetooth device 200. The description of the two embodiments will be detailed below.

And S902, carrying out data synchronization with the second Bluetooth device in the target time slot when the target time slot and the communication period are not overlapped.

By implementing the embodiment of the application, when the communication time period of the target time slot and the terminal equipment is not overlapped, the data synchronization can be carried out with the second Bluetooth equipment in the target time slot. Therefore, the data synchronization between the Bluetooth devices and the data transmission of the terminal devices are staggered in the time domain, so that the retransmission rate of the data between the Bluetooth devices and the retransmission rate of the terminal device side are reduced, and the respective communication load and the respective device power consumption of the Bluetooth devices and the terminal devices are further reduced. The problems that communication load and equipment power consumption of terminal equipment and earphone ends are increased in the prior art are solved.

Fig. 10 is a flowchart of another data synchronization method according to an embodiment of the present application. The method as described in fig. 10 is applied to the first bluetooth device 100, and the method includes the following implementation steps:

S1001, detecting communication data sent by the terminal device 300 in a first sub-slot of a target slot, where the target slot is a slot in which data synchronization is performed between the first bluetooth device 100 and the second bluetooth device 200, the target slot includes the first sub-slot and a second sub-slot, and the first sub-slot is located before the second sub-slot.

The target time slot of the present application refers to a time slot used when the first bluetooth device 100 and the second bluetooth device 200 perform data synchronization, and the time slot may be an even time slot or an odd time slot, which may be set according to actual requirements. Typically, the target time slot is specified in the bluetooth protocol as an even number of time slots. The first bluetooth device 100 and the second bluetooth device 200 are two different bluetooth devices, and the types of the two bluetooth devices are not limited. That is, they may be the same class of bluetooth devices, such as bluetooth headsets; but may be different kinds of bluetooth devices, and the present application is not limited thereto. The description of the first bluetooth device 100 and the second bluetooth device 200 may correspond to the description of the bluetooth devices in the foregoing embodiments, and will not be repeated herein.

The communication data of the present application refers to data transmitted in communication between the terminal device 300 and the bluetooth device, and the type of the data is not limited. For example, when the bluetooth device is a bluetooth headset, the communication data is typically audio data. The sub-slot of the present application is a sub-slot in the target slot, and the duration and position of the sub-slot (specifically, the first sub-slot or the second sub-slot) are not limited by the present application. For example, the duration of each of the first sub-slot and the second sub-slot is typically half of the period of the target slot, specifically the first sub-slot is the first half of the period of the target slot, and the second sub-slot is the second half of the period of the target slot.

When the first Bluetooth device 100 is a master device, the second Bluetooth device 200 is a slave device; conversely, when the first bluetooth device 100 is a slave device, the second bluetooth device 200 is a master device, such as a master headset and a slave headset in a TWS headset. A specific embodiment of step S1001 is described below.

In one possible implementation, when the first bluetooth device 100 is the master device, the master device may turn on the receiver during the first sub-slot, and use the receiver to detect the communication data sent by the terminal device 300. When communication data transmitted by the terminal device 300 is detected, normal reception of the communication data can be continued using the receiver. After receiving the communication data, a corresponding ACK message may be replied to the terminal device 300 in the next slot to wait for the terminal device 300 to transmit the next communication data. The ACK message here is used to indicate/inform the master device that the current communication data has been successfully received.

In another possible implementation, when the first bluetooth device 100 is a slave device, if the slave device may also establish bluetooth link communication with the terminal device 300, the slave device may also turn on the receiver in the first sub-slot, and use the receiver to detect the communication data sent by the terminal device 300. The details not described or not described in this embodiment may be referred to the related description in the first embodiment, which is not repeated here.

In another possible implementation manner, when the first bluetooth device 100 is a slave device, if the slave device uses a listening manner to obtain the communication data sent by the terminal device 300, the slave device turns on a listener (e.g. a receiver) in a first sub-slot, and uses the listener to detect (i.e. listen to) the communication data sent by the terminal device 300, and specifically, may use the listener and a communication password between the terminal device 300 and the master device to listen to the communication data sent by the terminal device 300. The details not described or not described in this embodiment may be referred to the related description in the first embodiment, which is not repeated here.

In another possible embodiment, the present application may determine whether the start time of data synchronization between bluetooth devices is within the first sub-slot, whether the first bluetooth device 100 is a master device or a slave device. If so, determining that the communication data sent by the terminal device 300 is detected in the first sub-time slot; otherwise, it may be determined that communication data transmitted by the terminal device 300 is not detected in the first sub-slot, indicating that the first sub-slot has passed the start time of data synchronization, and the first bluetooth device 100 does not synchronize to the access code of the terminal device 300, at which time the terminal device 300 does not retransmit communication data in the slot.

It can be appreciated that in some scenarios where periodic data synchronization is required, for example, in an audio switching scenario with a fixed duration, the present application may determine the start time of each data synchronization in advance, and then detect the communication data sent by the terminal device 300 in the first sub-slot according to the above embodiment, thereby being beneficial to improving the intelligence and convenience of data synchronization.

S1002, when the communication data sent by the terminal device 300 is not detected in the first sub-slot, performing data synchronization with the second bluetooth device 200 in the second sub-slot.

The present application detects whether there is communication data from the terminal device 300 in the first sub-slot of the target slot, and if so, continues to normally receive the communication data sent by the terminal device 300. If not, the first bluetooth device 100 starts data synchronization with the second bluetooth device 200 from the second sub-slot, and the end time of the data synchronization is determined according to the size of the synchronization data between the two bluetooth devices. For example, the synchronization data is smaller, and the data synchronization can be completed in the second sub-time slot; if the synchronous data is larger, the time length of three time slots is required to be occupied to finish the synchronization, and the data synchronization can be finished in the third time slot after the target time slot in this case. That is, the present application needs to perform data synchronization with the second bluetooth device 200 in the second sub-slot.

The specific embodiment of step S1002 is not limited by the present application, and two possible embodiments thereof are exemplarily described below.

In a possible embodiment, when the first bluetooth device 100 is the master device, the master device may turn on the transmitter in the second sub-slot to send the synchronization data to the second bluetooth device 200 when the communication data sent by the terminal device 300 is not detected in the first sub-slot.

In another possible embodiment, when the first bluetooth device 100 is a slave device, the slave device may turn on the receiver in the second sub-slot when the slave device does not detect the communication data sent by the terminal device 300 in the first sub-slot, and receive the synchronization data sent by the second bluetooth device 200 (i.e., the master device), so that the slave device receives the synchronization data in time when the master device sends the synchronization data.

In an alternative embodiment, after the master device has transmitted the synchronization data, the master device and the slave device repeatedly perform the steps of S1001 to S1002 of the present application in the next target slot. For example, the master-slave device may start detecting communication data transmitted by the terminal device 300 at the next even slot. If the communication data sent by the terminal device 300 is not detected in the first sub-slot of the even slot, the slave device starts to send the synchronization data to the master device in the second sub-slot of the even slot, and completes one-time data synchronization. If communication data transmitted by the terminal device 300 is detected in the first sub-slot of the even slot, the communication data transmitted by the terminal device 300 is normally received. The content not described in this embodiment may be referred to the related description in the foregoing embodiments, which is not repeated here.

In practical applications, the communication data and the synchronization data according to the present application are both transmitted in a frame format, and may also be referred to as frame data. The synchronization data of the present application refers to data that needs to be synchronized between the first bluetooth device 100 and the second bluetooth device 200, and may include, but is not limited to, information such as a play progress, a remaining power, a play volume, a set noise reduction level, or other information to be synchronized, etc.

For example, please refer to fig. 11, which is a schematic diagram illustrating another device slot communication according to an embodiment of the present application. As in fig. 11, the description will be made taking a bluetooth device as an example of TWS headphones (master headphone and slave headphone). The time slots of the communication between the TWS headphones are staggered by half a time slot from the main time slot (i.e. the target time slot) of the communication of the terminal device 300, the start point of the communication between the TWS headphones not being at the beginning of the target time slot but at the middle of the target time slot, i.e. half a period of the target time slot. That is, the target time slot of the terminal device 300 includes a first sub-time slot and a second sub-time slot, and the time lengths of the two sub-time slots each occupy a half period of the target time slot. The TWS earpiece does not detect frame data (i.e., an access code in the frame data) transmitted by the terminal device 300 in the first sub-slot of each receiving slot (illustrated as RX), indicating that the terminal device 300 will not transmit frame data in the receiving slot, and the slave earpiece turns on the receiver again at the middle of the receiving slot (i.e., the second sub-slot) to synchronize the synchronization data transmitted by the master earpiece. If the slave earphone does not detect the synchronous data (namely the access code in the synchronous data) of the master earphone, the receiver is closed; otherwise, if the access code of the main earphone is detected, the synchronous data is normally received, and an ACK message is returned to the main earphone when the receiving is finished so as to inform the main earphone of finishing the receiving of the synchronous data. For example, it is illustrated that the master earphone does not detect frame data from the terminal device in the first sub-slot of the 8 th slot, and then transmits synchronization data to the slave earphone in the second sub-slot of the 8 th slot. Accordingly, if the slave earphone does not monitor the frame data from the terminal device in the first sub-time slot of the 8 th time slot, the slave earphone receives the synchronous data sent by the master earphone in the second sub-time slot of the 8 th time slot. The audio in the illustrated terminal event means that the terminal device 300 needs to send audio data to the master earphone in the current time slot. Synchronization in the illustrated earpiece event refers to the need for data synchronization between the TWS earpiece in the current time slot.

By implementing the embodiment of the present application, the first bluetooth device 100 detects communication data sent by the terminal device 300 in a first sub-slot of a target slot, where the target slot is a slot in which data synchronization is performed between the first bluetooth device 100 and the second bluetooth device 200, the target slot includes the first sub-slot and a second sub-slot, and the first sub-slot is located before the second sub-slot; and when the communication data sent by the terminal device 300 is not detected in the first sub-time slot, the data synchronization is performed with the second bluetooth device 200 in the second sub-time slot. Therefore, under the condition of not increasing hardware cost, the application fully utilizes the characteristics of the private communication protocol between the Bluetooth devices and the Bluetooth communication protocol of the terminal device 300 to fuse so as to synchronize data in the second sub-time slot of the target time slot when the communication data from the terminal device 300 is not detected in the first sub-time slot of the target time slot. In this way, the data synchronization between the bluetooth devices and the data transmission of the terminal device 300 are staggered in the time domain, so that the retransmission rate of the data between the bluetooth devices and the retransmission rate of the terminal device 300 side are reduced, and the respective communication load and device power consumption of the bluetooth devices and the terminal device 300 are further reduced. The problems of the prior art that the communication load and the device power consumption of the terminal device 300 and the earphone end are increased are solved.

Fig. 12 is a flowchart of a data synchronization method according to an embodiment of the present application. The method as shown in fig. 12 is applied to the first bluetooth device 100, and includes the following implementation steps:

S1201, acquiring a data transmission period of the terminal device 300.

The data transmission period of the present application refers to a period in which the terminal device 300 transmits one frame of data. The method of acquiring the data transmission period is not limited, and the data transmission period is acquired actively and regularly through a timer, for example, and is acquired from the terminal device 300 through a network, etc.

S1202, at least one interrupt processing period is acquired, wherein the interrupt processing period is a period required by the first Bluetooth device 100 when processing a preset interrupt event, and the preset interrupt event corresponding to each interrupt processing period is different.

The interrupt processing cycle of the present application refers to the user perceived time required for the first bluetooth device 100to process a preset interrupt event. The preset interrupt event is an interrupt reporting event set by a system or a user in a user-defined manner, for example, the user generates an interrupt reporting event through a touch key, specifically, for example, a volume adjustment event, a progress adjustment event, a noise reduction adjustment event, and the like. Wherein each preset interrupt event corresponds to an interrupt processing period, and different preset interrupt events correspond to different interrupt processing periods. That is, the preset interrupt event corresponds to the interrupt processing period one by one.

The application does not limit the number of interrupt processing cycles, and can be set according to actual requirements. The embodiment of the present application for acquiring the interrupt processing period is not limited either, and may be obtained from other devices (e.g., a server) via a network, or may be obtained by calculation from a series of experimental data, or may directly acquire a value configured in advance by the user from the system, or the like.

S1203 determines a data synchronization period between the first bluetooth device 100 and the second bluetooth device 200 according to the data transmission period and at least one interrupt processing period.

In a possible implementation manner, the application can calculate the data transmission period and each interrupt processing period according to a preset formula to obtain the data synchronization period between two bluetooth devices. The preset formula is an operation rule set by the system in a self-defining way, for example, summation according to preset weights and the like.

In another possible embodiment, the present application may select, from at least one interrupt processing period, an interrupt processing period in which a least common multiple with respect to a data transmission period reaches a maximum value, as the data synchronization period between two bluetooth devices.

Alternatively, the present application will perform data synchronization between the first bluetooth device 100 and the second bluetooth device 200 in accordance with the data synchronization period. For example, every interval of the data synchronization period, the first bluetooth device 100 needs to transmit synchronization data to the second bluetooth device 200 or receive synchronization data transmitted by the second bluetooth device 200. The receiving or transmitting of the synchronization data in this embodiment may be referred to the related description in the foregoing embodiment, and will not be repeated here.

And S1204, determining a conflict occurrence period according to the data transmission period and the data synchronization period, wherein the conflict occurrence period is a period in which a conflict occurs between the data transmission of the first Bluetooth device 100 and the data transmission of the terminal device 300, and the conflict occurrence period is larger than the data transmission period and the data synchronization period.

The collision occurrence period of the present application refers to a period in which a collision occurs when the first bluetooth device 100 and the terminal device 300 each perform data transmission. The collision occurrence period is calculated according to the data transmission period and the data synchronization period, and the specific embodiment of the calculation is not limited, for example, calculation according to a preset rule, etc. Typically, the collision occurrence period is the least common multiple between the data transmission period and the data synchronization period.

And S1205, performing data synchronization with the second Bluetooth device in the target time slot when the target time slot and/or the communication time slot are not correspondingly positioned in the last target period in the conflict occurrence period.

The target time slot of the present application refers to a time slot or period used when the first bluetooth device 100 performs data synchronization with the second bluetooth device 200. The communication period of the present application refers to a period used for data transmission between the terminal device 300 and the first bluetooth device 100, and specifically may be a period used for the terminal device 300 to transmit communication data to the first bluetooth device 100, etc., which is not limited by the present application. That is, the first bluetooth device 100 may perform data synchronization with the second bluetooth device 200 in a target time slot in which the first bluetooth device 100 performs data synchronization with the second bluetooth device 200, and/or when none of the communication periods in which the terminal device 300 transmits communication data to the first bluetooth device 100 is within the last target period in the collision occurrence period, that is, when there is no time-domain collision between the above data synchronization and the above transmission communication data.

In contrast, when the target time slot in which the first bluetooth device 100 performs data synchronization with the second bluetooth device 200 and/or when the communication period in which the terminal device 300 transmits communication data to the first bluetooth device 100 corresponds to the last target period in the collision occurrence period, that is, when the data synchronization and the transmission of communication data have a time-domain collision, the first bluetooth device 100 may normally receive communication data transmitted from the terminal device 300 in the target time slot, and data synchronization between bluetooth devices is not allowed.

And S1206, when the target time slot and/or the communication time period is correspondingly positioned in the last target period in the conflict occurrence period, the data synchronization period is adjusted, and the target period is the data transmission period or the data synchronization period.

When the target time slot and/or the communication period is located in the last target period of the collision occurrence period correspondingly, that is, when the terminal device needs to generate communication data to the first bluetooth device 100 in the last target period and/or the first bluetooth device 100 and the second bluetooth device 200 need to perform data synchronization in the last target period, the application can adjust the data synchronization period in the last target period of the collision occurrence period so as to adjust the data synchronization period between the bluetooth devices to another synchronization period, thereby reducing the probability of collision occurrence. The target period may be a data transmission period or a data synchronization period, typically a data synchronization period.

For example, please refer to fig. 13, which is a schematic diagram illustrating a data transmission collision according to an embodiment of the present application. As shown in fig. 12, the audio data transmitted between bluetooth devices is encoded by using advanced audio (Advanced Audio Coding, AAC), and the duration occupied by each time slot is 625us, for example, the audio sampling rate is 44.1KHz, and the duration of each frame of data is 23.22ms (i.e., the data transmission period of the terminal device 300 is 23.22ms, and 37.152 time slots are occupied), that is, the terminal device 300 updates the audio data to the bluetooth 325 device (such as a TWS headset) every 23.22 ms. The terminal device 300 transmits frame data to the bluetooth headset alternately in 36 and 38 slots. If the data synchronization period of communication between bluetooth headsets is 65ms (104 slots are occupied), then a collision or collision occurs between the respective data transmissions of the bluetooth headsets and the terminal device 300 at 325ms intervals (23.22×14=65×5), i.e., the collision occurrence period here is 325ms. In other words, the terminal device 300 collides with the bluetooth headset when transmitting data for the 14 th time. As shown in the figure, the dashed boxes represent the synchronization data transmitted between the bluetooth headsets, and the solid boxes represent the frame data transmitted between the terminal device 300 and the bluetooth headsets.

Fig. 14 is a schematic diagram of adjustment of a collision occurrence cycle according to an embodiment of the present application. In connection with the example shown in fig. 13, the present application may adjust the collision occurrence period within the last data transmission period of 325ms of the collision occurrence periods. In the experiment, it is found that if the data synchronization period between bluetooth headsets is 65ms (occupies 104 slots), the retransmission rate of the actually measured terminal device 300 is 7.1%; if the data synchronization period between the bluetooth headsets is 97.5ms (occupies 156 timeslots), the retransmission rate of the actually measured terminal device 300 is 5.3%; if the data synchronization period between bluetooth headsets is 130ms (occupies 208 timeslots), the retransmission rate of the terminal device 300 is 3.6%. Therefore, when the data synchronization period between the Bluetooth headsets is doubled, the retransmission rate is reduced by half, and the collision occurrence period shown in fig. 14 is also adjusted from 325ms to 650ms, which shows that the scheme achieves the effect of reducing the collision occurrence probability.

Based on the above embodiments, the following describes embodiments of the apparatus and device according to the present application. Fig. 15 is a schematic structural diagram of a data synchronization device according to an embodiment of the present application. The apparatus as shown in fig. 15 includes: a determination module 1501 and a synchronization module 1502. Wherein:

the determining module 1501 is configured to determine whether a target time slot overlaps with a communication period of a terminal device, where the target time slot is a period during which data synchronization is performed between the first bluetooth device and the second bluetooth device, and the communication period is a period during which the terminal device sends communication data to the first bluetooth device;

The synchronization module 1502 is configured to perform data synchronization with the second bluetooth device in the target time slot when there is no overlap between the target time slot and the communication period.

In some embodiments, the determining module 1501 is specifically configured to:

Detecting communication data sent by a terminal device in a first sub-time slot of the target time slot to determine whether the target time slot overlaps with the communication time period;

When the communication data sent by the terminal equipment is not detected in the first sub-time slot, determining that the target time slot is not overlapped with the communication time period; the target time slot comprises a first sub-time slot and a second sub-time slot, and the first sub-time slot is positioned before the second sub-time slot;

The synchronization module 1502 is specifically configured to perform data synchronization with the second bluetooth device in the second sub-slot.

In some embodiments, the determining module 1501 is specifically configured to:

in a first sub-time slot of a target time slot, detecting communication data sent by a terminal device through a receiver of the first Bluetooth device; or alternatively

Judging whether the starting time of the data synchronization is positioned in a first sub-time slot of a target time slot or not so as to detect communication data sent by terminal equipment;

When judging that the starting time of the data synchronization is positioned in the first sub-time slot, determining that the communication data sent by the terminal equipment is detected in the first sub-time slot; and when judging that the starting time of the data synchronization is not located in the first sub-time slot, determining that the communication data sent by the terminal equipment is not detected in the first sub-time slot.

In some embodiments, the synchronization module 1502 is specifically configured to:

receiving synchronous data sent by the second Bluetooth device in the second sub-time slot; or alternatively

And transmitting synchronous data to the second Bluetooth device in the second sub-time slot.

In some embodiments, the target time slot is an even time slot.

In some embodiments, the determining module 1501 is specifically configured to:

Detecting whether the target time slot and/or the communication time period is/are located in the last target period in the conflict occurrence period or not, so as to determine whether the target time slot is overlapped with the communication time period or not;

Wherein when the target time slot and/or the communication time period are not correspondingly positioned in the last target period in the conflict occurrence period, determining that the target time slot is not overlapped with the communication time period; the collision occurrence period is a period of collision between data transmission of the first Bluetooth device and data transmission of the terminal device, and the target period is a data transmission period of the terminal device or a data synchronization period between the first Bluetooth device and the second Bluetooth device.

In some embodiments, please refer to fig. 16, which is a schematic diagram illustrating another data synchronization apparatus according to an embodiment of the present application. The apparatus as shown in fig. 16 includes: a determination module 1501, a synchronization module 1502, an acquisition module 1503, and a processing module 1504. The description of detection module 1501 and synchronization module 1502 may correspond to the relevant description described above with reference to fig. 15. Wherein:

The processing module 1504 is configured to adjust the data synchronization period when the target time slot and/or the communication period is located in the last target period in the collision occurrence period.

In some embodiments, the detecting whether the target time slot and/or the communication period corresponds to being located before a last target period in a collision occurrence period,

The acquiring module 1503 is configured to acquire a data transmission period of the terminal device;

The obtaining module 1503 is further configured to obtain at least one interrupt processing period, where the interrupt processing period is a period required by the first bluetooth device when processing a preset interrupt event, and each interrupt processing period corresponds to a different preset interrupt event;

The processing module 1504 is configured to determine a data synchronization period between the first bluetooth device and the second bluetooth device according to the data transmission period and at least one interrupt processing period.

In some embodiments, the processing module 1504 is specifically configured to:

And selecting an interrupt processing period with the least common multiple reaching the maximum value from at least one interrupt processing period as the data synchronization period.

In some embodiments, the processing module 1504 is further to:

And determining the conflict occurrence period according to the data transmission period and the data synchronization period, wherein the conflict occurrence period is the least common multiple between the data transmission period and the data synchronization period.

In some embodiments, when the first bluetooth device is a master device, the second bluetooth device is a slave device; or when the first Bluetooth device is a slave device, the second Bluetooth device is a master device.

Fig. 17 is a schematic structural diagram of a bluetooth device according to an embodiment of the present application. The bluetooth device as shown in fig. 17 includes: a memory 1701 and a processor 1702 coupled to the memory 1701; the memory 1701 is configured to store instructions and the processor 1702 is configured to execute the instructions; wherein the processor 1702, when executing the instructions, performs the steps of:

In some embodiments, the determining whether there is overlap of the target time slot with the communication period of the terminal device includes:

Said synchronizing data with said second bluetooth device in said target time slot includes:

And carrying out data synchronization with the second Bluetooth device in the second sub-time slot.

In some embodiments, the detecting the communication data sent by the terminal device in the first sub-slot of the target slot includes:

In some embodiments, said synchronizing data with said second bluetooth device in said second sub-slot comprises:

In some embodiments, the target time slot is an even time slot.

In some embodiments, the processor 1702, when executing the instructions, is further configured to implement the steps of:

acquiring a data transmission period of the terminal equipment;

acquiring at least one interrupt processing period, wherein the interrupt processing period is a period required by the first Bluetooth equipment when processing a preset interrupt event, and the preset interrupt event corresponding to each interrupt processing period is different;

And determining a data synchronization period between the first Bluetooth device and the second Bluetooth device according to the data transmission period and at least one interrupt processing period.

In some embodiments, the determining a data synchronization period between the first bluetooth device and the second bluetooth device according to the data transmission period and at least one of the interrupt processing periods includes:

The embodiment of the application also discloses a computer readable storage medium, on which a computer program is stored, which when being executed by a processor, realizes all or part of the steps in the previous method embodiment.

The embodiments of the present application also disclose a computer program product having a computer program stored thereon, which, when executed by a processor, implements all or part of the steps of the previous method embodiments.

It should be appreciated that reference throughout this specification to "one embodiment" or "an embodiment" means that a particular feature, structure or characteristic described in connection with the embodiment is included in at least one embodiment of the present application. Thus, the appearances of the phrases "in one embodiment" or "in an embodiment" or "in a possible embodiment" in various places throughout this specification are not necessarily all referring to the same embodiment. Furthermore, the particular features, structures, or characteristics may be combined in any suitable manner in one or more embodiments. Those skilled in the art will also appreciate that the embodiments described in the specification are alternative embodiments and that the acts and modules referred to are not necessarily required for the present application.

In various embodiments of the present application, it should be understood that the sequence numbers of the foregoing processes do not imply that the execution sequences of the processes should be determined by the functions and internal logic of the processes, and should not be construed as limiting the implementation of the embodiments of the present application.

The units described above as separate components may or may not be physically separate, and components shown as units may or may not be physical units, may be located in one place, or may be distributed over a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the embodiment.

In addition, each functional unit in the embodiments of the present application may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit. The integrated units may be implemented in hardware or in software functional units.

The integrated units described above, if implemented in the form of software functional units and sold or used as stand-alone products, may be stored in a computer-accessible memory. Based on this understanding, the technical solution of the present application, or a part contributing to the prior art or all or part of the technical solution, may be embodied in the form of a software product stored in a memory, comprising several requests for a computer device (which may be a personal computer, a server or a network device, etc., in particular may be a processor in a computer device) to execute some or all of the steps of the above-mentioned method of the various embodiments of the present application.

Those of ordinary skill in the art will appreciate that all or part of the steps of the various methods of the above embodiments may be implemented by a program that instructs associated hardware, the program may be stored in a computer readable storage medium including Read-Only Memory (ROM), random access Memory (Random Access Memory, RAM), programmable Read-Only Memory (Programmable Read-Only Memory, PROM), erasable programmable Read-Only Memory (Erasable Programmable Read Only Memory, EPROM), one-time programmable Read-Only Memory (OTPROM), electrically erasable programmable Read-Only Memory (EEPROM), compact disc Read-Only Memory (Compact Disc Read-Only Memory, CD-ROM) or other optical disk Memory, magnetic disk Memory, tape Memory, or any other medium that can be used for carrying or storing data.

The foregoing has described in detail a data synchronization method and related products disclosed in the embodiments of the present application, and specific examples have been applied to illustrate the principles and embodiments of the present application, where the foregoing examples are provided to assist in understanding the method and core ideas of the present application; meanwhile, as those skilled in the art will have variations in the specific embodiments and application scope in accordance with the ideas of the present application, the present description should not be construed as limiting the application in view of the above.

Claims

1. A method of data synchronization, for use with a first bluetooth device, the method comprising:

2. The method of claim 1, wherein the determining whether there is overlap of the target time slot with the communication period of the terminal device comprises:

3. The method of claim 2, wherein detecting communication data transmitted by the terminal device in the first sub-slot of the target slot comprises:

4. The method of claim 2, wherein said synchronizing data with said second bluetooth device in said second sub-slot comprises:

5. The method of any of claims 1-4, wherein the target time slot is an even time slot.

6. The method of claim 1, wherein the determining whether there is overlap of the target time slot with the communication period of the terminal device comprises:

7. The method of claim 6, wherein the method further comprises:

And when the target time slot and/or the communication time period is correspondingly positioned in the last target period in the conflict occurrence period, the data synchronization period is adjusted.

8. The method according to claim 7, wherein the detecting whether the target time slot and/or the communication period corresponds to being located before a last target period in a collision occurrence period, the method further comprising:

acquiring a data transmission period of the terminal equipment;

9. The method of claim 8, wherein said determining a data synchronization period between said first bluetooth device and said second bluetooth device based on said data transmission period and at least one of said interrupt handling periods comprises:

10. The method according to any one of claims 7-9, further comprising:

Determining the collision occurrence period based on the data transmission period and the data synchronization period,

The conflict occurrence period is the least common multiple between the data transmission period and the data synchronization period.

11. The method of claim 1, wherein when the first bluetooth device is a master device, the second bluetooth device is a slave device; or when the first Bluetooth device is a slave device, the second Bluetooth device is a master device.

12. A data synchronization device, comprising:

13. A bluetooth device, comprising: a memory and a processor coupled with the memory; the memory is used for storing instructions, and the processor is used for executing the instructions; wherein the processor, when executing the instructions, implements the method of any of the preceding claims 1-11.

14. A data synchronization system comprising a first bluetooth device and a second bluetooth device in communication with the first bluetooth device, wherein the first bluetooth device is a bluetooth device as claimed in claim 13.

15. A computer readable storage medium storing a computer program, characterized in that the computer program, when executed by a processor, implements the method of any of the preceding claims 1-11.

16. A computer program product, characterized in that the computer program product comprises a computer program which, when executed by a processor, implements the method according to any of the preceding claims 1-11.