Radio frequency transceiver for bluetooth devices and method of operation thereof

By connecting the parameter register group and the timing calculation module via the hardware link, the Bluetooth RF transceiver was able to operate autonomously in broadcast, scan, and connected states. This solved the problems of frequent MCU wake-up and weak link synchronization fault tolerance in the existing technology, reduced power consumption, and improved link stability.

CN123074532APending Publication Date: 2026-11-10BEIJING ONMICRO ELECTRONICS CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202611230925.4
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2026-08-13
Publication Date
2026-11-10

AI Technical Summary

Technical Problem

Existing Bluetooth RF transceivers rely excessively on MCU intervention in broadcast, scan, and connected states, making them unable to adapt to low-power idle connection maintenance. The MCU needs to be frequently woken up to send empty data packets, resulting in weak link synchronization fault tolerance and high pressure on link connection parameter update interaction.

Method used

It adopts a hardware link connection parameter register group and a hardware link timing calculation module to complete the link timing calculation and parameter management independently of the MCU, including autonomous operation in broadcast mode, scan mode and connection mode, autonomously generating empty data packets, and hardware autonomously identifying link control messages and updating parameters.

Benefits of technology

It achieves deep MCU sleep mode, reduces invalid interrupt wake-up, lowers power consumption, improves link synchronization fault tolerance, reduces software interaction pressure for link connection parameter updates, and adapts to the low power consumption requirements of Bluetooth devices in all scenarios.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN123074532A_ABST
    Figure CN123074532A_ABST
Patent Text Reader

Abstract

Provided are a radio frequency transceiver for a Bluetooth device and an operating method thereof. The radio frequency transceiver for the Bluetooth device comprises a communication interface configured to be connected with a master micro controller (MCU); a hardware link connection parameter register group configured to be connected with the communication interface and to store link connection parameters, wherein in an initial configuration, the MCU writes the link connection parameters into the hardware link connection parameter register group through the communication interface; and a hardware link timing calculation module configured to solidify a Bluetooth protocol standard frequency hopping algorithm and a connection timing calculation formula, and to calculate timing parameters for subsequent link communication events independently of the MCU based on the link connection parameters stored in the hardware link connection parameter register group; wherein the MCU does not participate in the calculation of the timing parameters for the subsequent link communication events after the initialization configuration is completed; and wherein the subsequent link communication events include communication events in a broadcast state, a scanning state and a connection state.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This disclosure relates to the field of wireless communication technology, specifically to a radio frequency transceiver for Bluetooth devices based on the Bluetooth Low Energy (BLE) protocol and its operation method, and particularly to a low-power Bluetooth radio frequency transceiver capable of performing link timing calculations and management independently of the host microcontroller (MCU). Background Technology

[0002] Current mainstream Bluetooth RF transceivers typically communicate with the host microcontroller (MCU) via a serial interface (e.g., SPI, UART, or I2C). In this architecture, the RF transceiver is only responsible for signal modulation and demodulation, while all link timing control, packet acknowledgment, channel frequency hopping, and connection maintenance logic are managed by the MCU in real time. According to the Bluetooth protocol, broadcast scan requests (SCAN_REQ) and scan responses (SCAN_RSP), as well as connected uplink and downlink data exchanges, must complete message parsing and data rewriting within an extremely short fixed frame interval (T_IFS, typically 150μs). This places extremely high demands on the MCU's real-time interrupt response capability, serial interface transmission rate, and idle computing power.

[0003] Furthermore, existing RF transceivers lack hardware-autonomous link maintenance capabilities in connected mode, further exacerbating overall power consumption. Specifically, Bluetooth slave devices (e.g., mice, keyboards, sensors, passive wearables, etc.) are in an idle state with no service data transmission or reception for most of the operating time, only needing to periodically exchange empty data packets to maintain the link connection and avoid connection timeouts. In existing solutions, each connection event requires the MCU to be forcibly woken up to generate, fill, and send empty data packets within the T_IFS window. Even with the slave latency mechanism enabled, the generation of empty data packets and link timing scheduling still rely on MCU software execution. This high-frequency, periodic forced wake-up prevents the MCU from entering deep sleep mode, resulting in continuous static power consumption, becoming the core bottleneck hindering the high standby power consumption and low-power capabilities of existing BLE terminal devices.

[0004] Furthermore, existing RF transceivers lack the ability to autonomously calculate hardware link timing; all underlying timing parameters for connection events rely entirely on MCU computation and scheduling. This includes calculating the communication frequency for the next connection event, accurately activating the RF module's wake-up timestamp, determining the transmit / receive switching timing within a single connection event, and compensating for the offset of the link synchronization reference point—all underlying timing logic. The MCU must perform these tasks in advance, including computation and timing planning, and then issue configuration commands sequentially via the serial interface. These periodic underlying computation tasks are frequent and have stringent timing accuracy requirements, continuously consuming MCU core computing power. Even if the MCU is only briefly awakened, it cannot quickly return to sleep mode, thus continuously increasing the overall average power consumption of the system. Simultaneously, software timing calculations are highly prone to errors, leading to communication stability issues such as Bluetooth link synchronization anomalies and connection drops. Summary of the Invention

[0005] Technical issues

[0006] Against this backdrop, this disclosure aims to address the technical problem that existing RF transceivers for Bluetooth devices heavily rely on MCU intervention in broadcast, scan, and connected modes, making them unsuitable for the mainstream low-power idle-to-connection scenarios of Bluetooth devices. Specifically, existing solutions have the following inherent drawbacks:

[0007] During the idle keep-connect phase, the MCU must be continuously woken up: when there is no service data, the MCU still needs to periodically intervene to generate and send empty data packets for each connection event, and cannot enter a long-term deep sleep, resulting in high idle power consumption;

[0008] The entire set of link connection parameters depends on the MCU for real-time configuration: connection interval, connection delay, channel mapping, and channel frequency hopping timing are all calculated and issued by the software in real time. The MCU needs to run the Bluetooth link scheduling algorithm at high frequency, which consumes a lot of computing power.

[0009] Weak link synchronization fault tolerance: When airborne wireless interference causes link synchronization failure, each synchronization failure triggers an MCU interrupt and relies on software to adjust the receiving window. Frequent interrupts disrupt the MCU's sleep state.

[0010] The real-time interaction pressure for updating link connection parameters is high: When the host side dynamically issues link parameters such as channel mapping updates and connection interval updates, the MCU needs to parse the messages and rewrite the radio frequency configuration in real time, resulting in high interaction pressure.

[0011] Technical solution

[0012] To address the aforementioned shortcomings, this disclosure provides a radio frequency transceiver for Bluetooth devices and its operation method.

[0013] One aspect of the present invention provides a radio frequency transceiver for a Bluetooth device, comprising: a communication interface configured to connect to a master microcontroller (MCU); a hardware link connection parameter register group configured to connect to the communication interface and store link connection parameters, wherein, in an initial configuration, the MCU writes the link connection parameters into the hardware link connection parameter register group through the communication interface; and a hardware link timing calculation module configured to embed the Bluetooth protocol standard frequency hopping algorithm and connection timing calculation formula, and calculate timing parameters for subsequent link communication events independently of the MCU based on the link connection parameters stored in the hardware link connection parameter register group; wherein, after the initial configuration is completed, the MCU does not participate in the calculation of the timing parameters for the subsequent link communication events; wherein, the subsequent link communication events include communication events in broadcast state, scan state, and connected state.

[0014] Preferably, the hardware link connection parameter register group includes a general timing interval register and a general channel mask register. When the RF transceiver is in the broadcast state, the hardware link timing calculation module is further configured to autonomously perform broadcast transmission and response processing based on the broadcast timing parameters stored in the general timing interval register and the broadcast channel parameters stored in the general channel mask register. The execution of broadcast transmission and response processing includes: automatically sending broadcast messages pre-written by the MCU in the transmit buffer queue (TX FIFO) of the RF transceiver according to the broadcast timing parameters; waiting for a standard frame interval after sending the broadcast message and then switching to receive mode to listen for scan request messages; obtaining the device address in the scan request message and matching it with the device address in the broadcast message; and if the match is successful, automatically sending the scan response message pre-written by the MCU in the TX FIFO.

[0015] Preferably, when the RF transceiver is in the scanning state, the hardware link timing calculation module is further configured to autonomously perform scanning monitoring and connection establishment processing based on the scanning monitoring interval stored in the general timing interval register and the scanning monitoring channel parameters stored in the general channel mask register; wherein, the execution of scanning monitoring and connection establishment processing includes: periodically opening the RF receiving window based on the scanning monitoring interval, autonomously polling the corresponding RF frequency point based on the scanning monitoring channel parameters, and continuously monitoring the broadcast message; obtaining the device address in the broadcast message and matching it with the device address pre-written by the MCU in the connection establishment message in the TX FIFO; and if the match is successful, waiting for the standard frame interval, reading the connection establishment message, sending an over-the-air connection establishment command, and waking up the MCU to switch from the scanning state to the connection state.

[0016] Preferably, the RF transceiver is in the connected state, and the hardware link connection parameter register group further includes: a channel mapping register for storing a Bluetooth connection valid communication channel bitmap; a channel frequency hopping register for storing the Bluetooth protocol standard frequency hopping algorithm parameters; a connection interval register for storing the connection event period; a connection delay register for storing Bluetooth slave connection delay parameters; and an error threshold register for storing a synchronization failure count threshold and a connection timeout count threshold for synchronization failures.

[0017] Preferably, when there is service data interaction, the hardware link timing calculation module is further configured to: schedule the internal transmit / receive timing of the current connection event based on the link connection parameters stored in the channel frequency hopping register, the connection interval register, and the channel mapping register, including calculating the communication frequency point of the current connection event in real time and generating a wake-up timestamp; open a receive window according to the internal transmit / receive timing to receive downlink service data, and cache the downlink service data in the receive buffer queue (RX FIFO) in the radio frequency transceiver; if uplink service data pre-written by the MCU exists in the TX FIFO, then the uplink service data is sent within the current connection event; after all transmit / receive processes within the current connection event are completed, wake up the MCU to read the downlink service data in the RX FIFO.

[0018] Preferably, when there is no business data interaction, the hardware link timing calculation module is also configured to send empty data packets to maintain the link connection.

[0019] Preferably, when the Bluetooth device is a slave device, the hardware link timing calculation module is further configured to: based on the Bluetooth slave connection delay parameters stored in the connection delay register, skip unnecessary connection events and send the empty data packet only in necessary connection events to maintain the link connection.

[0020] Preferably, when the Bluetooth device is a host device, the hardware link timing calculation module is further configured to initiate downlink communication and listen for slave responses at each connection event.

[0021] Preferably, the hardware link timing calculation module is further configured to: receive and identify a link control message (PDU); obtain new link connection parameters included in the PDU and the update time point corresponding to the new link connection parameters; when the update time point arrives, use the new link connection parameters to update the link connection parameters stored in the hardware link connection parameter register group; and calculate the timing parameters for the subsequent link communication events based on the updated link connection parameters.

[0022] Preferably, the hardware link timing calculation module is further configured to: count the number of synchronization failures when the Bluetooth device is a slave device; count the number of connection timeouts when the Bluetooth device is a master device; and trigger an interrupt and wake up the MCU when the number of synchronization failures exceeds the synchronization failure count threshold stored in the error threshold register or the number of connection timeouts exceeds the connection timeout count threshold stored in the error threshold register.

[0023] Preferably, the TX FIFO is configured to contain messages to be sent pre-written by the MCU in the initial configuration, including broadcast messages, scan response messages, and connection establishment messages; the hardware link timing calculation module is further configured to directly read the pre-written messages to be sent from the TX FIFO in subsequent link communication events, without requiring the MCU to send the messages to be sent in real time.

[0024] Preferably, the communication interface is an SPI serial communication interface; and after the initial configuration is completed, if the RF transceiver is in the broadcast state or scan state, or in the connected state without service data interaction and without link abnormality, the hardware link timing calculation module automatically controls the SPI interface to shut down clock and data interaction, and there is no periodic data interaction between the MCU and the RF transceiver.

[0025] Preferably, the radio frequency transceiver is further configured to include a hardware empty data packet automatic generation module; wherein, the sending of empty data packets to maintain the link connection includes: when there is no service data interaction, the hardware empty data packet automatic generation module automatically generates standard BLE empty data packets, and the hardware link timing calculation module sends the standard BLE empty data packets to maintain the link connection, without the MCU filling the empty data packets.

[0026] Preferably, the hardware link timing calculation module is further configured to include a T_IFS hardware timing module; after the broadcast message is sent, the T_IFS hardware timing module automatically starts timing, and after the timing ends, it automatically switches the RF transceiver from the transmitting mode to the receiving mode without the MCU issuing a switching command.

[0027] Preferably, after the MCU is woken up to switch from the scanning state to the connected state, the hardware link timing calculation module is further configured to automatically identify whether the Bluetooth device in the connected state is a master device or a slave device, and automatically adapt the corresponding timing rules, channel frequency hopping logic and fault tolerance counting rules.

[0028] Preferably, the RF transceiver is compatible with the timing control module, FIFO management module, event management module, state management module, mode control module and flow control module included in the BLE SoC in terms of software and hardware, and the RF transceiver and the BLE SoC work together to achieve full hardware low power autonomous operation of the whole machine.

[0029] Preferably, after a synchronization failure, the process of skipping unnecessary connection events based on the Bluetooth slave connection delay parameters stored in the connection delay register is paused.

[0030] Beneficial effects

[0031] The radio frequency transceiver and its operating method disclosed herein have the following beneficial effects:

[0032] This solves the problem that traditional RF transceivers rely on the MCU for message parsing and response backfilling within the broadcast state T_IFS window, which limits interface speed and real-time computing power.

[0033] It solves the industry pain point that existing RF transceivers still require the MCU to continuously send empty data packets and cannot sleep for a long time during the idle delay phase of the connected state, and supports the MCU to enter deep sleep;

[0034] The entire set of BLE connection link parameters and underlying timing calculation logic are pushed down to the RF hardware. The hardware independently completes the calculation of the channel frequency point of the next connection event, the calculation of the precise RF wake-up timestamp, and the timing arrangement of connection event transmission and reception, completely eliminating the MCU.

[0035] Automatic hardware identification and register updates for link connection parameter updates or channel map update messages are achieved without software intervention;

[0036] A hardware synchronization failure counting fault tolerance mechanism is added, so that the MCU does not need to be woken up under slight wireless interference. An interrupt is only triggered when the synchronization failure exceeds the limit, minimizing invalid interrupt wake-up.

[0037] Differentiated link maintenance logic for master and slave devices is implemented. Slave devices support maintaining the connection with latency-free data packets, while the master device has no latency and automatically counts connection timeouts. One set of hardware can adapt to all scenarios of Bluetooth master and slave devices. Attached Figure Description

[0038] Figure 1 A block diagram of a Bluetooth radio frequency transceiver according to an embodiment of the present invention is shown.

[0039] Figure 2 A flowchart is shown in the broadcast state according to an embodiment of the present invention.

[0040] Figure 3 A flowchart illustrating the scanning state according to an embodiment of the present invention is shown.

[0041] Figure 4 A block diagram of the hardware link connection parameter register group in the connected state according to an embodiment of the present invention is shown.

[0042] Figure 5 A flowchart illustrating business data interaction in a connected state according to an embodiment of the present invention is shown.

[0043] Figure 6A A flowchart illustrating the hardware autonomously maintaining the link connection in slave connection state when there is no service data, according to an embodiment of the present invention, is shown.

[0044] Figure 6B A flowchart illustrating the hardware autonomously maintaining the link connection when there is no service data in the host connection state according to an embodiment of the present invention is shown.

[0045] Figure 7 A flowchart illustrating the automatic hardware update process for link connection parameters according to an embodiment of the present invention is shown.

[0046] Figure 8A A flowchart illustrating the hardware synchronization failure tolerance mechanism in slave mode according to an embodiment of the present invention is shown.

[0047] Figure 8B A flowchart illustrating the hardware connection timeout fault tolerance mechanism in host mode according to an embodiment of the present invention is shown. Detailed Implementation

[0048] Before proceeding with the detailed description below, it may be advantageous to define certain words and phrases used throughout this patent document. The terms “coupled,” “connected,” and their derivatives refer to any direct or indirect communication between two or more elements, regardless of whether those elements are physically in contact with each other. The terms “transmit,” “receive,” and “communicate,” and their derivatives cover both direct and indirect communication. The terms “comprising” and “including,” and their derivatives refer to, but are not limited to, those including. The term “or” is inclusive, meaning and / or. The phrase “associated with,” and its derivatives refer to, including, being contained within, interconnected, containing, being included in, connected or connected to, coupled or coupled to, communicating with, cooperating, intertwining, juxtaposed, proximate, bound or bound to, having, having attributes, having a relationship or being related to, etc. The term “controller” refers to any device, system, or part thereof that controls at least one operation. Such a controller may be implemented in hardware, or a combination of hardware and software and / or firmware. The functionality associated with any particular controller may be centralized or distributed, local or remote. The phrase "at least one" when used with a list of items means that different combinations of one or more of the listed items may be used, and that only one item from the list may be required. For example, "at least one of A, B, and C" includes any of the following combinations: A, B, C, A and B, A and C, B and C, A and B and C.

[0049] Definitions of other specific words and phrases are provided throughout this patent document. Those skilled in the art will understand that, in many, if not most, cases, such definitions apply to the prior and future use of the words and phrases thus defined.

[0050] In this patent document, the application combination of modules and the hierarchical division of sub-modules are for illustrative purposes only. Without departing from the scope of this disclosure, the application combination of modules and the hierarchical division of sub-modules can be in different ways.

[0051] Figure 1 A block diagram of a Bluetooth radio frequency transceiver 100 according to an embodiment of the present invention is shown.

[0052] like Figure 1 As shown, this embodiment provides a radio frequency transceiver 100 for a Bluetooth device. The radio frequency transceiver 100 mainly includes a communication interface 110, a hardware link connection parameter register group 120, a hardware link timing calculation module 130, and a data buffer queue 140.

[0053] The communication interface 110 (e.g., SPI, UART, or I2C) is configured to connect to the host microcontroller (MCU) for the MCU to perform initialization configuration and data exchange with the RF transceiver 100.

[0054] Hardware link connection parameter register group 120 is configured to connect to communication interface 110 for storing link connection parameters. During the initial configuration phase, the MCU writes the link connection parameters into hardware link connection parameter register group 120 via communication interface 110. It should be noted that "link connection parameters" in this application is a broad concept, encompassing all parameters required for communication events in broadcast, scan, and connection states, such as broadcast interval, scan interval, connection interval, and channel mapping bitmap.

[0055] According to an embodiment of the present invention, the hardware link connection parameter register group 120 may include a general timing interval register and a general channel mask register for storing link connection parameters related to timing and channel configuration in broadcast and scan states; and a channel mapping register, a channel frequency hopping register, a connection interval register, a connection delay register and an error threshold register for storing link connection parameters related to channel, timing, delay and fault tolerance configuration in the connection state.

[0056] The hardware link timing calculation module 130 is configured to natively embed the Bluetooth protocol standard frequency hopping algorithm and connection timing calculation formula. Based on the link connection parameters stored in the hardware link connection parameter register group 120, this module calculates the timing parameters for subsequent link communication events independently of the MCU. That is, the hardware link timing calculation module 130 can autonomously output the RF wake-up time, target communication frequency, and transmit / receive switching timing for the next connection event. After initialization and configuration, the MCU does not participate in calculating the timing parameters for subsequent link communication events, thus achieving autonomous hardware control over link timing.

[0057] The data buffer queue 140 may include a transmit buffer queue (TX FIFO) and a receive buffer queue (RX FIFO), and is configured to be connected to the hardware link timing calculation module 130 for caching pre-written messages to be sent by the MCU (such as broadcast messages, scan response messages, connection establishment messages, uplink / downlink service data) and received downlink service data.

[0058] Subsequent link communication events can include communication events in broadcast mode, scan mode, and connection mode. Therefore, the operating modes of the RF transceiver 100 can include: broadcast autonomous mode, scan autonomous mode, slave connection autonomous mode, and master connection autonomous mode, fully covering the entire lifecycle scenarios such as device broadcast standby, master scan connection establishment, connection with data exchange, and idle connection maintenance, completely eliminating the timing calculation pressure on the MCU.

[0059] According to embodiments of the present invention, the hardware link timing calculation module 130 may further include multiple built-in sub-modules. In broadcast and scanning states, it mainly includes: a hardware timing status module, responsible for automatically polling the channel according to the configured interval and channel mask, autonomously sending broadcast packets, or periodically opening a scanning reception window; and a hardware address matching module, responsible for hardware comparison of the device address in the air packet with the pre-stored packets in the TX FIFO. In the connected state, it mainly includes: a hardware packet identification module, responsible for receiving and identifying link control packets; a hardware parameter acquisition module, responsible for extracting new parameters and updating registers; a connection event timing module, responsible for autonomously aligning connection event timing; a hardware empty data packet automatic generation module, responsible for autonomously generating empty data packets to maintain link connection when there is no service data; a hardware synchronization monitoring module, responsible for counting synchronization failures and performing fault tolerance judgment in slave mode; and a hardware connection timeout monitoring module, responsible for counting connection timeouts and performing link disconnection judgment in master mode.

[0060] Figure 2 A flowchart 200 in broadcast mode is shown according to an embodiment of the present invention. Figure 2 As shown in the figure, this embodiment describes in detail the fully automatic operation logic and workflow of the radio frequency transceiver in broadcast mode.

[0061] In broadcast mode or broadcast standby, the RF transceiver adopts a hardware autonomous mode. The MCU only completes a one-time initialization configuration and does not need to intervene in any subsequent RF timing operations. Specifically, the MCU writes the link connection parameters into two multiplexed basic configuration registers: a general timing interval register and a general channel mask register. The hardware link timing calculation module autonomously performs broadcast transmission and response processing based on the broadcast timing parameters stored in the general timing interval register and the broadcast channel parameters stored in the general channel mask register. This includes: automatically sending broadcast messages pre-written by the MCU in the transmit buffer queue (TX FIFO) in the RF transceiver according to the broadcast timing parameters; switching to receive mode to listen for scan request messages after waiting for a standard frame interval after sending the broadcast message; obtaining the device address in the scan request message and matching it with the device address in the broadcast message; and if the match is successful, automatically sending a scan response message pre-written by the MCU in the TX FIFO.

[0062] According to an embodiment of the present invention, in broadcast mode, the hardware timing status module included in the hardware link timing calculation module automatically polls the channel according to the configured interval and channel mask, and autonomously sends broadcast packets. After sending, the hardware automatically waits for the standard T_IFS (150μs), switches the radio frequency to receive mode, and listens for air scan request packets. The hardware address matching module included in the hardware link timing calculation module directly compares the device address in the scan request. If the address does not match, the packet is discarded directly without generating any interruption. After the address matches successfully, the hardware waits for the T_IFS interval again, automatically reads the pre-stored scan response from the FIFO, and completes the response. The above operation is repeated until the channel polling is completed, at which point the radio frequency is turned off, and the above operation is repeated again when the waiting interval time point arrives. The entire broadcast cycle runs repeatedly, and the MCU can remain in deep sleep continuously. Only when the hardware captures the host sending a connection establishment message (CONNECT_IND) will a connection establishment interrupt be generated, waking up the MCU to complete the working mode switch and switch the radio frequency from broadcast mode to slave connection mode.

[0063] Specifically, such as Figure 2 As shown, the broadcast state workflow 200 includes the following steps:

[0064] Step S210: Initialize the MCU configuration once.

[0065] The MCU pre-writes standard broadcast messages (ADV_IND) and scan response messages (SCAN_RSP) into the transceiver's internal transmit buffer queue (TX FIFO) via the SPI interface (this example uses ADV_IND; the process is similar for other types of broadcast packets such as NON_CONNECT_IND, DIRECT_CONN_IND, and SCAN_IND). Then, it writes the link connection parameters into the hardware link connection parameter register group via the SPI interface. This initialization configuration is executed only once upon power-on or mode switching. It mainly includes: configuring the general timing interval register (a 32-bit read / write register): the MCU writes the broadcast transmission interval into this register, and the hardware link timing calculation module reads the broadcast timing parameters stored in this register to complete the timing calculation in conjunction with the hardware timer, eliminating the need for MCU software timing; configuring the general channel mask register (an 8-bit channel mask register): the MCU writes the broadcast channel mask into this register, and the hardware link timing calculation module reads the broadcast channel parameters stored in this register to configure the RF air scan listening frequency. After configuration, the MCU enters deep sleep and no longer issues any RF control commands.

[0066] Specifically, the broadcast state workflow includes the following steps:

[0067] Step S220: Hardware autonomous broadcast transmission.

[0068] The hardware link timing calculation module automatically sends broadcast messages (such as ADV_IND) pre-written in the TX FIFO of the RF transceiver by the MCU based on the broadcast timing parameters stored in the general timing interval register.

[0069] Step S230: Automatic timing switching and scan request reception.

[0070] After the broadcast message is sent, the T_IFS hardware timing module automatically starts timing with a standard 150μs frame interval. After the timing ends, the hardware automatically switches the radio frequency from transmit mode to receive mode without MCU instructions, and listens for uplink SCAN_REQ scan request messages in the air.

[0071] Step S240: Hardware address filtering and automatic response.

[0072] The hardware link timing calculation module obtains the device address in the scan request message and matches it with the device address in the broadcast message. If the address does not match, the message is discarded directly without generating an interrupt or waking up the MCU. After the address matches successfully, the hardware waits for another 150μs T_IFS interval, automatically switches to transmit mode, and reads the pre-stored SCAN_RSP message in the TX FIFO to complete the air response.

[0073] Step S250: Establish connection interrupt wake-up and loop.

[0074] The RF transceiver continuously listens for airborne packets. Upon capturing a connection establishment message from the host in broadcast mode, it generates a connection establishment interrupt to wake up the MCU and switches to slave connection mode. If no connection establishment message is captured, steps S220 to S240 are repeated.

[0075] Throughout the entire broadcast standby phase, the SPI interface is completely shut down except during the initialization phase, with no clock or data interaction. The MCU is not periodically interrupted to wake up, thus completely eliminating power consumption of the MCU and SPI interface during the broadcast phase.

[0076] Figure 3 A flowchart 300 in the scanning state according to an embodiment of the present invention is shown. Figure 3 As shown, this embodiment describes in detail the fully automatic operation logic and workflow of the radio frequency transceiver in scanning mode.

[0077] In scanning mode, the RF transceiver adopts a hardware autonomous mode. The MCU only completes a one-time initialization configuration and does not need to intervene in any RF timing operations afterward. Specifically, the MCU writes the link connection parameters into the two basic configuration registers mentioned above, namely the general timing interval register and the general channel mask register. The hardware link timing calculation module autonomously performs scanning listening and connection establishment processing based on the scan listening interval stored in the general timing interval register and the scan listening channel parameters stored in the general channel mask register. This includes: opening the RF receiving window periodically based on the scan listening interval; autonomously polling the corresponding RF frequency point based on the scan listening channel parameters; continuously listening to broadcast messages; obtaining the device address in the broadcast message and matching it with the device address in the connection establishment message (CONNECT_IND) pre-written by the MCU in the transmit buffer queue (TX FIFO); and if the match is successful, waiting for a standard T_IFS (150μs) frame interval, reading the pre-written connection establishment message, sending an over-the-air connection establishment command, and waking up the MCU to switch from scanning mode to connection mode.

[0078] In scan mode, the RF transceiver supports hardware-autonomous scanning, sharing a set of general timing interval registers and general channel mask registers with the broadcast mode. No additional register resources are required; the hardware automatically identifies the register meanings based on the current operating mode. The entire scan mode requires only one initialization configuration by the MCU, with subsequent processes entirely autonomous in hardware, requiring no real-time MCU intervention.

[0079] Specifically, the scan-state workflow includes the following steps:

[0080] Step S310: Initialize the MCU configuration once.

[0081] The MCU initializes and configures the general timing interval register and general channel mask register via the SPI interface. Specifically, it stores the scan-listening interval in the general timing interval register and the scan-listening channel parameters in the general channel mask register. Simultaneously, the MCU pre-writes the host connection establishment message into the TX FIFO. After configuration, the MCU shuts down the SPI interface and enters deep sleep mode.

[0082] Step S320: Autonomous periodic aerial scan.

[0083] The hardware timing status module in the hardware link timing calculation module opens the radio frequency receiving window periodically according to the scan listening interval stored in the general timing interval register; according to the scan listening channel parameters stored in the general channel mask register, it autonomously polls the corresponding radio frequency point and continuously listens for all slave broadcast messages in the air, such as the non-directional broadcast packet ADV_IND and the directional broadcast packet ADV_DIRECT_IND.

[0084] Step S330: Automatic address matching and filtering.

[0085] The hardware address matching module in the hardware link timing calculation module directly obtains the device address in the air broadcast message and compares it with the device address in the connection establishment message pre-stored in the TX FIFO. If the addresses do not match, the current broadcast message is discarded directly without generating any interruption or waking up the MCU. If the addresses match completely, it is determined that the target slave device has been scanned and the connection establishment response timing is immediately entered.

[0086] Step S340: Automatically send a connection establishment message and switch working modes.

[0087] After a successful address match, the hardware waits for the standard T_IFS frame interval, automatically reads the pre-stored connection establishment message from the TX FIFO, and completes the over-the-air connection establishment command transmission. After the connection establishment message is sent, a connection establishment interrupt is generated, waking up the MCU to complete the working mode switch, switching the radio frequency from scanning mode to connection mode. If the match is unsuccessful, steps S320 to S340 are repeated.

[0088] Throughout the entire scan cycle, the SPI interface remains completely shut down except during the initialization phase, with no clock or data interaction. The MCU experiences no periodic interrupts or wake-ups, completely eliminating power consumption by the MCU and SPI interface during the scan phase. This achieves full hardware autonomy in the scan state, completely removing the burden of scan scheduling, message matching, connection establishment, and packet sending from the Bluetooth host MCU during the scan phase.

[0089] Figure 4 A block diagram of a hardware link connection parameter register group 400 in the connected state according to an embodiment of the present invention is shown.

[0090] like Figure 4 As shown, when the RF transceiver is in the connected state, the hardware link connection parameter register group 400 (i.e., Figure 1 The hardware link connection parameter register group 120 shown further includes:

[0091] Channel mapping register 410 is used to store a bitmap of valid communication channels for Bluetooth connection. The hardware link timing calculation module uses this register to autonomously select available radio frequency channels, block invalid communication channels, and complete data transmission and reception only on valid channels, avoiding interference channels.

[0092] The channel frequency hopping register 420 stores the Bluetooth protocol standard frequency hopping algorithm parameters. Based on these parameters, the hardware link timing calculation module can automatically perform channel frequency hopping calculation and frequency switching for each connection event without the need for MCU intervention.

[0093] Connection interval register 430 is used to store connection event cycles. The hardware link timing calculation module, through its included connection event timing module, autonomously aligns or schedules connection event timing without requiring MCU software timing.

[0094] Connection delay register 440 is used to store Bluetooth slave connection delay parameters (corresponding to BLE slave latency parameters). Based on this, the hardware autonomously skips a preset number of idle connection events, reducing RF transceiver frequency and power consumption.

[0095] Error threshold register 450 stores the threshold for the number of synchronization failures and the threshold for the number of connection timeouts. The hardware link timing calculation module automatically identifies the current transceiver's working role, counts the number of RF synchronization failures in slave mode, and counts the number of connection event timeouts in master mode, and uses the value of this register as the maximum tolerance threshold; if the threshold is exceeded, the hardware directly determines that the link is abnormal and triggers an interrupt.

[0096] By adding the above 5 sets of dedicated registers, the hardware link timing calculation module integrated inside the RF transceiver can realize the full hardware-based fixed calculation of all connection timing, channel frequency hopping, and RF wake-up time. The MCU only needs to complete the initialization configuration once, and all subsequent underlying scheduling is completed autonomously by the hardware.

[0097] Figure 5 A flowchart 500 showing business data interaction in a connected state according to an embodiment of the present invention is shown.

[0098] According to an embodiment of the present invention, when there is service data interaction in the connected state, the hardware link timing calculation module is further configured to: schedule the internal transmit / receive timing of the current connection event based on the link connection parameters stored in the channel frequency hopping register, the connection interval register, and the channel mapping register, including real-time calculation of the communication frequency point of the current connection event and generation of a wake-up timestamp; open a receive window according to the internal transmit / receive timing to receive downlink service data, and buffer the downlink service data in the receive buffer queue (RX FIFO) in the radio frequency transceiver; if there is service data pre-written by the MCU in the TX FIFO, then send uplink data in the current connection event; after all transmit / receive processes in the current connection event are completed, wake up the MCU to read the downlink service data in the RX FIFO.

[0099] Specifically, the workflow when connected and there is business data interaction includes the following steps:

[0100] Step S510: Initialize the MCU configuration once.

[0101] After the connection is established, the MCU writes the relevant parameters into the hardware link connection parameter register group mentioned above all at once via the SPI interface. After this one-time initialization configuration is completed, the MCU enters sleep mode and disables the SPI interface.

[0102] Step S520: Connect event timing and channel autonomous scheduling.

[0103] The hardware link timing calculation module reads the relevant parameters stored in the channel frequency hopping register, connection interval register and channel mapping register. Through the link timing calculation module in the hardware link timing calculation module, it autonomously completes the real-time calculation of the next hop communication frequency, the generation of the precise wake-up timestamp of the RF module and the automatic scheduling of the internal transmit and receive timing of the connection event, without the need for the MCU to issue timing configuration instructions.

[0104] Step S530: Downlink service data reception and hardware buffering.

[0105] The receive window is automatically opened according to the internal transmit / receive timing to receive downlink service data sent by the host. After the downlink service data is received, the hardware directly buffers the data into the receive buffer queue (RX FIFO) in the RF transceiver, without the need for the MCU to handle it.

[0106] Step S540: Uplink business data is sent automatically.

[0107] The hardware automatically reads the data to be transmitted pre-written by the MCU from the TX FIFO and completes the uplink transmission. Therefore, if the MCU has service data to be transmitted, it only needs to write the data into the transmission buffer queue (TX FIFO) in advance. Within the current connection event, the hardware automatically reads the data from the TX FIFO and completes the uplink data transmission according to the Bluetooth link flow control rules, without the need for MCU intervention in the transmission timing.

[0108] Step S550: Batch interruption reporting and data backfilling.

[0109] After the entire transmission and reception process of the connection event is completed, the hardware generates a unified interrupt to wake up the MCU. The MCU reads the data in batches, fills in the data to be sent next, and then goes back to sleep.

[0110] After all transmit and receive processes within a single connection event are completed, the hardware generates a connection event interrupt to wake up the MCU. The MCU then reads downlink service data from the RX FIFO in batches via SPI, and can simultaneously fill the TX FIFO with data to be sent for the next connection event before entering sleep mode again.

[0111] Through the above process, during the connection state when there is business data interaction, the MCU only needs to configure the registers during initialization and process the data in batches after the event ends. The rest of the timing scheduling, frequency point calculation and transmit / receive control are all completed autonomously by the hardware, completely eliminating the MCU's periodic timing calculation tasks.

[0112] Figure 6A A flowchart 600A is shown illustrating how the slave device hardware autonomously maintains the link connection when there is no service data in the connected state according to an embodiment of the present invention.

[0113] When there is no service data interaction in the connected state, the hardware link timing calculation module is configured to autonomously generate and send empty data packets to maintain the link connection. In the slave connected state, the hardware enables the idle connection mechanism, which specifically includes the following steps:

[0114] Step S610: Read the connection delay parameters and determine whether it is a redundant connection event.

[0115] The hardware link timing calculation module reads the Bluetooth slave connection delay parameters stored in the connection delay register and autonomously determines whether the current connection event is a skippable idle connection event. Among them, the idle connection events determined to be skippable are redundant connection events, and the idle connection events that need to be retained to maintain the link are necessary connection events.

[0116] Step S620: Skip redundant connection events.

[0117] For redundant connection events that can be skipped, the hardware link timing calculation module skips them directly and does not perform RF transceiver operations to reduce power consumption.

[0118] Step S630: Generate and send an empty data packet automatically.

[0119] For necessary connection events that require maintaining the link, the hardware link timing calculation module automatically generates standard BLE empty data packets from hardware empty data packets, without the need for the MCU to participate in data filling; the hardware autonomously completes the transmission of empty data packets.

[0120] Step S640: Maintain link connection.

[0121] After completing the empty data packet exchange for the necessary connection events, the hardware maintains the link connection, and the MCU is not woken up throughout the process.

[0122] Throughout the entire idle period, the SPI interface remains in sleep mode and is turned off, and the MCU is never woken up, completely eliminating the dual power consumption overhead of the MCU and SPI interface caused by the periodic empty data packet interaction in traditional solutions.

[0123] Figure 6BA flowchart 600B is shown illustrating how the host device hardware autonomously maintains the link connection when there is no service data in the connected state according to an embodiment of the present invention.

[0124] When there is no service data in the connected state and the Bluetooth device is the master device, the hardware link timing calculation module is also configured to initiate downlink communication and listen for slave device responses in each connection event.

[0125] In host-connected mode, the hardware does not enable the connection latency skipping mechanism, specifically including the following steps:

[0126] Step S650: Actively initiate communication and listen for responses in each connection event.

[0127] The hardware link timing calculation module initiates downlink communication and listens for slave device responses in each connection event according to the parameters configured in the connection interval register and channel frequency hopping register.

[0128] Step S660: Mark the connection failure event.

[0129] The hardware connection timeout monitoring module in the hardware link timing calculation module continuously monitors the response message of each connection event. If no response message is received from the slave device for the corresponding connection event, a connection timeout is marked. Its counting logic is combined with the error threshold register for fault tolerance processing, as described in Figure 8.

[0130] Throughout the entire idle period, the SPI interface remains in sleep mode and is turned off, and the MCU is never woken up, completely eliminating the dual power consumption overhead of the MCU and SPI interface caused by the periodic empty data packet interaction in traditional solutions.

[0131] Figure 7 A flowchart 700 illustrating the automatic hardware update process for link connection parameters according to an embodiment of the present invention is shown.

[0132] The radio frequency transceiver according to an embodiment of the present invention can also automatically update link connection parameters. Specifically, the link timing calculation module is further configured to: receive and identify a link control message (PDU); obtain the new link connection parameters included in the PDU, and use the new link connection parameters to update the link connection parameters stored in the hardware link connection parameter register group; calculate timing parameters for subsequent link communication events based on the updated link connection parameters. Specifically, this includes the following steps:

[0133] Step S710: Receive and identify link control messages.

[0134] The hardware message recognition module included in the hardware link timing calculation module directly receives and recognizes link control messages (PDUs) at the physical layer, without requiring the MCU to parse the message content.

[0135] Step S720: Obtain the new link connection parameters and their update time.

[0136] The hardware parameter acquisition module included in the hardware link timing calculation module automatically acquires new link connection parameters and their corresponding update time points included in the PDU, such as new channel mapping, channel frequency hopping algorithm parameters, connection interval or connection delay, etc.

[0137] Step S730: Update the new parameters to the corresponding register at the update time point.

[0138] The hardware link timing calculation module updates the new parameters acquired to the corresponding registers in the hardware link connection parameter register group at the update time point, namely the channel mapping register, channel frequency hopping register, connection interval register, and connection delay register.

[0139] Step S740: Run the next connection event based on the updated parameters.

[0140] After the update is completed, the hardware link timing calculation module directly runs the next connection event based on the updated link connection parameters, without the need for SPI interaction or MCU intervention in parameter modification and timing adaptation.

[0141] With this hardware automatic update mechanism, the dynamic switching of connection parameters is completed entirely at the hardware level, which greatly improves the response speed and avoids the risk of timing misalignment that may be introduced by software intervention.

[0142] The Bluetooth RF transceiver according to an embodiment of the present invention can also autonomously perform synchronization failure statistics and fault tolerance processing. When the Bluetooth device is a slave device, it counts the number of synchronization failures; when the Bluetooth device is a master device, it counts the number of connection timeouts; and when the number of synchronization failures exceeds the synchronization failure count threshold stored in the error threshold register or the number of connection timeouts exceeds the connection timeout count threshold stored in the error threshold register, it triggers an interrupt and wakes up the MCU.

[0143] Figure 8A A flowchart 800A illustrating the hardware synchronization failure tolerance mechanism in slave mode according to an embodiment of the present invention is shown.

[0144] In slave mode, the hardware synchronization monitoring module included in the hardware link timing calculation module autonomously performs synchronization failure statistics and fault tolerance processing based on the error threshold register, specifically including the following steps:

[0145] Step S810: Count the number of consecutive synchronization failures.

[0146] In slave mode, the hardware synchronization monitoring module counts the number of RF signal synchronization failures in consecutive connection events in real time. Even if the slave has already started the connection event skipping logic, once a synchronization failure occurs, the hardware will pause the execution of the connection event skipping logic and will no longer skip subsequent connection events. Each time a synchronization failure occurs, the counter is incremented by 1; as soon as a synchronization is successful, the counter value is immediately reset to zero, and the system continues to operate according to the connection parameters in the connection parameter register group.

[0147] Step S820: Determine if the number of synchronization failures has exceeded the limit.

[0148] If step S820 determines that the number of synchronization failures has not exceeded the limit, then step S830 is executed: autonomously fine-tuning the receiving window to correct the deviation.

[0149] The hardware synchronization monitoring module compares the current number of synchronization failures with the synchronization failure threshold stored in the error threshold register. If the threshold is not exceeded, the hardware autonomously fine-tunes the receiving window to correct the synchronization deviation without generating an interrupt or waking up the MCU.

[0150] If the number of synchronization failures exceeds the limit in step S820, then step S840 is executed: determine the link is abnormal and trigger an interrupt.

[0151] If the number of synchronization failures exceeds the threshold, the hardware synchronization monitoring module determines that the wireless interference of the link is severe, immediately stops the timing scheduling of subsequent connection events, triggers a synchronization abnormality interrupt, and wakes up the MCU to perform subsequent processing.

[0152] Through the above mechanism, the slave device can autonomously repair itself without disturbing the MCU when it encounters instantaneous synchronization deviation, and only reports the anomaly when the accumulated error exceeds the tolerance, thus balancing power consumption and link reliability.

[0153] Figure 8B A flowchart 800B of the hardware connection timeout fault tolerance mechanism in host mode according to an embodiment of the present invention is shown.

[0154] In host mode, the hardware connection timeout monitoring module autonomously performs connection timeout statistics and link disconnection judgment based on the error threshold register, specifically including the following steps:

[0155] Step S840: Count the number of consecutive connection timeouts.

[0156] In master mode, the hardware connection timeout monitoring module does not execute connection event skipping logic. Each connection event actively initiates communication and listens for slave response messages within a preset receiving window. If no valid response is received within the window, the internal connection timeout counter automatically increments by 1, and the counter value is immediately reset to zero as soon as a synchronization is successful.

[0157] Step S850: Determine if the connection timeout limit has been exceeded.

[0158] If it is determined in step S850 that the number of connection timeouts has not exceeded the limit, then step S860 is executed: continue to maintain the connection link.

[0159] The hardware connection timeout monitoring module compares the number of consecutive connection timeouts with the connection timeout threshold stored in the error threshold register in real time. If the threshold is not exceeded, the hardware will automatically initiate the next connection event without MCU intervention.

[0160] If it is determined in step S850 that the number of connection timeouts has exceeded the limit, then step S870 is executed: the link is determined to be disconnected and an interrupt is triggered.

[0161] If the number of consecutive connection timeouts exceeds the threshold, the hardware connection timeout monitoring module determines that the link is completely disconnected, stops all connection timing scheduling, triggers a link disconnection interrupt, and wakes up the MCU.

[0162] Through the above mechanism, the host device can maintain the connection without interruption when the slave device is interfered with, and only reports the link disconnection when the continuous timeout reaches the threshold, avoiding frequent upper-layer intervention caused by instantaneous signal fluctuations and ensuring the robustness of the connection.

[0163] Although examples of specific implementation steps of a Bluetooth radio frequency transceiver are shown in the embodiments of the present invention, those skilled in the art should understand that the steps in the examples can be performed in the order shown, or in the reverse order or in parallel, without departing from the scope of the present invention.

[0164] Although this disclosure has been described with reference to exemplary embodiments, various changes and modifications may be suggested to those skilled in the art. This disclosure is intended to cover such changes and modifications that fall within the scope of the appended claims.

[0165] Any description in this invention should not be construed as implying that any particular element, step, or function is essential and must be included within the scope of the claims. The scope of the patent subject matter is defined only by the claims.

Claims

1. A radio frequency transceiver for a Bluetooth device, comprising: The communication interface is configured to connect to the host microcontroller (MCU); A hardware link connection parameter register group is configured to connect to the communication interface and store link connection parameters. In the initial configuration, the MCU writes the link connection parameters into the hardware link connection parameter register group via the communication interface. The hardware link timing calculation module is configured to embed the Bluetooth protocol standard frequency hopping algorithm and connection timing calculation formula, and calculates timing parameters for subsequent link communication events independently of the MCU based on the link connection parameters stored in the hardware link connection parameter register group. Wherein, after the initialization configuration is completed, the MCU does not participate in calculating the timing parameters used for the subsequent link communication events; The subsequent link communication events include communication events in broadcast state, scan state, and connection state.

2. The radio frequency transceiver according to claim 1, wherein, The hardware link connection parameter register group includes a general timing interval register and a general channel mask register, and When the radio frequency transceiver is in the broadcast state, the hardware link timing calculation module is also configured to autonomously perform broadcast transmission and response processing based on the broadcast timing parameters stored in the general timing interval register and the broadcast channel parameters stored in the general channel mask register. The execution of broadcast transmission and response processing includes: The broadcast message pre-written by the MCU in the transmit buffer queue (TX FIFO) of the RF transceiver is automatically sent according to the broadcast timing parameters. After sending the broadcast message, wait for the standard frame interval, then switch to receive mode to listen for scan request messages; Obtain the device address from the scan request message and match it with the device address from the broadcast message; and If a match is found, a scan response message pre-written by the MCU in the TX FIFO is automatically sent.

3. The radio frequency transceiver according to claim 2, wherein, When the radio frequency transceiver is in the scanning state, the hardware link timing calculation module is also configured to autonomously perform scanning monitoring and connection establishment processing based on the scanning monitoring interval stored in the general timing interval register and the scanning monitoring channel parameters stored in the general channel mask register. The execution of scanning, monitoring, and connection establishment processes includes: The radio frequency receiving window is opened periodically based on the scanning and monitoring interval, and the corresponding radio frequency point is automatically polled based on the scanning and monitoring channel parameters to continuously monitor the broadcast message. Obtain the device address from the broadcast message and match it with the device address pre-written by the MCU in the connection establishment message in the TX FIFO; and If a match is successful, wait for the standard frame interval, read the connection establishment message, send an over-the-air connection establishment command, and wake up the MCU to switch from the scanning state to the connection state.

4. The radio frequency transceiver according to claim 2, wherein, The radio frequency transceiver is in the connected state, and The hardware link connection parameter register group further includes: The channel mapping register is used to store the bitmap of valid communication channels for a Bluetooth connection. The channel frequency hopping register is used to store the Bluetooth protocol standard frequency hopping algorithm parameters; Connection interval register, used to store connection event cycles; Connection delay register is used to store Bluetooth slave connection delay parameters; The error threshold register stores the threshold number of synchronization failures and the threshold number of connection timeouts for synchronization failures.

5. The radio frequency transceiver according to claim 4, wherein, When there is business data interaction, the hardware link timing calculation module is also configured to: Based on the link connection parameters stored in the channel frequency hopping register, the connection interval register, and the channel mapping register, the internal transmit and receive timing of the current connection event is scheduled, including real-time calculation of the communication frequency point of the current connection event and generation of a wake-up timestamp; The receiving window is opened according to the internal transceiver timing to receive downlink service data, and the downlink service data is buffered in the receive buffer queue (RX FIFO) in the radio frequency transceiver. If the uplink service data pre-written by the MCU exists in the TX FIFO, then the uplink service data is sent within the current connection event; After all send and receive processes within the current connection event are completed, the MCU is woken up to read the downlink service data in the RX FIFO.

6. The radio frequency transceiver according to claim 4, wherein, When there is no business data interaction, the hardware link timing calculation module is also configured to send empty data packets to maintain the link connection.

7. The radio frequency transceiver according to claim 6, wherein, When the Bluetooth device is a slave device, the hardware link timing calculation module is further configured to: Based on the Bluetooth slave connection delay parameters stored in the connection delay register, unnecessary connection events are skipped and the empty data packet is sent only in necessary connection events to maintain the link connection.

8. The radio frequency transceiver according to claim 6, wherein, When the Bluetooth device is a host device, the hardware link timing calculation module is also configured to initiate downlink communication and listen for slave responses at each connection event.

9. The radio frequency transceiver according to claim 4, wherein, The hardware link timing calculation module is also configured to: Receive and identify link control messages (PDUs); Obtain the new link connection parameters included in the PDU and the update time point corresponding to the new link connection parameters; When the update time point arrives, the new link connection parameters are used to update the link connection parameters stored in the hardware link connection parameter register group; The timing parameters for the subsequent link communication events are calculated based on the updated link connection parameters.

10. The radio frequency transceiver according to claim 4, wherein, The hardware link timing calculation module is also configured to: When the Bluetooth device is a slave device, count the number of synchronization failures; When the Bluetooth device is a host device, count the number of connection timeouts; and When the number of synchronization failures exceeds the synchronization failure count threshold stored in the error threshold register, or when the number of connection timeouts exceeds the connection timeout count threshold stored in the error threshold register, an interrupt is triggered and the MCU is woken up.

11. The radio frequency transceiver according to claim 2, wherein, The TX FIFO is configured to receive messages pre-written by the MCU in the initial configuration, including broadcast messages, scan response messages, and connection establishment messages. The hardware link timing calculation module is also configured to directly read the pre-written message to be sent from the TXFIFO in the subsequent link communication event, without the MCU needing to send the message to be sent in real time.

12. The radio frequency transceiver according to claim 1, wherein, The communication interface is an SPI serial communication interface; and After the initial configuration is completed, if the RF transceiver is in the broadcast state or scan state, or in the connected state without service data interaction and without link abnormality, the hardware link timing calculation module automatically controls the SPI interface to shut down clock and data interaction, and there is no periodic data interaction between the MCU and the RF transceiver.

13. The radio frequency transceiver according to claim 6, wherein, The radio frequency transceiver is also configured to include a hardware empty data packet automatic generation module; The step of sending empty data packets to maintain the link connection includes: when there is no service data interaction, the hardware empty data packet automatic generation module automatically generates standard BLE empty data packets, and the hardware link timing calculation module sends the standard BLE empty data packets to maintain the link connection, without the MCU filling the empty data packets.

14. The radio frequency transceiver according to claim 2, wherein, The hardware link timing calculation module is also configured to include a T_IFS hardware timing module; after the broadcast message is sent, the T_IFS hardware timing module automatically starts timing, and after the timing ends, it automatically switches the RF transceiver from the transmitting mode to the receiving mode without the MCU issuing a switching command.

15. The radio frequency transceiver according to claim 3, wherein, After the MCU is woken up to switch from the scanning state to the connected state, the hardware link timing calculation module is also configured to automatically identify whether the Bluetooth device in the connected state is a master device or a slave device, and automatically adapt the corresponding timing rules, channel frequency hopping logic and fault tolerance counting rules.

16. The radio frequency transceiver according to claim 1, wherein, The radio frequency transceiver is compatible with the timing control module, FIFO management module, event management module, state management module, mode control module and flow control module included in the BLE SoC in terms of software and hardware. The radio frequency transceiver and the BLE SoC work together to achieve full hardware low power autonomous operation of the whole machine.

17. The radio frequency transceiver according to claim 7, wherein, The hardware link timing calculation module is also configured to: After a synchronization failure, the unnecessary connection event is skipped based on the Bluetooth slave connection delay parameters stored in the connection delay register.

18. A method of operating a radio frequency transceiver for a Bluetooth device, comprising: It connects to the main control microcontroller (MCU) via a communication interface; During the initial configuration phase, the MCU writes the link connection parameters into the hardware link connection parameter register group through the communication interface; Using the hardware link timing calculation module, the timing parameters for subsequent link communication events are calculated independently of the MCU based on the link connection parameters stored in the hardware link connection parameter register group. Wherein, after the initialization configuration is completed, the MCU does not participate in calculating the timing parameters used for the subsequent link communication events; The subsequent link communication events include communication events in broadcast state, scan state, and connection state.