Bluetooth radio frequency coexistence scheduling method, terminal equipment and vehicles
By breaking down the Bluetooth paging process into multiple micro-states in real time and dynamically scheduling the operation of the wireless LAN module, the problem of Bluetooth connection being affected by the wireless LAN is solved, improving spectrum utilization and connection success rate.
Patent Information
- Application Number
- CN202611270411.1
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2026-08-20
- Publication Date
- 2026-11-17
AI Technical Summary
In scenarios where Bluetooth and Wi-Fi coexist, the Bluetooth connection establishment process in existing technologies is easily affected by Wi-Fi transmission, leading to connection timeouts or failures, wasted spectrum resources, and poor user experience.
By breaking down the Bluetooth paging process into paging sending state, waiting for response state, and response receiving state in real time, and dynamically performing differentiated scheduling, Bluetooth is given priority in the paging sending state and response receiving state, while the wireless LAN module is allowed to transmit data in the waiting for response state.
It improves Bluetooth connection success rate, reduces performance loss of WLAN module, enhances spectrum utilization efficiency, and achieves efficient collaboration and coexistence between Bluetooth and WLAN.
Smart Images

Figure CN123124098A_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of intelligent connected vehicle technology, and in particular to a Bluetooth radio frequency coexistence scheduling method, terminal equipment, and vehicle. Background Technology
[0002] In wireless communication devices, Bluetooth and short-range communication technologies such as Wi-Fi (e.g., WiFi) often coexist on the same device and share the 2.4 GHz frequency band, making co-channel interference difficult to avoid. Especially during the Bluetooth connection establishment process, the reliability requirements of the radio frequency environment are high, making it highly susceptible to the impact of concurrent transmissions on Wi-Fi, leading to connection timeouts or failures and affecting the user experience.
[0003] Existing coexistence management methods often employ a fixed-priority arbitration strategy. This strategy forces the Wi-Fi to remain completely silent or significantly back off when Bluetooth enters the connection establishment phase, until the Bluetooth process ends. This approach treats the Bluetooth connection establishment process as an indivisible, continuous time period, rigidly blocking Wi-Fi transmission throughout this entire period, failing to recognize the naturally occurring waiting or idle intervals within the process. Radio frequency resources within these intervals, which could be appropriately utilized by the Wi-Fi, are not released due to static priority settings, resulting in wasted spectrum resources. Summary of the Invention
[0004] This application provides a Bluetooth radio frequency coexistence scheduling method, a terminal device, and a vehicle, with the aim of improving the spectrum resource utilization rate in scenarios where Bluetooth and wireless local area networks coexist.
[0005] To achieve the above objectives, this application provides the following technical solution:
[0006] A Bluetooth radio frequency coexistence scheduling method includes:
[0007] Send a Bluetooth connection request to the Bluetooth controller to trigger the Bluetooth controller to initiate a Bluetooth paging process;
[0008] Obtain the micro-state of the Bluetooth paging process; the micro-state is any one of the paging sending state, waiting for response state, and response receiving state;
[0009] The microstate is synchronized to the coexistence management module, and the scheduling instruction output by the coexistence management module according to the microstate is obtained; wherein, the scheduling instruction is used to: instruct the wireless LAN module to enter a silent state when the microstate is the paging sending state or the response receiving state; and instruct the wireless LAN module to perform data transmission when the microstate is the waiting response state.
[0010] A terminal device includes: a processor, a memory, and a bus; the processor and the memory are connected via the bus.
[0011] The memory is used to store the program, and the processor is used to run the program, wherein the program is executed by the processor to perform the Bluetooth radio frequency coexistence scheduling method described above.
[0012] A vehicle including the terminal equipment shown above.
[0013] The technical solution provided in this application involves: sending a Bluetooth connection request to the Bluetooth controller to trigger the Bluetooth controller to initiate a Bluetooth paging process; acquiring the micro-state of the Bluetooth paging process; synchronizing the micro-state to the coexistence management module; and acquiring the scheduling instructions output by the coexistence management module based on the micro-state. This application breaks through the traditional, crude strategy of forcing the WLAN module to remain completely silent during Bluetooth paging. By decomposing the paging process into a paging transmission state, a waiting response state, and a response reception state in real time, and dynamically executing differentiated scheduling based on the current micro-state, Bluetooth is given priority in the paging transmission and response reception states, while the WLAN module is allowed to transmit data in the waiting response state. This effectively reduces the performance loss of the WLAN module and improves spectrum utilization efficiency while ensuring a high Bluetooth connection success rate. Attached Figure Description
[0014] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.
[0015] Figure 1 This is a first flowchart illustrating a Bluetooth radio frequency coexistence scheduling method provided in an embodiment of this application.
[0016] Figure 2 This is a second flowchart illustrating a Bluetooth radio frequency coexistence scheduling method provided in an embodiment of this application.
[0017] Figure 3 A schematic diagram of the third process of a Bluetooth radio frequency coexistence scheduling method provided in an embodiment of this application;
[0018] Figure 4 A fourth flowchart illustrating a Bluetooth radio frequency coexistence scheduling method provided in this application embodiment;
[0019] Figure 5 A fifth flowchart illustrating a Bluetooth radio frequency coexistence scheduling method provided in this application embodiment;
[0020] Figure 6 A sixth flowchart illustrating a Bluetooth radio frequency coexistence scheduling method provided in this application embodiment;
[0021] Figure 7 This is a schematic diagram of the architecture of a terminal device provided in an embodiment of this application. Detailed Implementation
[0022] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.
[0023] In this application, relational terms such as "first" and "second" are used merely to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. The terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.
[0024] like Figure 1 The diagram shown is a first flowchart of a Bluetooth radio frequency coexistence scheduling method provided in an embodiment of this application. It can be applied to terminal devices (such as smartphones, tablets, vehicle terminals, etc.) that simultaneously support Bluetooth communication and wireless LAN communication. The terminal device includes a Bluetooth controller, a wireless LAN module, a coexistence management module, and a processor. The method can be specifically applied to the processor and includes the following steps.
[0025] S101: Send a Bluetooth connection request to the Bluetooth controller to trigger the Bluetooth controller to initiate a Bluetooth paging process.
[0026] Among them, the Bluetooth connection request refers to the instruction issued by the upper-layer protocol stack (such as the application layer or framework layer) of the terminal device to instruct the Bluetooth controller to establish a Bluetooth connection.
[0027] A Bluetooth controller is a hardware module in a terminal device that is responsible for executing the Bluetooth baseband protocol. It is usually integrated into the wireless communication chip of the terminal device and communicates with the host through HCI (Host Controller Interface).
[0028] The Bluetooth paging process is a crucial step in establishing a connection in Classic Bluetooth. The initiating device sends a paging request and waits for a paging response from the peer device. In the Classic Bluetooth protocol, the initiating device sequentially sends ID packets (composed of Bluetooth device access addresses) during the paging process, and after each transmission, it enters a state of waiting to receive an ID response packet from the peer device.
[0029] In a possible implementation, when a user initiates a Bluetooth connection operation through an application (such as an in-vehicle connectivity application, a Bluetooth headset connection application, etc.), the system framework layer of the terminal device generates a Bluetooth connection request and sends the Bluetooth connection request to the Bluetooth controller. After receiving the Bluetooth connection request, the Bluetooth controller initiates a paging process according to the Bluetooth protocol specification.
[0030] For example, in the Android system, the application layer initiates a Bluetooth connection operation through interfaces such as BluetoothAdapter.startDiscovery() or BluetoothDevice.createBond(). After receiving the call, the system framework layer sends the HCI_Create_Connection command to the Bluetooth controller through the HCI interface to trigger the Bluetooth controller to initiate the Bluetooth paging process.
[0031] It's important to note that the Bluetooth paging process is the foundation for establishing an ACL (Asynchronous Connection-Less) connection between Bluetooth devices. During Bluetooth paging, the initiating device (the master device) alternately sends paging messages and listens for paging responses on multiple frequency hopping channels until it receives a response from the peer device (the slave device) or a timeout occurs. In this Bluetooth paging process, the use of radio frequency resources is highly sensitive to latency and interference. Interference from 2.4GHz band signals can lead to paging failures or a significant increase in connection establishment delay.
[0032] Optionally, before sending a Bluetooth connection request, embodiments of this application may also perform a pre-notification management process to eliminate scheduling delays and optimize radio frequency resource allocation. The implementation process of this pre-notification management process can be found in [reference needed]. Figure 2 The steps are shown.
[0033] S102: Obtain the micro-state of the Bluetooth paging process.
[0034] The micro-state can be any one of the paging send state, waiting for response state, and response receive state.
[0035] Specifically, microstate refers to the fine-grained state information obtained by the Bluetooth controller after breaking down the paging process in real time.
[0036] The paging transmission state (which can be denoted as Page_TX) represents the period during which the Bluetooth controller is sending a paging message (such as an ID packet).
[0037] The waiting response state (which can be denoted as Page_Wait) represents the period during which the Bluetooth controller has completed sending the current paging message and is waiting for the peer device to return a paging response.
[0038] The response receive state (which can be denoted as Page_RX) represents the period during which the Bluetooth controller is receiving a paging response (including response packet and acknowledgment packet) from the peer device.
[0039] In a possible implementation, when the Bluetooth controller executes the Bluetooth paging process, the state machine based on the Bluetooth baseband protocol decomposes the Bluetooth paging process into the three micro-states mentioned above in real time, and reports the current micro-state to the processor through hardware interfaces (such as interrupt signals, register status words, shared memory, etc.).
[0040] Specifically, when the Bluetooth controller's baseband core enters the transmit state, the Bluetooth controller writes the paging transmit state flag to the status register; when it enters the wait to receive state, the Bluetooth controller writes the wait to respond state flag to the status register; when it enters the receive state and begins receiving the paging response from the peer device, the Bluetooth controller writes the respond to receive state flag to the status register. The terminal device processor obtains the current micro-state of the Bluetooth paging process by reading this status register or responding to an interrupt signal.
[0041] In some examples, the Bluetooth controller's state machine output can be driven by the physical layer's transmit / receive state machine signals. For instance, when the Bluetooth controller's baseband core (Bluetooth baseband) is in transmit mode and the transmitted data packet is a paging ID packet, the state machine outputs a paging transmit state. When the Bluetooth baseband completes ID packet transmission and switches to receive mode, if this receive state corresponds to the listening window of the paging process, the state machine outputs a wait-for-response state. When the Bluetooth baseband detects a valid preamble within the listening window and begins receiving response data, the state machine outputs a respond-for-receive state. In this way, the Bluetooth controller can output the current micro-state of the Bluetooth paging process in real time.
[0042] Optionally, the Bluetooth controller can notify the processor when reporting microstates via an interrupt, and the processor can read the microstate information in the interrupt service routine; alternatively, the Bluetooth controller can continuously update the current microstate in its status register, and the processor can obtain the microstate information by periodically reading this register. Different acquisition methods can adapt to different processor loads and real-time requirements.
[0043] Optionally, this micro-state acquisition process is executed after the Bluetooth controller initiates the paging process. The acquired micro-state is used for subsequent differentiated scheduling decisions. For details, please refer to [link to relevant documentation]. Figure 4 The steps are shown.
[0044] S103: Synchronize the microstate to the coexistence management module and obtain the scheduling instructions output by the coexistence management module based on the microstate.
[0045] The scheduling instruction is used to: instruct the wireless LAN module to enter a silent state when the micro-state is in the paging send state or the response receive state; and instruct the wireless LAN module to perform data transmission when the micro-state is in the waiting response state.
[0046] It should be noted that the coexistence management module refers to a hardware logic module or hardware-software co-operation mechanism used to resolve radio frequency interference between Bluetooth and Wi-Fi in the 2.4GHz band. The coexistence management module can be integrated into the wireless communication chip in hardware form, or implemented in the baseband processor or application processor of the terminal device in firmware or software form.
[0047] The core function of the coexistence management module is to arbitrate the access permissions of Bluetooth and Wi-Fi to shared radio frequency resources (including antennas and 2.4GHz spectrum) based on the real-time activity status of Bluetooth and Wi-Fi, in order to avoid conflicts.
[0048] Scheduling instructions are command information generated by the coexistence management module based on the currently determined micro-state, used to control the behavior of the wireless LAN module.
[0049] A wireless LAN module is a hardware module that supports wireless LAN communication (such as WiFi communication). It typically shares the same radio frequency front-end and antenna system as the Bluetooth controller.
[0050] In a possible implementation, the processor synchronously sends the currently acquired micro-state to the coexistence management module. Based on the received micro-state, the coexistence management module generates corresponding scheduling instructions according to a preset scheduling strategy, and outputs the scheduling instructions to the wireless LAN module via GPIO (General Purpose Input / Output) pins, the internal bus, or a dedicated coexistence interface.
[0051] Specifically, when the micro-state is in the paging transmit state or the response receive state, the coexistence management module generates a scheduling instruction to instruct the WLAN module to enter a silent state (e.g., setting the BT_PRIORITY signal to a high level, forcing the WLAN module to stop all RF transceiver activities), so as to prioritize ensuring that Bluetooth transmission during sensitive phases is not interfered with by the WLAN; when the micro-state is in the waiting response state, the coexistence management module generates a scheduling instruction to instruct the WLAN module to perform data transmission (e.g., setting the BT_PRIORITY signal to a low level, allowing the WLAN module to perform transceiver activities under controlled conditions), so as to utilize the idle interval of Bluetooth waiting response to release RF resources for use by the WLAN.
[0052] In some examples, the scheduling commands output by the coexistence management module can directly control the RF switch or antenna switching circuit. For instance, when a scheduling command instructs the Wi-Fi module to enter a silent state, the coexistence management module can either control the RF switch to allocate the antenna entirely to Bluetooth or control the Wi-Fi module's power management unit to shut down the Wi-Fi module's RF power amplifier. When a scheduling command instructs the Wi-Fi module to transmit data, the coexistence management module can time-division multiplex antenna resources between Bluetooth and Wi-Fi, or adjust the Wi-Fi module's transmit power and transmission parameters to keep the interference level of the Wi-Fi module's transmission activity to Bluetooth within an acceptable range.
[0053] In some examples, during the paging transmit state, the Bluetooth controller is sending a paging message (e.g., an ID packet containing the device access address). This paging message is highly sensitive to interference; if the Wi-Fi is simultaneously transmitting and receiving, the paging message may not be correctly received by the peer device. During the response receive state, the Bluetooth controller is receiving the paging response from the peer device. This response signal is typically weak (especially in free-space propagation environments, where the signal returned by the peer device may attenuate over several meters to tens of meters), making it highly susceptible to Wi-Fi interference and loss. Therefore, in both states, it is necessary to ensure complete silence of the Wi-Fi to guarantee the success rate of Bluetooth paging.
[0054] In the waiting response state, the Bluetooth controller is simply in a waiting state, and the RF transceiver is in receive listening mode but has not yet detected a valid response signal. At this time, the WLAN can appropriately utilize this idle interval for data transmission (e.g., sending short control or management frames), thereby effectively utilizing spectrum resources while ensuring the success rate of Bluetooth connections. The above differentiated scheduling strategy overcomes the crude approach of forcing the WLAN to remain completely silent during the entire Bluetooth paging process in traditional coexistence schemes, and achieves cooperative coexistence between Bluetooth and the WLAN in the same shared frequency band.
[0055] Optionally, the scheduling instructions are used to control the wireless LAN module to perform data transmission in the waiting response state. For details, please refer to [link / reference needed]. Figure 3 The steps are shown.
[0056] Optionally, embodiments of this application also utilize... Figure 5 The steps shown are to enable frame-level intelligent backoff when a backoff signal is received from the coexistence management module.
[0057] The process described in S101-S103 above breaks down the Bluetooth paging process into three micro-states in real time: paging transmission state, waiting for response state, and response reception state. Based on the current micro-state, differentiated scheduling is dynamically executed. In the paging transmission state and response reception state, the wireless LAN module is instructed to enter a silent state to ensure Bluetooth transmission priority. In the waiting for response state, the wireless LAN module is instructed to transmit data. This overcomes the shortcomings of traditional coexistence schemes that treat the Bluetooth paging process as an indivisible complete time period and rigidly block the wireless LAN module. While ensuring the success rate of Bluetooth connection, it effectively reduces the performance loss of the wireless LAN module, improves the spectrum utilization efficiency of the 2.4GHz band, and realizes efficient collaborative coexistence of Bluetooth and wireless LAN in the same shared frequency band.
[0058] like Figure 2 The diagram shown is a second flowchart of a Bluetooth radio frequency coexistence scheduling method provided in an embodiment of this application. The method includes the following steps.
[0059] S201: Send a paging intent message to the coexistence management module.
[0060] The paging intent message includes an estimated paging timeout, which triggers the coexistence management module to adjust the wake-up cycle of the wireless LAN module based on the estimated paging timeout.
[0061] It should be noted that after the processor's system framework layer intercepts the Bluetooth connection request sent by the application layer, it does not immediately send the Bluetooth connection request to the Bluetooth controller. Instead, it first sends a paging intent message to the coexistence management module through a preset communication channel.
[0062] In the Android system, after receiving a Bluetooth connection request initiated by the application layer through the BluetoothAdapter or BluetoothDevice interface, the Bluetooth service module in the system framework layer (e.g., the Framework layer) first sends a paging intent message to the coexistence management module through a preset communication channel (e.g., a private Vendor channel) before constructing and issuing the corresponding HCI_Create_Connection command. This paging intent message informs the coexistence management module that a Bluetooth paging process is about to be initiated, allowing the coexistence management module to prepare for radio frequency resource configuration and scheduling in advance.
[0063] The preset communication channel refers to the pre-established communication interface between the processor's system framework layer and the coexistence management module. This preset communication channel can be a proprietary vendor channel customized by the Bluetooth chip vendor, or it can be system-level shared memory or a message queue. The preset communication channel is independent of the standard HCI command channel and is used to transmit pre-notification information before officially issuing HCI commands. Paging intent messages sent through this preset communication channel are not parsed into standard HCI commands by the Bluetooth controller; instead, they are specifically received and processed by the coexistence management module.
[0064] The paging intent message includes an estimated paging timeout, which triggers the coexistence management module to adjust the wake-up cycle of the WLAN module based on the estimated paging timeout. Specifically, the coexistence management module extends the wake-up cycle of the WLAN module from the default value (e.g., 100 milliseconds) to align with the estimated paging timeout, thereby reducing the RF resources consumed by the WLAN module during Bluetooth paging due to power-saving polling operations.
[0065] For example, if the estimated paging timeout is 5.12 seconds, the coexistence management module can adjust the wake-up cycle of the WLAN module to a multiple or a specific longer cycle that matches the estimated paging timeout. This extends the wake-up cycle as much as possible without triggering access point disconnection, allowing the WLAN module to pause its periodic wake-up operations during Bluetooth paging. During Bluetooth paging, the WLAN module's energy-saving polling operation consumes RF resources in the 2.4GHz band and generates RF interference. Aligning the wake-up cycle with the estimated paging timeout reduces this interference.
[0066] In some examples, after receiving a paging intent message, the coexistence management module also pre-allocates radio frequency resources based on the parameter information in the paging intent message. For example, the coexistence management module can pre-allocate antenna resources to Bluetooth or pre-adjust the gain settings of the radio frequency front-end to ensure that the radio frequency environment is in optimal condition when Bluetooth paging is initiated.
[0067] In possible implementations, specific operations for pre-allocating radio frequency resources include, but are not limited to: configuring a radio frequency switch to switch the antenna to the Bluetooth path, adjusting the receiving gain of the Bluetooth radio frequency front end to improve receiving sensitivity, and configuring the priority parameters of the coexistence management module so that Bluetooth obtains a higher radio frequency access priority than the wireless local area network during an upcoming paging process.
[0068] Optionally, the paging intent message may also include the MAC address (Media Access Control Address) of the peer device. The coexistence management module can identify the type of peer device (e.g., in-vehicle system, Bluetooth headset, or smartwatch) based on this MAC address, thereby configuring the RF resource allocation strategy more accurately. Different types of Bluetooth peripherals have different RF characteristics during paging. For example, in-vehicle systems typically have higher transmit power and better antenna performance, resulting in a stronger paging response signal, while Bluetooth headsets typically have lower transmit power, resulting in a weaker paging response signal and lower tolerance to RF interference.
[0069] In a possible implementation, the coexistence management module determines different radio frequency protection strategies based on the type of the peer device. For example, for target devices with lower transmission power, the radio frequency priority during Bluetooth paging can be increased or the response time of the wireless LAN module's silence can be further shortened.
[0070] S202: When the Bluetooth paging process ends before the estimated paging timeout period, notify the coexistence management module to resume the wake-up cycle.
[0071] If the Bluetooth controller successfully receives a paging response from the peer device and completes the connection establishment before the estimated paging timeout expires, it confirms that Bluetooth paging has been detected and immediately sends a notification message to the coexistence management module. Upon receiving this notification message, the coexistence management module restores the wake-up cycle of the wireless LAN module from the adjusted state to the default value, thus restoring the wireless LAN module to normal operating mode.
[0072] In some examples, the processor determines whether paging has completed prematurely by detecting the connection status of the Bluetooth controller. When the Bluetooth controller receives a paging response from the peer device and completes the connection establishment, it reports an HCI_Connection_Complete event to the host device. The terminal device's Bluetooth host determines that paging has completed when it receives this event and the event parameters indicate a successful connection. If this event occurs earlier than the estimated paging timeout, it is considered prematurely completed. Upon detecting this event, the processor immediately sends a recovery notification to the coexistence management module, triggering the module to perform a wake-up cycle recovery operation.
[0073] Optionally, if the Bluetooth paging process fails to complete ahead of schedule and reaches the estimated paging timeout, the coexistence management module does not need to actively restore the wake-up cycle. This is because the Bluetooth paging process naturally ends after the estimated paging timeout is reached, and the coexistence management module can restore the wake-up cycle automatically, or wait for the next paging retry and readjust it based on the new estimated timeout. The purpose is to ensure that once the wake-up cycle is adjusted, whether it completes ahead of schedule or reaches the timeout, it can eventually be restored to the default value to guarantee the normal operation of the wireless LAN module.
[0074] It should be noted that if Bluetooth paging completes before the estimated timeout period, but the coexistence management module fails to restore the wake-up cycle in a timely manner, the WLAN module may remain in a state with an extended wake-up cycle. This can result in the WLAN module operating inefficiently even after paging ends, for example, failing to receive downlink data from the access point in a timely manner or failing to perform normal network scanning. By promptly notifying the restoration of the wake-up cycle when paging ends early, the WLAN module can quickly return to normal operation, thereby minimizing the impact on WLAN transmission performance.
[0075] The process described in S201-S202 above sends a paging intent message carrying the estimated paging timeout to the coexistence management module before the Bluetooth connection request is officially sent. This allows the coexistence management module to adjust the wake-up cycle of the wireless LAN module in advance to reduce radio frequency interference during paging. When paging is completed ahead of schedule, the wake-up cycle is restored in time to avoid the wireless LAN module being in a state of continuous inefficient operation. This achieves precise adaptation of radio frequency resources in the time dimension, effectively eliminates scheduling delay, and further improves the success rate of Bluetooth paging and the overall response efficiency of the system.
[0076] like Figure 3 The diagram shown is a third flowchart of a Bluetooth radio frequency coexistence scheduling method provided in an embodiment of this application. The method includes the following steps.
[0077] S301: Instructs the wireless LAN module to send non-data frames under preset transmission constraints.
[0078] Non-data frames refer to MAC frame types that do not carry upper-layer user data, including but not limited to control frames (such as RTS frames, CTS frames, ACK frames, PS-Poll frames, etc.) and management frames (such as Probe Request frames, Probe Response frames, Beacon frames, etc.). Compared with data frames, non-data frames are usually shorter (e.g., RTS frames are 20 bytes long, and ACK frames are 14 bytes long), have shorter transmission times (usually between hundreds of microseconds and milliseconds), and cause relatively less interference to Bluetooth radio frequency.
[0079] Preset transmission constraints refer to the restrictions imposed on the wireless LAN module when it transmits while waiting for a response. These restrictions include, but are not limited to, transmission power limits (e.g., limiting the transmission power to no more than a certain preset threshold), transmission duration limits (e.g., limiting the duration of a single transmission to no more than a certain preset duration), and time slot limits (e.g., allowing transmission only within a specific time slot).
[0080] In a possible implementation, when the micro-state is in a wait-to-respond state, the scheduling command output by the coexistence management module instructs the WLAN module to send non-data frames under preset transmission constraints. For example, the coexistence management module may instruct the WLAN module to send RTS frames or perform active background scanning (i.e., send Probe Request frames) provided that the transmission activity performed by the WLAN module in the wait-to-respond state does not substantially interfere with Bluetooth paging reception.
[0081] It should be noted that in the waiting response state, the Bluetooth controller does not perform any radio frequency transmission or reception activities; instead, it remains in a waiting state. Radio frequency resources can be appropriately utilized during this period. However, since Bluetooth may receive a paging response from the peer device at any time (the peer device may send a response at any moment during the waiting period), the transmission activities performed by the WLAN module during this period need to be constrained to avoid interference when Bluetooth begins receiving responses. By sending non-data frames under preset transmission constraints, the risk of interference to Bluetooth can be controlled while utilizing the spectrum resources during the waiting period.
[0082] Specifically, the process of sending non-data frames under preset transmission constraints can be seen in subsequent steps S302-S303.
[0083] S302: Divide the time window for waiting for a response into multiple micro-slots, each of which has a corresponding remaining time window.
[0084] The waiting response window refers to the total time the Bluetooth controller waits for the peer device to return a paging response after sending a paging message. For example, the paging timeout defined by the Bluetooth protocol specification is usually 5.12 seconds. During this time period, the Bluetooth controller may go through multiple alternating cycles of ID packet sending and response listening. Each round of send-listen cycle contains a send sub-state and a wait sub-state.
[0085] A micro-slot refers to a time window that is further divided into multiple smaller time segments, such as dividing each waiting sub-state into multiple micro-slots.
[0086] Each microtimeslot has a corresponding remaining time window, which refers to the length of time remaining from the current moment until the end of the current microtimeslot. For example, if the total length of the current microtimeslot is T...total The time elapsed since the start of this micro-slot is T. past The current remaining time window is T. remain =T total -T past .
[0087] In a possible implementation, the coexistence management module logically divides the waiting response state time window into multiple micro-slots. For example, the Bluetooth controller enters a waiting response state after each ID packet transmission. The duration of this waiting response state (i.e., the listening window length) depends on the response time and link quality of the peer device, typically ranging from tens to hundreds of milliseconds. The coexistence management module divides this listening window into several micro-slots (e.g., each micro-slot is 20 milliseconds long). At the beginning of each micro-slot, the remaining time window of the current micro-slot is equal to the total length of that micro-slot (e.g., 20 milliseconds), and the remaining time window gradually shortens over time.
[0088] S303: In each micro-time slot, when the frame to be sent by the wireless LAN module is a non-data frame, and the estimated transmission time of the non-data frame meets the time limit of the remaining time window corresponding to the micro-time slot, and the current state of the wireless LAN module meets the preset interference conditions, the wireless LAN module is instructed to send the non-data frame.
[0089] The estimated transmission time for non-data frames refers to the estimated time required for the WLAN module to send the non-data frame. This estimate can be calculated based on the length of the non-data frame and the current physical layer transmission rate. For example, the transmission time of an RTS frame can be obtained by dividing the frame length (including the PHY preamble and frame header) by the current transmission rate.
[0090] The remaining time window time limit refers to the upper limit constraint on the estimated transmission time of non-data frames. This time limit is determined based on a preset proportion of the remaining time window. For example, the preset proportion is 80%, meaning that the estimated transmission time does not exceed 80% of the remaining time window. This ensures that a 20% time margin is left before Bluetooth may receive a paging response, preventing the Wi-Fi transmission from occupying the entire remaining time window and interfering with Bluetooth response reception.
[0091] The current state of the wireless LAN module meets the preset interference conditions, which means that the current transmission power of the wireless LAN module is lower than the preset interference threshold. The preset interference threshold can be dynamically adjusted according to factors such as the current Bluetooth radio frequency sensitivity and the signal strength of the target device.
[0092] In some examples, the determination that a frame to be transmitted by the WLAN module is a non-data frame is performed by the WLAN module's MAC layer protocol stack. Before submitting the frame to the physical layer for transmission, the MAC layer protocol stack identifies whether the current frame is a non-data frame by parsing the frame type subfield in the frame control field.
[0093] In some examples, the estimated transmission time for non-data frames is calculated by the physical layer of the WLAN module based on the current modulation rate and frame length. The specific method for determining whether the current state of the WLAN module meets the preset interference conditions is as follows: the WLAN module's RF front-end has a power detection function, which can acquire the current transmit power value in real time. The coexistence management module reads this power value and compares it with a preset interference threshold to determine whether the interference conditions are met.
[0094] In a possible implementation, when the frame to be transmitted by the WLAN module is a non-data frame, the coexistence management module determines whether the estimated transmission time of the non-data frame meets the time limit of the remaining time window of the current micro-time slot (e.g., the estimated transmission time is less than 80% of the remaining time window), and simultaneously determines whether the current transmission power of the WLAN module is lower than a preset interference threshold (e.g., lower than -5dBm). Only when both conditions are met simultaneously will the coexistence management module instruct the WLAN module to transmit the control frame; otherwise, the WLAN module will not transmit the control frame and will wait for the next micro-time slot to make the determination.
[0095] The execution order of the above three conditions (i.e., frame type judgment, time condition judgment, and interference condition judgment) can be flexibly configured.
[0096] In a possible implementation, it is first determined whether the frame to be sent is a non-data frame. If not, the subsequent determination process is not entered. If it is, it is further determined whether the estimated transmission time meets the time limit, and then it is determined whether the current transmission power is lower than the preset interference threshold.
[0097] In another possible implementation, it is first determined whether the remaining time window of the current micro-slot meets the time limit. If not, transmission is directly prohibited. If it does meet the time limit, the frame type and transmission power are then determined. Different execution orders can adapt to different hardware architectures and real-time requirements.
[0098] It should be noted that dividing the waiting response window into micro-slots and performing conditional checks on each micro-slot enables fine-grained control of Wi-Fi transmission. By using both time ratios and power thresholds, it can be ensured that the Wi-Fi module can send non-data frames "opportunistically" during Bluetooth waiting periods without causing substantial interference to Bluetooth. For example, if the Wi-Fi module needs to send an RTS control frame with an estimated transmission time of 5 milliseconds, and the remaining time window of the current micro-slot is 8 milliseconds, and the current transmission power of the Wi-Fi module is -8dBm (below the preset interference threshold of -5dBm), then both conditions are met, and the Wi-Fi module is allowed to send the non-data frame. If the remaining time window is only 4 milliseconds, the estimated transmission time of 5 milliseconds does not meet the time limit, and the Wi-Fi module will not send the frame, waiting for the next micro-slot to attempt it again.
[0099] The processes described in S301-S303 above allow the WLAN module to send non-data frames under preset transmission constraints during the waiting response state. The waiting response state time window is divided into micro-time slots. Within each micro-time slot, the transmission of control frames is precisely determined based on both time ratio and transmission power threshold. This achieves fine-grained control over WLAN transmission within the waiting interval while ensuring that Bluetooth paging responses are not interfered with. It achieves the best balance between sufficiency of spectrum resource utilization and Bluetooth connection reliability.
[0100] like Figure 4 The diagram shown is a fourth flowchart of a Bluetooth radio frequency coexistence scheduling method provided in an embodiment of this application. The method includes the following steps.
[0101] S401: Receives micro-status information reported by the Bluetooth controller.
[0102] The micro-state information is obtained by the Bluetooth controller in real time from the Bluetooth paging process. Specifically, after initiating the Bluetooth paging process, the Bluetooth controller, based on the state machine of the Bluetooth baseband protocol stack, decomposes the Bluetooth paging process into multiple micro-states in real time (including paging send state, waiting for response state, and response receive state), and reports the current micro-state as micro-state information to the processor through the hardware interface.
[0103] In some examples, when the Bluetooth controller's baseband core (referred to as Bluetooth baseband) performs the paging process, its internal state machine cycles sequentially between the ID packet sending phase, the wait-for-response phase, and the receive-for-response phase. The Bluetooth controller encodes the current state of the state machine into a microstate identifier through hardware logic and notifies the terminal device processor via interrupt signal lines or register updates.
[0104] For example, when the Bluetooth baseband is in the transmitting state and the transmitted data packet is a paging ID packet, the state machine outputs a paging transmit state flag. When the Bluetooth baseband completes the ID packet transmission and switches to the receiving state, if this receiving state corresponds to the listening window of the paging process, the state machine outputs a waiting response state flag. When the Bluetooth baseband detects a valid preamble within the listening window and begins receiving response data, the state machine outputs a response receive state flag.
[0105] In some examples, the Bluetooth controller sets a microstate field in its status register, where the encoded value corresponds to a different microstate. For example, encoding "00" represents the idle state, encoding "01" represents the paging transmit state, encoding "10" represents the waiting for a response state, and encoding "11" represents the response received state. During the paging process, the Bluetooth controller updates the microstate field in this status register whenever the state machine transitions. The processor can obtain the current microstate of the Bluetooth paging process by reading the value of this status register.
[0106] Optionally, the Bluetooth controller can notify the processor when reporting microstates via an interrupt. For example, when a microstate switches from a wait-to-respond state to a respond-to-receive state, the Bluetooth controller triggers a high-priority interrupt, and the processor immediately reads the value of the status register in the interrupt service routine, thereby obtaining the microstate switch event within the shortest possible delay. Alternatively, the Bluetooth controller can continuously update the current microstate in its status register, and the processor can obtain microstate information by periodically reading this register (e.g., every 1 millisecond).
[0107] S402: Parse the microstate information to determine the current microstate of the Bluetooth paging process.
[0108] Upon receiving micro-state information reported by the Bluetooth controller, the processor parses the micro-state fields contained in the information to determine the current micro-state of the Bluetooth paging process. Based on the parsing result, the processor generates a corresponding micro-state identifier and stores it in system memory for the coexistence management module to read during subsequent scheduling decisions.
[0109] In some examples, the processor reads the value of the status register and, by referring to a pre-defined encoding mapping table, converts the encoded value into the corresponding microstate name. The encoding mapping table can be pre-stored in system memory; for example, the table could contain the following correspondence: register value 0x01 corresponds to the paging transmit state, 0x02 to the waiting response state, and 0x03 to the response receive state. After reading the register value, the processor retrieves the semantic information of the current microstate by looking up the table and stores it in system variables.
[0110] Optionally, after parsing the current microstate, the processor can also compare the current microstate with the previous microstate to detect whether a microstate transition has occurred. When a microstate transition is detected, the processor can proactively notify the coexistence management module so that the coexistence management module can update the scheduling policy in a timely manner. For example, when the processor detects that the microstate has switched from a waiting response state to a response receiving state, the processor immediately notifies the coexistence management module to output a new scheduling instruction to instruct the wireless LAN module to enter a silent state.
[0111] The processes shown in S401-S402 above enable the terminal device processor to accurately perceive the fine-grained state changes within the paging process through the real-time disassembly and active reporting of the paging process by the Bluetooth controller. This provides an accurate data foundation for subsequent differentiated scheduling decisions, thereby ensuring the real-time performance and accuracy of the entire coexistence scheduling scheme in the time dimension. It is a key preliminary step for realizing micro-state perception and dynamic scheduling.
[0112] like Figure 5 The diagram shown is a fifth flowchart of a Bluetooth radio frequency coexistence scheduling method provided in an embodiment of this application. The method includes the following steps.
[0113] S501: Receives backoff signal.
[0114] The backoff signal is a control signal sent by the coexistence management module to the wireless local area network module when the wireless local area network module needs to relinquish radio frequency resources. This backoff signal is used to notify the wireless local area network module that it is about to perform a backoff operation (such as stopping radio frequency transmission and reception and transferring radio frequency resources to Bluetooth).
[0115] In some examples, backoff signals can be transmitted via hardware signal lines (such as level changes on GPIO pins), internal bus messages, or register flags.
[0116] In a possible implementation, when the microstate switches to the paging transmit state or the response receive state, the coexistence management module generates a backoff signal and sends it to the wireless LAN module to instruct the wireless LAN module to relinquish radio frequency resources. For example, the coexistence management module can switch the BT_PRIORITY signal line from low to high; upon detecting this level change, the wireless LAN module knows that a backoff operation is required.
[0117] S502: In response to a backoff signal, determine the type of frame that the wireless LAN module is currently transmitting.
[0118] Among them, frame type refers to the type of MAC frame that the wireless LAN module is currently sending, which includes at least aggregated frames and single frames.
[0119] An aggregated frame is a frame containing multiple aggregated MAC Protocol Data Units (A-MPDUs). This frame is composed of multiple subframes (i.e., A-MPDU subframes) and is used to improve transmission efficiency. Aggregated frames are typically quite long; for example, an A-MPDU can contain multiple MSDU (MAC Service Data Unit) subframes, with a total length reaching tens of thousands of bytes and a transmission time ranging from milliseconds to tens of milliseconds.
[0120] A single frame refers to an independent MAC frame that does not contain aggregated subframes, such as a single data frame, control frame, or management frame. It is relatively short, usually ranging from tens to hundreds of bytes.
[0121] In a possible implementation, after receiving the backoff signal, the wireless LAN module first checks the current transmit buffer and the MAC layer state machine to determine if a frame is currently being transmitted. If a frame is being transmitted, it further identifies whether the currently transmitted frame is an aggregated frame or a single frame by parsing the frame control field or aggregation control field in the MAC frame header. For example, if the frame type in the MAC frame header of the currently transmitted frame indicates a data frame, and the frame carries an A-MPDU aggregation identifier, it is determined to be an aggregated frame; otherwise, it is determined to be a single frame.
[0122] S503: If an aggregate frame is currently being transmitted, control the wireless LAN module to postpone the backoff action until the aggregate frame transmission is completed before relinquishing radio frequency resources.
[0123] Specifically, "delaying the backoff action" means that the terminal device processor controls the Wi-Fi module not to immediately stop transmitting the current frame after receiving the backoff signal, but to wait until the complete transmission of the current aggregated frame is completed before performing the backoff. The completion of aggregated frame transmission means that all A-MPDU subframes of the aggregated frame have been transmitted and the frame boundary of the aggregated frame has been reached (i.e., the moment when the last bit of the last subframe has been transmitted). "Relinquishing radio frequency resources" means that the Wi-Fi module stops radio frequency transmission and reception activities, handing over the radio frequency resources to Bluetooth.
[0124] In a possible implementation, if the WLAN module is currently transmitting an aggregated frame, the terminal device processor controls the WLAN module not to immediately perform a backoff action, but to continue transmitting the aggregated frame. The WLAN module only stops radio frequency transmission and relinquishes radio frequency resources after the last A-MPDU subframe of the aggregated frame has been transmitted and reached the frame boundary. Specifically, when the terminal device processor receives a backoff signal, it obtains the remaining transmission time of the current aggregated frame from the WLAN module. If the remaining transmission time is less than a preset threshold, it controls the WLAN module to continue transmitting until completion. Alternatively, the terminal device processor continuously monitors the frame boundary signal during the aggregated frame transmission process, and immediately controls the WLAN module to perform a backoff action when the frame boundary is detected.
[0125] In some examples, an aggregated frame (A-MPDU) consists of multiple A-MPDU subframes arranged sequentially, separated by subframe delimiters. The entire aggregated frame includes a frame end padding field at the end. The frame boundary refers to the moment when the last A-MPDU subframe of the aggregated frame and the last bit of its end padding are transmitted. When the MAC layer of the WLAN module transmits the aggregated frame, it records the number of bytes transmitted and the total number of bytes using a hardware counter. When the number of bytes transmitted equals the total number of bytes, the hardware generates a "transmission complete" interrupt signal. The trigger time of this interrupt signal is the frame boundary. When the terminal device processor receives a backoff signal, if it detects that an aggregated frame is currently being transmitted, it records the total length of the current frame and the length transmitted, and calculates the remaining transmission time using the difference. When the hardware generates a transmission complete interrupt, the terminal device processor controls the WLAN module to perform a backoff action in the interrupt service routine, relinquishing radio frequency resources. This method ensures that the execution time of the backoff action is precisely aligned with the complete end time of the aggregated frame transmission, avoiding retransmission overhead caused by premature interruption.
[0126] S504: If a single frame is currently being transmitted, control the wireless LAN module to immediately perform a backoff action.
[0127] If the wireless LAN module is currently transmitting a single frame, the terminal device processor immediately controls the wireless LAN module to stop transmitting that single frame and execute a backoff action, relinquishing radio frequency resources. Because the single frame is short, the overhead of immediately interrupting and retransmitting is relatively small.
[0128] It's important to note that aggregated frames typically contain multiple subframes and have a longer transmission time. If the transmission of an aggregated frame is forcibly interrupted, the entire frame needs to be retransmitted (because the integrity of the A-MPDU is compromised). This not only wastes the already consumed transmission time and channel bandwidth but also increases the system's retransmission overhead and the overall noise floor of the 2.4GHz band. In contrast, single frames are shorter in length and transmission time, resulting in relatively lower retransmission overhead after interruption. By identifying frame types and implementing differentiated backoff strategies—aggregated frames backoff to the boundary while single frames backoff immediately—the retransmission overhead caused by abruptly interrupting large data packet transmissions on the Wi-Fi network can be avoided while maintaining Bluetooth transmission priority. This improves the overall communication efficiency and robustness of the system.
[0129] Optionally, in addition to performing A-MPDU boundary backoff, embodiments of this application also... Figure 6 The steps shown enable dynamic adjustment of the timeout for the next paging retry when paging fails.
[0130] The processes described in S501-S504 above identify the type of frames currently being transmitted by the wireless LAN module and execute differentiated backoff strategies. Aggregated frames are delayed and backoffed to the frame boundary, while single frames are backoffed immediately. This avoids the retransmission overhead caused by abruptly interrupting the transmission of aggregated frames in the wireless LAN while ensuring the priority of Bluetooth transmission. It also reduces the overall noise floor of the 2.4GHz band and improves the overall communication efficiency and robustness of the system.
[0131] like Figure 6 The diagram shown is a sixth flowchart of a Bluetooth radio frequency coexistence scheduling method provided in this application embodiment, which includes the following steps.
[0132] S601: Detects whether the Bluetooth controller has lost its paging response.
[0133] In this process, the Bluetooth controller starts a paging timeout timer while in the waiting-for-response state and continuously listens for paging responses from the peer device. If no valid paging response packet is detected before the timeout timer expires, a paging response loss is determined to have occurred. The terminal device processor obtains the paging response loss information by receiving an HCI event reported by the Bluetooth controller or by reading the Bluetooth controller's status register. In the Bluetooth protocol, paging response loss typically manifests as the Bluetooth controller failing to receive an ID response packet or FHS packet from the peer device by the time the paging timeout timer expires.
[0134] In some examples, the Bluetooth controller opens a listening window after each ID packet transmission. This listening window is several Bluetooth time slots in length (e.g., 2 to 4 time slots, each 625 microseconds long). If no ID response packet is detected from the peer device within this listening window, the Bluetooth controller switches to the next frequency hopping channel and repeats the transmit-listen process. If multiple attempts on all frequency hopping channels fail to receive a response until the paging timeout timer expires, the Bluetooth controller reports an HCI_Connection_Complete event to the host via the HCI interface. The event parameters include a status code indicating connection failure and the reason for the failure. Upon receiving this event, the processor determines that a paging response loss has occurred.
[0135] S602: When the paging response is lost by the Bluetooth controller, obtain the backoff delay of the wireless LAN module and the current channel status.
[0136] When the terminal device processor detects a lost paging response, it obtains the backoff delay from the coexistence management module and the current channel status from the Bluetooth controller and / or the wireless LAN module.
[0137] The backoff delay refers to the time delay between when the WLAN module receives the backoff signal and when it actually relinquishes radio frequency resources. This backoff delay is recorded by the coexistence management module based on the execution status of the most recent backoff signal. For example, if the WLAN module is transmitting an A-MPDU aggregation frame when it receives the backoff signal, and the aggregation frame still needs 5 milliseconds to complete transmission, then the backoff delay is 5 milliseconds.
[0138] In a possible implementation, the backoff delay can be obtained through timestamp recording within the WLAN module: the WLAN module records a first moment when it receives the backoff signal, and a second moment when it completes the transmission of the current aggregated frame and actually relinquishes the radio frequency resources. The difference between the second moment and the first moment is the backoff delay. The WLAN module reports the above records to the coexistence management module, and the terminal device processor reads the backoff delay from the coexistence management module.
[0139] At the same time, the processor obtains the current channel status, which includes parameters such as channel congestion, interference level, and signal-to-noise ratio.
[0140] In some examples, the current channel state is obtained through a channel quality assessment performed by the Bluetooth controller during paging intervals. During its idle periods or paging intervals, the Bluetooth controller samples and analyzes the RSSI (Received Signal Strength Indication) within the 2.4 GHz band to obtain the noise floor level and signal activity of the current band. When the RSSI noise floor is higher than a preset noise floor threshold (e.g., higher than -80 dBm), it indicates strong radio frequency interference and high channel congestion. The terminal device processor obtains these channel state parameters by reading the channel assessment register of the Bluetooth controller.
[0141] Optionally, the current channel state can also be obtained through the CCA (Clear Channel Assessment) mechanism of the wireless LAN module. Before performing a backoff operation, the wireless LAN module typically detects that the channel is busy via CCA, and the proportion of busy time can be used as a reference value for channel congestion. The processor reads the CCA statistics from the wireless LAN module through the coexistence management module to obtain the current channel state.
[0142] S603: Calculate the dynamic compensation duration based on the backoff delay and the current channel state.
[0143] The dynamic compensation duration is calculated based on the obtained backoff delay and the current channel state. The dynamic compensation duration is related to the backoff delay and the current channel state: the larger the backoff delay or the higher the channel congestion, the longer the dynamic compensation duration, and vice versa.
[0144] In some examples, the dynamic compensation duration is positively correlated with the backoff delay; that is, the larger the backoff delay, the longer the dynamic compensation duration. For example, the dynamic compensation duration can be calculated using the following linear model: ΔT = α·D + β·C, where D is the backoff delay, C is the channel congestion level (e.g., the proportion of busy channel time, ranging from 0 to 1), and α and β are preset weighting coefficients, with α ranging from 0.5 to 2.0 and β ranging from 0.1 to 1.0. For example, when the backoff delay D = 5ms, the channel congestion level C = 60% (meaning the proportion of busy channel time is 60%), α = 1.0, and β = 0.5, ΔT = 1.0 × 5 + 0.5 × 60 = 35ms.
[0145] In a possible implementation, the dynamic compensation duration can also be determined using a stepped mapping method: when the backoff delay is less than 2ms and the channel congestion is less than 30%, ΔT = 0. When the backoff delay is 2-5ms or the channel congestion is 30%-60%, ΔT = 50ms. When the backoff delay is greater than 5ms or the channel congestion is greater than 60%, ΔT = 100ms. Both of these methods can achieve adaptive determination of the dynamic compensation duration, and the specific method used can be selected based on the system processing capacity and real-time requirements.
[0146] S604: Controls the Bluetooth controller to increase the timeout for the next paging retry by a dynamic compensation duration.
[0147] The processor sends the calculated dynamic compensation duration to the Bluetooth controller, which then increments the default paging timeout by this dynamic compensation duration before initiating the next paging retry. This new timeout is then used as the actual timeout for the next paging retry. For example, if the dynamic compensation duration is 35ms, the actual timeout for the next paging retry will be 5.12 seconds + 35ms = 5.155 seconds. The Bluetooth controller uses this adjusted timeout to start the paging timeout timer in subsequent paging retries.
[0148] In some examples, the application of dynamic compensation duration is one-time, effective only for the immediately following paging retry. If the current paging retry also fails, the terminal device processor recalculates the dynamic compensation duration based on the latest acquired backoff delay and the current channel state for the next paging retry. In other words, after each failed paging retry, the terminal device processor recalculates the dynamic compensation duration based on the real-time RF environment. This approach allows the dynamic compensation strategy to continuously respond to changes in the real-time RF environment, avoiding the use of previous compensation values after changes in channel state.
[0149] The processes described in S601-S604 above obtain the backoff delay and current channel state of the wireless LAN module when the paging response is lost. Based on this, the dynamic compensation time is calculated and added to the timeout time of the next paging retry. This enables the paging timeout time to dynamically adapt to the real-time radio frequency environment. In scenarios with severe radio frequency interference, time is used to improve success rate. In scenarios with mild interference, unnecessary power consumption is avoided, further enhancing the connection stability and energy efficiency of the system under different operating conditions.
[0150] This application also provides a terminal device, such as... Figure 7As shown, the terminal device includes a processor 701, a memory 702, and a bus 703. The processor 701 and the memory 702 are connected via the bus 703. The memory 702 is used to store programs, and the processor 701 is used to run the programs. When the program is run by the processor 701, it executes the Bluetooth radio frequency coexistence scheduling method described in any of the above method embodiments, including:
[0151] Send a Bluetooth connection request to the Bluetooth controller to trigger the Bluetooth controller to initiate a Bluetooth paging process;
[0152] Obtain the micro-state of the Bluetooth paging process; the micro-state is any one of the paging sending state, waiting for response state, and response receiving state;
[0153] The microstate is synchronized to the coexistence management module, and the scheduling instruction output by the coexistence management module according to the microstate is obtained; wherein, the scheduling instruction is used to: instruct the wireless LAN module to enter a silent state when the microstate is the paging sending state or the response receiving state; and instruct the wireless LAN module to perform data transmission when the microstate is the waiting response state.
[0154] Optionally, before sending a Bluetooth connection request to the Bluetooth controller, the method further includes:
[0155] Send a paging intent message to the coexistence management module; the paging intent message includes an estimated paging timeout time, so as to trigger the coexistence management module to adjust the wake-up cycle of the wireless LAN module according to the estimated paging timeout time.
[0156] Optionally, the method further includes:
[0157] When the Bluetooth paging process ends before the estimated paging timeout period, the coexistence management module is notified to resume the wake-up cycle.
[0158] Optionally, instructing the wireless local area network module to perform data transmission includes:
[0159] The wireless LAN module is instructed to send non-data frames under preset transmission constraints.
[0160] Optionally, instructing the wireless local area network module to send non-data frames under preset transmission constraints includes:
[0161] The time window for waiting for a response is divided into multiple micro-slots, and each micro-slot has a corresponding remaining time window.
[0162] Within each micro-time slot, when the frame to be transmitted by the wireless local area network module is a non-data frame, and the estimated transmission time of the non-data frame meets the time limit of the remaining time window, and the current state of the wireless local area network module meets the preset interference conditions, the wireless local area network module is instructed to transmit the non-data frame.
[0163] Optionally, obtaining the micro-state of the Bluetooth paging process includes:
[0164] Receive micro-state information reported by the Bluetooth controller; the micro-state information is obtained by the Bluetooth controller in real time by disassembling the Bluetooth paging process;
[0165] The microstate information is analyzed to determine the current microstate of the Bluetooth paging process.
[0166] Optionally, the method further includes:
[0167] Receive backoff signal;
[0168] In response to the backoff signal, determine the type of frame that the wireless LAN module is currently transmitting;
[0169] If an aggregate frame is currently being transmitted, the wireless LAN module is controlled to postpone the backoff action until the aggregate frame transmission is completed before relinquishing radio frequency resources.
[0170] If a single frame is currently being transmitted, the wireless LAN module is controlled to immediately perform a backoff action.
[0171] Optionally, the method further includes:
[0172] Detect whether the Bluetooth controller has experienced a loss of paging response;
[0173] When the paging response is lost by the Bluetooth controller, the backoff delay and current channel state of the wireless LAN module are obtained.
[0174] Calculate the dynamic compensation duration based on the backoff delay and the current channel state;
[0175] The Bluetooth controller is controlled to increase the timeout for the next paging retry by the dynamic compensation duration.
[0176] In possible implementations, the terminal device can be an electronic device that supports dual-mode communication via Bluetooth and Wi-Fi, such as a smartphone, tablet, in-vehicle terminal, smartwatch, or laptop. The processor can be a central processing unit, application processor, baseband processor, or application-specific integrated circuit (ASIC). The memory can be a computer-readable storage medium such as read-only memory, random access memory, or flash memory.
[0177] Taking an in-vehicle terminal as an example, when the vehicle starts, the processor of the in-vehicle terminal executes the program in the memory. When the user tries to connect to a Bluetooth headset or mobile phone through the in-vehicle system, the above-mentioned Bluetooth radio frequency coexistence scheduling method is executed to ensure that the Bluetooth connection is successful while maintaining the transmission performance of the in-vehicle wireless local area network (such as an in-vehicle hotspot).
[0178] In possible implementations, the vehicle can be a new energy vehicle (such as a pure electric vehicle, a plug-in hybrid electric vehicle, etc.) or a traditional fuel vehicle. The vehicle's in-vehicle infotainment system (vehicle infotainment system) integrates the functions of the aforementioned terminal devices. When the vehicle is in motion, if a user connects to a Bluetooth peripheral device (such as a Bluetooth headset, smart key, tire pressure monitoring device, etc.) through the in-vehicle system, the in-vehicle system executes the aforementioned Bluetooth radio frequency coexistence scheduling method to maintain the transmission performance of the in-vehicle wireless LAN hotspot or the in-vehicle wireless communication module while ensuring the success rate of Bluetooth connections, thereby ensuring the passenger's wireless network usage experience and the normal operation of the vehicle's remote communication functions.
[0179] In a possible implementation, the vehicle also includes a Bluetooth antenna and a Wi-Fi antenna, both of which are located inside the vehicle or on the vehicle body structure, for transmitting and receiving Bluetooth and Wi-Fi signals. When the on-board terminal's processor executes the above method, it controls the allocation of radio frequency resources in the antenna system to achieve efficient coexistence of Bluetooth and Wi-Fi in the shared 2.4GHz frequency band.
[0180] The aforementioned terminal device embodiments execute program instructions stored in the memory through a processor to implement all steps of the Bluetooth radio frequency coexistence scheduling method described in the preceding method embodiments. This integrates mechanisms such as micro-state awareness, differentiated scheduling, pre-notification management, frame-level intelligent backoff, and dynamic timeout compensation into products such as smartphones, tablets, or in-vehicle terminals, providing a complete radio frequency coexistence solution for terminal devices supporting dual-mode Bluetooth and Wi-Fi communication. Vehicles containing this terminal device can ensure the connection stability between the in-vehicle system and Bluetooth peripherals while maintaining the transmission performance of the in-vehicle Wi-Fi hotspot during driving, effectively improving the user's intelligent connected vehicle experience.
[0181] While several specific implementation details are included in the foregoing discussion, these should not be construed as limiting the scope of this application. Certain features described in the context of individual embodiments may also be implemented in combination in a single embodiment. Conversely, various features described in the context of a single embodiment may also be implemented individually or in any suitable sub-combination in multiple embodiments.
[0182] The above description is merely a preferred embodiment of this application and an explanation of the technical principles employed. Those skilled in the art should understand that the scope of disclosure in this application is not limited to technical solutions formed by specific combinations of the above-described technical features, but should also cover other technical solutions formed by arbitrary combinations of the above-described technical features or their equivalents without departing from the above-described concept. For example, technical solutions formed by substituting the above features with (but not limited to) technical features with similar functions disclosed in this application.
Claims
1. A Bluetooth radio frequency coexistence scheduling method, characterized in that, include: Send a Bluetooth connection request to the Bluetooth controller to trigger the Bluetooth controller to initiate a Bluetooth paging process; Obtain the micro-state of the Bluetooth paging process; The microstate is any one of the paging send state, waiting for response state, and response receive state; The microstate is synchronized to the coexistence management module, and the scheduling instruction output by the coexistence management module according to the microstate is obtained; wherein, the scheduling instruction is used to: instruct the wireless LAN module to enter a silent state when the microstate is the paging sending state or the response receiving state; and instruct the wireless LAN module to perform data transmission when the microstate is the waiting response state.
2. The method according to claim 1, characterized in that, Before sending a Bluetooth connection request to the Bluetooth controller, the method further includes: Send a paging intent message to the coexistence management module; the paging intent message includes an estimated paging timeout time, so as to trigger the coexistence management module to adjust the wake-up cycle of the wireless LAN module according to the estimated paging timeout time.
3. The method according to claim 2, characterized in that, The method further includes: When the Bluetooth paging process ends before the estimated paging timeout period, the coexistence management module is notified to resume the wake-up cycle.
4. The method according to claim 1, characterized in that, The instruction to the wireless local area network module to perform data transmission includes: The wireless LAN module is instructed to send non-data frames under preset transmission constraints.
5. The method according to claim 4, characterized in that, The instruction to the wireless local area network module to send non-data frames under preset transmission constraints includes: The time window for waiting for a response is divided into multiple micro-slots, and each micro-slot has a corresponding remaining time window. Within each micro-time slot, when the frame to be transmitted by the wireless local area network module is a non-data frame, and the estimated transmission time of the non-data frame meets the time limit of the remaining time window, and the current state of the wireless local area network module meets the preset interference conditions, the wireless local area network module is instructed to transmit the non-data frame.
6. The method according to claim 1, characterized in that, The acquisition of the micro-state of the Bluetooth paging process includes: Receive micro-state information reported by the Bluetooth controller; the micro-state information is obtained by the Bluetooth controller in real time by disassembling the Bluetooth paging process; The microstate information is analyzed to determine the current microstate of the Bluetooth paging process.
7. The method according to claim 1, characterized in that, The method further includes: Receive backoff signal; In response to the backoff signal, determine the type of frame that the wireless LAN module is currently transmitting; If an aggregate frame is currently being transmitted, the wireless LAN module is controlled to postpone the backoff action until the aggregate frame transmission is completed before relinquishing radio frequency resources. If a single frame is currently being transmitted, the wireless LAN module is controlled to immediately perform a backoff action.
8. The method according to claim 7, characterized in that, The method further includes: Detect whether the Bluetooth controller has experienced a loss of paging response; When the paging response is lost by the Bluetooth controller, the backoff delay and current channel state of the wireless LAN module are obtained. Calculate the dynamic compensation duration based on the backoff delay and the current channel state; The Bluetooth controller is controlled to increase the timeout for the next paging retry by the dynamic compensation duration.
9. A terminal device, characterized in that, include: Processor, memory, and bus; The processor and the memory are connected via the bus; The memory is used to store a program, and the processor is used to run the program, wherein the program is executed by the processor to perform the Bluetooth radio frequency coexistence scheduling method according to any one of claims 1 to 8.
10. A vehicle, characterized in that, Includes the terminal device as described in claim 9.
