Wireless connection method of battery management device and battery management device

Abstract

The embodiment of the present application provides a kind of battery management equipment wireless connection method and battery management equipment, which can improve the connection performance of battery management equipment.The battery management equipment wireless connection method comprises: with the first device is connected or disconnected wirelessly;Detection is connected or disconnected between the first device state data;According to the connection or disconnection state data, judge whether the wireless connection or disconnection between the first device is normal.Through the technical scheme, after the battery management equipment and the first device are connected or disconnected wirelessly, the battery management equipment detects the connection or disconnection state data between the first device, and judges whether the wireless connection or disconnection between the first device is normal according to the connection or disconnection state data, which is conducive to realizing the effective monitoring of the wireless connection or disconnection state between the battery management equipment and the first device, so as to improve the connection performance between the battery management equipment and the first device.

Description

Technical Field

[0001] This application relates to the field of batteries, and more specifically, to a wireless connection method for a battery management device and a battery management device. Background Technology

[0002] With the development of the times, electric vehicles, due to their advantages such as high environmental friendliness, low noise, and low operating costs, have a huge market prospect and can effectively promote energy conservation and emission reduction, which is beneficial to social development and progress. For electric vehicles, battery technology is a crucial factor in their development.

[0003] Currently, battery manufacturers, electric vehicles, and battery swapping stations can be equipped with battery management devices, such as Battery Manager Units (BMUs). These devices can connect and exchange information with other equipment, for example, battery management devices from different organizations can connect and exchange information to facilitate battery monitoring and management. Poor connectivity between battery management devices and other devices can affect the device's ability to manage batteries and create safety hazards. Therefore, improving the connectivity of battery management devices is a pressing technical problem that needs to be solved. Summary of the Invention

[0004] This application provides a wireless connection method and a battery management device, which can improve the connection performance of the battery management device.

[0005] In a first aspect, a wireless connection method for a battery management device is provided, comprising: wirelessly connecting or disconnecting from a first device; detecting connection / disconnection status data between the device and the first device; and determining, based on the connection / disconnection status data, whether the wireless connection or disconnection with the first device is normal.

[0006] Through the technical solution of the embodiments of this 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 itself and the first device, and determines whether the wireless connection between itself and the first device is normal based on the connection status data. This is beneficial to achieve 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.

[0007] In some possible implementations, the battery management device includes: a wireless connection device; the connection / disconnection status data includes: a first status identifier, the first status identifier indicating whether the wireless connection device and the first device are connected or disconnected.

[0008] The technical solution of this embodiment includes a wireless connection device in the battery management device, and uses a first status identifier for indicating whether the wireless connection device and the first device are connected or disconnected as connection status data to determine whether the wireless connection between the battery management device and the first device is normal. This method has high accuracy and is easy to implement through hardware and / or software.

[0009] In some possible implementations, the aforementioned wireless connection or disconnection with the first device includes: the wireless connection device receiving connection / disconnection request data; the wireless connection device wirelessly connecting or disconnecting with the first device according to the connection / disconnection request data; the aforementioned detection of connection / disconnection status data with the first device includes: the wireless connection device detecting a first status identifier; the aforementioned determination of whether the wireless connection or disconnection with the first device is normal based on the connection / disconnection status data includes: the wireless connection device determining whether the wireless connection or disconnection with the first device is normal based on the first status identifier and the connection / disconnection request data.

[0010] Through the technical solution of this embodiment, the wireless connection device detects a first status identifier used to indicate the connection status with the first device, and judges whether the wireless connection or disconnection with the first device is normal by combining the first status identifier and the connection request data. This is beneficial to realize the effective monitoring of the wireless connection status with the first device by the wireless connection device, thereby improving the connection performance between the battery management device and the first device.

[0011] 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 / disconnection request data, including: the wireless connection device determining whether the connection / disconnection status indicated by the first status identifier is consistent with the connection / disconnection request indicated by the connection / disconnection request data; if the connection / disconnection status indicated by the first status identifier is consistent with the connection / disconnection request indicated by the connection / disconnection request data, the wireless connection device determines that the wireless connection with the first device is normal; if the connection / disconnection status indicated by the first status identifier is inconsistent with the connection / disconnection request indicated by the connection / disconnection request data, the wireless connection device determines that the wireless connection with the first device is abnormal.

[0012] In this embodiment, by determining whether the connection / disconnection status indicated by the first status identifier is consistent with the connection / disconnection request indicated by the connection / disconnection request data, it is possible to accurately determine whether the wireless connection or disconnection between the wireless connection device and the first device is normal. This technical solution is convenient to implement and highly accurate. It can not only accurately and effectively monitor the wireless connection / disconnection between the wireless connection device and the first device, but also be easily implemented in the wireless connection device through hardware and / or software.

[0013] 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 performing the wireless connection or disconnection with the first device at least once more according to the connection / disconnection request data; the wireless connection device detecting the first status indicator at least once until the number of executions reaches a preset number or the connection / disconnection status indicated by the first status indicator is consistent with the connection / disconnection request indicated by the connection / disconnection request data.

[0014] Through this implementation, when an anomaly occurs in the wireless connection between the wireless connection device and the first device, the wireless connection device itself can repair the anomaly, restoring the wireless connection to normal, thereby further improving the connection reliability between the battery management device and the first device. Alternatively, if the wireless connection device repeatedly performs the wireless connection disconnection action with the first device a preset number of times and cannot repair the anomaly, the wireless connection device will no longer continue to repeatedly perform the wireless connection disconnection action with the first device, thus avoiding waste of system resources and optimizing the overall performance of the battery management device to some extent.

[0015] 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 connection / disconnection request data, the wireless connection method further includes: the wireless connection device storing the connection / disconnection request data in the structure module and / or the non-volatile storage module.

[0016] Through the technical solution of this embodiment, after receiving connection loss request data, the wireless connection device can write the connection loss request data into a structure module in memory. This allows for rapid reading and writing of the connection loss request data in the structure module during subsequent processes, and enables repair of connection faults based on the connection loss request data, thereby improving the connection reliability between the wireless connection device and the first device. Furthermore, after receiving the connection loss request data, the wireless connection device can also store the connection loss request data in a non-volatile storage module, thus preventing the loss of the connection loss request data due to external factors such as power failure. This ensures the monitoring performance of the wireless connection device on the connection status with the first device, further improving the connection reliability between the battery management device and the first device.

[0017] In some possible implementations, after detecting the first state identifier, the wireless connection method further includes writing the first state identifier into a structure module and / or a non-volatile storage module.

[0018] Through this implementation, after the wireless connection device detects the first status identifier, it can also write the first status identifier into a structure module in memory. This allows for rapid reading and writing of the first status identifier in the structure module during subsequent processes, and enables monitoring of the connection status between the wireless connection device and the first device based on the first status identifier, thereby improving the monitoring efficiency of the connection status between the wireless connection device and the first device. Furthermore, after the wireless connection device detects the first status identifier, it can also write the first status identifier into a non-volatile storage module to prevent loss of the first status identifier due to external factors such as power failure, ensuring the monitoring performance of the wireless connection device regarding the connection status with the first device.

[0019] 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 then powered on again, the wireless connection device reads the connection request data from the non-volatile storage module; and the wireless connection device reconnects or disconnects wirelessly with the first device based on the connection request data.

[0020] According to the technical solution of this embodiment, a non-volatile memory (NVM) module can be set in the wireless connection device. When the wireless connection device receives connection disconnection request data, it can synchronously store the connection disconnection request data in the NVM module. After the battery management device is powered off and then powered on again, the wireless connection device can read the connection disconnection request data from the NVM module and automatically re-establish the wireless connection with the first device according to the connection disconnection request data, thereby eliminating the impact of the power failure of the battery management device on the wireless connection between the battery management device and the first device, and thus improving the connection performance between the battery management device and the first device.

[0021] 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 then powered on again, the wireless connection device reads the first status identifier from the non-volatile storage module; wherein, the wireless connection device reconnects or disconnects wirelessly with the first device according to the connection / disconnection request data includes: the wireless connection device reconnects or disconnects wirelessly with the first device according to the connection / disconnection request data and the first status identifier.

[0022] According to the technical solution of this embodiment, after the battery management device is powered off and then powered on again, the wireless connection device can read the first status identifier and connection request data from the NVM module, and automatically re-establish the wireless connection with the first device based on the first status identifier and connection request data. Therefore, this technical solution can automatically eliminate the impact of power failure on the wireless connection between the battery management device and the first device, while also improving the reliability of the wireless connection device automatically re-establishing the wireless connection with the first device, thereby further improving the connection performance between the battery management device and the first device.

[0023] In some possible implementations, after the battery management device is powered off and then powered 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 wirelessly connects or disconnects from the first device according to the connection request data and the first status identifier, including: determining whether the connection status indicated by the first status identifier is a connection; if the connection status indicated by the first status identifier is a connection, wirelessly connecting to the first device again according to the connection request data.

[0024] The technical solution of this embodiment, when the connection status indicated by the first status identifier is connected, indicates that the wireless connection device and the first device are connected 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 the reconnection between the wireless connection device and the first device, and restore the state between the wireless connection device and the first device to that before the battery management device was powered off.

[0025] In some possible implementations, the connection / disconnection status data further includes: a first information identifier, which indicates the execution status of wireless connection or disconnection between the wireless connection device and the first device; wherein, detecting the connection / disconnection status data with the first device includes: the wireless connection device detecting the first information identifier; determining whether the wireless connection or disconnection with the first device is normal based on the connection / disconnection status data includes: the wireless connection device determining whether the wireless connection or disconnection with the first device is normal based on the first information identifier.

[0026] Through the technical solution of this embodiment, the wireless connection device detects a first information identifier used to indicate the execution status of wireless connection or disconnection with the first device, and determines whether the wireless connection or disconnection with the first device is normal based on the first information identifier. This is beneficial to enable the wireless connection device to effectively monitor the wireless connection status with the first device, thereby improving the connection performance between the battery management device and the first device.

[0027] In some possible implementations, the first information identifier is used to indicate whether the execution of wireless connection or disconnection with the first device has been 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 has been completed based on the first information identifier; if the wireless connection or disconnection with the first device has not been completed, the wireless connection device determines that the wireless connection or disconnection with the first device is abnormal; if the wireless connection or disconnection with the first device has been completed, the wireless connection device determines that the wireless connection or disconnection with the first device is normal.

[0028] In this embodiment, the first information identifier is used to determine whether the wireless connection or disconnection with the first device has been completed, which helps to determine whether the wireless connection or disconnection between the wireless connection device and the first device is normal. This technical solution can improve the connection performance between the wireless connection device and the first device, and can be easily implemented in the wireless connection device through hardware and / or software.

[0029] In some possible implementations, if 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 performing the wireless connection or disconnection with the first device at least once more; and the wireless connection device detecting the first information identifier at least once more until the first information identifier indicates that the wireless connection or disconnection with the first device has been completed.

[0030] Through the technical solution of this embodiment, in the event of an abnormal 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 is restored to normal, thereby further improving the connection reliability between the battery management device and the first device.

[0031] 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 connection / disconnection request data includes: the state machine module calling the wireless communication protocol stack module according to the connection / disconnection request data; the wireless communication protocol stack module executing wireless connection or disconnection with the first device to form a first information identifier, wherein the first information identifier is used to indicate the execution status of wireless connection or disconnection with the first device by the wireless communication protocol stack module.

[0032] According to the technical solution of this embodiment, the wireless connection device may include multiple software modules, wherein different software modules are used to perform different functions and can cooperate with each other. The wireless communication protocol stack module is used to specifically implement the 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 execution status of the wireless connection device's wireless connection or disconnection with the first device.

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

[0034] 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 be compatible with each other, thereby ensuring normal data transmission between the wireless connection device and the first device and improving system robustness.

[0035] In some possible implementations, the wireless connection device performs master-slave authentication with the first device, including: the wireless connection device receiving a first message and a first random number sent by the first device, the first message being used to indicate master-slave authentication of the first device; the wireless connection device performing algorithm processing on the first random number to obtain a first target number; the wireless connection device sending a second message matching the first message and the first target number to the first device, so that the first device can identify the second message and perform algorithm checks on the first target number to determine the result of master-slave authentication.

[0036] Through the technical solution of this embodiment, the master-slave authentication process is realized between the wireless connection device and the first device through the interaction of messages and data. It can have high accuracy and is also convenient for the software and / or hardware inside the wireless connection device and the first device to implement the master-slave authentication process.

[0037] In some possible implementations, the battery management device includes: a control device connected to a wireless connection device; wherein detecting connection / disconnection status data with the first device includes: the control device detecting a 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 / disconnection status data includes: the control device determining whether the wireless connection or disconnection between the wireless connection device and the first device is normal based on the first status identifier.

[0038] This implementation solution eliminates the need to modify the existing hardware of the battery management device. By adding a wireless connection device to the battery management device and controlling this device via a control unit, a wireless connection between the battery management device and the first device can be achieved. This wireless connection method is relatively simple to implement and compatible with existing products. Furthermore, the control unit of the battery management device can detect the first status indicator of the wireless connection device and determine whether the wireless connection or disconnection between the two devices is normal based on this indicator. This facilitates effective monitoring of the wireless connection between the battery management device and the first device, thereby improving the connection performance between them.

[0039] In some possible implementations, wirelessly connecting or disconnecting from the first device includes: a control device acquiring a connection / disconnection request command, the connection / disconnection request command indicating wireless connection or disconnection between the battery management device and the first device; the control device converting the connection / disconnection request command based on a first communication protocol into connection / disconnection request data based on a second communication protocol, wherein the first communication protocol and the second communication protocol are different; and sending the connection / disconnection request data to the wireless connection device so that the wireless connection device wirelessly connects or disconnects from the first device according to the connection / disconnection request data.

[0040] Through this embodiment, the control device can receive a connection / disconnection request command based on a first communication protocol and send connection / disconnection request data based on a second communication protocol to the wireless connection device. The control device can communicate with external devices based on the first communication protocol, while 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, optimizing the communication performance between the control device and other devices and improving the overall communication performance of the battery management device.

[0041] 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 connection / disconnection request data.

[0042] Compared to technical solutions that rely solely on the first status identifier of the wireless connection device to determine whether the wireless connection or disconnection between the battery management device and the first device is normal, the technical solution of this embodiment combines both the first status identifier and connection / disconnection request data to determine whether the wireless connection or disconnection between the wireless connection device and the battery management device and the first device is normal, thus further improving the accuracy of the determination. Therefore, the technical solution of this embodiment can more effectively monitor the wireless connection / disconnection between the battery management device and the first device, thereby improving the connection performance between the battery management device and the first device.

[0043] 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 / disconnection request data. This includes: the control device determining whether the connection / disconnection status indicated by the first status identifier is consistent with the connection / disconnection request indicated by the connection / disconnection request data; if the connection / disconnection status indicated by the first status identifier is consistent with the connection / disconnection request indicated by the connection / disconnection request data, the control device determines that the wireless connection or disconnection between the wireless connection device and the first device is normal; if the connection / disconnection status indicated by the first status identifier is inconsistent with the connection / disconnection request indicated by the connection / disconnection request data, the control device determines that the wireless connection or disconnection between the wireless connection device and the first device is abnormal.

[0044] In this embodiment, by determining whether the connection / disconnection status indicated by the first status identifier is consistent with the connection / disconnection request indicated by the connection / disconnection request data, it is possible to accurately determine whether the wireless connection or disconnection between the wireless connection device and its battery management device and the first device is normal. This technical solution is convenient to implement and highly accurate. It can not only accurately and effectively monitor the wireless connection / disconnection between the battery management device and the first device, but also be easily implemented in a control device through hardware and / or software.

[0045] 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 controlling the wireless connection device to wirelessly connect or disconnect from the first device at least once according to a connection / disconnection request command; the control device detecting the first status indicator 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.

[0046] Through the technical solution of this embodiment, in the event of an abnormal 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 is restored to normal, thereby further improving the connection reliability between the battery management device and the first device.

[0047] In some possible implementations, the control device includes a non-volatile storage module, and after the control device converts the connection disconnection request command into connection disconnection request data, the wireless connection method further includes: the control device storing the connection disconnection request data in the non-volatile storage module.

[0048] The technical solution of this implementation can prevent the loss of connection request data caused by external factors such as power failure, and ensure that the subsequent control device can make judgments on the abnormal wireless connection between the wireless connection device and the first device, thereby further improving the connection performance between the battery management device and the first device.

[0049] In some possible implementations, wireless connection or disconnection with the first device includes: Bluetooth connection or disconnection with the first device.

[0050] In this embodiment, the battery management device can establish a Bluetooth connection with the first device via the Bluetooth communication protocol to enable subsequent data communication. This Bluetooth connection method features low power consumption, low latency, and low cost, making it suitable for installation in vehicles and / or battery swapping stations to achieve reliable short-range, low-cost communication.

[0051] In some possible implementations, the battery management device is the main battery management unit (MBMU) in the power-consuming device, and the first device is the slave battery management unit (SBMU) in the power-consuming device; or, the battery management device is the rechargeable battery management unit (CBMU) in the battery swapping device, and the first device is the slave battery management unit (SBMU) in the battery swapping device; or, the battery management device is the battery swapping battery management unit (TBMU) in the battery swapping device, and the first device is the main battery management unit (MBMU) in the power-consuming device.

[0052] In this implementation, the battery management device can be of various types and applied in different scenarios. This solution enables relatively stable wireless connection and disconnection between the TBMU and MBMU, and / or between the CBMU / MBMU and SBMU, thereby simplifying the connection methods between various battery management devices in power-consuming equipment and / or battery-swapping equipment, and improving the overall system's connection stability and robustness.

[0053] In a second aspect, a battery management device is provided, comprising: a wireless connection device, the wireless connection device comprising: a first connection / disconnection module for wirelessly connecting or disconnecting from a first device; a first detection module for detecting connection / disconnection status data with the first device; and a first processing module for determining, based on the connection / disconnection status data, whether the wireless connection or disconnection with the first device is normal.

[0054] In some possible implementations, the battery management device further includes: a control device connected to the wireless connection device, and the control device includes: a second detection module for detecting a first status indicator of the wireless connection device; and a second processing module for determining, based on the first status indicator, whether the wireless connection or disconnection between the wireless connection device and the first device is normal.

[0055] Thirdly, a battery management device is provided, comprising: a processor and a memory, the memory for storing a program, and the processor for calling and running the program from the memory to perform the wireless connection method in the first aspect or any possible implementation thereof.

[0056] Fourthly, an electronic device is provided, comprising: the battery management device described in the second or third aspect above.

[0057] In some possible implementations, the electronic device is a power-consuming device or a power-swapping device.

[0058] Through the technical solution of the embodiments of this 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 itself and the first device, and determines whether the wireless connection between itself and the first device is normal based on the connection status data. This is beneficial to achieve 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. Attached Figure Description

[0059] To more clearly illustrate the technical solutions of the embodiments of this application, the drawings used in the embodiments of this application will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on the drawings without creative effort.

[0060] Figure 1 This is a schematic structural block diagram of a vehicle to which one embodiment of this application applies;

[0061] Figure 2 This is a schematic structural block diagram of a battery swapping station applicable to an embodiment of this application;

[0062] Figure 3 This is a schematic flowchart illustrating a wireless connection method for a battery management device according to an embodiment of this application;

[0063] Figure 4 This is a schematic structural block diagram of a battery management device provided in one embodiment of this application;

[0064] Figure 5This is a schematic flowchart illustrating a wireless connection method provided in another embodiment of this application;

[0065] Figure 6 This is a schematic flowchart illustrating a wireless connection method provided in another embodiment of this application;

[0066] Figure 7 This is a schematic flowchart illustrating a wireless connection method provided in another embodiment of this application;

[0067] Figure 8 This is a schematic flowchart illustrating a wireless connection method provided in another embodiment of this application;

[0068] Figure 9 This is a schematic flowchart illustrating a wireless connection method provided in another embodiment of this application;

[0069] Figure 10 This is a schematic flowchart illustrating a wireless connection method provided in another embodiment of this application;

[0070] Figure 11 This is a schematic flowchart illustrating a wireless connection method provided in another embodiment of this application;

[0071] Figure 12 This is a schematic flowchart illustrating a wireless connection method provided in another embodiment of this application;

[0072] Figure 13 This is a schematic flowchart illustrating a wireless connection method provided in another embodiment of this application;

[0073] Figure 14 This is a schematic flowchart illustrating a wireless connection method provided in another embodiment of this application;

[0074] Figure 15 This is a schematic flowchart illustrating a wireless connection method provided in another embodiment of this application;

[0075] Figure 16 This is a schematic flowchart illustrating a wireless connection method provided in another embodiment of this application;

[0076] Figure 17 This is a schematic flowchart illustrating a wireless connection method provided in another embodiment of this application;

[0077] Figure 18 This is a schematic flowchart illustrating a wireless connection method provided in another embodiment of this application;

[0078] Figure 19 This is a schematic flowchart illustrating a wireless connection method provided in another embodiment of this application;

[0079] Figure 20 This is a schematic flowchart illustrating a wireless connection method provided in another embodiment of this application;

[0080] Figure 21 This is a schematic flowchart illustrating a wireless connection method provided in another embodiment of this application;

[0081] Figure 22 This is a schematic flowchart illustrating a wireless connection method provided in another embodiment of this application;

[0082] Figure 23 This is a schematic flowchart illustrating a wireless connection method provided in another embodiment of this application;

[0083] Figure 24 This is a schematic flowchart illustrating a wireless connection method provided in another embodiment of this application;

[0084] Figure 25 This is a schematic flowchart illustrating a wireless connection method provided in another embodiment of this application;

[0085] Figure 26 This is a schematic flowchart illustrating a wireless connection method provided in another embodiment of this application;

[0086] Figure 27 This is a schematic structural block diagram of a battery management device provided in one embodiment of this application;

[0087] Figure 28 This is a schematic structural block diagram of a battery management device provided in another embodiment of this application;

[0088] Figure 29 This is a schematic structural block diagram of a battery management device provided in another embodiment of this application;

[0089] Figure 30 This is a schematic structural block diagram of an electronic device provided in one embodiment of this application.

[0090] The accompanying drawings are not drawn to scale. Detailed Implementation

[0091] The embodiments of this 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 this application by way of example, but should not be used to limit the scope of this application, that is, this application is not limited to the described embodiments.

[0092] In the description of this application, it should be noted that, unless otherwise stated, "a plurality of" means two or more; the terms "upper", "lower", "left", "right", "inner", "outer", etc., indicating orientation or positional relationship are only for the convenience of describing this application and simplifying the description, and do not indicate or imply that the device or element referred to must have a specific orientation, or be constructed and operated in a specific orientation, and therefore should not be construed as a limitation of this application.

[0093] In this application, the term "and / or" is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent three possibilities: A exists, A and B exist simultaneously, and B exists. Additionally, in this application, the character " / " generally indicates that the preceding and following related objects have an "or" relationship.

[0094] Unless otherwise defined, all technical and scientific terms used in this application have the same meaning as commonly understood by one of ordinary skill in the art to which this application pertains; the terminology used in the description of this application is for the purpose of describing particular embodiments only and is not intended to limit the application; the terms "comprising" and "having," and any variations thereof, in the description, claims, and accompanying drawings of this application 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, not to describe a specific order or hierarchy.

[0095] In this application, the reference to "embodiment" means that a specific feature, structure, or characteristic described in connection with an embodiment may be included in at least one embodiment of this application. The appearance of this phrase in various places throughout the specification does not necessarily refer to the same embodiment, nor is it a mutually exclusive, independent, or alternative embodiment. It will be explicitly and implicitly understood by those skilled in the art that the embodiments described in this application can be combined with other embodiments.

[0096] In the field of new energy, batteries are of paramount importance as the primary power source for electrical devices such as electric vehicles, ships, or spacecraft. In this application, a battery refers to a single physical module comprising one or more battery cells to provide higher voltage and capacity. The battery generally includes a casing for encapsulating one or more battery cells. Optionally, the battery mentioned in this application may be referred to as a battery pack. Optionally, the battery can be any type of battery, such as lithium-ion batteries, lithium metal batteries, lithium-sulfur batteries, lead-acid batteries, nickel-metal hydride batteries, or lithium-air batteries, etc.

[0097] During battery operation, charging, and battery swapping, real-time monitoring of the battery's status is necessary to improve battery safety in each process. Therefore, depending on actual needs, battery management devices, such as battery management units (BMUs), can be installed inside the battery, in electrical devices, or at battery swapping stations to facilitate monitoring and management of the battery's operating status.

[0098] As an example, both electric vehicles and batteries are equipped with BMUs. The BMU in the electric vehicle can be called the Master Battery Manager Unit (MBMU), and the BMU inside the battery can be called the Slave Battery Manager Unit (SBMU). In this example, the MBMU and SBMU can connect to each other and exchange information to jointly monitor and manage the battery's operating status.

[0099] In some implementations, the MBMU and SBMU are interconnected via physical wiring (e.g., Controller Area Network (CAN) wiring). The installation of this physical wiring on the two BMUs is complex, impacting manufacturing and maintenance efficiency. In other implementations, the MBMU and SBMU are connected wirelessly. However, in this wireless connection method, communication between the MBMU and SBMU is susceptible to various environmental factors, making connection failures more likely.

[0100] Understandably, in addition to the MBMU and SBMU mentioned above, one or more BMUs will also be configured in the battery swapping station. These various BMUs in the battery swapping station are interconnected, and / or, the BMUs in the battery swapping station are interconnected with the BMUs in the power-consuming device. Therefore, under wireless connection methods, in addition to the MBMU and SBMU being prone to connection failures, connection failures are also relatively common between the various BMUs in the battery swapping station, and / or between the BMUs in the battery swapping station and the BMUs in the power-consuming device.

[0101] In view of this, this application provides a wireless connection method for a battery management device. This method is applied to a wireless connection device within the battery management device. The wireless connection method includes: receiving connection / disconnection request data; wirelessly connecting or disconnecting with a first device based on the connection / disconnection request data; detecting a first status identifier, which indicates the connection / disconnection status with the first device; and determining whether the wireless connection / disconnection with the first device is normal based on the first status identifier and the connection / disconnection request data. This technical solution, by detecting the first status identifier indicating the connection / disconnection status with the first device and comprehensively considering the first status identifier and the connection / disconnection request data to determine whether the wireless connection / disconnection with the first device is normal, facilitates effective monitoring of the wireless connection / disconnection status between the wireless connection device and the first device, thereby improving the connection performance between the BMU and the first device.

[0102] Figure 1 A schematic structural block diagram of a vehicle 1 applicable to an embodiment of this application is shown. The vehicle 1 can be a gasoline-powered vehicle, a natural gas-powered vehicle, or a new energy vehicle. New energy vehicles can be pure electric vehicles, hybrid electric vehicles, or range-extended electric vehicles, etc.

[0103] like Figure 1 As shown in this embodiment, 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 serve as the operating power source for the vehicle 1's electrical system, such as meeting the power requirements for starting, navigation, and operation of the vehicle 1. In another embodiment of this application, the battery 10 can not only serve as the operating power source for the vehicle 1, but also as the driving power source for the vehicle 1, replacing or partially replacing fuel or natural gas to provide driving power for the vehicle 1.

[0104] To facilitate monitoring of the operating status of the battery 10 in the vehicle 1, a slave battery management unit (SBMU) 110 is provided in the battery 10. Corresponding to the SBMU 110 inside the battery 10, a master battery management unit (MBMU) 120 is also provided in the vehicle 1.

[0105] Specifically, the battery 10 may include at least one battery cell (or a battery cell) 11, which is encapsulated in the same housing to form a battery pack. In addition to the at least one battery cell 11, the housing may also be equipped with an SBMU 110 and other related components. The SBMU 110 is used to detect the relevant state parameters of each battery cell 11 in the battery 10, such as voltage, current, temperature, state of charge (SOC), state of health (SOH), etc.

[0106] In addition to the battery 10, the vehicle 1 is equipped with an MBMU 120 that can communicate with the SBMU 110. The SBMU 110 can transmit the relevant parameters of the detected battery 10 to the MBMU 120. The MBMU 120 can perform calculations and analysis on the received data and transmit signals to the SBMU 110 to control and manage the SBMU 110.

[0107] In addition to the battery 10 and MBMU, the vehicle 1 is also equipped with a vehicle controller 130, such as a vehicle control unit (VCU) or a domain control unit (DCU). The MBMU 120 can communicate with the SBMU 110 and 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.

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

[0109] It should be noted that the above text Figure 1 As an example only, vehicle 1 may be equipped with a communication system consisting of vehicle controller 130, MBMU 120, and multiple batteries 10. In other embodiments, vehicle 1 may be equipped with a communication system consisting solely of vehicle controller 130 and multiple batteries 10. For example, each of the multiple batteries 10 may have a monitoring unit inside it that monitors individual battery cells 11. This monitoring unit may establish a communication connection with vehicle controller 130, enabling vehicle controller 130 to control and manage the multiple batteries 10.

[0110] Optionally, in addition to the conventional cell-to-pack (CTP) architecture, the battery 10 in this embodiment can also adopt a cell-to-chassis (CTC) architecture, integrating at least one cell of the battery 10 into the vehicle chassis. In this case, the vehicle controller 130 in the vehicle 1 can be a domain controller, directly managing the battery 10 and even at least one cell of the battery 10.

[0111] Figure 2A schematic structural block diagram of a battery swapping station 2 applicable to embodiments of this application is shown. This battery swapping station 2 can provide fast battery swapping services for various types of vehicles, such as passenger cars or heavy trucks, and may also include a charging compartment 20 for charging batteries removed from the vehicle.

[0112] like Figure 2 As shown, the charging compartment 20 of the battery swapping station 2 can accommodate multiple batteries 10, each battery 10 containing an SBMU 110. To facilitate control and management of these multiple SBMUs 110, the charging compartment 20 also includes at least one Charger Battery Manager Unit (CBMU) 210. As an example, each CBMU 210 in the charging compartment 20 can establish a communication connection with a preset number of SBMUs 110 and control and manage those SBMUs 110. When the charging compartment 20 can accommodate a large number of batteries 10, multiple CBMUs 210 can be installed within it, each CBMU 210 communicating with a preset number of SBMUs 110 to ensure effective monitoring and management of each SBMU 110 and its associated battery 10.

[0113] See also Figure 2 In the battery swapping station 2, in addition to the charging compartment 20 for charging multiple batteries 10, a station control system 21 is also provided. This station control system 21 can control multiple functional devices in the battery swapping station 2 to perform corresponding functions. For example, the battery swapping station 2 includes battery loading and unloading equipment (… Figure 2 (Not shown in the image), the station control system 21 can control the battery loading and unloading equipment to remove batteries 10 that are in a depleted state from vehicles entering the battery swapping station 2, and install batteries 10 with sufficient charge in the battery swapping station onto the vehicles.

[0114] Specifically, in this embodiment of the 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 and manage multiple batteries 10 in the charging compartment 20 through the CBMU 210.

[0115] like Figure 2 As shown, in battery swapping station 2, in addition to CBMU 210, a Transmission Battery Manager Unit (TBMU) 220 is also installed. When Figure 1After the vehicle 1 shown enters the battery swapping station 2, the TBMU 220 can establish a communication connection with the MBMU 120 in the vehicle 1, which facilitates information exchange between the TBMU 220 and the MBMU 120, and also facilitates the TBMU 220 to monitor and manage the battery 10 on the vehicle 1 through the MBMU 120.

[0116] Furthermore, to facilitate the station control system 21's monitoring and management of 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.

[0117] Optionally, in the above Figure 1 and Figure 2 In the vehicle 1 and the battery swapping station 2 shown, different types of BMUs can establish communication connections wirelessly to reduce the complexity of connecting and installing different types of BMUs. Additionally, in the battery swapping station 2, to ensure the reliability of communication between the station control system 21 and other components, the station control system can establish communication connections with CBMU 210 and / or TBMU 220 via wired connections.

[0118] Figure 3 A schematic flowchart of a wireless connection method 300 for a battery management device provided in an embodiment of this application is shown.

[0119] like Figure 3 As shown in the embodiments of this application, the wireless connection method 300 includes the following steps.

[0120] S310: Wirelessly connect or disconnect from the first device.

[0121] S320: Detects connection status data between the device and the first device.

[0122] S330: Based on the connection / disconnection status data, determine whether the wireless connection or disconnection with the first device is normal.

[0123] Optionally, in this embodiment, the first device can be any device configured to wirelessly connect and disconnect 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.

[0124] Specifically, as an example, when the battery management device is an MBMU120 in an electrical device (e.g., the vehicle 1 described above) or a main controller (e.g., the vehicle controller 130 in the vehicle 1 described above), the first device includes, but is not limited to, an SBMU 110 in an electrical device (e.g., the vehicle 1 described above).

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

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

[0127] Through these examples of implementation methods, battery management devices can be of various types and applied in different scenarios. This solution enables relatively stable wireless connection and disconnection between TBMU 220 and MBMU 120, and / or between CBMU210 / MBMU 120 and SBMU 110, thereby simplifying the connection methods between various battery management devices in power-consuming and / or battery-swapping equipment, and improving the overall system's connection stability and robustness.

[0128] Optionally, in step S310, the battery management device may be equipped with a wireless connection device, such as a wireless communication chip. This wireless connection device enables wireless connection or disconnection with the first device via a wireless protocol.

[0129] Optionally, in some embodiments, step S310 may include: connecting or disconnecting via Bluetooth with the first device. In this embodiment, the battery management device may be equipped with a Bluetooth chip, which has a Bluetooth communication protocol stack. Through this Bluetooth chip, the Bluetooth connection and disconnection between the battery management device and the first device can be achieved via the Bluetooth communication protocol.

[0130] In this embodiment, the battery management device can establish a Bluetooth connection with the first device via the Bluetooth communication protocol to enable subsequent data communication. This Bluetooth connection method features low power consumption, low latency, and low cost, making it suitable for installation in vehicle 1 and / or battery swapping station 2 to achieve reliable communication over short distances at low cost.

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

[0132] When the wireless connection between the battery management device and the first device is normal, the battery management device can exchange information normally with the first device, ensuring the safe and effective operation of both the battery management device and the first device. Conversely, if the wireless connection between the battery management device and the first device is abnormal, the wireless connection may be lost, hindering normal information exchange between them.

[0133] When the wireless disconnection between the battery management device and the first device is normal, the battery management device's operating resources can be saved, its power consumption reduced, and its overall performance improved. Conversely, when the wireless disconnection between the battery management device and the first device is abnormal, the wireless connection between them may become faulty, wasting the battery management device's operating resources, increasing its power consumption, and affecting its overall performance.

[0134] Through the technical solution of the embodiments of this 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 itself and the first device, and determines whether the wireless connection between itself and the first device is normal based on the connection status data. This is beneficial to achieve 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.

[0135] Figure 4 A schematic structural block diagram of a battery management device 400 provided in an embodiment of this application is shown. Optionally, the battery management device 400 can be as described above. Figure 1 and Figure 2 The MBMU 120, CBMU 210, or TBMU 220 shown above. Figure 3 The wireless connection method 300 shown can be applied to the battery management device 400 shown in the embodiments of this application.

[0136] like Figure 4 As shown, the battery management device 400 includes a wireless connection device 420, which is capable of wirelessly connecting with other wireless devices, such as the wireless connection device 420 being capable of wirelessly connecting with the wireless device in the first device. By way of example and not limitation, the wireless connection device 420 may be a wireless communication chip in the battery management device 400.

[0137] When the battery management device 400 includes a wireless connection device 420, the aforementioned connection / disconnection status data may include a first status identifier, which indicates whether the wireless connection device and the first device are connected or disconnected.

[0138] Optionally, the first status identifier may be used only to indicate whether the wireless connection device 420 and the first device are connected or disconnected. Alternatively, the first status identifier may be further used to indicate other related connection and disconnection status information between the wireless connection device 420 and the first device, such as connection time, number of connections, etc.

[0139] Optionally, in some embodiments, the wireless connection device 420 may include a wireless communication protocol stack. The wireless connection device 420 can invoke the wireless communication protocol stack according to connection / disconnection request data to establish or disconnect a wireless connection with the first device. After the wireless connection device 420 establishes a wireless connection with the first device, the first device can send data packets to the wireless connection device 420. If the wireless connection device 420 receives the data packets sent by the first device within a preset time period, the wireless connection device 420 can set the first status flag to a connected state. Conversely, if the wireless connection device 420 does not receive the data packets sent by the first device within the preset time period, the wireless connection device 420 can set the first status flag to a disconnected state.

[0140] Optionally, the first status identifier can be an identifier that is updated in real time in the wireless connection device 420, that is, the wireless connection device 420 can detect the connection status between itself and the first device in real time in order to detect the first status identifier that is updated in real time.

[0141] The technical solution of this application embodiment provides a device wireless connection device in the battery management device, and uses a first status identifier for indicating whether the wireless connection device and the first device are connected or disconnected as connection status data to determine whether the wireless connection between the battery management device and the first device is normal. This method has high accuracy and is easy to implement through hardware and / or software.

[0142] Optionally, such as Figure 4 As shown, in some embodiments, in addition to the wireless connection device 420, the battery management device 400 may further include a control device 410 interconnected with the wireless connection device 420. The control device 410 is capable of sending commands to the wireless connection device 420 to control the wireless connection device 420 to perform corresponding actions according to the commands. By way of example and not limitation, the control device 410 may be the control chip of the battery management device 400, such as the main control chip in the battery management device 400.

[0143] Figure 5 A schematic flowchart of a wireless connection method 500 for a battery management device 400 according to an embodiment of this application is shown. This wireless connection method 500 can be applied to the above-described... Figure 4The wireless connection device 420 in the battery management device 400 shown in the embodiment of this application, in other words, the execution subject of the wireless connection method 400 is the aforementioned wireless connection device 420.

[0144] like Figure 5 As shown in the embodiments of this application, the wireless connection method 500 includes the following steps.

[0145] S510: Receive connection / disconnection request data.

[0146] S520: Based on the connection / disconnection request data, wirelessly connect or disconnect with the first device.

[0147] S530: Detect a first status identifier, which is used to indicate the connection status with the first device.

[0148] S540: Based on the first status identifier and the connection / disconnection request data, determine whether the wireless connection or disconnection with the first device is normal.

[0149] Specifically, in steps S510 and S520, the wireless connection device 420 can receive connection / disconnection request data sent externally. This connection / disconnection request data may include request data indicating the type of request to connect to or disconnect from the first device, and information data indicating the first device. The information data indicating 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, etc. Further, the wireless connection device 420 can perform wireless connection or disconnection with the first device based on the relevant information in the connection / disconnection request data, thereby realizing the wireless connection or disconnection between the battery management device 400 and the first device.

[0150] Optionally, in some embodiments, the battery management device 400 includes Figure 4 The control device 410 shown is connected to the wireless connection device 420. In this case, for step S510, the wireless connection device 420 can receive connection / disconnection request data sent by the control device 410. This connection / disconnection request data is data processed by the control device 410 after receiving a connection / disconnection request command. The connection / disconnection request command is communication data based on a first communication protocol, and the connection / disconnection request data is communication data based on a second communication protocol. The first and second communication protocols are two different types of communication protocols.

[0151] Specifically, in this embodiment, the control device 410 can 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 via a second communication protocol. In this case, the control device 410 can receive a connection / disconnection request command of a first data type sent by the external device based on the first communication protocol, and convert the first data type connection / disconnection request command into connection / disconnection request data of a second data type based on the second communication protocol, thereby facilitating the smooth transmission of the connection / disconnection request data of the second data type to the wireless connection device 420. By way of example and not limitation, the first communication protocol can be the CAN protocol, and the second communication protocol can be the Serial Peripheral Interface (SPI) protocol.

[0152] In this embodiment, the control device 410 in the battery management device 400 receives a connection / disconnection request command based on a first communication protocol and sends connection / disconnection request data based on a second communication protocol to the wireless connection device 420. The battery management device 400 can communicate with external devices based on the first communication protocol; for example, it can still use existing technologies such as CAN protocol or other protocols. The control device 410 converts the received connection / disconnection request command and can then communicate with the wireless connection device 420 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 is also better, thereby improving the overall communication performance of the battery management device 400.

[0153] Alternatively, in some other embodiments, the connection / disconnection request data received by the wireless connection device 420 may not be sent by the control device 410, but may be sent directly by an external device. The wireless connection device 420 may directly perform connection or disconnection with the first device based on the connection / disconnection request data.

[0154] In step S530, the wireless connection device 420 detects a first status identifier, which can be used to indicate the connection / disconnection status between the wireless connection device 420 and the first device. As described above, optionally, the first status identifier can be used to indicate whether the wireless connection device 420 and the first device are connected or disconnected. Alternatively, the first status identifier can also be further used to indicate other relevant connection / disconnection status information between the wireless connection device 420 and the first device.

[0155] Optionally, in some embodiments, before step S530, the wireless connection method 500 further includes: the wireless connection device 420 determining whether a data packet sent by the first device is received within a preset time period; and the wireless connection device 420 setting a first status identifier according to the determination result; wherein, if a data packet sent by the first device is received within the preset time period, the first status identifier is used to indicate the mutual connection with the first device, and if a data packet sent by the first device is not received within the preset time period, the first status identifier is used to indicate the mutual disconnection with the first device.

[0156] Through the technical solution of this embodiment, the wireless connection device 420 can effectively set a first status flag to indicate the connection status between itself and the first device. Therefore, after setting the first status flag, the wireless connection device 420 detects the first status flag and determines whether the wireless connection between itself and the first device is normal based on the first status flag, which has high reliability.

[0157] In step S540, the wireless connection device 420 can comprehensively determine whether the wireless connection or disconnection with the first device is normal based on the first status identifier and the connection / disconnection 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 status identifier, the technical solution of this embodiment combines the first status identifier and the connection / disconnection request data to determine whether the wireless connection or disconnection with the first device is normal, which can further improve the accuracy of the determination.

[0158] In summary, through the technical solution of the embodiments of this application, the wireless connection device 420 detects a first status identifier used to indicate the connection status with the first device, and judges whether the wireless connection or disconnection with the first device is normal by combining the first status identifier and the connection request data. This is beneficial to realize the effective monitoring of the wireless connection status between the wireless connection device 420 and the first device, thereby improving the connection performance between the battery management device 400 and the first device.

[0159] Figure 6 A schematic flowchart of a wireless connection method 600 for a battery management device 400 according to an embodiment of this application is shown. This wireless connection method 600 is also applicable to the above-described... Figure 4 The wireless connection device 420 in the battery management device 400 shown.

[0160] like Figure 6 As shown in the embodiments of this application, the wireless connection method 600 includes the following steps.

[0161] S610: Receive connection / disconnection request data.

[0162] S620: Based on the connection / disconnection request data, wirelessly connect or disconnect with the first device.

[0163] S630: Detect a first status indicator, which is used to indicate the connection status with the first device.

[0164] S641: Determine whether the connection / disconnection status indicated by the first status identifier is consistent with the connection / disconnection request indicated by the connection / disconnection request data.

[0165] S642: If the connection / disconnection status indicated by the first status identifier is consistent with the connection / disconnection request indicated by the connection / disconnection request data, determine that the wireless connection with the first device is normal.

[0166] S643: If the connection / disconnection status indicated by the first status identifier is inconsistent with the connection / disconnection request indicated by the connection / disconnection request data, determine that the wireless connection with the first device is abnormal.

[0167] Specifically, in the embodiments of this application, the specific technical solutions for steps S610 to S630 can be found above. Figure 5 The relevant descriptions of steps S510 to S530 in the illustrated embodiment are as follows.

[0168] In addition, steps S641 to S643 in the embodiments of this application can be an implementation of step S540 above.

[0169] Specifically, in step S641, the first status identifier can be used to indicate whether the current connection status between the wireless connection device 420 and the first device is mutual connection or mutual disconnection. The connection request data may include request data indicating the request type for connecting or disconnecting the wireless connection device 420 and the first device.

[0170] In step S642, if the connection / disconnection status indicated by the first status identifier matches the connection / disconnection request indicated by the connection / disconnection request data, the wireless connection device 420 can determine that the wireless connection with the first device is normal. For example, if the connection / disconnection status indicated by the first status identifier is mutual connection, and the connection / disconnection request indicated by the connection / disconnection request data is also mutual connection, the wireless connection device 420 can determine that the wireless connection with the first device is normal.

[0171] Correspondingly, in step S643, if 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 420 can determine that the wireless connection with the first device is abnormal. For example, if the connection status indicated by the first status identifier is mutually disconnected, but the connection request data indicates mutually connected, the wireless connection device 420 can determine that the wireless connection with the first device is abnormal.

[0172] In the technical solution of this application embodiment, by determining whether the connection / disconnection status indicated by the first status identifier is consistent with the connection / disconnection request indicated by the connection / disconnection request data, it is possible to accurately determine whether the wireless connection or disconnection between the wireless connection device 420 and the first device is normal. This technical solution is convenient to implement and highly accurate. It can not only accurately and effectively monitor the wireless connection / disconnection between the wireless connection device 420 and the first device, but also be easily implemented in the wireless connection device 420 through hardware and / or software.

[0173] Optionally, in some embodiments, the first status identifier is configured to: use a first value to indicate a connection status with the first device as connected, and use a second value to indicate a disconnected connection status with the first device. The connection request data is configured to: use a first value to indicate a connection request with the first device as connected, and use a second value to indicate a connection request with the first device as disconnected.

[0174] In this implementation, the above Figure 6 Step S641 may include: determining whether the first status identifier is consistent with the connection / disconnection request data. Further, step S642 may include: if the first status identifier and the connection / disconnection request data are consistent, determining that the wireless connection with the first device is normal. Step S643 may include: if the first status identifier and the connection / disconnection request data are inconsistent, determining that the wireless connection with the first device is abnormal.

[0175] As an example, the first and second values ​​can be 0 and 1 respectively, which only require a small amount of storage space to effectively identify different connection / disconnection states and connection / disconnection requests. Of course, in other examples, the first and second values ​​can also be other values, and this application embodiment does not specifically limit them.

[0176] In this implementation, the first status identifier and the connection / disconnection request data each use different values ​​to represent different states and different requests. Therefore, by directly judging whether the first status identifier and the connection / disconnection request data are consistent, it is possible to accurately determine whether the wireless connection or disconnection between the battery management device and the first device is normal. This implementation method is the most convenient and can reduce the storage space required for the first status identifier and the connection / disconnection request data in the wireless connection device 420, thereby improving the processing efficiency of the wireless connection device 420 for the first status identifier and the connection / disconnection request data.

[0177] Figure 7 A schematic flowchart of a wireless connection method 700 for a battery management device 400 according to an embodiment of this application is shown. This wireless connection method 700 is also applicable to the above-described... Figure 4The wireless connection device 420 in the battery management device 400 shown.

[0178] like Figure 7 As shown in the embodiments of this application, the wireless connection method 700 includes the above-described... Figure 6 Based on steps S610 to S643 in the illustrated embodiment, if it is determined that the wireless connection or disconnection with the first device is abnormal, the wireless connection method 700 may further include the following steps.

[0179] S750: Based on the connection / disconnection request data, perform at least one more wireless connection or disconnection with the first device.

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

[0181] Specifically, in this embodiment of the 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 wireless connection or disconnection with the first device at least once more according to the connection request data, so as to repair the abnormal wireless connection with the first device.

[0182] Specifically, after each wireless connection or disconnection with the first device, the wireless connection device 420 can re-detect the first status indicator and determine whether the wireless connection or disconnection with the first device is normal based on the newly detected first status indicator.

[0183] The wireless connection device 420 re-executes the wireless connection or disconnection with the first device at least once, and checks the first status indicator at least once, until it is determined that the wireless connection between the wireless connection device 420 and the first device is normal, that is, the abnormal wireless connection between the wireless connection device 420 and the first device has been repaired, or until the number of executions reaches a preset number, at which point the wireless connection device 420 stops continuing to execute the 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, it may be 5.

[0184] If the number of executions reaches a preset number and the wireless connection device 420 is unable to repair the anomaly, the wireless connection device 420 can send the anomaly information to an external device of the battery management device 400 so that the administrator can pay attention to the anomaly in a timely manner and repair the relevant components.

[0185] Through the technical solution of this application embodiment, 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 the wireless connection between it and the first device returns to a normal state, thereby further improving the connection reliability between the battery management device 400 and the first device. Alternatively, if the wireless connection device 420 repeatedly performs the wireless connection disconnection action with the first device a preset number of times and cannot repair the abnormality, the wireless connection device 420 will no longer continue to repeatedly perform the wireless connection disconnection action with the first device, thus avoiding waste of system resources and optimizing the overall performance of the battery management device 400 to a certain extent.

[0186] Figure 8 A schematic flowchart of a wireless connection method 800 for a battery management device 400 according to an embodiment of this application is shown. This wireless connection method 800 is also applicable to the above-described... Figure 4 The wireless connection device 420 in the battery management device 400 shown.

[0187] like Figure 8 As shown in the embodiments of this application, the wireless connection method 800 may include the following steps.

[0188] S810: Receive connection / disconnection request data.

[0189] S820: Based on the connection / disconnection request data, wirelessly connect or disconnect with the first device.

[0190] S830: Detect a first status indicator, which is used to indicate the connection status with the first device.

[0191] S840: At preset time intervals, based on the first status indicator and connection / disconnection request data, determine whether the wireless connection or disconnection with the first device is normal.

[0192] In this application embodiment, the specific implementation of steps S810 to S830 can be found above. Figure 5 Description of steps S510 to S530.

[0193] Step S840 can be the above text Figure 5 One implementation of step S540.

[0194] Specifically, in step S840, the wireless connection device 420 can determine whether the wireless connection or disconnection with the first device is normal based on the first status identifier and connection / disconnection request data at preset time intervals, so as to realize continuous monitoring of the wireless connection with the first device and ensure the reliability of the long-term wireless connection between the wireless connection device 420 and the first device.

[0195] As an example, the preset time period in this embodiment may be less than or equal to 1ms. In other examples, the preset time period may be adjusted according to the actual situation, and this embodiment does not limit the specific value of the preset time period.

[0196] Figure 9 A schematic flowchart of a wireless connection method 900 for a battery management device 400 according to an embodiment of this application is shown. This wireless connection method 900 is also applicable to the above-described... Figure 4 The battery management device 400 shown includes a wireless connection device 420. Optionally, in this embodiment, the wireless connection device 420 may further include a structure module and / or a non-volatile memory (NVM) module. The structure module may be located in the memory of the wireless connection device 420, facilitating the wireless connection device 420 to read and write data in the structure module. The NVM module may be located outside the wireless connection device 420 and connected to it.

[0197] like Figure 9 As shown in the embodiments of this application, the wireless connection method 900 may include the following steps.

[0198] S910: Receive connection / disconnection request data.

[0199] S920: Write the connection break request data to the structure module and / or NVM module.

[0200] S930: Based on the connection / disconnection request data, wirelessly connect or disconnect with the first device.

[0201] S940: Detect a first status indicator, which is used to indicate the connection status with the first device.

[0202] S950: Write the first state identifier to the structure module and / or the NVM module.

[0203] S960: Based on the first status identifier and connection / disconnection request data, determine whether the wireless connection or disconnection with the first device is normal.

[0204] In this application embodiment, the specific implementation schemes of steps S910, S930, S940, and S960 can be found above. Figure 5 Description of steps S510 to S540.

[0205] In step S920, after receiving the connection failure request data, the wireless connection device 420 can write the connection failure request data into a structure module in memory. This allows for quick reading and writing of the connection failure request data in the structure module during subsequent processes, and enables repair of connection faults based on the connection failure request data, thereby improving the connection reliability between the wireless connection device 420 and the first device. Alternatively, after receiving the connection failure request data, the wireless connection device 420 can also store the connection failure request data in an NVM module. The NVM module is a storage module whose stored data is not lost after power failure. Therefore, storing the connection failure request data in the NVM module prevents the loss of connection failure request data due to external factors such as power failure, ensuring the monitoring performance of the wireless connection device 420 on the connection status with the first device, thereby further improving the connection reliability between the battery management device 400 and the first device.

[0206] Similarly, in step S950, after the wireless connection device 420 detects the first status identifier indicating the connection status with the first device, it can also write the first status identifier into the structure module in memory. This allows for quick reading and writing of the first status identifier in the structure module in subsequent processes, and enables monitoring of the connection status between the wireless connection device 420 and the first device based on the first status identifier, thereby improving the monitoring efficiency of the connection status between the wireless connection device 420 and the first device. Furthermore, after the wireless connection device 420 detects the first status identifier indicating the connection status with the first device, it can also write the first status identifier into the NVM module to prevent the loss of the first status identifier due to external factors such as power failure, ensuring the monitoring performance of the connection status between the wireless connection device 420 and the first device.

[0207] Figure 10 A schematic flowchart of a wireless connection method 1000 for a battery management device 400 according to an embodiment of this application is shown. This wireless connection method 1000 can also be applied to the methods described above. Figure 4 The wireless connection device 420 in the battery management device 400 shown.

[0208] like Figure 10 As shown in the embodiments of this application, the wireless connection method 1000 may include the following steps.

[0209] S1010: Receive connection / disconnection request data.

[0210] S1020: Write the connection interruption request data to the NVM module.

[0211] S1030: Based on the connection / disconnection request data, wirelessly connect or disconnect with the first device.

[0212] S1040: Detect a first status identifier, which is used to indicate the connection status with the first device.

[0213] S1050: Based on the first status identifier and the connection / disconnection request data, determine whether the wireless connection or disconnection with the first device is normal.

[0214] S1060: After the battery management device is powered off and then powered on again, read the connection / disconnection request data from the NVM module.

[0215] S1070: Based on the connection / disconnection request data, reconnect or disconnect wirelessly with the first device.

[0216] In this application embodiment, the specific implementation of steps S1010 to S1050 can be found above. Figure 9 Description of the embodiments.

[0217] In steps S1060 and S1070, after the battery management device 400 is powered off and then powered on again, the wireless connection device 420 can read the connection / disconnection request data stored before the power failure from the NVM module, and re-execute the wireless connection or disconnection with the first device according to the connection / disconnection request data.

[0218] According to the technical solution of this application embodiment, an NVM module can be set in the wireless connection device 420. When the wireless connection device 420 receives connection disconnection request data, it can synchronously store the connection disconnection request data in the NVM module. After the battery management device 400 is powered off and then powered on again, the wireless connection device 420 can read the connection disconnection request data from the NVM module and automatically re-establish the wireless connection with the first device according to the connection disconnection request data, thereby eliminating the impact of the power failure of the battery management device 400 on 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.

[0219] Optionally, in some embodiments, after step S1040, the wireless connection method 1000 may further include: writing a first status identifier into the NVM module. Further, step S1060 may include: reading connection / disconnection request data and the first status identifier from the NVM module after the battery management device is powered off and then powered on again. Step S1070 may include: reconnecting or disconnecting wirelessly with the first device based on the connection / disconnection request data and the first status identifier.

[0220] Optionally, in some embodiments, the wireless connection device 420 can determine whether the connection / disconnection status indicated by the first status identifier is consistent with the connection / disconnection request indicated by the connection / disconnection request data. If the connection / disconnection status indicated by the first status identifier is consistent with the connection / disconnection request indicated by the connection / disconnection request data, the wireless connection or disconnection with the first device is performed according to the connection / disconnection request data.

[0221] According to the technical solution of this application embodiment, after the battery management device 400 is powered off and then powered on again, the wireless connection device 420 can read the first status identifier and connection request data from the NVM module, and automatically re-establish the wireless connection with the first device based on the first status identifier and connection request data. Therefore, this technical solution can automatically eliminate 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, while also improving the reliability of the wireless connection device 420 automatically re-establishing the wireless connection with the first device, thereby further improving the connection performance between the battery management device 400 and the first device.

[0222] Figure 11 A schematic flowchart of a wireless connection method 1100 for a battery management device 400 according to an embodiment of this application is shown. This wireless connection method 1100 can also be applied to the methods described above. Figure 4 The wireless connection device 420 in the battery management device 400 shown.

[0223] like Figure 11 As shown in the embodiments of this application, the wireless connection method 1100 may include the following steps.

[0224] S1110: Receive connection request data.

[0225] S1120: Write the connection request data to the NVM module.

[0226] S1130: Based on the connection request data, wirelessly connect or disconnect with the first device.

[0227] S1140: Detect a first status identifier, which is used to indicate the connection status with the first device.

[0228] S1150: Write the first status identifier to the NVM module.

[0229] S1160: Based on the first status identifier and connection request data, determine whether the wireless connection or disconnection with the first device is normal.

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

[0231] S1181: Determine whether the connection / disconnection status indicated by the first status identifier is connected.

[0232] S1182: If the connection status indicated by the first status identifier is connected, wirelessly reconnect or disconnect with the first device according to the connection request data.

[0233] If the connection status indicated by the first status flag is disconnected, then reconnection with the first device will not be performed.

[0234] Optionally, in this embodiment of the application, step S1110 can be... Figure 10 One implementation of step S1010. When the connection / disconnection request data is used to indicate a wireless connection with the first device, the connection / disconnection request data can also be referred to as connection request data.

[0235] Furthermore, in this application embodiment, the specific implementation of steps S1120 to S1170 can be found above. Figure 10 The relevant description of the embodiment. Optionally, steps S1181 to S1182 can be... Figure 10 One implementation of step S1070.

[0236] Specifically, in steps S1181 and S1182, the first status identifier can be used to indicate whether the current connection status between the wireless connection device 420 and the first device is connected or disconnected. Based on the first status identifier, the wireless connection device 420 can determine whether its connection status with the first device was connected before the battery management device 400 was powered off.

[0237] In step S1182, if the connection status indicated by the first status identifier is "connected," it means that the wireless connection device 420 was connected to the first device before the battery management device 400 was powered off. At this time, the wireless connection device 420 reconnects to the first device based on the connection request data, which improves the reliability of reconnection between the wireless connection device 420 and the first device, restoring the state between the wireless connection device 420 and the first device to what it was before the battery management device 400 was powered off.

[0238] Optionally, in some embodiments, after the wireless connection device 420 reconnects or disconnects wirelessly with the first device according to the connection / disconnection request data, the wireless connection method 1000 or wireless connection method 1100 further includes: detecting the first status indicator again, and determining whether the wireless connection or disconnection with the first device is normal according to the first status indicator and the connection / disconnection request data.

[0239] That is, in this embodiment, the wireless connection device 420 can repeatedly perform the above-described... Figure 10Steps S1040 and S1050 shown above can also be repeated by the wireless connection device 420. Figure 11 Steps S1140 to S1160 shown are used to continuously detect the first status identifier and monitor the wireless connection between the wireless connection device 420 and the first device, thereby further continuously and effectively monitoring 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.

[0240] The above text combined Figures 5 to 11 This document describes the technical solution in which the connection / disconnection status data includes a first status identifier in the embodiments of this application. Optionally, in addition to the first status identifier, the connection / disconnection 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. Based on the first information identifier, it can be determined whether the wireless connection / disconnection between the wireless connection device 420 and its battery management device 400 and the first device is normal.

[0241] In this case, Figure 12 A schematic flowchart of a wireless connection method 1200 for a battery management device 400 according to an embodiment of this application is shown. This wireless connection method 1200 is also applicable to the above-described... Figure 4 The wireless connection device 420 in the battery management device 400 shown.

[0242] like Figure 12 As shown in the embodiments of this application, the wireless connection method 1200 may include the following steps.

[0243] S1210: Receive connection / disconnection request data.

[0244] S1220: Based on the connection / disconnection request data, wirelessly connect or disconnect with the first device.

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

[0246] S1240: Based on the first information identifier, determine whether the wireless connection or disconnection with the first device is normal.

[0247] Specifically, in the embodiments of this application, the specific implementation schemes for steps S1210 to S1220 can be found above. Figure 5 The relevant descriptions of steps S510 and S520 in the illustrated embodiment are as follows.

[0248] In step S1230, the wireless connection device 420 detects a first information identifier, which indicates the status of wireless connection or disconnection between the wireless connection device 420 and the first device. Optionally, the first information identifier can be used to indicate whether the connection or disconnection between the wireless connection device 420 and the first device is complete. Alternatively, the first information identifier can be further used to indicate other related connection / disconnection information between the wireless connection device 420 and the first device.

[0249] Optionally, in some embodiments, the wireless connection device 420 may include a wireless communication protocol stack. The wireless connection device 420 can invoke the wireless communication protocol stack according to connection / disconnection request data to perform wireless connection or disconnection with the first device. The wireless connection device 420 may be equipped with a first information identifier to indicate the execution status of the wireless communication protocol stack for wireless connection or disconnection with the first device.

[0250] Since the wireless connection device 420's wireless connection or disconnection with the first device affects the actual state of subsequent wireless connection or disconnection between the wireless connection device 420 and the first device, in step S1240, the wireless connection device 420 can determine whether the wireless connection or disconnection with the first device is normal based on the aforementioned first information identifier, which is beneficial to effectively monitor the wireless connection status between the wireless connection device 420 and the first device.

[0251] In summary, through the technical solution of the embodiments of this application, the wireless connection device 420 detects a first information identifier used to indicate the execution status of wireless connection or disconnection with the first device, and determines whether the wireless connection or disconnection with the first device is normal based on the first information identifier. This is beneficial to enable the wireless connection device 420 to 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.

[0252] Figure 13 A schematic flowchart of a wireless connection method 1300 for a battery management device 400 according to an embodiment of this application is shown. This wireless connection method 1300 is also applicable to the above-described... Figure 4 The wireless connection device 420 in the battery management device 400 shown.

[0253] like Figure 13 As shown in the embodiments of this application, the wireless connection method 1300 includes the following steps.

[0254] S1310: Receive connection / disconnection request data.

[0255] S1320: Based on the connection / disconnection request data, wirelessly connect or disconnect with the first device.

[0256] S1330: Detect the first information identifier.

[0257] S1341: Based on the first information identifier, determine whether the execution of wirelessly connecting or disconnecting from the first device has been completed.

[0258] S1342: If the wireless connection or disconnection with the first device is completed, determine that the wireless connection or disconnection with the first device is normal.

[0259] S1343: If the wireless connection or disconnection with the first device has not been completed, determine that the wireless connection or disconnection with the first device is abnormal.

[0260] Specifically, in the embodiments of this application, the specific technical solutions for steps S1310 to S1330 can be found above. Figure 12 The relevant descriptions of steps S1210 to S1230 in the illustrated embodiment.

[0261] In addition, steps S1341 to S1343 in the embodiments of this application can be an implementation of step S1240 above.

[0262] Specifically, in step S1341, the first information identifier can be used to indicate whether the wireless connection device 420 has completed the current wireless connection or disconnection process with the first device. In step S1342, if the first information identifier indicates that the wireless connection device 420 has completed the wireless connection or disconnection process with the first device, the wireless connection device 420 can determine that the wireless connection or disconnection with the first device is normal. Correspondingly, in step S1343, if the first information identifier indicates that the wireless connection device 420 has not completed the wireless connection or disconnection process with the first device, the wireless connection device 420 can determine that the wireless connection or disconnection with the first device is abnormal.

[0263] In the technical solution of this application embodiment, by using the first information identifier to determine whether the wireless connection or disconnection with the first device has been completed, it can assist in determining whether the wireless connection or disconnection between the wireless connection device 420 and the first device is normal. This technical solution can improve the connection performance between the wireless connection device 420 and the first device, while being relatively easy to implement in the wireless connection device 420 through hardware and / or software.

[0264] Optionally, in some embodiments, the first information identifier can be configured to: indicate the completion of execution by wirelessly connecting or disconnecting from the first device using a first value, and indicate the incomplete execution by wirelessly connecting or disconnecting from the first device using a second value.

[0265] As an example, the first and second values ​​can be 0 and 1 respectively, which only require a small amount of storage space to effectively identify different execution states. Of course, in other examples, the first and second values ​​can also be other values, and this application embodiment does not specifically limit them.

[0266] Alternatively, in some other embodiments, whether the first information identifier is updated is used to indicate whether the execution of wirelessly connecting or disconnecting from the first device is complete. In this embodiment, step S1341 may include: determining whether the first information identifier is updated to determine whether the execution of wirelessly connecting or disconnecting from the first device is complete. Specifically, if the first information identifier is updated, it is determined that the execution of wirelessly connecting or disconnecting from the first device is complete; conversely, if the first information identifier is not updated, it is determined that the execution of wirelessly connecting or disconnecting from the first device is not complete.

[0267] The technical solution of this embodiment can be used to determine whether the wireless connection or disconnection with the first device has been completed by updating the first information identifier. The determination process is very convenient and relatively simple to implement, which can improve the monitoring efficiency of the wireless connection device 420 on the wireless connection status with the first device.

[0268] Figure 14 A schematic flowchart of a wireless connection method 1400 for a battery management device 400 according to an embodiment of this application is shown. This wireless connection method 1400 is also applicable to the above-described... Figure 4 The wireless connection device 420 in the battery management device 400 shown.

[0269] like Figure 14 As shown in the embodiments of this application, the wireless connection method 1400 includes the above-described... Figure 13 Based on steps S1310 to S1343 in the illustrated embodiment, if it is determined that the wireless connection or disconnection with the first device is abnormal, the wireless connection method 1400 may further include the following steps.

[0270] S1450: Based on the connection / disconnection request data, perform at least one more wireless connection or disconnection with the first device.

[0271] S1460: Detect the first information identifier at least once more until the first information identifier indicates that the wireless connection with the first device has been completed or disconnection has been achieved.

[0272] Specifically, in this embodiment of the 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 wireless connection or disconnection with the first device at least once more according to the connection request data, so as to repair the abnormal wireless connection with the first device.

[0273] Specifically, after each wireless connection or disconnection with the first device, the wireless connection device 420 can re-detect the first information identifier and determine whether the wireless connection or disconnection with the first device is normal based on the newly detected first information identifier.

[0274] The wireless connection device 420 re-executes the 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 abnormal wireless connection between the wireless connection device 420 and the first device is repaired.

[0275] Through the technical solution of this application embodiment, 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 the wireless connection between it and the first device is restored to normal, thereby further improving the connection reliability between the battery management device 400 and the first device.

[0276] Figure 15 A schematic flowchart of a wireless connection method 1500 for a battery management device 400 according to an embodiment of this application is shown. This wireless connection method 1500 is also applicable to the above-described... Figure 4 The wireless connection device 420 in the battery management device 400 shown.

[0277] like Figure 15 As shown in the embodiments of this application, the wireless connection method 1500 may include the following steps.

[0278] S1510: Receive connection / disconnection request data.

[0279] S1520: Based on the connection / disconnection request data, wirelessly connect or disconnect with the first device.

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

[0281] S1540: At preset time intervals, determine whether the wireless connection or disconnection with the first device is normal based on the first information identifier.

[0282] In this application embodiment, the specific implementation of steps S1510 to S1530 can be found above. Figure 12 Description of steps S1210 to S1230.

[0283] Step S1540 can be the above text Figure 12 One implementation of step S1240.

[0284] Specifically, in step S1540, the wireless connection device 420 can determine whether the wireless connection or disconnection with the first device is normal based on the first information identifier at preset time intervals, so as to realize continuous monitoring of the wireless connection with the first device and ensure the reliability of the long-term wireless connection between the wireless connection device 420 and the first device.

[0285] As an example, the preset time period in this embodiment may be less than or equal to 1ms. In other examples, the preset time period may be adjusted according to the actual situation, and this embodiment does not limit the specific value of the preset time period.

[0286] Figure 16 A schematic flowchart of a wireless connection method 1600 for a battery management device 400 according to an embodiment of this application is shown. This wireless connection method 1600 is also applicable to the above-described... Figure 4 The battery management device 400 shown includes a wireless connection device 420. Optionally, in this embodiment, the wireless connection device 420 may include a state machine module and a wireless communication protocol stack module, which can be software modules within the wireless connection device 420. 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, which can also be a software module within the wireless connection device 420.

[0287] like Figure 16 As shown in the embodiments of this application, the wireless connection method 1600 may include the following steps.

[0288] S1610: The main control module receives connection / disconnection request data and calls the state machine module.

[0289] S1621: The state machine module calls the wireless communication protocol stack module based on the connection / disconnection request data.

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

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

[0292] 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.

[0293] In this embodiment of the application, step S1610 can be as described above. Figure 12One implementation of step S1210. Steps S1621 to S1622 can be as described above. Figure 12 One implementation of step S1220. Step S1630 can be implemented as described above. Figure 12 One implementation of step S1230. Step S1640 can be implemented as described above. Figure 12 One implementation of step S1240.

[0294] Specifically, in the wireless connection device 420 of this application embodiment, multiple software modules can be stored internally. These 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 / disconnection request data sent by an external device. Based on the connection / disconnection request data, the main control module can call the state machine module to start executing the connection / disconnection action.

[0295] In steps S1621 and S1622, the state machine module invokes the wireless communication protocol stack module based on the connection / disconnection request data. This wireless communication protocol stack module then specifically executes the wireless connection or disconnection with the first device. Furthermore, after the wireless communication protocol stack module executes the wireless connection or disconnection with the first device, it can generate or update a first information identifier based on its own execution status. Therefore, in this embodiment, the first information identifier is used to indicate the execution status of the wireless communication protocol stack module's wireless connection or disconnection with the first device.

[0296] 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 periodically or irregularly call the state machine module, so that the state machine module can periodically or irregularly determine whether the wireless connection or disconnection between the wireless connection device and the first device is normal based on the first information identifier.

[0297] According to the technical solution of this application embodiment, the wireless connection device 420 may include multiple software modules, wherein different software modules are used to perform different functions and can cooperate with each other. The wireless communication protocol stack module is used to specifically implement the execution of 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. The first information identifier can accurately reflect the execution status of wireless connection device 420 wirelessly connecting or disconnecting with the first device.

[0298] Figure 17 A schematic flowchart of a wireless connection method 1700 for a battery management device 400 according to an embodiment of this application is shown. This wireless connection method 1700 is also applicable to the above-described... Figure 4 The wireless connection device 420 in the battery management device 400 shown.

[0299] like Figure 17 As shown in the embodiments of this application, the wireless connection method 1700 may include the following steps.

[0300] S1710: Receive connection / disconnection request data.

[0301] S1720: Connect wirelessly to the first device based on the connection / disconnection request data.

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

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

[0304] In this application embodiment, the specific implementation of steps S1710 to S1720 can be found above. Figure 12 The relevant descriptions of steps S1210 and S1220 in the illustrated embodiment.

[0305] In addition, in this embodiment of the application, after step S1720, that is, after the wireless connection device 420 wirelessly connects to the first device according to the connection / disconnection request data, the wireless connection device 420 executes step S1730, that is, the wireless connection device 420 performs master-slave authentication with the first device to determine whether the wireless connection device 420 and the first device can be mutually adapted, thereby ensuring normal data transmission between the wireless connection device 420 and the first device and improving system robustness.

[0306] Optionally, such as Figure 17 As shown, in some embodiments, step S1730 may include the following steps.

[0307] S1731: Receive a first message and a first random number sent by the first device, wherein the first message is used to indicate master-slave authentication of the first device.

[0308] S1732: Execute the algorithm to process the first random number to obtain the first target number.

[0309] S1733: Send a second message matching the first message and a first target number to the first device, so that the first device can identify the second message and perform an algorithm check on the first target number to determine the master-slave authentication result.

[0310] Specifically, in step S1731, the wireless connection device 420 receives a first message and a first random number sent by the first device. The wireless connection device 420 can identify the first message and determine to start master-slave authentication with the first device based on the first message.

[0311] In step S1732, the wireless connection device 420 can use a specific algorithm to process the first random number to obtain the first target number. This specific algorithm can be an algorithm pre-agreed upon by the wireless connection device 420 and the first device; however, this embodiment does not specifically limit the type of this specific algorithm.

[0312] In step S1733, the wireless connection device 420 sends a second message matching the first message and a first target number to the first device. The second message is used to instruct the wireless connection device 420 on master-slave authentication. The first device receives and identifies the second message and determines to start master-slave authentication with the wireless connection device 420 based on the first message.

[0313] 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 be matched with 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 be a decryption algorithm that matches the encryption algorithm.

[0314] In some implementations, if the first device can recover the first random number after processing the first target number using a specific algorithm, then the master-slave authentication between the first device and the wireless connection device 420 is considered successful, indicating that the first device and the wireless connection device 420 are compatible. The first device will then begin sending data to the wireless connection device 420 via wireless communication, and a normal wireless connection will be established between the two devices. Conversely, if the first device cannot recover the first random number after processing the first target number using the specific algorithm, then the master-slave authentication between the first device and the wireless connection device 420 is considered failed, indicating that the first device and the wireless connection device 420 are not compatible. The first device will not send data to the wireless connection device 420, and the wireless connection between the two devices will be disconnected.

[0315] Through the technical solution of this application embodiment, the wireless connection device 420 and the first device realize the master-slave authentication process through the interaction of messages and data, which can have high accuracy and is also convenient for the software and / or hardware inside the wireless connection device 420 and the first device to implement the master-slave authentication process.

[0316] In some implementations, the first and second messages are Controller Area Network (CAN) messages. In this implementation, the wireless connection device 420 and the first device use CAN messages to indicate master-slave authentication. On the one hand, this can be adapted to the technical solution of using CAN messages for master-slave authentication between the battery management device 400 and the first device in related technologies. On the other hand, it also facilitates the subsequent parsing of the CAN message to locate the master-slave authentication interaction between the wireless connection device 420 and the first device.

[0317] Optionally, in this embodiment, the wireless connection device 420 may further include an NVM module. See also... Figure 17 Optionally, in this embodiment of the 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, if the master-slave authentication with the first device is successful, the authentication information of the first device is stored in the NVM module, wherein the authentication information of the first device is used to indicate that the master-slave authentication between the first device and the wireless connection device 420 is successful.

[0318] Through the technical solution of this application embodiment, even if the wireless connection device 420 loses power, the storage of the authentication information of the first device in the NVM module will not be affected. After the wireless connection device 420 loses power and restarts, based on the authentication information of the first device in the NVM module, when the wireless connection device 420 subsequently establishes a wireless connection with the first device, it can directly conduct data communication without having to re-authenticate with the first device as master and slave, thereby saving system resources and improving the wireless connection performance between the wireless connection device 420 and the first device.

[0319] Optionally, in this embodiment, after the wireless connection device 420 executes step S1730, the wireless connection device 420 is further configured to detect a first status identifier and / or a first information identifier with the first device, and determine whether the wireless connection or disconnection with the first device is normal based on the first status identifier and / or the first information identifier. Specific solutions can be found in the relevant descriptions of the embodiments above, and will not be elaborated upon here.

[0320] Figure 18 A schematic flowchart of a wireless connection method 1800 for a battery management device 400 according to an embodiment of this application is shown. This wireless connection method 1800 can also be applied to the methods described above. Figure 4 The wireless connection device 420 in the battery management device 400 shown may optionally 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 master control chip, or it may also be referred to as a main chip.

[0321] like Figure 18 As shown in the embodiments of this application, the wireless connection method 1800 may include the following steps.

[0322] S1810: After receiving the connection / disconnection request data, copy the specific data to a specific array.

[0323] S1820: Call the disconnect command processing function to copy to the specific ECU table and NVM, and switch the master state machine to process disconnect commands.

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

[0325] S1840: Determine whether the Bluetooth protocol stack connection / disconnection action has been completed.

[0326] S1851: Update specific flags after the Bluetooth protocol stack disconnection action is completed.

[0327] S1852: Do not update specific flags if the Bluetooth protocol stack disconnection action is not completed.

[0328] S1860: Master-slave authentication.

[0329] S1870: Determine whether authentication was successful.

[0330] S1880: Normal data interaction.

[0331] S1890: 1ms scheduling master state machine.

[0332] S18100: Detects Bluetooth connection status and specific flags.

[0333] S18110: Determine whether a specific flag has been updated and check whether the connection status is consistent with the connection request.

[0334] S18120: Reconnect to the device to be connected if a specific flag is not updated and / or the connection status is inconsistent with the connection request.

[0335] S18130: Initialize NVM after power-on.

[0336] S18140: Check if the connection status is "connected".

[0337] 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.

[0338] Specifically, for step S1810, the connection disconnection request data can be data sent from the main chip in the battery management device 400 to the Bluetooth chip via a communication bus (e.g., SPI bus). After receiving the connection disconnection request data, the Bluetooth chip copies it to a specific array so that subsequent connection disconnection command processing functions can access the connection disconnection request data in the array.

[0339] In step S1820, the Bluetooth chip includes a main program and a main state machine program. The main program can call a connection / disconnection command processing function, which can copy the connection / disconnection request data from the aforementioned specific array to a specific Electronic Control Unit (ECU) table and NVM, and switch the main state machine to process the connection / disconnection request data. The ECU table is a structure in the Bluetooth chip's memory, and the NVM is a non-volatile memory within the Bluetooth chip.

[0340] In step S1830, the Bluetooth chip also includes a Bluetooth protocol stack. The main state machine determines the content of the connection / disconnection request data. If it is a connection command, it calls the connection interface of the Bluetooth protocol stack and inputs the content of the connection / disconnection request data into the connection interface. If it is a disconnection command, it calls the disconnection interface of the Bluetooth protocol stack and inputs the content of the connection / disconnection request data into the disconnection interface. Through this interface call of the Bluetooth protocol stack by the main state machine, the Bluetooth chip can achieve Bluetooth connection / disconnection with the device to be connected (e.g., the first device mentioned above).

[0341] In step S1840, it can be determined whether the Bluetooth connection / disconnection action of the Bluetooth protocol stack is complete, and a specific flag bit (e.g., the first information identifier mentioned above) can be set in the Bluetooth chip to indicate whether the Bluetooth connection / disconnection action of the Bluetooth protocol stack is complete. By default, this specific flag bit is not updated and can be a default value.

[0342] For steps S1851 and S1852, if the Bluetooth connection / disconnection action in the Bluetooth protocol stack is not completed, the specific flag bit in the Bluetooth chip will not be updated and will remain at its default value. Conversely, if the Bluetooth connection / disconnection action in the Bluetooth protocol stack is completed, the specific flag bit in the Bluetooth chip will be updated, changing from the default value to another target value.

[0343] After the main state machine calls the Bluetooth protocol stack to complete the connection and disconnection with the device to be connected, the Bluetooth chip and the device to be connected can establish a Bluetooth connection or disconnection. After the Bluetooth chip and the device to be connected are connected, the device to be connected and the Bluetooth chip can send data packets (or, in other words, heartbeat packets) to each other.

[0344] If the Bluetooth chip receives the data packet normally, the flag bit recorded in the ECU table of the Bluetooth chip to indicate the Bluetooth connection status (e.g., the first status flag mentioned above) is written to the first value (e.g., 1), indicating that the Bluetooth is in the connected state.

[0345] When the signal is unstable, if the data packets received by the Bluetooth chip are not updated after a preset time period (e.g., 2 seconds), the Bluetooth protocol stack will process the disconnection. At this time, the flag bit in the ECU table of the Bluetooth chip, which is used to indicate the Bluetooth connection status, is set to the second value (e.g., 0), indicating that Bluetooth is in a disconnected state.

[0346] Optionally, the flags in the ECU table can be updated in real time to indicate the connection status between the Bluetooth chip and the device to be connected.

[0347] For step S1860, master-slave authentication can be understood as a handshake process between the Bluetooth chip and the device to be connected. The battery management device containing the Bluetooth chip can be understood as the master device, and the device to be connected as the slave device. Specifically, during master-slave authentication, after the Bluetooth chip and the device to be connected connect, they enable data transmission and reception, allowing only limited-length data exchanges. 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 using a specific algorithm to obtain the target number B. Then, the Bluetooth chip sends another message frame and the target number B to the device to be connected. After receiving the target number B, the device to be connected performs an algorithm check. If there are no issues, normal data exchange is allowed. The above master-slave authentication process needs to be completed within a predetermined time period (e.g., 500ms). If the device to be connected does not receive any data during the exchange and the timeout occurs, the device to be connected will actively disconnect from the Bluetooth chip.

[0348] For steps S1870 and S1880, it is determined whether authentication was successful. If successful, the Bluetooth chip and the device to be connected are considered to be compatible, and they can subsequently exchange data normally. For example, if the device to be connected is the SMBU in a vehicle, and the battery management device containing the Bluetooth chip is the MBMU, the SMBU 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, and the device to be connected will actively disconnect from the Bluetooth chip and will not send data to the Bluetooth chip.

[0349] In addition, after successful master-slave authentication, the relevant information of the device to be connected can be written into the NVM of the Bluetooth chip. When the Bluetooth chip connects to the device to be connected in the future, master-slave authentication will no longer be required, thus saving system resources.

[0350] 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, to detect the current Bluetooth connection / disconnection status and specific flag bits, and to determine whether the specific flag bits are updated and whether the Bluetooth connection / disconnection status is consistent with the connection / disconnection request, thereby determining whether the current Bluetooth connection / disconnection is normal.

[0351] Specifically, the master state machine can check the flag bits in the ECU table that indicate the Bluetooth connection / disconnection status to determine if the current Bluetooth connection / disconnection status matches the connection / disconnection request. Additionally, the master state machine can also determine if a specific flag bit has been updated. If the Bluetooth connection / disconnection status matches the connection / disconnection request and the specific flag bit has been updated, then the current Bluetooth connection / disconnection status is considered normal.

[0352] If the Bluetooth connection status is inconsistent with the connection request and / or a specific flag is not updated, it indicates that the current Bluetooth connection status is abnormal. The main program of the Bluetooth chip needs to execute step S18120 to reconnect the Bluetooth chip to the device to be connected in order to repair the abnormality.

[0353] Specifically, if the Bluetooth connection status and the connection request are inconsistent, the Bluetooth chip's main program can read the connection request command data from the ECU table and re-execute steps S1820 to S1830 to reconnect via Bluetooth. This reconnection can be performed up to five times to prevent excessive reconnections and wasted system resources.

[0354] If a specific flag is not updated, the Bluetooth chip's main program calls the Bluetooth protocol stack again, causing the Bluetooth protocol stack to re-execute the connection / disconnection action. Then, the specific flag will be updated again. In this case, steps S18100 to S18120 can be repeated, that is, repeatedly checking whether the specific flag has been updated, and repeatedly performing connection / disconnection with the device to be connected if the specific flag has not been updated, until the specific flag is successfully updated.

[0355] In step S18130, after the battery management device 400 loses power and is powered on again, the Bluetooth chip can initialize its internal NVM to facilitate subsequent reading and writing of data in the NVM.

[0356] In step S18140, the Bluetooth chip reads its connection status with the device to be connected from the NVM and then checks whether the connection status is "connected". It is understood that in this embodiment, before the Bluetooth chip is powered on again, it can detect its connection status with the device to be connected and write this status into the NVM. Therefore, after the battery management device 400 loses power and is powered on again, the Bluetooth chip can read the connection status of the device to be connected from the NVM before the power loss.

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

[0358] When the Bluetooth chip determines that the connection status between the Bluetooth chip and the device to be connected is "connected", the Bluetooth chip reads the connection request data corresponding to the device to be connected from the NVM, calls the connection command processing function, copies the connection request data to the specific ECU table and the NVM again, and switches the main state machine to process the connection request data to achieve reconnection with the device to be connected.

[0359] It is understandable that after step S18150, the Bluetooth chip can continue to execute steps S1890 to S18130 to continuously monitor whether a connection failure occurs between the Bluetooth chip and the device to be connected.

[0360] The above text combined Figures 5 to 18 This document describes wireless connection methods 500 to 1700, in embodiments of this application, where the wireless connection device 420 in the battery management device 400 acts as the execution subject. The following is a detailed description in conjunction with... Figures 19 to 26 This describes a wireless connection method in this embodiment of the application, in which the control device 410 in the battery management device 400 acts as the execution subject.

[0361] Figure 19 A schematic flowchart of a wireless connection method 1900 for a battery management device 400 according to an embodiment of this application is shown. This wireless connection method 1900 is applied to the above... Figure 4 The control device 410 in the battery management device 400 shown, in other words, the execution subject of the wireless connection method 1900 in this application embodiment is the aforementioned control device 410.

[0362] like Figure 19 As shown in the embodiments of this application, the wireless connection method 1900 includes the following steps.

[0363] S1910: Obtain a connection / disconnection request command, which indicates whether the wireless connection between the battery management device and the first device is disconnected.

[0364] S1920: Based on the connection / disconnection request command, control the wireless connection device to wirelessly connect or disconnect from the first device.

[0365] S1930: First status indicator for detecting wireless connection devices.

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

[0367] Specifically, in steps S1910 and S1920, the control device 410 receives a connection / disconnection request command instructing the battery management device 400 to wirelessly connect or disconnect from the first device. Based on this connection / disconnection request command, the control device 410 controls the wireless connection device 420 to wirelessly connect or disconnect from the first device, thereby achieving wireless connection or disconnection between the battery management device 400 and the first device.

[0368] Optionally, in some embodiments, the control device 410 in the battery management device 400 can receive a connection / disconnection request command from an external device of the battery management device 400 to control the wireless connection or disconnection between the wireless connection device 420 and the first device.

[0369] For example, when the battery management device 400 is a TBMU 220 and the first device is an MBMU 120, when the vehicle 1 is outside the battery swapping station 2, the TBMU 220 receives a first connection / disconnection request command sent by the station control system 21. The TBMU 220 can wirelessly connect or disconnect with the MBMU 120 in the vehicle 1 based on the first connection / disconnection request command.

[0370] For example, when the battery management device 400 is MBMU 120 and the first device is SBMU 110, after the vehicle 1 enters the battery swapping station 2, TBMU 220 receives the second connection / disconnection request command sent by the station control system 21, and then sends the second connection / disconnection request command to MBMU 120 in vehicle 1. MBMU 120 can then wirelessly connect or disconnect with SBMU 110 in battery 10 based on the second connection / disconnection request command.

[0371] For example, when the battery management device 400 is a CBMU 210 and the first device is an SBMU 110, in the battery swapping station 2, the CBMU 210 in the battery swapping compartment 20 receives a third connection / disconnection request command sent by the station control system 21. The CBMU 210 can wirelessly connect or disconnect with the SBMU 110 in the battery 10 based on the third connection / disconnection request command.

[0372] Alternatively, in other embodiments, the control device 410 in the battery management device 400 may also generate the disconnection request command based on the relevant information it has obtained, or the control device 410 may also obtain the disconnection request command from other devices in the battery management device 400. The specific method by which the control device 410 obtains the disconnection request command is not limited in the embodiments of this application.

[0373] In steps S1930 and S1940, after the control device 410 controls the wireless connection device 420 to wirelessly connect or disconnect from the first device according to the connection / disconnection request command, the control device 410 can further detect a first status identifier of the wireless connection device 420, such as the first status identifier and / or first information identifier described in the above embodiment. This first status identifier can be used to characterize the wireless connection / disconnection 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 based on the first status identifier, thereby further determining whether the wireless connection or disconnection between the battery management device 400 and the first device is normal.

[0374] The technical solution of this application embodiment does not require modification to the existing hardware of the battery management device 400. By adding a wireless connection device 420 to the battery management device 400 and controlling the wireless connection device 420 through the control device 410, a wireless connection between the battery management device 400 and the first device can be achieved. This wireless connection method is relatively simple to implement and compatible with existing products. Furthermore, the control device 410 of the battery management device 400 can detect the first status indicator 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 indicator. This facilitates 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.

[0375] Figure 20 A schematic flowchart of a wireless connection method 2000 for a battery management device 400 according to an embodiment of this application is shown. This wireless connection method 2000 can also be applied to the methods described above. Figure 4 The control device 410 in the battery management device 400 shown.

[0376] like Figure 20 As shown in the embodiments of this application, the wireless connection method 2000 includes the following steps.

[0377] S2010: Obtain a connection / disconnection request command, which indicates whether the wireless connection between the battery management device and the first device is disconnected.

[0378] S2021: Convert the connection / disconnection request command based on the first communication protocol into connection / disconnection request data based on the second communication protocol.

[0379] S2022: Send the connection / disconnection request data to the wireless connection device so that the wireless connection device can wirelessly connect or disconnect from the first device according to the connection / disconnection request data.

[0380] S2030: First status indicator for detecting wireless connected devices.

[0381] S2040: Based on the first status identifier and connection / disconnection request data, determine whether the wireless connection or disconnection between the wireless connection device and the first device is normal.

[0382] In this application embodiment, the specific implementation of steps S2010 and S2030 can be found above. Figure 19 Description of steps S1910 and S1930.

[0383] Steps S2021 and S2022 can be described above. Figure 19 One implementation of step S1920. Step S2040 can be described above. Figure 19 One implementation of step S1940.

[0384] Specifically, in steps S2021 and S2022, the control device 410 can connect to an external device of the battery management device 400 based on a first communication protocol and to the wireless connection device 420 via a second communication protocol. The first and second communication protocols are of different types. In this case, the control device 410 can receive a connection / disconnection request command of a first data type sent by the external device based on the first communication protocol, and convert this first data type connection / disconnection request command into connection / disconnection request data of a second data type based on the second communication protocol, thereby facilitating the smooth transmission of the second data type connection / disconnection request data to the wireless connection device 420.

[0385] Through this embodiment, the control device 410 can receive a connection / disconnection request command based on a first communication protocol and send connection / disconnection request data based on a second communication protocol to the wireless connection device 420. The control device 410 can communicate with external devices based on the first communication protocol, while 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.

[0386] Specifically, in order for the wireless connection device 420 to wirelessly connect to or disconnect from the first device based on the connection / disconnection request data, the connection / disconnection request data may include: request data indicating the type of request for connecting to or disconnecting from the first device and information data indicating the first device. The information data indicating 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, etc.

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

[0388] In this example, the control device 410 in the battery management device 400 can be connected to an external device via a CAN bus and receive connection / disconnection request commands via the CAN protocol. Therefore, the control device 410 and the battery management device 400 are well compatible with existing battery management systems. Furthermore, the control device 410 is connected to the wireless connection device 420 via a high-speed, easy-to-operate SPI bus and sends connection / disconnection request data to the wireless connection device 420 via the SPI protocol, thereby improving the communication performance between the control device 410 and the wireless connection device 420.

[0389] See also Figure 20 As shown, optionally, in step S2040, the control device 410 can determine whether the wireless connection or disconnection between the wireless connection device 420 and the first device is normal based on the detected first status identifier of the wireless connection device 420 and the connection / disconnection request data converted according to the connection / disconnection request command.

[0390] Specifically, in this embodiment, the first status identifier can be used to indicate the connection / disconnection status between the wireless connection device 420 and the first device, and the connection / disconnection request data can be used to indicate the connection / disconnection request between the wireless connection device 420 and the first device. Based on the first status identifier and the connection / disconnection 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 or disconnection between the battery management device 400 where the wireless connection device 420 is located and the first device is normal.

[0391] Compared to a technical solution that relies solely on the first status identifier of the wireless connection device 420 to determine whether the wireless connection or disconnection between the battery management device 400 and the first device is normal, the technical solution of this embodiment combines both the first status identifier and connection / disconnection request data to determine whether the wireless connection or disconnection between the wireless connection device 420 and its associated battery management device 400 and the first device is normal, thereby further improving the accuracy of the determination. Therefore, the technical solution of this embodiment can more effectively monitor the wireless connection / disconnection 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.

[0392] Figure 21 A schematic flowchart of a wireless connection method 2100 for a battery management device 400 according to an embodiment of this application is shown. This wireless connection method 2100 can also be applied to the methods described above. Figure 4 The control device 410 in the battery management device 400 shown.

[0393] like Figure 21 As shown in the embodiments of this application, the wireless connection method 2100 includes the following steps.

[0394] S2110: Obtain a connection / disconnection request command, which indicates whether the wireless connection between the battery management device and the first device is disconnected.

[0395] S2121: Convert the connection / disconnection request command based on the first communication protocol into connection / disconnection request data based on the second communication protocol.

[0396] S2122: Send connection / disconnection request data to the wireless connection device so that the wireless connection device can wirelessly connect or disconnect from the first device according to the connection / disconnection request data.

[0397] S2130: First status indicator for detecting wireless connection devices.

[0398] S2141: Determine whether the connection / disconnection status indicated by the first status identifier is consistent with the connection / disconnection request indicated by the connection / disconnection request data.

[0399] S2142: If the connection / disconnection status indicated by the first status identifier is consistent with the connection / disconnection request indicated by the connection / disconnection request data, it is determined that the wireless connection or disconnection between the wireless connection device and the first device is normal.

[0400] S2143: If the connection / disconnection status indicated by the first status identifier is inconsistent with the connection / disconnection request indicated by the connection / disconnection request data, determine that the wireless connection or disconnection between the wireless connection device and the first device is abnormal.

[0401] Specifically, in the embodiments of this application, the specific technical solutions for steps S2110 to S2130 can be found above. Figure 20 The relevant descriptions of steps S2010 to S2030 in the illustrated embodiment.

[0402] In addition, steps S2141 to S2143 in the embodiments of this application can be an implementation of step S2040 above.

[0403] Specifically, in step S2141, the first status identifier can be used to indicate the connection / disconnection status between the wireless connection device 420 and the first device, that is, to indicate whether the connection / disconnection status between the wireless connection device 420 and the first device is mutual connection or mutual disconnection. The connection / disconnection request data may include the connection / disconnection 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 be mutual connection or mutual disconnection.

[0404] In step S2142, if the connection status indicated by the first status identifier matches the connection request indicated by the connection request data, the control device 410 can 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, if the connection status indicated by the first status identifier is mutual connection, and the connection request indicated by the connection request data is also mutual connection, it can be determined that the wireless connection between the wireless connection device 420 and its battery management device 400 and the first device is normal.

[0405] Correspondingly, in step S2143, if 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 can determine that the wireless connection between the wireless connection device 420 and the first device 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, if the connection status indicated by the first status identifier is mutually disconnected, but the connection request data indicates mutually connected, it can be determined that the wireless connection between the wireless connection device 420 and its battery management device 400 and the first device is abnormal.

[0406] In the technical solution of this application embodiment, by determining whether the connection / disconnection status indicated by the first status identifier is consistent with the connection / disconnection request indicated by the connection / disconnection request data, it is possible to accurately determine whether the wireless connection or disconnection between the wireless connection device 420 and its battery management device 400 and the first device is normal. This technical solution is convenient to implement and highly accurate. It can not only accurately and effectively monitor the wireless connection / disconnection between the battery management device 400 and the first device, but also be easily implemented in the control device 410 through hardware and / or software.

[0407] Optionally, in some embodiments, the first status identifier is configured to: use a first value to indicate that the connection status between the wireless connection device 420 and the first device is connected, and use a second value to indicate that the connection status between the wireless connection device 420 and the first device is disconnected. The 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 connected, and use a second value to indicate that the connection request between the wireless connection device 420 and the first device is disconnected.

[0408] In this implementation, the above Figure 21 Step S2141 may include: determining whether the first status identifier is consistent with the connection / disconnection request data. Further, step S2142 may include: if the first status identifier and the connection / disconnection request data are consistent, determining that the wireless connection between the wireless connection device and the first device is normal. Step S2143 may include: if the first status identifier and the connection / disconnection request data are inconsistent, determining that the wireless connection between the wireless connection device and the first device is abnormal.

[0409] Figure 22 A schematic flowchart of a wireless connection method 2200 for a battery management device 400 according to an embodiment of this application is shown. This wireless connection method 2200 can also be applied to the methods described above. Figure 4 The control device 410 in the battery management device 400 shown.

[0410] like Figure 22 As shown in the embodiments of this application, the wireless connection method 2200 includes the above-described... Figure 19 Based on steps S1910 to S1940 in the illustrated embodiment, if 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 2200 may further include the following steps.

[0411] S2250: Based on the connection / disconnection request command, control the wireless connection device to wirelessly connect to or disconnect from the first device at least once.

[0412] S2260: Detect the first status indicator 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.

[0413] Specifically, in this embodiment of the 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 device 420 to reconnect or disconnect wirelessly with the first device at least once according to the connection request command, so as to repair the abnormal wireless connection between the wireless connection device 420 and the first device.

[0414] Specifically, after each wireless connection device 420 performs a wireless connection or disconnection with the first device, the control device 410 can re-detect the first status indicator of the wireless connection device 420, and determine whether the wireless connection or disconnection between the wireless connection device 420 and the battery management device 400 and the first device is normal based on the newly detected first status indicator.

[0415] By controlling the wireless connection device 420 to reconnect or disconnect wirelessly with the first device at least once, and detecting the first status indicator of the wireless connection device 420 at least once, until it is determined that the wireless connection between the wireless connection device 420 and the battery management device 400 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 controlling the wireless connection device 420 to continue to wirelessly connect or disconnect with the first device.

[0416] Through the technical solution of this application embodiment, 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 wireless connection between the battery management device 400 and the first device is restored to normal, thereby further improving the connection reliability between the battery management device 400 and the first device.

[0417] Figure 23 A schematic flowchart of a wireless connection method 2300 for a battery management device 400 according to an embodiment of this application is shown. This wireless connection method 2300 can also be applied to the methods described above. Figure 4 The control device 410 in the battery management device 400 shown.

[0418] like Figure 23 As shown in the embodiments of this application, the wireless connection method 2300 includes the above-described... Figure 21Based on steps S2110 to S2143 in the illustrated embodiment, after step S2143, i.e., when 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 2300 may further include the following steps.

[0419] S2350: Send connection / disconnection request data to the wireless connection device at least once, so that the wireless connection device wirelessly connects or disconnects from the first device at least once according to the connection / disconnection request data.

[0420] S2360: Detect the first status indicator of the wireless connection device at least once until the connection / disconnection status indicated by the first status indicator matches the connection / disconnection request indicated by the connection / disconnection request data.

[0421] Optionally, step S2350 can be described above. Figure 22 One implementation of step S2250. Step S2360 can be described above. Figure 22 One implementation of step S2260.

[0422] Specifically, in this embodiment of the application, the control device 410 can send the connection request data converted from the connection request command to the wireless connection device 420 at least once, so as to control the wireless connection device 420 to wirelessly connect or disconnect from the first device at least once according to the connection request data.

[0423] Furthermore, after the control device 410 sends a connection / disconnection 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 whether the connection / disconnection status indicated by the first status identifier is consistent with the connection / disconnection request indicated by the connection / disconnection request data, thereby determining whether the wireless connection or disconnection between the wireless connection device 420 and its battery management device 400 and the first device is normal.

[0424] After the control device 410 sends connection disconnection 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 disconnection status indicated by the first status identifier is consistent with the connection disconnection request indicated by the connection disconnection request data, it can be determined that the wireless connection between the wireless connection device 420 and the battery management device 400 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, and the control device 410 stops sending connection disconnection request data to the wireless connection device 420.

[0425] Through the technical solution of this application embodiment, 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 has a high accuracy in judging the abnormal wireless connection between the wireless connection device 420 and its battery management device 400 and the first device, and can effectively and quickly repair the abnormality, so that the wireless connection between the battery management device 400 and the first device can be quickly and reliably restored to the normal state.

[0426] Figure 24 A schematic flowchart of a wireless connection method 2400 for a battery management device 400 according to an embodiment of this application is shown. This wireless connection method 2400 can also be applied to the methods described above. Figure 4 The battery management device 400 shown includes a control device 410. Optionally, the control device 410 may include a non-volatile memory (NVM) module.

[0427] like Figure 24 As shown in the embodiments of this application, the wireless connection method 2400 may include the above-described... Figure 23 Based on steps S2110 to S2143 and steps S2350 to S2360 in the illustrated embodiment, after step S2121, the wireless connection method 2400 may further include the following steps.

[0428] S2410: Store connection / disconnection request data in the NVM module.

[0429] Specifically, in this embodiment, the NVM module is a storage module whose stored data is not lost after a power outage. The NVM module can be located inside the control device 410, facilitating read and write operations by the control device 410. Alternatively, the NVM module can be located outside the control device 410 and electrically connected to it.

[0430] To facilitate subsequent detection of wireless connection failures between the battery management device 400 and the first device based on the connection failure request data, after the control device 410 receives the connection failure request command and converts it into connection failure request data, the control device 410 synchronously stores the connection failure request data in the NVM module. This technical solution prevents the loss of connection failure request data due to external factors such as power outages, ensuring the control device 410's ability to detect wireless connection failures between the wireless connection device 420 and the first device, thereby further improving the connection performance between the battery management device 400 and the first device.

[0431] Based on the NVM module, after step S2143, that is, after determining 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.

[0432] S2420: Obtain connection / disconnection request data from the NVM module.

[0433] After step S2420, the control device 410 executes steps S2350 to S2360.

[0434] 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 connection performance between the battery management device 400 and the first device.

[0435] Figure 25 A schematic flowchart of a wireless connection method 2500 for a battery management device 400 according to an embodiment of this application is shown. This wireless connection method 2500 can also be applied to the methods described above. Figure 4 The control device 410 in the battery management device 400 shown.

[0436] like Figure 25 As shown in the embodiments of this application, the wireless connection method 2500 may include the following steps.

[0437] S2510: Obtain a connection / disconnection request command, which indicates whether the wireless connection between the battery management device and the first device is disconnected.

[0438] S2521: Convert the connection / disconnection request command based on the first communication protocol into connection / disconnection request data based on the second communication protocol.

[0439] S2522: Send connection / disconnection request data to the wireless connection device so that the wireless connection device can wirelessly connect or disconnect from the first device according to the connection / disconnection request data.

[0440] S2531: Detect the first status indicator of the wireless connection device within a first preset time period after sending the connection disconnection request data.

[0441] S2532: Detect the first status indicator of the wireless connection device at every second preset time interval.

[0442] S2540: Based on the first status identifier and connection / disconnection request data, determine whether the wireless connection or disconnection between the wireless connection device and the first device is normal.

[0443] In this application embodiment, the specific implementation schemes of steps S2510, S2521, S2522 and S2540 can be found above. Figure 20 The relevant description in the text. Steps S2531 and S2532 can be described in the above text. Figure 20 One implementation of step S2030.

[0444] Specifically, in step S2531, the first preset time period is greater than or equal to the transmission time of the connection / disconnection request data between the control device 410 and the wireless connection device 420. This transmission time is controlled by the connection method between the control device 410 and the wireless connection device 420. For example, when the control device 410 and the wireless connection device 420 are interconnected via an SPI bus, the data transmission time between them is approximately 5ms. Therefore, in this embodiment, the first preset time period can be 5ms, and within 5ms after sending the connection / disconnection request data to the wireless connection device 420, the control device 410 detects the first status flag of the wireless connection device 420.

[0445] Through this technical solution, the control device 410 can effectively detect the latest first status identifier of the wireless connection device 420, ensuring the validity and reliability of the data. Based on this valid and reliable first status identifier, the effectiveness and reliability of the control device 410's judgment on abnormal wireless connection between the wireless connection device 420 and the first device can be improved.

[0446] Specifically, in step S2532, the control device 410 can also detect the current first status indicator of the wireless connection device 420 at second preset time intervals to realize continuous monitoring of the wireless connection between the wireless connection device 420 and the first device, and ensure the reliability of the long-term wireless connection between the wireless connection device 420 and the first device.

[0447] As an example, in this embodiment, the second preset time period may be less than or equal to 100ms. In other examples, the second preset time period may be adjusted according to the actual situation, and this embodiment does not limit the specific value of the second preset time period.

[0448] Figure 26 A schematic flowchart of a wireless connection method 2600 for a battery management device 400 according to an embodiment of this application is shown. This wireless connection method 2600 can also be applied to the methods described above. Figure 4 The control device 410 in the battery management device 400 shown may optionally be a control chip, or it may also be referred to as a main chip. This control chip (main chip) is connected to a wireless communication chip in the battery management device 400, such as a Bluetooth chip.

[0449] like Figure 26 As shown in the embodiments of this application, the wireless connection method 2600 may include the following steps.

[0450] S2610: Receives Bluetooth connection / disconnection request commands transmitted via CAN.

[0451] S2620: Convert the Bluetooth connection / disconnection command message into connection / disconnection request data, which includes: the Bluetooth MAC address of the device to be connected, its location, and the connection / disconnection request.

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

[0453] S2640: Calls the SPI data transmission state machine to copy the connection / disconnection request data to the array to be transmitted by the SPI.

[0454] S2650: Uses the SPI protocol to transmit connection / disconnection request data to the Bluetooth chip.

[0455] S2660: Reads back the Bluetooth connection status of the Bluetooth chip via SPI after 5ms.

[0456] S2670: Determine whether the connection / disconnection status is the same as the connection / disconnection request data.

[0457] S2680: If the connection disconnection status is different from the connection disconnection request data, read the connection disconnection request data from NVM and call the connection disconnection command processing function again.

[0458] Specifically, in step S2610, during the battery swapping process of the vehicle or during the operation of the vehicle, the main chip in the battery management device 400 can be connected to an external device via the CAN bus. The main chip can receive the Bluetooth connection / disconnection request command transmitted by the external device via the CAN bus. The Bluetooth connection / disconnection request command can be used to indicate the Bluetooth connection / disconnection between the battery management device 400 and the device to be connected (such as the first device mentioned above).

[0459] In step S2620, the main chip converts the Bluetooth connection / disconnection command message into connection / disconnection request data, which includes: Bluetooth MAC, the location of the device to be connected, and the connection / disconnection request.

[0460] Specifically, the Bluetooth connection / disconnection command transmitted via the CAN bus can be message data. The main chip can convert this message data into connection / disconnection request data, which can satisfy the SPI protocol. This connection / disconnection request data can include information such as the Bluetooth MAC address, location, and connection / disconnection request of the device to be connected. This allows the main chip to transmit the connection / disconnection request data to the Bluetooth chip, which can then determine the device to be connected based on the Bluetooth MAC address and location information, and establish a Bluetooth connection with the device based on the connection / disconnection request.

[0461] For step S2630, the main chip may include a main program, which can call a connection / disconnection command processing function. This function can be used to synchronously copy connection / disconnection request data to the SPI accessible structure and the NVM. During the copying process, the connection / disconnection request data can be calibrated; that is, each time a piece of data is copied, the corresponding flag bit is updated to ensure that all connection / disconnection request data has been copied.

[0462] For step S2640, the main chip may also include an SPI data transmission state machine. The main program may call the SPI data transmission state machine, which is used to copy the connection / disconnection request data in the SPI accessible structure to the array to be transmitted by the SPI.

[0463] For step S2650, the main chip may also include an SPI protocol layer, which the main program in the main chip can call to transmit the connection / disconnection request data in the array to be transmitted by SPI to the Bluetooth chip via SPI.

[0464] For step S2660, the time required for one data transmission via the SPI protocol is 5ms. After transmitting data via the SPI protocol, the master chip immediately reads back the status of the Bluetooth chip. For example, the master chip sends a connection / disconnection status request to the Bluetooth chip, and the Bluetooth chip sends its connection / disconnection status with the device to be connected back to the master chip, so that the master chip can read back the current connection / disconnection status between the Bluetooth chip and the device to be connected.

[0465] In step S2670, the main chip determines whether the connection / disconnection status is the same as the connection / disconnection request data. If so, it indicates that the current Bluetooth chip and the device to be connected are connected normally, and no abnormality has occurred.

[0466] If not, proceed to step S2680, where the main chip reads the connection request data from the NVM, calls the connection command processing function again, and copies the connection request data to the SPI accessible structure and the NVM again. Then, repeat steps S2630 to S2670 to retransmit the connection request data to the Bluetooth chip and read back the Bluetooth chip's Bluetooth connection status until the connection status is found to be the same as the connection request data, thus confirming that the current connection between the Bluetooth chip and the device to be connected is normal and no abnormality has occurred.

[0467] The above text combined Figure 3 , Figures 5 to 26 This application describes an embodiment of the wireless connection method for the battery management device. The following is a detailed explanation in conjunction with... Figure 27 and Figure 28 This application describes an embodiment of the battery management device. It should be understood that the device embodiments correspond to the method embodiments, and similar descriptions can be found in the method embodiments.

[0468] Figure 27 A schematic structural block diagram of a battery management device 2700 provided in an embodiment of this application is shown.

[0469] like Figure 27 As shown in the embodiment of this application, the battery management device 2700 includes a wireless connection device 2710, wherein the wireless connection device 2710 includes a first connection / disconnection module 2711, a first detection module 2712, and a first processing module 2713.

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

[0471] In some possible implementations, the connection / disconnection status data includes: a first status identifier, which indicates whether the wireless connection device and the first device are connected or disconnected.

[0472] In some possible implementations, the first connection / disconnection module 2711 is configured to: receive connection / disconnection request data, and wirelessly connect or disconnect with the first device according to the connection / disconnection request data. The first detection module 2712 is configured to: detect a first status indicator. The first processing module 2713 is configured to: determine whether the wireless connection or disconnection with the first device is normal based on the first status indicator and the connection / disconnection request data.

[0473] In some possible implementations, the first processing module 2713 is configured to: determine whether the connection / disconnection status indicated by the first status identifier is consistent with the connection / disconnection request indicated by the connection / disconnection request data; if the connection / disconnection status indicated by the first status identifier is consistent with the connection / disconnection request indicated by the connection / disconnection request data, determine that the wireless connection with the first device is normal; if the connection / disconnection status indicated by the first status identifier is inconsistent with the connection / disconnection request indicated by the connection / disconnection request data, determine that the wireless connection with the first device is abnormal.

[0474] In some possible implementations, if the first processing module 2713 determines that the wireless connection or disconnection with the first device is abnormal, the first processing module 2713 is further configured to: perform the wireless connection or disconnection with the first device at least once more according to the connection / disconnection request data; and detect the first status identifier at least once until the number of executions reaches a preset number or the connection / disconnection status indicated by the first status identifier is consistent with the connection / disconnection request indicated by the connection / disconnection request data.

[0475] In some possible implementations, such as Figure 27 As shown, 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 further configured to: store connection / disconnection request data to the structure module 2714 and / or the non-volatile memory module 2715.

[0476] In some possible implementations, the first processing module 2713 is further configured to: store the first state identifier to the structure module 2714 and / or the non-volatile storage module 2715.

[0477] In some possible implementations, after the first processing module 2713 stores the connection disconnection request data in the non-volatile storage module 2715, the first processing module 2713 is further configured to: read the connection disconnection request data from the non-volatile storage module 2715 after the battery management device 2700 is powered off and then powered on again; and reconnect or disconnect wirelessly with the first device according to the connection disconnection request data.

[0478] In some possible implementations, after the first processing module 2713 stores the first status identifier in the non-volatile storage module 2715, the first processing module 2713 is further configured to: read the first status identifier from the non-volatile storage module 2715 after the battery management device 2700 is powered off and then powered on again; and reconnect or disconnect wirelessly with the first device according to the connection / disconnection request data and the first status identifier.

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

[0480] In some possible implementations, the connection / disconnection status data further includes: a first information identifier, which indicates 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 used to determine, based on the first information identifier, whether the wireless connection or disconnection with the first device is normal.

[0481] In some possible implementations, the first information identifier is used to indicate whether the execution of wirelessly connecting or disconnecting from the first device is completed; the first processing module 2713 is used to: determine whether the execution of wirelessly connecting or disconnecting from the first device is completed based on the first information identifier; if the execution of wirelessly connecting or disconnecting from the first device is not completed, determine that the wireless connection or disconnection with the first device is abnormal; if the execution of wirelessly connecting or disconnecting from the first device is completed, determine that the wireless connection or disconnection with the first device is normal.

[0482] In some possible implementations, if the first processing module 2713 determines that the wireless connection or disconnection with the first device is abnormal, the first processing module 2713 is further configured to: perform the wireless connection or disconnection with the first device at least once more; and detect the first information identifier at least once more until the first information identifier indicates that the wireless connection or disconnection with the first device has been completed.

[0483] In some possible implementations, the first connection / disconnection module 2711 includes a state machine module and a wireless communication protocol stack module. The state machine module is used to invoke the wireless communication protocol stack module based on connection / disconnection request data; the wireless communication protocol stack module is used to execute wireless connection or disconnection with the first device to form a first information identifier, wherein the first information identifier is used to indicate the execution status of the wireless communication protocol stack module's wireless connection or disconnection with the first device.

[0484] 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.

[0485] 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, wherein the first message is used to indicate master-slave authentication of the first device; perform algorithm processing on the first random number to obtain a first target number; and send a second message matching the first message and the first target number to the first device so that the first device can identify the second message and perform algorithm checks on the first target number to determine the result of master-slave authentication.

[0486] Figure 28 A schematic structural block diagram of another battery management device 2800 provided in an embodiment of this application is shown.

[0487] like Figure 28 As shown in the embodiment of this application, the battery management device 2800 includes: the aforementioned wireless connection device 2710 and the 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 a second processing module 2812.

[0488] Specifically, the second detection module 2811 is used to detect the first status indicator of the wireless connection device 2710. The second processing module 2812 is used to determine, based on the first status indicator, whether the wireless connection or disconnection between the wireless connection device 2710 and the first device is normal.

[0489] In some possible implementations, such as Figure 28 As shown, the control device 2810 further includes a second receiving module 2813 and a second transmitting module 2814. The second receiving module 2813 is used to: acquire a connection / disconnection request command, which indicates whether the battery management device and the first device are wirelessly connected or disconnected. The second processing module 2812 is used to: convert the connection / disconnection request command based on a first communication protocol into connection / disconnection request data based on a second communication protocol, wherein the first and second communication protocols are two different types of communication protocols. The second transmitting module 2814 is used to: send the connection / disconnection request data to the wireless connection device 2710, so that the wireless connection device 2710 wirelessly connects or disconnects from the first device according to the connection / disconnection request data.

[0490] In some possible implementations, the second processing module 2812 is used 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 / disconnection request data.

[0491] In some possible implementations, the second processing module 2812 is used to: determine whether the connection / disconnection status indicated by the first status identifier is consistent with the connection / disconnection request indicated by the connection / disconnection request data; if the connection / disconnection status indicated by the first status identifier is consistent with the connection / disconnection request indicated by the connection / disconnection request data, determine that the wireless connection or disconnection between the wireless connection device 2710 and the first device is normal; if the connection / disconnection status indicated by the first status identifier is inconsistent with the connection / disconnection request indicated by the connection / disconnection request data, determine that the wireless connection or disconnection between the wireless connection device 2710 and the first device is abnormal.

[0492] In some possible implementations, if 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 further configured to: control the wireless connection device 2710 to wirelessly connect or disconnect from the first device at least once according to the connection / disconnection request command; detect the first status indicator of the wireless connection device 2710 at least once until it is determined that the wireless connection or disconnection between the wireless connection device 2710 and the first device is normal.

[0493] In some possible implementations, such as Figure 28 As shown, the control device 2810 also includes a non-volatile storage module 2815. After the second processing module 2812 converts the connection / disconnection request command into connection / disconnection request data, the second processing module 2812 is further configured to: store the connection / disconnection request data in the non-volatile storage module 2815.

[0494] 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 / disconnect module 2711 in the wireless connection device 2710 is used to connect or disconnect with the first device via Bluetooth.

[0495] In some possible implementations, the battery management device 2700 or battery management device 2800 is the main battery management unit (MBMU) in the power-consuming device, and the first device is the slave battery management unit (SBMU) in the power-consuming device; or, the battery management device 2700 or battery management device 2800 is the rechargeable battery management unit (CBMU) in the battery swapping device, and the first device is the slave battery management unit (SBMU) in the battery swapping device; or, the battery management device 2700 or battery management device 2800 is the battery swapping battery management unit (TBMU) in the battery swapping device, and the first device is the main battery management unit (MBMU) in the power-consuming device.

[0496] Figure 29 A schematic structural block diagram of another battery management device 2900 provided in an embodiment of this application is shown.

[0497] like Figure 29As shown, the battery management device 2900 includes a processor 2910 and a memory 2920, wherein the memory 2920 is used to store programs, and the processor 2910 is used to call and run programs from the memory 2920 to perform the wireless connection method in the above embodiments.

[0498] Specifically, the battery management device 2900 may also include a wireless connection device and a control device. The wireless connection device includes a first processor and a first memory, which cooperate to implement the wireless connection method in the above embodiments, where the wireless connection device acts as the execution subject. Additionally, the control device includes a second processor and a second memory, which cooperate to implement the wireless connection method in the above embodiments, where the control device acts as the execution subject.

[0499] Figure 30 A schematic structural block diagram of an electronic device 3000 provided in an embodiment of this application is shown.

[0500] like Figure 30 As shown, the electronic device 3000 may include: the battery management device 2700, battery management device 2800 or battery management device 2900 described above.

[0501] Optionally, the electronic device 3000 can be an electrical appliance, such as the one described above. Figure 1 The vehicle 1 shown. Alternatively, the electronic device 3000 can also be a battery swapping device, for example, the battery swapping device can be the one described above. Figure 2 The battery swapping station 2 shown in the image.

[0502] It should be understood that the specific examples in this document are only intended to help those skilled in the art better understand the embodiments of this application, and are not intended to limit the scope of the embodiments of this application.

[0503] It should also be understood that, in the various embodiments of this application, the sequence number of each process does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0504] It should also be understood that the various implementation methods described in this specification can be implemented individually or in combination, and the embodiments of this application are not limited in this respect.

[0505] Although this application has been described with reference to preferred embodiments, various modifications can be made thereto and components can be replaced with equivalents without departing from the scope of this application. In particular, the technical features mentioned in the various embodiments can be combined in any manner, provided there is no structural conflict. This application is not limited to the specific embodiments disclosed herein, but includes all technical solutions falling within the scope of the claims.

Claims

1. A wireless connection method for a battery management device, characterized in that, include: Wirelessly connect to or disconnect from the first device; Detect connection status data between the device and the first device; Based on the connection / disconnection status data, determine whether the wireless connection or disconnection with the first device is normal; The battery management device includes: a wireless connection device; the connection / disconnection status data includes: a first status identifier, which indicates whether the wireless connection device and the first device are connected or disconnected. The wireless connection or disconnection with the first device includes: The wireless connection device receives connection / disconnection request data; The wireless connection device wirelessly connects to or disconnects from the first device according to the connection / disconnection request data. The detection of connection status data between the device and the first device includes: The wireless connection device detects the first status identifier. The step of determining whether the wireless connection or disconnection with the first device is normal based on the connection / disconnection 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 / disconnection request data.

2. The wireless connection method according to claim 1, characterized in that, 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 / disconnection request data, including: The wireless connection device determines whether the connection / disconnection status indicated by the first status identifier is consistent with the connection / disconnection request indicated by the connection / disconnection request data. 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 determines 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, the wireless connection device determines that the wireless connection with the first device is abnormal.

3. The wireless connection method according to claim 2, characterized in that, If 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 shall, at least once more, wirelessly connect to or disconnect from the first device based on the connection / disconnection 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 / disconnection status indicated by the first status identifier is consistent with the connection / disconnection request indicated by the connection / disconnection request data.

4. The wireless connection method according to claim 1, characterized in that, The wireless connection device includes a structural module and / or a non-volatile storage module; Wherein, after the wireless connection device receives the connection / disconnection request data, the wireless connection method further includes: The wireless connection device stores the connection / disconnection request data in the structure module and / or the non-volatile storage module; Furthermore, the wireless connection device stores the first state identifier in the structure module and / or the non-volatile storage module.

5. The wireless connection method according to claim 4, characterized in that, After the wireless connection device stores the connection / disconnection request data in the non-volatile storage module, the wireless connection method further includes: After the battery management device is powered off and then powered on again, the wireless connection device reads the connection disconnection request data from the non-volatile storage module; The wireless connection device reconnects or disconnects from the first device wirelessly based on the connection / disconnection request data.

6. The wireless connection method according to claim 5, characterized in that, After the wireless connection device stores the first state identifier to the non-volatile storage module, the wireless connection method further includes: After the battery management device is powered off and then powered on again, the wireless connection device reads the first status identifier from the non-volatile storage module; The wireless connection device reconnects or disconnects from the first device wirelessly based on the connection / disconnection request data, including: The wireless connection device reconnects or disconnects wirelessly with the first device based on the connection / disconnection request data and the first status identifier.

7. The wireless connection method according to claim 6, characterized in that, After the battery management device is powered off and then powered on again, the connection disconnection request data read by the wireless connection device from the non-volatile storage module is connection request data. The wireless connection device wirelessly connects or disconnects from the first device based on the connection / disconnection request data and the first status identifier, including: The wireless connection device determines whether the connection status indicated by the first status identifier is a connection; When the connection status indicated by the first status identifier is connected, the wireless connection device reconnects wirelessly to the first device according to the connection request data.

8. The wireless connection method according to claim 1, characterized in that, The connection / disconnection status data further includes: a first information identifier, which is used to indicate the execution status of the wireless connection device wirelessly connecting or disconnecting from the first device; The connection status data between the detection device and the first device includes: The wireless connection device detects the first information identifier; The step of determining whether the wireless connection or disconnection with the first device is normal based on the connection / disconnection 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.

9. The wireless connection method according to claim 8, characterized in that, The first information identifier is used to indicate whether the wireless connection or disconnection with the first device has been completed; 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 wireless connection or disconnection with the first device has been completed based on the first information identifier. If 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; Once 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.

10. The wireless connection method according to claim 9, characterized in that, If 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 shall wirelessly connect to or disconnect from the first device at least once more; The wireless connection device will detect the first information identifier at least once more until the first information identifier indicates that the wireless connection with the first device or the disconnection is completed.

11. The wireless connection method according to claim 8, characterized in that, The wireless connection device includes: a state machine module and a wireless communication protocol stack module; The step of wirelessly connecting or disconnecting from the first device based on the connection / disconnection request data includes: The state machine module calls the wireless communication protocol stack module based on the connection / disconnection 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 the execution status of the wireless communication protocol stack module wirelessly connecting or disconnecting with the first device.

12. The wireless connection method according to claim 1, characterized in that, After wirelessly connecting to the first device, the wireless connection method further includes: The wireless connection device performs master-slave authentication with the first device.

13. The wireless connection method according to claim 12, 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, wherein 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 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 can identify the second message and perform an algorithm check on the first target number to determine the master-slave authentication result.

14. The wireless connection method according to claim 1, characterized in that, The battery management device includes: a control device connected to the wireless connection device; The connection status data between the detection device and the first device includes: The control device detects the first status identifier of the wireless connection device; The step of determining whether the wireless connection or disconnection with the first device is normal based on the connection / disconnection 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 indicator.

15. The wireless connection method according to claim 14, characterized in that, The wireless connection or disconnection with the first device includes: The control device acquires a connection / disconnection request command, which is used to indicate whether the wireless connection between the battery management device and the first device is disconnected. The control device converts the connection / disconnection request command based on the first communication protocol into connection / disconnection request data based on the second communication protocol, wherein the first communication protocol and the second communication protocol are different. The control device sends the connection / disconnection request data to the wireless connection device, so that the wireless connection device can wirelessly connect to or disconnect from the first device according to the connection / disconnection request data.

16. The wireless connection method according to claim 15, 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 indicator, 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 / disconnection request data.

17. The wireless connection method according to claim 16, 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 and the connection / disconnection request data, including: The control device determines whether the connection / disconnection status indicated by the first status identifier is consistent with the connection / disconnection request indicated by the connection / disconnection request data. If the connection / disconnection status indicated by the first status identifier is consistent with the connection / disconnection request indicated by the connection / disconnection request data, the control device determines that the wireless connection or disconnection between the wireless connection device and the first device is normal. If the connection / disconnection status indicated by the first status identifier is inconsistent with the connection / disconnection request indicated by the connection / disconnection request data, the control device determines that the wireless connection or disconnection between the wireless connection device and the first device is abnormal.

18. The wireless connection method according to claim 14, characterized in that, If the control device determines that the wireless connection between the wireless connection device and the first device is abnormal, the wireless connection method further includes: According to the connection / disconnection request command, the control device controls the wireless connection device to wirelessly connect to or disconnect from the first device at least once. The control device detects the first status indicator 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.

19. The wireless connection method according to claim 15, characterized in that, The control device includes a non-volatile storage module. After the control device converts the connection / disconnection request command into connection / disconnection request data, the wireless connection method further includes: The control device stores the connection / disconnection request data in the non-volatile storage module.

20. The wireless connection method according to any one of claims 1 to 19, characterized in that, The wireless connection or disconnection with the first device includes: Connect or disconnect via Bluetooth with the first device.

21. The wireless connection method according to any one of claims 1 to 20, characterized in that, The battery management device is the main battery management unit (MBMU) in the electrical device, and the first device is the slave battery management unit (SBMU) in the electrical device. or, The battery management device is the rechargeable battery management unit (CBMU) in the battery swapping device, and the first device is the slave battery management unit (SBMU) in the battery swapping device. or, The battery management device is the battery management unit (TBMU) in the battery swapping equipment, and the first device is the main battery management unit (MBMU) in the power-consuming equipment.

22. A battery management device, characterized in that, include: A wireless connection device, the wireless connection device comprising: The first connection / disconnection module is used to wirelessly connect to or disconnect from the first device; The first detection module is used to detect the connection status data with the first device; The first processing module is used to determine whether the wireless connection or disconnection with the first device is normal based on the connection / disconnection status data. The connection / disconnection status data includes: a first status identifier, which is used to indicate whether the wireless connection device and the first device are connected or disconnected; The first connection / disconnection module is used to: receive connection / disconnection request data, and wirelessly connect or disconnect with the first device according to the connection / disconnection request data; The first detection module is used to: detect the first status identifier; The first processing module is used to: determine whether the wireless connection or disconnection with the first device is normal based on the first status identifier and the connection / disconnection request data.

23. The battery management device according to claim 22, characterized in that, The first processing module is used for: Determine whether the connection / disconnection status indicated by the first status identifier is consistent with the connection / disconnection request indicated by the connection / disconnection request data; If the connection / disconnection status indicated by the first status identifier is consistent with the connection / disconnection request indicated by the connection / disconnection request data, the wireless connection with the first device is determined to be normal. If the connection status indicated by the first status identifier is inconsistent with the connection request indicated by the connection request data, the wireless connection with the first device is determined to be abnormal.

24. The battery management device according to claim 23, characterized in that, If the first processing module determines that the wireless connection or disconnection with the first device is abnormal, the first processing module is further configured to: Based on the connection / disconnection request data, perform at least one more wireless connection or disconnection with the first device; The first status identifier is checked at least once until the number of executions reaches a preset number or the connection / disconnection status indicated by the first status identifier is consistent with the connection / disconnection request indicated by the connection / disconnection request data.

25. The battery management device according to claim 22, characterized in that, The wireless connection device further includes a structural module and / or a non-volatile storage module; The first processing module is further configured to: store the connection disconnection request data in the structure module and / or the non-volatile storage module; The first state identifier is stored in the structure module and / or the non-volatile storage module.

26. The battery management device according to claim 25, characterized in that, After the first processing module stores the connection disconnection request data in the non-volatile storage module, the first processing module is further configured to: After the battery management device is powered off and then powered on again, the connection interruption request data is read from the non-volatile storage module; Based on the connection / disconnection request data, reconnect or disconnect wirelessly with the first device.

27. The battery management device according to claim 26, characterized in that, After the first processing module stores the first state identifier into the non-volatile storage module, the first processing module is further configured to: After the battery management device is powered off and then powered on again, the first status identifier is read from the non-volatile storage module; Based on the connection / disconnection request data and the first status identifier, reconnect or disconnect wirelessly with the first device.

28. The battery management device according to claim 27, characterized in that, After the battery management device is powered off and then powered on again, the connection disconnection request data read by the first processing module from the non-volatile storage module is connection request data. The first processing module is used to: determine whether the connection / disconnection status indicated by the first status identifier is connected; If the connection status indicated by the first status identifier is "connected", the device wirelessly reconnects to the first device according to the connection request data.

29. The battery management device according to claim 22, characterized in that, The connection / disconnection status data further includes: a first information identifier, which is used to indicate the execution status of the wireless connection device wirelessly connecting or disconnecting from the first device; The first detection module is used to: detect the first information identifier; The first processing module is used to: determine whether the wireless connection or disconnection with the first device is normal based on the first information identifier.

30. The battery management device according to claim 29, characterized in that, The first information identifier is used to indicate whether the wireless connection or disconnection with the first device has been completed; The first processing module is used to: determine whether the wireless connection or disconnection with the first device has been completed based on the first information identifier; If the wireless connection or disconnection with the first device is not completed, the wireless connection or disconnection with the first device is determined to be abnormal. Once 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.

31. The battery management device according to claim 30, characterized in that, In cases where the first processing module determines that the wireless connection or disconnection with the first device is abnormal, the first processing module is further configured to: Perform at least one more wireless connection or disconnection with the first device; The first information identifier is checked at least once more until the first information identifier indicates that the wireless connection with the first device has been completed or disconnected.

32. The battery management device according to claim 29, characterized in that, The first connection / disconnection 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 / disconnection request data; The wireless communication protocol stack module is used 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 the execution status of the wireless communication protocol stack module wirelessly connecting or disconnecting with the first device.

33. The battery management device according to claim 22, characterized in that, The wireless connection device further includes a first receiving unit. After the first processing module is used to wirelessly connect with the first device, the first receiving unit and the first processing module are further used to: Perform master-slave authentication with the first device.

34. The battery management device according to claim 33, characterized in that, The wireless connection device further includes: a first transmitting unit; The first receiving unit is configured to: receive a first message and a first random number sent by the first device, wherein the first message is used to indicate master-slave authentication of the first device; The first processing module is used 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 can identify the second message and perform an algorithm check on the first target number to determine the master-slave authentication result.

35. The battery management device according to claim 22, characterized in that, The battery management device further includes: a control device connected to the wireless connection device, and the control device comprising: The second detection module is used to detect the first status identifier of the wireless connection device; The second processing module is used to determine whether the wireless connection or disconnection between the wireless connection device and the first device is normal based on the first status indicator.

36. The battery management device according to claim 35, characterized in that, The control device further includes: a second receiving module and a second transmitting module; The second receiving module is used to: acquire a connection / disconnection request command, the connection / disconnection request command being used to indicate whether the wireless connection between the battery management device and the first device is disconnected; The second processing module is used to: convert the connection / disconnection request command based on the first communication protocol into connection / disconnection request data based on the second communication protocol, wherein the first communication protocol is different from the second communication protocol; The second sending module is used to send the connection / disconnection request data to the wireless connection device, so that the wireless connection device can wirelessly connect to or disconnect from the first device according to the connection / disconnection request data.

37. The battery management device according to claim 36, characterized in that, The second processing module is used to: determine 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 / disconnection request data.

38. The battery management device according to claim 37, characterized in that, The second processing module is used for: Determine whether the connection / disconnection status indicated by the first status identifier is consistent with the connection / disconnection request indicated by the connection / disconnection request data; If the connection / disconnection status indicated by the first status identifier is consistent with the connection / disconnection request indicated by the connection / disconnection request data, it is determined that the wireless connection or disconnection between the wireless connection device and the first device is normal. If the connection / disconnection status indicated by the first status identifier is inconsistent with the connection / disconnection request indicated by the connection / disconnection request data, the wireless connection or disconnection between the wireless connection device and the first device is determined to be abnormal.

39. The battery management device according to claim 35, characterized in that, If the second processing module determines that the wireless connection or disconnection between the wireless connection device and the first device is abnormal, the second processing module is further configured to: According to the connection / disconnection request command, control the wireless connection device to wirelessly connect to or disconnect from the first device at least once; The first status indicator of the wireless connection device is checked at least once until it is determined that the wireless connection or disconnection between the wireless connection device and the first device is normal.

40. The battery management device according to claim 36, characterized in that, The control device further includes a non-volatile storage module. After the second processing module converts the connection / disconnection request command into connection / disconnection request data, the second processing module is further configured to: The connection disconnection request data is stored in the non-volatile storage module.

41. The battery management device according to claim 22, characterized in that, The first connection / disconnection module is used to connect or disconnect with the first device via Bluetooth.

42. The battery management device according to any one of claims 22 to 41, characterized in that, The battery management device is the main battery management unit (MBMU) in the electrical device, and the first device is the slave battery management unit (SBMU) in the electrical device. or, The battery management device is the rechargeable battery management unit (CBMU) in the battery swapping device, and the first device is the slave battery management unit (SBMU) in the battery swapping device. or, The battery management device is the battery management unit (TBMU) in the battery swapping equipment, and the first device is the main battery management unit (MBMU) in the power-consuming equipment.

43. A battery management device, characterized in that, include: A processor and a memory, the memory being used to store a program, the processor being used to call and run the program from the memory to perform the wireless connection method according to any one of claims 1 to 21.

44. An electronic device, characterized in that, include: The battery management device as described in any one of claims 22 to 42.

45. The electronic device according to claim 44, characterized in that, The electronic device is a power-consuming device or a power-swapping device.

Images