Control method and device of vehicle power battery, and electronic equipment

Abstract

A control method and device of a vehicle power battery and an electronic device are disclosed, and relate to the technical fields of new energy vehicles and Internet of Vehicles. The method comprises the following steps: first, collecting, by a TBOX, multi-dimensional state parameters such as battery voltage, temperature, SOC, etc. in real time and uploading the parameters to the cloud; when the cloud monitors that the vehicle satisfies a first determination condition and the high-voltage power supply system satisfies a starting condition, controlling the vehicle to enter a discharge mode requested by a first instruction. When the cloud monitors that the vehicle satisfies the first determination condition and the high-voltage power supply system satisfies the starting condition, the vehicle is controlled to enter the discharge mode requested by the first instruction. In this way, the residual electric quantity can be safely utilized in an extremely low electric quantity condition, and the vehicle is prevented from breaking down. Meanwhile, the entire process is ensured to be safe and controllable through mechanisms such as usage frequency management, double timeout protection and multi-level safety monitoring, and the driving safety and user experience are improved.

Description

Technical Field

[0001] This application relates to the fields of new energy vehicles and vehicle networking technology, and more specifically, to a control method, device, and electronic equipment for a vehicle power battery. Background Technology

[0002] With the rapid growth in the number of new energy vehicles, users' demands for driving safety and range assurance in extreme low-battery scenarios are becoming increasingly urgent. New energy vehicles automatically cut off power output when the displayed battery level reaches zero, meaning users cannot continue driving using the remaining battery power even when they are close to charging facilities. This causes significant inconvenience, especially in special scenarios such as urban traffic congestion and highways, where vehicle breakdowns due to depleted battery power are frequent, severely impacting traffic efficiency and posing safety hazards. Vehicle-mounted BMS (Battery Management System) often employs fixed threshold control strategies, lacking cloud-based collaboration and intelligent decision-making capabilities, and thus cannot safely utilize the remaining battery power when the battery is depleted.

[0003] Therefore, how to achieve safe emergency driving under extremely low battery conditions through cloud-based decision-making and collaborative deep discharge remote control, thereby reducing breakdowns and improving driving safety and user satisfaction, has become an urgent problem to be solved. Summary of the Invention

[0004] In view of this, embodiments of this application propose a control method, device, and electronic device for a vehicle power battery. By using mechanisms such as cycle management, dual timeout protection, and multi-level safety monitoring, the entire process is ensured to be safe and controllable. This achieves the effective utilization of hidden power to avoid vehicle breakdowns while ensuring battery life, significantly improving driving safety and user experience.

[0005] The following technical solution is adopted in this application.

[0006] According to a first aspect of the embodiments of this application, a control method for a vehicle power battery is provided, applied to a vehicle-side device, wherein the vehicle-side device communicates with a cloud, the method comprising: In response to a first instruction sent from the cloud, the operating status of the vehicle's high-voltage power supply system is obtained; the first instruction is generated based on the vehicle meeting a first determination condition; the first determination condition indicates that the vehicle's battery status supports the vehicle executing the first instruction, and the number of successful executions of the first instruction by the vehicle has not exceeded a first threshold; based on the operating status, it is determined that the high-voltage power supply system meets the start-up conditions, and the vehicle is controlled to execute the discharge mode requested by the first instruction.

[0007] In some embodiments, prior to the first instruction sent in response to the cloud, the following is included: Obtain the vehicle's battery status; the battery status includes: state of charge and battery temperature; send the vehicle's battery status to the cloud.

[0008] In some embodiments, prior to the first instruction sent in response to the cloud, the method further includes: Upon receiving the first instruction sent by the cloud, send a success message for receiving the first instruction to the cloud.

[0009] In some embodiments, after the controlled vehicle executes the discharge mode requested by the first instruction, the following is included: Record the startup duration of the vehicle initiating the discharge mode; send the startup duration to the cloud.

[0010] According to a second aspect of the embodiments of this application, another method for controlling a vehicle power battery is provided, applied in a cloud, wherein the cloud communicates with the vehicle, the method comprising: Obtain the unique identifier of the vehicle; receive the battery status of the vehicle; the battery status includes: state of charge and battery temperature; determine whether the vehicle meets a first determination condition by matching the unique identifier of the vehicle with the identifier stored in the cloud; the first determination condition includes that the deviation value of the state of charge in the battery status of the vehicle does not exceed a first deviation threshold and the battery temperature is not lower than a second temperature threshold; send a first instruction to the vehicle if the vehicle meets the first determination condition.

[0011] In some embodiments, after sending the first instruction to the vehicle, the following is included: Record the transmission duration of the first instruction; receive the start duration sent by the vehicle; and determine the execution result of the vehicle's discharge mode requesting the first instruction based on the start duration and the transmission duration.

[0012] In some embodiments, determining the execution result of the discharge mode of the vehicle executing the first instruction request based on the startup duration and the transmission duration includes: If the transmission duration exceeds a first time threshold and no successful reception instruction is received from the vehicle, the execution result is determined to be execution failure, and the execution count remains unchanged. If the transmission duration does not exceed the first time threshold and a successful reception instruction is received from the vehicle, and the startup duration exceeds a second time threshold, the execution result is determined to be execution timeout, and the execution count remains unchanged. If the transmission duration does not exceed the first time threshold and a successful reception instruction is received from the vehicle, and the startup duration does not exceed the second time threshold, the execution result is determined to be execution success, and the execution count is accumulated once.

[0013] According to a third aspect of the embodiments of this application, a control device for a vehicle power battery is provided, applied at a vehicle end, the vehicle end communicating with a cloud, the device comprising: A first processing module is configured to respond to a first instruction sent from the cloud and determine whether the high-voltage power supply system of the vehicle meets the start-up conditions. The first instruction is generated based on the vehicle meeting a first determination condition. The first determination condition indicates that the vehicle's battery status supports the vehicle executing the first instruction and that the number of successful executions of the first instruction by the vehicle has not exceeded a first threshold. A control module is configured to determine that the high-voltage power supply system meets the start-up conditions based on the working status and control the vehicle to execute the discharge mode requested by the first instruction.

[0014] According to a fourth aspect of the embodiments of this application, another control device for a vehicle power battery is provided, applied in a cloud, wherein the cloud communicates with the vehicle, the device comprising: The system includes an acquisition module for acquiring the vehicle's unique identifier; a receiving module for receiving the vehicle's battery status, including state of charge and battery temperature; a second processing module for matching the vehicle's unique identifier with identifiers stored in the cloud to determine whether the vehicle meets a first determination condition; the first determination condition includes the deviation value of the vehicle's state of charge not exceeding a first deviation threshold and the battery temperature not lower than a second temperature threshold; and a sending module for sending a first instruction to the vehicle based on whether the vehicle meets the first determination condition.

[0015] According to a fifth aspect of the embodiments of this application, an electronic device is provided, the electronic device comprising: a processor; and a memory storing computer-readable instructions, wherein when the computer-readable instructions are executed by the processor, the control method described above is implemented.

[0016] In this application's solution, the vehicle status and the number of times the deep discharge function is available are dynamically bound to the cloud through real-time interaction between the cloud and the VCU and TBOX. After the cloud sends the first command to the vehicle, when the cloud detects that the vehicle meets the first judgment condition and the high-voltage power supply system meets the start-up condition, it controls the vehicle to enter the discharge mode requested by the first command. This enables the safe use of residual power in extremely low battery situations, preventing the vehicle from breaking down. When the cloud detects that the vehicle does not meet the first judgment condition or the high-voltage power supply system does not meet the start-up condition, the cloud determines that the discharge mode requested by the first command is unavailable, and simultaneously locks the issuance of the first command, controlling the vehicle to prevent it from entering the discharge mode requested by the first command. This further improves the vehicle's driving safety at the critical point of battery depletion and significantly enhances the user experience.

[0017] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and do not limit this application. Attached Figure Description

[0018] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application. It is obvious that the drawings described below are merely some embodiments of this application, and those skilled in the art can obtain other drawings based on these drawings without any inventive effort.

[0019] Figure 1 This is a schematic diagram of a vehicle power battery control system provided in an embodiment of this application.

[0020] Figure 2 This is a flowchart illustrating a control method for a vehicle power battery provided in an embodiment of this application.

[0021] Figure 3 This is a flowchart illustrating a method for obtaining battery status and startup duration provided in an embodiment of this application.

[0022] Figure 4 This is a schematic diagram illustrating the control process of another vehicle power battery provided in an embodiment of this application.

[0023] Figure 5 This is a flowchart illustrating a method for determining an execution result provided in an embodiment of this application.

[0024] Figure 6 This is a schematic diagram of a cloud-based remote control process provided in an embodiment of this application.

[0025] Figure 7 This is a timing diagram of a cloud-based remotely controlled deep discharge method provided in an embodiment of this application.

[0026] Figure 8 This is a schematic diagram of the structure of a control device for a vehicle power battery provided in an embodiment of this application.

[0027] Figure 9 This is a schematic diagram of another vehicle power battery control device provided in an embodiment of this application.

[0028] Figure 10 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application.

[0029] The accompanying drawings have illustrated specific embodiments of this application, which will be described in more detail below. These drawings and descriptions are not intended to limit the scope of the concept in any way, but rather to illustrate the concept of this application to those skilled in the art through specific embodiments. Detailed Implementation

[0030] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application as detailed in the appended claims.

[0031] In conventional technologies, solutions for driving with low battery power suffer from three main limitations: First, in-vehicle BMS systems employ fixed voltage threshold control strategies, failing to dynamically adjust based on real-time battery status, ambient temperature, and other parameters, thus lacking intelligent decision-making capabilities. Second, existing systems lack effective cloud platform intervention mechanisms, hindering remote activation and control, leaving users completely passive in emergency situations. Third, the collaborative control architecture between the vehicle and the cloud platform is incomplete, making it difficult to guarantee the real-time performance and reliability of command transmission. Therefore, safe emergency driving under extremely low battery conditions is impossible, potentially leading to vehicle breakdowns and severely impacting driving safety and user experience.

[0032] The vehicle power battery control method provided in this application aims to solve the above-mentioned technical problems of the prior art.

[0033] The technical solution of this application and how it solves the above-mentioned technical problems will be described in detail below with specific embodiments. These specific embodiments can be combined with each other, and the same or similar concepts or processes may not be described again in some embodiments. The embodiments of this application will be described below with reference to the accompanying drawings.

[0034] Figure 1 This is a schematic diagram of a vehicle power battery control system provided in an embodiment of this application. Figure 1 As shown, the vehicle power battery control system 100 provided in this application embodiment includes a cloud service platform 110 and a control unit 120; wherein, the control unit 120 includes a communication module 121, a vehicle controller 122, a battery management module 123, and a motor controller 124.

[0035] In one alternative implementation, the cloud service platform 110 and the control unit 120 refer to software units or modules. Specifically, the cloud service platform 110 generates and issues a first instruction based on preset control logic, and the second module 102 receives the first instruction and executes it according to the preset control logic.

[0036] In another alternative implementation, the cloud service platform 110 and the control unit 120 refer to hardware devices.

[0037] For example, cloud service platform 110 may include, but is not limited to, electronic devices with data processing capabilities such as servers or data centers.

[0038] As another example, the control unit 120 may include, but is not limited to, an on-board computer.

[0039] Optionally, the cloud service platform 110 and the control unit 120 communicate via the communication module 120. This communication connection may include, but is not limited to, transmission control protocol / internet protocol (TCP / IP), or remote direct memory access (RDMA) over converged ethernet (RoCE) network protocol.

[0040] The following is combined with Figure 1 The vehicle power battery control system 100 shown illustrates the vehicle power battery control method provided in this application embodiment: the vehicle controller 122 collects the current battery status (state of charge, battery temperature) of the vehicle in real time through the battery management module 123 and obtains the vehicle's unique identifier (i.e., VIN information). The vehicle controller 122 uploads the battery status and unique identifier to the cloud service platform 110 through the communication module 121.

[0041] Secondly, the cloud service platform 110 receives the unique identifier and battery status, matches the unique identifier with the locally stored identifier, and determines whether the vehicle meets the first determination condition based on the battery status. The first determination condition includes that the deviation value of the state of charge does not exceed the first deviation threshold, the battery temperature is not lower than the second temperature threshold, and the number of times the vehicle successfully executes the first command does not exceed the first threshold. In addition, the cloud service platform 110 sends the first command to the control unit 120 based on the vehicle meeting the first determination condition.

[0042] Furthermore, upon receiving the first instruction, the vehicle controller 130 sends a successful receipt instruction to the cloud service platform 110 via the communication module 121. Simultaneously, in response to the first instruction, the vehicle controller 130 determines the operating status of the vehicle's high-voltage power supply system via the motor controller 124. Furthermore, based on the operating status, the vehicle controller 130 determines that the high-voltage power supply system meets the startup conditions and controls the battery management module 123 and the motor controller 124 to execute the discharge mode requested by the first instruction.

[0043] Below Figure 1 Based on the vehicle power battery control system 100 shown, the control method for the vehicle power battery provided in the embodiments of this application will be further described, such as... Figure 2 The diagram illustrates a flow chart of a control method for a vehicle power battery. In a specific embodiment, this control of the vehicle power battery can be applied to, for example... Figure 8 The diagram shows a vehicle power battery control device 600 and an electronic device 800 configured with a vehicle power battery control device 600. Figure 10 The specific process of the embodiments of this application will be described below. Of course, it is understood that this method can be executed by a cloud server with computing power. The following will focus on... Figure 2 The process shown is described in detail. The control method of the vehicle power battery may specifically include the following steps 201 to 202.

[0044] Step 201: In response to the first instruction sent from the cloud, obtain the working status of the vehicle's high-voltage power supply system; the first instruction is generated based on the vehicle meeting a first determination condition; the first determination condition is used to indicate that: the vehicle's battery status supports the vehicle executing the first instruction, and the number of times the vehicle successfully executes the first instruction has not exceeded a first threshold.

[0045] In this embodiment, the first instruction is a deep discharge request instruction generated in the cloud and sent to the vehicle; the working state of the high-voltage power supply system includes the overall operating conditions of the vehicle's high-voltage circuit being powered on and off, relays being switched on and off, high-voltage load operation, and fault protection lockout.

[0046] In this embodiment of the application, the first determination condition is used by the cloud to determine whether the current vehicle status meets the conditions for generating the first instruction, including at least: the vehicle's battery status supports the vehicle to execute the first instruction, and the number of times the vehicle successfully executes the first instruction does not exceed a first threshold.

[0047] The vehicle's battery status supporting the execution of the first command can be understood as the deviation value of the state of charge in the battery status not exceeding a first deviation threshold and the battery temperature not lower than a second temperature threshold. The first threshold can be understood as the number of times the vehicle can execute the first command. For example, the first threshold can be set to 15 times.

[0048] For example, in order to safely utilize the remaining power to avoid vehicle breakdown under extremely low power conditions, a highly efficient collaborative system between the cloud and the vehicle has been built to achieve intelligent remote controllable deep discharge, high-voltage safe power-on, low-energy limited driving, and active fault exit control of the entire process in scenarios of extremely low power and normal driving power depletion, while taking into account both emergency vehicle needs and power battery safety protection.

[0049] In one alternative example, combining Figure 7 The diagram shown illustrates the timing of remote deep discharge control via the cloud. The cloud, acting as the decision-making layer of the entire system, receives vehicle status data periodically uploaded by the vehicle's TBOX in real time. This data includes at least the state of charge (SOC) of the power battery, the highest / lowest voltage of individual cells, battery temperature, the status of the high-voltage power supply system, vehicle fault information, and driving condition information. The cloud-based evaluation model then comprehensively determines whether the vehicle currently meets the conditions for performing deep discharge.

[0050] Furthermore, when the vehicle meets the conditions for performing deep discharge, the cloud generates the first instruction and sends it to the vehicle's TBOX, while automatically counting and managing the remaining available number of deep discharge operations for the vehicle.

[0051] For example, when the vehicle's TBOX receives the first instruction from the cloud, it performs message verification and protocol conversion, and then forwards it synchronously to the vehicle control unit (VCU) and battery management system (BMS) to ensure the real-time, security and reliability of cloud control instructions and vehicle status data transmission.

[0052] For example, the VCU, as the control layer at the vehicle end, after receiving the first instruction forwarded by the TBOX, first verifies the power-on conditions such as the working status of the high-voltage power supply system, the fault level of the whole vehicle, the braking signal, and the gear status.

[0053] Step 202: Based on the operating status, determine that the high-voltage power supply system meets the startup conditions, and control the vehicle to execute the discharge mode requested by the first instruction.

[0054] In one alternative example, continue combining Figure 7 The timing diagram of the cloud-based remote control deep discharge is shown. When the VCU determines that the working status of the high-voltage power supply system, the vehicle fault level, the braking signal, the gear status and other power-on conditions are met, it sends a high-voltage power-on request command to the BMS and monitors the activation and deactivation status of the BMS main negative relay, pre-charge relay and main positive relay in real time, and controls the high-voltage power-on timing logic and safety interlock throughout the process.

[0055] Furthermore, after confirming that the main positive relay is reliably closed and the high-voltage circuit is powered on, the VCU executes a 150ms delay control logic, successively sending the working enable and target voltage regulation commands to the DC-DC converter, and at the same time outputting the drive system enable signal to the motor controller MCU, thus orderly activating the vehicle's low-voltage power supply and power drive system.

[0056] In addition, after the vehicle enters deep discharge mode, the VCU continuously collects feedback signals such as the output voltage / current of the DC-DC converter, the working status of the MCU, the vehicle speed, and the accelerator pedal opening in real time to ensure stable system operation. At this time, in order to ensure that the vehicle is always in a low-energy driving state, a low-battery safety management strategy will be triggered. On the one hand, it will block the start-up requests of high-voltage comfort accessories such as the air conditioning compressor and the heater, and on the other hand, it will limit the maximum output torque of the motor and the maximum driving speed of the vehicle to constrain the vehicle's acceleration performance and ensure driving safety.

[0057] For example, the BMS monitors the battery status in real time, receives the deep discharge enable command forwarded by the TBOX and the VCU high voltage power-on request command, and then completes the power-on of the high voltage power supply system in the standard sequence of closing the main negative relay, the precharge relay and the main positive relay, and feeds back the status of each relay to the VCU in real time.

[0058] Meanwhile, throughout the entire operation of the high-voltage power supply system, the BMS continuously monitors the voltage of individual cells, battery temperature, charging and discharging current, and fault level. It sets up multiple exit protection logics, that is, once any of the following conditions are triggered: a level 3 or above fault in the whole vehicle, the voltage of an individual cell reaches the deep discharge protection threshold, the vehicle is connected to the charging gun and enters the charging state, or a high-voltage reduction command is received from the VCU, the system immediately exits the deep discharge mode, disconnects the high-voltage relays step by step, cuts off the high-voltage circuit, and forces the whole vehicle to reduce the high voltage, so as to avoid damage risks such as over-discharge, thermal runaway and irreversible capacity decay of the power battery.

[0059] For example, after receiving the delayed enable signal from the VCU, the DC-DC low-voltage converter performs a high-voltage DC to low-voltage DC conversion, stably converting the high-voltage power from the battery to a 12V low-voltage power supply for the vehicle. This continuously provides stable low-voltage power to the body controller, instrument panel, lights, TBOX, and various electronic control units, ensuring uninterrupted normal operation of the vehicle's low-voltage power supply system under deep discharge mode. Simultaneously, the DC-DC converter feeds back its own operating status, output voltage, output current, and fault status to the VCU in real time, providing data support for VCU vehicle management and high-voltage circuit fault diagnosis.

[0060] For example, after receiving the enable signal from the VCU, the MCU motor controller completes the motor system self-test and feeds back the high-voltage standby status to the VCU, confirming that the vehicle's power system is ready to operate. At the same time, it receives the gear signal and target torque command issued by the VCU in real time, and drives the motor to operate in combination with the current vehicle speed, pedal opening and other operating parameters, supporting the vehicle to maintain a low-energy driving state and drive smoothly at low speed in emergencies. In addition, the MCU uploads data such as voltage, motor speed, operating temperature and fault information to the vehicle's CAN bus in real time for monitoring by the VCU, BMS and cloud, realizing full-domain perception of the power system status.

[0061] In this embodiment, firstly, the vehicle status, location, and number of times the deep discharge function is available are dynamically bound to the cloud through real-time interaction between the cloud and the VCU and TBOX. When the cloud detects that the vehicle meets the first judgment condition and the high-voltage power supply system meets the start-up condition, the VCU controls the vehicle to enter the deep discharge mode, enabling the safe use of residual power in extremely low battery conditions and preventing the vehicle from breaking down. When the cloud detects that the vehicle does not meet the first judgment condition or the high-voltage power supply system does not meet the start-up condition, the cloud determines that the deep discharge mode is unavailable and locks the first command issuance. The VCU controls the vehicle to prevent it from entering the deep discharge mode, further improving the driving safety of the vehicle at the critical point of power depletion and significantly enhancing the user experience.

[0062] Building upon the foregoing, and prior to responding to the first instruction sent from the cloud and after the vehicle executes the discharge mode requested by the first instruction, this application provides an optional implementation method, such as... Figure 3 The flowchart shown is a method for obtaining battery status and startup time, which may specifically include the following steps 301 to 307.

[0063] Step 301: Obtain the battery status of the vehicle; the battery status includes: state of charge and battery temperature.

[0064] For example, the vehicle control unit (VCU) collects and obtains the operating status parameters of the vehicle's power battery in real time through the battery management system (BMS); the battery status specifically includes at least the battery state of charge (SOC) and battery pack temperature, and simultaneously correlates auxiliary information such as cell voltage and fault status as data support.

[0065] Step 302: Send the vehicle's battery status to the cloud.

[0066] For example, the vehicle control unit (VCU) encapsulates and encrypts battery status parameters, including state of charge and battery temperature, through the TBOX according to a preset communication cycle, and uploads them to the cloud in real time via a wireless network, providing accurate vehicle-side data for cloud decision-making.

[0067] Step 303: Based on the first instruction received from the cloud, send a success message for receiving the first instruction to the cloud.

[0068] For example, when the TBOX successfully receives the first deep discharge control command sent by the cloud, it can first verify the validity of the command message. After the verification is successful, the vehicle end immediately sends feedback information to the cloud, that is, sends a first command reception receipt command to the cloud, informing the cloud that it has reliably received and is ready to respond to this deep discharge request.

[0069] Step 304: In response to the first instruction sent from the cloud, obtain the working status of the vehicle's high-voltage power supply system; the first instruction is generated based on the vehicle meeting a first determination condition; the first determination condition is used to indicate that: the vehicle's battery status supports the vehicle executing the first instruction, and the number of times the vehicle successfully executes the first instruction has not exceeded a first threshold.

[0070] Step 305: Based on the operating status, determine that the high-voltage power supply system meets the startup conditions, and control the vehicle to execute the discharge mode requested by the first instruction.

[0071] Step 306: Record the start-up time of the vehicle starting the discharge mode.

[0072] For example, the vehicle control unit (VCU) and battery management system (BMS) work together to record the start-up time of the vehicle performing the start-up deep discharge mode operation. Specifically, the time can be started from the moment the vehicle responds to the first command from the cloud, completes the high voltage power-on, and officially enters the start-up deep discharge operation mode. The actual operation time during the start-up action is continuously accumulated to ensure that the whole process is safe and controllable and to protect the battery life.

[0073] Step 307: Send the startup duration to the cloud.

[0074] Similarly, the vehicle control unit (VCU) sends the startup duration to the cloud via TBOX, providing data support for cloud-based decision-making.

[0075] The specific steps of steps 304 to 305 can be found in steps 201 to 202, and will not be repeated here.

[0076] In this embodiment, by monitoring the vehicle's battery status in real time and limiting the start-up time when the vehicle executes deep discharge mode, the safety of the entire control process on the vehicle side is ensured, thereby enabling the effective utilization of hidden power while ensuring battery life.

[0077] Below Figure 1 Based on the first module 101 and the second module 102 shown, the control method for the vehicle power battery provided in the embodiments of this application will be further described, such as... Figure 4 The flowchart shown illustrates another method for controlling a vehicle power battery. In a specific embodiment, this control of the vehicle power battery can be applied to, for example... Figure 9 The diagram shows a control device 700 for another type of vehicle power battery and an electronic device 800 equipped with the control device 700 for another type of vehicle power battery. Figure 10The specific process of the embodiments of this application will be described below. Of course, it is understood that this method can be executed by a cloud server with computing power. The following will focus on... Figure 4 The process shown is described in detail. The control method of the vehicle power battery may specifically include the following steps 401 to 404.

[0078] Step 401: Obtain the unique identifier of the vehicle.

[0079] In this embodiment, the unique identifier of a vehicle is its VIN (Vehicle Identification Number), through which information such as maintenance records and accident records of the vehicle can be obtained. The cloud obtains the vehicle's unique identification code (VIN) from the vehicle's terminal, which serves as the sole basis for vehicle identification, data binding, and access control.

[0080] Step 402: Receive the battery status of the vehicle; the battery status includes: state of charge and battery temperature.

[0081] For example, combined with Figure 6 The diagram illustrates a cloud-based remote control process. The cloud receives the vehicle's battery status uploaded by the TBOX in real time and combines it with the vehicle's unique identifier obtained in real time. The cloud database is then used to search and match the vehicle's identity identifiers stored in the database to complete the vehicle identity verification.

[0082] Step 403: Based on the unique identifier of the vehicle and the identifier stored in the cloud, determine whether the vehicle meets the first determination condition; the first determination condition includes that the deviation value of the state of charge in the battery state of the vehicle does not exceed a first deviation threshold and the battery temperature is not lower than a second temperature threshold.

[0083] For example, based on the successful matching of the vehicle's unique identifier with the vehicle's identity identifier in the cloud database, a comprehensive judgment is made according to preset control logic to determine whether the vehicle meets the first judgment condition. Specifically, on the one hand, the SOC deviation between the real-time estimated value and the actual value of the vehicle's battery state of charge does not exceed the first deviation threshold calibrated by the system, ensuring accurate power estimation; on the other hand, the current battery temperature must not be lower than the second temperature threshold calibrated by the system, avoiding risks such as battery aging caused by deep discharge in low-temperature environments.

[0084] Step 404: Based on the fact that the vehicle meets the first determination condition, send a first instruction to the vehicle.

[0085] For example, after verifying the identity and the first judgment condition, the cloud confirms that the vehicle simultaneously meets the requirements of SOC deviation, battery temperature, and no other faults or abnormal states. Then, it generates and sends a deep discharge request command to the TBOX to trigger the subsequent high-voltage power-on and deep discharge mode execution on the vehicle side.

[0086] If the cloud sends a deep discharge request command to the vehicle but does not receive a successful reception response from the vehicle within 30 seconds, the deep discharge operation is deemed to have failed and the cloud will not accumulate the number of attempts.

[0087] In addition, if the cloud sends a deep discharge request command to the vehicle and receives a successful reception feedback from the vehicle within 30 seconds, it will send a deep discharge request command to the vehicle. If the vehicle does not enter the deep discharge mode within 3 minutes, it will be determined that the deep discharge execution timed out and the cloud will not accumulate the execution count. If the vehicle enters the deep discharge mode within 3 minutes, it will be determined that the deep discharge execution was successful and the cloud will accumulate 1 execution count.

[0088] In this embodiment, the cloud determines that the vehicle's high-voltage power supply system meets the working conditions and that the number of successful deep discharges performed by the vehicle has not exceeded a first threshold. It then sends a deep discharge request command to the vehicle to control the vehicle to enter the deep discharge mode. This solves the technical problem that the vehicle's battery management lacks collaborative decision-making capabilities with the cloud and cannot safely utilize the remaining battery power when the battery is depleted. It achieves the technical effect of effectively utilizing hidden power to avoid vehicle breakdowns while ensuring battery life.

[0089] Based on the above, after sending the first instruction to the vehicle, this application embodiment provides an optional implementation method, such as... Figure 5 The flowchart shown is a method for determining the execution result, which may specifically include the following steps 501 to 507.

[0090] Step 501: Obtain the unique identifier of the vehicle.

[0091] Step 502: Receive the battery status of the vehicle; the battery status includes: state of charge and battery temperature.

[0092] Step 503: Based on the unique identifier of the vehicle and the identifier stored in the cloud, determine whether the vehicle meets the first determination condition; the first determination condition includes the deviation value of the state of charge in the battery state of the vehicle not exceeding a first deviation threshold and the battery temperature not lower than a second temperature threshold.

[0093] Step 504: Based on the fact that the vehicle meets the first determination condition, send a first instruction to the vehicle.

[0094] Step 505: Record the duration of sending the first instruction.

[0095] For example, after the first instruction (deep discharge instruction) is issued in the cloud, the time of issuance of the instruction is recorded in real time and the duration of instruction transmission is continuously counted.

[0096] Step 506: Receive the start-up duration sent by the vehicle.

[0097] For example, the cloud receives the vehicle's deep discharge mode startup duration uploaded by the vehicle terminal.

[0098] Step 507: Determine the execution result of the vehicle's discharge mode for executing the first instruction request based on the startup duration and the transmission duration.

[0099] For example, the cloud performs correlation comparison and logic control based on the sending duration of the first instruction and the start duration of the deep discharge mode, thereby determining the final execution result of the vehicle's response to the deep discharge mode requested by the first instruction.

[0100] Regarding step 507, how to determine the execution result of the vehicle's execution of the discharge mode requested by the first instruction, this application embodiment provides an optional implementation method, which may specifically include the following steps 517 to 537.

[0101] Step 517: If the sending time exceeds the first time threshold and no successful reception instruction is received from the vehicle, the execution result is determined to be execution failure and the number of executions remains unchanged.

[0102] For example, if the transmission time of the first instruction exceeds the first time threshold (30s) and the cloud does not receive the first instruction reception success instruction from the vehicle, the cloud determines that the deep discharge instruction has failed to be executed, does not deduct the number of available functions, and the remaining number of times the vehicle can execute the deep discharge mode remains unchanged.

[0103] Step 527: When the sending duration does not exceed the first time threshold and a successful reception instruction is received from the vehicle, the execution result is determined to be execution timeout and the number of executions remains unchanged based on the fact that the startup duration exceeds the second time threshold.

[0104] For example, if the sending time of the first instruction does not exceed the first time threshold (30s), and the cloud has received the successful reception instruction from the vehicle, but the startup time reported by the vehicle exceeds the preset third time threshold (3min), the cloud determines that the deep discharge request has timed out and is considered as not having effectively completed mode activation. Similarly, no function availability count will be deducted, and the vehicle availability count will remain unchanged.

[0105] Step 537: When the sending duration does not exceed the first time threshold and a successful reception instruction is received from the vehicle, the execution result is determined to be successful and the execution count is accumulated once, based on the fact that the startup duration does not exceed the second time threshold.

[0106] For example, if the sending time of the first instruction does not exceed the first time threshold (30s), the cloud has received the vehicle terminal's successful reception instruction, and the startup time reported by the vehicle terminal does not exceed the third time threshold (3min), it means that the vehicle terminal has responded to the instruction normally and successfully activated the deep discharge mode within the specified time limit. The platform determines that the request was executed successfully, deducts one execution count for the deep discharge function of the vehicle, and updates the remaining available count record in the background.

[0107] Optionally, the entire process of issuing, responding to, starting, and executing this command can be logged in the cloud for future traceability and control.

[0108] The specific steps of steps 501 to 504 can be found in steps 401 to 404, and will not be repeated here.

[0109] Based on the above, such as Figure 7 The diagram illustrates a timing sequence for remotely controlled deep discharge via the cloud. Further explanation is provided in conjunction with the vehicle-side and cloud-side functionalities. The cloud-side primarily performs the following functions: inputting vehicle VIN information and binding the vehicle to the platform; receiving vehicle data and determining whether the current vehicle status meets deep discharge conditions (such as battery SOC, minimum single-cell voltage, fault information, etc.), and upon confirmation of feasibility, issuing a deep discharge request command to the vehicle-side TBOX; recording and managing the available number of deep discharge functions for each vehicle (not a fixed value, determined by the BMS battery status), with the available number decreasing by 1 each time a command is successfully issued and the vehicle enters the start-up state.

[0110] It is important to note that once the cloud sends a request and detects that the vehicle has entered the starting state from a non-starting state, the function is considered to be successfully activated and one available attempt is deducted. To ensure reliability, the cloud has a timeout mechanism. If the vehicle does not enter the starting state within 3 minutes after the command is sent, it is considered a timeout, and the available attempts will not be deducted. In addition, multiple requests within 30 seconds will only be responded to once to prevent accidental operation.

[0111] The main functions of TBOX include: receiving deep discharge commands from the cloud and forwarding them to the vehicle control unit (VCU) and battery management system (BMS) to trigger the vehicle to receive and forward cloud commands; and collecting and uploading vehicle status data (such as battery voltage, temperature, fault codes, etc.) to the cloud in real time.

[0112] The TBOX acts as a communication hub, ensuring the real-time performance and stability of the transmission of cloud commands and vehicle status data between the wireless network and the vehicle's wired network.

[0113] Furthermore, the main functions of the DC-DC converter include: receiving the enable signal and target operating voltage signal from the VCU, and issuing a key command after the VCU controls the high-voltage relay to close and delays for 150ms; after receiving the enable signal, the DC-DC converter converts the high-voltage DC power from the power battery into the low-voltage DC power required by the vehicle, ensuring that the vehicle's low-voltage system can operate normally in deep discharge mode; and feeding back the current operating mode, actual output voltage, and output current signals to the VCU in real time, so that the VCU can monitor the status of the entire high-voltage system.

[0114] Furthermore, the main functions of the VCU include: receiving the cloud-based deep discharge request command forwarded by the TBOX; determining whether the high-voltage power supply system meets the conditions for high-voltage connection, and if so, sending a high-voltage connection command to the BMS and monitoring the status signals fed back by the BMS to ensure the safe power-on of the high-voltage system; after confirming the closure of the main positive relay, sending an enable signal to the DC-DC converter after a 150ms delay, and simultaneously sending an enable signal to the MCU; receiving feedback signals from the DC-DC converter and the MCU to monitor whether the entire system has entered the working state normally; and after entering the deep discharge mode, disallowing the response to the working requests of the comfort high-voltage accessories and limiting the vehicle's acceleration and maximum speed to ensure driving safety under extremely low battery conditions.

[0115] Furthermore, the main functions of the BMS include: receiving deep discharge commands from the TBOX; receiving high-voltage command from the VCU, first closing the main negative relay, then closing the pre-charge relay for pre-charging, and after pre-charging, closing the main positive relay and opening the pre-charge relay to perform high-voltage power-on and status feedback; and real-time monitoring of battery cell status. When any exit condition is met (a level 3 fault occurs; the voltage reaches the deep discharge threshold; the battery enters charging mode; the VCU sends a high-voltage de-charging command), the BMS immediately exits the deep discharge mode. Specifically, when the voltage reaches the deep discharge exit threshold, the BMS sends a power-off command to power off the entire vehicle, ensuring battery safety.

[0116] In addition, the main functions of the MCU include: receiving the enable signal sent by the VCU, and then feeding back the high voltage ready status to the VCU, indicating that the motor system can work normally; receiving the gear signal and torque request signal sent by the VCU, and entering the corresponding working mode according to the actual working conditions of the vehicle (such as vehicle speed and pedal position) to drive the vehicle to continue driving with the lowest energy consumption; and sending key parameters such as the DC bus voltage monitored in real time to the CAN network to provide data support for the VCU to perform vehicle energy management and safety monitoring.

[0117] Optionally, the cloud can also directly send deep discharge enable or terminate commands to the TBOX. After the vehicle is powered on and off again, it will respond to the enable or terminate operation. If the unique vehicle identifier stored in the TBOX and VCU is inconsistent, the GPS signal is lost for a cumulative period of 2 hours, or the battery temperature is lower than the deep discharge safety threshold, the cloud will directly refuse to execute the command and trigger a safety alarm. Therefore, it can avoid human tampering with the TBOX binding information, disconnecting the GPS antenna, or damaging the battery sensor harness, ensuring that the cloud can monitor the vehicle battery status and location in real time, accurately control the deep discharge process, and prevent battery over-discharge damage.

[0118] To achieve the functions of the above embodiments, the vehicle power battery control method includes hardware structures and / or software modules corresponding to each function. Those skilled in the art should readily recognize that, based on the units and method steps described in conjunction with the embodiments disclosed in this application, this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed by hardware or by computer software driving hardware depends on the specific application scenario and design constraints of the technical solution.

[0119] exist Figures 2 to 7 Based on the control method for vehicle power batteries shown, the present application also provides a control device for further explanation, such as... Figure 8 The diagram shows a structural schematic of a control device for a vehicle power battery. The control device 600 for a vehicle power battery includes: a first processing module 610 and a control module 620.

[0120] The first processing module 610 is configured to respond to a first instruction sent from the cloud and determine whether the high-voltage power supply system of the vehicle meets the operating conditions for starting; the first instruction is generated based on the vehicle meeting a first determination condition; the first determination condition indicates that the vehicle's battery status supports the vehicle executing the first instruction, and the number of successful executions of the first instruction by the vehicle has not exceeded a first threshold; wherein, the first processing module 610 may include, for example, Figure 1 The control unit 120 shown includes the communication module 121 and the vehicle controller 122.

[0121] Control module 620 is configured to determine, based on the operating state, that the high-voltage power supply system meets the startup conditions, and control the vehicle to execute the discharge mode requested by the first command; wherein, control module 620 may include, for example, Figure 1 The control unit 120 shown includes a communication module 121, a vehicle controller 122, a battery management module 123, and a motor controller 124.

[0122] In some embodiments, the first processing module 610 includes: acquiring the battery status of the vehicle; the battery status includes: state of charge and battery temperature; and sending the vehicle's battery status to the cloud.

[0123] In some embodiments, the first processing module 610 further includes: a method for sending a successful receipt instruction of the first instruction to the cloud based on the received first instruction sent by the cloud.

[0124] In other embodiments, the control module 620 includes: recording the startup duration of the vehicle activating the discharge mode; and sending the startup duration to the cloud.

[0125] exist Figures 2 to 7 Based on the control method for vehicle power batteries shown, this application further describes another control device, such as... Figure 9 The diagram shows the structure of another vehicle power battery control device 700, which includes: an acquisition module 710, a receiving module 720, a second processing module 730, and a sending module 740.

[0126] Acquisition module 710 is used to acquire the unique identifier of the vehicle; wherein, acquisition module 710 may include, for example, Figure 1 The cloud service platform 110 shown.

[0127] The receiving module 720 is used to receive the battery status of the vehicle; the battery status includes: state of charge and battery temperature; wherein, the acquiring module 710 may include, for example, Figure 1 The cloud service platform 110 shown.

[0128] The second processing module 730 is configured to determine whether the vehicle meets a first determination condition by matching the vehicle's unique identifier with an identifier stored in the cloud; the first determination condition includes the deviation value of the state of charge in the vehicle's battery state not exceeding a first deviation threshold and the battery temperature not being lower than a second temperature threshold; wherein, the second processing module 730 may include, for example, Figure 1 The cloud service platform 110 shown.

[0129] The sending module 740 is configured to send a first instruction to the vehicle based on the vehicle meeting a first determination condition; wherein, the sending module 740 may include, for example, Figure 1 The cloud service platform 110 shown.

[0130] In some embodiments, the sending module 740 includes: recording the sending duration of the first instruction; receiving the start-up duration sent by the vehicle; and determining the execution result of the vehicle's discharge mode requesting the first instruction based on the start-up duration and the sending duration.

[0131] In some embodiments, the sending module 740 further includes: determining that the execution result is execution failure and the number of executions remains unchanged when the sending duration exceeds a first time threshold and no successful reception instruction is received from the vehicle; determining that the execution result is execution timeout and the number of executions remains unchanged when the sending duration does not exceed the first time threshold and a successful reception instruction is received from the vehicle, based on the start duration exceeding a second time threshold; and determining that the execution result is execution success and the number of executions is accumulated once when the sending duration does not exceed the first time threshold and a successful reception instruction is received from the vehicle, based on the start duration not exceeding the second time threshold.

[0132] According to one aspect of the embodiments of this application, Figure 10 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Figure 8 As shown, the electronic device 800 includes a processor 810 and one or more memories 820. The one or more memories 820 are used to store program instructions executed by the processor 810. When the processor 810 executes the program instructions, it implements the above-described control method for the vehicle power battery.

[0133] Furthermore, the processor 810 may include one or more processing cores. The processor 810 runs or executes instructions, programs, code sets, or instruction sets stored in the memory 820, and retrieves data stored in the memory 820. Optionally, the processor 810 may be implemented using at least one hardware form selected from Digital Signal Processing (DSP), Field-Programmable Gate Array (FPGA), and Programmable Logic Array (PLA). The processor 810 may integrate one or a combination of several of the following: a Central Processing Unit (CPU), a Graphics Processing Unit (GPU), and a modem. The CPU primarily handles the operating system, user interface, and applications; the GPU is responsible for rendering and drawing the displayed content; and the modem handles wireless communication. It is understood that the modem may also not be integrated into the processor and may be implemented using a separate communication chip.

[0134] According to one aspect of this application, a computer-readable storage medium is also provided, which may be included in the electronic device described in the above embodiments; or it may exist independently and not assembled into the electronic device. The computer-readable storage medium carries computer-readable instructions that, when executed by a processor, implement the methods in any of the above embodiments.

[0135] It should be noted that the computer-readable medium shown in the embodiments of this application can be a computer-readable signal medium or a computer-readable storage medium, or any combination of the two. Computer-readable storage media can be, for example, but not limited to: electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatuses, or devices, or any combination thereof. More specific examples of computer-readable storage media may include, but are not limited to: electrical connections with one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), flash memory, optical fiber, portable compact disc read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof. In this application, a computer-readable storage medium can be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, apparatus, or device. In this application, a computer-readable signal medium can include data signals propagated in baseband or as part of a carrier wave, carrying computer-readable program code. Such transmitted data signals can take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. The computer-readable signal medium can also be any computer-readable medium other than a computer-readable storage medium, which can send, propagate, or transmit a program for use by or in connection with an instruction execution system, apparatus, or device. The program code contained on the computer-readable medium can be transmitted using any suitable medium, including but not limited to wireless, wired, etc., or any suitable combination thereof.

[0136] The units described in the embodiments of this application can be implemented in software or hardware, and the described units can also be located in a processor. The names of these units do not necessarily limit the specific unit itself.

[0137] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this application. Each block in a flowchart or block diagram may represent a module, segment, or portion of code, which contains one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in a block diagram or flowchart, and combinations of blocks in a block diagram or flowchart, can be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0138] Other embodiments of this application will readily occur to those skilled in the art upon consideration of the specification and practice of the embodiments disclosed herein. This application is intended to cover any variations, uses, or adaptations of this application that follow the general principles of this application and include common knowledge or customary techniques in the art not disclosed herein.

[0139] It should be understood that this application is not limited to the precise structure described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of this application is limited only by the appended claims.

Claims

1. A control method for a vehicle power battery, characterized in that, Applied to the vehicle end, the vehicle end communicates with the cloud, including: In response to a first instruction sent from the cloud, the operating status of the vehicle's high-voltage power supply system is obtained; the first instruction is generated based on the vehicle meeting a first determination condition; the first determination condition is used to indicate that: the vehicle's battery status supports the vehicle executing the first instruction, and the number of times the vehicle successfully executes the first instruction has not exceeded a first threshold. Based on the operating status, it is determined that the high-voltage power supply system meets the startup conditions, and the vehicle is controlled to execute the discharge mode requested by the first instruction.

2. The method according to claim 1, characterized in that, Prior to the first instruction sent in response to the cloud, the following is included: Obtain the battery status of the vehicle; the battery status includes: state of charge and battery temperature; Send the vehicle's battery status to the cloud.

3. The method according to claim 1, characterized in that, Prior to the first instruction sent in response to the cloud, the following is included: Upon receiving the first instruction sent by the cloud, send a success message for receiving the first instruction to the cloud.

4. The method according to claim 1, characterized in that, After the controlled vehicle executes the discharge mode requested by the first instruction, the following steps are included: Record the start-up time of the vehicle initiating the discharge mode; Send the startup duration to the cloud.

5. A control method for a vehicle power battery, characterized in that, It is applied in the cloud, and the cloud communicates with the vehicle, including: Obtain the unique identifier of the vehicle; Receive the battery status of the vehicle; the battery status includes: state of charge and battery temperature; Based on the unique identifier of the vehicle and the identifier stored in the cloud, it is determined whether the vehicle meets the first determination condition; the first determination condition includes the deviation value of the state of charge in the battery state of the vehicle not exceeding a first deviation threshold and the battery temperature not lower than a second temperature threshold. If the vehicle meets the first determination condition, a first instruction is sent to the vehicle.

6. The method according to claim 5, characterized in that, After sending the first instruction to the vehicle, the process includes: Record the duration of sending the first instruction; Receive the start-up duration sent by the vehicle; Based on the startup duration and the transmission duration, the execution result of the vehicle's discharge mode for executing the first instruction request is determined.

7. The method according to claim 6, characterized in that, The step of determining the execution result of the vehicle's discharge mode for executing the first instruction request based on the startup duration and the transmission duration includes: If the transmission duration exceeds the first time threshold and no successful reception instruction is received from the vehicle, the execution result is determined to be execution failure, and the number of executions remains unchanged. If the sending duration does not exceed the first time threshold and a successful reception instruction is received from the vehicle, and the starting duration exceeds the second time threshold, the execution result is determined to be execution timeout and the number of executions remains unchanged. If the sending time does not exceed the first time threshold and a successful reception instruction is received from the vehicle, and the startup time does not exceed the second time threshold, the execution result is determined to be successful and the execution count is accumulated once.

8. A control device for a vehicle power battery, characterized in that, Applied to a vehicle-mounted system that communicates with the cloud, the device includes: The first processing module is configured to respond to a first instruction sent from the cloud and determine whether the high-voltage power supply system of the vehicle meets the start-up conditions. The first instruction is generated based on the vehicle meeting a first determination condition. The first determination condition indicates that the vehicle's battery status supports the vehicle in executing the first instruction and that the number of times the vehicle successfully executes the first instruction has not exceeded a first threshold. The control module is used to determine, based on the operating state, that the high-voltage power supply system meets the startup conditions, and to control the vehicle to execute the discharge mode requested by the first instruction.

9. A control device for a vehicle power battery, characterized in that, The device is applied in the cloud, where the cloud communicates with the vehicle, and includes: The acquisition module is used to acquire the unique identifier of the vehicle; A receiving module is used to receive the battery status of the vehicle; the battery status includes: state of charge and battery temperature; The second processing module is used to determine whether the vehicle meets the first determination condition by matching the vehicle's unique identifier with the identifier stored in the cloud; the first determination condition includes the deviation value of the state of charge in the battery state of the vehicle not exceeding a first deviation threshold and the battery temperature not being lower than a second temperature threshold. The sending module is used to send a first instruction to the vehicle based on the vehicle meeting a first determination condition.

10. An electronic device, characterized in that, The electronic device includes: processor; A memory storing computer-readable instructions that, when executed by the processor, implement the control method as described in any one of claims 1 to 7.

Images