Power battery management method, background server, battery management controller and power battery system
The dynamic key mechanism solves the problem of abuse of charging and discharging limits of power batteries under overvoltage or undervoltage conditions, realizes safe and controllable deactivation operation, and ensures the safety and legality of the power battery system.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-08-30
- Publication Date
- 2026-03-10
AI Technical Summary
In the early stages of vehicle commissioning or in scenarios where automatic charging is not fully implemented, the power battery may experience severe overvoltage or undervoltage, resulting in ineffective control of charge and discharge limits and the risk of abuse of the operation to lift charge and discharge limits.
A dynamic key mechanism is adopted. The backend server receives the request to remove the charging and discharging limit, obtains and sends the target dynamic key, and ensures the uniqueness and security of each unlocking operation, including the review process and the generation and verification process of the dynamic key.
This effectively prevents the abuse of charge and discharge limit operations, improves the safety and controllability of power battery management, and ensures the legality and uniqueness of lifting charge and discharge limits.
Smart Images
Figure CN121642218A_ABST
Abstract
Description
TECHNICAL FIELD
[0001] The present application relates to the technical field of vehicle control, in particular to a power battery management method, a background server, a battery management controller and a power battery system. BACKGROUND
[0002] In the use process of the power battery, the power battery system will monitor the cell voltage of the power battery in real time. If the cell voltage triggers the protection threshold, the power battery system will issue a serious overvoltage or serious under-voltage fault alarm to the vehicle and cut off the battery contactor and not respond to the subsequent charging or discharging request instruction (i.e. charging and discharging restriction on the power battery), thereby achieving the purpose of protecting the power battery. In the initial debugging of the vehicle, the battery limit test or the scene where automatic charging cannot be fully realized, the power battery may have a certain frequency of serious overvoltage or serious under-voltage. After the research and development engineers evaluate the actual situation, they give the conclusion that the charging and discharging restriction can be removed for continuous use or must be returned to the factory for repair. However, in actual operation, the after-sales personnel often bypass the research and development personnel and directly remove the charging and discharging restriction, which poses a risk that the charging and discharging restriction cannot be controlled. SUMMARY
[0003] In order to solve the above technical problems or at least partially solve the above technical problems, the present disclosure provides a power battery management method, a background server, a battery management controller and a power battery system.
[0004] To achieve the above-mentioned purpose, the first aspect of the present application provides a power battery management method, which comprises:
[0005] receiving a request for removing the charging and discharging restriction on the target power battery; and
[0006] obtaining a target dynamic key and sending the target dynamic key; wherein the target dynamic key is used to remove the charging and discharging restriction on the target power battery.
[0007] The power battery management method provided by the present application obtains a target dynamic key after receiving a request for removing the charging and discharging restriction on the target power battery, and then sends the target dynamic key to remove the charging and discharging restriction on the target power battery. Since the target dynamic key is dynamically changed, the unlocking key is strictly controlled from the process, which can eliminate the risk of abuse of the charging and discharging restriction removal operation from the source.
[0008] The second aspect of the present application also provides another power battery management method, which comprises:
[0009] receiving a target dynamic key; wherein the target dynamic key is used to remove the charging and discharging restriction on the target power battery;
[0010] Receive the key to be verified; and
[0011] When it is determined that the key to be verified matches the target dynamic key, the charging and discharging restrictions on the target power battery are lifted.
[0012] A third aspect of this application also provides a backend server for executing the power battery management method described in the first aspect.
[0013] A fourth aspect of this application also provides a battery management controller for performing the power battery management method described in the second aspect above.
[0014] The fifth aspect of this application also provides a power battery system, the power battery system including the back-end server described in the third aspect above, and / or including the battery management controller described in the fourth aspect above.
[0015] Additional aspects and advantages of this application will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice of this application. Attached Figure Description
[0016] Figure 1 This is a flowchart of the first power battery management method provided in the embodiments of this application;
[0017] Figure 2 This is a flowchart of the second power battery management method provided in the embodiments of this application;
[0018] Figure 3 This is a flowchart of the third power battery management method provided in the embodiments of this application;
[0019] Figure 4 This is a flowchart of the fourth power battery management method provided in the embodiments of this application.
[0020] The following detailed description of the embodiments will be provided in conjunction with the above-described drawings. Detailed Implementation
[0021] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of this application.
[0022] Furthermore, the terms "first," "second," etc., used in this specification are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of the invention described herein can be implemented in orders other than those illustrated or described herein. Additionally, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.
[0023] It should be noted that, where there is no conflict, the features in the embodiments of this application can be combined with each other.
[0024] Please see Figure 1 , Figure 1 This is a flowchart of a first power battery management method provided in an embodiment of this application. This application provides a power battery management method for removing charging and discharging restrictions on a power battery.
[0025] like Figure 1 As shown, the power battery management method includes:
[0026] Step S1: Receive a request to lift the charge / discharge restrictions on the target power battery; and,
[0027] Step S2: Obtain the target dynamic key and send the target dynamic key.
[0028] The target dynamic key is used to remove the charging and discharging restrictions on the target power battery.
[0029] The power battery management method provided in this application, after receiving a request to lift the charge and discharge restrictions on the target power battery, obtains the target dynamic key and then sends the target dynamic key to lift the charge and discharge restrictions on the target power battery. Since the target dynamic key is dynamically changing, the unlocking key is strictly controlled in the process, which can eliminate the risk of abuse of the operation to lift the charge and discharge restrictions from the source.
[0030] In some embodiments, the first power battery management method is applied to a backend server. Each power battery is configured with a corresponding battery management controller, and the backend server establishes a communication connection with each battery management controller. The battery management controller is used to limit the charge and discharge of the corresponding power battery and to remove the charge and discharge restrictions on the corresponding power battery. For example, the backend server may be a single server, a server cluster consisting of several servers, or a cloud computing service terminal, etc.
[0031] The battery management controller, also known as the battery management system (BMS), is a key component in electric vehicles. It is primarily responsible for monitoring and managing the battery pack's status, ensuring safe, efficient, and long-term battery operation. Exemplarily, the main functions of the BMS include: battery status monitoring, which monitors battery parameters such as voltage, current, and temperature in real time to assess battery health; charge / discharge management, which controls the battery charging process to prevent overcharging and overheating, extending battery life; and controls the battery discharging process to prevent over-discharging, protecting the battery; and limits or removes charge / discharge limits when the battery experiences severe overvoltage or undervoltage faults. Fault diagnosis, which detects abnormalities in the battery and electric vehicle system and provides fault diagnosis information; equalization management, which improves overall performance and lifespan by equalizing the charge levels of individual battery cells in the battery pack; data logging and communication, which records battery usage data and exchanges information with other vehicle systems (such as the onboard computer) via a communication interface; and thermal management, which monitors battery temperature and activates cooling or heating systems when necessary to maintain the battery within its optimal operating temperature range. Safety protection: When abnormal conditions are detected, such as battery overheating or abnormal voltage, the BMS can take measures to protect the battery, such as cutting off power or limiting output.
[0032] In some embodiments, receiving a request to lift the charge / discharge restrictions on the target power battery includes:
[0033] Receive the power battery fault information of the target power source.
[0034] The power battery fault information is used to determine whether the target power battery meets the conditions for lifting the charge and discharge restrictions.
[0035] The step of obtaining the target dynamic key and sending the target dynamic key includes:
[0036] If the target power battery is confirmed to meet the conditions for lifting the charge / discharge restrictions based on the power battery fault information, then the target dynamic key is obtained and sent.
[0037] The power battery management method also includes:
[0038] If the target power battery is confirmed to not meet the conditions for lifting the charge / discharge restrictions based on the power battery fault information, then the target dynamic key will not be obtained.
[0039] The backend server can determine whether the target power battery meets the conditions for lifting the charge and discharge restrictions by comparing the power battery fault information of the target power battery with the preset unlocking condition information.
[0040] Thus, since the target dynamic key is obtained only after determining that the target power battery meets the conditions for lifting the charge and discharge restrictions based on the power battery fault information of the target power battery, the security is higher.
[0041] Specifically, the backend server obtains different target dynamic keys for the same battery management controller in different key distribution processes. In other words, each target dynamic key can only be used once and is discarded after use, thus preventing the target dynamic key from being reused repeatedly.
[0042] In some embodiments, receiving a request to lift the charge / discharge restriction on the target power battery further includes:
[0043] Receive the power battery identification information of the target power battery.
[0044] The target dynamic key is obtained based on the power battery identification information.
[0045] In some embodiments, the power battery fault information and power battery identification information of the target power battery can be input by the applicant or sent by the battery management controller or other devices. The applicant can be after-sales personnel, their application account, or their terminal. For example, the power battery identification information and power battery fault information are input by after-sales personnel after analyzing and concluding that the charge / discharge restriction needs to be lifted, logging into the vehicle data monitoring platform associated with the backend server, and creating an application process to obtain the charge / discharge unlock key. The power battery identification information may include the vehicle identification ID, the power battery identification ID, and ID message data for the time period in which the power battery fault occurred. The vehicle identification ID and the power battery identification ID can be used by the backend server to lock the target power battery for which the charge / discharge restriction needs to be lifted, the battery management controller electrically connected to the target power battery, and the version number of its battery management program. The power battery fault information may include a description of the fault process and a conclusion on the fault cause analysis.
[0046] In some embodiments, the reviewer may determine whether the target power battery meets the conditions for lifting the charge / discharge restrictions. Specifically, before obtaining and sending the target dynamic key, the power battery management method further includes:
[0047] Output the power battery identification information and power battery fault information; and,
[0048] Upon receiving the key distribution approval instruction, it is determined that the target power battery meets the conditions for lifting the charge and discharge restrictions.
[0049] The reviewer can be a research and development (R&D) personnel, their review account, or their terminal. For example, when R&D personnel receive power battery identification information and power battery fault information from the vehicle data monitoring platform, and determine based on the power battery fault information that the target power battery meets the conditions for lifting charge / discharge restrictions, they can send a key distribution approval instruction to the backend server through the vehicle data monitoring platform. Conversely, if R&D personnel determine based on the power battery fault information that the target power battery does not meet the conditions for lifting charge / discharge restrictions, they can send a key distribution rejection instruction to the backend server through the vehicle data monitoring platform to close the application.
[0050] Since the target dynamic key is obtained by the backend server based on the power battery identification information only after the reviewer determines that the target power battery meets the conditions for lifting the charge and discharge restrictions, neither the applicant nor the reviewer can know the target dynamic key in advance before obtaining it.
[0051] Thus, after the applicant initiates the process of obtaining the charging and discharging unlocking key, the reviewer determines whether the target power battery meets the conditions for lifting the charging and discharging restrictions based on the power battery fault information. Only after the reviewer confirms that the target power battery meets the conditions for lifting the charging and discharging restrictions will the target dynamic key be obtained. This achieves a closed-loop process control from after-sales personnel submitting the unlocking application, to R&D personnel reviewing it online, to R&D personnel approving and authorizing the dynamic key (or rejecting the authorization of the dynamic key), and finally to after-sales personnel obtaining the key for unlocking. This results in higher key security.
[0052] In some embodiments, the target power battery is configured with N preset dynamic keys for invocation, where N≥2. These N preset dynamic keys can be stored in the battery management controller corresponding to the target power battery.
[0053] The step of obtaining the target dynamic key and sending the target dynamic key includes:
[0054] From the N preset dynamic keys corresponding to the target power battery, a preset dynamic key that has not been called before is selected as the target dynamic key; and...
[0055] Send the target dynamic key.
[0056] The battery management controller is applied to the vehicle and is electrically connected to the vehicle's in-vehicle information terminal. Thus, the backend server can retrieve the dynamic key from the battery management controller by establishing a communication connection with the in-vehicle information terminal.
[0057] Thus, by providing the backend server with the target dynamic key through a preset dynamic key library, implementation only requires modification to the battery management program of the battery management controller, resulting in minimal changes. Furthermore, since each preset dynamic key can only be used once and is discarded afterward, the abuse of charge / discharge cancellation operations can be prevented from the outset, enhancing security.
[0058] Furthermore, the target power battery is configured with a one-to-one correspondence between N preset dynamic keys and N serial numbers, and the values of the N serial numbers increase sequentially.
[0059] The step of calling an unused preset dynamic key from among the N preset dynamic keys corresponding to the target power battery as the target dynamic key includes:
[0060] From the N preset dynamic keys corresponding to the target power battery that have not been called, the preset dynamic key with the smallest serial number value is called as the target dynamic key.
[0061] Thus, the control logic is simpler by calling the dynamic key with the smallest serial number each time. Of course, in other embodiments, the target dynamic key can also be the dynamic key with the largest serial number that has not been called from among the N preset dynamic keys corresponding to the target power battery.
[0062] Furthermore, the N serial numbers are 1 to N. Of course, in other embodiments, the N serial numbers may also be other values.
[0063] The step of selecting the preset dynamic key with the smallest sequence number from among the N preset dynamic keys corresponding to the target power battery that has not been called includes:
[0064] When the dynamic key corresponding to the target power battery is called for the first time, the preset dynamic key with serial number 1 is called from the N preset dynamic keys corresponding to the target power battery as the target dynamic key;
[0065] When the dynamic key corresponding to the target power battery is invoked for the first time, obtain the cumulative number x of times the target power battery's charge / discharge restrictions have been lifted; and,
[0066] From the N preset dynamic keys corresponding to the target power battery, the preset dynamic key with sequence number x+1 is called as the target dynamic key. Wherein, N-1≥x≥1.
[0067] Optionally, when sending the target dynamic key to the applicant, the backend server may simultaneously send the sequence number of the target dynamic key. In this way, the applicant can also use the sequence number of the target dynamic key to determine the number of remaining unused dynamic keys among the N preset dynamic keys corresponding to the target power battery.
[0068] In some embodiments, the power battery management method further includes:
[0069] When all N preset dynamic keys corresponding to the target power battery have been invoked, N new preset dynamic keys are configured for the target power battery.
[0070] Specifically, when all N preset dynamic keys corresponding to the target power battery have been invoked, the N new preset dynamic keys can be sent to the battery management controller during a battery management program version upgrade. Optionally, when storing the N new preset dynamic keys in the battery management controller, the original N preset dynamic keys can be cleared. In this way, the N serial numbers can be reused, saving system resources.
[0071] In some embodiments, obtaining the target dynamic key includes:
[0072] Based on the power battery identification information, the target dynamic key is generated; and,
[0073] Send the target dynamic key.
[0074] The battery management controller may include a storage unit, in which the generated target dynamic key may be stored.
[0075] The target dynamic key generated by the backend server is a randomly generated key string according to a certain encryption rule agreed upon with the battery management controller. Optionally, when generating the target dynamic key, the backend server may also simultaneously generate an authorization serial number N0 corresponding to the target dynamic key, and send the authorization serial number to the target battery management controller corresponding to the target power battery, and also to the applicant. In this way, the cumulative number of times the charge / discharge restrictions of the target power battery have been lifted can be determined.
[0076] Furthermore, each of the battery management controllers may include a battery management control circuit and a wireless communication circuit electrically connected to each other. The battery management control circuit is used to limit or remove the charge / discharge restrictions on the corresponding power battery. The wireless communication circuit is used to establish a wireless communication connection with the backend server, enabling the battery management control circuit to communicate wirelessly with the backend server through the wireless communication circuit. The backend server is used to send the target dynamic key to the battery management control circuit through the wireless communication circuit.
[0077] Therefore, obtaining the target dynamic key through a fully automated dynamic key generation method offers higher security.
[0078] In some embodiments, the power battery management method further includes:
[0079] When sending the target dynamic key, the cumulative number of times the N preset dynamic keys corresponding to the target power battery are called is counted.
[0080] In some embodiments, the power battery management method further includes:
[0081] The system receives a successful charge / discharge release message from the target power battery and counts the cumulative number of times the target power battery's charge / discharge restrictions have been lifted. The successful charge / discharge release message is sent after the target power battery's charge / discharge restrictions have been lifted.
[0082] Please see Figure 2 , Figure 2 This is a flowchart of a second power battery management method provided in the embodiments of this application. This application also provides a second power battery management method, which includes:
[0083] Step S3: Receive the target dynamic key; wherein the target dynamic key is used to remove the charging and discharging restrictions on the target power battery;
[0084] Step S4, receive the key to be verified; and,
[0085] Step S5: When it is determined that the key to be verified matches the target dynamic key, the charging and discharging restrictions on the target power battery are lifted.
[0086] In some embodiments, the target dynamic key is obtained after the backend server receives a request to lift the charge and discharge restrictions on the target power battery.
[0087] The power battery management method provided in this application uses a dynamic key as the unlocking message. By receiving the key to be verified and determining that the key to be verified matches the target dynamic key, the charging and discharging restrictions on the target power battery are lifted. Since the target dynamic key is dynamically changing, the unlocking key is strictly controlled in the process, which can eliminate the risk of abuse of the operation to lift the charging and discharging restrictions from the source.
[0088] In some embodiments, the second power battery management method is applied to a battery management controller, which establishes a communication connection with a backend server. The target dynamic key is obtained based on the power battery fault information and sent to the applicant after determining that the target power battery meets the conditions for lifting charge / discharge restrictions.
[0089] The key to be verified can be entered by the applicant into the battery management controller.
[0090] In some embodiments, the battery management controller can obtain the verification key input by the applicant via hardwired communication. Specifically, the monitoring host computer is hardwired to the vehicle diagnostic interface of the battery management controller, so that the applicant can input the verification key to the battery management controller through the monitoring host computer. In other embodiments, the battery management controller can obtain the verification key input by the applicant via wireless communication or near-field communication. Specifically, the vehicle can be equipped with a wireless communication circuit electrically connected to the battery management controller, which is used to establish a wireless communication connection with the backend server, so that the applicant can input the verification key to the battery management controller through the backend server; or the vehicle can be equipped with a near-field communication module electrically connected to the battery management controller, which is used to establish a wireless communication connection with a mobile terminal with near-field communication capability, so that the applicant can input the verification key to the battery management controller through the mobile terminal.
[0091] In some embodiments, the target power battery is configured with N preset dynamic keys for invocation, where N≥2.
[0092] The power battery management method also includes:
[0093] When the key to be verified matches a preset dynamic key that has not been invoked among the N preset dynamic keys, it is determined that the key to be verified matches the target dynamic key.
[0094] The N preset dynamic keys can be written by the battery management controller when the battery management program is first burned.
[0095] Thus, by providing the backend server with the target dynamic key through a preset dynamic key library, implementation only requires modification to the battery management program of the battery management controller, resulting in minimal changes. Furthermore, since each preset dynamic key can only be used once and is discarded afterward, the abuse of charge / discharge cancellation operations can be prevented from the outset, enhancing security.
[0096] In some embodiments, the target power battery is configured with a one-to-one correspondence between N preset dynamic keys and N serial numbers, where the values of the N serial numbers increase sequentially. The N preset dynamic keys are called in ascending order of their serial number values.
[0097] The step of determining that the key to be verified matches the target dynamic key when the key to be verified matches a preset dynamic key that has not been called among the N preset dynamic keys includes:
[0098] When the key to be verified matches a preset dynamic key with a sequence number greater than or equal to x+1 among the N preset dynamic keys, it is determined that the key to be verified matches a preset dynamic key that has not been called among the N preset dynamic keys.
[0099] Where x is the cumulative number of times the target power battery has had its charge / discharge restrictions lifted.
[0100] In some embodiments, the power battery management method further includes:
[0101] When the key to be verified matches a preset dynamic key with a sequence number less than x+1 among the N preset dynamic keys, a first prompt signal is issued to indicate that the key to be verified has been used.
[0102] In some embodiments, the power battery management method further includes:
[0103] If the key to be verified does not match any of the N preset dynamic keys, a second prompt signal is issued to indicate that the key to be verified is incorrect.
[0104] In some embodiments, the power battery management method further includes:
[0105] After the charge / discharge restriction on the target power battery is lifted, a charge / discharge lifting success message is sent to count the cumulative number of times the charge / discharge restriction on the target power battery has been lifted.
[0106] In some embodiments, the power battery management method further includes:
[0107] Before lifting the charge / discharge restrictions on the target power battery, clear the fault alarm, reply with a message indicating successful alarm clearance, and then restart.
[0108] In some embodiments, receiving the target dynamic key includes:
[0109] Receive the target dynamic key and store the target dynamic key.
[0110] The target dynamic key is automatically generated based on the power battery identification information of the target power battery.
[0111] The target dynamic key can be stored in the storage unit of the battery management controller, and the storage unit will clear the historical dynamic key before storing the target dynamic key.
[0112] In this way, the target dynamic key is obtained by generating a dynamic key automatically, and the historical dynamic key is cleared after use, which improves security.
[0113] Furthermore, the power battery management method also includes:
[0114] When the key to be verified matches the target dynamic key that is pre-stored, it is determined that the key to be verified matches the target dynamic key.
[0115] Please see Figure 3 , Figure 3 This is a flowchart illustrating a third power battery management method provided in an embodiment of this application. This application also provides a third power battery management method, which is applied to a power battery system, the power battery system including the backend server and the battery management controller.
[0116] like Figure 3 As shown, the power battery management method includes:
[0117] Step S10: The backend server receives a request to lift the charge / discharge restrictions on the target power battery.
[0118] Step S20: The backend server obtains the target dynamic key and sends the target dynamic key;
[0119] Step S30: The battery management controller receives the target dynamic key;
[0120] Step S40, the battery management controller receives the key to be verified; and,
[0121] In step S50, when the battery management controller determines that the key to be verified matches the target dynamic key, it removes the charging and discharging restrictions on the target power battery.
[0122] The target dynamic key is obtained after receiving a request to lift the charging and discharging restrictions on the target power battery.
[0123] Please see Figure 4 , Figure 4 This is a flowchart of a fourth power battery management method provided in this application. In some embodiments, the backend server receives a request to lift the charge / discharge restrictions on the target power battery, including:
[0124] Step S11: The background server receives the power battery fault information of the target power battery.
[0125] The power battery fault information is used to determine whether the target power battery meets the conditions for lifting the charge / discharge restrictions. The target dynamic key is obtained after the target power battery meets the conditions for lifting the charge / discharge restrictions.
[0126] In some embodiments, the backend server receiving a request to lift the charge / discharge restrictions on the target power battery further includes:
[0127] Step S12: The backend server receives the power battery identification information of the target power battery.
[0128] The target dynamic key is obtained based on the power battery identification information.
[0129] In some embodiments, before the backend server obtains the target dynamic key and sends the target dynamic key, the power battery management method further includes:
[0130] Step S13: The backend server outputs the power battery identification information and power battery fault information of the target power battery; and,
[0131] In step S14, when the backend server receives the key distribution approval instruction, it determines that the target power battery meets the conditions for lifting the charge and discharge restrictions.
[0132] In some embodiments, the target power battery is configured with N preset dynamic keys, where N≥2.
[0133] The backend server obtains the target dynamic key, including:
[0134] The backend server retrieves an unused preset dynamic key from among the N preset dynamic keys corresponding to the target power battery as the target dynamic key; and...
[0135] The backend server sends the target dynamic key.
[0136] Furthermore, the target power battery is configured with a one-to-one correspondence between N preset dynamic keys and N serial numbers, and the values of the N serial numbers increase sequentially.
[0137] The backend server retrieves an unused preset dynamic key from among N preset dynamic keys corresponding to the target power battery as the target dynamic key, including:
[0138] The backend server selects the preset dynamic key with the smallest serial number from among the N preset dynamic keys corresponding to the target power battery that has not been called, and uses it as the target dynamic key.
[0139] Furthermore, the N sequence numbers are from 1 to N.
[0140] The backend server selects the preset dynamic key with the smallest sequence number from among the N preset dynamic keys corresponding to the target power battery that has not been called, and uses it as the target dynamic key, including:
[0141] When the backend server calls the dynamic key corresponding to the target power battery for the first time, it calls the preset dynamic key with serial number 1 from the N preset dynamic keys corresponding to the target power battery as the target dynamic key.
[0142] When the backend server calls the dynamic key corresponding to the target power battery for the first time, it obtains the cumulative number x of times the target power battery's charge / discharge restrictions have been lifted; and...
[0143] The backend server selects the preset dynamic key with sequence number x+1 from the N preset dynamic keys corresponding to the target power battery as the target dynamic key. Wherein, N-1≥x≥1.
[0144] In some embodiments, the power battery management method further includes:
[0145] When all N preset dynamic keys corresponding to the target power battery have been called, the backend server configures N new preset dynamic keys for the target power battery.
[0146] In some embodiments, the backend server obtains the target dynamic key, including:
[0147] The backend server generates the target dynamic key based on the power battery identification information; and,
[0148] The backend server sends the target dynamic key.
[0149] In some embodiments, the power battery management method further includes:
[0150] When sending the target dynamic key, the backend server counts the cumulative number of times the N preset dynamic keys corresponding to the target power battery are called.
[0151] In some embodiments, the power battery management method further includes:
[0152] The backend server receives the charge / discharge release success message from the target power battery and counts the cumulative number of times the target power battery's charge / discharge restrictions have been lifted. The charge / discharge release success message is sent after the target power battery's charge / discharge restrictions have been lifted.
[0153] In some embodiments, the target power battery is configured with N preset dynamic keys for invocation, where N≥2.
[0154] The power battery management method also includes:
[0155] When the key to be verified matches a preset dynamic key that has not been called among the N preset dynamic keys, the battery management controller determines that the key to be verified matches the target dynamic key.
[0156] In some embodiments, the target power battery is configured with a one-to-one correspondence between N preset dynamic keys and N serial numbers, where the values of the N serial numbers increase sequentially. The N preset dynamic keys are called in ascending order of their serial number values.
[0157] When the key to be verified matches a preset dynamic key that has not been invoked among the N preset dynamic keys, the battery management controller determines that the key to be verified matches the target dynamic key, including:
[0158] When the key to be verified matches a preset dynamic key whose sequence number is greater than or equal to x+1 among the N preset dynamic keys, the battery management controller determines that the key to be verified is a preset dynamic key that has not been called among the N preset dynamic keys.
[0159] Where x is the cumulative number of times the target power battery has been de-charged and de-discharged.
[0160] In some embodiments, the power battery management method further includes:
[0161] When the key to be verified matches a preset dynamic key with a serial number less than x+1 among the N preset dynamic keys, the battery management controller issues a first prompt signal to indicate that the key to be verified has been used.
[0162] In some embodiments, the power battery management method further includes:
[0163] When the key to be verified is inconsistent with any of the N preset dynamic keys, the battery management controller issues a second prompt signal to indicate that the key to be verified is incorrect.
[0164] In some embodiments, the power battery management method further includes:
[0165] After the battery management controller removes the charge / discharge restrictions on the target power battery, it sends a charge / discharge removal success message to count the cumulative number of times the charge / discharge restrictions on the target power battery have been removed.
[0166] In some embodiments, the power battery management method further includes:
[0167] Before removing the charge / discharge restrictions on the target power battery, the battery management controller clears the fault alarm, replies with a message indicating successful alarm clearance to the backend server, and restarts.
[0168] In some embodiments, the power battery management method further includes:
[0169] The battery management controller receives the target dynamic key sent by the backend server and stores the target dynamic key. The target dynamic key is automatically generated based on the power battery identification information of the target power battery.
[0170] Furthermore, the power battery management method also includes:
[0171] When the key to be verified matches the target dynamic key that is pre-stored, the battery management controller determines that the key to be verified matches the target dynamic key.
[0172] It should be noted that the steps executed by the backend server in the third power battery management method correspond to those in the first power battery management method described above, and the steps executed by the battery management controller in the third power battery management method correspond to those in the second power battery management method described above. For a more detailed description, please refer to the contents of the various embodiments of the first and second power battery management methods described above.
[0173] This application also provides a backend server, which is used to receive a request to remove the charge / discharge restrictions on a target power battery, obtain a target dynamic key, and send the target dynamic key. The target dynamic key is used to remove the charge / discharge restrictions on the target power battery.
[0174] For example, the backend server may be a single server, a server cluster consisting of several servers, or a cloud computing service terminal, etc.
[0175] In some embodiments, the backend server is specifically used to receive power battery fault information of the target power battery, and when it is determined from the power battery fault information that the target power battery meets the conditions for lifting the charge and discharge restrictions, obtain the target dynamic key and send the target dynamic key, and when it is determined from the power battery fault information that the target power battery does not meet the conditions for lifting the charge and discharge restrictions, not obtain the target dynamic key.
[0176] In some embodiments, the backend server is further configured to receive power battery identification information of the target power battery. The target dynamic key is obtained based on the power battery identification information.
[0177] In some embodiments, the backend server is further configured to output the power battery identification information and power battery fault information, and upon receiving a key distribution approval instruction, determine that the target power battery meets the conditions for lifting the charge and discharge restrictions.
[0178] In some embodiments, the target power battery is configured with N preset dynamic keys, where N≥2. The backend server is used to select an unused preset dynamic key from the N preset dynamic keys corresponding to the target power battery as the target dynamic key, and to send the target dynamic key.
[0179] In some embodiments, the target power battery is configured with a one-to-one correspondence between N preset dynamic keys and N serial numbers, where the values of the N serial numbers increase sequentially. Specifically, the backend server is used to select the preset dynamic key with the smallest serial number from among the N preset dynamic keys corresponding to the target power battery that has not yet been called, and use it as the target dynamic key.
[0180] In some embodiments, the N serial numbers are 1 to N. The backend server is configured to, upon first invoking the dynamic key corresponding to the target power battery, retrieve the preset dynamic key with serial number 1 from the N preset dynamic keys corresponding to the target power battery as the target dynamic key; and upon subsequent invokings of the dynamic key corresponding to the target power battery, obtain the cumulative number x of times the target power battery's charge / discharge restrictions have been lifted, and retrieve the preset dynamic key with serial number x+1 from the N preset dynamic keys corresponding to the target power battery as the target dynamic key. Where N-1 ≥ x ≥ 1.
[0181] In some embodiments, the backend server is further configured to configure N new preset dynamic keys for the target power battery when all N preset dynamic keys corresponding to the target power battery have been invoked.
[0182] In some embodiments, each of the battery management controllers includes a storage unit. Specifically, the backend server is configured to generate the target dynamic key based on the power battery identification information, and send the target dynamic key to the target battery management controller, so that the target battery management controller stores the target dynamic key in the storage unit and sends the target dynamic key.
[0183] In some embodiments, the backend server is further configured to receive a charge / discharge release success message from the target power battery and to count the cumulative number of times the charge / discharge restriction of the target power battery has been lifted. The charge / discharge release success message is sent after the charge / discharge restriction of the target power battery has been lifted.
[0184] It should be noted that the backend server corresponds to the first power battery management method described above. For a more detailed description, please refer to the contents of the various embodiments of the first power battery management method described above.
[0185] This application also provides a battery management controller, which establishes a communication connection with the backend server to receive a target dynamic key, receive a key to be verified, and, when it is determined that the key to be verified matches the target dynamic key, remove the charging and discharging restrictions on the target power battery.
[0186] The target dynamic key is obtained by the backend server after receiving the request from the applicant to lift the charging and discharging restrictions on the target power battery and then sent to the applicant.
[0187] In some embodiments, the target power battery is configured with N preset dynamic keys for invocation, where N≥2. The battery management controller is specifically used to receive the key to be verified, and when the key to be verified matches a preset dynamic key that has not been invoked among the N preset dynamic keys, it determines that the key to be verified matches the target dynamic key.
[0188] In some embodiments, the target power battery is configured with a one-to-one correspondence between N preset dynamic keys and N serial numbers, where the values of the N serial numbers increase sequentially. The N preset dynamic keys are called in ascending order of their serial numbers. Specifically, the battery management controller is used to determine whether the key to be verified matches a preset dynamic key among the N preset dynamic keys whose serial number is greater than or equal to x+1, and when the key to be verified matches a preset dynamic key among the N preset dynamic keys whose serial number is greater than or equal to x+1, it determines that the key to be verified matches a preset dynamic key among the N preset dynamic keys that has not been called. Here, x is the cumulative number of times the target power battery has been de-charged and de-discharged.
[0189] In some embodiments, the battery management controller is further configured to issue a first prompt signal when the key to be verified matches a preset dynamic key with a sequence number less than x+1 among the N preset dynamic keys, so as to indicate that the key to be verified has been used.
[0190] In some embodiments, the battery management controller is further configured to send a charge / discharge release success message to the backend server after the charge / discharge restriction on the target power battery is lifted, so that the backend server can count the cumulative number of times the charge / discharge restriction on the target power battery has been lifted.
[0191] In some embodiments, the battery management controller includes a storage unit. The battery management controller is further configured to acquire and store the target dynamic key. The target dynamic key is automatically generated based on the power battery identification information of the target power battery.
[0192] In some embodiments, the battery management controller is specifically configured to receive a key to be verified, and when the key to be verified matches the target dynamic key stored in advance, determine that the key to be verified matches the target dynamic key.
[0193] It should be noted that the battery management controller corresponds to the second power battery management method described above. For a more detailed description, please refer to the various embodiments of the second power battery management method described above.
[0194] This application also provides a power battery system, which includes a backend server as described in any of the above embodiments, and / or a battery management controller as described in any of the above embodiments.
[0195] It should be noted that the power battery system corresponds to the third power battery management method mentioned above. For a more detailed description, please refer to the contents of the various embodiments of the third power battery management method mentioned above.
[0196] Based on the same inventive concept, this application also provides a computer-readable storage medium storing a computer program, which is executed by a processor to implement the steps of the power battery management method described in any of the above embodiments.
[0197] The computer storage medium in this application embodiment can be any combination of one or more computer-readable media. A computer-readable medium can be a computer-readable signal medium or a computer-readable storage medium. A computer-readable storage medium can be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of computer-readable storage media (a non-exhaustive list) include: an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination thereof. In this document, 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.
[0198] Computer-readable signal media may include data signals propagated in baseband or as part of a carrier wave, carrying computer-readable program code. Such propagated data signals may take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. Computer-readable signal media may also be any computer-readable medium other than computer-readable storage media, capable of sending, propagating, or transmitting programs for use by or in connection with an instruction execution system, apparatus, or device.
[0199] Program code contained on a computer-readable medium may be transmitted using any suitable medium, including but not limited to wireless, wire, optical fiber, RF, etc., or any suitable combination thereof.
[0200] Computer program code for performing the operations of this invention can be written in one or more programming languages or a combination thereof, including object-oriented programming languages such as Java, Smalltalk, and C++, as well as conventional procedural programming languages such as C or similar languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving remote computers, the remote computer can be connected to the user's computer via any type of network, including a local area network (LAN) or a wide area network (WAN), or can be connected to an external computer (e.g., via the Internet using an Internet service provider).
[0201] Although embodiments of this application have been shown and described, those skilled in the art will understand that various changes, modifications, substitutions and alterations can be made to these embodiments without departing from the principles and spirit of this application, the scope of which is defined by the claims and their equivalents.
Claims
1. A method of managing a power battery, characterized in that, The power battery management method comprises: receiving a request for removing the charge and discharge restriction on the target power battery; and obtaining a target dynamic key and sending the target dynamic key; wherein the target dynamic key is used to remove the charge and discharge restriction on the target power battery.
2. The power battery management method of claim 1, wherein, The receiving the request for removing the charge and discharge restriction on the target power battery comprises: receiving power battery fault information of the target power battery; wherein the power battery fault information is used to determine whether the target power battery meets the condition for removing the charge and discharge restriction; The obtaining the target dynamic key and sending the target dynamic key comprises: if it is confirmed according to the power battery fault information that the target power battery meets the condition for removing the charge and discharge restriction, obtaining the target dynamic key and sending the target dynamic key.
3. The power battery management method of claim 2, wherein, The receiving the request for removing the charge and discharge restriction on the target power battery further comprises: receiving power battery identification information of the target power battery; wherein the target dynamic key is obtained according to the power battery identification information.
4. The power battery management method of claim 1, wherein, The target power battery is correspondingly configured with N preset dynamic keys, and N≥2; the obtaining the target dynamic key and sending the target dynamic key comprises: calling an un-called preset dynamic key from the N preset dynamic keys corresponding to the target power battery as the target dynamic key; and sending the target dynamic key.
5. The power battery management method of claim 4, wherein, The target power battery is correspondingly configured with a one-to-one correspondence relationship between N preset dynamic keys and N serial numbers, and the values of the N serial numbers increase in turn; The calling the un-called preset dynamic key from the N preset dynamic keys corresponding to the target power battery as the target dynamic key comprises: calling a preset dynamic key with the smallest serial number value from the un-called preset dynamic keys of the N preset dynamic keys corresponding to the target power battery as the target dynamic key.
6. The power battery management method of claim 5, wherein, The N serial numbers are 1 to N; the calling the un-called preset dynamic key from the N preset dynamic keys corresponding to the target power battery as the target dynamic key comprises: when the dynamic key corresponding to the target power battery is called for the first time, calling a preset dynamic key with a serial number of 1 from the N preset dynamic keys corresponding to the target power battery as the target dynamic key; when the dynamic key corresponding to the target power battery is called for the first time, calling a preset dynamic key with a serial number of 1 from the N preset dynamic keys corresponding to the target power battery as the target dynamic key; obtaining a cumulative number x of times that the target power battery is removed from the charge and discharge restriction; and 7. The power battery management method of claim 6, wherein, calling a preset dynamic key with a serial number of x+1 from the N preset dynamic keys corresponding to the target power battery as the target dynamic key; wherein N-1≥x≥1. The power battery management method further comprises:
8. The power battery management method of claim 1, wherein, when all the N preset dynamic keys corresponding to the target power battery are called, configuring N new preset dynamic keys for the target power battery. The obtaining the target dynamic key and sending the target dynamic key comprises: generating the target dynamic key according to the power battery identification information; and sending the target dynamic key.
9. The power battery management method of claim 6, wherein, The power battery management method further includes: receiving a charge-discharge release success message of the target power battery, and counting the accumulated number of times that the target power battery is released from the charge-discharge restriction; wherein the charge-discharge release success message is sent after the target power battery is released from the charge-discharge restriction.
10. A method of managing a power battery, characterized in that, The power battery management method includes: receiving a target dynamic key; wherein the target dynamic key is used to release the charge-discharge restriction on the target power battery; receiving a to-be-verified key; and releasing the charge-discharge restriction on the target power battery when it is determined that the to-be-verified key matches the target dynamic key.
11. The power cell management method of claim 10, wherein, The target power battery is correspondingly configured with N preset dynamic keys for calling, and N≥2; the power battery management method further includes: determining that the to-be-verified key matches the target dynamic key when the to-be-verified key matches a preset dynamic key that has not been called among the N preset dynamic keys.
12. The power cell management method of claim 11, wherein, The target power battery is correspondingly configured with a one-to-one correspondence relationship between N preset dynamic keys and N serial numbers, and the values of the N serial numbers increase sequentially; the N preset dynamic keys are called in the order of the serial number values from small to large; The determination that the to-be-verified key matches the target dynamic key when the to-be-verified key matches a preset dynamic key that has not been called among the N preset dynamic keys includes: determining that the to-be-verified key matches the preset dynamic key that has not been called among the N preset dynamic keys when the to-be-verified key matches a preset dynamic key whose serial number is greater than or equal to x+1 among the N preset dynamic keys; wherein x is the accumulated number of times that the target power battery is released from the charge-discharge restriction.
13. The power cell management method of claim 12, wherein, The power battery management method further includes: sending a first prompt signal to prompt that the to-be-verified key has been used when the to-be-verified key matches a preset dynamic key whose serial number is less than x+1 among the N preset dynamic keys.
14. The power cell management method of claim 10, wherein, The power battery management method further includes: sending a charge-discharge release success message after releasing the charge-discharge restriction on the target power battery, so as to count the accumulated number of times that the target power battery is released from the charge-discharge restriction.
15. The power cell management method of claim 10, wherein, The receiving of the target dynamic key includes: receiving the target dynamic key and storing the target dynamic key; wherein the target dynamic key is automatically generated according to the power battery identification information of the target power battery.
16. The power cell management method of claim 15, wherein, The power battery management method further includes: determining that the to-be-verified key matches the target dynamic key when the to-be-verified key matches the target dynamic key stored in advance.
17. A back-end server, characterized by The background server is configured to perform the power battery management method according to any one of claims 1-9.
18. A battery management controller, comprising: The battery management controller is configured to perform the power battery management method according to any one of claims 10-16.
19. A power battery system, characterized in that The power battery system includes the background server according to claim 17 and / or the battery management controller according to claim 18.