Multifunctional low-power-consumption Bluetooth auxiliary control system

Abstract

The utility model discloses a kind of multifunctional low-power-consumption bluetooth auxiliary control system, and the system is equipped with optional bluetooth auxiliary control framework, with low-power-consumption bluetooth SoC as core, through single UART interface and whole vehicle main control MCU transparent communication, without invading original main control logic;Integrates PWM audio playback, HID non-inductive unlocking, bluetooth key identification, App business interaction and OTA upgrade function, adapts 24-100V whole vehicle wide voltage power supply, matches on-board inverted F antenna with SPI-Flash storage module, realizes function high integration.The utility model supports whole vehicle factory according to vehicle type matching, reduces cost, main control zero code changes can be plug and play, applicable to intelligent electric vehicle, two-wheeled vehicle bluetooth enhanced control scene.The utility model discloses a kind of multifunctional low-power-consumption bluetooth auxiliary control system.

Description

Technical Field

[0001] This utility model relates to the field of two-wheeled vehicle control technology, specifically to a multi-functional low-power Bluetooth auxiliary control system. Background Technology

[0002] With the development of intelligent transportation, the demand for functions such as Bluetooth interaction, contactless unlocking, audio prompts, and app integration in intelligent electric vehicles and two-wheeled vehicles is increasing. Current vehicle main control architectures on the market have some problems in terms of function integration, cost control, scalability, and after-sales maintenance, making it difficult to meet the diverse configuration needs of OEMs and the user experience requirements of end users. Existing technical solutions and problems include:

[0003] (I) Single MCU Main Control Architecture. The entire vehicle is equipped with only one main control MCU, which is responsible for all core logic such as drive control, battery management, and display interaction. Bluetooth communication, audio playback, and 433MHz key unlocking functions are all implemented through independent modules, each operating independently without unified control logic. Each module interacts with the main control MCU via interfaces such as UART, I2C, or GPIO. Different modules use their own communication protocols, and there is no unified standard protocol for data integration and management. The technical problems of this architecture include:

[0004] (1) Excessive main control load: The main control MCU needs to frequently respond to the interrupt requests of each independent module and parse serial port data of different protocols, which leads to a significant increase in CPU operating load, data processing delays, and affects the real-time performance of vehicle control.

[0005] (2) Redundancy of protocol stack: The Bluetooth module has its own independent MCU and runs the BLE (Bluetooth Low Energy) protocol stack, while the main control MCU needs to run the corresponding application protocol stack, resulting in redundant deployment of the protocol stack, wasting hardware resources and increasing system complexity.

[0006] (3) Poor real-time performance: Business data needs to go through a round-trip process of module serial port sending → main control receiving → logic processing → main control serial port feedback → module receiving. Data transmission and processing take a long time and may miss the best response window for vehicle control. For example, the delay in unlocking command may cause users to wait too long.

[0007] (4) Data consistency is difficult to guarantee: Information such as business data whitelist and OTA upgrade status are stored separately in the main control and each module. Differences in power failure timing can easily lead to data inconsistency. An additional handshake protocol needs to be designed for data synchronization, which further increases the complexity of the system.

[0008] (5) Limited function expansion: Each independent module adopts a closed firmware design, which makes it impossible to add functions such as voice control and multi-device concurrent connection according to needs, making it difficult to adapt to the end users' upgrade needs for intelligent interaction.

[0009] (6) Cumbersome after-sales maintenance: When upgrading the system, it is necessary to burn the main control MCU and independent modules such as Bluetooth and audio separately. Multiple sets of tooling equipment are required, the operation process is complicated and the working time is doubled, which increases the after-sales maintenance cost.

[0010] (II) Integrated Bluetooth Main Control Architecture. Using a Bluetooth SoC as the core main control unit for the entire vehicle, Bluetooth communication, audio processing, key recognition, and vehicle control functions are integrated into a single chip, forming an integrated design with single-chip vehicle control and Bluetooth enhancement. The Bluetooth SoC directly interfaces with the vehicle's actuators and interactive peripherals, eliminating the need for additional independent modules. This enables deep collaboration of functions such as Bluetooth key unlocking, remote vehicle control via App, and audio playback, resulting in good overall functional completeness and user experience. Technical challenges of this architecture include:

[0011] (1) High cost rigidity: OEMs need to purchase a full-function board that integrates all functions at once. Even for low-end models that only require basic key unlocking functions, they still need to pay for unnecessary functions such as audio amplifiers, radio frequency components, and protocol licensing fees, which significantly increases the production cost of the whole vehicle.

[0012] (2) Functions cannot be disassembled: The Bluetooth SoC and the basic vehicle control circuit are integrated on the same PCB board. The Bluetooth subsystem cannot be canceled separately. Functions are sold in a bundled manner. Redundant functions cannot be flexibly removed or removed according to vehicle configuration, resulting in poor adaptability.

[0013] (3) High functional redundancy: Low-end models only need to meet basic requirements such as key unlocking, but idle components such as audio amplifiers and external Flash are still soldered on the board, with an idle rate of more than 50%, resulting in a waste of hardware resources.

[0014] (4) High supply chain risk: The system relies on a single Bluetooth SoC chip. If the chip is out of stock or out of production, it will directly lead to the suspension of vehicle production. It is impossible to quickly resume production by replacing other modules, resulting in poor supply chain stability.

[0015] (5) High after-sales maintenance costs: When Bluetooth-related components such as the radio frequency front end are damaged, the entire main control board containing the vehicle control function needs to be replaced. The faulty components cannot be repaired individually, which significantly increases the after-sales maintenance costs for end users.

[0016] In summary, a technical solution is needed that can balance cost control, functional integration, flexible expansion, and convenient after-sales service to meet the development needs of intelligent electric vehicles and two-wheeled vehicles. Utility Model Content

[0017] To address the issues of poor real-time performance and difficult expansion of existing single-MCU main control architectures, as well as the high cost and risk of integrated Bluetooth main control architectures, this invention proposes a multi-functional low-power Bluetooth auxiliary control system through an optional Bluetooth auxiliary control architecture. The system includes an auxiliary control unit, a power supply link, a communication interface, and functional peripherals. The auxiliary control unit is a low-power Bluetooth SoC. The power supply link is electrically connected to the auxiliary control unit and provides stable power. The communication interface includes a UART interface and a BLE communication module, both connected to the auxiliary control unit. The auxiliary control unit communicates transparently with the vehicle's main control MCU via the UART interface. The functional peripherals are connected to the auxiliary control unit.

[0018] Preferably, the low-power Bluetooth SoC is the OM6626 BLE SoC, which integrates the full Bluetooth low-power protocol stack.

[0019] Preferably, it also includes a memory connected to the auxiliary control unit, wherein the memory is a P25Q SPI-Flash and is connected to the auxiliary control unit via an SPI0 interface.

[0020] Preferably, the power supply input voltage is the 24-100V constant vehicle power supply, which is successively reduced to 5V by a DC-DC converter, and then regulated to 3.3V by an LDO before supplying power to the auxiliary control unit and functional peripherals.

[0021] Preferably, the functional peripheral includes an audio channel; the audio channel consists of a PWM output terminal, an audio amplifier, and a speaker, and the PWM0 port of the auxiliary control unit is connected to the speaker via the audio amplifier.

[0022] Preferably, the functional peripheral includes an antenna; the antenna is an onboard inverted-F antenna, which is connected to the radio frequency terminal of the auxiliary control unit.

[0023] Preferably, the functional peripherals include a human-machine interface; the human-machine interface is a GPIO interface that can connect to buttons and LEDs.

[0024] Preferably, it includes a debugging and upgrade interface, wherein the debugging and upgrade interface leads out SWDIO and SWCLK signals through a surface mount socket.

[0025] The beneficial effects of this utility model are as follows:

[0026] (1) Cost controllability is significantly improved, adapting to the needs of multiple vehicle models. On-demand configuration reduces overall vehicle cost. The optional design allows OEMs to flexibly choose according to vehicle model configuration. Low-end models do not need to pay for redundant functions such as audio and contactless unlocking, while high-end models only need to add auxiliary control modules to achieve enhanced functions, avoiding the rigid cost of purchasing a full-function board at once in the traditional integrated architecture. This utility model integrates multiple functions such as audio playback, HID contactless unlocking, Bluetooth key management, and App interaction based on a single BLE SoC, reducing hardware procurement and production assembly costs.

[0027] (2) Strong compatibility, achieving zero-intrusion integration and aftermarket friendliness. The main control requires zero code modification, is plug-and-play, and interfaces with the vehicle's main control MCU via a transparent UART protocol. With a fixed baud rate and unified protocol format, it not only adapts to the rapid mass production of new models but can also be directly installed on existing models. The system adopts an independent module design, allowing end users to complete installation through simple wiring during the aftermarket phase, improving the flexibility of market promotion and user acceptance.

[0028] (3) Functional performance optimization to improve user experience and system reliability. Reduce the load on the main control module and enhance real-time response. The auxiliary control module independently undertakes all Bluetooth-related enhancement functions, reducing the CPU load on the main control module. Multiple security mechanisms ensure safe use. HID contactless unlocking adopts multiple protections such as RPA address resolution, IRK whitelist, and RSSI trend determination. Bluetooth key management supports time-limited authorization and real-time whitelist synchronization, ensuring vehicle use safety.

[0029] In summary, this utility model takes into account the requirements of low cost, high compatibility, strong performance, and easy expansion, thereby improving the user experience and the flexibility of function upgrades for end users. Attached Figure Description

[0030] Figure 1 This is a system block diagram of an embodiment of the present utility model;

[0031] Figure 2 This is a circuit diagram of an embodiment of the present invention. Detailed Implementation

[0032] The technical solutions of the present utility model will be clearly and completely described below with reference to the accompanying drawings of the embodiments. Obviously, the described embodiments are only some embodiments of the present utility model, and not all embodiments. Based on the embodiments of the present utility model, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the protection scope of the present utility model.

[0033] This embodiment discloses a multi-functional low-power Bluetooth auxiliary control system that can be applied to intelligent electric vehicle scenarios. It adopts an optional Bluetooth auxiliary control architecture and is positioned as a Bluetooth enhancement module of the main control MCU. It communicates transparently with the vehicle's main control through a single serial port without replacing or intruding on the original logic, achieving low cost, high integration, easy connection, scalability, and aftermarket-friendly performance.

[0034] The overall system architecture uses BLE SoC as an auxiliary control unit, such as... Figure 1 and Figure 2 As shown, a three-layer architecture of auxiliary control, main control, and peripherals is constructed. The auxiliary control unit is connected one-to-one with the vehicle's main control MCU via a UART interface. Externally, it integrates interactive peripherals such as Bluetooth key, mobile app, horn, buttons, and LEDs. Internally, it uses a transparent protocol to achieve data forwarding and status synchronization, forming a division of labor where the main control is responsible for core vehicle control, and the auxiliary control handles Bluetooth-related enhancement functions. The hardware of this embodiment consists of the following parts:

[0035] (I) Core Components. The core uses the OnMicro OM6626 BLE SoC, which has a built-in Cortex-M4F core with a main frequency multiplier of 64MHz. It integrates the full BLE 5.1 ​​protocol stack and can simultaneously carry out multiple tasks such as audio processing, key management, and wireless communication without the need for additional external function chips.

[0036] (ii) Power supply link. Adaptable to the wide voltage operating environment of electric vehicles, the input voltage covers the constant power supply of the vehicle from 24-100V. The voltage is first reduced to 5V by a DC-DC converter, and then regulated to 3.3V by an LDO to provide stable power supply for the SoC and other peripherals, ensuring reliable operation of the system under different voltage conditions.

[0037] (iii) Communication interface, including:

[0038] 1. UART interface: The baud rate is set to 115200. It adopts a transparent protocol design and achieves a one-to-one connection with the vehicle's main control unit. The main control unit can directly connect without modifying any code, achieving plug-and-play functionality.

[0039] 2. BLE Communication: Supports LE Secure Connection, adopts the proprietary BLE GATT protocol, has an MTU value of 247 bytes, supports packet transmission, and meets the needs of multi-device connection and large data volume interaction.

[0040] (iv) Functional peripherals, including

[0041] 1. Audio Channel: The audio signal is output from the PWM0 port inside the SoC, amplified by the LP43T1G audio amplifier, and then transmitted to the speaker to realize the audio playback function.

[0042] 2. Memory: Connects to P25Q32SH SPI-Flash via SPI0 interface to store data such as audio files, key whitelists, and user configurations, ensuring data is not lost after power failure.

[0043] 3. Antenna: It adopts an onboard inverted F antenna design, eliminating the need for external antenna components, simplifying the installation process and saving extra space.

[0044] 4. Human-machine interface: Reserved GPIO interface, which can be connected to buttons and LEDs for local function triggering and status indication; it also supports basic GPIO control functions such as saddle lock control, charging detection and control.

[0045] 5. Debugging and upgrade interface: SWDIO and SWCLK signals are brought out through a 0.5mm surface mount socket, supporting J-Link online debugging and BLE dual-image OTA upgrade, making production and after-sales maintenance convenient and efficient.

[0046] The embodiments of this utility model can achieve the following functions:

[0047] (I) PWM Audio Playback. Audio uses WAV format, supports SBC encoding and decoding, has a sampling rate of 32kHz, and a maximum capacity of 80KB per audio track. Storage employs a dual-zone header design, divided into a default zone and a user zone, each storing 24 audio tracks. These tracks are loaded into RAM index management upon power-up. Volume adjustment range is 0-100, controlled collaboratively by software coefficients and PWM duty cycle. It supports interrupted playback, loop playback, and combined playback. Combined playback is triggered sequentially via a linked list.

[0048] The audio download process involves the mobile app using SBC encoding to compress the audio file, transmitting it to the auxiliary control system via BLE, and then writing it to the SPI-Flash after CRC8 verification. The playback process involves the SoC decoding the stored audio file using SBC, directly outputting a 32kHz PWM signal via a built-in timer, amplifying it, and then playing it through the speaker. The mobile app allows for audio preview, settings, deletion, and synchronization.

[0049] (II) HID Seamless Unlock. Identity recognition is based on the LE Secure Connection protocol. A 16-byte identity resolution key (IRK) is captured in the pairing event GAP_EVT_BOND_INFO and written to the SPI-Flash whitelist table, supporting up to 8 mobile phones. Distance determination uses a 30-level RSSI threshold table, combined with Kalman filtering and least squares trend recognition. 50 RSSI data points are collected every 250ms, the first and last 30 points are removed, and the average is taken. After Kalman filtering, the slope is calculated using a 5-point sliding window.

[0050] The unlocking logic is as follows: when the sliding window slope is ≥ +0.8dB / point and the RSSI reaches the set threshold, it is determined that the phone is close, and the system notifies the main controller to unlock via UART; when the sliding window slope is < -0.8dB / point and the RSSI reaches the set threshold, it is determined that the phone is far away, and the main controller is notified to lock. The mobile app supports a "calibrate wherever you go" function, which can write the corresponding RSSI threshold level, and the module writes it to Flash in real time and it takes effect. The security mechanism adopts triple protection of RPA address resolution + IRK whitelist + trend judgment. Non-whitelisted devices are directly disconnected and do not enter the RSSI judgment process, preventing relay or spoofing attacks.

[0051] (III) Bluetooth Key Recognition. Recognition is achieved by parsing the Bluetooth key broadcast packet, sequentially completing MAC address matching and function bit verification before responding to button commands. The Bluetooth key lifecycle can be managed through a mobile app, supporting addition, deletion, sharing, and time-limited authorization operations. All changes are synchronized to the SPI-Flash in real time, and data is not lost after power failure.

[0052] The key supports 6 customizable functions including unlocking, locking, seat control, and vehicle location. Validity is determined by bitwise AND of a 6-bit function mask and key values; valid commands are directly forwarded to the main controller via UART. The system supports up to four keys online simultaneously, automatically prioritizing the key command with the strongest signal.

[0053] (iv) App Business Interaction. The App authentication and login process involves the system triggering a specific broadcast. After the App connects, it sends a password. The module stores the password and switches back to a normal broadcast. The App sends the same password again, and if the verification is successful, the login is complete. The password is retained even after power failure. The system supports more than 60 business commands, including audio management, key configuration, status query, parameter setting, and OTA upgrade, and can be flexibly expanded.

[0054] Status reporting uses the Notify Characteristic mechanism, which packages and pushes information such as connection status, login status, key status, lock status, volume, and battery level every second. Apps can receive these messages in real time after subscribing. OTA upgrades use an A / B dual-image design. The upgrade package is first received and verified via BLE. If the CRC check passes, an active flag is set. If the upgrade fails, it can automatically roll back to the original image, preventing system bricking.

[0055] (v) UART Master Control Communication. Data transmission adopts the forwarding path of "App-ble-uart-master control". The master control response data can be returned along the original path to achieve bidirectional transparent transmission. The system defines a unified proxy frame format. After the master control fills in information such as ACC status, lock status, and charging status, it is transparently transmitted by the auxiliary control module to the App for unpacking and display. The data format of the three terminals is consistent.

[0056] Supports MCU OTA upgrade proxy function. After the upgrade packet is received by BLE, it is forwarded to the main controller by the auxiliary control module via UART. At the same time, upgrade data can be cached through SPI-Flash. To ensure communication reliability, a frame sequence number identification and error retransmission mechanism is adopted. Each frame carries a 1B sequence number. If no acknowledgment is received within 100ms by the transmitting side timer, it will be retransmitted, with a maximum of 3 retransmissions. The receiving side will discard any duplicate sequence numbers.

[0057] The power supply link of this embodiment undergoes multi-stage voltage regulation to ensure stable operation in the complex voltage environment of electric vehicles. Optional features allow OEMs to flexibly select according to vehicle configuration requirements; low-end models may not require installation, while high-end models can be plugged and played. End users can also install it themselves during the aftermarket without replacing the vehicle controller, adapting to the diverse needs of both existing and new models.

[0058] It should be noted that the functions described in this embodiment require the cooperation of software and other related programs to be fully realized; the aforementioned software and other related programs are not the technical solutions claimed by this utility model and are not within the protection scope of this utility model.

[0059] In summary, this utility model takes into account the requirements of low cost, high compatibility, strong performance, and easy expansion. It not only meets the cost control and rapid adaptation of OEMs for multi-level models, but also improves the user experience and functional upgrade flexibility of end users, while reducing supply chain and after-sales risks, and has good industrial application value.

[0060] The above description is only a preferred embodiment of the present utility model. It should be noted that for those skilled in the art, several improvements and modifications can be made without departing from the technical principles of the present utility model, and these improvements and modifications should also be considered within the protection scope of the present utility model.

Claims

1. A multifunctional low-power Bluetooth auxiliary control system, characterized in that, It includes an auxiliary control unit, a power supply link, a communication interface, and functional peripherals; the auxiliary control unit is a low-power Bluetooth SoC, the power supply link is electrically connected to the auxiliary control unit and provides stable power supply, the communication interface includes a UART interface and a BLE communication module, both of which are connected to the auxiliary control unit; the auxiliary control unit communicates transparently with the vehicle's main control MCU through the UART interface; the functional peripherals are connected to the auxiliary control unit.

2. The multifunctional low-power Bluetooth auxiliary control system according to claim 1, characterized in that, The Bluetooth Low Energy SoC is the OM6626 BLE SoC, which integrates the full Bluetooth Low Energy protocol stack.

3. The multifunctional low-power Bluetooth auxiliary control system according to claim 1, characterized in that, It also includes a memory connected to the auxiliary control unit, which is a P25Q SPI-Flash and is connected to the auxiliary control unit via an SPI0 interface.

4. The multifunctional low-power Bluetooth auxiliary control system according to claim 1, characterized in that, The power supply input voltage is the constant 24-100V vehicle power, which is successively reduced to 5V by a DC-DC converter, and then regulated to 3.3V by an LDO before supplying power to the auxiliary control unit and functional peripherals.

5. The multifunctional low-power Bluetooth auxiliary control system according to claim 1, characterized in that, The functional peripherals include an audio channel; the audio channel consists of a PWM output terminal, an audio amplifier, and a speaker, and the PWM0 port of the auxiliary control unit is connected to the speaker via the audio amplifier.

6. The multifunctional low-power Bluetooth auxiliary control system according to claim 1, characterized in that, The functional peripheral includes an antenna; the antenna is an onboard inverted-F antenna, which is connected to the radio frequency terminal of the auxiliary control unit.

7. The multifunctional low-power Bluetooth auxiliary control system according to claim 1, characterized in that, The functional peripherals include a human-machine interface; the human-machine interface is a GPIO interface that can connect to buttons and LEDs.

8. The multifunctional low-power Bluetooth auxiliary control system according to claim 1, characterized in that, It includes a debugging and upgrade interface, which brings out the SWDIO and SWCLK signals through a surface mount connector.

Images