Battery state monitoring method for a vehicle and vehicle

Abstract

The embodiment of the application provides a battery state monitoring method of a vehicle and the vehicle, and the method comprises the following steps: collecting battery related information and running information of the vehicle; determining a working condition of the vehicle according to the running information of the vehicle; and detecting a first type of abnormality of battery capacity of a target battery in the working condition according to the battery related information and / or the running information of the vehicle. The embodiment of the application can monitor the abnormality of the battery capacity of the vehicle.

Description

Technical Field

[0001] This application relates to the field of vehicle battery management technology, and more particularly to a method for monitoring the battery status of a vehicle and a vehicle. Background Technology

[0002] In new energy vehicles and intelligent vehicles, the battery's state of charge (SOC) is a key parameter for energy management and user interaction. However, currently, users sometimes find that the battery's SOC changes irrationally during vehicle use, leading to a poor user experience and decreased trust in the vehicle. Summary of the Invention

[0003] This application provides a method for monitoring the battery status of a vehicle and a vehicle that can monitor abnormal changes in the battery charge level.

[0004] Firstly, embodiments of this application provide a method for monitoring the state of a vehicle's battery, comprising: collecting battery-related information and vehicle operating information; determining the vehicle's operating condition based on the vehicle's operating information; and detecting a first type of charge anomaly in the target battery under the operating condition based on the battery-related information and / or the vehicle's operating information. This method determines the vehicle's operating condition based on the vehicle's operating information, and then detects a first type of charge anomaly in the target battery under the operating condition based on the battery-related information and / or the vehicle's operating information, thereby achieving the monitoring of abnormal changes in the charge of the target battery in the vehicle; furthermore, the monitoring results can provide a data basis for subsequent optimization of the vehicle battery's control strategy, improving the control performance of the vehicle battery.

[0005] One possible implementation also includes: detecting a second type of charge anomaly in the target battery based on battery-related information and / or vehicle operating information.

[0006] In one possible implementation, the operating conditions include: driving operating conditions, which are determined based on the vehicle's operating information, including: When the vehicle speed is greater than 0 and the vehicle's overall operating mode is driving mode, the vehicle's operating condition is determined to be driving condition. And / or, Operating conditions include: Recharging condition, which is determined based on the vehicle's operating information, including: When the vehicle's overall operating mode is charging or low-voltage battery charging, the vehicle's operating condition is determined to be charging condition. And / or, Operating conditions include: power-off operating condition, which is determined based on the vehicle's operating information, including: When the vehicle's overall power supply mode is off and the vehicle's operating mode is any one of power-off, hibernation, low-voltage battery charging, or charging, the vehicle's operating condition is determined to be power-off. And / or, Operating conditions include: power-off and power-on conditions. The vehicle's operating conditions are determined based on its operating information, including: When the vehicle's overall power mode is off and the vehicle's operating mode is charging or low-voltage battery charging, the vehicle's operating condition is determined to be a power-off and charging condition. And / or, Operating conditions include: power-off and no power replenishment. The vehicle's operating condition is determined based on its operating information, including: When the vehicle's overall power supply mode is off and the vehicle's operating mode is power-down or hibernation, the vehicle's operating condition is determined to be power-down and without power replenishment.

[0007] In one possible implementation, the vehicle operates under driving conditions. Based on battery-related information and / or vehicle operating information, a first type of charge anomaly in the target battery under these conditions is detected, including: If, during a period when the vehicle is under electrical load, the duration for which the output current of the target battery is less than the first current threshold is greater than the first time threshold, it is determined that an abnormality of battery non-discharge under driving conditions has been detected.

[0008] In one possible implementation, if the vehicle is in a charging condition, a first type of charge anomaly of the target battery is detected based on battery-related information and / or vehicle operating information, including: if the target battery's SOC change is less than or equal to a first charge change threshold and the target battery's voltage change is greater than a voltage change threshold during the charging condition, it is determined that no abnormal change in battery SOC is detected during the charging condition.

[0009] In one possible implementation, the vehicle operates in a power-off state. Based on battery-related information and / or vehicle operating information, a first type of charge anomaly of the target battery under the power-off state is detected, including: if the duration of the power-off state is greater than a second time threshold, and the duration of the target battery satisfying a first condition exceeds a third time threshold, it is determined that a high SOC and low voltage anomaly under the power-off state has been detected; the first condition includes: the SOC of the target battery is greater than or equal to the charge threshold and the voltage of the target battery is less than or equal to the voltage threshold.

[0010] In one possible implementation, a first type of power anomaly of the target battery is detected based on battery-related information and / or vehicle operating information, including: if the SOC of the target battery increases during the period when the vehicle is powered off and not recharged, an abnormal increase in SOC under the power-off and non-recharged operating condition is detected.

[0011] In one possible implementation, the detection of a first type of battery charge anomaly under the operating condition based on battery-related information and / or vehicle operating information includes: if the vehicle is in a power-down and recharging condition, and M effective recharging events for the target battery occur within N consecutive power-down events, it is determined that a frequent recharging anomaly under the power-down and recharging condition has been detected; the N consecutive complete power-down events include the power-down events to which the current power-down and recharging condition of the vehicle belongs; an effective recharging event for the target battery refers to a recharging event in which the duration of a single recharging of the target battery exceeds a fourth time threshold; N and M are both integers greater than 0.

[0012] In one possible implementation, the second type of power anomaly includes: anomalies that do not meet the self-learning conditions. The second type of power anomaly of the target battery is detected based on battery-related information and / or vehicle operating information, including: If the vehicle's overall operating mode is sleep mode, and the acquisition time of two adjacent frames of data is greater than the first duration and less than the second duration, it is determined that an anomaly that does not meet the self-learning conditions has been detected; and / or, if the vehicle's overall operating mode is sleep mode, and the acquisition time of two adjacent frames of data is greater than the first duration and less than the second duration, and target user operation is detected, it is determined that an anomaly that does not meet the self-learning conditions has been detected; and / or, if the vehicle's overall operating mode is sleep mode, and the SOC change of the target battery exceeds the second charge change threshold, or the DC-DC converter is detected to be working, or the charging current of the target battery is detected, or it is determined that the initial SOC is not within the calibrable range, it is determined that an anomaly that does not meet the self-learning conditions has been detected; and / or, if the battery temperature of the target battery is detected to be lower than the first temperature threshold, or the battery temperature of the target battery is detected to be higher than the second temperature threshold, or a serious fault code is detected, or the target bus communication is detected to be interrupted, it is determined that an anomaly that does not meet the self-learning conditions has been detected. And / or, The second type of power anomaly includes: SOC jump anomaly. This type of power anomaly is detected in the target battery based on battery-related information and / or vehicle operating information, including: If the SOC difference of the target battery in two adjacent frames of data is greater than the first threshold, and the time interval between the acquisition times of the two adjacent frames of data is less than the fifth time threshold, it is determined that an abnormal SOC jump has been detected.

[0013] In one possible implementation, the method further includes: when a first type of power anomaly is detected, generating an anomaly event record, the anomaly event record including at least one of the following information: the anomaly type of the first type of power anomaly, the time of occurrence, the current SOC of the target battery, the voltage of the target battery, the current of the target battery, the current operating condition of the vehicle, and snapshots of the number of target frames before and after.

[0014] In a second aspect, embodiments of this application provide a vehicle, including: a processor and a memory; wherein one or more computer programs are stored in the memory, and the one or more computer programs include instructions that, when executed by the processor, cause the vehicle to perform the method of any of the first aspects.

[0015] Thirdly, embodiments of this application provide a computer-readable storage medium storing a computer program that, when moved on a computer, causes the computer to execute the method of any one of the first aspects.

[0016] Fourthly, embodiments of this application provide a computer program product, which includes a computer program that, when run on a computer, causes the computer to perform the method of any one of the first aspects. Attached Figure Description

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

[0018] Figure 1 A schematic diagram of the structure of a vehicle provided in an embodiment of this application; Figure 2 A schematic flowchart of a vehicle battery state monitoring method provided in an embodiment of this application; Figure 3 Another schematic flowchart of the vehicle battery state monitoring method provided in the embodiments of this application; Figure 4 A schematic diagram of a third method for monitoring the battery status of a vehicle provided in an embodiment of this application; Figure 5 This is a schematic diagram of the fourth process of the vehicle battery state monitoring method provided in the embodiments of this application; Figure 6 This is a schematic diagram of a vehicle battery status monitoring device provided in an embodiment of this application. Detailed Implementation

[0019] The terminology used in the implementation section of this application is for the purpose of explaining specific embodiments of this application only, and is not intended to limit this application.

[0020] In new energy vehicles and intelligent vehicles, the state of charge (SOC) of the battery is a key parameter for energy management and user interaction. However, currently, users sometimes find that the battery SOC changes irrationally during vehicle use, leading to a poor user experience and a decrease in user trust in the vehicle.

[0021] Therefore, embodiments of this application provide a method for monitoring the battery status of a vehicle and a vehicle capable of monitoring abnormal changes in the charge level of a target battery in the vehicle.

[0022] The embodiments of this application can be applied to vehicles or remote diagnostic terminals that can communicate with vehicles.

[0023] The target battery in this application embodiment can be a low-voltage storage battery of a vehicle or a power battery of a vehicle. The following example uses a low-voltage storage battery of a vehicle as the target battery; however, it can be understood that the low-voltage storage battery in the following embodiments can also be replaced by a power battery.

[0024] Figure 1 A schematic diagram of the structure of a vehicle provided in an embodiment of this application, such as... Figure 1 As shown, vehicle 100 may include: processor 110, memory 120, battery 130, vehicle wireless terminal (Telematics BOX, TBOX) 140, etc.

[0025] The processor 110, memory 120, and vehicle wireless terminal (Telematics BOX, TBOX) 140 can communicate with each other through an internal communication link, such as a Controller Area Network (CAN) bus, to transmit control and / or data signals. The memory 120 is used to store computer programs, and the processor 110 is used to call and run the computer programs from the memory 120.

[0026] The processor 110 may include one or more processing units, such as a vehicle control unit (VCU), a conversion and distribution unit (CDU), a battery management system (BMS), a motor control unit (MCU), etc.

[0027] The aforementioned memory 120 may be a read-only memory (ROM), other types of static storage devices capable of storing static information and instructions, random access memory (RAM), or other types of dynamic storage devices capable of storing information and instructions. It may also be an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compressed optical discs, laser discs, optical discs, digital universal optical discs, Blu-ray discs, etc.), magnetic disk storage media, or other magnetic storage devices. Alternatively, it may be any other medium capable of carrying or storing desired program code in the form of instructions or data structures that can be accessed by a computer.

[0028] The processor 110 and memory 120 can be combined into a single processing device, or more commonly, they are independent components. The processor 110 executes the program code stored in the memory 120 to achieve the aforementioned functions. In specific implementations, the memory 120 can be integrated into the processor 110, or it can be independent of the processor 110.

[0029] The vehicle-mounted wireless terminal 140 can support communication between the vehicle and external devices such as remote diagnostic terminals.

[0030] Battery 130 may include a power battery and a low-voltage storage battery. The power battery provides the main power for high-voltage electrical equipment such as vehicle drive and air conditioning. The low-voltage storage battery supplies power to the vehicle's low-voltage electrical appliances and starting control module, and maintains power supply to the low-voltage system when the vehicle is in sleep mode.

[0031] The following will combine Figure 1 The vehicle implementation structure shown is an exemplary illustration of the battery state monitoring method for vehicles according to embodiments of this application.

[0032] The embodiments of this application can be executed by a vehicle or by a remote diagnostic terminal connected to the vehicle. When the embodiments of this application are executed by a vehicle, they can be specifically executed by the VCU or BMS in the vehicle.

[0033] Figure 2 This is a schematic flowchart of a vehicle battery state monitoring method provided in an embodiment of this application, such as... Figure 2 As shown, the method may include: Step 201: Collect battery-related information and vehicle operation information.

[0034] In some embodiments, this step may involve collecting battery-related information and vehicle operating information from the vehicle's internal communication links, such as the Controller Area Network (CAN) bus.

[0035] Among them, battery-related information describes the operating conditions of the target battery in the vehicle. Taking a low-voltage battery as an example, battery-related information may include: DC / DC converter operating status, low-voltage battery voltage range, low-voltage battery state of charge (SOC), low-voltage battery voltage, low-voltage battery output current, low-voltage battery charging and discharging current (A), low-voltage battery temperature, DC / DC converter operating current, and DC / DC converter charging current for the low-voltage battery, etc.

[0036] The DC / DC converter can be used to charge low-voltage batteries and supply power to low-voltage electrical appliances in the vehicle.

[0037] Among them, vehicle operation information describes the operation and body status of the entire vehicle, which may include, for example: vehicle identification number (VIN), data acquisition time, vehicle power mode, vehicle operating mode, vehicle speed, door status, central locking signal, remote control command, on-board diagnostics (OBD) wake-up flag, ignition key position, CAN bus communication status, etc.

[0038] The vehicle power mode is used to control the on / off of the high-voltage and low-voltage power supply circuits of the vehicle, enabling the vehicle's electrical system to operate when powered on or go into hibernation mode when powered off.

[0039] The vehicle operation mode is used to manage different operating modes of the vehicle, such as power-off hibernation, driving, and charging.

[0040] It is understood that the specific parameters included in the battery-related information and the specific parameters included in the vehicle operation information mentioned above are only examples. In actual applications, more or fewer parameters can be collected, as long as the collected parameters can support the implementation of subsequent steps.

[0041] In some embodiments, this step can be a periodically executed step. Each time battery-related information and vehicle operating information are collected, a data frame can be obtained. This data frame can record the battery-related information and vehicle operating information collected in this cycle. For example, battery-related information and vehicle operating information can be obtained from the CAN bus each cycle to obtain a data frame for that cycle.

[0042] Step 202: Determine the vehicle's operating condition based on the vehicle's operating information.

[0043] In some embodiments, the vehicle's operating conditions can be divided into: power-off operating condition, power-on operating condition, and driving operating condition. The power-on operating condition can include: driving and power-on operating condition, and power-off and power-on operating condition. The power-off operating condition can further include: power-off and no power-on operating condition, and power-off and power-on operating condition.

[0044] The following example illustrates the implementation of this step.

[0045] In some embodiments, if the vehicle speed is greater than 0 and the vehicle's overall operating mode is driving mode, the vehicle's operating condition is determined to be driving condition.

[0046] In some embodiments, if the vehicle's overall operating mode is low-voltage battery charging, the vehicle's operating condition is determined to be charging condition.

[0047] In some embodiments, if the vehicle's overall power mode is off and the vehicle's operating mode is any one of power-off, hibernation, low-voltage battery charging, or charging, the vehicle's operating condition is determined to be power-off.

[0048] In some embodiments, if the vehicle's overall power supply mode is off and the vehicle's operating mode is power-down or hibernation, the vehicle's operating condition is determined to be power-down and without power replenishment.

[0049] In some embodiments, if the vehicle's overall power mode is off and the vehicle's operating mode is charging or low-voltage battery charging, the vehicle's operating condition is determined to be a power-off and charging condition.

[0050] In some embodiments, if the vehicle's overall power mode is on and the vehicle's operating mode is low-voltage battery charging, the vehicle's operating condition is determined to be driving and charging condition.

[0051] Step 203: Detect the first type of charge anomaly of the target battery under the above operating conditions based on battery-related information and / or vehicle operating information.

[0052] In this step, the first type of power anomaly of the target battery refers to the power anomaly that occurs in the target battery under different operating conditions.

[0053] In some embodiments, the first type of charge anomaly to be detected in the target battery differs under different operating conditions. The following example, using a low-voltage battery as the target battery, illustrates the implementation of the first type of charge anomaly in low-voltage batteries under different operating conditions, as well as the implementation of this step.

[0054] Example 1: If the operating condition is driving condition, the first type of low-voltage battery charge abnormality may include: low-voltage battery not discharging abnormality; then, this step may include: If, during a period when the vehicle is under electrical load, the duration for which the output current of the low-voltage battery is less than the first current threshold is greater than the first time threshold, it is determined that an abnormality of non-discharge of the low-voltage battery under driving conditions has been detected.

[0055] Since the target battery is a low-voltage battery, the electrical load can be a low-voltage electrical load on the vehicle, such as headlights, interior lighting, air conditioning blowers, etc.

[0056] The first current threshold and the first time threshold are mainly used as the basis for judging whether the low-voltage battery has failed to supply power to the electrical load normally within a certain period of time. The first current threshold can be a value greater than or equal to 0. The specific value is not limited in this application embodiment. For example, it can be 0.1A. The first time threshold can be a value greater than 0. The specific value is not limited in this application embodiment. For example, it can be 30 minutes.

[0057] Example 2: If the operating condition is a recharging condition, the first type of power abnormality of the low-voltage battery may include: no change in battery SOC; then this step may include: If the vehicle is in a charging condition, and the change in SOC of the low-voltage battery is less than or equal to the first charge change threshold and the change in voltage of the low-voltage battery is greater than the voltage change threshold, it is determined that no abnormal change in battery SOC was detected during the charging condition.

[0058] The specific values ​​of the voltage change threshold and the first charge change threshold are not limited in this application embodiment. For example, the normal charging voltage range of some 12V low-voltage batteries is usually between 13.8V and 14.8V. Therefore, 13.8V can be used as the voltage change threshold to confirm that the charging system for charging the low-voltage battery has been started normally and is supplying power to the low-voltage battery. At this time, the first charge change threshold can be set to 0 or a value close to 0. So when the SOC change of the low-voltage battery is less than or equal to the first charge change threshold, it can be determined that there is no abnormal change in the battery SOC under the charging condition.

[0059] Example 3: If the operating condition is a power-off condition, the first type of charge abnormality of the low-voltage battery may include: high SOC and low voltage abnormality; then this step may include: If the duration of the vehicle being in a power-off state exceeds the second time threshold, and the duration of the low-voltage battery meeting the first condition exceeds the third time threshold, it is determined that a high SOC and low voltage anomaly under the power-off state has been detected. The first condition includes: the SOC of the low-voltage battery is greater than or equal to the charge threshold and the voltage of the low-voltage battery is less than or equal to the voltage threshold.

[0060] The second time threshold is set to wait for the low-voltage battery polarization to subside after the vehicle enters the power-off state. The specific value is not limited and depends on the time required for the low-voltage battery polarization to subside. For example, if the low-voltage battery polarization takes 30 minutes to subside, the second time threshold can be set to a value greater than or equal to 30 minutes.

[0061] The third time threshold is used to determine the duration for which the low-voltage battery meets the first condition. The specific value is not limited in this application embodiment, but can be, for example, 10 seconds.

[0062] The setting of the power threshold and voltage threshold is related to the relationship between the power and voltage of the low-voltage battery. The specific values ​​of the power threshold and voltage threshold are not limited in this application embodiment. For example, assuming that the low-voltage battery is a 12V lead-acid battery, when the SOC of the lead-acid battery is 80%, the resting no-load voltage is generally 12.3V to 12.4V. Then the power threshold can be set to 80% and the voltage threshold to 10.5V, so as to detect the abnormal power of the low-voltage battery with high SOC when the voltage is low.

[0063] Example 4: If the operating condition is one of power failure and no recharging, the first type of charge anomaly of the low-voltage battery may include: abnormal SOC rise; then this step may include: If the SOC of the low-voltage battery increases during the period when the vehicle is powered off and not recharged, it is confirmed that an abnormal increase in SOC has been detected under the condition of power off and not recharged.

[0064] In one possible implementation, when the vehicle's operating mode switches to power-down or sleep mode, for each frame of data collected from the CAN bus, it is first determined that the vehicle's operating mode is still in a power-down or sleep state in that frame of data to ensure that the vehicle is still in a power-down or sleep state, in other words, still in a power-down and unrecharged condition. Then, the SOC of the low-voltage battery in the current frame of data is compared with the SOC of the low-voltage battery in the previous frame of data. If the SOC of the low-voltage battery in the current frame of data is greater than the SOC of the low-voltage battery in the previous frame of data, in other words, the difference between the SOC of the low-voltage battery in the current frame of data and the SOC of the low-voltage battery in the previous frame of data is greater than 0, then it is determined that an abnormal increase in SOC under the power-down and unrecharged condition has been detected.

[0065] Example 5: If the operating condition is power-off and recharging, the first type of power abnormality of the low-voltage battery may include: frequent recharging abnormalities; then this step may include: If the vehicle is in a power-down and power-up condition, and M effective power-up events occur for the low-voltage battery in N consecutive power-down events, it is determined that frequent abnormal power-up events are detected in the power-down and power-up condition; the aforementioned N consecutive complete power-down events include the power-down events to which the current condition belongs.

[0066] Wherein, N and M are integers greater than 0, and their specific values ​​are not limited in this application embodiment. For example, N can be 5 times and M can be 3 times.

[0067] A power-down event refers to the process from when the vehicle's ignition key is turned OFF until when it is turned ON. Based on the vehicle's overall power mode and overall operating mode, a power-down event can refer to the process from when the vehicle's overall power mode is turned OFF until when it is turned ON. During this period, the vehicle's overall operating mode can be any of the following modes: power-down, hibernation, low-voltage battery charging, or charging.

[0068] Among them, an effective charging event for a low-voltage battery refers to a charging event in which the duration of a single charging operation for a low-voltage battery exceeds the fourth time threshold.

[0069] A single charging event for a low-voltage battery refers to the process from the start to the end of charging the low-voltage battery. Based on the vehicle's overall operating mode, a single charging event for a low-voltage battery refers to the process from the start of the vehicle's overall operating mode changing to low-voltage battery charging until it changes to another overall vehicle operating mode.

[0070] For example, if the vehicle's operating mode changes to power-down, a power-down event begins. If the vehicle's operating mode then changes to low-voltage battery charging, a charging event for the low-voltage battery begins. If the vehicle's operating mode changes back to power-down, the charging event for the low-voltage battery ends. If the duration of this charging event exceeds a fourth time threshold, then this charging event is a valid charging event. If the vehicle's operating mode changes back to power-on, a power-down event ends. The fourth time threshold can be a value greater than 0 seconds; its specific value is not limited in this embodiment. For example, to eliminate transient interference or signal jitter, the fourth time threshold can be set to 1 minute (i.e., 60 seconds).

[0071] The above steps use a low-voltage battery as an example for illustration. It can be understood that the low-voltage battery in the example can also be replaced by other target batteries such as power batteries, which will not be listed here.

[0072] This method determines the vehicle's operating condition based on the vehicle's operating information, and then detects the first type of charge anomaly of the target battery under the operating condition based on battery-related information and / or vehicle operating information. This enables the monitoring of abnormal changes in the charge of the target battery in the vehicle, providing a data basis for subsequent optimization of the vehicle battery control strategy and improving the control performance of the vehicle battery.

[0073] In some embodiments, such as Figure 3As shown, the method may further include: Step 301: Detect the second type of charge anomaly of the target battery based on battery-related information and / or vehicle operation information.

[0074] The first type of power anomaly of the target battery in the steps refers to the power anomaly that occurs in the target battery under any operating condition.

[0075] In some embodiments, taking a low-voltage battery as an example, the second type of power abnormality may include: SOC jump abnormality, and abnormality that does not meet the self-learning conditions.

[0076] For example, if the second type of power anomaly of the low-voltage battery includes: SOC fluctuation, this step may include: If the SOC difference of the low-voltage battery in two adjacent frames of data is greater than the first threshold, and the time interval between the acquisition times of the two adjacent frames of data is less than the first time threshold, it is determined that an abnormal SOC jump has been detected.

[0077] For example, if the second type of power anomaly of the low-voltage battery includes: failure to meet self-learning conditions, this step may include: An anomaly that does not meet the self-learning conditions is determined to be detected when any of the following conditions are met, based on battery-related information and / or vehicle operating information: Condition 1: Insufficient idle time: When the vehicle's overall operating mode is sleep mode, the acquisition time of two adjacent frames of data is greater than the first duration and less than the second duration. For example, the first duration can be 10 seconds and the second duration can be 6 hours.

[0078] Condition 2, Sleep Interference: When the vehicle's overall operating mode is sleep, the acquisition time of two adjacent frames is greater than the first duration and less than the second duration, and a target user operation is detected. For example, the first duration can be 10 seconds, and the second duration can be 6 hours. For example, the aforementioned target user operation can include, but is not limited to: door opening / closing, remote unlocking, APP remote wake-up, or charging, etc.

[0079] Condition 3, Abnormal power / voltage: When the vehicle is in sleep mode, the change in SOC of the low-voltage battery exceeds the second power change threshold, or the DC-DC converter is detected to be working, or the charging current of the low-voltage battery is detected, or the initial SOC is determined to be outside the calibrable range.

[0080] The initial SOC refers to the SOC of the low-voltage battery when the vehicle's operating mode is switched to hibernation. The calibrable range can be preset, and there is no limit to the specific range; for example, it could be (20%, 80%).

[0081] Condition 4, Environmental or system anomaly: The battery temperature of the low-voltage battery is detected to be lower than the first temperature threshold or higher than the second temperature threshold, or a serious fault code is detected, or a CAN bus communication interruption is detected.

[0082] The first and second temperature thresholds are used to determine whether the battery temperature of the low-voltage battery is within the safe temperature range of the low-voltage battery. Therefore, the specific values ​​of the first and second temperature thresholds are related to the safe temperature range of the low-voltage battery. For example, assuming that the safe temperature range of the low-voltage battery is (5℃, 45℃), the first temperature threshold can be set to 5℃ and the second temperature threshold can be set to 45℃.

[0083] When some components in a vehicle experience serious problems, the corresponding parameter values ​​in the battery-related information on the CAN bus and the vehicle's operating information can become serious fault codes. This step checks whether the parameter values ​​in the battery-related information and the vehicle's operating information are serious fault codes; if so, a serious fault code has been detected. For example: Serious fault codes related to voltage abnormalities: When the voltage of a certain device (such as a low-voltage battery) is over-voltage or under-voltage, or when the total voltage of the vehicle is over-voltage or under-voltage, the corresponding voltage parameter value can be a serious fault code. For example, if the voltage difference is too large, the corresponding voltage difference parameter value can be a serious fault code.

[0084] Temperature anomaly type serious fault codes: If the temperature of a device is too high, a high temperature / overheat alarm is required; if the temperature is too low, a low temperature alarm is required. The corresponding temperature parameter value can be a serious fault code. If the temperature difference is too large, the corresponding temperature difference parameter value can be a serious fault code. If the temperature sensor fails, the temperature sensor status parameter can be a serious fault code.

[0085] Serious fault codes related to abnormal current and charge / discharge status: Overcurrent in battery charging / discharging, output short circuit, etc. The corresponding parameter value can be a serious fault code. When the charge / discharge prohibition flag is triggered, the corresponding status parameter value can be a serious fault code.

[0086] Serious fault codes related to insulation and high voltage safety: low insulation resistance, high voltage interlock fault, relay / contactor fault. The corresponding parameter values ​​can be serious fault codes.

[0087] Serious fault codes related to communication and internal system failures: CAN communication loss / timeout, BMS internal failure, equalization circuit failure, the corresponding parameter values ​​can be serious fault codes.

[0088] In this step, the interruption of CAN bus communication can be detected based on the parameter values ​​of the CAN bus communication status in the vehicle's operating information.

[0089] The execution order of steps 301 and steps 202-203 is not restricted, as long as they are executed after step 201.

[0090] This method is relative to Figure 2 The embodiment shown can detect a second type of power anomaly based on battery-related information and / or vehicle operating information, thereby enabling the monitoring of more types of power anomalies in vehicle batteries and providing a data foundation for subsequent optimization of vehicle battery control strategies.

[0091] In some embodiments, such as Figure 4 As shown, the method may further include: Step 401: When an abnormal power level is detected (which may be a first type of abnormal power level or a second type of abnormal power level), an abnormal event record is generated. The abnormal event record may include at least one of the following information: the abnormal type of the abnormal power level, the time of occurrence of the abnormal power level, the current SOC of the target battery, the voltage of the target battery, the current of the target battery, the current operating condition of the vehicle, and snapshots of the target number of frames before and after.

[0092] In some embodiments, timestamps can be used to record the time when a power outage occurs.

[0093] In some embodiments, different identifiers can be set for different operating conditions, and the current operating condition of the vehicle can be recorded through the operating condition identifiers.

[0094] In some embodiments, since the second type of power abnormality is unrelated to the operating condition, the vehicle's current operating condition can be defaulted when generating an abnormal event record for the second type of power abnormality.

[0095] Among them, the target quantity frame data before and after refers to the target quantity frame data collected from the bus, such as the CAN bus, before and after the time of the power abnormality.

[0096] It is understandable that when the first type of power abnormality is detected in step 203 or the second type of power abnormality is detected in step 204, step 401 can be triggered to generate an abnormal event record corresponding to the power abnormality, thereby providing a structured data foundation for subsequent optimization of the vehicle battery control strategy.

[0097] Figure 5 This is a schematic flowchart of a vehicle battery state monitoring method provided in an embodiment of this application, such as... Figure 5 As shown, the method may include: Step 501: According to a preset cycle, collect one frame of bus data from the CAN bus in each cycle (corresponding to the aforementioned frame of data). This frame of bus data includes: battery-related information and vehicle operation information. Execute steps 502, 514, and 515.

[0098] Step 502: Determine the vehicle's operating condition based on the vehicle operation information in each frame of bus data.

[0099] If the vehicle is in driving condition, proceed to step 503; if it is in power replenishment condition, proceed to step 505; if it is in power-off condition, proceed to steps 507 and 509.

[0100] The implementation of this step can be referred to the corresponding description in the foregoing embodiments, and will not be repeated here.

[0101] Step 503: During the duration of the vehicle's operating condition being driving, determine whether an abnormality of battery non-discharge under driving conditions is detected. If yes, proceed to step 504; otherwise, this branch process ends.

[0102] Each cycle can trigger step 502 after collecting one frame of bus data. Step 502 determines that the vehicle is in driving condition and executes this step. If the result of this step is negative, it means that no abnormality of battery non-discharge under driving condition was detected. Then this branch process ends and waits to be triggered for execution again.

[0103] Step 504: Generate an abnormal event record for the battery not discharging.

[0104] Step 505: During the duration of the vehicle's charging condition, determine whether an abnormal change in battery SOC is detected under the charging condition. If yes, proceed to step 506; otherwise, this branch process ends.

[0105] Each cycle can trigger step 502 after collecting one frame of bus data. Step 502 determines that the vehicle is in a charging condition and executes this step. If the result of this step is negative, it means that no abnormal change in battery SOC under the charging condition was detected. Then this branch process ends and waits to be triggered for execution again.

[0106] Step 506: Generate an abnormal event record for the absence of change in battery SOC.

[0107] Step 507: After detecting that the duration of the power-down condition is greater than the second time threshold, during the duration of the power-down condition of the vehicle, determine whether a high SOC and low voltage abnormality under the power-down condition is detected. If yes, proceed to step 508; otherwise, this branch process ends.

[0108] Each cycle can trigger step 502 after collecting one frame of bus data. Step 502 determines that the vehicle is in a power-down state. If the result of this step is negative, it means that no high SOC low voltage abnormality was detected in the power-down state. Then this branch process ends and waits to be triggered again.

[0109] Step 508: Generate an abnormal event record for high SOC and low voltage anomalies.

[0110] Step 509: Determine whether the vehicle is in a power-off and power-on state. If yes, proceed to step 510; otherwise, proceed to step 511.

[0111] Since it has been determined in step 502 that the vehicle is in a power-off condition, this step can specifically determine whether the vehicle's operating mode is charging or low-voltage battery charging mode. If so, the vehicle is determined to be in a power-off and charging condition; otherwise, the vehicle is determined to be in a power-off and non-charging condition.

[0112] Step 510: Determine whether frequent abnormal power replenishment under power-down and power replenishment conditions is detected, and proceed to step 511; otherwise, this branch process ends.

[0113] If the result of this step is negative, it means that no power-down was detected and the power replenishment under the power replenishment condition is frequently abnormal. In this case, this branch of the process ends and waits to be triggered and executed again.

[0114] Step 511: Generate an abnormal event record for frequent power replenishment anomalies.

[0115] Step 512: During the period when the vehicle is in a power-down and non-power-up condition, determine whether an abnormal increase in SOC is detected under the power-down and non-power-up condition. If so, proceed to step 513. Otherwise, this branch process ends.

[0116] If the result of this step is negative, it means that no abnormal rise in SOC was detected under the condition of power-down and no power replenishment. In this case, this branch of the process ends and waits to be triggered for execution again.

[0117] Step 513: Generate an exception event record for the SOC increase anomaly.

[0118] Step 514: Detect anomalies that do not meet the self-learning conditions based on battery-related information and / or the vehicle's operating information. If anomalies that do not meet the self-learning conditions are detected, generate an anomaly event record for the anomalies that do not meet the self-learning conditions.

[0119] In this process, step 514 can be triggered after collecting one frame of bus data in each cycle. If no abnormality that does not meet the self-learning conditions is detected, the process of this branch ends and waits for the next cycle to collect one frame of bus data before continuing the detection.

[0120] Step 515: Detect SOC jump anomaly based on battery-related information and / or the vehicle's operating information. If an SOC jump anomaly is detected, generate an abnormal event record for the SOC jump anomaly.

[0121] In this process, step 515 can be triggered after collecting one frame of bus data in each cycle. If no SOC transition abnormality is detected, this branch process ends and waits for the next cycle to collect one frame of bus data before continuing the detection.

[0122] The vehicle battery status monitoring method provided in this application embodiment can significantly improve the early detection capability of SOC anomalies and avoid user misjudgment or control strategy failure due to data distortion. Furthermore, the frequent abnormal charging is focused on the ineffective charging cycles caused by battery aging, excessive static current, or insufficient DC-DC charging capacity. It can effectively trigger fault warnings, remote diagnostics, or user prompts to avoid the risk of startup failure.

[0123] Furthermore, the method provided in this application embodiment can provide high-value anomaly event inputs for after-sales diagnosis, remote early warning, and over-the-air (OTA) data analysis.

[0124] Furthermore, the method provided in this application embodiment does not require modification of the existing BMS core algorithm, and can be deployed as an independent monitoring module, which has strong compatibility and low implementation cost; Furthermore, the method provided in this application clearly focuses on the "problem discovery" stage, with clear technical boundaries, and can serve as a foundational support for subsequent SOC calibration or strategy optimization.

[0125] In summary, the method provided in this application can be integrated into the vehicle's existing electronic architecture as an independent monitoring module, providing a reliable basis for fault warning, data diagnosis and subsequent strategy optimization, and effectively enhancing the vehicle's robustness in sensing battery status and its intelligent operation and maintenance capabilities.

[0126] Figure 6 This is a schematic diagram of a vehicle battery state monitoring device provided in an embodiment of this application, such as... Figure 6 As shown, the device 600 may include: The data acquisition module 610 is used to collect battery-related information and vehicle operating information; The operating condition determination module 620 is used to determine the operating condition of the vehicle based on the vehicle's operating information. The detection module 630 is used to detect a first type of power anomaly of the target battery under the operating condition based on the battery-related information and / or the vehicle's operating information.

[0127] Figure 6 The apparatus provided in the illustrated embodiments can be used to execute the technical solutions of the method embodiments shown in this application, and its implementation principles and technical effects can be further referred to the relevant descriptions in the method embodiments.

[0128] The above should be understood Figure 6The division of the various modules in the illustrated device is merely a logical functional division. In actual implementation, they can be fully or partially integrated into a single physical entity, or they can be physically separated. These modules can be implemented entirely in software via processing element calls; they can be fully implemented in hardware; or some modules can be implemented in software via processing element calls, while others are implemented in hardware. For example, the acquisition module can be a separate processing element or integrated into a chip in the terminal device. The implementation of other modules is similar. Furthermore, these modules can be fully or partially integrated together, or they can be implemented independently. For example, the aforementioned device can be a chip or a chip module, or it can be a part of a chip or a chip module. During implementation, each step of the above method or each of the above modules can be completed through integrated logic circuits in the hardware of the processor element or through software instructions.

[0129] This application also provides a vehicle, including: a processor and a memory; wherein one or more computer programs are stored in the memory, the one or more computer programs including instructions that, when executed by the processor, cause the vehicle to perform the method provided in this application.

[0130] This application also provides a computer-readable storage medium storing a computer program that, when moved on a computer, causes the computer to execute the method provided in this application.

[0131] This application also provides a computer program product, which includes a computer program that, when run on a computer, causes the computer to execute the method provided in this application.

[0132] In this application embodiment, "at least one" refers to one or more, and "more than one" refers to two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent the existence of A alone, A and B simultaneously, or B alone. A and B can be singular or plural. The character " / " generally indicates that the preceding and following related objects are in an "or" relationship. "At least one of the following" and similar expressions refer to any combination of these items, including any combination of singular or plural items. For example, at least one of a, b, and c can represent: a, b, c, a and b, a and c, b and c, or a and b and c, where a, b, and c can be single or multiple.

[0133] Those skilled in the art will recognize that the units and algorithm steps described in the embodiments disclosed herein can be implemented using electronic hardware, computer software, or a combination of electronic hardware and software. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0134] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0135] In the several embodiments provided in this application, any function, if implemented as a software functional unit and sold or used as an independent product, can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, essentially, or the part that contributes to the prior art, or a part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0136] The above description is merely a specific embodiment of this application. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the protection scope of this application. The protection scope of this application should be determined by the protection scope of the claims.

Claims

1. A method for monitoring the battery status of a vehicle, characterized in that, include: Collect battery-related information and vehicle operating information; The operating condition of the vehicle is determined based on the vehicle's operating information; Based on the battery-related information and / or the vehicle's operating information, detect the first type of charge anomaly of the target battery under the operating condition.

2. The method according to claim 1, characterized in that, Also includes: The second type of power anomaly of the target battery is detected based on the battery-related information and / or the vehicle's operating information.

3. The method according to claim 1 or 2, characterized in that, The operating conditions include: driving conditions, and determining the vehicle's operating conditions based on the vehicle's operating information includes: When the vehicle speed is greater than 0 and the vehicle's overall operating mode is driving mode, the vehicle's operating condition is determined to be driving condition. And / or, The operating conditions include: recharging operating condition, wherein determining the vehicle's operating condition based on the vehicle's operating information includes: When the vehicle's overall operating mode is charging or low-voltage battery charging, the vehicle's operating condition is determined to be charging condition. And / or, The operating conditions include: power-off operating conditions. Determining the vehicle's operating conditions based on the vehicle's operating information includes: When the vehicle's overall power supply mode is off and the vehicle's operating mode is any one of power-off, hibernation, low-voltage battery charging, or charging, the vehicle's operating condition is determined to be power-off. And / or, The operating conditions include: power-off and power-on operating conditions. Determining the vehicle's operating conditions based on its operating information includes: When the vehicle's overall power mode is off and the vehicle's operating mode is charging or low-voltage battery charging, the vehicle's operating condition is determined to be a power-off and charging condition. And / or, The operating conditions include: a power-off and no-recharge condition. Determining the vehicle's operating condition based on its operating information includes: When the vehicle's overall power supply mode is off and the vehicle's operating mode is power-down or hibernation, the vehicle's operating condition is determined to be power-down and no power replenishment condition.

4. The method according to claim 3, characterized in that, The vehicle's operating condition is a driving condition. The step of detecting a first type of abnormal charge level in the target battery under this operating condition based on the battery-related information and / or the vehicle's operating information includes: If, during a period when the vehicle is under electrical load, the duration for which the output current of the target battery is less than a first current threshold is greater than a first time threshold, it is determined that an abnormality in battery non-discharge under driving conditions has been detected.

5. The method according to claim 3, characterized in that, If the vehicle is in a charging condition, the step of detecting the first type of power anomaly of the target battery under the condition based on the battery-related information and / or the vehicle's operating information includes: If the vehicle is in a charging condition, and the change in the SOC of the target battery is less than or equal to a first charge change threshold and the change in the voltage of the target battery is greater than a voltage change threshold, then it is determined that no abnormal change in the battery SOC was detected during the charging condition.

6. The method according to claim 3, characterized in that, The vehicle is in a powered-off operating condition. The detection of a first type of abnormal charge level in the target battery under this condition, based on battery-related information and / or the vehicle's operating information, includes: If the duration of the power-down condition is greater than the second time threshold, and the duration of the target battery satisfying the first condition exceeds the third time threshold, it is determined that a high SOC and low voltage anomaly under the power-down condition has been detected. The first condition includes: the SOC of the target battery is greater than or equal to the charge threshold and the voltage of the target battery is less than or equal to the voltage threshold.

7. The method according to claim 3, characterized in that, The step of detecting the first type of abnormal charge level of the target battery under the operating condition based on the battery-related information and / or the vehicle's operating information includes: If the target battery's SOC increases during the period when the vehicle is powered off and not recharged, it is determined that an abnormal increase in SOC has been detected under the power-off and non-recharged condition.

8. The method according to claim 3, characterized in that, The step of detecting the first type of abnormal charge level of the target battery under the operating condition based on the battery-related information and / or the vehicle's operating information includes: If the vehicle is in a power-down and power-up condition, and M effective power-up events for the target battery occur within N consecutive power-down events, it is determined that a frequent abnormality in power-up during the power-down and power-up condition has been detected; the N consecutive complete power-down events include the power-down events to which the current power-down and power-up condition of the vehicle belongs; an effective power-up event for the target battery refers to a power-up event in which the duration of a single power-up event for the target battery exceeds the fourth time threshold; N and M are both integers greater than 0.

9. The method according to claim 2, characterized in that, The second type of power anomaly includes: anomalies that do not meet self-learning conditions. The detection of the second type of power anomaly of the target battery based on the battery-related information and / or the vehicle's operating information includes: If the vehicle's overall operating mode is sleep mode, and the acquisition time of two adjacent frames of data is greater than the first duration and less than the second duration, it is determined that an anomaly that does not meet the self-learning conditions has been detected; and / or, If the vehicle's overall operating mode is sleep, the acquisition time of two adjacent frames of data is greater than the first duration and less than the second duration, and a target user operation is detected, it is determined that an anomaly that does not meet the self-learning conditions has been detected; and / or, If the vehicle's overall operating mode is sleep mode, and the target battery's SOC change exceeds the second charge change threshold, or the DC-DC converter is detected to be operating, or the target battery's charging current is detected, or the initial SOC is determined to be outside the calibrable range, or an anomaly that does not meet the self-learning conditions is detected; and / or, If the target battery temperature is detected to be lower than the first temperature threshold, or the target battery temperature is detected to be higher than the second temperature threshold, or a serious fault code is detected, or the target bus communication is interrupted, it is determined that an anomaly that does not meet the self-learning conditions has been detected. And / or, The second type of power anomaly includes: SOC jump anomaly. The detection of the second type of power anomaly of the target battery based on the battery-related information and / or the vehicle's operating information includes: If the SOC difference of the target battery in two adjacent frames of data is greater than the first threshold, and the time interval between the acquisition times of the two adjacent frames of data is less than the fifth time threshold, it is determined that an abnormal SOC jump has been detected.

10. The method according to any one of claims 1 to 9, characterized in that, Also includes: When a first type of power anomaly is detected, an anomaly event record is generated. The anomaly event record includes at least one of the following information: the anomaly type of the first type of power anomaly, the time of occurrence, the current SOC of the target battery, the voltage of the target battery, the current of the target battery, the current operating condition of the vehicle, and snapshots of the number of target frames before and after.

Images