A method of load management for a battery and a vehicle

Abstract

The application provides a load management method of a storage battery and a vehicle, and applies to the technical field of vehicle control. The method comprises the following steps: in the process of managing the storage battery, receiving state flag bits periodically sent by a sensor of the storage battery; in the case that a plurality of invalid state flag bits exist in a plurality of continuously received state flag bits, estimating the residual capacity of the storage battery to obtain an estimated residual capacity; and managing the load of the storage battery based on the estimated residual capacity. In this way, after the sensor of the storage battery fails, the load of the storage battery can be managed by using the estimated residual capacity, so as to avoid directly cutting off all loads of the storage battery, and thus the risk of engine stall of the vehicle can be reduced.

Description

Technical Field

[0001] This application relates to the field of vehicle control technology, and more specifically, to a battery load management method and a vehicle within the field of vehicle control technology. Background Technology

[0002] Currently, in order to manage the low-voltage batteries (hereinafter referred to as batteries) in vehicles, intelligent energy battery sensors (IEBS, hereinafter referred to as sensors) are usually installed in vehicles. These sensors detect and report information such as the battery's terminal voltage, current, temperature, and remaining charge to the vehicle. They also report status flags representing the sensor's own state, enabling the vehicle to manage the battery.

[0003] When managing low-voltage batteries, if the status flag indicates sensor failure, the usual practice is to disconnect the battery load. However, this method increases the risk of the vehicle stalling. Summary of the Invention

[0004] This application provides a battery load management method and a vehicle, which can reduce the risk of vehicle stalling.

[0005] Firstly, a load management method for a storage battery is provided, the method comprising: The sensor receives the status flag bits periodically sent by the battery. If multiple failure status flags are present among the multiple status flags received consecutively, the remaining power of the battery is estimated to obtain the estimated remaining power. The load of the battery is managed based on the estimated remaining power.

[0006] In this embodiment, during battery management, status flags periodically sent by the battery's sensors are received. If multiple failure status flags are among the consecutively received status flags, the remaining battery charge is estimated to obtain an estimated remaining charge. The battery load is then managed based on this estimated remaining charge. Therefore, even after a battery sensor malfunctions, the estimated remaining charge allows for load management of the battery, avoiding the direct disconnection of all battery loads and thus reducing the risk of vehicle stalling.

[0007] Optionally, estimating the remaining battery power when multiple failure status flags exist among the continuously received status flags, to obtain an estimated remaining battery power, includes: If multiple consecutive received status flag bits are all failure status flag bits, a first duration is determined, the first duration being the duration from the first receipt of the failure status flag bit to the last receipt of the failure status flag bit; if the first duration is greater than or equal to a first duration threshold, the estimated remaining power is estimated. And / or, determine the number of failure status flag bits included in the plurality of status flag bits received continuously within a preset time period; if the number is greater than or equal to a preset number threshold, estimate the estimated remaining power, wherein the number threshold is an integer greater than 1.

[0008] Optionally, estimating the estimated remaining power when the first duration is greater than or equal to the first duration threshold includes: calibrating the battery when the first duration is greater than or equal to the first duration threshold; and estimating the estimated remaining power if a status flag bit as a failure status flag bit is received after the calibration of the battery is completed.

[0009] Optionally, estimating the estimated remaining power when the quantity is greater than or equal to a preset quantity threshold includes: when the quantity is greater than or equal to the quantity threshold, if it is determined that a failure status flag bit is received within the observation period, then estimating the estimated remaining power, wherein the observation period is a time period starting from the current time.

[0010] Optionally, the method further includes: if the number is greater than or equal to the number threshold, and it is determined that no failure status flag bit is received within the observation period, then outputting a first prompt message, wherein the first prompt message indicates that the sensor connection is abnormal.

[0011] Optionally, the step of estimating the estimated remaining power if a failure status flag bit is received within the observation period includes: estimating the estimated remaining power if multiple consecutive failure status flag bits are received within the observation period.

[0012] Optionally, the method includes: if the number is greater than or equal to the number threshold, and if it is determined that multiple status flag bits received consecutively within the observation period are all valid status flag bits, then determining a second duration, the second duration being the duration from the first reception of a valid status flag bit to the last reception of a valid status flag bit; if the second duration is greater than or equal to a second duration threshold, clearing the number to zero; and / or, if the number is greater than or equal to the number threshold, and if a sensor restart is detected, then clearing the number to zero when a status flag bit that is a valid status flag bit is received.

[0013] Optionally, after managing the battery load based on the estimated remaining power, the method further includes: determining a third duration if multiple consecutively received status flag bits are all valid status flag bits, the third duration being the duration from the first receipt of a valid status flag bit to the last receipt of a valid status flag bit; managing the battery load based on the actual remaining power sent by the sensor if the third duration is greater than or equal to a third duration threshold; and / or, after detecting a sensor restart, managing the battery load based on the actual remaining power if a status flag bit that is a valid status flag bit is received.

[0014] Optionally, the valid status flag bit is a valid status flag bit that indicates that the error of the sensor is less than 10%.

[0015] Secondly, a load management device for a storage battery is provided, the device comprising: The receiving module is used to receive the status flag bits periodically sent by the battery's sensors; An estimation module is used to estimate the remaining power of the battery when multiple failure status flags are present among the multiple status flags received consecutively, so as to obtain an estimated remaining power. The management module is used to manage the load of the battery based on the estimated remaining power.

[0016] Thirdly, a vehicle is provided, the vehicle comprising: Memory, used to store executable program code; A processor is configured to call and run the executable program code from the memory, causing the vehicle to perform the method in any possible implementation of the first aspect described above.

[0017] Fourthly, a program product is provided, comprising: executable program code, which, when run on a vehicle, causes the vehicle to perform the method in any possible implementation of the first aspect described above.

[0018] Fifthly, a readable storage medium is provided that stores executable program code, which, when run on a vehicle, causes the vehicle to perform the method in any possible implementation of the first aspect described above. Attached Figure Description

[0019] Figure 1 This is a flowchart illustrating the steps of a battery load management method provided in an embodiment of this application. Figure 2 This is a schematic flowchart of a battery load management method provided in an embodiment of this application; Figure 3 This is a schematic diagram of the structure of a load management device for a storage battery provided in an embodiment of this application; Figure 4 This is a schematic diagram of the structure of a vehicle provided in an embodiment of this application. Detailed Implementation

[0020] The technical solutions in this application will be clearly and thoroughly described below with reference to the accompanying drawings. In the description of the embodiments of this application, unless otherwise stated, " / " means "or," for example, A / B can mean A or B. "And / or" in the text is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, and B existing alone. Furthermore, in the description of the embodiments of this application, "multiple" refers to two or more than two.

[0021] Hereinafter, the terms "first" and "second" are used for descriptive purposes only and should not be construed as implying or suggesting relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of that feature.

[0022] To supply power to various low-voltage loads in a vehicle, a battery is installed. The core function of the battery is to supply power to low-voltage loads such as the ignition system, instrument panel, central control screen, headlights, and windshield wipers when the engine or high-voltage power system is not running. It is an essential component to ensure the normal operation of the vehicle.

[0023] With the continuous development of vehicle technology, low-voltage loads in vehicles are increasing. In order to better manage the battery, IEBS is installed in the vehicle. IEBS can detect and report battery parameters such as terminal voltage, current, temperature and remaining charge, as well as status flag bits that represent the status of the sensors themselves, to the controller in the vehicle so that the controller can manage the battery.

[0024] The status flag typically has four values: 0, 1, 2, and 3. When the status flag is 0, it indicates that the sensor has not yet completed learning of the battery, and the error is greater than 15%. When the status flag is 1, it indicates that the sensor's error is less than 15%. When the status flag is 2, it indicates that the sensor's error is less than 10%. When the status flag is 3, it indicates that the sensor has failed, and the battery parameters reported by the sensor are failure information. For ease of description of the technical solution provided in this application, the status flag with a value of 3 will be referred to as the failure status flag, and the status flags with values ​​of 1 and 2 will be referred to as the valid status flags.

[0025] Currently, when the status flag reported by the sensor is a failure status flag, the usual practice is to directly determine that the sensor has failed, cut off all loads on the battery, and stop the battery from supplying power to low-voltage loads such as the ignition system, instrument panel, central control screen, headlights and wipers. This method may cause the vehicle to stall, which increases the risk of the vehicle stalling.

[0026] To address the aforementioned technical problems, this application provides a battery load management method. The method involves receiving status flags periodically sent by a sensor. When multiple status flags received consecutively include multiple failure status flags, a sensor failure is determined. At this point, the remaining battery power is estimated, and the battery load is managed based on this estimated remaining power. By managing the battery load using the estimated remaining battery power when a sensor failure is determined, directly cutting off all battery load can be avoided, thereby reducing the risk of vehicle stalling.

[0027] The method provided in this application is executed by a controller in a vehicle connected to sensors for managing the battery. The controller may be an Electronic Control Unit (ECU), Domain Control Unit (DCU), Vehicle Control Unit (VCU), Body Control Module (BCM), etc., but is not limited to these.

[0028] See Figure 1 , Figure 1This is a flowchart illustrating the steps of a battery load management method provided in an embodiment of this application. Figure 1 As shown, the method may include the following steps: Step 101: Receive the status flag bits periodically sent by the battery's sensors.

[0029] In this embodiment, the sensor and controller are communicatively connected. When the sensor and controller are powered on and in operation, the sensor continuously monitors parameters such as the battery's terminal voltage, current, and temperature, and calculates the remaining battery charge, also known as the State of Charge (SOC). Simultaneously, the sensor can determine its own status in real time to generate a status flag. The sensor periodically sends the battery's terminal voltage, current, and temperature, as well as the remaining charge and status flag, to the controller.

[0030] For example, the sensor's detection cycle is 100 milliseconds. The sensor can send a data packet to the controller every 100 milliseconds. This data packet includes the sensor's most recently detected terminal voltage, current, and temperature, as well as the calculated remaining battery power and a determined status flag. Correspondingly, the controller can receive the data packets periodically sent by the sensor, and parse each data packet to obtain the battery's terminal voltage, current, and temperature, as well as the remaining battery power and status flag. In this way, the controller can receive the continuous status flags periodically sent by the sensor.

[0031] It should be understood that the data packets sent by the sensor to the controller may include, but are not limited to, terminal voltage, current, temperature, remaining battery power, and status flags. The specific method and process by which the sensor sends the above battery parameters to the controller can be set according to actual needs, and this embodiment does not impose any restrictions on this.

[0032] Step 102: If multiple failure status flags are present among the multiple status flags received consecutively, estimate the remaining battery power to obtain the estimated remaining power.

[0033] If multiple failure status flags are received consecutively among multiple status flags, it indicates that the sensor is likely to be faulty or malfunctioning.

[0034] In this embodiment, during the process of receiving the status flag bits continuously sent by the sensor, the controller can count the continuous status flag bits sent by the sensor to determine whether there are multiple failure status flag bits among the multiple status flag bits received continuously. If it is determined that there are multiple failure status flag bits among the multiple status flag bits received continuously, then the sensor is determined to be faulty.

[0035] For example, the controller can determine that the sensor is likely faulty if the number of failure status flags among multiple status flags received consecutively within a preset time period exceeds a preset upper limit. For instance, the preset time period might be 2 hours, and the preset upper limit might be 10. Using the example above, the controller receives a status flag every 100 milliseconds. Upon receiving each status flag, if the status flag is 3, it can be determined that the received status flag is a failure status flag. Upon the first determination of a failure status flag, the controller can set a count value to 1 and start timing, then continue receiving status flags from the sensor. During the timing process, each time a received status flag is determined to be a failure status flag, the count value is incremented by 1. When the timing period reaches the preset time of 2 hours, the count value is compared with the preset upper limit of 10. If the count value is greater than or equal to the upper limit of 10, the sensor is determined to be faulty. Conversely, if the count value is less than the upper limit of 10 when the timing period reaches the preset time of 2 hours, the sensor is determined not to be faulty.

[0036] In this embodiment, when the controller determines that the sensor has failed, it can determine that the remaining power sent by the sensor is the failure data. At this time, the remaining power of the battery can be estimated, and the estimated remaining power is the estimated remaining power.

[0037] In one implementation, a battery mapping table can be pre-stored in the controller. This mapping table stores the mapping relationship between the battery's terminal voltage, temperature, and open-circuit voltage, which has been pre-calibrated experimentally. Simultaneously, a battery self-discharge rate model can be pre-stored in the controller. This model is used to estimate the battery's remaining capacity based on its open-circuit voltage. During the estimation of the battery's remaining capacity, the controller can acquire the most recently received valid terminal voltage and temperature data from the sensors. As described above, the controller stores each received data packet. When acquiring the most recently received valid terminal voltage and temperature data, it can determine from the pre-stored data packets the most recently received packet containing a valid status flag, and use the terminal voltage and temperature data from that packet as the most recently received valid terminal voltage and temperature.

[0038] After obtaining the most recently received valid terminal voltage and temperature, the corresponding open-circuit voltage is determined by looking up the corresponding open-circuit voltage in the mapping table based on the terminal voltage and temperature. This found open-circuit voltage is then used as the current open-circuit voltage of the battery. Next, the open-circuit voltage is substituted into the self-discharge rate model, and the remaining battery capacity is estimated using the self-discharge rate model. This remaining capacity is the estimated remaining battery capacity.

[0039] It should be understood that the above are merely illustrative examples, and specific methods for estimating the remaining power of a battery may include, but are not limited to, the examples above.

[0040] Step 103: Manage the battery load based on the estimated remaining power.

[0041] In this embodiment, after obtaining the estimated remaining battery power, the controller can manage the battery load based on the estimated remaining power. For example, when the estimated remaining power is lower than a preset power threshold, the controller can cut off non-critical loads on the battery, allowing the battery to supply power only to critical loads. For instance, regarding the battery load, loads that do not affect normal vehicle operation, such as air conditioning, seats, and heaters, can be classified as non-critical loads, while loads that affect normal vehicle operation, such as ECUs, DCUs, and VCUs, can be classified as critical loads. The preset power threshold is, for example, 20%. During the process of managing the battery load based on the estimated remaining power, the controller compares the estimated remaining power with the power threshold. When the estimated remaining power is less than the power threshold, the controller controls the battery to stop supplying power to non-critical loads while maintaining power supply to critical loads. Conversely, when the estimated remaining power is greater than or equal to the power threshold, the controller controls the battery to supply power to both non-critical and critical loads simultaneously.

[0042] If the sensor is confirmed to be functioning correctly, the battery parameters transmitted by the sensor can be considered valid. In this case, the controller manages the battery load using conventional management methods and can manage the battery load based on the remaining battery power transmitted by the sensor.

[0043] It should be understood that the above are merely illustrative examples, and the specific method for managing the battery load is based on estimating the remaining power capacity.

[0044] In this embodiment, during battery management, status flags periodically sent by the battery's sensors are received. If multiple failure status flags are among the consecutively received status flags, the remaining battery charge is estimated to obtain an estimated remaining charge. The battery load is then managed based on this estimated remaining charge. Therefore, even after a battery sensor malfunctions, the estimated remaining charge allows for load management of the battery, avoiding the direct disconnection of all battery loads and thus reducing the risk of vehicle stalling.

[0045] Optionally, in the event of a sensor failure, while managing the battery load based on an estimated remaining charge, the controller can also control the vehicle to output an alarm message to notify the user of the sensor malfunction and prompt the user to take appropriate action. For example, if multiple failure status flags are detected among consecutively received status flags, the controller can send a first notification to the vehicle's in-vehicle display screen, causing the display screen to show an alarm message such as "Battery sensor failure, please contact after-sales service."

[0046] It should be understood that the above are merely illustrative examples, and the specific methods for outputting alarm information may include, but are not limited to, the examples above.

[0047] In practical applications, sensors connect to the controller via a Local Interconnect Network (LIN) bus, which has connectors. Vibrations during vehicle operation may cause these connectors to loosen. When connectors are loose, the various battery parameters sent by the sensors to the controller fluctuate significantly, leading the controller to misjudge battery failure. Following this misjudgment, the user will then seek compensation from the vehicle manufacturer.

[0048] In the embodiments of this application, the following are adopted: Figure 1 The method described can output alarm messages to alert users in the event of sensor failure, reducing the probability of false alarms. A lower false alarm rate can reduce user claims against automakers, thus lowering after-sales costs. Furthermore, alerting users of sensor failures via alarm messages facilitates rapid fault location during after-sales repairs, improving repair efficiency.

[0049] Optionally, step 102 may include: If multiple consecutive status flags are received as failure status flags, a first duration is determined. The first duration is the duration from the first receipt of the failure status flag to the last receipt of the failure status flag. If the first duration is greater than or equal to the first duration threshold, the estimated remaining power is obtained.

[0050] In one implementation, when the controller determines whether a sensor is faulty based on continuously received status flags, it can determine that the sensor is faulty if multiple continuously received status flags are continuously in the form of a faulty status flag and the duration reaches a first duration threshold.

[0051] For example, the sensor sends a status flag to the controller every 100 milliseconds. During the process of receiving the status flags periodically sent by the sensor, the controller starts timing when it first determines that the received status flag is a failure status flag. After timing begins, if it is determined that the received status flag continues to be a failure status flag, it is determined that a failure status flag is continuously being received, and timing continues. If it is determined that the received status flag continues to be a valid status flag, timing stops, and the timing duration is taken as the first duration. During timing, the first duration is compared with a first duration threshold, for example, 10 minutes. If the comparison determines that the first duration is greater than or equal to the first duration threshold, the sensor is determined to have failed, and then the remaining battery power is estimated to obtain the estimated remaining battery power.

[0052] Furthermore, after the first determination that the received status flag is a failure status flag and the start of timing, if the timing duration (i.e. the first duration) is less than the first duration threshold, and the received status flag is determined to be a valid status flag, then the timing is stopped and the timing duration is cleared to zero.

[0053] Alternatively, the controller records the reception time of each status flag bit during the periodic transmission of status flag bits from the sensor. After the first received status flag bit is determined to be a failure status flag bit, for each subsequent received status flag bit that is also a failure status flag bit, the time difference between the reception time of the currently received failure status flag bit and the reception time of the first received failure status flag bit is calculated. This time difference is used as a first duration. The first duration is compared with a first duration threshold. If the first duration is greater than or equal to the first duration threshold, the sensor is determined to be faulty. Then, the remaining battery power is estimated to obtain the estimated remaining battery power.

[0054] Furthermore, after the first determination that the received status flag is a failure status flag, if the first duration is less than the first duration threshold, and if the received status flag is determined to be a valid status flag, then the previously received failure status flag is cleared.

[0055] It should be understood that the above are merely illustrative examples, and the specific methods for determining the first duration may include, but are not limited to, the examples above.

[0056] In practical applications, the more failure status flags a sensor sends and the longer they last, the greater the probability of sensor failure.

[0057] In this embodiment of the application, when multiple consecutive received status flag bits are continuously in the state of failure and the duration (i.e. the first duration) reaches the first duration threshold, the sensor is determined to be faulty. This can reliably and accurately determine whether the sensor is faulty and reduce the probability of misjudgment.

[0058] Optionally, if the first duration is greater than or equal to a first duration threshold, the remaining battery capacity is estimated to obtain the estimated remaining capacity, including: The battery is calibrated if the first duration is greater than or equal to the first duration threshold. After the battery calibration is completed, if a status flag indicating a failure is received, the estimated remaining power can be obtained.

[0059] In one implementation, if multiple consecutive received status flags remain as failure status flags and the first duration is greater than or equal to a first duration threshold, the controller can first calibrate the battery. After completing the battery calibration, if it is determined that the received status flags continue to be failure status flags, it is determined that the battery has likely failed, and the remaining battery capacity can then be estimated.

[0060] For example, the calibration method could be to charge the battery once. If the controller determines that the received status flag bit remains a failure status flag bit and the first duration is greater than or equal to a first duration threshold, it can control the generator or power battery in the vehicle (hybrid vehicle) to charge the battery once, thereby completing one calibration of the battery. After completing one calibration of the battery, the controller continues to receive status flag bits periodically sent by the sensor. If it determines that the received status flag bit remains a failure status flag bit, it can determine that the sensor has failed.

[0061] For example, the calibration method may involve controlling the battery to rest for a preset resting time. If the controller determines that the received status flag bit remains a failure status flag bit and the first duration is greater than or equal to a first duration threshold, it may control the vehicle to shut off and disconnect the battery from all loads, allowing the battery to rest for the preset resting time (e.g., 4 hours). After the preset resting time, the controller continues to receive status flag bits from the sensors. If the controller determines that the received status flag bit remains a failure status flag bit, it may determine that the sensor has failed.

[0062] Furthermore, after completing a battery calibration, the controller can determine that the sensor has not failed if it confirms that the received status flag has become a valid status flag.

[0063] It should be noted that battery calibration can be performed while the vehicle is starting or stopping, as long as the battery calibration can be completed.

[0064] The above are merely illustrative examples; specific methods for calibrating batteries may include, but are not limited to, the examples described above.

[0065] In this embodiment of the application, when the received status flag bit is continuously a failure status flag bit and the duration (i.e., the first duration) reaches the first duration threshold, the battery is calibrated. After the calibration is completed, if the received status flag bit is again determined to be a failure status flag bit, the sensor is determined to be faulty. After reliably determining that the sensor is faulty, the battery load can be managed based on the estimated remaining power, which can reduce the probability of misjudgment and improve the reliability of the vehicle.

[0066] Optionally, if multiple failure status flags exist among the continuously received status flags, the remaining battery capacity is estimated to obtain the estimated remaining capacity, including: Determine the number of failure status flags included in multiple status flags received consecutively within a preset time period; If the quantity is greater than or equal to a preset quantity threshold, the estimated remaining power is obtained. The quantity threshold is an integer greater than 1.

[0067] In one implementation, during the process of determining whether a sensor has failed based on multiple consecutively received status flags, the controller can count the number of failure status flags among the multiple consecutive status flags received within a preset time period. If the number of failure status flags is greater than or equal to a preset threshold, the sensor is determined to have failed, and the estimated remaining battery power is obtained. The threshold is an integer greater than 1, such as 2, 3, 4, or 5.

[0068] For example, the preset time period can be a time period of a preset duration ending at the current time. For instance, if the preset duration is 24 hours, then the preset time period is the period within the most recent 24 hours ending at the current time. During the process of receiving status flags periodically sent by the sensor, the controller records each received status flag and performs a statistical analysis every 24 hours for all recorded status flags. During this statistical analysis, it retrieves all status flags received within the most recent 24 hours and determines the number of failed status flags among them. Then, it compares the statistically obtained number with a preset threshold. If the statistically obtained number is greater than or equal to the threshold, the sensor is determined to be faulty, and the estimated remaining battery power is then calculated.

[0069] Conversely, if the number obtained from the statistics is less than the preset threshold, it is determined that the battery has not failed, and the remaining power of the battery is not estimated. Instead, the remaining power sent by the sensor is used directly to control the battery load.

[0070] For example, the preset time period can be a time period between a preset start time and an end time. For instance, the preset start time is 00:00:00 every day, and the preset end time is 24:60:60 every day, meaning the preset time period is one day. During the process of receiving status flags periodically sent by the sensor, the controller records each received status flag. At 24:60:60 every day, it can retrieve all the status flags recorded that day and then count the number of failed status flags among all the status flags recorded that day. Then, it compares the counted number with a preset number threshold. If the counted number is greater than or equal to the number threshold of 2, it determines that the sensor has failed, and then estimates the remaining battery power.

[0071] Conversely, if the number obtained from the statistics is less than the preset threshold, it is determined that the battery has not failed, and the remaining power of the battery is not estimated. Instead, the remaining power sent by the sensor is used directly to control the battery load.

[0072] It should be understood that the above are merely illustrative examples, and the specific form of the preset time period may include, but is not limited to, the examples above.

[0073] In this embodiment, the number of failure status flags included in a plurality of status flags received consecutively within a preset time period is determined. If the number is greater than or equal to a preset threshold, the sensor is determined to have failed. This allows for a more accurate determination of sensor failure even when failure status flags are received intermittently.

[0074] Optionally, when the quantity is greater than or equal to a preset quantity threshold, the step of estimating the remaining power may include: If the number is greater than or equal to the number threshold, and it is determined that a failure status flag is received within the observation period, the estimated remaining power can be obtained. The observation period is the time period starting from the current time.

[0075] In one implementation, if the number of failure status flag bits received within a preset time period is greater than or equal to a number threshold, the system can continue to judge the status flag bits received later. If it is determined that the subsequent received status flag bits include failure status flag bits, then the sensor is determined to be faulty.

[0076] Based on the above example, when the preset time period is a 24-hour period ending at the current time (i.e., the preset duration), the observation time period is the 1-hour period starting at the current time, i.e., 1 hour after the current time. If the number of failure status flags received in the 24 hours before the current time is greater than or equal to the number threshold, the system continues to receive status flags sent by the sensor. If it is determined that one or more failure status flags are among the multiple status flags received within 1 hour after the current time, the sensor is determined to have failed, and the estimated remaining battery power is obtained.

[0077] Conversely, if the number of failure status flags received in the 24 hours prior to the current moment is greater than or equal to the number threshold, the system continues to receive status flags sent by the sensor. If it is determined that there are no failure status flags among the multiple status flags received within one hour after the current moment, the sensor is determined to be not faulty, and the remaining power sent by the sensor is used to manage the battery load.

[0078] Referring to the above example, when the preset time period is a time interval between a preset start time and end time (e.g., 1 day), the duration of the observation period is, for example, 1 hour. At 24:60:60 each day, if the number of failure status flags received within the day is greater than or equal to a threshold, the system continues to receive status flags sent by the sensor. After 1 hour (i.e., 1:00:00), if it is determined that one or more failure status flags are among all the status flags received within 1 hour, then the sensor is determined to have failed, and the estimated remaining battery power can be calculated.

[0079] Conversely, if after one hour it is determined that there is no failure status flag among all the status flags received within one hour, then it is determined that the sensor has not failed, and the remaining power sent by the sensor is used to manage the battery load.

[0080] In this embodiment of the application, if the number of failure status flag bits received within a preset time period is greater than or equal to a number threshold, and it is determined that a failure status flag bit is received within the observation time period, then the sensor is determined to be faulty, which can further improve the reliability of the judgment result.

[0081] Optionally, the method may further include: If the number is greater than or equal to the number threshold, and it is determined that no failure status flag bit is received within the observation period, the first prompt message is output, which indicates that the sensor connection is abnormal.

[0082] In one implementation, if the number of failure status flag bits received within a preset time period is greater than or equal to a number threshold, the system continues to judge the status flag bits received within the observation time period. If it is determined that there are no failure status flag bits among the consecutive multiple status flag bits received within the observation time period, it is determined that the sensor may have a connection abnormality, that is, the connector may be loose.

[0083] Based on the above example, when the preset time period is a time interval between a preset start time and end time (e.g., 1 day), the duration of the observation period is, for example, 1 hour. At 24:60:60 each day, if the number of failure status flags received within the day is greater than or equal to a threshold, the system continues to receive status flags sent by the sensor. After 1 hour (i.e., 1:00:00), if it is determined that there are no failure status flags among all the status flags received within 1 hour, then it is determined that the sensor connection is abnormal, i.e., the connector may be loose, causing the sensor to be unable to send battery parameters normally.

[0084] At this point, the controller can instruct the vehicle to output a first prompt message to notify the user of the sensor connection, enabling the user to take relevant measures. For example, if it is determined that multiple failure status flags exist among the multiple status flags received consecutively, the controller can send a second notification to the vehicle's onboard display screen, causing the onboard display screen to display the first prompt message, such as "Battery sensor connection abnormal, please contact after-sales service."

[0085] It should be understood that the above are merely illustrative examples, and the specific driving instructions for the first prompt may include, but are not limited to, the examples above.

[0086] In practical applications, when the sensor connection is abnormal, the sensor may send intermittent failure status flags to the controller. The number of failure status flags sent may be greater than or equal to the number threshold within a preset time period, but the failure status flags will not be sent again within the observation period.

[0087] In this embodiment of the application, if the number of failure status flag bits sent by the sensor within a preset time period is greater than or equal to a number threshold, and no failure status flag bits are received within the subsequent observation time period, it is determined that the sensor connection is abnormal. At this time, a first prompt message indicating the sensor connection abnormality is output, which can promptly notify the user when the sensor connection is abnormal.

[0088] In cases where a sensor connection malfunction is detected, and a battery malfunction is determined based on the battery parameters sent by the sensor (e.g., low battery power), the alarm information indicating a battery malfunction can be masked while outputting the first prompt message to prevent false alarms.

[0089] Furthermore, if a sensor connection malfunction is detected, protective measures related to battery malfunctions can be disabled. For example, if a battery malfunction prevents the vehicle from starting and charging, this protection can be activated if a sensor connection malfunction is detected, allowing the vehicle to start and charge normally.

[0090] Optionally, after determining the number of failure status flags included in the multiple status flags received continuously within a preset time period, if the number is less than the number threshold, it can be determined that the sensor is fault-free. At this time, no alarm or prompt information is output, and the battery load can be managed normally using the battery parameters sent by the sensor.

[0091] Optionally, if it is determined that a failure status flag bit is received during the observation period, an estimated remaining power is obtained, including: If multiple consecutive failure status flags are received within the observation period, the estimated remaining power can be obtained.

[0092] In one implementation, if the number of failure status flag bits received within a preset time period is greater than or equal to a number threshold, the system can continue to judge the status flag bits received in the subsequent observation time period. If it is determined that multiple consecutive failure status flag bits are received within the observation time period, the sensor is determined to be faulty.

[0093] Based on the above example, when the preset time period is a 24-hour period ending at the current time (i.e., the preset duration), the observation period is the one-hour period starting at the current time. If the number of failure status flags received within the 24 hours prior to the current time is greater than or equal to a threshold, the system continues to receive status flags from the sensor. If multiple consecutive failure status flags are received within the one-hour period following the current time, the sensor is considered faulty, and the estimated remaining battery power is obtained.

[0094] Conversely, if the number of failure status flags received in the 24 hours prior to the current moment is greater than or equal to the number threshold, the status flags sent by the sensor continue to be received. If it is determined that there are no time-sensitive status flags within 1 hour after the current moment, or if failure status flags are received intermittently (i.e., the received failure status flags are not continuous), then the sensor is determined to be faulty and the estimated remaining power is obtained.

[0095] Alternatively, if the number of failure status flags received within 24 hours prior to the current moment is greater than or equal to a certain threshold, the sensor continues to receive status flags. If multiple consecutive failure status flags are received within one hour after the current moment and the number of failure status flags exceeds a preset limit, the sensor is determined to have failed, and the estimated remaining battery power is obtained.

[0096] In this embodiment of the application, if the number of failure status flag bits sent by the sensor within a preset time period is greater than or equal to a number threshold, and if consecutive failure status flag bits are received within a subsequent observation time period, the sensor is determined to be faulty, thus obtaining a more accurate determination of whether the sensor is faulty.

[0097] Optionally, the method may further include: If the number is greater than or equal to the number threshold, and it is determined that multiple status flag bits received consecutively within the observation period are all valid status flag bits, then a second duration is determined. The second duration is the duration from the first valid status flag bit received to the last valid status flag bit received. If the second duration is greater than or equal to the second duration threshold, the number is cleared to zero. And / or, if a sensor restart is detected when the quantity is greater than or equal to the quantity threshold, the quantity will be cleared to zero when a status flag bit that is valid is received.

[0098] In one implementation, if the number of failure status flag bits received within a preset time period is greater than or equal to a number threshold, the status flag bits received within the subsequent observation time period can be further judged. If it is determined that multiple status flag bits received consecutively within the observation time period are all valid status flag bits, then a second duration from the first valid status flag bit received to the last valid status flag bit received is determined. If the second duration is greater than or equal to the second duration threshold, the number is cleared to zero, and the sensor is determined to be fault-free and valid.

[0099] For example, if the second duration threshold is 10 minutes, and the preset time period is within a 24-hour period ending at the current time (i.e., the preset duration), the observation time period is within one hour starting at the current time. If the number of failure status flags received within the 24 hours prior to the current time is greater than or equal to the threshold, the system continues to receive status flags from the sensor. Within one hour after the current time, timing begins when the first valid status flag is received and ends when the last valid status flag is received; this timing duration is the second duration. Afterward, if the second duration is greater than or equal to the second duration, the sensor is determined to be fault-free and effective. If the sensor is determined to be fault-free and effective, the number of failure status flags recorded within the preset time period can be cleared to zero, equivalent to no failure status flags being received within the preset time period.

[0100] Optionally, if the number of failure status flag bits received within a preset time period is greater than or equal to a number threshold, and multiple status flag bits received consecutively within the observation time period are all valid status flag bits (i.e., valid status flag bits with a status value of 2), and the second duration is greater than or equal to a second duration threshold, the number can be cleared to zero, thus determining that the sensor is fault-free and valid.

[0101] It is understandable that when the duration of the valid status flag exceeds a certain duration (i.e., the second duration threshold), it can be determined that the sensor fault may have been recovered, and the battery parameters can be reliably detected and sent to the controller.

[0102] In one implementation, if the number of failure status flag bits received within a preset time period is greater than or equal to a number threshold, and a sensor restart is detected, the status flag bits sent after the sensor restart can be further judged. If it is determined that the status flag bits sent after the sensor restart are valid status flag bits, the number is cleared to zero, and the sensor is determined to be fault-free and valid.

[0103] Alternatively, if the number of failure status flags received within a preset time period is greater than or equal to the number threshold, and a sensor restart is detected, the status flags sent after the sensor restart can be further judged. If it is determined that the status flags sent after the sensor restart are valid status flags indicating that the sensor error is less than 10% (i.e., valid status flags with a status value of 2), the number is cleared to zero, and the sensor is determined to be fault-free and valid.

[0104] Sensor restarts may be caused by a vehicle restart or by the user manually controlling the sensor restart. The specific methods that cause the sensor to restart may include, but are not limited to, the examples mentioned above.

[0105] It is understandable that if a valid status flag is received after the sensor restarts, it can be determined that the sensor has eliminated any possible faults through the restart.

[0106] In this embodiment of the application, if the number of failure status flag bits received within a preset time period is greater than or equal to a number threshold, and if it is determined that the second duration of the valid status flag bits continuously received within the observation time period is greater than or equal to a second duration threshold, the sensor is determined to be fault-free and valid. After the sensor fault is eliminated, the pre-recorded failure status flag bits can be cleared in a timely manner to avoid the pre-recorded failure status flag bits causing subsequent misjudgments of sensor faults.

[0107] Similarly, if the number of failure status flags received within a preset time period is greater than or equal to the number threshold, and a sensor restart is detected, the sensor is determined to be fault-free and valid when a status flag that is a valid status flag is received. After the sensor fault is cleared, the pre-recorded failure status flags can be cleared in a timely manner to avoid the pre-recorded failure status flags causing subsequent misjudgments of sensor faults.

[0108] It is understandable that compared to an effective status flag with a characterization error of less than 15% (i.e., an effective status flag with a status value of 1), a sensor with an effective status flag with a characterization error of less than 10% has higher reliability and accuracy. Therefore, when the sensor is determined to be fault-free and effective with a status flag with a characterization error of less than 10%, the number of failure status flags can be cleared to zero with relatively reliable and accurate confirmation of the sensor's fault-free status. This can improve the reliability and accuracy of battery management processes.

[0109] Optionally, after step 103, the method may further include: If multiple consecutive status flags are received as valid status flags, a third duration is determined. The third duration is the duration from the first valid status flag received to the last valid status flag received. If the third duration is greater than or equal to the third duration threshold, the battery load is managed based on the actual remaining power transmitted by the sensor. And / or, after detecting a sensor restart, if a status flag bit that is valid is received, the battery load is managed based on the actual remaining power.

[0110] In one implementation, after managing the battery load using an estimated remaining charge, the system can continue to receive status flags from sensors and determine whether each flag is a valid status flag. If multiple consecutive status flags are received as valid status flags (i.e., valid status flags are continuously received), a third duration is determined from the first received valid status flag to the last received valid status flag. Then, the third duration is compared to a third duration threshold. If the third duration is greater than or equal to the third duration threshold, it is determined that the sensor fault has been eliminated and the battery parameters sent by the sensor are valid. Furthermore, the battery load can be managed based on the remaining charge (i.e., the actual remaining charge) sent by the sensor.

[0111] Alternatively, after managing the battery load using estimated remaining power, the system can continue to receive status flags from the sensor and determine if they are valid. If multiple consecutive received status flags are valid (indicating sensor error is less than 10%, i.e., valid status flags with a value of 2), a third duration is determined and compared to a third duration threshold. If the third duration is greater than or equal to the third duration threshold, it is determined that the sensor fault has been eliminated and the battery parameters sent by the sensor are valid. Furthermore, the battery load can be managed based on the actual remaining power transmitted by the sensor.

[0112] Conversely, if the third duration is less than the third duration threshold or no valid status flag is received, the battery load can continue to be managed based on the estimated remaining power.

[0113] In one implementation, after managing the battery load using estimated remaining power, the system can continue to receive status flags from sensors. If a sensor restart is detected, the system can continue to receive status flags and determine if they are valid. If they are valid, it is determined that the sensor fault has been eliminated and the battery parameters sent by the sensor are valid. Furthermore, the battery load can be managed based on the remaining power (i.e., the actual remaining power) sent by the sensor.

[0114] Alternatively, after managing the battery load using estimated remaining power, the system can continue to receive status flags from the sensors. If a sensor restart is detected, the system can continue to receive status flags and determine if the flags are valid (i.e., a status value of 2 indicates a sensor error of less than 10%). If the flags are valid (i.e., a status value of 2 indicates a sensor error of less than 10%), the sensor fault is considered eliminated, and the battery parameters sent by the sensor are valid. Furthermore, the battery load can be managed based on the remaining power (i.e., the actual remaining power) sent by the sensors.

[0115] In this embodiment of the application, after managing the battery load by estimating the remaining power, if multiple valid status flag bits are received consecutively, it is determined that the sensor is fault-free and valid. After the sensor fault is cleared, the battery load can be managed in a timely manner based on the remaining power sent by the sensor.

[0116] Similarly, if a valid status flag is received after a sensor restart is detected, it indicates that the sensor is fault-free and valid. After the sensor fault is cleared, the battery load can be managed promptly based on the remaining power sent by the sensor.

[0117] It is understandable that compared to a valid status flag with a characterization error of less than 15% (i.e., a valid status flag with a status value of 1), a valid status flag with a characterization error of less than 10% indicates higher reliability and accuracy of the sensor. Furthermore, when the received status flag is a valid status flag with a characterization error of less than 10%, managing the battery load based on the actual remaining charge allows for more reliable and accurate determination of the sensor's fault-free operation. This improves the reliability and accuracy of battery management.

[0118] See Figure 2 , Figure 2 This is a schematic flowchart illustrating a battery load management method provided in an embodiment of this application. Figure 2 As shown, the method may include the following steps: Step 201: Receive the status flag bits periodically sent by the sensor.

[0119] Step 202: Determine the number of failure status flags included in the multiple status flags received within the preset time period.

[0120] Step 203: Is the quantity greater than or equal to the quantity threshold?

[0121] Step 204: If yes, then the estimated remaining power is obtained.

[0122] Step 205: Manage the battery load based on the estimated remaining power.

[0123] In this embodiment, the controller receives status flags periodically sent by the sensor. During the process of receiving the status flags periodically sent by the sensor, it determines the number of failure status flags included in the multiple status flags received within a preset time period, and determines whether the number is greater than or equal to a quantity threshold. If the number is determined to be greater than or equal to the quantity threshold, steps 204 and 205 are executed to estimate the estimated remaining power, and the battery load is managed based on the estimated remaining power.

[0124] Conversely, if the quantity is determined to be less than the threshold, the sensor is considered fault-free. In this case, no alarm or notification messages are output, and the battery load can be managed normally using the battery parameters sent by the sensor. Simultaneously, the process can return to step 202.

[0125] Based on the above examples, during the process of receiving status flags periodically sent by the sensor, the controller can also determine the first duration if multiple consecutively received status flags are all failure status flags. If the first duration is greater than or equal to the first duration threshold, the controller can estimate the remaining battery power and manage the battery load based on the estimated remaining battery power.

[0126] Step 206: Determine whether a valid status flag is continuously received.

[0127] Step 207: If so, manage the battery load according to the actual remaining power.

[0128] In this embodiment, after managing the battery load based on the estimated remaining power, the controller continues to receive status flags periodically sent by the sensor. During the process of receiving the status flags periodically sent by the sensor, it determines whether a valid status flag is continuously received. If a valid status flag is continuously received, the controller manages the battery load based on the actual remaining power.

[0129] Based on the above example, after managing the battery load according to the estimated remaining power, the controller determines the third duration if multiple consecutive status flags are valid (i.e., continuously receiving valid status flags). If the third duration is greater than or equal to the third duration threshold, the controller manages the battery load based on the actual remaining power sent by the sensor.

[0130] Furthermore, if the number is greater than or equal to a quantity threshold, and if it is determined that multiple consecutively received status flags within the observation period are valid status flags, then a second duration is determined. If the second duration is greater than or equal to a second duration threshold, the number is reset to zero. And / or, if a sensor restart is detected when the number is greater than or equal to a quantity threshold, the number is reset to zero when a valid status flag is received.

[0131] The above text combined Figure 1-2 The battery load management method provided in the embodiments of this application is described in detail below; the following will be combined with Figure 3 and Figure 4 The apparatus embodiments of this application are described in detail below. It should be understood that the apparatus in the embodiments of this application can perform the various methods described in the foregoing embodiments of this application, that is, the specific working processes of the various products described below can be referred to the corresponding processes in the foregoing method embodiments.

[0132] See Figure 3 , Figure 3 This is a schematic diagram of the structure of a battery load management device provided in an embodiment of this application. Figure 3 As shown, the battery load management device 300 may include: The receiving module 301 is used to receive the status flag bits periodically sent by the battery's sensors; The estimation module 302 is used to estimate the remaining power of the battery when multiple failure status flags exist among the multiple status flags received in succession, so as to obtain the estimated remaining power. Management module 303 is used to manage the load of the battery based on the estimated remaining power.

[0133] Optionally, the estimation module 302 is specifically configured to: determine a first duration when all of the continuously received status flags are failure status flags, the first duration being the duration from the first reception of the failure status flag to the last reception of the failure status flag; estimate the estimated remaining battery power when the first duration is greater than or equal to a first duration threshold; and / or determine the number of failure status flags included in the multiple continuously received status flags within a preset time period; estimate the estimated remaining battery power when the number is greater than or equal to a preset number threshold, the number threshold being an integer greater than 1.

[0134] Optionally, the estimation module 302 is specifically used to calibrate the battery when the first duration is greater than or equal to the first duration threshold; after the calibration of the battery is completed, if the status flag bit as a failure status flag bit is received, the estimated remaining power is estimated.

[0135] Optionally, the estimation module 302 is specifically used to estimate the estimated remaining power if it is determined that a failure status flag bit is received within the observation period when the quantity is greater than or equal to the quantity threshold, wherein the observation period is a time period starting from the current time.

[0136] Optionally, the estimation module 302 is further configured to, if it is determined that no failure status flag bit is received within the observation period when the number is greater than or equal to the number threshold, output a first prompt message, the first prompt message indicating that the sensor connection is abnormal.

[0137] Optionally, the estimation module 302 is specifically used to estimate the estimated remaining power if it is determined that multiple consecutive failure status flag bits are received within the observation period.

[0138] Optionally, the estimation module 302 is further configured to, if the number is greater than or equal to the number threshold, determine a second duration if it is determined that all of the multiple status flag bits received consecutively within the observation period are valid status flag bits, the second duration being the duration from the first reception of a valid status flag bit to the last reception of a valid status flag bit; if the second duration is greater than or equal to the second duration threshold, reset the number to zero; and / or, if the sensor is detected to have restarted when the number is greater than or equal to the number threshold, reset the number to zero when a status flag bit that is a valid status flag bit is received.

[0139] Optionally, the management module 303 is further configured to determine a third duration when multiple consecutively received status flag bits are all valid status flag bits, the third duration being the duration from the first receipt of a valid status flag bit to the last receipt of a valid status flag bit; if the third duration is greater than or equal to a third duration threshold, manage the load of the battery based on the actual remaining power transmitted by the sensor; and / or, after detecting a restart of the sensor, if a status flag bit that is a valid status flag bit is received, manage the load of the battery based on the actual remaining power.

[0140] Optionally, the valid status flag bit is a valid status flag bit that indicates that the error of the sensor is less than 10%.

[0141] See Figure 4 , Figure 4 This is a structural schematic diagram of a vehicle provided in an embodiment of this application. For example... Figure 4As shown, the vehicle 400 includes a memory 401 and a processor 402. The memory 401 stores executable program code 4011, and the processor 402 is used to call and execute the executable program code 4011 to perform a battery load management method.

[0142] Furthermore, embodiments of this application also protect a battery load management device, which may include a memory and a processor, wherein the memory stores executable program code, and the processor is used to call and execute the executable program code to perform a battery load management method provided in embodiments of this application.

[0143] This embodiment can divide the device into functional modules according to the above method example. For example, each module can correspond to a separate functional module, or two or more functions can be integrated into one output module. The integrated module can be implemented in hardware. It should be noted that the module division in this embodiment is illustrative and only represents one logical functional division. In actual implementation, there may be other division methods.

[0144] It should be understood that the device provided in this embodiment is used to execute the above-described battery load management method, and therefore can achieve the same effect as the above-described implementation method.

[0145] This embodiment also provides a readable storage medium storing executable program code. When the executable program code is run on a vehicle, the vehicle performs the aforementioned method steps to implement a battery load management method provided in the above embodiment.

[0146] This embodiment also provides a program product that, when run on a vehicle, causes the vehicle to perform the aforementioned steps to implement a battery load management method provided in the above embodiment.

[0147] In this embodiment, the device, readable storage medium, program product, or chip are all used to execute the corresponding methods provided above. Therefore, the beneficial effects that can be achieved can be referred to the beneficial effects of the corresponding methods provided above, and will not be repeated here.

[0148] Through the above description of the embodiments, those skilled in the art will understand that, for the sake of convenience and brevity, only the division of the above functional modules is used as an example. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above.

[0149] In the embodiments provided in this application, it should be understood that the disclosed apparatus and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of modules or units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another device, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between devices or units may be electrical, mechanical, or other forms.

[0150] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. 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 scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A load management method for a storage battery, characterized in that, The method includes: The sensor receives the status flag bits periodically sent by the battery. If multiple failure status flags are present among the multiple status flags received consecutively, the remaining power of the battery is estimated to obtain the estimated remaining power. The load of the battery is managed based on the estimated remaining power.

2. The method as described in claim 1, characterized in that, In the case where multiple failure status flags are present among the continuously received status flags, the remaining battery power is estimated to obtain the estimated remaining battery power, including: If multiple consecutive received status flag bits are all failure status flag bits, a first duration is determined, the first duration being the duration from the first receipt of the failure status flag bit to the last receipt of the failure status flag bit; if the first duration is greater than or equal to a first duration threshold, the estimated remaining power is estimated. And / or, determine the number of failure status flag bits included in the plurality of status flag bits received continuously within a preset time period; if the number is greater than or equal to a preset number threshold, estimate the estimated remaining power, wherein the number threshold is an integer greater than 1.

3. The method as described in claim 2, characterized in that, The step of estimating the estimated remaining battery power when the first duration is greater than or equal to the first duration threshold includes: The battery is calibrated if the first duration is greater than or equal to the first duration threshold. After the battery calibration is completed, if the status flag bit is received as a failure status flag bit, the estimated remaining power is estimated.

4. The method as described in claim 2, characterized in that, The step of estimating the estimated remaining power when the quantity is greater than or equal to a preset quantity threshold includes: If the quantity is greater than or equal to the quantity threshold, and if a failure status flag is received within the observation period, the estimated remaining power is estimated, wherein the observation period is the period starting from the current time.

5. The method as described in claim 4, characterized in that, The method further includes: If the number is greater than or equal to the number threshold, and it is determined that no failure status flag is received within the observation period, a first prompt message is output, which indicates that the sensor connection is abnormal.

6. The method as described in claim 4, characterized in that, The step of estimating the estimated remaining battery power if a failure status flag is received within the observation period includes: If multiple consecutive failure status flag bits are received within the observation period, the estimated remaining power is obtained.

7. The method as described in claim 4, characterized in that, The method includes: If the number is greater than or equal to the number threshold, and if it is determined that multiple status flag bits received consecutively within the observation period are all valid status flag bits, then a second duration is determined, the second duration being the duration from the first valid status flag bit received to the last valid status flag bit received; if the second duration is greater than or equal to the second duration threshold, the number is cleared to zero. And / or, if the number is greater than or equal to the number threshold, and a restart of the sensor is detected, the number is cleared to zero upon receiving the status flag bit as a valid status flag bit.

8. The method as described in claim 1, characterized in that, After managing the battery load based on the estimated remaining power, the method further includes: If multiple consecutive received status flag bits are all valid status flag bits, a third duration is determined, the third duration being the duration from the first valid status flag bit received to the last valid status flag bit received; if the third duration is greater than or equal to a third duration threshold, the load of the battery is managed based on the actual remaining power sent by the sensor. And / or, after detecting that the sensor has restarted, if the status flag bit is received as a valid status flag bit, the load of the battery is managed based on the actual remaining power.

9. The method as described in claim 7 or 8, characterized in that, The valid status flag is a flag indicating that the error of the sensor is less than 10%.

10. A vehicle, characterized in that, The vehicles include: Memory, used to store executable program code; A processor for calling and running the executable program code from the memory, causing the vehicle to perform the method as described in any one of claims 1 to 9.

Images