WO2023206471A1

WO2023206471A1 - Wireless connection method for battery management device, and battery management device

Info

Publication number: WO2023206471A1
Application number: PCT/CN2022/090562
Authority: WO
Inventors: 程康; 翟江浪
Original assignee: 时代电服科技有限公司
Priority date: 2022-04-29
Filing date: 2022-04-29
Publication date: 2023-11-02
Also published as: CN117256116A

Abstract

Provided in the embodiments of the present application are a wireless connection method for a battery management device, and a battery management device, which can improve the connection performance of the battery management device. The wireless connection method for a battery management device comprises: performing wireless connection with or disconnection from a first device; detecting connection/disconnection state data with the first device; and according to the connection/disconnection state data, determining whether the wireless connection with or disconnection from the first device is normal. By means of the technical solution, after the battery management device is wirelessly connected to or disconnected from the first device, the battery management device detects the connection/disconnection state data between the battery management device and the first device, and determines, according to the connection/disconnection state data, whether the wireless connection/disconnection between the battery management device and the first device is normal, which facilitates the realization of the effective monitoring of a wireless connection/disconnection state between the battery management device and the first device, thereby improving the connection performance between the battery management device and the first device.

Description

Wireless connection method of battery management device and battery management device

Technical field

Embodiments of the present application relate to the field of batteries, and more specifically, to a wireless connection method of a battery management device and a battery management device.

Background technique

With the development of the times, electric vehicles have huge market prospects due to their high environmental protection, low noise, low use cost and other advantages, and can effectively promote energy conservation and emission reduction, which is beneficial to the development and progress of society. For electric vehicles, battery technology is an important factor related to their development.

Currently, batteries, electric vehicles, battery swap stations and other institutions can be equipped with battery management equipment, such as battery management unit (Battery Manager Unit, BMU), etc. The battery management equipment can be connected to other equipment and exchange information, for example, Battery management devices between different organizations can be connected to each other and exchange information to facilitate battery monitoring and management. When the connection performance between the battery management device and other devices is poor, the battery management effect of the battery management device will be affected, resulting in potential safety hazards for the battery. In view of this, how to improve the connection performance of battery management equipment is an urgent technical issue that needs to be solved.

Contents of the invention

Embodiments of the present application provide a wireless connection method and battery management device for a battery management device, which can improve the connection performance of the battery management device.

In a first aspect, a wireless connection method for a battery management device is provided, including: wirelessly connecting or disconnecting with a first device; detecting connection status data with the first device; and determining connection status with the first device based on the connection status data. Whether the wireless connection or disconnection between devices is normal.

Through the technical solutions of the embodiments of the present application, after the battery management device is wirelessly connected or disconnected from the first device, the battery management device detects the connection status data between it and the first device, and determines whether it is connected to the first device based on the connection status data. Whether the wireless connection between the first device is normal is conducive to effective monitoring of the wireless connection status between the battery management device and the first device, thereby improving the connection performance between the battery management device and the first device.

In some possible implementations, the battery management device includes: a wireless connection device; the connection status data includes: a first status identifier, and the first status identifier is used to indicate that the wireless connection device and the first device are connected or disconnected from each other. .

Through the technical solution of this embodiment, a wireless connection device is installed in the battery management device, and the first status identifier used to indicate that the wireless connection device and the first device are connected to or disconnected from each other are used as connection status data to determine the battery Whether the wireless connection between the management device and the first device is normal has high accuracy and is easy to implement through hardware and/or software.

In some possible implementations, the above-mentioned wireless connection or disconnection with the first device includes: the wireless connection device receives the connection request data; the wireless connection device wirelessly connects or disconnects with the first device according to the connection request data; the above-mentioned Detecting connection status data with the first device includes: the wireless connection device detects the first status identifier; judging whether the wireless connection or disconnection with the first device is normal based on the connection status data includes: wireless connection The connection device determines whether the wireless connection or disconnection with the first device is normal based on the first status identifier and the connection request data.

Through the technical solution of this embodiment, the wireless connection device detects the first state identifier used to indicate the connection state with the first device, and determines the connection with the first device based on the first state identifier and the connection request data. Whether the wireless connection or disconnection is normal is conducive to effective monitoring of the wireless connection status between the wireless connection device and the first device, thereby improving the connection performance between the battery management device and the first device.

In some possible implementations, the wireless connection device determines whether the wireless connection or disconnection with the first device is normal based on the first status identifier and the connection request data, including: the wireless connection device determines the first status identifier indication. Whether the connection status indicated by the connection request data is consistent with the connection request indicated by the connection request data; when the connection status indicated by the first status identifier is consistent with the connection request indicated by the connection request data, the wireless connection device determines that it is connected to the first device The wireless connection between the two devices is normal; when the connection state indicated by the first status identifier is inconsistent with the connection request indicated by the connection request data, the wireless connection device determines that the wireless connection with the first device is abnormal.

In the technical solution of this embodiment, by determining whether the connection status indicated by the first status identifier is consistent with the connection request indicated by the connection request data, the wireless connection or connection between the wireless connection device and the first device can be accurately determined. Is the disconnection normal? This technical solution is easy to implement and has high accuracy. It can not only accurately and effectively monitor the wireless connection between the wireless connection device and the first device, but can also be more conveniently implemented in the wireless connection device through hardware and/or software. middle.

In some possible implementations, when the wireless connection device determines that the wireless connection or disconnection with the first device is abnormal, the wireless connection method further includes: the wireless connection device performs at least one execution based on the connection request data. Wirelessly connect or disconnect with the first device; the wireless connection device detects the first status identifier at least once until the number of executions reaches a preset number or the connection status indicated by the first status identifier is consistent with the connection request indicated by the connection request data.

Through the technical solution of this embodiment, when there is an abnormality in the wireless connection between the wireless connection device and the first device, the wireless connection device itself can repair the abnormality, so that the wireless connection between it and the first device The connection is restored to the normal state, thereby further improving the connection reliability between the battery management device and the first device. Alternatively, when the wireless connection device repeatedly performs the wireless connection operation with the first device for a preset number of times and the abnormality cannot be repaired, the wireless connection device will not continue to repeatedly perform the wireless connection with the first device. Intermittent actions result in a waste of system resources and can also optimize the overall performance of the battery management device to a certain extent.

In some possible implementations, the wireless connection device includes a structure module and/or a non-volatile storage module; wherein, after the wireless connection device receives the connection request data, the wireless connection method further includes: the wireless connection device will disconnect Request data to be stored in the structure module and/or non-volatile storage module.

Through the technical solution of this embodiment, after the wireless connection device receives the connection request data, the connection request data can be written into the structure module in the memory, so that the structure module can be quickly accessed in the subsequent process. The connection request data in the wireless connection device is read and written, and the connection fault is repaired according to the connection request data, thereby improving the connection reliability between the wireless connection device and the first device. In addition, after the wireless connection device receives the connection request data, it can also store the connection request data in a non-volatile storage module, thereby preventing the loss of the connection request data caused by external reasons such as power outage and ensuring subsequent wireless connection. The connection device monitors the connection status with the first device, thereby further improving the connection reliability between the battery management device and the first device.

In some possible implementations, after detecting the first status identifier, the wireless connection method further includes: writing the first status identifier into the structure module and/or the non-volatile storage module.

Through the technical solution of this embodiment, after the wireless connection device detects the first status identifier, the first status identifier can also be written into the structure module in the memory, so that the structure module can be quickly updated in the subsequent process. Read and write the first status identifier in the device, and monitor the connection and disconnection status between the wireless connection device and the first device according to the first status ID, thereby improving the monitoring of the connection and disconnection status between the wireless connection device and the first device. efficiency. In addition, after the wireless connection device detects the first status identifier, the first status identifier can also be written into the non-volatile storage module to prevent the loss of the first status identifier caused by external reasons such as power outage and ensure that the wireless connection device can Monitoring performance of the connection status with the first device.

In some possible implementations, after the wireless connection device stores the connection request data in the non-volatile storage module, the wireless connection method further includes: after the battery management device is powered off and powered on again, the wireless connection device never The connection request data is read from the volatile storage module; the wireless connection device wirelessly connects or disconnects with the first device again according to the connection request data.

Through the technical solution of this embodiment, a non-volatile memory (NVM) module can be provided in the wireless connection device. After the wireless connection device receives the connection request data, the connection request data can be synchronously stored in the NVM module. After the battery management device is powered off and powered on again, the wireless connection device can read the connection request data from the NVM module, and automatically re-establish the wireless connection with the first device based on the connection request data, eliminating the need for The power outage of the battery management device affects the wireless connection between the battery management device and the first device, thereby improving the connection performance between the battery management device and the first device.

In some possible implementations, after the wireless connection device stores the first status identifier in the non-volatile storage module, the wireless connection method further includes: after the battery management device is powered off and powered on again, the wireless connection device is powered on from the non-volatile storage module. The first state identifier is read from the volatile storage module; wherein the wireless connection device wirelessly connects or disconnects with the first device again according to the connection request data, including: the wireless connection device according to the connection request data and the first state identifier , connect or disconnect wirelessly to the first device again.

Through the technical solution of this embodiment, after the battery management device is powered off and powered on again, the wireless connection device can read the first status identifier and connection request data from the NVM module, and use the first status identifier and connection request data based on the first status identifier and connection request data. The wireless connection with the first device is automatically re-established based on the disconnection request data. Therefore, through this technical solution, the impact of the power outage of the battery management device on the wireless connection between the battery management device and the first device can be automatically eliminated, and at the same time, it can also improve the automatic re-implementation of the wireless connection device and the first device. The reliability of the wireless connection is improved, thereby further improving the connection performance between the battery management device and the first device.

In some possible implementations, after the battery management device is powered off and on again, the connection request data read by the wireless connection device from the non-volatile storage module is connection request data; wherein the wireless connection device reads the connection request data according to the connection request data. The disconnection request data and the first status identifier are used to wirelessly connect or disconnect with the first device, including: determining whether the connection state indicated by the first status identifier is connected; when the connection state indicated by the first status identifier is connected , wirelessly connect with the first device again according to the connection request data.

Through the technical solution of this embodiment, when the connection state indicated by the first status indicator is connected, it means that the wireless connection device and the first device are connected to each other before the battery management device is powered off. At this time, the wireless connection device then performs a wireless connection with the first device according to the connection request data, which can improve the reliability of reconnection between the wireless connection device and the first device and restore the state between the wireless connection device and the first device. until the battery management device is powered off.

In some possible implementations, the connection status data also includes: a first information identifier, the first information identifier is used to indicate the execution status of wireless connection or disconnection between the wireless connection device and the first device; wherein, detecting the connection with the first device The connection status data between the two devices includes: the wireless connection device detects the first information identifier; and based on the connection status data, determines whether the wireless connection or disconnection with the first device is normal, including: the wireless connection device detects the first information according to the connection status data. mark, and determine whether the wireless connection or disconnection with the first device is normal.

Through the technical solution of this embodiment, the wireless connection device detects the first information identifier used to indicate the execution status of wireless connection or disconnection with the first device, and determines the wireless connection with the first device based on the first information identifier Or whether the disconnection is normal, it is helpful to realize the effective monitoring of the wireless connection status between the wireless connection device and the first device, thereby improving the connection performance between the battery management device and the first device.

In some possible implementations, the first information identifier is used to indicate whether the execution of wireless connection or disconnection with the first device is completed; wherein the wireless connection device determines the wireless connection with the first device according to the first information identifier. Or whether the disconnection is normal, including: the wireless connection device determines whether the execution of wireless connection or disconnection with the first device is completed according to the first information identifier; when the wireless connection or disconnection with the first device is not completed, the wireless connection device determines whether the wireless connection or disconnection with the first device is completed. The connection device determines that the wireless connection or disconnection with the first device is abnormal; when the wireless connection or disconnection with the first device is completed, the wireless connection device determines the wireless connection or disconnection with the first device is normal.

In the technical solution of this embodiment, the first information identifier is used to determine whether the wireless connection or disconnection with the first device is completed, which can assist in determining whether the wireless connection or disconnection between the wireless connection device and the first device is normal. While this technical solution can improve the connection performance between the wireless connection device and the first device, it can be more conveniently implemented in the wireless connection device through hardware and/or software.

In some possible implementations, when the wireless connection device determines that the wireless connection or disconnection with the first device is abnormal, the wireless connection method further includes: the wireless connection device performs the wireless connection with the first device at least once or disconnected; the wireless connection device detects the first information identifier at least once again until the first information identifier indicates that the wireless connection or disconnection with the first device is completed.

Through the technical solution of this embodiment, when there is an abnormality in the wireless connection between the wireless connection device and the first device, the wireless connection device itself can repair the abnormality, so that the wireless connection between it and the first device The connection is restored to the normal state, thereby further improving the connection reliability between the battery management device and the first device.

In some possible implementations, the wireless connection device includes: a state machine module and a wireless communication protocol stack module; wherein, wirelessly connecting or disconnecting with the first device according to the connection request data includes: the state machine module according to the connection request data, calling the wireless communication protocol stack module; the wireless communication protocol stack module performs wireless connection or disconnection with the first device to form a first information identifier, where the first information identifier is used to indicate that the wireless communication protocol stack module and the first device Implementation of wireless connection or disconnection.

Through the technical solution of this embodiment, the wireless connection device may include multiple software modules, where different software modules are used to perform different functions and can cooperate with each other. Utilizing the wireless communication protocol stack module to specifically implement wireless connection or disconnection with the first device, it is easy to monitor the execution actions of the wireless communication protocol stack module and generate a first information identifier, which can accurately reflect the relationship between the wireless connection device and the first device. The first device performs wireless connection or disconnection.

In some possible implementations, after wirelessly connecting with the first device, the wireless connection method further includes: the wireless connection device performing master-slave authentication with the first device.

Through the technical solution of this embodiment, the wireless connection device performs master-slave authentication with the first device to determine whether the wireless connection device and the first device can adapt to each other, thereby ensuring the subsequent communication between the wireless connection device and the first device. Normal data transmission improves system robustness.

In some possible implementations, the wireless connection device performs master-slave authentication with the first device, including: the wireless connection device receives a first message and a first random number sent by the first device, and the first message is used to indicate the Master-slave authentication of a device; the wireless connection device performs algorithm processing on the first random number to obtain the first target number; the wireless connection device sends a second message matching the first message and the first target number to the first device, So that the first device recognizes the second message, performs an algorithm check on the first target number, and determines the result of the master-slave authentication.

Through the technical solution of this embodiment, the master-slave authentication process is realized through the interaction of messages and data between the wireless connection device and the first device, which can achieve higher accuracy and facilitate the internal software of the wireless connection device and the first device. And/or hardware implements the master-slave authentication process.

In some possible implementations, the battery management device includes: a control device connected to the wireless connection device; wherein detecting the connection status data with the first device includes: the control device detects the first connection status of the wireless connection device. Status identification; judging whether the wireless connection or disconnection with the first device is normal according to the connection status data, including: the control device judging the wireless connection or disconnection between the wireless connection device and the first device according to the first status identification. Is it normal to open?

Through the technical solution of this embodiment, there is no need to modify the existing hardware of the battery management device. A wireless connection device is added to the battery management device, and the wireless connection device is controlled by the control device to realize the integration of the battery management device with the third device. Wireless connection between devices, this wireless connection method is relatively simple to implement and can be compatible with existing products. In addition, the control device of the battery management device can detect the first status identifier of the wireless connection device, and determine whether the wireless connection or disconnection between the wireless connection device and the first device is normal based on the first status identifier, which is beneficial to implementation Effectively monitor the wireless connection between the battery management device and the first device, thereby improving the connection performance between the battery management device and the first device.

In some possible implementations, wirelessly connecting or disconnecting with the first device includes: the control device obtains a connection request command, and the connection request command is used to instruct the wireless connection or disconnection between the battery management device and the first device. ; The control device converts the connection request command based on the first communication protocol into connection request data based on the second communication protocol, where the first communication protocol is different from the second communication protocol; sending the connection request data to the wireless connection device, So that the wireless connection device can wirelessly connect or disconnect with the first device according to the connection request data.

Through the technical solution of this embodiment, the control device can receive the connection request command based on the first communication protocol, and send the connection request data based on the second communication protocol to the wireless connection device. The control device and the external device can communicate with each other based on the first communication protocol, and the control device and the wireless connection device can communicate with each other based on the second communication protocol. Therefore, the control device can use different communication protocols for different devices or equipment, optimizing the communication performance between the control device and other devices, and improving the overall communication performance of the battery management device.

In some possible implementations, the control device determines whether the wireless connection or disconnection between the wireless connection device and the first device is normal based on the first status identifier, including: the control device determines whether the wireless connection or disconnection between the wireless connection device and the first device is normal based on the first status identifier and the connection request data, Determine whether the wireless connection or disconnection between the wireless connection device and the first device is normal.

Compared with the technical solution that only determines whether the wireless connection or disconnection between the battery management device and the first device is normal based on the first status identification of the wireless connection device, through the technical solution of this embodiment, the first status identification and the connection are combined. The two types of data, disconnection request data, are used to determine whether the wireless connection or disconnection between the wireless connection device and the battery management device where it is located and the first device is normal, which can further improve the accuracy of the judgment. Therefore, through the technical solution of this embodiment, the wireless connection monitoring between the battery management device and the first device can be more effectively implemented, thereby improving the connection performance between the battery management device and the first device.

In some possible implementations, the control device determines whether the wireless connection or disconnection between the wireless connection device and the first device is normal based on the first status identifier and the connection request data, including: the control device determines the first status identifier indication. Whether the connection status indicated by the connection request data is consistent with the connection request indicated by the connection request data; when the connection status indicated by the first status identifier is consistent with the connection request indicated by the connection request data, the control device determines that the wireless connection device is connected to the third connection request data. The wireless connection or disconnection between a device is normal; when the connection state indicated by the first status identifier is inconsistent with the connection request indicated by the connection request data, the control device determines the connection between the wireless connection device and the first device. The wireless connection or disconnection is abnormal.

In the technical solution of this embodiment, by determining whether the connection state indicated by the first status identifier is consistent with the connection request indicated by the connection request data, it is possible to accurately determine whether the wireless connection device and the battery management device where it is located are consistent with the first connection request. Whether the wireless connection or disconnection between devices is normal. This technical solution is easy to implement and has high accuracy. It can not only accurately and effectively monitor the wireless connection between the battery management device and the first device, but can also be easily implemented in the control device through hardware and/or software.

In some possible implementations, when the control device determines that the wireless connection or disconnection between the wireless connection device and the first device is abnormal, the wireless connection method further includes: the control device controls the wireless connection according to the connection request command. The device is wirelessly connected or disconnected with the first device at least once; the control device detects the first status identifier of the wireless connection device at least once until it is determined that the wireless connection or disconnection between the wireless connection device and the first device is normal.

Through the technical solution of this embodiment, when there is an abnormality in the wireless connection between the wireless connection device and the first device, the control device can repair the abnormality, so that the wireless connection between the battery management device and the first device The connection is restored to the normal state, thereby further improving the connection reliability between the battery management device and the first device.

In some possible implementations, the control device includes a non-volatile storage module. After the control device converts the connection request command into connection request data, the wireless connection method further includes: the control device stores the connection request data in a non-volatile storage module. Volatile memory module.

Through the technical solution of this embodiment, it is possible to prevent the loss of connection request data caused by external reasons such as power outages, and ensure that the subsequent control device can judge the abnormality of the wireless connection between the wireless connection device and the first device, thereby further improving the connection between the battery management equipment and the first device. The connection performance between the first devices.

In some possible implementations, wirelessly connecting or disconnecting with the first device includes: connecting or disconnecting with the first device via Bluetooth.

In the technical solution of this embodiment, the battery management device can perform Bluetooth connection and disconnection with the first device through the Bluetooth communication protocol to achieve subsequent data communication. This implementation method of Bluetooth connection can have the characteristics of low power consumption, low delay, and low cost, so it is more suitable to be installed in vehicles and/or battery swap stations to achieve short-distance, low-cost and reliable communication.

In some possible implementations, the battery management device is the master battery management unit MBMU in the powered device, and the first device is the slave battery management unit SBMU in the powered device; or, the battery management device is the charger in the power replacement device. The battery management unit CBMU, the first device is the slave battery management unit SBMU in the power replacement device; or the battery management device is the power replacement battery management unit TBMU in the power replacement device, and the first device is the master battery management unit in the power consumption device. Unit MBMU.

In the technical solution of this embodiment, the battery management device can be of multiple types and applied in different scenarios. Through this solution, a relatively stable wireless connection between TBMU and MBMU can be achieved, and/or a relatively stable wireless connection between CBMU/MBMU and SBMU can be achieved, thereby simplifying many aspects of power consumption equipment and/or power replacement equipment. A connection method between battery management devices to improve the connection stability and robustness of the entire system.

In a second aspect, a battery management device is provided, including: a wireless connection device. The wireless connection device includes: a first connection and disconnection module for wirelessly connecting or disconnecting with the first device; a first detection module for detecting and The connection status data between the first devices; the first processing module is used to determine whether the wireless connection or disconnection with the first device is normal based on the connection status data.

In some possible implementations, the battery management device further includes: a control device, the control device is connected to the wireless connection device, and the control device includes: a second detection module, used to detect the first status identifier of the wireless connection device; a second process A module configured to determine whether the wireless connection or disconnection between the wireless connection device and the first device is normal according to the first status identifier.

In a third aspect, a battery management device is provided, including: a processor and a memory, the memory is used to store a program, and the processor is used to call and run the program from the memory to execute the above first aspect or any possible implementation of the first aspect. wireless connection method.

A fourth aspect provides an electronic device, including: the battery management device in the above second or third aspect.

In some possible implementations, the electronic device is a power consumption device or a power exchange device.

Description of drawings

In order to explain the technical solutions of the embodiments of the present application more clearly, the drawings required to be used in the embodiments of the present application will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. Those of ordinary skill in the art can also obtain other drawings based on the drawings without exerting creative efforts.

Figure 1 is a schematic structural block diagram of a vehicle applicable to an embodiment of the present application;

Figure 2 is a schematic structural block diagram of a power swap station applicable to an embodiment of the present application;

Figure 3 is a schematic flow diagram of a wireless connection method for a battery management device provided by an embodiment of the present application;

Figure 4 is a schematic structural block diagram of a battery management device provided by an embodiment of the present application;

Figure 5 is a schematic flow chart of a wireless connection method provided by another embodiment of the present application;

Figure 6 is a schematic flow chart of a wireless connection method provided by another embodiment of the present application;

Figure 7 is a schematic flow chart of a wireless connection method provided by another embodiment of the present application;

Figure 8 is a schematic flow chart of a wireless connection method provided by another embodiment of the present application;

Figure 9 is a schematic flow chart of a wireless connection method provided by another embodiment of the present application;

Figure 10 is a schematic flow chart of a wireless connection method provided by another embodiment of the present application;

Figure 11 is a schematic flow chart of a wireless connection method provided by another embodiment of the present application;

Figure 12 is a schematic flow chart of a wireless connection method provided by another embodiment of the present application;

Figure 13 is a schematic flow chart of a wireless connection method provided by another embodiment of the present application;

Figure 14 is a schematic flow chart of a wireless connection method provided by another embodiment of the present application;

Figure 15 is a schematic flow chart of a wireless connection method provided by another embodiment of the present application;

Figure 16 is a schematic flow chart of a wireless connection method provided by another embodiment of the present application;

Figure 17 is a schematic flow chart of a wireless connection method provided by another embodiment of the present application;

Figure 18 is a schematic flow chart of a wireless connection method provided by another embodiment of the present application;

Figure 19 is a schematic flow chart of a wireless connection method provided by another embodiment of the present application;

Figure 20 is a schematic flow chart of a wireless connection method provided by another embodiment of the present application;

Figure 21 is a schematic flow chart of a wireless connection method provided by another embodiment of the present application;

Figure 22 is a schematic flow chart of a wireless connection method provided by another embodiment of the present application;

Figure 23 is a schematic flow chart of a wireless connection method provided by another embodiment of the present application;

Figure 24 is a schematic flow chart of a wireless connection method provided by another embodiment of the present application;

Figure 25 is a schematic flow chart of a wireless connection method provided by another embodiment of the present application;

Figure 26 is a schematic flow chart of a wireless connection method provided by another embodiment of the present application;

Figure 27 is a schematic structural block diagram of a battery management device provided by an embodiment of the present application;

Figure 28 is a schematic structural block diagram of a battery management device provided by another embodiment of the present application;

Figure 29 is a schematic structural block diagram of a battery management device provided by another embodiment of the present application;

Figure 30 is a schematic structural block diagram of an electronic device provided by an embodiment of the present application.

In the drawings, the drawings are not drawn to actual scale.

Detailed ways

The embodiments of the present application will be described in further detail below with reference to the accompanying drawings and examples. The detailed description of the following embodiments and the accompanying drawings are used to illustrate the principles of the present application, but cannot be used to limit the scope of the present application, that is, the present application is not limited to the described embodiments.

In the description of this application, it should be noted that, unless otherwise stated, "plurality" means more than two; the terms "upper", "lower", "left", "right", "inside", " The orientation or positional relationship indicated such as "outside" is only for the convenience of describing the present application and simplifying the description. It does not indicate or imply that the device or element referred to must have a specific orientation, be constructed and operated in a specific orientation, and therefore cannot be understood as a limitation of the present application. Application restrictions.

The term "and/or" in this application is just an association relationship describing associated objects, indicating that there can be three relationships, for example, A and/or B, which can mean: A exists, A and B exist simultaneously, and B exists these three situations. In addition, the character "/" in this application generally indicates that the related objects are an "or" relationship.

Unless otherwise defined, all technical and scientific terms used in this application have the same meanings as commonly understood by those skilled in the technical field of this application; the terms used in the specification of this application are only for describing specific implementations. The purpose of the examples is not intended to limit the application; the terms "including" and "having" and any variations thereof in the description and claims of the application and the above description of the drawings are intended to cover non-exclusive inclusion. The terms "first", "second", "third", etc. in the description, claims or drawings of this application are used to distinguish different objects, rather than to describe a specific order or primary-secondary relationship.

Reference in this application to "an embodiment" means that a particular feature, structure or characteristic described in connection with the embodiment may be included in at least one embodiment of the application. The appearances of this phrase in various places in the specification are not necessarily all referring to the same embodiment, nor are separate or alternative embodiments mutually exclusive of other embodiments. It will be explicitly and implicitly understood by those skilled in the art that the embodiments described herein may be combined with other embodiments.

In the field of new energy, the importance of batteries as the main power source for electrical devices, such as electric vehicles, ships or spacecrafts, is self-evident. In this application, a battery refers to a single physical module that includes one or more battery cells to provide higher voltage and capacity. The battery generally includes a case for enclosing one or more battery cells. Optionally, the battery mentioned in this application may be called a battery pack. Optionally, the battery can be any type of battery, such as: lithium-ion battery, lithium metal battery, lithium-sulfur battery, lead-acid battery, nickel separator battery, nickel-metal hydride battery, or lithium-air battery, etc.

During the battery operation, charging, and battery replacement processes, the real-time status of the battery needs to be monitored to improve the safety of the battery in the above processes. Therefore, according to actual needs, battery management equipment, such as a battery management unit (BMU), can be configured inside the battery, at the power consumption device, at the battery swap station, etc., to facilitate monitoring and management of the battery's operating status.

As an example, BMUs are configured inside both electric vehicles and batteries. The BMU in the electric vehicle can be called the Master Battery Manager Unit (MBMU), and the BMU configured inside the battery can be called the Master Battery Manager Unit (MBMU). It is the slave battery management unit (Slaver Battery Manager Unit, SBMU). In this example, the MBMU and the SBMU can be connected to each other and exchange information to jointly monitor and manage the operating status of the battery.

In some implementations, the MBMU and SBMU are connected to each other through physical wiring (for example: Controller Area Network (Controller Area Network, CAN) wiring). The installation method of this physical wiring on the two BMUs is relatively complex and affects manufacturing. and maintenance efficiency. In other implementations, the MBMU and the SBMU are connected through a wireless connection. In this wireless connection mode, the communication between the MBMU and the SBMU is easily affected by various factors such as the environment, so connection failures are prone to occur.

It can be understood that, in addition to the above-mentioned MBMU and SBMU, one or more BMUs will also be configured in the battery swap station. Various BMUs in the power swap station are also connected to each other, and/or the BMUs in the power swap station and the BMUs in the power devices are also connected to each other. Therefore, in the wireless connection mode, in addition to the above-mentioned MBMU and SBMU being prone to connection failures, , Connection failures are also more likely to occur between various BMUs in the power swap station, and/or between the BMUs in the power swap station and the BMUs in the power consumption devices.

In view of this, the present application provides a wireless connection method for battery management equipment. The wireless connection method is applied to the wireless connection device in the battery management equipment. The wireless connection method includes: receiving connection request data, and according to the connection request data, Wirelessly connect or disconnect with the first device, detect the first status identifier, the first status identifier is used to indicate the connection status with the first device, and determine the connection with the first device based on the first status identifier and the connection request data. Whether the wireless connection or disconnection between devices is normal. Through this technical solution, the first state identifier used to indicate the connection state with the first device is detected, and the wireless connection with the first device is determined based on the first state identifier and the connection request data. Or whether the disconnection is normal, it is helpful to effectively monitor the wireless connection status between the wireless connection device and the first device, thereby improving the connection performance between the BMU and the first device.

Figure 1 shows a schematic structural block diagram of a vehicle 1 to which the embodiment of the present application is applicable. The vehicle 1 may be a fuel vehicle, a gas vehicle or a new energy vehicle, and the new energy vehicle may be a pure electric vehicle, a hybrid vehicle or an extended-range vehicle, etc.

As shown in Figure 1, in the embodiment of the present application, a battery 10 is provided in the vehicle 1. The battery 10 can be used to power the vehicle 1. For example, the battery 10 can be used as an operating power supply for the vehicle 1 and for the circuit of the vehicle 1. The system is, for example, used for starting, navigation and operating power requirements of the vehicle 1 . In another embodiment of the present application, the battery 10 can not only be used as an operating power source of the vehicle 1 , but also can be used as a driving power source of the vehicle 1 , replacing or partially replacing fuel or natural gas to provide driving power for the vehicle 1 .

In order to facilitate monitoring the operating status of the battery 10 in the vehicle 1 , the battery 10 is provided with a slave battery management unit (SBMU) 110 . Corresponding to the SBMU 110 inside the battery 10, the vehicle 1 is also provided with a main battery management unit (MBMU) 120.

Specifically, the battery 10 may include at least one battery cell (or battery cell) 11 , and the at least one battery cell 11 is packaged in the same box to form a battery pack. In addition to the at least one battery cell 11, the box can also be provided with an SBMU 110 and other related components. The SBMU 110 is used to detect relevant status parameters of each battery cell 11 in the battery 10, such as voltage, current , temperature, state of charge (State of Charge, SOC), health state (State of Health, SOH), etc.

In addition to the battery 10, the vehicle 1 is provided with an MBMU 120 capable of communicating with the SBMU 110. The SBMU 110 can transmit the detected relevant parameters of the battery 10 to the MBMU 120, and the MBMU 120 can perform calculations and analysis on the data it receives, and transmit signals to the SBMU 110 to control and manage the SBMU 110.

In addition, in addition to the battery 10 and MBMU, the vehicle 1 is also provided with a vehicle controller 130, such as a vehicle controller (Vehicle Control Unit, VCU) or a domain controller (Domain Control Unit, DCU), etc., the MBMU 120 In addition to being able to communicate with the SBMU 110, it can also communicate with the vehicle controller 130. Specifically, the MBMU 120 can transmit relevant data of the battery 10 in the vehicle 1 to the vehicle controller 130.

Optionally, as shown in Figure 1, in some embodiments, the vehicle 1 may be provided with multiple batteries 10, and each battery 10 may be provided with a corresponding SBMU 110. In other words, the vehicle 1 may be provided with multiple batteries 110. Each SBMU 110 and MBMU 120 can establish communication connections with multiple SBMUs 110 at the same time to achieve control and management of multiple SBMUs 110.

It should be noted that the above FIG. 1 is only an example, illustrating that the vehicle 1 may be provided with a communication system formed by a vehicle controller 130, an MBMU 120 and a plurality of batteries 10. In other embodiments, the vehicle 1 may be provided with a communication system formed only by the vehicle controller 130 and a plurality of batteries 10 . For example, each battery 10 in the plurality of batteries 10 may be provided with a monitoring unit that monitors the battery cells 11 . The monitoring unit may establish a communication connection with the vehicle controller 130 so that the vehicle controller 130 can monitor the multiple batteries. 10. Control management.

Optionally, in addition to the traditional Cell To Pack (CTP) architecture, the battery 10 in the embodiment of the present application can also adopt the Cell To Chassis (CTC) architecture. At least one cell in the battery 10 is integrated into the chassis of the vehicle. In this case, the vehicle controller 130 in the vehicle 1 may be a domain controller that directly manages the battery 10 and even at least one cell in the battery 10 .

Figure 2 shows a schematic structural block diagram of a power swap station 2 applicable to the embodiment of the present application. The power swap station 2 can provide rapid battery replacement services for various types of vehicles such as passenger cars or heavy trucks, and the power swap station 2 can also include a charging bin 20 to charge the replaced batteries in the vehicle.

As shown in Figure 2, a plurality of batteries 10 can be provided in the charging compartment 20 of the battery swap station 2, wherein an SBMU 110 is provided in each battery 10. In order to facilitate the control and management of the plurality of SBMUs 110, the charging compartment 20 is also provided with at least one charging battery management unit (Charger Battery Manager Unit, CBMU) 210. As an example, each CBMU 210 in the charging compartment 20 can establish communication connections with a preset number of SBMUs 110, and control and manage the SBMUs 110. When the number of batteries 10 that can be accommodated in the charging compartment 20 is large, multiple CBMUs 210 can be installed in the charging compartment 20, and each CBMU 210 establishes communication with a preset number of SBMUs 110 to ensure that each SBMU 110 and its location are The battery 10 is effectively monitored and managed.

Continuing to refer to FIG. 2 , in the power swap station 2 , in addition to providing a charging compartment 20 to charge multiple batteries 10 , a station control system 21 is also provided. The station control system 21 can control multiple functional devices in the power swap station 2 to Execute the corresponding function. For example, the power swap station 2 includes a battery loading and unloading device (not shown in FIG. 2 ), and the station control system 21 can control the battery loading and unloading device to remove the battery 10 in a depleted state from the vehicle entering the power swap station 2 . , and install the battery 10 with sufficient power in the battery swap station to the vehicle.

Specifically, in the embodiment of the present application, the station control system 21 can establish a communication connection with at least one CBMU 210 in the charging compartment 20, thereby facilitating the station control system 21 to control multiple batteries 10 in the charging compartment 20 through the CBMU 210. Carry out control management.

As shown in Figure 2, in the battery swap station 2, in addition to the CBMU 210, a battery swap battery management unit (Transmission Battery Manager Unit, TBMU) 220 is also provided. When the vehicle 1 shown in Figure 1 enters the battery swap station 2, the TBMU 220 can establish a communication connection with the MBMU 120 in the vehicle 1, thereby facilitating information exchange between the TBMU 220 and the MBMU 120, and also facilitating the TBMU 220 to communicate with each other through the MBMU 120. The battery 10 on the vehicle 1 implements monitoring and management.

Further, in order to facilitate the station control system 21 to monitor and manage the battery 10 on the vehicle, the TBMU 220 also establishes a communication connection with the station control system 21. Therefore, the station control system 21 can monitor and manage the battery 10 on the vehicle 1 through the TBMU 220 and the MBMU 120.

Optionally, in the vehicle 1 and the battery swap station 2 shown in FIGS. 1 and 2 above, different types of BMUs can establish communication connections wirelessly to reduce the complexity of connection installation between different types of BMUs. In addition, in the power swap station 2, in order to ensure the reliability of communication between the station control system 21 and other components, the station control system can establish a communication connection with the CBMU 210 and/or TBMU 220 through a wired method.

FIG. 3 shows a schematic flow chart of a wireless connection method 300 for a battery management device provided by an embodiment of the present application.

As shown in Figure 3, in this embodiment of the present application, the wireless connection method 300 includes the following steps.

S310: Wirelessly connect or disconnect with the first device.

S320: Detect the connection status data with the first device.

S330: Determine whether the wireless connection or disconnection with the first device is normal based on the connection status data.

Optionally, in this embodiment of the present application, the first device may be any device configured to wirelessly connect with the battery management device 400 . In some embodiments, the first device and the battery management device 400 are two different types of battery management units.

Specifically, as an example, when the battery management device is the MBMU 120 or the main controller (such as the vehicle controller 130 in the above-mentioned vehicle 1) in the electrical device (such as the above-mentioned vehicle 1), the first device includes But it is not limited to the SBMU 110 in the electrical equipment (such as the above-mentioned vehicle 1).

As another example, in the case where the battery management device is the CBMU 210 in the power swapping device (such as the above-mentioned power swap station 2), the first device includes but is not limited to the SBMU in the power swap device (such as the above-mentioned power swap station 2). 110.

As a third example, in the case where the battery management device is the TBMU 220 in the power swapping device (such as the above-mentioned battery swapping station 2), the first device includes but is not limited to the MBMU 120 in the power-consuming device (such as the above-mentioned vehicle 1). .

Through the implementation of these examples, the battery management device can be of various types and applied in different scenarios. Through this solution, a relatively stable wireless connection between TBMU 220 and MBMU 120 can be achieved, and/or a relatively stable wireless connection between CBMU 210/MBMU 120 and SBMU 110 can be achieved, thereby simplifying electrical equipment and/or The connection method between various battery management devices in the battery swap equipment improves the connection stability and robustness of the entire system.

Optionally, in step S310, a wireless connection device, such as a wireless communication chip or the like, may be provided in the battery management device. The wireless connection device implements wireless connection or disconnection with the first device through a wireless protocol.

Optionally, in some implementations, step S310 may include: Bluetooth connection or disconnection with the first device. In this embodiment, the battery management device may be provided with a Bluetooth chip, which has a Bluetooth communication protocol stack. Through the Bluetooth chip, the Bluetooth connection between the battery management device and the first device can be realized using the Bluetooth communication protocol.

In this embodiment, the battery management device can perform Bluetooth connection and disconnection with the first device through the Bluetooth communication protocol to achieve subsequent data communication. The Bluetooth connection implementation method can have the characteristics of low power consumption, low delay, and low cost, so it is more suitable to be installed in the vehicle 1 and/or the battery swap station 2 to achieve short-distance, low-cost and reliable communication.

In steps S320 and S330, the battery management device may detect the connection status data between the battery management device and the first device. Based on the connection status data, the battery management device may determine whether the wireless connection between the battery management device and the first device is normal.

When the wireless connection between the battery management device and the first device is normal, the battery management device can achieve normal information interaction with the first device, ensuring the safe and effective operation of the device where the battery management device is located and the first device. On the contrary, when the wireless connection between the battery management device and the first device is abnormal, the wireless connection between the battery management device and the first device may be disconnected, which is not conducive to the implementation of the battery management device and the first device. Normal information exchange.

When the wireless disconnection between the battery management device and the first device is normal, the operating resources of the battery management device can be saved, the power consumption of the battery management device can be reduced, and the overall performance of the battery management device can be improved. On the contrary, when the wireless disconnection between the battery management device and the first device is abnormal, the wireless connection between the battery management device and the first device may be abnormally connected, which wastes the operating resources of the battery management device and increases The power consumption of the battery management device affects the overall performance of the battery management device.

FIG. 4 shows a schematic structural block diagram of a battery management device 400 provided by an embodiment of the present application. Optionally, the battery management device 400 may be the MBMU 120, CBMU 210 or TBMU 220 shown in Figures 1 and 2 above. The wireless connection method 300 shown in FIG. 3 above can be applied to the battery management device 400 shown in the embodiment of the present application.

As shown in Figure 4, the battery management device 400 includes: a wireless connection device 420. The wireless connection device 420 can implement wireless connections with other wireless devices. For example, the wireless connection device 420 can implement wireless connections with the wireless device in the first device. connect. As an example and not a limitation, the wireless connection device 420 may be a wireless communication chip in the battery management device 400 .

In the case where the battery management device 400 includes the wireless connection device 420, the above-mentioned connection status data may include: a first status identifier, the first status identifier is used to indicate that the wireless connection device and the first device are connected to or disconnected from each other. .

Optionally, the first status identifier may only be used to indicate that the wireless connection device 420 and the first device are connected to or disconnected from each other. Or, on this basis, the first status identifier can be further used to indicate other related connection status information between the wireless connection device 420 and the first device, such as connection time, number of connections, etc.

Optionally, in some embodiments, the wireless connection device 420 may have a wireless communication protocol stack, and the wireless connection device 420 may call the wireless communication protocol stack according to the connection request data to implement a wireless connection with the first device. or disconnected. After the wireless connection device 420 establishes a wireless connection with the first device, the first device can send a data packet to the wireless connection device 420. If the wireless connection device 420 receives the data packet sent by the first device within a preset time period, then The wireless connection device 420 may set the first status indicator to the mutual connection status. On the contrary, if the wireless connection device 420 does not receive the data packet sent by the first device within the preset time period, the wireless connection device 420 sets the first status indicator to the mutually disconnected state.

Optionally, the first status identifier may be a real-time updated identifier in the wireless connection device 420 , that is, the wireless connection device 420 may detect the connection status between itself and the first device in real time to detect the real-time updated first status. logo.

Through the technical solution of the embodiment of the present application, a wireless connection device is installed in the battery management device, and the first status identifier used to indicate that the wireless connection device and the first device are connected or disconnected from each other are used as connection status data to determine Whether the wireless connection between the battery management device and the first device is normal has high accuracy and is easy to implement through hardware and/or software.

Optionally, as shown in FIG. 4 , in some embodiments, in addition to the wireless connection device 420 , the battery management device 400 may also include: a control device 410 interconnected with the wireless connection device 420 . The control device 410 can send a command to the wireless connection device 420 to control the wireless connection device 420 to perform corresponding actions according to the command. As an example and not a limitation, the control device 410 may be a control chip of the battery management device 400 , for example, it may be a main control chip in the battery management device 400 .

FIG. 5 shows a schematic flow diagram of a wireless connection method 500 for a battery management device 400 provided by an embodiment of the present application. The wireless connection method 500 can be applied to the wireless connection device 420 in the battery management device 400 shown in FIG. 4. In other words, the execution subject of the wireless connection method 400 in the embodiment of the present application is the wireless connection device 420.

As shown in Figure 5, in this embodiment of the present application, the wireless connection method 500 includes the following steps.

S510: Receive connection request data.

S520: Wirelessly connect or disconnect with the first device according to the connection request data.

S530: Detect the first status identifier, which is used to indicate the connection state with the first device.

S540: Determine whether the wireless connection or disconnection with the first device is normal according to the first status identifier and the connection request data.

Specifically, in step S510 and step S520, the wireless connection device 420 may be configured to receive externally sent connection request data. The connection request data may include request data indicating a request type for connecting or disconnecting with the first device and information data indicating the first device. The information data used to indicate the first device includes but is not limited to: the location of the first device, the Media Access Control Address (MAC) of the first device, and so on. Further, the wireless connection device 420 can perform wireless connection or disconnection with the first device according to the relevant information in the connection request data, thereby realizing wireless connection or disconnection between the battery management device 400 and the first device.

Optionally, in some implementations, the battery management device 400 includes the control device 410 shown in FIG. 4 , and the control device 410 is connected to the wireless connection device 420 . In this case, for step S510, the wireless connection device 420 may receive the connection request data sent by the control device 410, where the connection request data is the data after the control device 410 processes the connection request command received by the control device 410. The connection request command is communication data based on the first communication protocol, the connection request data is communication data based on the second communication protocol, and the first communication protocol and the second communication protocol are two communication protocols of different types.

Specifically, in this embodiment, the control device 410 may be connected to an external device of the battery management device 400 based on a first communication protocol, and connected to the wireless connection device 420 through a second communication protocol. In this case, the control device 410 may receive a connection request command of the first data type sent by the external device based on the first communication protocol, and convert the connection request command of the first data type into a third connection request command based on the second communication protocol. The connection request data of the second data type is conveniently transmitted to the wireless connection device 420 smoothly. As an example and not a limitation, the first communication protocol may be a CAN protocol, and the second communication protocol may be a Serial Peripheral Interface (SPI) protocol.

In the technical solution of this embodiment, the control device 410 in the battery management device 400 receives the connection request command based on the first communication protocol, and sends the connection request data based on the second communication protocol to the wireless connection device 420 . The battery management device 400 and the external device can communicate with each other based on the first communication protocol. For example, the existing technology solution is still used to communicate with each other through the CAN protocol or other protocol methods, and the control device 410 receives the connection request command. After the conversion, the wireless connection device 420 can communicate with each other based on the second communication protocol. Therefore, this embodiment is compatible with the existing communication architecture of the battery management device 400, and the communication effect between the control device 410 and the wireless connection device 420 in the battery management device 400 is also better, thereby improving the overall communication performance of the battery management device 400. .

Alternatively, in other embodiments, the connection request data received by the wireless connection device 420 may not be sent by the control device 410 but directly sent by an external device. The wireless connection device 420 may directly respond to the connection request data. Perform connection or disconnection with the first device.

In step S530, the wireless connection device 420 detects a first status identifier, which may be used to indicate the connection status between the wireless connection device 420 and the first device. As mentioned above, optionally, the first status identifier may be used to indicate that the wireless connection device 420 and the first device are connected to or disconnected from each other. Alternatively, on this basis, the first status identifier may be further used to indicate other related connection status information between the wireless connection device 420 and the first device.

Optionally, in some embodiments, before step S530, the wireless connection method 500 further includes: the wireless connection device 420 determines whether the data packet sent by the first device is received within a preset time period; and the wireless connection The device 420 sets a first status identifier according to the judgment result; wherein, when a data packet sent by the first device is received within a preset time period, the first status identifier is used to indicate the interconnection with the first device. When a data packet sent by the first device is received within a preset time period, the first status identifier is used to indicate mutual disconnection from the first device.

Through the technical solution of this embodiment, the wireless connection device 420 can effectively set the first status indicator to indicate the connection status between it and the first device. Therefore, after setting the first status identifier, the wireless connection device 420 detects the first status identifier and determines whether the wireless connection with the first device is normal based on the first status identifier, which has higher reliability.

In step S540, the wireless connection device 420 may comprehensively determine whether the wireless connection or disconnection with the first device is normal based on the first status identifier and the connection request data. Compared with the technical solution that only determines whether the wireless connection or disconnection with the first device is normal based on the first state identifier, through the technical solution of this embodiment, the first state identifier and the connection request data are integrated, Determining whether the wireless connection or disconnection between the wireless connection device 420 and the first device is normal can further improve the accuracy of the determination.

In summary, through the technical solution of the embodiment of the present application, the wireless connection device 420 detects the first state identifier used to indicate the connection state with the first device, and combines the first state identifier and the connection request data to determine and Whether the wireless connection or disconnection between the first device is normal is helpful for the wireless connection device 420 to effectively monitor the wireless connection status with the first device, thereby improving the connection between the battery management device 400 and the first device. Connection performance.

FIG. 6 shows a schematic flow chart of a wireless connection method 600 for a battery management device 400 provided by an embodiment of the present application. The wireless connection method 600 is also applied to the wireless connection device 420 in the battery management device 400 shown in FIG. 4 above.

As shown in Figure 6, in this embodiment of the present application, the wireless connection method 600 includes the following steps.

S610: Receive connection request data.

S620: Wirelessly connect or disconnect with the first device according to the connection request data.

S630: Detect the first status identifier, which is used to indicate the connection state with the first device.

S641: Determine whether the connection status indicated by the first status identifier is consistent with the connection request indicated by the connection request data.

S642: When the connection state indicated by the first status identifier is consistent with the connection request indicated by the connection request data, determine that the wireless connection with the first device is normal.

S643: When the connection status indicated by the first status identifier is inconsistent with the connection request indicated by the connection request data, determine that the wireless connection with the first device is abnormal.

Specifically, in the embodiment of the present application, for the specific technical solution from step S610 to step S630, please refer to the relevant description of step S510 to step S530 in the embodiment shown in FIG. 5 above.

In addition, steps S641 to S643 in the embodiment of the present application may be an implementation manner of the above-mentioned step S540.

Specifically, in step S641, the first status identifier can be used to indicate that the current connection status of the wireless connection device 420 and the first device is mutual connection or mutual disconnection. The connection request data may include request data indicating a request type for indicating the wireless connection device 420 to connect or disconnect from the first device.

In step S642, if the connection status indicated by the first status identifier is consistent with the connection request indicated by the connection request data, the wireless connection device 420 may determine that the wireless connection with the first device is normal. For example, when the connection state indicated by the first status identifier is mutual connection, and the connection request indicated by the connection request data is also mutual connection, the wireless connection device 420 may determine that the wireless connection with the first device is normal.

Correspondingly, in step S643, if the connection state indicated by the first status identifier is inconsistent with the connection request indicated by the connection request data, the wireless connection device 420 may determine that the wireless connection with the first device is abnormal. For example, when the connection status indicated by the first status identifier is mutual disconnection, but the connection request indicated by the connection request data is mutual connection, the wireless connection device 420 may determine that the wireless connection with the first device is abnormal.

In the technical solution of the embodiment of the present application, by determining whether the connection status indicated by the first status identifier is consistent with the connection request indicated by the connection request data, the wireless connection between the wireless connection device 420 and the first device can be accurately determined. Whether the connection or disconnection is normal. This technical solution is easy to implement and has high accuracy. It can not only accurately and effectively monitor the wireless connection between the wireless connection device 420 and the first device, but can also more conveniently implement the wireless connection through hardware and/or software. in device 420.

Optionally, in some embodiments, the above-mentioned first status identifier is configured to: use a first value to indicate that the connection state with the first device is connected, and use a second value to indicate that the connection state with the first device is connected. The disconnection status is disconnected. The above-mentioned connection request data is configured to use a first numerical value to indicate that the connection request with the first device is a connection, and a second numerical value to indicate that the connection request with the first device is a disconnection.

In this implementation, step S641 in FIG. 6 may include: determining whether the first status identifier is consistent with the connection request data. Further, the above-mentioned step S642 may include: when the first status identifier is consistent with the connection request data, determining that the wireless connection with the first device is normal. The above step S643 may include: determining that the wireless connection with the first device is abnormal when the first status identifier is inconsistent with the connection request data.

As an example, the first value and the second value can be 0 and 1 respectively, which only need to occupy a small storage space and can effectively identify different connection states and connection requests. Of course, in other examples, the first numerical value and the second numerical value may also be other numerical values, which are not specifically limited in the embodiments of the present application.

Through the technical solution of this embodiment, the first status identifier and the connection request data use different values to represent different states and different requests. Therefore, the battery can be accurately determined by directly judging whether the first status identifier and the connection request data are consistent. Whether the wireless connection or disconnection between the management device and the first device is normal. This implementation method is the most convenient, and can reduce the storage space required by the first status identifier and connection request data in the wireless connection device 420, and improve the processing efficiency of the first status identifier and connection request data by the wireless connection device 420. .

FIG. 7 shows a schematic flow chart of a wireless connection method 700 for a battery management device 400 provided by an embodiment of the present application. The wireless connection method 700 is also applied to the wireless connection device 420 in the battery management device 400 shown in FIG. 4 above.

As shown in Figure 7, in the embodiment of the present application, the wireless connection method 700 includes steps S610 to S643 in the embodiment shown in Figure 6 above. Based on this, after determining the wireless connection with the first device Or when the disconnection is abnormal, the wireless connection method 700 may also include the following steps.

S750: Perform wireless connection or disconnection with the first device at least once according to the connection request data.

S760: Detect the first status identifier at least once until the number of executions reaches a preset number or the connection status indicated by the first status identifier is consistent with the connection request indicated by the connection request data.

Specifically, in this embodiment of the present application, when the wireless connection device 420 determines that the wireless connection with the first device is abnormal, the wireless connection device 420 may continue to perform at least one connection request based on the connection request data. The first device is connected or disconnected wirelessly to repair the abnormal wireless connection with the first device.

Specifically, each time the wireless connection device 420 performs wireless connection or disconnection with the first device, the wireless connection device 420 may re-detect the first state identifier, and determine whether it is connected to the first state identifier based on the newly detected first state identifier. Whether the wireless connection between the devices is normal.

The wireless connection device 420 re-executes wireless connection or disconnection with the first device at least once, and detects the first status identifier at least once until it is determined that the wireless connection with the first device is normal, that is, the wireless connection device 420 and the first device The abnormal wireless connection between the devices is repaired, or until the number of executions reaches a preset number, the wireless connection device 420 stops continuing to perform wireless connection or disconnection with the first device. As an example and not a limitation, the preset number may be less than or equal to 10, for example, the preset number may be 5.

When the number of executions reaches the preset number and the wireless connection device 420 cannot repair the abnormality, the wireless connection device 420 can send the abnormality information to the external device of the battery management device 400 so that the administrator can respond to the abnormality in a timely manner. Pay attention to and perform repairs on relevant parts.

Through the technical solution of the embodiment of the present application, when there is an abnormality in the wireless connection between the wireless connection device 420 and the first device, the wireless connection device 420 itself can repair the abnormality so that it can communicate with the first device. The wireless connection between the battery management device 400 and the first device is restored to a normal state, thereby further improving the connection reliability between the battery management device 400 and the first device. Alternatively, when the wireless connection device 420 repeatedly performs the wireless connection operation with the first device for a preset number of times and the abnormality cannot be repaired, the wireless connection device 420 will not continue to repeatedly perform the wireless connection operation with the first device. Wireless continuous actions cause a waste of system resources and can also optimize the overall performance of the battery management device 400 to a certain extent.

FIG. 8 shows a schematic flow chart of a wireless connection method 800 for a battery management device 400 provided by an embodiment of the present application. The wireless connection method 800 is also applied to the wireless connection device 420 in the battery management device 400 shown in FIG. 4 above.

As shown in Figure 8, in this embodiment of the present application, the wireless connection method 800 may include the following steps.

S810: Receive connection request data.

S820: Wirelessly connect or disconnect with the first device according to the connection request data.

S830: Detect the first status identifier, which is used to indicate the connection state with the first device.

S840: Every preset time period, determine whether the wireless connection or disconnection with the first device is normal according to the first status identifier and the connection request data.

In the embodiment of the present application, for the specific implementation of steps S810 to S830, please refer to the relevant description of steps S510 to S530 in Figure 5 above.

Step S840 may be an implementation of step S540 in Figure 5 above.

Specifically, in step S840, the wireless connection device 420 may determine whether the wireless connection or disconnection with the first device is normal according to the first status identifier and the connection request data every preset time period, so as to realize the connection with the first device. The continuous monitoring of the wireless connection between the first device ensures the reliability of the long-term wireless connection between the wireless connection device 420 and the first device.

As an example, the preset time period in the embodiment of the present application may be less than or equal to 1 ms. In other examples, the preset time period can also be adjusted according to actual conditions, and the embodiment of the present application does not limit the specific value of the preset time period.

FIG. 9 shows a schematic flow chart of a wireless connection method 900 for a battery management device 400 provided by an embodiment of the present application. The wireless connection method 900 is also applied to the wireless connection device 420 in the battery management device 400 shown in FIG. 4 above. Optionally, in this embodiment of the present application, the wireless connection device 420 may also include a structure module and/or a non-volatile memory (Non-Volatile Memory, NVM) module. The structure module can be located in the memory of the wireless connection device 420, so that the wireless connection device 420 can read and write the data in the structure module. In addition to being located in the wireless connection device 420 , the NVM module can also be located outside the wireless connection device 420 and connected to the wireless connection device 420 .

As shown in Figure 9, in this embodiment of the present application, the wireless connection method 900 may include the following steps.

S910: Receive connection request data.

S920: Write the connection request data into the structure module and/or NVM module.

S930: Wirelessly connect or disconnect with the first device according to the connection request data.

S940: Detect the first status identifier, which is used to indicate the connection state with the first device.

S950: Write the first status identifier into the structure module and/or NVM module.

S960: Determine whether the wireless connection or disconnection with the first device is normal according to the first status identifier and the connection request data.

In the embodiment of the present application, for the specific implementation of steps S910, S930, S940 and S960, please refer to the relevant description of steps S510 to S540 in Figure 5 above.

In step S920, after receiving the connection request data, the wireless connection device 420 can write the connection request data into the structure module in the memory, so that in the subsequent process, the connection request data in the structure module can be quickly processed. The connection request data is read and written, and the connection fault is repaired according to the connection request data, thereby improving the connection reliability between the wireless connection device 420 and the first device. In addition, after the wireless connection device 420 receives the connection request data, it can also store the connection request data in the NVM module. The NVM module is a storage module in which the data stored therein will not be lost after power failure. Therefore, after the connection request data is stored in the NVM module, the loss of the connection request data caused by external reasons such as power outage can be prevented, ensuring the monitoring performance of the subsequent wireless connection device 420 for the connection status with the first device, thereby further improving Connection reliability between the battery management device 400 and the first device.

Similarly, in step S950, after the wireless connection device 420 detects the first state identifier used to indicate the connection state with the first device, the first state identifier can also be written into the structure module in the memory. , so that in the subsequent process, the first status identifier in the structure module can be quickly read and written, and the connection status between the wireless connection device 420 and the first device can be monitored according to the first status identifier, The monitoring efficiency of the connection status between the wireless connection device 420 and the first device is improved. In addition, after the wireless connection device 420 detects the first state identifier used to indicate the connection state with the first device, the first state identifier can also be written into the NVM module to prevent the first state identifier from being caused by external reasons such as power outage. The loss of the status identifier ensures subsequent monitoring performance of the connection status between the wireless connection device 420 and the first device.

FIG. 10 shows a schematic flow chart of a wireless connection method 1000 for a battery management device 400 provided by an embodiment of the present application. The wireless connection method 1000 can also be applied to the wireless connection device 420 in the battery management device 400 shown in FIG. 4 above.

As shown in Figure 10, in this embodiment of the present application, the wireless connection method 1000 may include the following steps.

S1010: Receive connection request data.

S1020: Write the connection request data to the NVM module.

S1030: Wirelessly connect or disconnect with the first device according to the connection request data.

S1040: Detect the first status identifier, which is used to indicate the connection state with the first device.

S1050: Determine whether the wireless connection or disconnection with the first device is normal according to the first status identifier and the connection request data.

S1060: After the battery management device is powered off and powered on again, read the connection request data from the NVM module.

S1070: Wirelessly connect or disconnect with the first device again according to the connection request data.

In the embodiment of this application, for the specific implementation of steps S1010 to S1050, please refer to the relevant description of the embodiment in Figure 9 above.

In step S1060 and step S1070, after the battery management device 400 is powered off and powered on again, the wireless connection device 420 can read the connection request data stored before the power off from the NVM module, and reconnect according to the connection request data. Perform wireless connection or disconnection with the first device.

Through the technical solution of the embodiment of the present application, an NVM module can be provided in the wireless connection device 420. After the wireless connection device 420 receives the connection request data, the connection request data can be synchronously stored in the NVM module. In the battery management device After 400 is powered off and powered on again, the wireless connection device 420 can read the connection request data from the NVM module, and automatically re-implement the wireless connection with the first device based on the connection request data, eliminating battery management. The power outage of the device 400 affects the wireless connection between the battery management device 400 and the first device, thereby improving the connection performance between the battery management device 400 and the first device.

Optionally, in some implementations, after the above step S1040, the wireless connection method 1000 may further include: writing the first status identifier into the NVM module. On this basis, further, the above step S1060 may include: reading the connection request data and the first status identifier from the NVM module after the battery management device is powered off and powered on again. The above-mentioned step S1070 may include: wirelessly connecting or disconnecting with the first device again according to the connection request data and the first status identifier.

Optionally, in some embodiments, the wireless connection device 420 may determine whether the connection state indicated by the first status identifier is consistent with the connection request indicated by the connection request data. When the connection state indicated by the first status identifier is consistent with the connection request, If the connection request indicated by the connection request data is consistent, wireless connection or disconnection with the first device is performed according to the connection request data.

Through the technical solutions of the embodiments of the present application, after the battery management device 400 is powered off and on again, the wireless connection device 420 can read the first status identifier and the connection request data from the NVM module, and perform the operation according to the first status. The identification and connection request data automatically re-establish the wireless connection with the first device. Therefore, through this technical solution, the impact of the power outage of the battery management device 400 on the wireless connection between the battery management device 400 and the first device can be automatically eliminated, and at the same time, it can also improve the automatic re-implementation of the wireless connection device 420 and the first device. The reliability of the wireless connection between the devices further improves the connection performance between the battery management device 400 and the first device.

Figure 11 shows a schematic flow chart of a wireless connection method 1100 for a battery management device 400 provided by an embodiment of the present application. The wireless connection method 1100 can also be applied to the wireless connection device 420 in the battery management device 400 shown in FIG. 4 above.

As shown in Figure 11, in this embodiment of the present application, the wireless connection method 1100 may include the following steps.

S1110: Receive connection request data.

S1120: Write the connection request data to the NVM module.

S1130: Wirelessly connect or disconnect with the first device according to the connection request data.

S1140: Detect the first status identifier, which is used to indicate the connection state with the first device.

S1150: Write the first status identifier into the NVM module.

S1160: Determine whether the wireless connection or disconnection with the first device is normal according to the first status identifier and the connection request data.

S1170: After the battery management device is powered off and powered on again, read the connection request data and the first status identifier from the NVM module.

S1181: Determine whether the disconnection state indicated by the first status indicator is connected.

S1182: When the connection state indicated by the first status identifier is connected, wirelessly connect or disconnect with the first device again according to the connection request data.

When the connection status indicated by the first status indicator is disconnected, reconnection with the first device is not performed.

Optionally, in this embodiment of the present application, step S1110 may be an implementation of step S1010 in Figure 10 . When the connection request data is used to indicate a wireless connection with the first device, the connection request data may also be called connection request data.

In addition, in the embodiment of the present application, for the specific implementation of steps S1120 to S1170, please refer to the relevant description of the embodiment in Figure 10 above. Optionally, steps S1181 to S1182 may be an implementation of step S1070 in Figure 10 .

Specifically, in step S1181 and step S1182, the first status identifier can be used to indicate that the current connection status of the wireless connection device 420 and the first device is mutually connected or mutually disconnected. According to the first status identifier, the wireless connection device 420 can determine whether the connection state with the first device is connected before the battery management device 400 is powered off.

In step S1182, if the connection state indicated by the first status indicator is connected, it means that the wireless connection device 420 and the first device are connected to each other before the battery management device 400 is powered off. At this time, the wireless connection device 420 then performs a wireless connection with the first device according to the connection request data, which can improve the reliability of reconnection between the wireless connection device 420 and the first device, so that the wireless connection device 420 and the first device can The state is restored to before the battery management device 400 was powered off.

Optionally, in some embodiments, after the wireless connection device 420 wirelessly connects or disconnects with the first device again according to the connection request data, the above-mentioned wireless connection method 1000 or wireless connection method 1100 further includes: detecting again The first state identifier is used to determine again whether the wireless connection or disconnection with the first device is normal based on the first state identifier and the connection request data.

That is, in this embodiment, the wireless connection device 420 can repeatedly perform steps S1040 and S1050 shown in FIG. 10 above, or the wireless connection device 420 can also repeatedly perform steps S1140 to S1140 shown in FIG. 11 above. Step S1160, to continuously realize the detection of the first status identifier and the monitoring of the wireless connection between the wireless connection device 420 and the first device, so as to further continuously and effectively realize the wireless connection between the battery management device and the first device. Monitor the disconnection status, thereby improving the connection performance between the battery management device and the first device.

The above describes the relevant technical solution in which the connection state data includes the first state identifier in the embodiment of the present application with reference to FIGS. 5 to 11 . Optionally, in addition to the first status identifier, the connection status data may also include: a first information identifier, which is used to indicate the execution status of wireless connection or disconnection between the wireless connection device 420 and the first device. , according to the first information identifier, it can be determined whether the wireless connection between the wireless connection device 420 and the battery management device 400 where it is located and the first device is normal.

In this case, FIG. 12 shows a schematic flow chart of a wireless connection method 1200 of the battery management device 400 provided by the embodiment of the present application. The wireless connection method 1200 is also applied to the wireless connection device 420 in the battery management device 400 shown in FIG. 4 above.

As shown in Figure 12, in this embodiment of the present application, the wireless connection method 1200 may include the following steps.

S1210: Receive connection request data.

S1220: Wirelessly connect or disconnect with the first device according to the connection request data.

S1230: Detect the first information identifier, which is used to indicate the execution status of wireless connection or disconnection with the first device.

S1240: Determine whether the wireless connection or disconnection with the first device is normal according to the first information identifier.

Specifically, in the embodiment of the present application, for the specific implementation of step S1210 to step S1220, please refer to the relevant description of step S510 and step S520 in the embodiment shown in FIG. 5 above.

In step S1230, the wireless connection device 420 detects a first information identifier, which is used to indicate the execution status of wireless connection or disconnection between the wireless connection device 420 and the first device. Optionally, the first information identifier may be used to indicate whether the connection or disconnection between the wireless connection device 420 and the first device is completed. Alternatively, on this basis, the first information identifier may be further used to indicate other related connection and disconnection execution information between the wireless connection device 420 and the first device.

Optionally, in some embodiments, the wireless connection device 420 may have a wireless communication protocol stack, and the wireless connection device 420 may call the wireless communication protocol stack according to the connection request data to perform a wireless connection with the first device. or disconnected. The wireless connection device 420 may be provided with a first information identifier for indicating the execution status of the wireless communication protocol stack for wireless connection or disconnection with the first device.

Since the execution of the wireless connection or disconnection between the wireless connection device 420 and the first device will affect the subsequent actual state of the wireless connection or disconnection between the wireless connection device 420 and the first device, in step S1240, the wireless connection device 420 can perform the wireless connection or disconnection according to The above-mentioned first information identifier is used to determine whether the wireless connection or disconnection with the first device is normal, which is beneficial to effectively monitor the wireless connection status between the wireless connection device 420 and the first device.

In summary, through the technical solutions of the embodiments of the present application, the wireless connection device 420 detects the first information identifier used to indicate the execution status of wireless connection or disconnection with the first device, and determines the connection with the first device based on the first information identifier. Whether the wireless connection or disconnection between the two devices is normal will help the wireless connection device 420 effectively monitor the wireless connection status with the first device, thereby improving the connection performance between the battery management device 400 and the first device.

FIG. 13 shows a schematic flow diagram of a wireless connection method 1300 for a battery management device 400 provided by an embodiment of the present application. The wireless connection method 1300 is also applied to the wireless connection device 420 in the battery management device 400 shown in FIG. 4 above.

As shown in Figure 13, in this embodiment of the present application, the wireless connection method 1300 includes the following steps.

S1310: Receive connection request data.

S1320: Wirelessly connect or disconnect with the first device according to the connection request data.

S1330: Detect the first information identifier.

S1341: Based on the first information identifier, determine whether the execution of wireless connection or disconnection with the first device is completed.

S1342: When the wireless connection or disconnection with the first device is completed, determine that the wireless connection or disconnection with the first device is normal.

S1343: When the wireless connection or disconnection with the first device is not completed, determine that the wireless connection or disconnection with the first device is abnormal.

Specifically, in the embodiment of the present application, for the specific technical solution from step S1310 to step S1330, please refer to the relevant description of step S1210 to step S1230 in the embodiment shown in FIG. 12 above.

In addition, steps S1341 to S1343 in the embodiment of the present application may be an implementation manner of the above-mentioned step S1240.

Specifically, in step S1341, the first information identifier can be used to indicate whether the current wireless connection or disconnection between the wireless connection device 420 and the first device is completed. In step S1342, if the first information identifier indicates that the wireless connection device 420 completes the wireless connection or disconnection with the first device, the wireless connection device 420 may determine that the wireless connection with the first device is normal. Correspondingly, in step S1343, when the first information identifier indicates that the wireless connection or disconnection between the wireless connection device 420 and the first device has not been completed, the wireless connection device 420 may determine the wireless connection with the first device. is abnormal.

In the technical solution of the embodiment of the present application, the first information identifier is used to determine whether the wireless connection or disconnection with the first device is completed, which can assist in determining the wireless connection or disconnection between the wireless connection device 420 and the first device. Is it normal. While this technical solution can improve the connection performance between the wireless connection device 420 and the first device, it can be more conveniently implemented in the wireless connection device 420 through hardware and/or software.

Optionally, in some embodiments, the above-mentioned first information identifier may be configured to: use a first value to indicate the completion of wireless connection or disconnection with the first device, use a second value to indicate the completion of wireless connection or disconnection with the first device. The disconnected execution is not completed.

As an example, the first value and the second value can be 0 and 1 respectively, which only need to occupy a small storage space and can effectively identify different execution states. Of course, in other examples, the first numerical value and the second numerical value may also be other numerical values, which are not specifically limited in the embodiments of the present application.

Or, in other embodiments, whether the first information identifier is updated is used to indicate whether the execution of wireless connection or disconnection with the first device is completed. In this embodiment, the above step S1341 may include: determining whether the first information identifier is Update to determine whether the execution of wireless connection or disconnection with the first device is completed. Specifically, if the first information identifier is updated, it is determined that the wireless connection or disconnection with the first device is completed; conversely, if the first information identifier is not updated, it is determined that the wireless connection or disconnection with the first device is completed. The execution is not completed.

Through the technical solution of this embodiment, the update of the first information identifier can be used to determine whether the wireless connection or disconnection with the first device is completed. The determination process is very convenient and simple to implement, and can improve the connection between the wireless connection device 420 and the third device. Monitoring efficiency of wireless connection status between devices.

FIG. 14 shows a schematic flow diagram of a wireless connection method 1400 for a battery management device 400 provided by an embodiment of the present application. The wireless connection method 1400 is also applied to the wireless connection device 420 in the battery management device 400 shown in FIG. 4 above.

As shown in Figure 14, in the embodiment of the present application, the wireless connection method 1400 includes steps S1310 to S1343 in the embodiment shown in Figure 13 above. On this basis, after determining the wireless connection with the first device Or when the disconnection is abnormal, the wireless connection method 1400 may also include the following steps.

S1450: Perform wireless connection or disconnection with the first device at least once according to the connection request data.

S1460: Detect the first information identifier at least once again until the first information identifier indicates that the wireless connection or disconnection with the first device is completed.

Specifically, each time the wireless connection device 420 performs wireless connection or disconnection with the first device, the wireless connection device 420 may re-detect the first information identifier, and determine whether it is related to the third information identifier based on the newly detected first information identifier. Whether the wireless connection between the devices is normal.

The wireless connection device 420 re-executes wireless connection or disconnection with the first device at least once, and detects the first information identifier at least once, until the first information identifier indicates that the wireless connection between the wireless connection device 420 and the first device is normal, that is, the The wireless connection abnormality between the wireless connection device 420 and the first device is repaired.

Through the technical solution of the embodiment of the present application, when there is an abnormality in the wireless connection between the wireless connection device 420 and the first device, the wireless connection device 420 itself can repair the abnormality so that it can communicate with the first device. The wireless connection between the battery management device 400 and the first device is restored to a normal state, thereby further improving the connection reliability between the battery management device 400 and the first device.

FIG. 15 shows a schematic flow diagram of a wireless connection method 1500 for a battery management device 400 provided by an embodiment of the present application. The wireless connection method 1500 is also applied to the wireless connection device 420 in the battery management device 400 shown in FIG. 4 above.

As shown in Figure 15, in this embodiment of the present application, the wireless connection method 1500 may include the following steps.

S1510: Receive connection request data.

S1520: Wirelessly connect or disconnect with the first device according to the connection request data.

S1530: Detect the first information identifier, which is used to indicate the execution status of wireless connection or disconnection with the first device.

S1540: Every preset time period, determine whether the wireless connection or disconnection with the first device is normal according to the first information identifier.

In the embodiment of this application, for the specific implementation of steps S1510 to S1530, please refer to the relevant description of steps S1210 to S1230 in Figure 12 above.

Step S1540 may be an implementation of step S1240 in Figure 12 above.

Specifically, in step S1540, the wireless connection device 420 may determine whether the wireless connection or disconnection with the first device is normal according to the first information identifier every preset time period, so as to realize the communication between the first device and the first device. The continuous monitoring of wireless connection ensures the reliability of long-term wireless connection between the wireless connection device 420 and the first device.

FIG. 16 shows a schematic flow chart of a wireless connection method 1600 of the battery management device 400 provided by the embodiment of the present application. The wireless connection method 1600 is also applied to the wireless connection device 420 in the battery management device 400 shown in FIG. 4 above. Optionally, in this embodiment of the present application, the wireless connection device 420 may include a state machine module and a wireless communication protocol stack module, and the state machine module and the wireless communication protocol stack module may be software modules in the wireless connection device 420 . In order to control the state machine module and the wireless communication protocol stack module, the wireless connection device 420 may also include a main control module, and the main control module may also be a software module in the wireless connection device 420 .

As shown in Figure 16, in this embodiment of the present application, the wireless connection method 1600 may include the following steps.

S1610: The main control module receives the connection request data and calls the state machine module.

S1621: The state machine module calls the wireless communication protocol stack module according to the connection request data.

S1622: The wireless communication protocol stack module performs wireless connection or disconnection with the first device to form a first information identifier.

S1630: The state machine module detects the first information identifier, which is used to indicate the execution status of wireless connection or disconnection with the first device.

S1640: The state machine module determines whether the wireless connection or disconnection between the wireless connection device and the first device is normal based on the first information identifier.

In this embodiment of the present application, step S1610 may be an implementation of step S1210 in Figure 12 above. Steps S1621 to S1622 may be an implementation of step S1220 in Figure 12 above. Step S1630 may be an implementation of step S1230 in Figure 12 above. Step S1640 may be an implementation of step S1240 in Figure 12 above.

Specifically, in the wireless connection device 420 in the embodiment of the present application, multiple software modules may be stored therein, and the multiple software modules cooperate with each other to jointly realize the wireless function of the wireless connection device 420 . In step S1610, the main control module can be used to receive connection request data sent by the external device. According to the connection request data, the main control module can call the state machine module to start performing the connection action.

In steps S1621 and S1622, the state machine module calls the wireless communication protocol stack module according to the connection request data, and the wireless communication protocol stack module specifically performs wireless connection or disconnection with the first device. Further, after the wireless communication protocol stack module specifically performs wireless connection or disconnection with the first device, the wireless communication protocol stack module can generate or update the first information identifier according to its execution of wireless connection or disconnection with the first device. Therefore, in this embodiment of the present application, the first information identifier is used to indicate the execution status of wireless connection or disconnection between the wireless communication protocol stack module and the first device.

In steps S1630 and S1640, the state machine module detects and reads the first information identifier, and can determine whether the wireless connection or disconnection between the wireless connection device and the first device is normal based on the first information identifier. Optionally, the main control module can call the state machine module regularly or irregularly, so that the state machine module can regularly or irregularly determine the wireless connection between the wireless connection device and the first device based on the first information identifier. Is the disconnection normal?

Through the technical solutions of the embodiments of the present application, the wireless connection device 420 may include multiple software modules, where different software modules are used to perform different functions and can cooperate with each other. Utilizing the wireless communication protocol stack module to specifically implement wireless connection or disconnection with the first device, it is easy to monitor the execution actions of the wireless communication protocol stack module and generate a first information identifier, which can accurately reflect the wireless connection device 420 Implementation of wireless connection or disconnection with the first device.

FIG. 17 shows a schematic flow chart of a wireless connection method 1700 of the battery management device 400 provided by the embodiment of the present application. The wireless connection method 1700 is also applied to the wireless connection device 420 in the battery management device 400 shown in FIG. 4 above.

As shown in Figure 17, in this embodiment of the present application, the wireless connection method 1700 may include the following steps.

S1710: Receive connection request data.

S1720: Wirelessly connect to the first device according to the connection request data.

S1730: Perform master-slave authentication with the first device.

S1740: If the master-slave authentication with the first device is successful, store the authentication information of the first device in the non-volatile storage module.

In the embodiment of this application, for the specific implementation of steps S1710 to S1720, please refer to the relevant description of step S1210 and step S1220 in the embodiment shown in Figure 12 above.

In addition, in the embodiment of the present application, after step S1720, that is, after the wireless connection device 420 wirelessly connects to the first device according to the connection request data, the wireless connection device 420 executes step S1730, that is, the wireless connection device 420 executes the connection with the first device. Master-slave authentication of a device is used to determine whether the wireless connection device 420 and the first device can adapt to each other, thereby ensuring subsequent normal data transmission between the wireless connection device 420 and the first device and improving system robustness.

Optionally, as shown in Figure 17, in some implementations, step S1730 may include the following steps.

S1731: Receive the first message and the first random number sent by the first device. The first message is used to indicate the master-slave authentication of the first device.

S1732: Perform algorithm processing on the first random number to obtain the first target number.

S1733: Send the second message matching the first message and the first target number to the first device, so that the first device recognizes the second message, and performs an algorithm check on the first target number to determine the master-slave number. Certification results.

Specifically, in step S1731, the wireless connection device 420 receives the first message and the first random number sent by the first device. The wireless connection device 420 is able to identify the first message and determine the start time based on the first message. Perform master-slave authentication with the first device.

In step S1732, the wireless connection device 420 can use a specific algorithm to perform data on the first random number to obtain the first target number. The specific algorithm may be an algorithm pre-agreed between the wireless connection device 420 and the first device, and the embodiment of the present application does not specifically limit the type of the specific algorithm.

In step S1733, the wireless connection device 420 sends a second message matching the first message and the first target number to the first device, where the second message is used to indicate the master-slave authentication of the wireless connection device 420. , the first device receives and identifies the second message, and determines to start performing master-slave authentication with the wireless connection device 420 according to the first message.

Specifically, the first device can also use a specific algorithm to check the first target number to determine the master-slave authentication result with the wireless connection device 420 . The specific algorithm used by the first device can match the specific algorithm used by the wireless connection device 420. For example, the specific algorithm used by the wireless connection device 420 can be an encryption algorithm, and the specific algorithm used by the first device can match the encoding. Algorithm decryption algorithm.

In some embodiments, after the first device uses a specific algorithm to process the first target number and can recover the first random number, it is considered that the master-slave authentication between the first device and the wireless connection device 420 is successful. The connection devices 420 can adapt to each other, and the first device will start sending data to the wireless connection device 420 through wireless communication, and the first device and the wireless connection device 420 will establish a normal wireless connection. On the contrary, if the first device cannot recover the first random number after using a specific algorithm to process the first target number, it is considered that the master-slave authentication between the first device and the wireless connection device 420 has failed, and the first device and the wireless connection device 420 cannot authenticate each other. To adapt to each other, the first device does not send data to the wireless connection device 420, and the wireless connection between the first device and the wireless connection device 420 is disconnected from each other.

Through the technical solutions of the embodiments of the present application, the master-slave authentication process is implemented between the wireless connection device 420 and the first device through the exchange of messages and data, which can achieve higher accuracy and facilitate the communication between the wireless connection device 420 and the first device. Internal software and/or hardware implements the master-slave authentication process.

In some implementations, the first message and the second message are Controller Area Network (CAN) messages. In this embodiment, CAN messages are used between the wireless connection device 420 and the first device to indicate master-slave authentication. On the one hand, CAN messages can be used to perform master-slave authentication between the battery management device 400 and the first device in related technologies. On the other hand, the technical solution of slave authentication can also facilitate subsequent processes to parse the CAN message to locate the master-slave authentication interaction between the wireless connection device 420 and the first device.

Optionally, in this embodiment of the present application, the wireless connection device 420 may also include an NVM module. Continuing to refer to Figure 17, optionally, in this embodiment of the present application, after step S1730, that is, after the wireless connection device 420 completes the master-slave authentication with the first device, the wireless connection device 420 also performs step S1740, that is, after the wireless connection device 420 completes the master-slave authentication with the first device, When the master-slave authentication of the first device is successful, the authentication information of the first device is stored in the NVM module, where the authentication information of the first device is used to indicate that the master-slave authentication of the first device and the wireless connection device 420 is successful.

Through the technical solution of the embodiment of the present application, even if the wireless connection device 420 is powered off, the storage of the authentication information of the first device in the NVM module will not be affected. After the wireless connection device 420 is powered off and restarted, according to the authentication information of the first device in the NVM module, when the wireless connection device 420 subsequently performs a wireless connection with the first device, data communication can be directly performed without the need to perform it again. Master-slave authentication with the first device, thereby saving system resources and improving wireless connection performance between the wireless connection device 420 and the first device.

Optionally, in this embodiment of the present application, after the wireless connection device 420 performs step S1730, the wireless connection device 420 is also configured to detect the first status identifier and/or the first information identifier with the first device, and Determine whether the wireless connection or disconnection with the first device is normal according to the first status identifier and/or the first information identifier. For specific solutions, please refer to the relevant descriptions of the above embodiments, and will not be described in detail here.

FIG. 18 shows a schematic flow chart of a wireless connection method 1800 for the battery management device 400 provided by the embodiment of the present application. The wireless connection method 1800 can also be applied to the wireless connection device 420 in the battery management device 400 shown in FIG. 4 above. Alternatively, the wireless connection device 420 can be a Bluetooth chip. Optionally, the Bluetooth chip is connected to the control device 410 in the battery management device 400. For example, the control device 410 may be a main control chip, or may also be called a main chip.

As shown in Figure 18, in this embodiment of the present application, the wireless connection method 1800 may include the following steps.

S1810: After receiving the connection request data, copy the specific data to a specific array.

S1820: Call the connection command processing function to copy it to the specific ECU table and NVM, and switch the main state machine to process the connection command.

S1830: The main state machine determines the specific connection command and calls the protocol stack interface to complete the connection with the device to be connected.

S1840: Determine whether the Bluetooth protocol stack connection action is completed.

S1851: When the Bluetooth protocol stack connection action is completed, update the specific flag bit.

S1852: When the Bluetooth protocol stack connection action is not completed, the specific flag bit is not updated.

S1860: Master-slave authentication.

S1870: Determine whether the authentication is successful.

S1880: Normal data interaction.

S1890: 1ms scheduling main state machine.

S18100: Detect Bluetooth connection status and specific flag bits.

S18110: Determine whether the specific flag bit is updated and check whether the connection status is consistent with the connection request.

S18120: Reconnect with the device to be connected when the specific flag bit is not updated and/or the connection status is inconsistent with the connection request.

S18130: Initialize NVM after powering on again.

S18140: Check whether the connection status is "connected".

S18150: When the connection status is "connected", retrieve the connection request data from NVM, call the connection command processing function, and reconnect with the device to be connected.

Specifically, for step S1810, the connection request data may be data sent by the main chip in the battery management device 400 to the Bluetooth chip through a communication bus (such as an SPI bus). After receiving the connection request data, the Bluetooth chip copies it to a specific array so that subsequent connection command processing functions can access the connection request data in the array.

For step S1820, the Bluetooth chip includes a main program and a main state machine program. The main program can call the connection command processing function. The connection command processing function can copy the connection request data in the above-mentioned specific array to a specific electronic control. Unit (Electronic Control Unit, ECU) table and NVM, and switch the main state machine to process the connection request data. Among them, the ECU table is a structure in the memory of the Bluetooth chip, and NVM is the non-volatile memory in the Bluetooth chip.

For step S1830, the Bluetooth chip also includes a Bluetooth protocol stack. The main state machine determines the content of the connection request data. If it is a connection command, the connection interface of the Bluetooth protocol stack is called and the content of the connection request data is input to the connection interface. If it is a disconnection command, the disconnection interface of the Bluetooth protocol stack is called, and the content of the connection request data is input into the disconnection interface. Through the main state machine's interface call to the Bluetooth protocol stack, Bluetooth connection and disconnection between the Bluetooth chip and the device to be connected (for example, the first device above) can be realized.

For step S1840, it can be determined whether the Bluetooth connection and disconnection action of the Bluetooth protocol stack is completed, and a specific flag bit (for example, the first information identifier above) can be set in the Bluetooth chip to indicate whether the Bluetooth connection and disconnection action of the Bluetooth protocol stack is completed. Finish. By default, this specific flag is not updated and can be a default value.

For steps S1851 and S1852, when the Bluetooth connection and disconnection action of the Bluetooth protocol stack is not completed, the specific flag bit in the Bluetooth chip is not updated and remains at the default value. On the contrary, when the Bluetooth connection and disconnection action of the Bluetooth protocol stack is completed, the specific flag bit in the Bluetooth chip is updated and changed from the default value to other target values.

After the main state machine calls the Bluetooth protocol stack to complete the connection and disconnection with the device to be connected, Bluetooth connection or disconnection can be achieved between the Bluetooth chip and the device to be connected. After the Bluetooth chip and the device to be connected are connected via Bluetooth, the device to be connected and the Bluetooth chip can send data packets (or, it can also be called heartbeat packets) to each other.

If the Bluetooth chip receives the data packet normally, the identification bit recorded in the ECU table in the Bluetooth chip to indicate the Bluetooth connection status (for example, the first status identification above) is written as the first value (for example, 1), indicating that Bluetooth is connected.

When the signal is unstable and the data packets received by the Bluetooth chip are not updated after a preset time period (such as 2s), the Bluetooth protocol stack will handle the disconnection. At this time, the flag bit recorded in the ECU table in the Bluetooth chip for indicating the Bluetooth connection status is written as a second value (for example, 0), indicating that Bluetooth is in a disconnected state.

Optionally, the flag bits in the ECU table can be updated in real time to represent the connection status between the Bluetooth chip and the device to be connected in real time.

For step S1860, master-slave authentication can be understood as the process of handshaking between the Bluetooth chip and the device to be connected, where the battery management device where the Bluetooth chip is located can be understood as the master device, and the device to be connected can be understood as the slave device. Specifically, during the master-slave authentication process, after the Bluetooth chip and the device to be connected are connected to each other, they start sending and receiving data to each other. At this time, only data exchanges of limited length can be carried out. The device to be connected first sends a specific message frame and a random number A to the Bluetooth chip. The Bluetooth chip processes the random number A through a specific algorithm to obtain the target number B. Then, the Bluetooth chip sends another frame of message and the target number B to the Bluetooth chip. to the device to be connected. After the connected device receives the target number B, it performs an algorithm check. If there is no problem, normal data interaction is allowed. The above-mentioned master-slave authentication process needs to be completed within a predetermined time period (for example: 500ms). If any data to be connected is not received by any device to be connected during the interaction and times out, the device to be connected will actively disconnect the Bluetooth chip.

For steps S1870 and S1880, it is determined whether the authentication is successful. If so, the Bluetooth chip and the device to be connected can be considered to be mutually adapted, and the two can subsequently perform normal data interaction. For example, if the device to be connected is the SMBU in the vehicle, and the battery management device where the Bluetooth chip is located is the MBMU, the SBMU can send data such as battery current, voltage, temperature, SOC, and SOH to the Bluetooth chip in the MBMU. If not, the Bluetooth chip and the device to be connected are not compatible with each other, and the device to be connected actively disconnects the Bluetooth connection with the Bluetooth chip and does not send data to the Bluetooth chip.

In addition, after the master-slave authentication is successful, the relevant information of the device to be connected can be written into the NVM of the Bluetooth chip. When the Bluetooth chip subsequently connects to the device to be connected, the master-slave authentication can no longer be performed, saving system resources.

For step S1890, the main program in the Bluetooth chip can schedule the main state machine every 1ms, so that the main state machine executes steps S18100 and S18110, that is, detecting the current Bluetooth connection status and the specific flag bit, and judging whether the specific flag bit is updated and Check whether the Bluetooth connection status is consistent with the connection request to determine whether the current Bluetooth connection is normal.

Specifically, the main state machine can check the flag bit used to indicate the Bluetooth connection status in the ECU table to determine whether the current Bluetooth connection status is consistent with the connection request. In addition, the main state machine can also determine whether a specific flag bit is updated. When the Bluetooth connection status is consistent with the connection request and the specific flag bit has been updated, it means that the current Bluetooth connection status is normal.

If the Bluetooth connection status is inconsistent with the connection request and/or the specific flag is not updated, it means that the current Bluetooth connection status is abnormal, and the main program of the Bluetooth chip needs to execute step S18120 to reconnect the Bluetooth chip with the device to be connected. , to fix the exception.

Specifically, when the Bluetooth connection status and the connection request are inconsistent, the main program of the Bluetooth chip can read the connection request command data from the ECU table and re-execute the above steps S1820 to S1830 to perform Bluetooth reconnection. The number of reconnections can be up to 5 times to prevent excessive reconnections and waste of system resources.

When the specific flag bit is not updated, the main program of the Bluetooth chip calls the Bluetooth protocol stack again, causing the Bluetooth protocol stack to perform a connection and disconnection action again, and then the specific flag bit is updated again. In this case, S18100 to S18120 can be repeatedly executed, that is, it is repeatedly determined whether the specific flag bit is updated, and if the specific flag bit is not updated, the connection with the device to be connected is repeatedly executed until the specific flag bit is updated successfully.

For step S18130, after the battery management device 400 is powered off and powered on again, the Bluetooth chip can initialize its internal NVM to facilitate subsequent reading and writing of data in the NVM.

For step S18140, the Bluetooth chip reads the connection status between the Bluetooth chip and the device to be connected from the NVM, and then checks whether the connection status is "connected". It can be understood that in the embodiment of the present application, before the Bluetooth chip is powered on again, the Bluetooth chip can detect the connection status with the device to be connected, and write the connection status into the NVM. Therefore, when the battery After the management device 400 is powered off and powered on again, the Bluetooth chip can read the connection status of the device to be connected before the power off from the NVM.

Optionally, the Bluetooth chip can be configured to connect N devices to be connected, where N is a preset value. When the Bluetooth chip is connected to N devices to be connected, the NVM can simultaneously store the connection status of the Bluetooth chip and the N devices to be connected. In step S18140, the Bluetooth chip can sequentially read the connection status of each device to be connected from the NVM, and determine whether it is "connected".

When it is determined that the connection status of the Bluetooth chip and the device to be connected is "connected", the Bluetooth chip then reads the connection request data corresponding to the device to be connected from the NVM, calls the connection command processing function, and sends the connection request data again Copy it to a specific ECU table and NVM, and switch the main state machine to process the connection request data to achieve reconnection with the device to be connected.

It can be understood that after step S18150, the Bluetooth chip can continue to execute steps S1890 to S18130 to continuously monitor whether a connection abnormality occurs between the Bluetooth chip and the device to be connected.

The above describes the wireless connection method 500 to the wireless connection method 1700 in which the wireless connection device 420 in the battery management device 400 serves as the execution subject in the embodiment of the present application with reference to FIGS. 5 to 18 . The following description will be made with reference to FIGS. 19 to 26 In the embodiment of the present application, the control device 410 in the battery management device 400 serves as the execution subject of the wireless connection method.

FIG. 19 shows a schematic flow diagram of a wireless connection method 1900 for a battery management device 400 provided by an embodiment of the present application. The wireless connection method 1900 is applied to the control device 410 in the battery management device 400 shown in FIG. 4. In other words, the execution subject of the wireless connection method 1900 in the embodiment of the present application is the control device 410.

As shown in Figure 19, in this embodiment of the present application, the wireless connection method 1900 includes the following steps.

S1910: Obtain a connection request command, which is used to instruct wireless connection or disconnection between the battery management device and the first device.

S1920: Control the wireless connection device to wirelessly connect or disconnect from the first device according to the connection request command.

S1930: Detect the first status identifier of the wireless connection device.

S1940: Based on the first status identifier, determine whether the wireless connection or disconnection between the wireless connection device and the first device is normal.

Specifically, in steps S1910 and S1920, the control device 410 receives a connection request command for instructing the battery management device 400 to wirelessly connect or disconnect from the first device. According to the connection request command, the control device 410 controls the wireless connection device 420 to achieve wireless connection or disconnection with the first device, thereby achieving wireless connection or disconnection between the battery management device 400 and the first device.

Optionally, in some embodiments, the control device 410 in the battery management device 400 may receive a connection request command from an external device of the battery management device 400 to control the wireless connection between the wireless connection device 420 and the first device or disconnect.

For example, in the case where the battery management device 400 is the TBMU 220 and the first device is the MBMU 120, when the vehicle 1 is outside the battery swap station 2, the TBMU 220 receives the first connection request command sent by the station control system 21. The TBMU 220 can achieve wireless connection or disconnection with the MBMU 120 in the vehicle 1 based on the first connection request command.

For another example, in the case where the battery management device 400 is the MBMU 120 and the first device is the SBMU 110, when the vehicle 1 drives into the battery swap station 2, the TBMU 220 receives the second connection request command sent by the station control system 21, and then The second connection request command is then sent to the MBMU 120 in the vehicle 1, and the MBMU 120 can achieve wireless connection or disconnection with the SBMU 110 in the battery 10 based on the second connection request command.

For another example, in the case where the battery management device 400 is the CBMU 210 and the first device is the SBMU 110, in the battery swap station 2, the CBMU 210 in the battery swap bin 20 receives the third connection request command sent by the station control system 21, The CBMU 210 can achieve wireless connection or disconnection with the SBMU 110 in the battery 10 based on the third connection request command.

Alternatively, in other embodiments, the control device 410 in the battery management device 400 may also generate the connection request command based on the relevant information it has obtained, or the control device 410 may also obtain the connection request command from other devices in the battery management device 400 . The device obtains the connection request command. The embodiment of the present application does not limit the specific manner in which the control device 410 obtains the connection request command.

In steps S1930 and S1940, after the control device 410 controls the wireless connection device 420 to wirelessly connect or disconnect the first device according to the connection request command, the control device 410 may further detect the first status identifier of the wireless connection device 420. , such as the first status identifier and/or the first information identifier described in the above embodiment. The first status identifier can be used to characterize the wireless connection status between the wireless connection device 420 and the first device. Therefore, the control device 410 can determine whether the wireless connection or disconnection between the wireless connection device 420 and the first device is normal according to the first status identifier, thereby further determining the wireless connection between the battery management device 400 and the first device. Or whether the disconnection is normal.

Through the technical solution of the embodiment of the present application, there is no need to modify the existing hardware of the battery management device 400. It is enough to add a wireless connection device 420 to the battery management device 400, and control the wireless connection device 420 through the control device 410. A wireless connection is achieved between the battery management device 400 and the first device. This wireless connection method is relatively simple to implement and can be compatible with existing products. In addition, the control device 410 of the battery management device 400 can detect the first status identifier of the wireless connection device 420, and determine whether the wireless connection or disconnection between the wireless connection device 420 and the first device is normal based on the first status identifier. , which is conducive to effective monitoring of the wireless connection between the battery management device 400 and the first device, thereby improving the connection performance between the battery management device 400 and the first device.

Figure 20 shows a schematic flow chart of a wireless connection method 2000 for a battery management device 400 provided by an embodiment of the present application. The wireless connection method 2000 can also be applied to the control device 410 in the battery management device 400 shown in FIG. 4 above.

As shown in Figure 20, in this embodiment of the present application, the wireless connection method 2000 includes the following steps.

S2010: Obtain a connection request command, which is used to instruct wireless connection or disconnection between the battery management device and the first device.

S2021: Convert the connection request command based on the first communication protocol into connection request data based on the second communication protocol.

S2022: Send the connection request data to the wireless connection device, so that the wireless connection device wirelessly connects or disconnects with the first device according to the connection request data.

S2030: Detect the first status identifier of the wireless connection device.

S2040: Determine whether the wireless connection or disconnection between the wireless connection device and the first device is normal according to the first status identifier and the connection request data.

In the embodiment of this application, for the specific implementation of step S2010 and step S2030, please refer to the relevant description of step S1910 and step S1930 in Figure 19 above.

Step S2021 and step S2022 may be an implementation manner of step S1920 in Figure 19 above. Step S2040 may be an implementation of step S1940 in Figure 19 above.

Specifically, in step S2021 and step S2022, the control device 410 may be connected to the external device of the battery management device 400 based on the first communication protocol, and connected to the wireless connection device 420 through the second communication protocol, wherein the first communication The protocol and the second communication protocol are two different types of communication protocols. In this case, the control device 410 may receive a connection request command of the first data type sent by the external device based on the first communication protocol, and convert the connection request command of the first data type into a third connection request command based on the second communication protocol. The connection request data of the second data type is conveniently transmitted to the wireless connection device 420 smoothly.

Through the technical solution of this embodiment, the control device 410 can receive the connection request command based on the first communication protocol, and send the connection request data based on the second communication protocol to the wireless connection device 420 . The control device 410 and the external device can communicate with each other based on the first communication protocol, and the control device 410 and the wireless connection device 420 can communicate with each other based on the second communication protocol. Therefore, the control device 410 can use different communication protocols for different devices or equipment, optimizing the communication performance between the control device 410 and other devices, and improving the overall communication performance of the battery management device 400.

Specifically, in order to enable the wireless connection device 420 to implement wireless connection or disconnection with the first device according to the connection request data, the connection request data may include: a request type used to indicate connection or disconnection with the first device. request data and information data indicating the first device. The information data used to indicate the first device includes but is not limited to: the location of the first device, the Media Access Control Address (MAC) of the first device, and so on.

As an example and not a limitation, the above connection request command is a request command based on the Controller Area Network (Controller Area Network, CAN) protocol, and/or the above connection request data is based on the Serial Peripheral Interface (Serial Peripheral Interface). SPI) protocol request data.

In this example, the control device 410 in the battery management device 400 can be connected to the external device through the CAN bus and receive the connection request command through the CAN protocol. Therefore, the control device 410 and the battery management device 400 in which it is located can be well compatible with existing Battery management system. In addition, the control device 410 is connected to the wireless connection device 420 through a high-speed, easy-to-operate SPI bus, and sends connection request data to the wireless connection device 420 through the SPI protocol, thereby improving communication between the control device 410 and the wireless connection device 420 performance.

Continuing to refer to FIG. 20 , optionally, in step S2040 , the control device 410 may determine the wireless connection based on the detected first state identifier of the wireless connection device 420 and the connection request data converted according to the connection request command. Whether the wireless connection or disconnection between the device 420 and the first device is normal.

Specifically, in this embodiment, the first status identifier can be used to indicate the connection status between the wireless connection device 420 and the first device, and the connection request data can be used to indicate the connection status between the wireless connection device 420 and the first device. connection request. According to the first status identifier and the connection request data, it can be determined whether the wireless connection or disconnection between the wireless connection device 420 and the first device is normal, that is, it can be determined whether the wireless connection device 420 is located between the battery management device 400 and the first device. Whether the wireless connection or disconnection between the two devices is normal.

Compared with the technical solution that only determines whether the wireless connection or disconnection between the battery management device 400 and the first device is normal based on the first status identification of the wireless connection device 420, through the technical solution of this embodiment, the first status identification is integrated and connection request data to determine whether the wireless connection or disconnection between the wireless connection device 420 and the battery management device 400 where it is located and the first device is normal, which can further improve the accuracy of the determination. Therefore, through the technical solution of this embodiment, the wireless connection between the battery management device 400 and the first device can be monitored more effectively, thereby improving the connection performance between the battery management device 400 and the first device.

Figure 21 shows a schematic flow chart of a wireless connection method 2100 for a battery management device 400 provided by an embodiment of the present application. The wireless connection method 2100 can also be applied to the control device 410 in the battery management device 400 shown in FIG. 4 above.

As shown in Figure 21, in this embodiment of the present application, the wireless connection method 2100 includes the following steps.

S2110: Obtain a connection request command, which is used to instruct wireless connection or disconnection between the battery management device and the first device.

S2121: Convert the connection request command based on the first communication protocol into connection request data based on the second communication protocol.

S2122: Send connection request data to the wireless connection device, so that the wireless connection device wirelessly connects or disconnects with the first device according to the connection request data.

S2130: Detect the first status identifier of the wireless connection device.

S2141: Determine whether the connection status indicated by the first status identifier is consistent with the connection request indicated by the connection request data.

S2142: When the connection state indicated by the first status identifier is consistent with the connection request indicated by the connection request data, determine that the wireless connection or disconnection between the wireless connection device and the first device is normal.

S2143: When the connection state indicated by the first status identifier is inconsistent with the connection request indicated by the connection request data, determine that the wireless connection or disconnection between the wireless connection device and the first device is abnormal.

Specifically, in the embodiment of the present application, for the specific technical solution from step S2110 to step S2130, please refer to the relevant description of step S2010 to step S2030 in the embodiment shown in FIG. 20 above.

In addition, steps S2141 to S2143 in the embodiment of the present application may be an implementation manner of the above-mentioned step S2040.

Specifically, in step S2141, the first status identifier can be used to indicate the connection state between the wireless connection device 420 and the first device, that is, to indicate that the connection state between the wireless connection device 420 and the first device is mutual connection. Or disconnect from each other. The connection request data may include a connection request type between the wireless connection device 420 and the first device, that is, the external device requests the wireless connection device 420 and the first device to connect or disconnect from each other.

In step S2142, when the connection status indicated by the first status identifier is consistent with the connection request indicated by the connection request data, the control device 410 may determine that the wireless connection between the wireless connection device 420 and the first device is Normal, that is, the wireless connection between the battery management device 400 where the wireless connection device 420 is located and the first device is normal. For example, when the connection state indicated by the first status identifier is mutually connected, and the connection request indicated by the connection request data is also mutually connected, it can be determined that the wireless connection device 420 and the battery management device 400 where it is located are connected to the third wireless connection device 420 . The wireless connection between one device is normal.

Correspondingly, in step S2143, when the connection status indicated by the first status identifier is inconsistent with the connection request indicated by the connection request data, the control device 410 may determine the wireless connection between the wireless connection device 420 and the first device. The connection is abnormal, that is, the wireless connection between the battery management device 400 where the wireless connection device 420 is located and the first device is abnormal. For example, when the connection state indicated by the first status identifier is mutually disconnected, but the connection request indicated by the connection request data is mutually connected, it can be determined that the wireless connection device 420 and the battery management device 400 where it is located are connected to the third wireless connection device 420 . The wireless connection between one device is abnormal.

In the technical solution of the embodiment of the present application, by determining whether the connection state indicated by the first status identifier is consistent with the connection request indicated by the connection request data, the wireless connection device 420 and the battery management device 400 where it is located can be accurately determined. Whether the wireless connection or disconnection with the first device is normal. This technical solution is easy to implement and has high accuracy. It can not only accurately and effectively monitor the wireless connection between the battery management device 400 and the first device, but can also be more conveniently implemented in the control device 410 through hardware and/or software. middle.

Optionally, in some embodiments, the above-mentioned first status identifier is configured to: use a first value to indicate that the connection state between the wireless connection device 420 and the first device is connected, and use a second value to indicate that the wireless connection device 420 is connected. The connection state with the first device is disconnected. The above-mentioned connection request data is configured to: use a first value to indicate that the connection request between the wireless connection device 420 and the first device is a connection, and use a second value to indicate a connection request between the wireless connection device 420 and the first device. for disconnection.

In this implementation, step S2141 in FIG. 21 may include: determining whether the first status identifier is consistent with the connection request data. Further, the above-mentioned step S2142 may include: when the first status identifier is consistent with the connection request data, determining that the wireless connection between the wireless connection device and the first device is normal. The above step S2143 may include: determining that the wireless connection between the wireless connection device and the first device is abnormal when the first status identifier is inconsistent with the connection request data.

Figure 22 shows a schematic flow chart of a wireless connection method 2200 for a battery management device 400 provided by an embodiment of the present application. The wireless connection method 2200 can also be applied to the control device 410 in the battery management device 400 shown in FIG. 4 above.

As shown in Figure 22, in the embodiment of the present application, the wireless connection method 2200 includes steps S1910 to S1940 in the embodiment shown in Figure 19 above. On this basis, after determining the wireless connection device 420 and the first device In the case where the wireless connection or disconnection is abnormal, the wireless connection method 2200 may also include the following steps.

S2250: According to the connection request command, control the wireless connection device to wirelessly connect or disconnect with the first device at least once.

S2260: Detect the first status identifier of the wireless connection device at least once until it is determined that the wireless connection or disconnection between the wireless connection device and the first device is normal.

Specifically, in the embodiment of the present application, when the control device 410 detects that the wireless connection between the wireless connection device 420 and the first device is abnormal, the control device 410 may continue to control the wireless connection according to the connection request command. The device 420 wirelessly reconnects or disconnects from the first device at least once to repair the wireless connection abnormality between the wireless connection device 420 and the first device.

Specifically, after each time the wireless connection device 420 performs wireless connection or disconnection with the first device, the control device 410 may re-detect the first state identifier of the wireless connection device 420, and based on the newly detected first state identifier Determine whether the wireless connection between the wireless connection device 420 and the battery management device 400 where it is located and the first device is normal.

By controlling the wireless connection device 420 to reconnect or disconnect wirelessly with the first device at least once, and detecting the first status identifier of the wireless connection device 420 at least once, until it is determined that the wireless connection device 420 and the battery management device 400 where it is located are in contact with the first device. The wireless connection between the devices is normal, that is, the abnormal wireless connection between the battery management device 400 and the first device is repaired, and the control device 410 stops controlling the wireless connection device 420 to continue to wirelessly connect or disconnect with the first device.

Through the technical solution of the embodiment of the present application, when there is an abnormality in the wireless connection between the wireless connection device 420 and the first device, the control device 410 can repair the abnormality, so that the battery management device 400 and the first device The wireless connection between them is restored to the normal state, thereby further improving the connection reliability between the battery management device 400 and the first device.

Figure 23 shows a schematic flow chart of a wireless connection method 2300 for the battery management device 400 provided by the embodiment of the present application. The wireless connection method 2300 can also be applied to the control device 410 in the battery management device 400 shown in FIG. 4 above.

As shown in Figure 23, in the embodiment of the present application, the wireless connection method 2300 includes steps S2110 to S2143 in the embodiment shown in Figure 21 above. On this basis, after step S2143, that is, after determining the wireless connection device When the wireless connection or disconnection between 420 and the first device is abnormal, the wireless connection method 2300 may also include the following steps.

S2350: Send connection request data to the wireless connection device at least once, so that the wireless connection device wirelessly connects or disconnects with the first device according to the connection request data at least once.

S2360: Detect the first state identifier of the wireless connection device at least once until the connection state indicated by the first state identifier is consistent with the connection request indicated by the connection request data.

Optionally, step S2350 may be an implementation of step S2250 in Figure 22 above. This step S2360 may be an implementation of step S2260 in Figure 22 above.

Specifically, in this embodiment of the present application, the control device 410 may convert the connection request command to obtain the connection request data and send it to the wireless connection device 420 at least once, so as to control the wireless connection device 420 at least once according to the connection request. Data is wirelessly connected or disconnected from the first device.

Further, after the control device 410 sends a connection request data to the wireless connection device 420, the control device 410 can re-detect the first status identifier of the wireless connection device 420, and determine the connection and disconnection status indicated by the first status identifier. Whether the connection requests indicated by the disconnection request data are consistent, thereby determining whether the wireless connection or disconnection between the wireless connection device 420 and the battery management device 400 where it is located and the first device is normal.

After the control device 410 sends the connection request data to the wireless connection device 420 at least once, and detects the first status identifier of the wireless connection device 420 at least once, until it is determined that the connection state indicated by the first status identifier and the connection request data indicate If the connection requests are consistent, it can be determined that the wireless connection between the wireless connection device 420 and the battery management device 400 where it is located and the first device is normal, that is, the abnormal wireless connection between the battery management device 400 and the first device has been repaired. The control device 410 stops sending the connection request data to the wireless connection device 420 .

Through the technical solution of the embodiment of the present application, the control device 410 can effectively control the wireless connection between the wireless connection device 420 and the first device, and the control device 410 is responsible for the connection between the wireless connection device 420 and its battery management device 400 and the first device. The accuracy of determining the wireless connection abnormality is also high, and the abnormality can be effectively and quickly repaired, so that the wireless connection between the battery management device 400 and the first device can be restored to a normal state quickly and reliably.

Figure 24 shows a schematic flow chart of a wireless connection method 2400 for the battery management device 400 provided by the embodiment of the present application. The wireless connection method 2400 can also be applied to the control device 410 in the battery management device 400 shown in FIG. 4 above. Optionally, the control device 410 may include a non-volatile memory (NVM) module.

As shown in Figure 24, in the embodiment of the present application, the wireless connection method 2400 may include steps S2110 to S2143 and steps S2350 to S2360 in the embodiment shown in Figure 23. On this basis, after step S2121, The wireless connection method 2400 may also include the following steps.

S2410: Store the connection request data in the NVM module.

Specifically, in this embodiment of the present application, the NVM module is a storage module in which the data stored therein will not be lost after power failure. The NVM module may be located inside the control device 410 to facilitate the control device 410 to read and write data in the NVM module. Alternatively, the NVM module can also be located outside the control device 410 and be electrically connected to the control device 410 .

In order to facilitate subsequent wireless connection abnormality judgment between the battery management device 400 and the first device based on the connection request data, after the control device 410 receives the connection request command and converts the connection request command into connection request data, The control device 410 is used to synchronously store the connection request data in the NVM module. Through this technical solution, the loss of connection request data caused by external reasons such as power outage can be prevented, and the subsequent control device 410 can ensure the abnormal judgment of the wireless connection between the wireless connection device 420 and the first device, thereby further improving the connection between the battery management device 400 and the first device. The connection performance between the first devices.

Based on the NVM module, after step S2143, that is, after it is determined that the wireless connection or disconnection between the wireless connection device 420 and the first device is abnormal, the wireless connection method 2400 may further include the following steps.

S2420: Obtain the connection request data from the NVM module.

After step S2420, the control device 410 then executes steps S2350 to S2360.

Therefore, in this embodiment, the connection request data in the NVM module can also be used to ensure that the control device 410 subsequently repairs the abnormal wireless connection between the wireless connection device 420 and the first device, so as to further improve the battery management device 400 The performance of the connection to the first device.

Figure 25 shows a schematic flow chart of a wireless connection method 2500 for the battery management device 400 provided by the embodiment of the present application. The wireless connection method 2500 can also be applied to the control device 410 in the battery management device 400 shown in FIG. 4 above.

As shown in Figure 25, in this embodiment of the present application, the wireless connection method 2500 may include the following steps.

S2510: Obtain a connection request command, which is used to instruct wireless connection or disconnection between the battery management device and the first device.

S2521: Convert the connection request command based on the first communication protocol into connection request data based on the second communication protocol.

S2522: Send connection request data to the wireless connection device, so that the wireless connection device wirelessly connects or disconnects with the first device according to the connection request data.

S2531: Detect the first status identifier of the wireless connection device within the first preset time period after sending the connection request data.

S2532: Detect the first status identifier of the wireless connection device every second preset time period.

S2540: Determine whether the wireless connection or disconnection between the wireless connection device and the first device is normal according to the first status identifier and the connection request data.

In the embodiment of the present application, for the specific implementation of steps S2510, S2521, S2522 and step S2540, please refer to the relevant description in Figure 20 above. Step S2531 and step S2532 may be an implementation manner of step S2030 in Figure 20 above.

Specifically, in step S2531, the first preset time period is greater than or equal to the transmission time of the connection request data between the control device 410 and the wireless connection device 420. The transmission time is controlled by the connection mode between the control device 410 and the wireless connection device 420 . As an example, when the control device 410 and the wireless connection device 420 are connected to each other through the SPI bus, the data transmission time between the two is about 5 ms. In view of this, in the embodiment of the present application, the first preset time period may be 5 ms, and the control device 410 detects the first status identifier of the wireless connection device 420 within 5 ms after sending the connection request data to the wireless connection device 420 .

Through this technical solution, the control device 410 can effectively detect the latest first state identifier of the wireless connection device 420 to ensure the validity and reliability of the data. According to the valid and reliable first status identifier, the effectiveness and reliability of the control device 410's determination of abnormal wireless connection between the wireless connection device 420 and the first device can be improved.

Specifically, in step S2532, the control device 410 may also detect the current first status identifier of the wireless connection device 420 every second preset time period, so as to realize the wireless connection between the wireless connection device 420 and the first device. Continuous monitoring ensures the reliability of the long-term wireless connection between the wireless connection device 420 and the first device.

As an example, in the embodiment of the present application, the second preset time period may be less than or equal to 100 ms. In other examples, the second preset time period can also be adjusted according to actual conditions. The embodiment of the present application does not limit the specific value of the second preset time period.

Figure 26 shows a schematic flow chart of a wireless connection method 2600 for the battery management device 400 provided by the embodiment of the present application. This wireless connection method 2600 can also be applied to the control device 410 in the battery management device 400 shown in Figure 4 above. Alternatively, the control device 410 can be a control chip, or it can also be called a main chip. The control chip (main chip) is connected to the wireless communication chip in the battery management device 400, such as a Bluetooth chip.

As shown in Figure 26, in this embodiment of the present application, the wireless connection method 2600 may include the following steps.

S2610: Receive the Bluetooth connection request command transmitted by CAN.

S2620: Convert the Bluetooth connection command message into connection request data. The connection request data includes: Bluetooth MAC, location, and connection request of the device to be connected.

S2630: Call the connection command processing function, copy the connection request data to the SPI accessible structure and NVM, and perform data calibration.

S2640: Call the SPI transmission data state machine and copy the connection request data to the array to be transmitted by SPI.

S2650: Call the SPI protocol to transmit connection request data to the Bluetooth chip.

S2660: Read back the Bluetooth connection status of the Bluetooth chip through SPI after 5ms.

S2670: Determine whether the connection status and connection request data are the same.

S2680: When the connection status and connection request data are different, read the connection request data from NVM and call the connection command processing function again.

Specifically, for step S2610, during the battery replacement process of the vehicle, or during the operation of the vehicle, the main chip in the battery management device 400 can be connected to the external device through the CAN bus, and the main chip can receive data from the external device through the CAN bus. The transmitted Bluetooth connection request command can be used to instruct the battery management device 400 to disconnect the Bluetooth connection with the device to be connected (such as the first device above).

For step S2620, the main chip converts the Bluetooth connection command message into connection request data. The connection request data includes: Bluetooth MAC, the location of the device to be connected, and the connection request.

Specifically, the Bluetooth connection command transmitted through the CAN bus can be message data, and the main chip can convert the message data into connection request data, and the connection request data can satisfy the SPI protocol. The connection request data may include the Bluetooth Mac address, location, connection request and other information of the device to be connected, so that after the main chip transmits the connection request data to the Bluetooth chip, the Bluetooth chip can be based on the Bluetooth Mac Information such as address and location determines the device to be connected, and establishes a Bluetooth connection with the device to be connected based on the connection request.

For step S2630, the main chip may include a main program, and the main program may call a connection command processing function. The connection command processing function may be used to synchronously copy the connection request data to the SPI accessible structure and NVM. During the copy process, the connection request data can be calibrated, that is, every time a piece of data is copied, the flag bit corresponding to the data is updated to ensure that all the connection request data is copied.

For step S2640, the main chip may also include an SPI transmission data state machine. The main program may call the SPI transmission data state machine. The SPI transmission data state machine is used to copy the connection request data in the SPI accessible structure to the SPI. in the array to be transferred.

For step S2650, the main chip may also include: an SPI protocol layer. The main program in the main chip may call the SPI protocol layer to transmit the connection request data in the array to be transmitted by SPI to the Bluetooth chip through SPI.

For step S2660, it takes 5ms to transmit data once through the SPI protocol. After transmitting data through the SPI protocol, the main chip immediately reads back the status of the Bluetooth chip. For example, the main chip sends connection status request information to the Bluetooth chip, and the Bluetooth chip sends the connection status with the device to be connected back to the main chip, so that the main chip reads back the current connection status between the Bluetooth chip and the device to be connected. state.

For step S2670, the main chip determines whether the connection status and the connection request data are the same. If yes, it means that the current Bluetooth chip and the device to be connected are connected normally and no abnormality occurs.

If not, step S2680 is executed. The main chip reads the connection request data from NVM, calls the connection command processing function again, and copies the connection request data to the SPI accessible structure and NVM again. Then, the above-mentioned steps S2630 to S2670 are repeatedly executed to re-transmit the connection request data to the Bluetooth chip, and read back the Bluetooth connection status of the Bluetooth chip until it is determined that the connection status and the connection request data are the same to determine the current Bluetooth chip. The connection to the device to be connected is normal and no abnormality occurs.

The above describes the embodiment of the wireless connection method of the battery management device provided by the present application with reference to FIG. 3, FIG. 5 to FIG. 26. Next, the embodiment of the device of the battery management device provided by the present application is described with reference to FIG. 27 and FIG. 28. It should be understood that the device embodiments and method embodiments correspond to each other, and similar descriptions may refer to the method embodiments.

Figure 27 shows a schematic structural block diagram of a battery management device 2700 provided by an embodiment of the present application.

As shown in Figure 27, in the embodiment of the present application, the battery management device 2700 includes: a wireless connection device 2710, wherein the wireless connection device 2710 includes: a first connection module 2711, a first detection module 2712, and a first processing module 2713 .

Specifically, the first connection module 2711 is used to wirelessly connect or disconnect with the first device. The first detection module 2712 is used to detect the connection status data with the first device. The first processing module 2713 is configured to determine whether the wireless connection or disconnection with the first device is normal based on the connection status data.

In some possible implementations, the connection status data includes: a first status identifier, the first status identifier is used to indicate that the wireless connection device and the first device are connected to or disconnected from each other.

In some possible implementations, the first connection module 2711 is configured to: receive connection request data, and wirelessly connect or disconnect with the first device according to the connection request data. The first detection module 2712 is used to: detect the first status identifier. The first processing module 2713 is configured to determine whether the wireless connection or disconnection with the first device is normal according to the first status identifier and the connection request data.

In some possible implementations, the first processing module 2713 is configured to: determine whether the connection status indicated by the first status identifier is consistent with the connection request indicated by the connection request data; When the connection request indicated by the connection request data is consistent, the wireless connection with the first device is determined to be normal; when the connection state indicated by the first status identifier is inconsistent with the connection request indicated by the connection request data Next, the wireless connection device determines that the wireless connection with the first device is abnormal.

In some possible implementations, when the first processing module 2713 determines that the wireless connection or disconnection with the first device is abnormal, the first processing module 2713 is also configured to: based on the connection request data, at least Perform wireless connection or disconnection with the first device once; detect the first status identifier at least once until the number of executions reaches a preset number or the connection status indicated by the first status indicator is consistent with the connection request indicated by the connection request data.

In some possible implementations, as shown in Figure 27, the wireless connection device 2710 also includes a structure module 2714 and/or a non-volatile memory (NVM) module 2715; the first processing module 2713 is also used to: disconnect the The requested data is stored in the structure module 2714 and/or the non-volatile storage module 2715.

In some possible implementations, the first processing module 2713 is also configured to: store the first status identifier to the structure module 2714 and/or the non-volatile storage module 2715.

In some possible implementations, after the first processing module 2713 is configured to store the connection request data to the non-volatile storage module 2715, the first processing module 2713 is also configured to: when the battery management device 2700 is powered off and restarted. After power-on, the connection request data is read from the non-volatile storage module 2715; according to the connection request data, wireless connection or disconnection is performed with the first device again.

In some possible implementations, after the first processing module 2713 is configured to store the first status identifier into the non-volatile storage module 2715, the first processing module 2713 is also configured to: when the battery management device 2700 is powered off and restarted. After powering on, the first status identifier is read from the non-volatile storage module 2715; according to the connection request data and the first status identifier, wirelessly connects or disconnects with the first device again.

In some possible implementations, after the battery management device 2700 is powered off and on again, the connection request data read by the first processing module 2713 from the non-volatile storage module 2715 is connection request data; first processing Module 2713 is used to: determine whether the connection state indicated by the first status identifier is connected; if the connection state indicated by the first status identifier is connected, wirelessly connect with the first device again according to the connection request data.

In some possible implementations, the connection status data further includes: a first information identifier, and the first information identifier is used to indicate the execution status of wireless connection or disconnection between the wireless connection device and the first device. The first detection module 2712 is used to detect the first information identifier. The first processing module 2713 is configured to determine whether the wireless connection or disconnection with the first device is normal according to the first information identifier.

In some possible implementations, the first information identifier is used to indicate whether the wireless connection or disconnection with the first device is completed; the first processing module 2713 is used to: determine the wireless connection with the first device according to the first information identifier. or whether the execution of disconnection is completed; when the wireless connection or disconnection with the first device is not completed, it is determined that the wireless connection or disconnection with the first device is abnormal; when the wireless connection or disconnection with the first device is not completed, When the start execution is completed, it is determined that the wireless connection or disconnection with the first device is normal.

In some possible implementations, when the first processing module 2713 is used to determine that the wireless connection or disconnection with the first device is abnormal, the first processing module 2713 is also used to: perform at least one more connection with the first device. A device is wirelessly connected or disconnected; and the first information identifier is detected at least once until the first information identifier indicates that the wireless connection or disconnection with the first device is completed.

In some possible implementations, the first connection module 2711 includes: a state machine module and a wireless communication protocol stack module. Among them, the state machine module is used to call the wireless communication protocol stack module according to the connection request data; the wireless communication protocol stack module is used to perform wireless connection or disconnection with the first device to form a first information identifier, where the first information The identifier is used to indicate the execution status of wireless connection or disconnection between the wireless communication protocol stack module and the first device.

In some possible implementations, after the first processing module 2713 is used to wirelessly connect with the first device, the first processing module 2713 is also used to: perform master-slave authentication with the first device.

In some possible implementations, the first processing module 2713 is configured to: receive a first message and a first random number sent by the first device, where the first message is used to indicate master-slave authentication of the first device; Execute algorithm processing on random numbers to obtain the first target number; send a second message matching the first message and the first target number to the first device, so that the first device recognizes the second message and responds to the first target number. Perform algorithm check on the number to determine the result of master-slave authentication.

Figure 28 shows a schematic structural block diagram of another battery management device 2800 provided by an embodiment of the present application.

As shown in Figure 28, in the embodiment of the present application, the battery management device 2800 includes: the above-mentioned wireless connection device 2710 and a control device 2810. The control device 2810 is connected to the wireless connection device 2710, and the control device 2810 includes: a second detection module 2811 and the second processing module 2812.

Specifically, the second detection module 2811 is used to detect the first status identifier of the wireless connection device 2710. The second processing module 2812 is configured to determine whether the wireless connection or disconnection between the wireless connection device 2710 and the first device is normal according to the first status identifier.

In some possible implementations, as shown in Figure 28, the control device 2810 also includes: a second receiving module 2813 and a second sending module 2814. The second receiving module 2813 is configured to obtain a connection request command, which is used to instruct wireless connection or disconnection between the battery management device and the first device. The second processing module 2812 is configured to convert the connection request command based on the first communication protocol into the connection request data based on the second communication protocol, where the first communication protocol and the second communication protocol are two different types of communication. protocol. The second sending module 2814 is configured to send connection request data to the wireless connection device 2710, so that the wireless connection device 2710 wirelessly connects or disconnects with the first device according to the connection request data.

In some possible implementations, the second processing module 2812 is configured to determine whether the wireless connection or disconnection between the wireless connection device 2710 and the first device is normal based on the first status identifier and the connection request data.

In some possible implementations, the second processing module 2812 is used to: determine whether the connection status indicated by the first status identifier is consistent with the connection request indicated by the connection request data; when the connection status indicated by the first status indicator is consistent with the connection request data, When the connection request indicated by the connection request data is consistent, it is determined that the wireless connection or disconnection between the wireless connection device 2710 and the first device is normal; when the connection state indicated by the first status identifier is consistent with the connection request data indication If the connection requests are inconsistent, it is determined that the wireless connection or disconnection between the wireless connection device 2710 and the first device is abnormal.

In some possible implementations, when the second processing module 2812 determines that the wireless connection or disconnection between the wireless connection device 2710 and the first device is abnormal, the second processing module 2812 is also configured to: according to the connection request Command to control the wireless connection device 2710 to wirelessly connect or disconnect with the first device at least once; detect the first status identifier of the wireless connection device 2710 at least once until the wireless connection or disconnection between the wireless connection device 2710 and the first device is determined normal.

In some possible implementations, as shown in Figure 28, the control device 2810 also includes a non-volatile storage module 2815. After the second processing module 2812 converts the connection request command into the connection request data, the second processing module 2812 is also used to: store the connection request data in the non-volatile storage module 2815.

In some possible implementations, the wireless connection device 2710 is used to connect or disconnect with the first device via Bluetooth. Specifically, the first connection module 2711 in the wireless connection device 2710 is used to connect or disconnect with the first device via Bluetooth.

In some possible implementations, the battery management device 2700 or the battery management device 2800 is a master battery management unit (MBMU) in the powered device, and the first device is a slave battery management unit (SBMU) in the powered device; or , the above-mentioned battery management device 2700 or battery management device 2800 is the rechargeable battery management unit (CBMU) in the power exchange device, and the first device is the slave battery management unit (SBMU) in the power exchange device; or, the above-mentioned battery management device 2700 or The battery management device 2800 is a battery replacement battery management unit (TBMU) in the power replacement device, and the first device is a main battery management unit (MBMU) in the power consumption device.

Figure 29 shows a schematic structural block diagram of another battery management device 2900 provided by an embodiment of the present application.

As shown in Figure 29, the battery management device 2900 includes: a processor 2910 and a memory 2920, where the memory 2920 is used to store programs, and the processor 2910 is used to call and run the program from the memory 2920 to perform the wireless operation in the above embodiment. connection method.

Specifically, the battery management device 2900 may also include a wireless connection device and a control device, where the wireless connection device includes a first processor and a first memory. The first processor and the first memory cooperate with each other and are used to implement the above. In the embodiment, the wireless connection device serves as the execution subject of the wireless connection method. In addition, the control device includes a second processor and a second memory. The second processor and the second memory cooperate with each other and are used to implement the wireless connection method in which the control device serves as the execution subject in the above embodiment.

Figure 30 shows a schematic structural block diagram of an electronic device 3000 provided by an embodiment of the present application.

As shown in Figure 30, the electronic device 3000 may include: the above-mentioned battery management device 2700, battery management device 2800 or battery management device 2900.

Optionally, the electronic device 3000 may be an electrical device. For example, the electrical device may be the vehicle 1 shown in FIG. 1 . Alternatively, the electronic device 3000 may also be a power swapping device. For example, the power swapping device may be the power swapping station 2 shown in FIG. 2 .

It should be understood that the specific examples herein are only to help those skilled in the art better understand the embodiments of the present application, but are not intended to limit the scope of the embodiments of the present application.

It should also be understood that in the various embodiments of the present application, the size of the sequence numbers of each process does not mean the order of execution. The execution order of each process should be determined by its functions and internal logic, and should not be used in the embodiments of the present application. The implementation process constitutes any limitation.

It should also be understood that the various implementation modes described in this specification can be implemented individually or in combination, and the embodiments of the present application are not limited to this.

While the present application has been described with reference to preferred embodiments, various modifications may be made and equivalents may be substituted for components thereof without departing from the scope of the application. In particular, as long as there is no structural conflict, the technical features mentioned in the various embodiments can be combined in any way. The application is not limited to the specific embodiments disclosed herein, but includes all technical solutions falling within the scope of the claims.

Claims

A wireless connection method for battery management equipment, characterized by including:

Wirelessly connect or disconnect from the first device;

Detect connection status data with the first device;

According to the connection status data, it is determined whether the wireless connection or disconnection with the first device is normal.
The wireless connection method according to claim 1, characterized in that the battery management device includes: a wireless connection device; the connection status data includes: a first status identifier, the first status identifier is used to indicate the The wireless connection device and the first device are connected to or disconnected from each other.
The wireless connection method according to claim 2, wherein the wireless connection or disconnection with the first device includes:

The wireless connection device receives connection request data;

The wireless connection device wirelessly connects or disconnects from the first device according to the connection request data;

The connection status data between the detection and the first device includes:

The wireless connection device detects the first status identifier;

Determining whether the wireless connection or disconnection with the first device is normal based on the connection status data includes:

The wireless connection device determines whether the wireless connection or disconnection with the first device is normal based on the first status identifier and the connection request data.
The wireless connection method according to claim 3, characterized in that the wireless connection device determines whether the wireless connection or disconnection with the first device is based on the first status identifier and the connection request data. Whether it is normal, including:

The wireless connection device determines whether the connection status indicated by the first status identifier is consistent with the connection request indicated by the connection request data;

When the connection state indicated by the first status identifier is consistent with the connection request indicated by the connection request data, the wireless connection device determines that the wireless connection with the first device is normal;

When the connection status indicated by the first status identifier is inconsistent with the connection request indicated by the connection request data, the wireless connection device determines that the wireless connection with the first device is abnormal.
The wireless connection method according to claim 4, wherein when the wireless connection device determines that the wireless connection or disconnection with the first device is abnormal, the wireless connection method further includes:

The wireless connection device performs wireless connection or disconnection with the first device at least once according to the connection request data;

The wireless connection device detects the first status identifier at least once until the number of executions reaches a preset number or the connection status indicated by the first status indicator is consistent with the connection request indicated by the connection request data.
The wireless connection method according to any one of claims 3 to 5, characterized in that the wireless connection device includes a structure module and/or a non-volatile storage module;

Wherein, after the wireless connection device receives the connection request data, the wireless connection method further includes:

The wireless connection device stores the connection request data in the structure module and/or the non-volatile storage module;

And the wireless connection device stores the first status identifier in the structure module and/or the non-volatile storage module.
The wireless connection method according to claim 6, wherein after the wireless connection device stores the connection request data in the non-volatile storage module, the wireless connection method further includes:

After the battery management device is powered off and powered on again, the wireless connection device reads the connection request data from the non-volatile storage module;

The wireless connection device wirelessly connects or disconnects with the first device again according to the connection request data.
The wireless connection method according to claim 7, wherein after the wireless connection device stores the first status identifier in the non-volatile storage module, the wireless connection method further includes:

After the battery management device is powered off and powered on again, the wireless connection device reads the first status identifier from the non-volatile storage module;

Wherein, the wireless connection device wirelessly connects or disconnects with the first device again according to the connection request data, including:

The wireless connection device wirelessly connects or disconnects with the first device again according to the connection request data and the first status identifier.
The wireless connection method according to claim 8, characterized in that after the battery management device is powered off and powered on again, the wireless connection device reads the connection information from the non-volatile storage module. The disconnect request data is the connection request data;

Wherein, the wireless connection device wirelessly connects or disconnects from the first device according to the connection request data and the first status identifier, including:

The wireless connection device determines whether the disconnection state indicated by the first status indicator is connected;

When the connection state indicated by the first status identifier is connected, the wireless connection device wirelessly connects to the first device again according to the connection request data.
The wireless connection method according to any one of claims 2 to 9, characterized in that the connection status data further includes: a first information identifier, the first information identifier is used to indicate that the wireless connection device and The execution status of wireless connection or disconnection of the first device;

Wherein, the connection status data between the detection and the first device includes:

The wireless connection device detects the first information identifier;

Determining whether the wireless connection or disconnection with the first device is normal based on the connection status data includes:

The wireless connection device determines whether the wireless connection or disconnection with the first device is normal based on the first information identifier.
The wireless connection method according to claim 10, wherein the first information identifier is used to indicate whether the execution of wireless connection or disconnection with the first device is completed;

Wherein, the wireless connection device determines whether the wireless connection or disconnection with the first device is normal based on the first information identifier, including:

The wireless connection device determines whether the execution of wireless connection or disconnection with the first device is completed based on the first information identifier;

When the wireless connection or disconnection with the first device is not completed, the wireless connection device determines that the wireless connection or disconnection with the first device is abnormal;

When the wireless connection or disconnection with the first device is completed, the wireless connection device determines that the wireless connection or disconnection with the first device is normal.
The wireless connection method according to claim 11, characterized in that, when the wireless connection device determines that the wireless connection or disconnection with the first device is abnormal, the wireless connection method further includes:

The wireless connection device performs wireless connection or disconnection with the first device at least once;

The wireless connection device detects the first information identifier at least once again until the first information identifier indicates that the wireless connection or disconnection with the first device is completed.
The wireless connection method according to any one of claims 10 to 12, characterized in that the wireless connection device includes: a state machine module and a wireless communication protocol stack module;

Wherein, wirelessly connecting or disconnecting with the first device according to the connection request data includes:

The state machine module calls the wireless communication protocol stack module according to the connection request data;

The wireless communication protocol stack module performs wireless connection or disconnection with the first device to form the first information identifier, wherein the first information identifier is used to indicate that the wireless communication protocol stack module is connected to the first device. The first device performs wireless connection or disconnection.
The wireless connection method according to any one of claims 2 to 13, characterized in that, after wirelessly connecting with the first device, the wireless connection method further includes:

The wireless connection device performs master-slave authentication with the first device.
The wireless connection method according to claim 14, characterized in that the wireless connection device performs master-slave authentication with the first device, including:

The wireless connection device receives a first message and a first random number sent by the first device, where the first message is used to indicate master-slave authentication of the first device;

The wireless connection device performs algorithm processing on the first random number to obtain a first target number;

The wireless connection device sends a second message matching the first message and the first target number to the first device, so that the first device recognizes the second message and responds to The first target number is checked algorithmically to determine the result of master-slave authentication.
The wireless connection method according to any one of claims 2 to 15, wherein the battery management device includes: a control device, the control device is connected to the wireless connection device;

Wherein, the connection status data between the detection and the first device includes:

The control device detects the first status identifier of the wireless connection device;

Determining whether the wireless connection or disconnection with the first device is normal based on the connection status data includes:

The control device determines whether the wireless connection or disconnection between the wireless connection device and the first device is normal based on the first status identifier.
The wireless connection method according to claim 16, wherein the wireless connection or disconnection with the first device includes:

The control device obtains a connection request command, and the connection request command is used to instruct wireless connection or disconnection between the battery management device and the first device;

The control device converts the connection request command based on the first communication protocol into connection request data based on the second communication protocol, wherein the first communication protocol is different from the second communication protocol;

The control device sends the connection request data to the wireless connection device, so that the wireless connection device wirelessly connects or disconnects with the first device according to the connection request data.
The wireless connection method according to claim 17, characterized in that the control device determines whether the wireless connection or disconnection between the wireless connection device and the first device is normal based on the first status identifier, include:

The control device determines whether the wireless connection or disconnection between the wireless connection device and the first device is normal based on the first status identifier and the connection request data.
The wireless connection method according to claim 18, characterized in that the control device determines the wireless connection between the wireless connection device and the first device based on the first status identifier and the connection request data. Whether the connection or disconnection is normal, including:

The control device determines whether the connection status indicated by the first status indicator is consistent with the connection request indicated by the connection request data;

When the connection status indicated by the first status identifier is consistent with the connection request indicated by the connection request data, the control device determines the wireless connection between the wireless connection device and the first device. Or disconnected as normal;

When the connection status indicated by the first status identifier is inconsistent with the connection request indicated by the connection request data, the control device determines the wireless connection between the wireless connection device and the first device. Or disconnected as an exception.
The wireless connection method according to any one of claims 16 to 19, wherein the control device determines that the wireless connection or disconnection between the wireless connection device and the first device is abnormal. Below, the wireless connection method also includes:

The control device controls the wireless connection device to wirelessly connect or disconnect with the first device at least once according to the connection request command;

The control device detects the first status identifier of the wireless connection device at least once until it is determined that the wireless connection or disconnection between the wireless connection device and the first device is normal.
The wireless connection method according to any one of claims 17 to 20, characterized in that the control device includes a non-volatile storage module, and the control device converts the connection request command into a connection request. After data, the wireless connection method also includes:

The control device stores the connection request data in the non-volatile storage module.
The wireless connection method according to any one of claims 1 to 21, wherein the wireless connection or disconnection with the first device includes:

Bluetooth connection or disconnection with the first device.
The wireless connection method according to any one of claims 1 to 22, wherein the battery management device is a main battery management unit MBMU in the powered device, and the first device is a main battery management unit in the powered device. the slave battery management unit SBMU; or,

The battery management device is the rechargeable battery management unit CBMU in the power swap device, and the first device is the slave battery management unit SBMU in the power swap device; or,

The battery management device is a battery replacement battery management unit TBMU in a power replacement device, and the first device is a main battery management unit MBMU in a power consumption device.
A battery management device, characterized in that it includes: a wireless connection device, the wireless connection device includes:

The first connection module is used to wirelessly connect or disconnect with the first device;

A first detection module, configured to detect connection status data with the first device;

The first processing module is configured to determine whether the wireless connection or disconnection with the first device is normal according to the connection status data.
The battery management device according to claim 24, wherein the connection status data includes: a first status identifier, the first status identifier is used to indicate the connection between the wireless connection device and the first device. Connect or disconnect from each other.
The battery management device according to claim 25, wherein the first connection module is configured to: receive connection request data, and wirelessly connect or disconnect with the first device according to the connection request data;

The first detection module is used to: detect the first status identifier;

The first processing module is configured to determine whether the wireless connection or disconnection with the first device is normal according to the first status identifier and the connection request data.
The battery management device according to claim 26, characterized in that the first processing module is used for:

Determine whether the connection status indicated by the first status identifier is consistent with the connection request indicated by the connection request data;

When the connection status indicated by the first status identifier is consistent with the connection request indicated by the connection request data, determine that the wireless connection with the first device is normal;

If the connection status indicated by the first status identifier is inconsistent with the connection request indicated by the connection request data, it is determined that the wireless connection with the first device is abnormal.
The battery management device according to claim 27, wherein when the first processing module determines that the wireless connection or disconnection with the first device is abnormal, the first processing module further Used for:

According to the connection request data, perform wireless connection or disconnection with the first device at least once;

The first status identifier is detected at least once until the number of executions reaches a preset number or the connection status indicated by the first status identifier is consistent with the connection request indicated by the connection request data.
The battery management device according to any one of claims 26 to 28, wherein the wireless connection device further includes a structural module and/or a non-volatile storage module;

The first processing module is also configured to: store the connection request data to the structure module and/or the non-volatile storage module;

And store the first status identifier in the structure module and/or the non-volatile storage module.
The battery management device according to claim 29, wherein after the first processing module stores the connection request data into the non-volatile storage module, the first processing module further Used for:

After the battery management device is powered off and powered on again, read the connection request data from the non-volatile storage module;

According to the connection request data, wirelessly connect or disconnect with the first device again.
The battery management device according to claim 30, wherein after the first processing module stores the first status identifier into the non-volatile storage module, the first processing module further Used for:

After the battery management device is powered off and powered on again, read the first status identifier from the non-volatile storage module;

Wirelessly connect or disconnect with the first device again according to the connection request data and the first status identifier.
The battery management device according to claim 31, characterized in that, after the battery management device is powered off and powered on again, the first processing module reads the data from the non-volatile storage module. The connection request data is the connection request data;

The first processing module is configured to: determine whether the connection state indicated by the first status indicator is connected;

When the connection state indicated by the first status identifier is connected, wirelessly connect to the first device again according to the connection request data.
The battery management device according to any one of claims 24 to 32, characterized in that the connection status data further includes: a first information identifier, the first information identifier is used to indicate that the wireless connection device and The execution status of wireless connection or disconnection of the first device;

The first detection module is used to: detect the first information identifier;

The first processing module is configured to determine whether the wireless connection or disconnection with the first device is normal according to the first information identifier.
The battery management device according to claim 33, wherein the first information identifier is used to indicate whether the execution of wireless connection or disconnection with the first device is completed;

The first processing module is configured to: determine whether the execution of wireless connection or disconnection with the first device is completed according to the first information identifier;

When the wireless connection or disconnection with the first device is not completed, determine that the wireless connection or disconnection with the first device is abnormal;

When the wireless connection or disconnection with the first device is completed, it is determined that the wireless connection or disconnection with the first device is normal.
The battery management device according to claim 34, wherein when the first processing module determines that the wireless connection or disconnection with the first device is abnormal, the first processing module Modules are also used for:

Perform wireless connection or disconnection with the first device at least once again;

The first information identifier is detected at least once again until the first information identifier indicates that the wireless connection or disconnection with the first device is completed.
The battery management device according to any one of claims 33 to 35, wherein the first connection module includes: a state machine module and a wireless communication protocol stack module;

The state machine module is used to call the wireless communication protocol stack module according to the connection request data;

The wireless communication protocol stack module is configured to perform wireless connection or disconnection with the first device to form the first information identifier, wherein the first information identifier is used to indicate that the wireless communication protocol stack module is connected to or disconnected wirelessly from the first device. The execution status of wireless connection or disconnection of the first device.
The battery management device according to any one of claims 24 to 36, wherein after the first processing module is used to wirelessly connect with the first device, the first receiving unit and the first Processing modules are also used to:

Perform master-slave authentication with the first device.
The battery management device according to claim 37, wherein the wireless connection device further includes: a first sending unit;

The first receiving unit is configured to: receive a first message and a first random number sent by the first device, where the first message is used to indicate master-slave authentication of the first device;

The first processing module is configured to: perform algorithm processing on the first random number to obtain a first target number;

The first sending unit is configured to: send a second message matching the first message and the first target number to the first device, so that the first device identifies the second message. document, perform an algorithm check on the first target number, and determine the result of the master-slave authentication.
The battery management device according to any one of claims 25 to 38, characterized in that the battery management device further includes: a control device, the control device is connected to the wireless connection device, and the control device includes :

a second detection module, configured to detect the first status identifier of the wireless connection device;

The second processing module is configured to determine whether the wireless connection or disconnection between the wireless connection device and the first device is normal according to the first status identifier.
The battery management device according to claim 39, wherein the control device further includes: a second receiving module and a second sending module;

The second receiving module is configured to: obtain a connection request command, where the connection request command is used to indicate wireless connection or disconnection between the battery management device and the first device;

The second processing module is configured to convert the connection request command based on the first communication protocol into connection request data based on the second communication protocol, wherein the first communication protocol and the second communication protocol different;

The second sending module is configured to send the connection request data to the wireless connection device, so that the wireless connection device wirelessly connects or disconnects with the first device according to the connection request data.
The battery management device according to claim 40, wherein the second processing module is configured to determine whether the wireless connection device is connected to the first connection device according to the first status identifier and the connection request data. Whether the wireless connection or disconnection between devices is normal.
The battery management device according to claim 41, characterized in that the second processing module is used for:

Determine whether the connection status indicated by the first status identifier is consistent with the connection request indicated by the connection request data;

When the connection state indicated by the first status identifier is consistent with the connection request indicated by the connection request data, it is determined that the wireless connection or disconnection between the wireless connection device and the first device is normal;

When the connection status indicated by the first status identifier is inconsistent with the connection request indicated by the connection request data, it is determined that the wireless connection or disconnection between the wireless connection device and the first device is abnormal.
The battery management device according to any one of claims 39 to 42, wherein the second processing module determines that the wireless connection or disconnection between the wireless connection device and the first device is abnormal. In the case of , the second processing module is also used to:

Control the wireless connection device to wirelessly connect or disconnect with the first device at least once according to the connection request command;

The first status identifier of the wireless connection device is detected at least once until it is determined that the wireless connection or disconnection between the wireless connection device and the first device is normal.
The battery management device according to any one of claims 40 to 43, characterized in that the control device further includes a non-volatile storage module, and the second processing module converts the connection request command into After continuously requesting data, the second processing module is also used to:

The connection request data is stored in the non-volatile storage module.
The battery management device according to any one of claims 24 to 44, characterized in that the first connection module is used to connect or disconnect with the first device via Bluetooth.
The battery management device according to any one of claims 24 to 45, wherein the battery management device is a main battery management unit MBMU in a powered device, and the first device is a main battery management unit in the powered device. the slave battery management unit SBMU; or,

The battery management device is the rechargeable battery management unit CBMU in the power swap device, and the first device is the slave battery management unit SBMU in the power swap device; or,

The battery management device is a battery replacement battery management unit TBMU in a power replacement device, and the first device is a main battery management unit MBMU in a power consumption device.
A battery management device, characterized in that it includes: a processor and a memory, the memory is used to store a program, the processor is used to call and run the program from the memory to execute any one of claims 1 to 23 Described wireless connection method.
An electronic device, characterized by comprising: the battery management device according to any one of claims 24 to 47.
The electronic device according to claim 48, characterized in that the electronic device is a power consumption device or a power exchange device.