Battery low power protection method and device based on scene recognition and storage medium

Abstract

This application provides a method, apparatus, and storage medium for low battery protection based on scene recognition. The method includes: acquiring image information and scene information surrounding the vehicle; determining a target object based on the image information and acquiring distance information between the target object and the vehicle; generating a dangerous scene signal when the vehicle meets preset dangerous scene judgment conditions; responding to a charging request sent by a low-voltage battery management system, acquiring the power battery level; and generating a low battery protection request signal when the power battery level is below a second level threshold (the charging request is sent when the low-voltage battery level is below a first level threshold); and determining whether to charge the power battery and low-voltage battery based on the dangerous scene signal and the low battery protection request signal, and executing a corresponding low battery protection strategy. This application can avoid the risk of over-discharge of the battery, improve battery life, and reduce safety hazards.

Description

Technical Field

[0001] This application relates to the field of new energy vehicle technology, and in particular to a method, device and storage medium for low battery protection based on scene recognition. Background Technology

[0002] With the rapid development of range-extended electric vehicles (REEVs) and the increasing intelligence of these vehicles, the power battery, as a core component, is crucial to the overall vehicle performance and lifespan through its power battery management. Existing low-battery protection strategies primarily involve triggering the range extender to recharge when the battery level falls below a set threshold, or issuing a warning to the user when the battery is low.

[0003] However, these traditional strategies suffer from insufficient intelligence and are prone to performing charging or protection operations inappropriately, leading to problems such as battery over-discharge, reduced battery life, and increased safety hazards in existing technologies. Summary of the Invention

[0004] In view of this, embodiments of this application provide a method, device and storage medium for low battery protection based on scene recognition, in order to solve the problems of battery over-discharge, reduced battery life and increased safety hazards in the prior art.

[0005] A first aspect of this application provides a low battery protection method based on scene recognition, comprising: acquiring image information and scene information around a vehicle; determining a target object based on the image information and acquiring distance information between the target object and the vehicle; generating a dangerous scene signal based on the image information, scene information, and distance information, provided that the vehicle meets preset dangerous scene judgment conditions; acquiring the power battery charge level in response to a charging request sent by a low-voltage battery management system; generating a low battery protection request signal when the power battery charge level is lower than a second charge threshold, wherein the charging request is sent when the low-voltage battery charge level is lower than a first charge threshold; and determining whether to charge the power battery and the low-voltage battery based on the dangerous scene signal and the low battery protection request signal, and executing a corresponding low battery protection strategy.

[0006] A second aspect of this application provides a low-battery protection device based on scene recognition, comprising: an acquisition module for acquiring image information and scene information around a vehicle, determining a target object based on the image information, and acquiring distance information between the target object and the vehicle; an analysis module for generating a dangerous scene signal based on the image information, scene information, and distance information, provided that the vehicle meets preset dangerous scene judgment conditions; a generation module for acquiring the power battery charge level in response to a charging request sent by a low-voltage battery management system, and generating a low-battery protection request signal when the power battery charge level is lower than a second charge threshold, wherein the charging request is sent when the low-voltage battery charge level is lower than a first charge threshold; and an execution module for determining whether to charge the power battery and the low-voltage battery based on the dangerous scene signal and the low-battery protection request signal, and executing a corresponding low-battery protection strategy.

[0007] A third aspect of this application provides an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the steps of the above-described method.

[0008] A fourth aspect of this application provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the steps of the above-described method.

[0009] The above-described technical solutions adopted in the embodiments of this application can achieve the following beneficial effects:

[0010] By acquiring image and scene information around the vehicle, the system identifies target objects based on the image information and obtains the distance information between the target objects and the vehicle. Based on the image, scene, and distance information, and if the vehicle meets preset hazardous scene judgment conditions, a hazardous scene signal is generated. In response to a charging request sent by the low-voltage battery management system, the system acquires the power battery level. If the power battery level is lower than a second level threshold, a low-charge protection request signal is generated. The charging request is sent when the low-voltage battery level is lower than a first level threshold. Based on the hazardous scene signal and the low-charge protection request signal, the system determines whether to charge the power battery and the low-voltage battery and executes the corresponding low-charge protection strategy. This application can avoid the risk of battery over-discharge, improve battery life, and reduce safety hazards. Attached Figure Description

[0011] To more clearly illustrate the technical solutions in the embodiments of this application, the drawings used in the description of the embodiments or the prior art 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.

[0012] Figure 1 This is a schematic diagram of the overall architecture of the low battery protection system provided in the embodiments of this application;

[0013] Figure 2 This is a schematic flowchart of the low battery protection method based on scene recognition provided in the embodiments of this application;

[0014] Figure 3 This is a schematic diagram of a dangerous scenario under the first condition provided in the embodiments of this application;

[0015] Figure 4 This is a schematic diagram of a dangerous scenario under the second condition provided in the embodiments of this application;

[0016] Figure 5 This is a schematic diagram of a dangerous scenario under the third condition provided in the embodiments of this application;

[0017] Figure 6 This is a schematic diagram of the low battery protection device based on scene recognition provided in the embodiments of this application;

[0018] Figure 7 This is a schematic diagram of the structure of the electronic device provided in the embodiments of this application. Detailed Implementation

[0019] In the following description, specific details such as particular system architectures and techniques are set forth for illustrative purposes and not for limitation, in order to provide a thorough understanding of the embodiments of this application. However, those skilled in the art will understand that this application may also be implemented in other embodiments without these specific details. In other instances, detailed descriptions of well-known systems, apparatuses, circuits, and methods have been omitted so as not to obscure the description of this application with unnecessary detail.

[0020] It should be understood that the steps described in the method embodiments of this application may be performed in different orders and / or in parallel. Furthermore, the method embodiments may include additional steps and / or omit the steps shown. The scope of this application is not limited in this respect.

[0021] The term "comprising" and its variations as used herein are open-ended, meaning "including but not limited to". The term "based on" means "at least partially based on". The term "one embodiment" means "at least one embodiment"; the term "another embodiment" means "at least one additional embodiment"; the term "some embodiments" means "at least some embodiments". Definitions of other terms will be given in the following description. It should be noted that the concepts of "first", "second", etc., mentioned in this application are used only to distinguish different devices, modules, or units, and are not intended to limit the order of functions performed by these devices, modules, or units or their interdependencies.

[0022] It should be noted that the terms "a" and "a plurality of" used in this application are illustrative rather than restrictive, and those skilled in the art should understand that, unless otherwise expressly indicated in the context, they should be understood as "one or more".

[0023] With the rapid development of range-extended electric vehicles (REEVs), the level of intelligence in these vehicles is constantly improving, and many systems and functions rely on intelligent algorithms and sensors. However, the power battery is a critical component of REEVs, and its power management is crucial to the overall vehicle performance and lifespan. If the power battery's charge level falls below a certain point and is not replenished or protected in time, it may lead to over-discharge, reduced battery life, or even battery damage. This will negatively impact user experience, vehicle performance, and maintenance costs.

[0024] Currently, mainstream range-extended electric vehicles typically employ a simple low-charge protection strategy when the battery level is low. For example, the main functions include:

[0025] 1. Trigger range extender charging: When the battery level is too low, the range extender is activated to generate electricity to replenish the power battery.

[0026] 2. Simple alarm function: Notifies the user when the battery is low so that timely measures can be taken.

[0027] However, these existing technologies have a low level of intelligence and fail to provide flexible protection based on external conditions such as vehicle parking scenarios. For example, if the battery level continues to drop while the vehicle is parked for an extended period, the following problems may occur: The battery may be over-discharged due to lack of timely charging, affecting battery life. Furthermore, existing strategies cannot determine if there are any safety hazards in the surrounding environment, and may trigger the range extender to generate electricity under unsuitable circumstances. For instance, the activation of the range extender may pose a safety hazard in enclosed parking environments or flammable and explosive areas.

[0028] As can be seen from the above existing technologies, current low battery protection strategies still have the following technical problems:

[0029] 1. Insufficient scene perception: Failed to identify whether the environment in which the vehicle is located is suitable for triggering the range extender to generate electricity, which poses a potential safety hazard.

[0030] 2. Insufficient intelligence: The power protection strategy is relatively simple and lacks the ability to make automatic decisions based on specific situations, which may lead to the range extender operating in inappropriate situations.

[0031] 3. Inadequate user reminder mechanism: In cases where the range extender fails to start generating electricity, it fails to provide sufficient prompts or warnings to the user.

[0032] In view of the problems existing in the prior art, and to address the safety and intelligent protection issues of current range-extended vehicle power batteries in low-charge states, this application provides a novel scene-recognition-based low-charge battery protection method. This application combines sensors such as cameras and ultrasonic radar to identify the scene surrounding the vehicle. The low-charge protection strategy can determine whether the vehicle's environment is suitable for starting the range extender to generate electricity, thereby improving the intelligence level of low-charge protection. Simultaneously, when the surrounding environment is unsuitable for power generation, an alarm can be issued to the user, reminding them to take timely measures. This intelligent low-charge protection strategy not only improves vehicle safety but also extends battery life and reduces maintenance costs.

[0033] The following detailed description, in conjunction with the accompanying drawings and embodiments, illustrates the architectural composition of the battery low-power protection system involved in this application in a real-world scenario. Figure 1 This is a schematic diagram of the overall architecture of the low battery protection system provided in this application embodiment. Figure 1 As shown, the low battery protection system may specifically include the following structural components:

[0034] 1. Ultrasonic Radar: Ultrasonic radar uses ultrasonic waves to measure distance and detect targets (ultrasonic radar is generally used for short-range target detection). It determines the target's distance and direction by measuring the reflection time and frequency of the ultrasonic waves. The ultrasonic radar transmits the collected distance between the target and the vehicle to the intelligent driving domain controller.

[0035] 2. Camera: Captures images by learning the typical characteristics of target objects and using image processing technology to identify typical target objects and their quantities. Examples include: common hazardous scenarios such as gas stations and hazardous chemical plants; common hazardous materials such as fireworks, oil tanks, gas cylinders, and tank trucks; and common hazard signs such as flammable and explosive material signs.

[0036] 3. Autonomous Driving Controller (ADC): Data processing and control module. It receives target information and quantity information from cameras, and the distance between the target and the vehicle from ultrasonic radar. It processes the data, and if a dangerous target is detected within the distance S1 (calibrated value), or the camera is obstructed (e.g., the vehicle is covered by a car cover or the camera information is unreliable), or the vehicle is detected in a dangerous scenario (e.g., a gas station or a hazardous chemical plant), it sends a dangerous scenario warning signal to the vehicle controller via the gateway.

[0037] 4. Vehicle Domain Controller (VDC): Data processing and control module. It receives charging requests from the low-voltage battery management system, wakes up the battery management system, and determines whether to implement a low-charge protection strategy based on the battery management system's SOC (State of Charge) level.

[0038] 5. Engine Management System (EMS): The EMS receives control requests from the vehicle controller (VDC) to control the start of the range extender and generate electricity according to the power required by the vehicle controller (VDC).

[0039] 6. Battery Management System (BMS): The BMS uses the power sensor to feed back the SOC information of the power battery to the vehicle controller (VDC), and receives the high voltage request from the vehicle controller (VDC) to execute the high voltage connection of the power battery. It can also replenish the low voltage battery.

[0040] 7. Low Battery Management System (LBMS): Periodically wakes itself up and checks the SOC of the low-voltage battery. If the detected SOC is ≤ SOC1 (calibrated value), the LBMS wakes up the vehicle controller (VDC) and sends a low-voltage battery charging request to the vehicle controller (VDC).

[0041] 8. Body Control Module (BCM): Receives the low-voltage power-on request from the vehicle controller (VDC), performs the low-voltage power-on action, and wakes up the vehicle.

[0042] 9. Telematics Box (TBOX): Receives the low battery alarm sent by the vehicle controller (VDC) and sends the alert to the user's terminal device (APP) via the cloud.

[0043] 10. Gateway (GW): The role of the gateway (GW) is to convert and transmit data between different networks, and to be responsible for the signal interaction between the intelligent driving domain controller (ADC), the vehicle controller (VDC), the body controller (BCM), and the vehicle communication module (TBOX).

[0044] The technical solution of this application will now be described in detail with reference to the accompanying drawings and specific embodiments.

[0045] Figure 2 This is a flowchart illustrating the low battery protection method based on scene recognition provided in an embodiment of this application. Figure 2 As shown, the low battery protection method based on scene recognition may specifically include:

[0046] S201, acquire image information and scene information around the vehicle, determine the target object based on the image information, and acquire the distance information between the target object and the vehicle;

[0047] S202, Based on image information, scene information and distance information, if it is determined that the vehicle meets the preset dangerous scene judgment conditions, a dangerous scene signal is generated;

[0048] S203, in response to the power replenishment request sent by the low-voltage battery management system, obtain the power battery level, and generate a low power protection request signal when the power battery level is lower than the second power threshold. The power replenishment request is sent when the low-voltage battery level is lower than the first power threshold.

[0049] S204, based on the dangerous scenario signal and the low battery protection request signal, determines whether to recharge the power battery and the low-voltage battery, and executes the corresponding low battery protection strategy.

[0050] In some embodiments, this embodiment provides a low battery protection method based on scene recognition, which uses a combination of camera and ultrasonic radar to acquire information about the vehicle's surrounding environment to identify potential dangerous scenes and dangerous objects, thereby providing more intelligent decision support for low battery protection.

[0051] First, cameras are installed around the vehicle to capture image and scene information about the environment. The cameras acquire environmental image data by capturing real-time images of the area around the vehicle. This image data is then analyzed using a pre-designed target feature model, which includes characteristic information about typical hazards and hazardous scenarios. For example, the model has pre-learned common hazardous scenarios (such as gas stations and hazardous chemical plants) and their distinctive features, including building layouts and identification signs. Furthermore, the model has also learned the characteristics of common hazardous targets, including but not limited to fireworks, oil tanks, gas cylinders, and the distinctive markings of flammable and explosive materials, such as red triangle signs or "Danger" text warnings.

[0052] Through image processing algorithms, the camera can analyze the captured images, identify dangerous scenes or targets in the images, and transmit the identification results to the Intelligent Driving Domain Controller (ADC). The ADC further determines whether the identified object type and its distance from the vehicle constitute a potential threat based on the information transmitted by the camera.

[0053] Secondly, the system is also equipped with ultrasonic radar for short-range target detection and ranging. Ultrasonic radar emits ultrasonic waves and receives the waveform signals reflected back from the target surface, using the changes in reflection time and frequency to calculate the precise distance and relative direction between the target and the vehicle. This distance information provides accurate measurement data when the vehicle is close to the target, improving the reliability and accuracy of hazardous scene identification.

[0054] Once the ultrasonic radar detects a target and measures its distance from the vehicle, the system combines this distance information with the image recognition results from the camera and performs comprehensive analysis through the Intelligent Driving Domain Controller (ADC). For example, if the camera identifies a tanker truck sign ahead, and the ultrasonic radar measures the distance between the object and the vehicle to be less than a preset safe distance, the ADC will generate a hazard scene signal to trigger appropriate low-battery protection strategies in the event of a low battery condition.

[0055] Through the method described in the above embodiments, this embodiment effectively combines the image recognition capability of the camera and the precise ranging function of the ultrasonic radar, realizing the identification and judgment of potential dangerous scenes and targets around the vehicle, and providing strong support for intelligent decision-making for low battery protection.

[0056] In some embodiments, based on image information, scene information, and distance information, a dangerous scene signal is generated when it is determined that the vehicle meets preset dangerous scene judgment conditions, including:

[0057] Data processing is performed on image information, scene information, and distance information to determine the type of target object and the relative distance between the target object and the vehicle;

[0058] Based on the data processing results, determine whether the vehicle meets any of the preset dangerous scenario judgment conditions. If it does, generate a dangerous scenario signal.

[0059] The criteria for determining a dangerous scenario include the relative distance between the target and the vehicle being less than a preset safe distance, the camera being obstructed or the image information being unavailable, and the vehicle being in a dangerous scenario.

[0060] In some examples, the system acquires data input from cameras and ultrasonic radar. Camera data includes real-time image and scene information captured around the vehicle. The cameras use pre-trained target feature models to identify typical target types, such as hazardous materials (fireworks, oil tanks, gas cylinders, etc.), hazard signs (flammable and explosive signs, etc.), and hazardous scenes (such as gas stations, chemical plants, etc.). Ultrasonic radar data includes real-time measurements of the distance between the target and the vehicle, providing accurate distance information and relative position and direction.

[0061] The system transmits the above data to the Intelligent Driving Domain Controller (ADC) and performs the following processing within the ADC:

[0062] 1) Comprehensive data processing:

[0063] Based on the image information provided by the camera, the type and location of the target object are identified, and it is determined whether the target object belongs to the category of dangerous objects or scenes.

[0064] Based on the distance information provided by ultrasonic radar, the relative distance between the target and the vehicle is determined.

[0065] 2) Hazardous scenario assessment:

[0066] The system analyzes the processed data based on preset hazardous scenario assessment criteria. These criteria can include the following three scenarios:

[0067] Target approaching: The distance between the target and the vehicle is less than the preset safe distance (i.e., S < S1). This situation may involve the vehicle approaching dangerous objects such as tanker trucks or gas cylinders.

[0068] Camera obstruction: When the camera is obstructed (e.g., covered by a car cover or contaminated), making image information unusable, the system determines that the surrounding scene cannot be accurately perceived, which is considered a potential danger.

[0069] Vehicle in a dangerous situation: The camera recognizes that the vehicle is in a specific dangerous situation, such as a gas station or a hazardous chemical plant.

[0070] 3) Generate hazardous scene signals

[0071] If the analysis results meet any of the above-mentioned hazardous scenario determination conditions, the Intelligent Driving Domain Controller (ADC) generates a hazardous scenario signal. In practical applications, the hazardous scenario signal is transmitted to the Vehicle Controller (VDC) via the Gateway (GW). The Vehicle Controller, based on the received hazardous scenario signal and the current vehicle status, determines whether to trigger a low battery protection strategy or other safety strategies.

[0072] The following examples illustrate the dangerous scene determination conditions for generating dangerous scene signals in this application.

[0073] Example 1: The target object is approaching

[0074] When the vehicle is parked, the camera detects a tanker truck in front of it, and the ultrasonic radar measures the distance between the tanker truck and the vehicle to be 1.5 meters (less than the safe distance of 2 meters). The ADC determines that the dangerous scenario condition of "target approaching" is met and generates a dangerous scenario signal.

[0075] Example 2: Camera obstruction

[0076] If the camera is covered by a car cover when the vehicle is parked, making it impossible to obtain effective image information, the ADC will regard this as a potentially dangerous environment and generate a dangerous scene signal.

[0077] Example 3: Hazardous Scene Recognition

[0078] When a vehicle is parked inside a gas station, the camera identifies the unique landmarks and layout of the gas station to determine that the vehicle is in a dangerous situation and generates a dangerous situation signal.

[0079] Through the method described in the above embodiments, this embodiment can intelligently identify and judge dangerous scene conditions based on multi-source information around the vehicle, ensuring that the system generates dangerous scene signals and notifies relevant control modules when necessary, thus providing support for the execution of subsequent protection strategies.

[0080] In addition to the dangerous scenario determination conditions in the above embodiments, this embodiment further discloses several dangerous scenarios under different conditions. The dangerous scenarios provided in this embodiment will be explained and described below with reference to the accompanying drawings and specific examples.

[0081] Figure 3 This is a schematic diagram of a dangerous scenario under the first condition provided in the embodiments of this application. For example... Figure 3 As shown, this dangerous scenario includes common hazardous materials (such as fireworks, oil tanks, gas cylinders, etc.) and common hazard signs (such as flammable and explosive material signs).

[0082] Figure 4 This is a schematic diagram of a dangerous scenario under the second condition provided in the embodiments of this application. For example... Figure 4As shown, the hazardous scenarios include, but are not limited to, the following common hazardous scenarios: gas stations, hazardous chemical plants, etc.

[0083] Figure 5 This is a schematic diagram of a dangerous scenario under the third condition provided in the embodiments of this application. For example... Figure 5 As shown, this hazardous scenario includes common dangerous vehicles (such as tanker trucks, hazardous chemical transport vehicles, etc.).

[0084] In some embodiments, the power battery charge is acquired, and when the power battery charge is lower than a second charge threshold, a low charge protection request signal is generated, including:

[0085] In response to a power replenishment request, the battery management system is activated and requests to obtain the power battery charge, and the power battery charge returned by the battery management system is received.

[0086] If the power battery charge is lower than the preset second charge threshold, a low charge protection request signal is generated, and a low voltage power-on request is sent to the vehicle domain controller to wake up the vehicle and start the vehicle high voltage power-on.

[0087] In some examples, this embodiment provides a low battery protection request generation method based on vehicle battery power detection. It utilizes the low-voltage battery management system (LBMS), vehicle controller (VDC), and battery management system (BMS) to work together to monitor the power battery power, generate protection requests, and implement high-voltage power-on of the vehicle.

[0088] First, the low-voltage battery management system (LBMS) is configured to periodically wake up and monitor the state of charge (SOC) of the low-voltage battery. When the SOC value of the low-voltage battery is detected to be lower than the first charge threshold SOC1, the LBMS will actively wake up the vehicle controller (VDC) and send a low-voltage battery charging request to the VDC.

[0089] Upon receiving the power-up request from the LBMS, the VDC initializes its own state and begins coordinating the wake-up process of relevant modules. The specific implementation is as follows:

[0090] The VDC sends a wake-up request to the BMS and simultaneously requests to obtain the state of charge (SOC) of the power battery. The BMS responds to the request and detects the current SOC value of the power battery.

[0091] The BMS transmits the detection results to the VDC, including the current SOC value of the power battery.

[0092] If the SOC value of the power battery fed back by the BMS is lower than the second power threshold SOC2, the VDC generates a low power protection request signal.

[0093] After generating a low battery protection request signal, the VDC sends a low-voltage power-on request to the Body Controller (BCM) to wake up the entire vehicle, including the Intelligent Driving Domain Controller (ADC) and other related modules.

[0094] After the BCM completes low-voltage power-on, the VDC further performs high-voltage power-on operation for the entire vehicle, providing support for subsequent power replenishment or protection strategies.

[0095] After the VDC completes high-voltage power-on, it waits for vehicle scene recognition feedback from the Intelligent Driving Domain Controller (ADC). The ADC analyzes the scene to determine whether there are any dangerous scenarios in the vehicle's environment, providing a scenario basis for the subsequent execution of low battery protection strategies.

[0096] For example, in one scenario, suppose the vehicle has been parked for an extended period and has not been used. The State of Charge (SOC) of the low-voltage battery drops below SOC1. The LBMS detects the low charge and wakes up the VDC. The VDC, by waking up the BMS, checks the SOC of the power battery and finds that its SOC is also below SOC2, indicating that the power battery is in a low-charge state. At this point, the VDC generates a low-charge protection request signal and coordinates the vehicle to perform low-voltage and high-voltage power-on, preparing for subsequent charging of the power battery and the low-voltage battery.

[0097] Through the methods described in the above embodiments, this application can intelligently coordinate multiple control modules in a low-power state to ensure the normal operation of the power battery and low-voltage storage battery, while providing reliable support for subsequent low-power protection strategies.

[0098] In some embodiments, it is determined whether to recharge the power battery and the low-voltage battery, and corresponding low battery protection strategies are implemented, including:

[0099] When the low-voltage battery charge is below the first charge threshold, the power battery charge is below the second charge threshold, and the vehicle is in a dangerous situation, the first low battery protection strategy of not charging the battery is implemented.

[0100] When the low-voltage battery charge is below the first charge threshold, the power battery charge is below the second charge threshold, and the vehicle is in a non-dangerous situation, a second low-charge protection strategy is implemented to replenish the battery.

[0101] In some examples, this embodiment provides a method for determining whether to recharge the power battery and low-voltage battery based on the vehicle scenario and executing the corresponding low battery protection strategy. Through comprehensive analysis of scenario recognition signals and battery status, the method intelligently selects the recharge strategy to ensure vehicle safety and battery performance.

[0102] First, the intelligent driving domain controller ADC analyzes the vehicle's surrounding environment in real time, combining image information, scene information, and distance information obtained from cameras and ultrasonic radar to determine whether the vehicle is in a dangerous situation.

[0103] If the ADC identifies the vehicle as being in a dangerous environment such as a gas station or a hazardous chemical plant, or if the camera is obstructed and cannot obtain valid information, it will be marked as a dangerous scene. If no dangerous objects, warning signs, or dangerous scene are detected, it will be marked as a non-dangerous scene.

[0104] Then, VDC combines the low-voltage battery SOC information from LBMS and the power battery SOC information from BMS to determine whether the battery meets the following conditions: 1. The low-voltage battery charge is lower than the first charge threshold (SOC1); 2. The power battery charge is lower than the second charge threshold (SOC2). When both of the above conditions are met, the low charge protection process is triggered.

[0105] In practical applications, VDC selects different protection strategies based on the vehicle scene signal transmitted by the ADC, which can specifically include the following two strategies:

[0106] 1) Low battery protection strategy for the first battery (hazardous scenarios):

[0107] When the vehicle is in a dangerous situation, the VDC generates a low battery alarm signal and transmits the alarm information to the cloud through the vehicle communication module TBOX.

[0108] TBOX further sends a reminder to the user's mobile app, indicating that the vehicle is in a dangerous environment and cannot be automatically recharged, and suggests that the user take manual action.

[0109] The notification method can be controlled by a user-preset function switch:

[0110] ① Function switch A: When turned on, VDC determines whether to send a prompt message; when turned off, the prompt authority is given to the user. If the user does not respond within the preset time, the alarm process will be exited.

[0111] ② Function switch B: When turned on, it will always prompt the user; when turned off, it will only prompt once. If the user does not respond within the preset time, the prompting process will be exited.

[0112] 2) Second battery low charge protection strategy (non-hazardous scenarios):

[0113] When the vehicle is in a non-hazardous situation, the VDC controls the range extender to start, replenishing the power battery. At the same time, the BMS provides power from the power battery to the low-voltage battery, completing the replenishment of the low-voltage battery.

[0114] During the charging process, TBOX uploads the real-time power status of the power battery and low-voltage battery to the cloud and feeds it back to the user's APP so that the user can monitor the battery status in real time.

[0115] The following examples, using two different scenarios, will illustrate the specific applications of the two battery low-power protection strategies mentioned above.

[0116] Scenario Example 1: The vehicle is parked near a gas station, and both the power battery and the low-voltage battery are low on power. The ADC detects a dangerous scenario signal, and the VDC selects the first low battery protection strategy. A warning message is sent to the user's APP via the TBOX, stating, "Power battery is low on power. The current scenario is unsafe. Automatic charging is not possible. Please charge as soon as possible."

[0117] Scenario Example 2: The vehicle is parked in a regular parking lot, and both the power battery and the low-voltage battery are low on power. The ADC does not detect any dangerous scenario signals, and the VDC selects the second battery low-power protection strategy, activating the range extender to recharge the power battery and the low-voltage battery. At the same time, it sends feedback on the recharging status to the user's APP via the TBOX, such as "Range extender has started, power battery power is being recharged".

[0118] Through the methods described in the above embodiments, this embodiment achieves intelligent protection strategy selection under dangerous and non-dangerous scenarios by combining comprehensive analysis of vehicle scenarios and battery status. This effectively avoids the safety hazards caused by blindly starting charging operations in dangerous environments, while ensuring power replenishment in non-dangerous environments, thereby improving the safety and intelligence level of the system.

[0119] In some embodiments, a first low battery protection strategy that does not recharge the battery is implemented, including:

[0120] Generate a low battery alarm signal and send it to the vehicle communication module;

[0121] The vehicle communication module transmits a low battery alarm signal to the user's mobile device via the cloud, displaying a reminder message on the user's mobile device to notify the user that the surrounding environment of the vehicle is unsafe and automatic charging cannot be performed.

[0122] In some examples, this embodiment provides a method for implementing a first low battery protection strategy that does not recharge the battery in dangerous scenarios. By monitoring the vehicle battery status and surrounding scene information in real time, when the vehicle is in a dangerous environment and the battery power is too low, an alarm signal is generated and the user is notified to ensure the safety of the vehicle.

[0123] First, the Intelligent Driving Domain Controller (ADC) acquires environmental information about the vehicle's surroundings through cameras and ultrasonic radar, and comprehensively analyzes the image information, scene information, and distance information to determine whether the vehicle is in a dangerous situation. For example:

[0124] If a dangerous object (such as an oil tank, gas cylinder, fireworks, etc.) is detected near the vehicle and the distance to the vehicle is less than a preset safe distance, it is marked as a dangerous scene. If the vehicle is parked in a dangerous scene such as a gas station or chemical plant, it is also marked as a dangerous scene.

[0125] The low-voltage battery management system (LBMS) periodically checks the state of charge (SOC) of the low-voltage battery. When the SOC falls below the first charge threshold (SOC1), it sends a charge request to the vehicle controller (VDC).

[0126] VDC further wakes up the battery management system (BMS) to obtain the SOC value of the power battery, and triggers the low-charge protection process when it is lower than the second charge threshold (SOC2).

[0127] The VDC receives scene recognition signals from the intelligent driving domain controller ADC and determines whether the vehicle is in a dangerous scene. If it is determined to be a dangerous scene, the VDC selects to execute the first low battery protection strategy.

[0128] After confirming that the vehicle battery status and hazardous scenario conditions are met, the VDC generates a low battery alarm signal and sends the signal to the vehicle communication module (TBOX).

[0129] After receiving a low battery alarm signal, the TBOX transmits the alarm information to the user's mobile device (such as a smartphone) via the cloud. The alarm information includes the vehicle's current low battery status and a description of the hazardous environment, such as: "The battery power is too low, the area around the vehicle may be unsafe, intelligent charging is not possible, please charge as soon as possible."

[0130] The user's mobile app receives and displays a notification that the vehicle is currently unable to automatically recharge. The user can then take appropriate action based on the prompts, such as manually charging the vehicle as soon as possible or moving it to a safe environment.

[0131] For example, in one scenario, suppose a vehicle has been parked near a gas station for an extended period, and the battery charge gradually decreases. The Intelligent Driving Domain Controller (ADC) detects the presence of a gas station nearby, identifies the gas station sign using a camera, and determines that the distance to the gas station is less than the safe range using ultrasonic radar, generating a hazard warning signal. Simultaneously, the Battery Management System (LBMS) detects that the low-voltage battery's State of Charge (SOC) is below SOC1, and the Vehicle DC (VDC) obtains the power battery's SOC from the BMS as being below SOC2.

[0132] Once the above conditions are met, the VDC generates a low battery alarm signal and transmits the alert to the user's app via the TBOX. The user app displays a message: "The battery level is too low. The area around the vehicle may be unsafe. Intelligent charging is not possible. Please charge as soon as possible." The user understands the vehicle's status through this message and can take appropriate action.

[0133] By using the methods described in the above embodiments, this embodiment avoids the safety hazards caused by blindly performing charging operations in dangerous environments by intelligently identifying dangerous scenarios and battery status. At the same time, through a cloud-based reminder mechanism, it ensures that users are promptly informed of the vehicle status and can take appropriate measures, effectively improving vehicle safety and the level of intelligence in battery management.

[0134] In some embodiments, a second battery low-charge protection strategy for replenishing the battery is implemented, including:

[0135] The range extender is started and used to replenish the power battery. At the same time, the low-voltage battery is replenished through the battery management system.

[0136] The real-time charging status of the power battery and low-voltage battery is fed back to the user's mobile device so that the user can monitor the battery charging process.

[0137] In some examples, this embodiment also provides a method for implementing a second low-charge protection strategy to replenish the battery when the vehicle battery is in a low-charge state. This method controls the range extender to replenish the power battery and simultaneously replenishes the low-voltage battery, thereby ensuring that the vehicle receives the necessary power recovery in non-hazardous environments, improving the intelligence of battery management and the vehicle's range.

[0138] When a vehicle has been parked for an extended period of time, the Low Voltage Battery Management System (LBMS) detects that the State of Charge (SOC) of the low voltage battery is lower than a preset first charge threshold SOC1 and sends a charge request to the Vehicle Controller (VDC).

[0139] After receiving the request, VDC wakes up the Battery Management System (BMS) to obtain the State of Charge (SOC) of the power battery. If the SOC of the power battery is also lower than the second charge threshold SOC2, low charge protection is triggered.

[0140] The VDC further receives vehicle scene recognition signals from the Intelligent Driving Domain Controller (ADC) to determine whether there are dangerous objects or dangerous scenes in the vehicle's surrounding environment. If no dangerous objects or signs are detected, the ADC determines that the vehicle is in a non-dangerous scene, and the VDC decides to implement a second low battery protection strategy.

[0141] After confirming that the vehicle is in a non-hazardous situation, the VDC control unit starts the range extender. The range extender begins generating electricity and transferring it to the power battery to replenish it. The battery charging process is monitored by the BMS to ensure the safety of the charging process and the stability of current and voltage.

[0142] Because the main battery normally supplies power to the low-voltage battery, and the main battery's charge is currently too low to automatically charge the low-voltage battery, the range extender simultaneously charges the main battery while the main battery is being recharged. This is managed by the BMS (Battery Management System) and utilizes the main battery's charge to charge the low-voltage battery as well. This step ensures the low-voltage battery's charge is restored to support the vehicle's basic electrical needs and system stability.

[0143] The vehicle communication module TBOX receives charging status information from VDC and BMS, and feeds back the real-time power status of the power battery and low-voltage battery to the user's mobile device (such as APP) via the cloud.

[0144] Users can view the charging progress and battery status on a mobile app. For example, the charging status information may display as "The power battery is charging, the low-voltage battery is recovering its charge, please keep the vehicle in a non-hazardous environment."

[0145] For example, in one scenario, suppose the vehicle has been parked in a safe parking area for an extended period, and both the main battery and the low-voltage battery are below their respective thresholds. The LBMS detects the low-voltage battery's insufficient charge and sends a charging request. The VDC obtains the main battery's SOC information from the BMS, confirming that the main battery's charge is also below SOC2, and simultaneously confirms via the ADC that the vehicle is in a non-hazardous situation.

[0146] The VDC controller starts the range extender to generate electricity and transmits it to the power battery via the BMS to restore its charge. Simultaneously, the BMS also charges the low-voltage battery to ensure the operation of the vehicle's basic electrical systems. The onboard communication module TBOX provides real-time feedback on the charging status to the user's mobile app, allowing the user to monitor the charging progress at any time.

[0147] Through the methods described in the above embodiments, this embodiment achieves synchronous charging of the power battery and the low-voltage battery by implementing an automatic charging strategy for low battery states in non-hazardous scenarios. This ensures that the vehicle receives reliable power replenishment in a safe environment and enhances the user's monitoring capabilities and the vehicle's range assurance through real-time feedback.

[0148] In some embodiments, the method further includes:

[0149] After sending a low battery alarm to the user's mobile device, in response to the user's selection to force start the range extender via emergency control command, the range extender is controlled to start according to the preset power and power generation time, so as to perform a preset charging operation to the power battery.

[0150] In some examples, this embodiment also provides a control method for forcibly activating the range extender for short-term charging via the user's emergency control command when the vehicle is in a dangerous situation and the user requests emergency charging. This method can provide short-term charging support to the battery in specific emergency situations, ensuring that the vehicle's basic functions are maintained.

[0151] When the system detects that the power battery and low-voltage battery are both below the preset threshold and the vehicle is in a dangerous situation (such as near a gas station or chemical plant area), the vehicle controller VDC generates a low battery alarm signal.

[0152] The VDC transmits the alarm signal to the vehicle communication module TBOX. The TBOX then sends the low battery alarm information to the user's mobile device (such as an app on a smartphone) via the cloud, reminding the user that the vehicle is in a dangerous situation and cannot be automatically recharged.

[0153] After receiving a low battery alarm, if a user deems it an emergency requiring a short-term boost to the vehicle's battery, they can select the "Force Start Range Extender" emergency option in the mobile app. The user's emergency command is transmitted to the TBOX via the cloud, and the TBOX then forwards the command to the vehicle controller (VDC).

[0154] Upon receiving a forced start command from the user, the VDC controls the range extender to start according to the preset emergency power replenishment strategy, setting the power and duration accordingly. For example, the range extender is set to generate electricity at 10kW and maintain this power generation for 10 minutes, providing a short-term power replenishment to the battery. This process is precisely controlled by the VDC to ensure that the range extender's power generation and duration meet the preset emergency parameters, thus avoiding potential safety hazards from prolonged operation.

[0155] During emergency power replenishment, the VDC transmits the real-time operating status of the range extender and the charging status of the power battery to the user's mobile device APP via the TBOX. Users can view real-time information about the emergency power replenishment on the APP interface, such as "The range extender has been forcibly started, and the power battery is undergoing short-term emergency power replenishment, which is expected to stop in 10 minutes."

[0156] For example, in one scenario, suppose a vehicle is parked near a gas station with a low battery, and the user wants to provide some power to the battery in a short time. The system detects that the vehicle's battery is low and in a dangerous situation, generates a low battery alarm, and sends a message to the user's app indicating that automatic charging is not possible. The user selects the "Force Start Range Extender" emergency option in the app, triggering the emergency charging process.

[0157] Upon receiving an emergency command, the VDC controls the range extender to generate electricity at 10kW for 10 minutes, providing short-term charging support for the power battery. The charging status is fed back to the user's app in real time, displaying the emergency charging progress and allowing the user to monitor the vehicle's battery status.

[0158] Through the methods described in the above embodiments, this embodiment provides a technical means for users to forcibly start the range extender for short-term power replenishment through emergency control in emergency scenarios. This method can provide short-term power replenishment to the power battery while ensuring safety, guaranteeing basic vehicle functions, and giving users flexible battery management capabilities in emergency scenarios.

[0159] The following are embodiments of the apparatus described in this application, which can be used to execute the embodiments of the method described in this application. For details not disclosed in the apparatus embodiments of this application, please refer to the embodiments of the method described in this application.

[0160] Figure 6 This is a schematic diagram of the low battery protection device based on scene recognition provided in an embodiment of this application. Figure 6 As shown, the low battery protection device based on scene recognition includes:

[0161] The acquisition module 601 acquires image information and scene information around the vehicle, determines the target object based on the image information, and acquires the distance information between the target object and the vehicle.

[0162] Analysis module 602 generates a dangerous scene signal based on image information, scene information, and distance information, provided that the vehicle meets the preset dangerous scene judgment conditions.

[0163] The generation module 603 responds to the power replenishment request sent by the low-voltage battery management system, obtains the power battery level, and generates a low power protection request signal when the power battery level is lower than the second power threshold. The power replenishment request is sent when the low-voltage battery level is lower than the first power threshold.

[0164] The execution module 604 determines whether to recharge the power battery and low-voltage battery based on the dangerous scenario signal and the low-power protection request signal, and executes the corresponding low-power battery protection strategy.

[0165] In some embodiments, Figure 6The analysis module 602 processes the image information, scene information, and distance information. Based on the data processing results, if the vehicle meets any of the preset dangerous scene judgment conditions, a dangerous scene signal is generated. The dangerous scene judgment conditions include the relative distance between the target object and the vehicle being less than the preset safe distance, the camera being blocked or the image information being unavailable, and the vehicle being in a dangerous scene.

[0166] In some embodiments, Figure 6 In response to the power replenishment request, the generation module 603 wakes up the battery management system and requests to obtain the power battery power, and receives the power battery power returned by the battery management system; if the power battery power is lower than the preset second power threshold, it generates a low power protection request signal and sends a low voltage power-on request to the vehicle domain controller to wake up the vehicle and start the vehicle high voltage power-on.

[0167] In some embodiments, Figure 6 When the low-voltage battery charge is below a first charge threshold, the power battery charge is below a second charge threshold, and the vehicle is in a dangerous situation, the execution module 604 executes a first low battery charge protection strategy of not recharging the battery; when the low-voltage battery charge is below the first charge threshold, the power battery charge is below the second charge threshold, and the vehicle is in a non-dangerous situation, the execution module 604 executes a second low battery charge protection strategy of recharging the battery.

[0168] In some embodiments, Figure 6 The execution module 604 generates a low battery alarm signal and sends it to the vehicle communication module. The vehicle communication module then transmits the low battery alarm signal to the user's mobile device via the cloud to display a reminder message on the user's mobile device, notifying the user that the surrounding environment of the vehicle is unsafe and automatic charging cannot be performed.

[0169] In some embodiments, Figure 6 The execution module 604 controls the start of the range extender, which replenishes the power battery. While replenishing the power battery, it also replenishes the low-voltage battery through the battery management system. The real-time charging status of the power battery and the low-voltage battery is fed back to the user's mobile device so that the user can monitor the battery charging process.

[0170] In some embodiments, Figure 6 After sending a low battery alarm message to the user's mobile device, the execution module 604 responds to the user's operation of selecting to force start the range extender through an emergency control command, and controls the range extender to start according to the preset power and power generation time, so as to perform a preset charging operation to the power battery.

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

[0172] Figure 7 This is a schematic diagram of the structure of the electronic device 7 provided in an embodiment of this application. Figure 7 As shown, the electronic device 7 of this embodiment includes a processor 701, a memory 702, and a computer program 703 stored in the memory 702 and executable on the processor 701. When the processor 701 executes the computer program 703, it implements the steps in the various method embodiments described above. Alternatively, when the processor 701 executes the computer program 703, it implements the functions of each module / unit in the various device embodiments described above.

[0173] For example, computer program 703 may be divided into one or more modules / units, which are stored in memory 702 and executed by processor 701 to complete this application. The one or more modules / units may be a series of computer program instruction segments capable of performing a specific function, which describe the execution process of computer program 703 in electronic device 7.

[0174] Electronic device 7 can be a desktop computer, laptop, handheld computer, cloud server, or other electronic device. Electronic device 7 may include, but is not limited to, processor 701 and memory 702. Those skilled in the art will understand that... Figure 7 This is merely an example of electronic device 7 and does not constitute a limitation on electronic device 7. It may include more or fewer components than shown, or combine certain components, or different components. For example, electronic device may also include input / output devices, network access devices, buses, etc.

[0175] The processor 701 can be a Central Processing Unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor can be a microprocessor or any conventional processor.

[0176] The memory 702 can be an internal storage unit of the electronic device 7, such as a hard disk or RAM of the electronic device 7. The memory 702 can also be an external storage device of the electronic device 7, such as a plug-in hard disk, Smart Media Card (SMC), Secure Digital (SD) card, or Flash Card equipped on the electronic device 7. Furthermore, the memory 702 can include both internal and external storage units of the electronic device 7. The memory 702 is used to store computer programs and other programs and data required by the electronic device. The memory 702 can also be used to temporarily store data that has been output or will be output.

[0177] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the above-described division of functional units and modules is merely an example. In practical applications, the above functions can be assigned to different functional units and modules as needed, that is, the internal structure of the device can be divided into different functional units or modules to complete all or part of the functions described above. The functional units and modules in the embodiments can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit. Furthermore, the specific names of the functional units and modules are only for easy differentiation and are not intended to limit the scope of protection of this application. The specific working process of the units and modules in the above system can be referred to the corresponding process in the foregoing method embodiments, and will not be repeated here.

[0178] In the above embodiments, the descriptions of each embodiment have different focuses. For parts that are not described in detail or recorded in a certain embodiment, please refer to the relevant descriptions of other embodiments.

[0179] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. 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.

[0180] In the embodiments provided in this application, it should be understood that the disclosed apparatus / computer devices and methods can be implemented in other ways. For example, the apparatus / computer device 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. Multiple units or components may be combined or integrated into another system, 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, and the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0181] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0182] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0183] If integrated modules / units are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, all or part of the processes in the methods of the above embodiments can also be implemented by a computer program instructing related hardware. The computer program can be stored in a computer-readable storage medium, and when executed by a processor, it can implement the steps of the various method embodiments described above. The computer program may include computer program code, which can be in the form of source code, object code, executable files, or certain intermediate forms. Computer-readable media may include: any entity or device capable of carrying computer program code, recording media, USB flash drives, portable hard drives, magnetic disks, optical disks, computer memory, read-only memory (ROM), random access memory (RAM), electrical carrier signals, telecommunication signals, and software distribution media, etc.

[0184] The above embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application, and should all be included within the protection scope of this application.

Claims

1. A low battery protection method based on scene recognition, characterized in that, include: Acquire image and scene information around the vehicle, determine the target object based on the image information, and acquire the distance information between the target object and the vehicle; Based on the image information, the scene information, and the distance information, a dangerous scene signal is generated when it is determined that the vehicle meets the preset dangerous scene judgment conditions. In response to a power replenishment request sent by the low-voltage battery management system, the power battery level is obtained. If the power battery level is lower than a second power threshold, a low power protection request signal is generated. The power replenishment request is sent when the low-voltage battery level is lower than a first power threshold. Based on the dangerous scenario signal and the low battery protection request signal, determine whether to recharge the power battery and the low-voltage battery, and execute the corresponding low battery protection strategy.

2. The method according to claim 1, characterized in that, The step of generating a dangerous scene signal based on the image information, the scene information, and the distance information, when determining that the vehicle meets preset dangerous scene judgment conditions, includes: The image information, the scene information, and the distance information are processed. Based on the data processing results, if the vehicle meets any of the preset dangerous scene determination conditions, a dangerous scene signal is generated. The dangerous scene determination conditions include the relative distance between the target object and the vehicle being less than a preset safe distance, the camera being blocked or the image information being unavailable, and the vehicle being in a dangerous scene.

3. The method according to claim 1, characterized in that, The step of acquiring the power battery charge and generating a low battery protection request signal when the power battery charge is lower than a second charge threshold includes: In response to the power replenishment request, the battery management system is woken up and requests to obtain the power battery charge, and the power battery charge returned by the battery management system is received. If the power battery charge is lower than the preset second charge threshold, a low charge protection request signal is generated, and a low voltage power-on request is sent to the vehicle domain controller to wake up the vehicle and start the vehicle high voltage power-on.

4. The method according to claim 1, characterized in that, The step of determining whether to recharge the power battery and the low-voltage battery, and executing the corresponding low battery protection strategy, includes: When the low-voltage battery charge is below a first charge threshold, the power battery charge is below a second charge threshold, and the vehicle is in a dangerous situation, a first low battery protection strategy of not recharging the battery is implemented. When the low-voltage battery charge is below a first charge threshold, the power battery charge is below a second charge threshold, and the vehicle is in a non-hazardous situation, a second low-charge protection strategy to replenish the battery is implemented.

5. The method according to claim 4, characterized in that, The first low battery protection strategy that does not recharge the battery includes: Generate a low battery alarm signal and send the low battery alarm signal to the vehicle communication module; The vehicle communication module transmits the low battery alarm signal to the user's mobile device via the cloud, so that a reminder message is displayed on the user's mobile device, notifying the user that the surrounding environment of the vehicle is unsafe and automatic charging cannot be performed.

6. The method according to claim 4, characterized in that, The second battery low-power protection strategy for replenishing the battery includes: The range extender is started and used to replenish the power battery. At the same time, the low-voltage battery is replenished through the battery management system. The real-time charging status of the power battery and the low-voltage battery is fed back to the user's mobile device so that the user can monitor the battery charging process.

7. The method according to claim 5, characterized in that, The method further includes: After sending the low battery alarm information to the user's mobile device, in response to the user's operation of selecting to force start the range extender through an emergency control command, the range extender is controlled to start according to the preset power and power generation time, so as to perform a preset charging operation on the power battery.

8. A low battery protection device based on scene recognition, characterized in that, include: The acquisition module acquires image information and scene information around the vehicle, determines the target object based on the image information, and acquires the distance information between the target object and the vehicle. The analysis module generates a dangerous scene signal based on the image information, the scene information, and the distance information, provided that the vehicle meets the preset dangerous scene judgment conditions. The generation module, in response to a power replenishment request sent by the low-voltage battery management system, obtains the power battery level and generates a low-power protection request signal when the power battery level is lower than a second power threshold. The power replenishment request is sent when the low-voltage battery level is lower than a first power threshold. The execution module determines whether to recharge the power battery and the low-voltage battery based on the dangerous scenario signal and the low-power protection request signal, and executes the corresponding low-power battery protection strategy.

9. An electronic device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the computer program, it implements the steps of the method as described in any one of claims 1 to 7.

10. A computer-readable storage medium storing a computer program, characterized in that, When the computer program is executed by a processor, it implements the steps of the method as described in any one of claims 1 to 7.

Images