Charging protection method and device of vehicle, cloud server and battery management system

Abstract

The invention relates to the technical field of vehicle charging, in particular to a vehicle charging protection method and device, a cloud server and a battery management system.The method comprises the steps that current fault information, sent by the vehicle cloud server, of a target vehicle is received, and historical fault information of the target vehicle is obtained; generating a charging protection action of the target vehicle in combination with the current fault information and the historical fault information; and under the condition that the target vehicle is charged, controlling a charging device controlled by the charging pile server to execute a charging protection action on the vehicle, or controlling the target vehicle to execute the charging protection action. Therefore, the problem that in the related technology, when the vehicle cloud server protects the vehicle, only safety early warning can be carried out, and protection action cannot be carried out in time when a fault occurs, so that the battery continues to be normally used in the early warning period, and the probability of occurrence of hazards is increased is solved.

Description

Technical Field

[0001] This application relates to the technical field of vehicle charging, and particularly to a charging protection method, device, cloud server, and battery management system for a vehicle. Background Art

[0002] In practical applications, lithium-ion power batteries of electric vehicles have various potential risks, including but not limited to thermal runaway, battery aging, internal short circuit, etc. To effectively manage these risks, it is necessary to conduct strict risk assessments on the batteries and take corresponding protection measures based on the assessment results. The battery risk assessment and early warning mechanism mainly relies on the BMS (Battery Management System), vehicle cloud server, and a series of monitoring and analysis technologies, aiming to monitor the battery status in real time, evaluate the battery health status, and predict possible failures or safety risks.

[0003] In the related art, the vehicle cloud server monitors various parameters of the battery in real time, evaluates the health status of the battery, analyzes the battery failure status, thereby issuing a warning, and providing a scientific basis for the maintenance and management of the battery.

[0004] However, since the vehicle cloud server only issues safety warnings, once a vehicle fails, users can only handle it offline. However, the battery will continue to be used normally during the waiting period for offline processing. Then, once the failure is serious, major safety accidents may occur, and even spontaneous combustion may occur, seriously threatening the safety of users' lives, which urgently needs to be improved. Summary of the Invention

[0005] This application provides a charging protection method, device, cloud server, and battery management system for a vehicle to solve the problem in the related art that when the vehicle cloud server monitors the battery, it can only issue safety warnings and cannot make protection actions in time, reducing the reliability and safety of the vehicle and the user experience.

[0006] The first aspect embodiment of this application provides a charging protection method for a vehicle, including the following steps: receiving the current fault information of the target vehicle sent by the vehicle cloud server, and obtaining the historical fault information of the target vehicle; combining the current fault information and the historical fault information to generate a charging protection action for the target vehicle; when the target vehicle is charging, controlling the charging device controlled by the charging pile server to execute the charging protection action on the vehicle, or controlling the target vehicle to execute the charging protection action.

[0007] Through the above technical solution, the embodiment of the present application can receive and comprehensively analyze the current fault information and historical fault information of the target vehicle, and combine the current and historical fault information of the vehicle to intelligently generate and execute a charging protection action. The charging protection action can be executed by a charging device controlled by a charging pile server or by the target vehicle, achieving the purpose of charging protection for a dual loop, effectively improving the reliability of vehicle charging protection decision-making and the safety of the charging process, enhancing the user experience, and ensuring customer viscosity.

[0008] Optionally, in an embodiment of the present application, the current fault information includes fault information of at least one of cell overvoltage, total battery voltage overvoltage, battery overtemperature, charging overcurrent, maximum temperature deviation, maximum temperature difference deviation, maximum pressure difference deviation, temperature rise rate deviation, and battery internal resistance deviation of the power battery of the target vehicle, and the charging protection action is a vehicle charging prohibition action, a charging window and charging rate limitation action, a charging window limitation action, or a charging rate action.

[0009] Through the above technical solution, the embodiment of the present application can timely and effectively monitor multiple key parameters of the battery, can timely capture situations that may affect the safety and performance of the battery, ensures comprehensive monitoring of the battery state, and improves the comprehensiveness and accuracy of fault diagnosis.

[0010] Optionally, in an embodiment of the present application, the matching of the charging protection action of the target vehicle by combining the current fault information and the historical fault information includes: when the current fault information includes fault information of at least one of the cell overvoltage, the total battery voltage overvoltage, the battery overtemperature, and the charging overcurrent, determining the number of faults according to the current fault information and the historical fault information; determining a first fault level of the target vehicle according to the number of faults, and matching the charging protection action based on the first fault level.

[0011] Through the above technical solution, the embodiment of the present application can determine the number of faults based on the current fault information and the historical fault information, thereby determining the fault level, making the formulation of protection measures more targeted, and can match corresponding protection actions according to the severity of the fault, avoiding extreme or incorrect handling methods, improving the pertinence and effectiveness of protection measures, and enhancing the user experience.

[0012] Optionally, in an embodiment of the present application, the matching of the charging protection action of the target vehicle by combining the current fault information and the historical fault information includes: when the current fault information includes at least one of the maximum temperature deviation, the maximum temperature difference deviation, the maximum pressure difference deviation, the temperature rise rate deviation, and the battery internal resistance deviation, determining a second fault level and a corresponding duration of the target vehicle according to the current fault information and the historical fault information; and matching the charging protection action based on the second fault level and the duration.

[0013] Through the above technical solution, the embodiment of the present application can consider the duration when determining the second fault level, which is different from the above embodiment, helps to match a more reasonable protection decision, avoids over-limiting charging due to short-term faults, protects the battery while ensuring the charging efficiency of the battery, and improves user satisfaction.

[0014] Optionally, in an embodiment of the present application, it further includes: based on the current fault information and / or the historical fault information, determining whether the target vehicle meets a preset fault clearing condition; if the fault clearing condition is met, clearing the corresponding fault information.

[0015] Through the above technical solution, the embodiment of the present application can determine whether the target vehicle meets the preset fault clearing condition, thereby dynamically clearing the resolved or no longer existing fault information, ensuring the timeliness and accuracy of the fault record, avoiding the influence of outdated information on subsequent decisions, and ensuring the sustainability of the fault, making it more intelligent and effective.

[0016] An embodiment of the second aspect of the present application provides a charging protection device for a vehicle, which is applied to a charging cloud server or a battery management system. The device includes: an acquisition module, configured to receive the current fault information of the target vehicle sent by the vehicle cloud server and acquire the historical fault information of the target vehicle; a generation module, configured to generate a charging protection action of the target vehicle by combining the current fault information and the historical fault information; and a protection module, configured to, when the target vehicle is charging, control the charging device controlled by the charging pile server to perform the charging protection action on the vehicle, or control the target vehicle to perform the charging protection action.

[0017] Through the above technical solutions, the embodiments of the present application can receive and comprehensively analyze the current fault information and historical fault information of the target vehicle, and combine the current and historical fault information of the vehicle to intelligently generate and execute a charging protection action. The charging protection action can be executed by a charging device controlled by a charging pile server or by the target vehicle, achieving the purpose of charging protection for a dual loop, effectively improving the reliability of vehicle charging protection decisions and the safety of the charging process, enhancing the user experience, and ensuring customer viscosity.

[0018] Optionally, in an embodiment of the present application, the current fault information includes fault information of at least one of cell overvoltage, total battery voltage overvoltage, battery overtemperature, charging overcurrent, maximum temperature deviation, maximum temperature difference deviation, maximum pressure difference deviation, temperature rise rate deviation, and battery internal resistance deviation of the power battery of the target vehicle, and the charging protection action is a vehicle charging prohibition action, a charging window and charging rate limitation action, a charging window limitation action, or a charging rate action.

[0019] Through the above technical solutions, the embodiments of the present application can timely and effectively monitor multiple key parameters of the battery, can timely capture situations that may affect the safety and performance of the battery, ensure comprehensive monitoring of the battery state, and improve the comprehensiveness and accuracy of fault diagnosis.

[0020] Optionally, in an embodiment of the present application, the generating module includes: a first determination unit, configured to determine the number of faults according to the current fault information and the historical fault information when the current fault information includes fault information of at least one of the cell overvoltage, the total battery voltage overvoltage, the battery overtemperature, and the charging overcurrent; a first matching unit, configured to determine a first fault level of the target vehicle according to the number of faults and match the charging protection action based on the first fault level.

[0021] Through the above technical solutions, the embodiments of the present application can determine the number of faults based on the current fault information and the historical fault information, thereby determining the fault level, making the formulation of protection measures more targeted, matching corresponding protection actions according to the severity of the fault, avoiding extreme or incorrect processing methods, improving the pertinence and effectiveness of protection measures, and enhancing the user experience.

[0022] Optionally, in an embodiment of the present application, the generating module further includes: a second determination unit, configured to determine a second fault level and a corresponding duration of the target vehicle according to the current fault information and the historical fault information when the current fault information includes at least one of the highest temperature deviation, the maximum temperature difference deviation, the maximum pressure difference deviation, the temperature rise rate deviation, and the battery internal resistance deviation; a second matching unit, configured to match the charging protection action based on the second fault level and the duration.

[0023] Through the above technical solution, the embodiment of the present application can consider the duration when determining the second fault level, which is different from the above embodiment, helps to match a more reasonable protection decision, avoids over-restricting charging due to short-term faults, protects the battery while ensuring the charging efficiency of the battery, and improves user satisfaction.

[0024] Optionally, in an embodiment of the present application, the protection module further includes: a judgment unit, configured to judge whether the target vehicle meets a preset fault clearing condition based on the current fault information and / or the historical fault information; a control unit, configured to clear the corresponding fault information when the fault clearing condition is met.

[0025] Through the above technical solution, the embodiment of the present application can judge whether the target vehicle meets the preset fault clearing condition, thereby dynamically clearing the fault information that has been resolved or no longer exists, ensuring the timeliness and accuracy of the fault record, avoiding the influence of outdated information on subsequent decisions, and ensuring the sustainability of the fault, making it more intelligent and effective.

[0026] An embodiment of the third aspect of the present application provides a charging cloud server, including: a memory, a processor, and a computer program stored on the memory and executable on the processor, where the processor executes the program to implement the vehicle charging protection method as described in the above embodiment.

[0027] An embodiment of the fourth aspect of the present application provides a battery management system, including: a memory, a processor, and a computer program stored on the memory and executable on the processor, where the processor executes the program to implement the vehicle charging protection method as described in the above embodiment.

[0028] An embodiment of the fifth aspect of the present application provides a computer-readable storage medium, where the computer-readable storage medium stores a computer program, and when the program is executed by a processor, it implements the vehicle charging protection method as described above.

[0029] An embodiment of the sixth aspect of the present application provides a computer program product, including a computer program, and when the computer program is executed, it is used to implement the vehicle charging protection method as described above.

[0030] Embodiments of the present application can receive and comprehensively analyze the current fault information and historical fault information of the target vehicle, monitor multiple key parameters of the battery in a timely and effective manner, be able to capture in a timely manner the situations that may affect the safety and performance of the battery, ensure comprehensive monitoring of the battery state, and improve the comprehensiveness and accuracy of fault diagnosis. Further, by combining the current and historical fault information of the vehicle, charging protection actions are intelligently generated and executed. That is, the number of faults can be determined based on the current fault information and historical fault information, and then the fault level can be determined. Also, the duration can be considered when determining the fault level, making the formulation of protection measures more targeted and effective. Corresponding charging protection actions are matched according to the severity of the fault. The charging protection actions can be executed by the charging device controlled by the charging pile server or by the target vehicle, thus achieving the purpose of charging protection for a dual loop, improving the reliability of the vehicle charging protection decision and the safety of the charging process. At the same time, to avoid the influence of outdated information on subsequent decisions, embodiments of the present application can also determine whether the target vehicle meets the fault clearance condition, thereby dynamically clearing the fault information that has been resolved or no longer exists, ensuring the timeliness and accuracy of the fault record, and ensuring the sustainability of the fault, being more intelligent and effective, and improving the user experience.

[0031] Additional aspects and advantages of the present application will be given in part in the following description, become apparent in part from the following description, or be understood through the practice of the present application. BRIEF DESCRIPTION OF THE DRAWINGS

[0032] The above and / or additional aspects and advantages of the present application will become apparent and be readily understood from the following description of the embodiments in conjunction with the drawings, where:

[0033] Figure 1 is a schematic structural diagram of a charging safety system according to an embodiment of the present application;

[0034] Figure 2 is a schematic diagram of the early warning process of a power battery according to an embodiment of the present application;

[0035] Figure 3 is a flowchart of a charging protection method for a vehicle provided according to an embodiment of the present application;

[0036] Figure 4 is a schematic diagram of the principle of a charging protection method for a vehicle according to an embodiment of the present application;

[0037] Figure 5 is a schematic structural diagram of a charging protection device for a vehicle provided according to an embodiment of the present application;

[0038] Figure 6Schematic diagram of the charging cloud server provided according to an embodiment of the present application;

[0039] Figure 7 Schematic diagram of the battery management system provided according to an embodiment of the present application. Detailed implementation manners

[0040] The embodiments of the present application will be described in detail below. The examples of the embodiments are shown in the accompanying drawings, where the same or similar reference numerals denote the same or similar elements or elements with the same or similar functions from beginning to end. The embodiments described below by referring to the accompanying drawings are exemplary and are intended to explain the present application, and should not be construed as a limitation to the present application.

[0041] The charging protection method, device, cloud server and battery management system of a vehicle according to an embodiment of the present application will be described below with reference to the accompanying drawings. In view of the problem in the related art mentioned in the above background technology that when the vehicle cloud server monitors the battery, it can only give a safety warning and cannot take protection actions in time, reducing the reliability and safety of the vehicle and the user experience. The present application provides a charging protection method for a vehicle. In this method, the current fault information of the target vehicle sent by the vehicle cloud server can be received, and the historical fault information of the target vehicle can be obtained, so as to comprehensively and accurately evaluate the fault situation of the vehicle. Then, combining the current fault information and the historical fault information, a charging protection action for the target vehicle is generated. That is, in addition to the warning function, effective protection actions can be taken in time to improve the reliability and safety of the vehicle. The charging protection action of the vehicle is executed by the charging device controlled by the charging cloud server or by the target vehicle. This dual-loop charging protection method ensures that the charging protection can be effectively implemented in different scenarios, improves the safety and stability of the charging process, enhances the user's confidence in vehicle charging, and improves the user experience. Thus, the problem in the related technology that when the vehicle cloud server monitors the battery, it can only give a safety warning and cannot take protection actions in time, reducing the reliability and safety of the vehicle and the user experience is solved.

[0042] Before elaborating on the charging protection method of the vehicle according to an embodiment of the present application, the charging safety system involved in the embodiment of the present application will be described first.

[0043] As Figure 1 shown, the charging safety system in the related technology includes: vehicle 1, vehicle cloud server 2, charging cloud server 3 and charging pile 4.

[0044] Based on this system, the vehicle power battery warning process in the related technology is as Figure 2As shown in the figure. During the operation of the vehicle, the vehicle BMS collects and estimates the state information of the power battery in real time and sends the vehicle VIN (Vehicle Identification Number), the state information of the power battery, and the fault information to the vehicle cloud server. After receiving the above information, the vehicle cloud server further processes and evaluates it. Then, according to the preset rules and strategies, the vehicle cloud server decides whether to send the power battery fault information to the vehicle BMS or the charging pile cloud server. At the same time, the vehicle BMS or the charging pile cloud server stores the power battery fault information to generate historical fault information. In the whole process, the BMS and the vehicle cloud server continuously conduct data interaction and collaborative processing to ensure timely and accurate discovery and response to the fault situation of the power battery and ensure the safe operation of the vehicle.

[0045] In summary, when the vehicle cloud server in the related technology protects the vehicle, it can only give a safety warning. The charging equipment controlled by the vehicle BMS and the charging cloud server cannot take protection actions in time when a fault occurs, resulting in the battery continuing to be used normally during the warning period, thus increasing the probability of harm. It is precisely for the above reasons that under the architecture of the same charging safety system, this application proposes a charging protection method for vehicles.

[0046] Specifically, Figure 3 is a schematic flowchart of a charging protection method for a vehicle provided by an embodiment of this application.

[0047] As Figure 3 shown, the charging protection method for the vehicle includes the following steps:

[0048] In step S301, receive the current fault information of the target vehicle sent by the vehicle cloud server, and obtain the historical fault information of the target vehicle.

[0049] It can be understood that the current fault information can refer to some information included in the occurrence of a fault in the vehicle or the power battery, and the historical fault information can be understood as the same type of fault or some fault information previously stored in the vehicle. Examples will be given below.

[0050] Optionally, in an embodiment of this application, the current fault information may include, but is not limited to, at least one of the fault information of overvoltage of a single battery cell of the power battery of the target vehicle, overvoltage of the total battery voltage, overheating of the battery, overcurrent during charging, deviation of the highest temperature, deviation of the maximum temperature difference, deviation of the maximum pressure difference, deviation of the temperature rise rate, and deviation of the battery internal resistance. And the charging protection actions are to prohibit the vehicle charging action, limit the charging window and charging rate actions, limit the charging window action, or limit the charging rate action.

[0051] During the actual execution process, the BMS of the vehicle can obtain the status information of the vehicle's power battery in real time, such as including but not limited to voltage, current, temperature, SOC (State of Charge), etc. The status information of the vehicle's power battery and the vehicle's unique identification code VIN are sent to the vehicle cloud server through the vehicle's on-vehicle communication terminal, and the vehicle cloud server receives the status information of the vehicle's power battery and the vehicle's unique identification code VIN. Further, the vehicle cloud server sends the received status information of the vehicle's power battery and the vehicle's unique identification code VIN to the charging cloud server, and the charging cloud server performs fault diagnosis on the received status information of the vehicle's power battery. The charging device controlled by the vehicle BMS and the charging cloud server receives the fault diagnosis. At the same time, the BMS of the vehicle and the charging cloud server will record and store the current fault information to form historical fault information.

[0052] The embodiment of the present application not only obtains the current fault information of the target vehicle, but also stores the current fault information to obtain historical fault information, which can more comprehensively and accurately understand the fault situation of the target vehicle.

[0053] In step S302, a charging protection action for the target vehicle is generated by combining the current fault information and the historical fault information.

[0054] It can be understood that the target vehicle is the vehicle determined by the vehicle cloud server using the vehicle's unique identification code VIN, and the charging protection action is an action to protect the vehicle's power battery generated by the charging device controlled by the vehicle BMS or the charging cloud server by combining the current fault information and the historical fault information. The following is an example.

[0055] Optionally, in an embodiment of the present application, matching the charging protection action of the target vehicle by combining the current fault information and the historical fault information includes: when the current fault information includes at least one of the fault information such as battery cell overvoltage, total battery voltage overvoltage, battery overtemperature, and charging overcurrent, determining the number of faults according to the current fault information and the historical fault information; determining the first fault level of the target vehicle according to the number of faults, and matching the charging protection action based on the first fault level.

[0056] For example, for power battery abuse faults including but not limited to power battery cell overvoltage, total power battery voltage overvoltage, power battery overtemperature, and charging overcurrent, the first fault level is determined according to the severity level and the number of occurrences of the fault, and the charging protection action corresponding to the level of the first fault level is matched. Specifically, as shown in Table 1, Table 1 is the first fault handling level table, as follows:

[0057] Table 1

[0058]

[0059]

[0060] Optionally, in an embodiment of the present application, combining the current fault information and the historical fault information to match the charging protection action of the target vehicle, including: when the current fault information includes at least one of the fault information such as the maximum temperature deviation, the maximum temperature difference deviation, the maximum pressure difference deviation, the temperature rise rate deviation, and the battery internal resistance deviation, determining the second fault level and the corresponding duration of the target vehicle according to the current fault information and the historical fault information; matching the charging protection action based on the second fault level and the duration.

[0061] For example, for battery performance degradation faults including but not limited to the maximum temperature deviation, the maximum temperature difference deviation, the maximum pressure difference deviation, the temperature rise rate deviation, and the battery internal resistance deviation, determining the second fault level according to the severity level of the fault and the corresponding duration, and matching the charging protection action of the corresponding level by the level of the second fault level. Specifically, as shown in Table 2, Table 2 is the second fault handling level table, as follows:

[0062] Table 2

[0063]

[0064] Furthermore, when performing the fault level rating, the supplementary scoring rules include: accumulating 2 minor faults is equivalent to 1 medium fault; occurring 2 medium faults, occurring 1 medium fault and 1 minor fault, or occurring 3 minor faults is equivalent to 1 severe fault.

[0065] In the actual execution process, according to the fault level, the charging protection actions corresponding to the vehicle BMS or the charging device controlled by the charging cloud server include but are not limited to: in the case of a first-level fault, prohibiting the vehicle from charging; in the case of a second-level fault, restricting the charging window and the charging rate, that is, reducing the charging upper cut-off voltage and at the same time reducing the charging current; in the case of a third-level fault, restricting the charging window, that is, reducing the charging upper cut-off voltage; in the case of a fourth-level fault, restricting the charging rate, that is, reducing the charging current.

[0066] Furthermore, the above charging window restriction is divided into three gears, and each gear of charging window restriction is set according to the fault level. Specifically, as shown in Table 3, Table 3 is the charging window restriction table, as follows:

[0067] Table 3

[0068]

[0069]

[0070] Further, the above charging current limit is also divided into three levels, and the charging current magnification limit for each level is set according to the fault handling measure level. Specifically, as shown in Table 4, Table 4 is the charging magnification limit table, as follows:

[0071] Table 4

[0072] Severity level of fault Severe Medium Minor Current reduction level Level 2 Level 2 Level 3 Current reduction multiple 0.5 0.7 0.9

[0073] In some embodiments, the charging device controlled by the vehicle BMS or the charging cloud server first determines the fault level according to the current fault information and historical fault information received this time, and according to Tables 1, 2 and the foregoing supplementary scoring rules. If the fault level is level one, vehicle charging is prohibited; if the fault level is level two or three, query Table 3 and limit the charging current to the maximum allowable charging current estimated by the BMS multiplied by the current reduction magnification; if the fault handling level is level two or four, query Table 4 and limit the charging upper limit voltage to the highest allowable charging voltage estimated by the BMS minus the limit window voltage.

[0074] The embodiments of the present application can determine the number of faults based on the current fault information and historical fault information, thereby determining the fault level, and can also determine the fault level based on the current fault information, historical fault information and fault duration, making the formulation of protection measures more targeted. Matching corresponding protection actions according to the fault level can protect the battery while ensuring the charging efficiency of the battery, and improve the pertinence and effectiveness of the protection measures.

[0075] In step S303, when the target vehicle is charging, control the charging device controlled by the charging pile server to perform a charging protection action on the vehicle, or control the target vehicle to perform a charging protection action.

[0076] It can be understood that the embodiments of the present application can be understood as having a dual protection loop. One loop is that the charging device controlled by the charging pile server performs a charging protection action on the vehicle, and the other loop is that the vehicle BMS performs a charging protection action. Either one or both can be selected.

[0077] The principle is as follows: The first protection loop is the BMS of the vehicle playing a role. The BMS monitors the state information of the vehicle's power battery during the charging process, including but not limited to current and voltage, etc. When a fault occurs, such as excessive current or excessive voltage, the BMS determines the fault level and performs corresponding charging protection actions. The second loop is that when the vehicle is charging, the vehicle transmits the vehicle unique identification code VIN to the charging device through the charging interface, and the charging device forwards the VIN to the charging cloud server. The charging cloud server receives and queries in real time whether the vehicle has a fault, and then, according to the fault level judgment, sends a charging protection action instruction to the charging device. Specifically, as Figure 4 shown Figure 4It is the flowchart for charging protection of power batteries. The steps of the power battery charging protection process are as follows:

[0078] Step S401: The vehicle starts charging.

[0079] Step S402: Send the vehicle VIN to the charging pile and the vehicle BMS.

[0080] When the vehicle is charging, it transmits the vehicle VIN code to the charging pile through the charging interface, and the charging pile forwards the vehicle VIN code to the charging pile server and the vehicle BMS.

[0081] Step S403: Is charging protection required (vehicle BMS)?

[0082] The vehicle BMS receives the VIN code of the charging vehicle in real time, and queries whether there is a fault based on the current power battery status information and historical fault information.

[0083] Step S404: Normal charging.

[0084] If no fault is found in the power battery in steps S403 and S405, normal charging is carried out.

[0085] Step S405: Is charging protection required (charging pile cloud service)?

[0086] The charging cloud server receives the VIN code of the charging vehicle in real time, and queries whether there is a fault based on the current power battery status information and historical fault information.

[0087] Step S406: Is charging to be prohibited (vehicle BMS)?

[0088] If the query result in step S403 shows that there is a fault in the vehicle power battery, the vehicle BMS determines whether charging needs to be prohibited according to the severity of the fault.

[0089] Step S407: Stop charging (vehicle BMS)

[0090] If it is determined in step S406 that the vehicle power battery fault requires a primary fault handling measure, the vehicle BMS issues a control instruction to stop charging.

[0091] Step S408: Send a charging control instruction to the charging pile (vehicle BMS).

[0092] If it is determined in step S406 that the vehicle power battery fault does not require a primary fault handling measure, secondary, tertiary or quaternary fault handling measures are taken for charging.

[0093] Step S409: Respond to the charging control instruction (charging pile).

[0094] The charging pile performs corresponding charging protection actions according to the charging control instructions sent by the vehicle BMS.

[0095] Step S410: Send a charging protection control instruction to the charging pile (charging cloud server).

[0096] According to the diagnostic result of step S405, the charging cloud server issues first-level, second-level, third-level, or fourth-level fault handling measure instructions to the charging pile.

[0097] Step S411: Respond to the charging protection control instruction (charging pile).

[0098] The charging pile performs corresponding charging protection actions based on the control instruction sent by the charging cloud server.

[0099] The above steps are described below through specific embodiments.

[0100] In some cases, when the vehicle is charging, the vehicle VIN code is transmitted to the vehicle BMS through the charging interface. The vehicle BMS queries whether there is a current fault based on the current state information and historical fault information of the vehicle power battery. If there is no fault, normal charging is carried out. If there is a fault, the corresponding protection measure level is judged. The vehicle BMS first judges whether it is necessary to take first-level fault handling measures, that is, immediately stop charging, according to the aforementioned fault severity level and the number of times of occurrence of the fault or the fault severity level and the duration of the fault. If it is not necessary to stop charging, the vehicle BMS takes corresponding measures according to the fault level, that is, if the fault level is second or third, the charging current is limited to the maximum allowable charging current estimated by the BMS multiplied by the current reduction factor. If the fault is second or fourth, the charging upper limit is limited to the highest allowable charging voltage estimated by the BMS minus the limit window voltage.

[0101] In other cases, when the vehicle is charging, the vehicle VIN code is transmitted to the charging device through the charging interface. The charging device forwards the vehicle VIN code to the charging cloud server. The charging cloud server receives the VIN code of the charging vehicle in real time, queries whether there is a fault, and sends control instructions to the charging device according to the aforementioned fault level judgment description, including but not limited to prohibiting charging, restricting the charging window or charging rate.

[0102] The embodiment of the present application realizes the purpose of charging protection through a dual loop, effectively improves the reliability of the vehicle charging protection decision-making and the safety of the charging process, improves the user experience, and ensures customer viscosity.

[0103] Optionally, in an embodiment of the present application, it further includes: judging whether the target vehicle meets the preset fault clearing condition based on the current fault information and / or historical fault information; if the fault clearing condition is met, the corresponding fault information is cleared.

[0104] It should be understood that the fault clearing conditions include, but are not limited to: repairing or replacing the vehicle power battery; the vehicle BMS uses balancing technical means to naturally restore the vehicle power battery fault after a certain period of time. The following is an example for illustration.

[0105] In some embodiments, after the vehicle power battery is repaired or replaced, it is necessary to clear the power battery fault information stored in the vehicle local BMS and the charging cloud server. At this time, the fault information corresponding to the vehicle VIN code has been cleared, and the charging equipment controlled by the vehicle BMS or the charging cloud server will no longer perform charging safety protection.

[0106] In other embodiments, for faults such as the maximum pressure difference deviation caused by the performance attenuation of the vehicle power battery, even if the power battery is not repaired or replaced, the vehicle BMS can effectively reduce the degree of pressure difference deviation through balancing technical means. When such a fault naturally recovers after a period of time, the system can actively clear the fault record. Specifically, if the vehicle runs continuously for more than 72 hours and the fault does not occur again, the corresponding fault information can be cleared.

[0107] The embodiments of the present application can determine whether the target vehicle meets the fault clearing conditions, thereby dynamically clearing the resolved or non-existent fault information, ensuring the timeliness and accuracy of the fault record, avoiding the influence of outdated information on subsequent decisions, and ensuring the sustainability of the fault, making it more intelligent and effective.

[0108] According to the vehicle charging protection method proposed by the embodiments of the present application, it can receive and comprehensively analyze the current fault information and historical fault information of the target vehicle, timely and effectively monitor multiple key parameters of the battery, and can timely capture the situations that may affect the battery safety and performance faults, ensuring the comprehensive monitoring of the battery state and improving the comprehensiveness and accuracy of fault diagnosis. Further combining the current and historical fault information of the vehicle, it can intelligently generate and execute charging protection actions. That is, it can determine the number of faults based on the current fault information and historical fault information, thereby determining the fault level, or considering the duration while determining the fault level, making the formulation of protection measures more targeted and effective, matching corresponding charging protection actions according to the severity of the fault. The charging protection actions can be executed by the charging equipment controlled by the charging pile server or by the target vehicle, so as to achieve the purpose of double-loop charging protection, improve the reliability of vehicle charging protection decision-making and the safety of the charging process. At the same time, to avoid the influence of outdated information on subsequent decisions, the embodiments of the present application can also determine whether the target vehicle meets the preset fault clearing conditions, thereby dynamically clearing the resolved or non-existent fault information, ensuring the timeliness and accuracy of the fault record, and ensuring the sustainability of the fault, making it more intelligent and effective, and improving the user experience.

[0109] Next, a charging protection device for a vehicle according to an embodiment of the present application will be described with reference to the accompanying drawings.

[0110] Figure 5 It is a block diagram of a charging protection device for a vehicle according to an embodiment of the present application.

[0111] As Figure 5 shown, the charging protection device 10 of the vehicle includes: an acquisition module 100, a generation module 200, and a protection module 300.

[0112] Specifically, the acquisition module 100 is configured to receive the current fault information of the target vehicle sent by the vehicle cloud server and acquire the historical fault information of the target vehicle.

[0113] The generation module 200 is configured to generate a charging protection action for the target vehicle by combining the current fault information and the historical fault information.

[0114] The protection module 300 is configured to, when the target vehicle is charging, control the charging device controlled by the charging pile server to perform a charging protection action on the vehicle, or control the target vehicle to perform a charging protection action.

[0115] Optionally, in an embodiment of the present application, the current fault information includes at least one of the fault information of overvoltage of a battery cell of the power battery of the target vehicle, overvoltage of the total battery voltage, overheating of the battery, overcurrent during charging, deviation of the highest temperature, deviation of the maximum temperature difference, deviation of the maximum pressure difference, deviation of the temperature rise rate, and deviation of the battery internal resistance, and the charging protection action is a vehicle charging prohibition action, a charging window and charging rate limitation action, a charging window limitation action, or a charging rate action.

[0116] Optionally, in an embodiment of the present application, the generation module 200 includes: a first determination unit and a first matching unit.

[0117] Wherein, the first determination unit is configured to determine the number of faults according to the current fault information and the historical fault information when the current fault information includes at least one of the fault information of overvoltage of a battery cell, overvoltage of the total battery voltage, overheating of the battery, and overcurrent during charging.

[0118] The first matching unit is configured to determine the first fault level of the target vehicle according to the number of faults and match the charging protection action based on the first fault level.

[0119] Optionally, in an embodiment of the present application, the generation module 200 further includes: a second determination unit and a second matching unit.

[0120] Among them, the second determination unit is configured to determine a second fault level and a corresponding duration of the target vehicle according to the current fault information and historical fault information when the current fault information includes at least one of a maximum temperature deviation, a maximum temperature difference deviation, a maximum pressure difference deviation, a temperature rise rate deviation, and a battery internal resistance deviation.

[0121] The second matching unit is configured to match a charging protection action based on the second fault level and the duration.

[0122] Optionally, in an embodiment of the present application, the protection module 300 further includes: a judgment unit and a control unit.

[0123] Among them, the judgment unit is configured to judge whether the target vehicle meets a preset fault clearing condition based on the current fault information and / or historical fault information.

[0124] The control unit is configured to clear the corresponding fault information when the fault clearing condition is met.

[0125] It should be noted that the foregoing explanation of the embodiment of the vehicle charging protection method also applies to the vehicle charging protection device of this embodiment, and will not be repeated here.

[0126] The vehicle charging protection device proposed according to the embodiment of the present application can receive and comprehensively analyze the current fault information and historical fault information of the target vehicle, timely and effectively monitor multiple key parameters of the battery, and can timely capture situations that may affect the safety and performance of the battery, ensuring a comprehensive monitoring of the battery state, improving the comprehensiveness and accuracy of fault diagnosis. Further combining the current and historical fault information of the vehicle, it intelligently generates and executes charging protection actions, that is, it can determine the number of faults based on the current fault information and historical fault information, thereby determining the fault level, and can also consider the duration while determining the fault level, making the formulation of protection measures more targeted and effective. Matching corresponding charging protection actions according to the severity of the fault, the charging protection actions can be executed by the charging equipment controlled by the charging pile server or by the target vehicle, so as to achieve the purpose of double-loop charging protection, improve the reliability of vehicle charging protection decision-making and the safety of the charging process. At the same time, to avoid the influence of outdated information on subsequent decisions, the embodiment of the present application can also judge whether the target vehicle meets the preset fault clearing condition, thereby dynamically clearing the resolved or no longer existing fault information, ensuring the timeliness and accuracy of the fault record, and ensuring the sustainability of the fault, making it more intelligent and effective, and improving the user experience.

[0127] Figure 6 It is a schematic structural diagram of a charging cloud server provided by an embodiment of the present application. The charging cloud server may include:

[0128] A memory 601, a processor 602, and a computer program stored on the memory 601 and executable on the processor 602.

[0129] When the processor 602 executes the program, it implements the vehicle charging protection method provided in the above embodiments.

[0130] Furthermore, the charging cloud server further includes:

[0131] A communication interface 603 for communication between the memory 601 and the processor 602.

[0132] The memory 601 is used to store a computer program that can run on the processor 602.

[0133] The memory 601 may include a high-speed RAM memory, and may also include non-volatile memory, such as at least one disk memory.

[0134] If the memory 601, the processor 602, and the communication interface 603 are implemented independently, the communication interface 603, the memory 601, and the processor 602 can be interconnected through a bus and communicate with each other. The bus can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus, etc. The bus can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Figure 6 only a thick line is used to represent it in the figure, but it does not mean that there is only one bus or one type of bus.

[0135] Optionally, in a specific implementation, if the memory 601, the processor 602, and the communication interface 603 are integrated on a chip, the memory 601, the processor 602, and the communication interface 603 can communicate with each other through an internal interface.

[0136] The processor 602 may be a Central Processing Unit (CPU), or an Application Specific Integrated Circuit (ASIC), or one or more integrated circuits configured to implement the embodiments of the present application.

[0137] Figure 7Schematic diagram of the battery management system provided by the embodiments of the present application. The battery management system may include:

[0138] A memory 701, a processor 702, and a computer program stored on the memory 701 and executable on the processor 702.

[0139] When the processor 702 executes the program, it implements the charging protection method for the vehicle provided in the above embodiments.

[0140] Furthermore, the battery management system further includes:

[0141] A communication interface 703 for communication between the memory 701 and the processor 702.

[0142] The memory 701 is used to store a computer program executable on the processor 702.

[0143] The memory 701 may include a high-speed RAM memory, and may also include a non-volatile memory, such as at least one disk memory.

[0144] If the memory 701, the processor 702, and the communication interface 703 are implemented independently, the communication interface 703, the memory 701, and the processor 702 may be interconnected through a bus and communicate with each other. The bus may be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, an Extended Industry Standard Architecture (EISA) bus, etc. The bus may be divided into an address bus, a data bus, a control bus, etc. For the sake of representation, Figure 7 only a thick line is shown in the figure, but it does not mean that there is only one bus or one type of bus.

[0145] Optionally, in a specific implementation, if the memory 701, the processor 702, and the communication interface 703 are integrated on a chip, the memory 701, the processor 702, and the communication interface 703 may communicate with each other through an internal interface.

[0146] The processor 702 may be a Central Processing Unit (CPU), or an Application Specific Integrated Circuit (ASIC), or one or more integrated circuits configured to implement the embodiments of the present application.

[0147] The embodiments of the present application also provide a computer-readable storage medium, on which a computer program is stored. When the program is executed by a processor, the charging protection method of the vehicle as described above is implemented.

[0148] The embodiments of the present application also provide a computer program product, including a computer program. When the computer program is executed by a processor, the charging protection method of the vehicle provided by the embodiments of the present invention is implemented.

[0149] In the description of this specification, the descriptions with reference to the terms "one embodiment", "some embodiments", "example", "specific example", or "some examples", etc. mean that the specific features, structures, materials, or characteristics described in connection with the embodiment or example are included in at least one embodiment or example of the present application. In this specification, the schematic representations of the above terms do not necessarily refer to the same embodiment or example. Moreover, the specific features, structures, materials, or characteristics described can be combined in any one or N embodiments or examples in a suitable manner. In addition, without contradiction, those skilled in the art can combine and combine the different embodiments or examples described in this specification and the features of the different embodiments or examples.

[0150] In addition, the terms "first" and "second" are only used for descriptive purposes and cannot be understood as indicating or implying relative importance or implicitly specifying the quantity of the indicated technical features. Thus, the features defined with "first" and "second" may explicitly or implicitly include at least one of the features. In the description of the present application, the meaning of "N" is at least two, such as two, three, etc., unless otherwise specifically defined.

[0151] Any process or method description in the flowchart or described in other ways herein can be understood as representing a module, segment, or part of code including one or N executable instructions for implementing a customized logic function or process. The scope of the preferred embodiments of the present application includes additional implementations, where the functions can be executed in a substantially simultaneous manner or in a reverse order according to the involved functions, rather than in the order shown or discussed, which should be understood by those skilled in the art of the embodiments of the present application.

[0152] The logic and / or steps represented in the flowchart or otherwise described herein, for example, can be considered as a definable sequence list of executable instructions for implementing logical functions, which can be specifically implemented in any computer-readable medium for use by an instruction execution system, apparatus, or device (such as a computer-based system, a system including a processor, or other systems that can fetch and execute instructions from the instruction execution system, apparatus, or device), or used in combination with these instruction execution systems, apparatus, or devices. For the purposes of this specification, a "computer-readable medium" can be any device that can contain, store, communicate, propagate, or transmit a program for use by or in combination with an instruction execution system, apparatus, or device. More specific examples (non-exhaustive list) of computer-readable media include the following: an electrical connection portion (electronic device) having one or N wirings, a portable computer disk cartridge (magnetic device), a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber device, and a portable compact disc read-only memory (CDROM). Additionally, the computer-readable medium can even be paper or other suitable media on which the program can be printed, because the program can be obtained electronically by optically scanning the paper or other media, followed by editing, interpretation, or otherwise processing as appropriate, and then stored in a computer memory.

[0153] It should be understood that the various parts of the present application can be implemented by hardware, software, firmware, or a combination thereof. In the above-described embodiments, the N steps or methods can be implemented by software or firmware stored in a memory and executed by a suitable instruction execution system. If implemented in hardware, as in another embodiment, any one or a combination of the following techniques well known in the art can be used: discrete logic circuits having logic gate circuits for implementing logical functions on data signals, application-specific integrated circuits having suitable combinational logic gate circuits, programmable gate arrays (PGAs), field programmable gate arrays (FPGAs), and the like.

[0154] Those of ordinary skill in the art of this technology can understand that all or part of the steps carried by the methods of the above-described embodiments can be completed by a program instructing relevant hardware, and the program can be stored in a computer-readable storage medium. When the program is executed, it includes one or a combination of the steps of the method embodiments.

[0155] In addition, each functional unit in various embodiments of the present application may be integrated into a processing module, or each unit may exist physically alone, or two or more units may be integrated into one module. The above-mentioned integrated module may be implemented in the form of hardware or in the form of a software functional module. When the integrated module is implemented in the form of a software functional module and sold or used as an independent product, it may also be stored in a computer-readable storage medium.

[0156] The above-mentioned storage medium may be a read-only memory, a magnetic disk, an optical disc, etc. Although the embodiments of the present application have been shown and described above, it can be understood that the above embodiments are exemplary and should not be construed as limiting the present application. Those of ordinary skill in the art can make changes, modifications, substitutions, and variations to the above embodiments within the scope of the present application.

Claims

1. A charging protection method for a vehicle, characterized in that: Applied to a charging cloud server or a battery management system, wherein the method comprises the following steps: Receive current fault information of the target vehicle sent by the vehicle cloud server, and obtain historical fault information of the target vehicle; Combining the current fault information and the historical fault information, generating a charging protection action for the target vehicle; When the target vehicle is charging, the charging device controlled by the charging pile server is controlled to perform the charging protection action on the vehicle, or the target vehicle is controlled to perform the charging protection action.

2. The method according to claim 1, characterized in that The current fault information includes at least one of the fault information of battery cell overvoltage, battery total voltage overvoltage, battery overtemperature, charging overcurrent, maximum temperature deviation, maximum temperature difference deviation, maximum pressure difference deviation, temperature rise rate deviation, and battery internal resistance deviation of the power battery of the target vehicle, and the charging protection action is prohibiting vehicle charging action, limiting charging window and charging rate action, limiting charging window action or charging charging rate action.

3. The method according to claim 2, characterized in that The combining the current fault information and the historical fault information to match the charging protection action of the target vehicle includes: When the current fault information includes at least one of the fault information of the battery cell overvoltage, the battery total voltage overvoltage, the battery overtemperature, and the charging overcurrent, determining the fault number according to the current fault information and the historical fault information; A first fault level of the target vehicle is determined according to the number of faults, and the charging protection action is matched based on the first fault level.

4. The method according to claim 2, characterized in that: The combining the current fault information and the historical fault information to match the charging protection action of the target vehicle includes: When the current fault information includes at least one of the maximum temperature deviation, the maximum temperature difference deviation, the maximum pressure difference deviation, the temperature rise rate deviation and the battery internal resistance deviation, determining a second fault level and a corresponding duration of the target vehicle according to the current fault information and the historical fault information; The charging protection action is matched based on the second fault level and the duration.

5. The method according to claim 1, characterized in that Also includes: Based on the current fault information and / or the historical fault information, determining whether the target vehicle meets a preset fault clearing condition; If the fault clearing condition is met, the corresponding fault information is cleared.

6. A charging protection device for a vehicle, characterized in that: Applied to a charging cloud server or a battery management system, wherein the device comprises: An acquisition module, used to receive current fault information of a target vehicle sent by a vehicle cloud server, and acquire historical fault information of the target vehicle; A generating module, used to generate a charging protection action of the target vehicle by combining the current fault information and the historical fault information; The protection module is used to control the charging device controlled by the charging pile server to perform the charging protection action on the vehicle, or control the target vehicle to perform the charging protection action when the target vehicle is charging.

7. A charging cloud server, characterized in that: include: A memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the program to implement the vehicle charging protection method as described in any one of claims 1 to 5.

8. A battery management system, characterized in that: include: A memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the program to implement the vehicle charging protection method as described in any one of claims 1 to 5.

9. A computer-readable storage medium having a computer program stored thereon, characterized in that: The program is executed by a processor to implement the charging protection method for a vehicle as described in any one of claims 1 to 5.

10. A computer program product, a computer program, characterized in that When the computer program is executed, it is used to implement the charging protection method for a vehicle as described in any one of claims 1-5.

Images