Battery evaluation method and related device

Abstract

A battery evaluation method and a related apparatus are provided. The method includes: when a device under test satisfies a trigger condition of a battery evaluation task, a first device controls the device under test to perform a charge / discharge process corresponding to the battery evaluation task, and acquires test data for the device under test during the charge / discharge process (S201); the first device determines a battery evaluation result based on the test data (S202); and the first device transmits the battery evaluation result to a second device (S203). This technical solution can improve the efficiency of acquiring the battery evaluation result.

Description

[Technical Field]

[0001] Technical Field This application relates to the field of new energy technologies, and in particular to battery evaluation methods and related devices. [Background technology]

[0002] Battery health directly reflects the battery's energy storage value. For original equipment manufacturers (OEMs), accurately understanding the health of vehicle batteries can provide support for battery after-sales service and provide effective input for battery research and development, thereby improving the overall product performance of vehicles. For users, accurately understanding the health of vehicle batteries can improve vehicle reliability, reduce mileage concerns caused by external environmental fluctuations, and help them know the vehicle's residual value, making overall vehicle value prediction more realistic.

[0003] Currently, vehicles are usually sent to specialized testing laboratories for testing to obtain vehicle battery evaluation results. However, this solution requires a lot of manual intervention and long testing periods, and there is a need to improve the efficiency of obtaining battery evaluation results. Summary of the Invention [Problem to be solved by the invention]

[0004] SUMMARY OF THE INVENTION The embodiments of the present application provide a battery evaluation method and related apparatus to improve the efficiency of obtaining battery evaluation results. [Means for solving the problem]

[0005] According to a first aspect, an embodiment of the present application provides a battery evaluation method, the method including:

[0006] When the device under test satisfies a trigger condition of the battery evaluation task, the first device controls the device under test to perform a charge / discharge process corresponding to the battery evaluation task, and obtains test data of the device under test in the charge / discharge process; The first device determines a battery evaluation result based on the test data; The first device transmits the battery assessment result to the second device.

[0007] According to the above embodiment, when the device under test satisfies the trigger condition of the battery evaluation task, the first device controls the device under test to perform a charge / discharge process corresponding to the battery evaluation task, obtains test data for the device under test during the charge / discharge process, and determines a battery evaluation result based on the test data. That is, the first device automatically performs the battery evaluation task to obtain a battery evaluation result for the device under test, and the first device transmits the battery evaluation result to the second device. The user can know the battery evaluation result by viewing the information received by the second device. In this way, the user does not need to send the device under test to a specialized testing facility for battery evaluation. This reduces manual intervention and time costs and improves the efficiency of obtaining battery evaluation results.

[0008] In a possible implementation, the first device controlling the device under test to perform a charge / discharge process corresponding to the battery evaluation task includes:

[0009] When obtaining authorization to perform the battery evaluation task, the first device controls the device under test to perform a charge / discharge process corresponding to the battery evaluation task.

[0010] In the above implementation, when the first device has obtained authorization to perform the battery evaluation task, the first device performing the battery evaluation task may be understood as the first device performing the battery evaluation task when the user agrees to provide authorization, thereby avoiding an impact on use of the device under test due to the first device performing the battery evaluation task when the user does not agree to provide authorization.

[0011] In a possible implementation, the method further includes:

[0012] When the first device does not obtain authorization to perform the battery assessment task, the first device sends request information to the second device; The first device receives authorization information sent by the second device, where the authorization information is used to authorize the first device to perform the battery assessment task.

[0013] In the above implementation, when the first device does not obtain authorization to perform the battery assessment task, the first device may send request information to the second device and send a request to the user to obtain authorization to perform the battery assessment task. When the user agrees to provide authorization, the second device may send authorization information to the first device, and the first device may receive the authorization information sent by the second device and obtain authorization to perform the battery assessment task.

[0014] In a possible implementation, the authorization information includes the number of authorizations and / or the authorization period.

[0015] In the above implementation, the authorization information may include an authorization count, an authorization period, or both an authorization count and an authorization period, so that the user can flexibly set the number of times and / or the period for which the first device is allowed to perform the battery assessment task based on actual requirements.

[0016] In a possible implementation, the trigger condition includes being able to accurately obtain the state of charge of the device under test.

[0017] In a possible implementation, the trigger condition includes the device under test being in a fully charged state.

[0018] In the above implementation, when the device under test is in a fully charged state, the first device is triggered to perform the battery evaluation task, thereby ensuring the stability and reliability of the trigger opportunity, and the first device can start the battery evaluation task at a stable and reliable opportunity.

[0019] In a possible implementation, the trigger condition includes the cumulative mileage of the device under test being greater than a preset mileage and / or the cumulative number of times the device under test has been charged being greater than a preset number.

[0020] In the above implementation, when the cumulative mileage of the device under test is greater than a preset mileage and / or the cumulative number of times the device under test has been charged is greater than a preset number, the battery of the device under test may be degraded to a certain extent. In this case, it may be deemed necessary to evaluate the battery status of the device under test, and the first device is triggered to perform a battery evaluation task. In this way, the first device can reduce unnecessary battery evaluation tasks, thereby saving computing resources.

[0021] In a possible implementation, the first device controls the device under test to perform a charge / discharge process corresponding to the battery evaluation task, and acquiring test data of the device under test in the charge / discharge process includes:

[0022] The first device controls the device under test to discharge, and obtains a first charge state after the device under test finishes discharging; the first device acquires a second charge state and charge amount of the device under test, where the second charge state corresponds to a charge state obtained when the device under test is charged until a charge termination condition is met, and the charge amount corresponds to a charge amount of the device under test from the end of discharging to the time when the device is charged until a charge termination condition is met; The test data includes a first state of charge, a second state of charge, and a charge amount.

[0023] In the above implementation, the available electrical energy of the battery can be accurately reflected based on the first state of charge, the second state of charge, and the charge amount, and a highly accurate battery evaluation result is determined based on the available electrical energy of the battery.

[0024] In a possible implementation, the first device controlling the device under test to discharge includes:

[0025] The first device controls the device under test to self-discharge until a discharge termination condition is met; and / or The first device sends first reminder information to the second device, where the first reminder information reminds the user to discharge the device under test until a discharge termination condition is met.

[0026] In the above implementation, the first device may control the device under test to self-discharge until the discharge termination condition is met. In this way, the discharge process of the device under test is implemented automatically without manual intervention. Alternatively, the first device may send first reminder information to the second device to remind the user to discharge the device under test until the discharge termination condition is met. This allows the user to determine whether to discharge the device under test by using the device under test based on actual needs. This helps to effectively utilize the battery level of the device under test.

[0027] In a possible implementation, the discharge termination condition includes the state of charge of the device under test being below a first threshold.

[0028] In the above implementation, when the charge state of the device under test is less than the first threshold, the device under test terminates discharging, which may cause the device under test to enter a low battery state after discharging is terminated. In this case, the charge state of the device under test is used as the charge state obtained when the device under test starts charging. This ensures the reliability of the charge state obtained when the device under test starts charging.

[0029] In a possible implementation, the method further includes:

[0030] monitoring parameter data of the device under test while the first device controls the device under test to self-discharge; When detecting that an exception occurs in the parameter data, the first device transmits alarm information to the second device and controls the device under test to terminate self-discharge.

[0031] In the above implementation, when the first device detects that an exception occurs in the parameter data of the device under test during the process of controlling the device under test to perform self-discharge, the first device sends warning information to the second device, so that the user can be notified of the exception in a timely manner. In addition, the first device controls the device under test to end self-discharge, which helps to avoid possible security risks in a timely manner.

[0032] In a possible implementation, obtaining the first charge state after the device under test finishes discharging includes:

[0033] After the device under test has finished discharging and remained in an idle state for a first period of time, the first device acquires a first open circuit voltage of the device under test; The first device obtains a first state of charge based on the state of charge corresponding to the first open circuit voltage.

[0034] In the above implementation, the first open-circuit voltage is first obtained after the device under test has finished discharging and remained in an idle state for a certain period of time, and then the first state of charge is obtained based on the state of charge corresponding to the first open-circuit voltage, so that the first state of charge obtained is highly accurate.

[0035] In a possible implementation, the first device obtaining the second charge state and charge amount of the device under test includes:

[0036] After the device under test finishes discharging and remains in an idle state for a first period of time, the first device controls the device under test to be charged and obtains a second charge state and charge amount of the device under test.

[0037] In the above implementation, after the device under test finishes discharging and remains in an idle state for a first period, the first device controls the device under test to start charging. Since the charge state after the device under test finishes discharging and remains in an idle state for the first period can be accurately obtained based on the open-circuit voltage, the charge state is used as the charge state obtained when the device under test starts charging. This can improve the reliability of the charge state obtained when the device under test starts charging.

[0038] In a possible implementation, the first device controlling the device under test to be charged includes: when the device under test is connected to the charging pile, the first device turns on a charging switch of the device under test to allow the device under test to be charged until a charging termination condition is met.

[0039] In the above implementation, when the device under test is connected to the charging pile, the first device can turn on the charging switch of the device under test to allow the device under test to be charged until the charging termination condition is met. In this way, the charging process of the device under test is implemented automatically without manual intervention.

[0040] In a possible implementation, the first device controlling the device under test to be charged includes: when the device under test is connected to a charging pile, the first device sends second reminder information to the second device, where the second reminder information reminds a user to turn on a charging switch of the device under test to allow the device under test to be charged until a charging termination condition is met.

[0041] In the above implementation, when the device under test is connected to the charging pile, the first device may send second reminder information to the second device to remind the user to turn on the charging switch of the device under test. The user may use the second device to turn on the charging switch of the device under test, thereby starting charging of the device under test. This satisfies the user's desire to control the charging-initiating node.

[0042] In a possible implementation, the charge termination condition includes being able to accurately obtain the state of charge of the device under test.

[0043] In a possible implementation, the charge termination condition includes the device under test reaching a fully charged state.

[0044] In the above implementation, the charge state obtained when the device under test reaches a fully charged state is 100%, and the charge state is reliable. In this case, the device under test stops charging. This ensures the reliability of the charge state obtained when the device under test stops charging.

[0045] In a possible implementation, the first device controlling the device under test to be charged further includes:

[0046] When the device under test is not connected to the charging pile, the first device sends third reminder information to the second device, where the third reminder information reminds the user to connect the device under test to the charging pile.

[0047] In the above implementation, when the device under test is not connected to the charging pile, the first device sends third reminder information to the second device to remind the user to connect the device under test to the charging pile, so that when the device under test is connected to the charging pile, the charging switch of the device under test is turned on.

[0048] In a possible implementation, the first device determining a battery evaluation result based on the test data includes:

[0049] the first device determines a maximum available amount of electricity for the device under test based on the charge amount and the difference between the first state of charge and the second state of charge; The first device determines a battery health of the device under test based on a ratio of a maximum available power of the device under test to a rated power of the device under test; Here, the battery evaluation results include the battery health of the device under test.

[0050] In the above implementation, the first device first evaluates the maximum available charge of the device under test based on the charge amount and the difference between the first state of charge obtained when the device under test starts charging and the second state of charge obtained when the device under test stops charging, and then evaluates the battery health of the device under test based on the ratio of the maximum available charge of the device under test to the rated charge of the device under test. This method of evaluating battery health uses "first principles," i.e., evaluates battery health by using physical quantities directly related to battery health and their logical relationships, which are easier to interpret. In this way, the evaluated battery health has high accuracy and the evaluated value is close to the real value.

[0051] According to a second aspect, an embodiment of the present application provides a battery evaluation method, the method including:

[0052] The second device receives the battery evaluation result sent by the first device, wherein the battery evaluation result is determined by the first device based on test data of the device under test in a charge / discharge process corresponding to the battery evaluation task, and the charge / discharge process is executed by the device under test under the control of the first device when the device under test satisfies a trigger condition of the battery evaluation task.

[0053] According to the above implementation, when the device under test meets the trigger condition of the battery evaluation task, the first device executes the device under test to perform a charge / discharge process corresponding to the battery evaluation task, obtains test data for the device under test during the charge / discharge process, and determines a battery evaluation result based on the test data. That is, the first device automatically executes the battery evaluation task to obtain a battery evaluation result for the device under test, then transmits the battery evaluation result to the second device, and the second device receives the battery evaluation result transmitted by the first device. The user can know the battery evaluation result by viewing the information received by the second device. In this way, the user does not need to send the device under test to a specialized testing facility for battery evaluation. This reduces manual intervention and time costs and improves the efficiency of obtaining battery evaluation results.

[0054] In a possible implementation, the method further includes:

[0055] The second device receives request information sent by the first device when the first device has not obtained authorization to perform the battery assessment task; The second device sends authorization information to the first device, where the authorization information is used to authorize the first device to perform the battery assessment task.

[0056] In the above implementation, when the first device has not obtained authorization to perform the battery assessment task, the second device receives request information sent by the first device, where the request information is used to send a request to a user to obtain authorization to perform the battery assessment task. When the user agrees to provide authorization, the second device sends authorization information to the first device, whereby the first device obtains authorization to perform the battery assessment task.

[0057] In a possible implementation, the authorization information includes the number of authorizations and / or the authorization period.

[0058] In the above implementation, the authorization information may include an authorization count, an authorization period, or both an authorization count and an authorization period, so that the user can flexibly set the number of times and / or the period for which the first device is allowed to perform the battery assessment task based on actual requirements.

[0059] In a possible implementation, the trigger condition includes being able to accurately obtain the state of charge of the device under test.

[0060] In a possible implementation, the trigger condition includes the device under test being in a fully charged state.

[0061] In the above implementation, when the device under test is in a fully charged state, the first device is triggered to perform the battery evaluation task, thereby ensuring the stability and reliability of the trigger opportunity, and the first device can start the battery evaluation task at a stable and reliable opportunity.

[0062] In a possible implementation, the trigger condition includes the cumulative mileage of the device under test being greater than a preset mileage and / or the cumulative number of times the device under test has been charged being greater than a preset number.

[0063] In the above implementation, when the cumulative mileage of the device under test is greater than a preset mileage and / or the cumulative number of times the device under test has been charged is greater than a preset number, the battery of the device under test may be degraded to a certain extent. In this case, it may be deemed necessary to evaluate the battery status of the device under test, and the first device is triggered to perform a battery evaluation task. In this way, the first device can reduce unnecessary battery evaluation tasks, thereby saving computing resources.

[0064] In a possible implementation, the method further includes:

[0065] The second device receives first reminder information sent by the first device when the first device controls the device under test to perform discharging, where the first reminder information reminds the user to discharge the device under test until a discharge termination condition is met.

[0066] In the above implementation, the second device receives the first reminder information sent by the first device, and the first reminder information reminds the user to discharge the device under test until the discharge termination condition is met, so that the user can determine whether to discharge the device under test by using the device under test based on actual needs, which helps to effectively utilize the battery level of the device under test.

[0067] In a possible implementation, the discharge termination condition includes the state of charge of the device under test being below a first threshold.

[0068] In the above implementation, when the charge state of the device under test is less than the first threshold, the device under test terminates discharging, which may cause the device under test to enter a low battery state after discharging is terminated. In this case, the charge state of the device under test is used as the charge state obtained when the device under test starts charging. This ensures the reliability of the charge state obtained when the device under test starts charging.

[0069] In a possible implementation, the method further includes:

[0070] In the process of controlling the device under test to perform self-discharge, when the first device detects that an exception has occurred in the parameter data of the device under test, the second device receives alarm information transmitted by the first device.

[0071] In the above implementation, the second device receives alarm information sent by the first device, where the alarm information indicates that an exception has occurred in the parameter data of the device under test during the self-discharge process, so that the user can be informed of the exception in a timely manner and help avoid possible security risks.

[0072] In a possible implementation, the method further includes:

[0073] The first device controls the device under test to be charged, and when the device under test is connected to the charging pile, the second device receives second reminder information sent by the first device, where the second reminder information reminds a user to turn on a charging switch of the device under test to allow the device under test to be charged until a charging termination condition is met; The second device turns on the charging switch of the device under test and allows the device under test to be charged until a charging termination condition is met.

[0074] In the above implementation, the second device receives second reminder information sent by the first device, where the second reminder information reminds the user to turn on the charging switch of the device under test. The user may use the second device to turn on the charging switch of the device under test, so that the device under test starts charging. This satisfies the user's desire to control the charging-initiating node.

[0075] In a possible implementation, the charge termination condition includes being able to accurately obtain the state of charge of the device under test.

[0076] In a possible implementation, the charge termination condition includes the device under test reaching a fully charged state.

[0077] In the above implementation, the device under test terminates charging when it reaches a full charge state, so that the charge state obtained when the device under test terminates charging is 100% and the charge state is reliable. This helps ensure the reliability of the charge state obtained when the device under test terminates charging.

[0078] In a possible implementation, the method further includes:

[0079] When the first device controls the device under test to be charged and the device under test is not connected to the charging pile, the second device receives second reminder information sent by the first device, where the third reminder information reminds the user to connect the device under test to the charging pile.

[0080] In the above implementation, the second device receives third reminder information sent by the first device, where the third reminder information reminds the user to connect the device under test to the charging pile, and thus, when the device under test is connected to the charging pile, the charging switch of the device under test is turned on.

[0081] In a possible implementation, the test data includes a first state of charge, a second state of charge, and a charge amount, where the first state of charge corresponds to a charge state obtained after the device under test has terminated discharging, the second state of charge corresponds to a charge state obtained when the device under test is charged until a charge termination condition is met, and the charge amount corresponds to a charge amount of the device under test from the end of discharging to the end of charging until the charge termination condition is met.

[0082] In the above implementation, the available electrical energy of the battery can be accurately reflected based on the first state of charge, the second state of charge, and the charge amount, and a highly accurate battery evaluation result is determined based on the available electrical energy of the battery.

[0083] In a possible implementation, the battery assessment result includes a battery health of the device under test, the battery health of the device under test being determined based on a ratio of a maximum available amount of electricity of the device under test to a rated amount of electricity of the device under test, and the maximum available amount of electricity of the device under test being determined based on a charge amount and a difference between a first state of charge and a second state of charge.

[0084] In the above implementation, the maximum available charge of the device under test is first evaluated based on the charge amount and the difference between a first charge state obtained when the device under test starts charging and a second charge state obtained when the device under test stops charging. Then, the battery health of the device under test is evaluated based on the ratio of the maximum available charge of the device under test to the rated charge of the device under test. This method of evaluating battery health uses "first principles," i.e., evaluates battery health by using physical quantities directly related to battery health and their logical relationships, which are easier to interpret. In this way, the evaluated battery health has high accuracy and the evaluated value is close to the real value.

[0085] According to a third aspect, an embodiment of the present application provides a battery evaluation apparatus, the apparatus including a module or unit configured to perform the method according to the first aspect or any one of the possible implementations of the first aspect.

[0086] In a possible implementation, the apparatus comprises: a processing unit configured to, when the device under test satisfies a trigger condition of the battery evaluation task, control the device under test to perform a charge / discharge process corresponding to the battery evaluation task, obtain test data of the device under test in the charge / discharge process, and determine a battery evaluation result based on the test data; a transceiver unit configured to transmit the battery assessment result to a second device; Equipped with.

[0087] In a possible implementation, when controlling the device under test to perform a charge / discharge process corresponding to the battery evaluation task, the processing unit is specifically configured to control the device under test to perform a charge / discharge process corresponding to the battery evaluation task when authorization to perform the battery evaluation task has been obtained.

[0088] In a possible implementation, the transmitting and receiving unit comprises: When authorization to perform the battery assessment task is not obtained, sending request information to the second device; receiving the authorization information sent by the second device; wherein the authorization information is used to authorize the first device to perform the battery assessment task.

[0089] In a possible implementation, the authorization information includes the number of authorizations and / or the authorization period.

[0090] In a possible implementation, the trigger condition includes being able to accurately obtain the state of charge of the device under test.

[0091] In a possible implementation, the trigger condition includes the device under test being in a fully charged state.

[0092] In a possible implementation, the trigger condition includes the cumulative mileage of the device under test being greater than a preset mileage and / or the cumulative number of times the device under test has been charged being greater than a preset number.

[0093] In a possible implementation, when controlling the device under test to perform a charge / discharge process corresponding to a battery evaluation task, and obtaining test data for the device under test in the charge / discharge process, the processing unit specifically: Controlling the device under test to discharge, and obtaining a first charge state after the device under test has finished discharging; Obtain the secondary charging status and charge amount of the device under test; wherein the second charge state corresponds to a charge state obtained when the device under test is charged until a charge termination condition is satisfied, and the charge amount corresponds to a charge amount of the device under test from when discharge is terminated until when the device under test is charged until the charge termination condition is satisfied; The test data includes a first state of charge, a second state of charge, and a charge amount.

[0094] In a possible implementation, when controlling the device under test to perform discharging, the processing unit is specifically configured to control the device under test to perform self-discharge until a discharge termination condition is met.

[0095] In a possible implementation, the transceiver unit is further configured to send first reminder information to the second device, where the first reminder information reminds the user to discharge the device under test until a discharge termination condition is met.

[0096] In a possible implementation, the discharge termination condition includes the state of charge of the device under test being below a first threshold.

[0097] In a possible implementation, the processing unit is further configured to monitor parameter data of the device under test in the process of controlling the device under test to perform self-discharge, and to control the device under test to terminate self-discharge when it detects that an exception has occurred in the parameter data.

[0098] The transceiver unit is further configured to send alarm information to the second device when detecting that an exception occurs in the parameter data.

[0099] In a possible implementation, when the device under test acquires the first charge state after finishing discharging, the processing unit specifically: obtaining a first open-circuit voltage of the device under test after the device under test has finished discharging and remained in an idle state for a first period of time; obtaining a first state of charge based on the state of charge corresponding to the first open circuit voltage; It is configured as follows.

[0100] In a possible implementation, when obtaining the second charge state and charge amount of the device under test, the processing unit is specifically configured to control the device under test to finish discharging and remain in an idle state for a first period of time, and then charge the device under test, and obtain the second charge state and charge amount of the device under test.

[0101] In a possible implementation, when controlling the device under test to be charged, the processing unit specifically turns on a charging switch of the device under test when the device under test is connected to a charging pile, and allows the device under test to be charged until a charging termination condition is met.

[0102] In a possible implementation, the transceiver unit is further configured to send second reminder information to the second device when the device under test is connected to the charging pile, where the second reminder information reminds a user to turn on a charging switch of the device under test to allow the device under test to be charged until a charging termination condition is met.

[0103] In a possible implementation, the charge termination condition includes being able to accurately obtain the state of charge of the device under test.

[0104] In a possible implementation, the charge termination condition includes the device under test reaching a fully charged state.

[0105] In a possible implementation, the transceiver unit is further configured to send third reminder information to the second device when the device under test is not connected to the charging pile, where the third reminder information reminds the user to connect the device under test to the charging pile.

[0106] In a possible implementation, when determining a battery evaluation result based on the test data, the processing unit specifically: determining a maximum available amount of electricity for the device under test based on the charge amount and the difference between the first state of charge and the second state of charge; determining the battery health of the device under test based on a ratio of the maximum available electrical charge of the device under test to the rated electrical charge of the device under test; wherein the battery evaluation result includes the battery health of the device under test.

[0107] For technical effects and any possible implementations provided by the third aspect, please refer to the description of the technical effects and corresponding implementations corresponding to the first aspect.

[0108] According to a fourth aspect, an embodiment of the present application provides a battery evaluation apparatus, the apparatus including a module or unit configured to perform the method according to the second aspect or any one of the possible implementations of the second aspect.

[0109] In a possible implementation, the apparatus comprises: The battery evaluation task includes a transmitting / receiving unit configured to receive a battery evaluation result transmitted by a first device, the battery evaluation result being determined by the first device based on test data of the device under test in a charge / discharge process corresponding to the battery evaluation task, and the charge / discharge process being executed by the device under test under the control of the first device when the device under test satisfies a trigger condition of the battery evaluation task.

[0110] In a possible implementation, the transmitting and receiving unit comprises: receiving request information sent by the first device when the first device has not obtained authorization to perform the battery assessment task; Sending the authorization information to the first device; wherein the authorization information is used to authorize the first device to perform the battery assessment task.

[0111] In a possible implementation, the authorization information includes the number of authorizations and / or the authorization period.

[0112] In a possible implementation, the trigger condition includes being able to accurately obtain the state of charge of the device under test.

[0113] In a possible implementation, the trigger condition includes the device under test being in a fully charged state.

[0114] In a possible implementation, the trigger condition includes the cumulative mileage of the device under test being greater than a preset mileage and / or the cumulative number of times the device under test has been charged being greater than a preset number.

[0115] In a possible implementation, the transceiver unit is further configured to receive first reminder information sent by the first device when the first device controls the device under test to perform discharging, wherein the first reminder information reminds the user to discharge the device under test until a discharge termination condition is met.

[0116] In a possible implementation, the discharge termination condition includes the state of charge of the device under test being below a first threshold.

[0117] In a possible implementation, the transceiver unit is further configured to receive alarm information transmitted by the first device when the first device detects that an exception has occurred in the parameter data of the device under test during the process of controlling the device under test to perform self-discharge.

[0118] In a possible implementation, the transceiver unit is further configured to receive second reminder information sent by the first device when the first device controls the device under test to be charged and the device under test is connected to the charging pile, where the second reminder information reminds a user to turn on a charging switch of the device under test to allow the device under test to be charged until a charging termination condition is met. The device further includes a processing unit configured to turn on a charging switch of the device under test to allow the device under test to be charged until a charging termination condition is met.

[0119] In a possible implementation, the charge termination condition includes being able to accurately obtain the state of charge of the device under test.

[0120] In a possible implementation, the charge termination condition includes the device under test reaching a fully charged state.

[0121] In a possible implementation, the transceiver unit is further configured to receive second reminder information sent by the first device when the first device controls the device under test to be charged and the device under test is not connected to the charging pile, wherein the third reminder information reminds the user to connect the device under test to the charging pile.

[0122] In a possible implementation, the test data includes a first state of charge, a second state of charge, and a charge amount, where the first state of charge corresponds to a charge state obtained after the device under test has terminated discharging, the second state of charge corresponds to a charge state obtained when the device under test is charged until a charge termination condition is met, and the charge amount corresponds to a charge amount of the device under test from the end of discharging to the end of charging until the charge termination condition is met.

[0123] In a possible implementation, the battery assessment result includes a battery health of the device under test, the battery health of the device under test being determined based on a ratio of a maximum available amount of electricity of the device under test to a rated amount of electricity of the device under test, and the maximum available amount of electricity of the device under test being determined based on a charge amount and a difference between a first state of charge and a second state of charge.

[0124] For technical effects and any possible implementations provided by the fourth aspect, please refer to the description of the technical effects and corresponding implementations corresponding to the second aspect.

[0125] According to a fifth aspect, an embodiment of the present application provides an electronic device. The electronic device includes a processor. The processor may be coupled to a memory and configured to execute a computer program or instructions in the memory to implement a method according to either the first aspect or the second aspect, or any one of possible implementations of the first aspect or the second aspect. Optionally, the electronic device further includes the memory. Optionally, the electronic device further includes a communication interface, and the processor is coupled to the communication interface.

[0126] According to a sixth aspect, an embodiment of the present application provides a computer-readable storage medium, the computer-readable storage medium storing a computer program or instructions, which, when executed, implements a method according to either the first aspect or the second aspect, or any one of possible implementations of the first aspect or the second aspect.

[0127] According to a seventh aspect, an embodiment of the present application provides a computer program product, the computer program product comprising computer programs or instructions that, when executed, implement a method according to either the first aspect or the second aspect, or any one of possible implementations of the first aspect or the second aspect.

[0128] According to an eighth aspect, an embodiment of the present application provides a chip. The chip includes a processor. The processor is configured to execute a computer program or instructions. When the processor executes the computer program or instructions, the chip is capable of performing a method according to either the first aspect or the second aspect, or any one of possible implementations of the first aspect and the second aspect. Optionally, the chip further includes a communication interface, the communication interface configured to receive a signal or transmit a signal.

[0129] According to a ninth aspect, an embodiment of the present application provides a system, the system including an apparatus according to the third aspect or any one of the possible implementations of the third aspect, and an apparatus according to the fourth aspect or any one of the possible implementations of the fourth aspect.

[0130] According to a tenth aspect, an embodiment of the present application provides a system, the system including a first device and a second device, the first device configured to perform a method according to the first aspect or any one of possible implementations of the first aspect, and the second device configured to perform a method according to the second aspect or any one of possible implementations of the second aspect.

[0131] Additionally, in the process of performing the method according to either the first aspect or the second aspect, or any one of the possible implementations of the first aspect or the second aspect, the processes related to transmitting information and / or receiving information in the method may be understood as a process of outputting information by a processor and / or a process of receiving input information by a processor. When outputting information, the processor may output the information to a transceiver (or a communication interface or a transmission module), which then transmits the information. After the information is output by the processor, other processing may need to be performed on the information before it arrives at the transceiver. Similarly, when the processor receives input information, the transceiver (or a communication interface or a transmission module) receives the information and inputs the information to the processor. Furthermore, after the transceiver receives the information, other processing may need to be performed on the information before it is input to the processor.

[0132] Based on the above principle, for example, in the above method, transmitting information may be understood as outputting information by the processor. In another example, receiving information may be understood as receiving input information by the processor.

[0133] Optionally, operations such as transmitting, sending, and receiving related to a processor may be understood more generally as operations such as output, receiving, and input of a processor, unless otherwise specified or provided that the operations do not contradict the actual functionality or internal logic of the operations in the associated description.

[0134] Optionally, in the process of performing the method according to either the first aspect or the second aspect, or any one of the possible implementations of the first aspect or the second aspect, the processor may be a processor specially configured to perform the method, or may be a processor that performs the method by executing computer instructions in a memory, such as a general-purpose processor. The memory may be a non-transitory memory, such as a read-only memory (ROM). The memory and the processor may be integrated on the same chip or may be separately located on different chips. The type of memory and the manner in which the memory and the processor are located are not limited in the embodiments of the present application. [Brief explanation of the drawings]

[0135] In order to more clearly describe the technical solutions in the embodiments of the present application, the following briefly describes the accompanying drawings used in the embodiments of the present application. The accompanying drawings described below only illustrate some embodiments of the present application, and it is obvious that those skilled in the art can derive other drawings from these accompanying drawings without creative efforts.

[0136] [Figure 1] 1 is a diagram of an application scenario of a battery evaluation method according to an embodiment of the present application;

[0137] [Figure 2] 1 is a schematic flowchart of a battery evaluation method according to an embodiment of the present application.

[0138] [Figure 3] 1 is a diagram of the structure of a battery evaluation device according to an embodiment of the present application;

[0139] [Figure 4] 1 is a diagram of a structure of an electronic device according to an embodiment of the present application;

[0140] [Figure 5]1 is a diagram of a chip structure according to an embodiment of the present invention. DETAILED DESCRIPTION OF THE INVENTION

[0141] To make the objectives, technical solutions and advantages of the present application clearer, the following describes embodiments of the present application with reference to the accompanying drawings in the embodiments of the present application.

[0142] In this application, terms such as "example" or "for example" mean to serve as an example, illustration, or explanation. Any embodiment or design scheme described in this application as an "example" or "for example" should not be described as preferred or having more advantages over another embodiment or design scheme. Rather, terms such as "example" or "for example" are intended to present the relevant concept in a particular way.

[0143] In the embodiments of the present application, "first," "second," "third," etc. are intended to distinguish between different objects, but do not indicate a particular order. In addition, terms such as "comprise" and "have," as well as any other variations thereof, are intended to cover a non-exclusive inclusion. For example, a process, method, system, product, or device that includes a series of steps or units is not limited to the listed steps or units, and optionally further includes unlisted steps or units, or optionally further includes other steps or units inherent to those processes, methods, products, or devices.

[0144] In this specification, the phrase "embodiment" means that a particular feature, structure, or characteristic described in connection with an embodiment may be included in at least one embodiment of the present application. Phrases appearing in various places in this specification do not necessarily refer to the same embodiment, nor do they refer to an embodiment that is independent or exclusive of another embodiment. In the embodiments of the present application, unless otherwise specified or logically contradictory, the terms and / or descriptions in all embodiments are consistent and may be cross-referenced, and those skilled in the art can explicitly and implicitly understand that technical features in different embodiments may be combined into a new embodiment based on their internal logical relationships.

[0145] In this application, "at least one" means one or more, "multiple" means two or more, "at least two" means two, three, or more, and "and / or" is used to describe an association relationship between related objects and indicates that three relationships may exist. For example, "A and / or B" may indicate the following three cases: only A is present, only B is present, or both A and B are present, where A and B may be singular or plural. The character " / " typically indicates an "or" relationship between related objects. "At least one of the following items" or similar expressions refers to any combination of these items, including any combination of a single item or multiple items. For example, "at least one of a, b, or c" may refer to a, b, c, a and b, a and c, b and c, or a, b, and c, where a, b, and c may be singular or plural.

[0146] The methods provided in the present application may be applied to various communication systems, such as internet of things (IoT) systems, narrowband internet of things (NB-IoT) systems, long term evolution (LTE) systems, 5th generation (5G) communication systems, and new communication systems (e.g., 6G) emerging in future communication developments.

[0147] The technical solutions provided in this application may further be applied to machine-type communication (MTC), long term evolution-machine (LTE-M) technology, device-to-device (D2D) networks, machine-to-machine (M2M) networks, internet of things (IoT) networks, or other networks. IoT networks may include, for example, internet of vehicles. Communication modes in internet of things (IoT) networks for vehicular systems are collectively called vehicle-to-everything (V2X, where X may represent everything). For example, V2X may include vehicle-to-vehicle (V2V) communications, vehicle-to-infrastructure (V2I) communications, vehicle-to-pedestrian (V2P) communications, vehicle-to-network (V2N) communications, etc.

[0148] 1 is a diagram of an application scenario of a battery evaluation method according to an embodiment of the present application. The application scenario includes a cloud 101, a vehicle 102, and a user equipment 103. The cloud 101 may communicate with the vehicle 102 to provide multiple services to the vehicle 102. The cloud 101 may also communicate with the user equipment 103, and the vehicle 102 may also communicate with the user equipment 103. The cloud 101 may include a cloud server and / or a cloud virtual machine. The vehicle 102 may be an electric vehicle equipped with a power battery, such as an electric car, a train, or an electric bicycle. The user equipment 103 may be a device capable of providing communication services to a user, such as a mobile phone, a smartphone, a personal digital assistant (PDA) computer, a tablet computer, a handheld device, or a wearable device.

[0149] In a possible implementation, when the vehicle 102 meets the trigger condition of the battery assessment task, the cloud 101 automatically executes the battery assessment task to assess the battery status of the vehicle 102 and obtains the battery assessment result of the vehicle 102. The cloud 101 transmits the battery assessment result of the vehicle 102 to the user equipment 103. Please refer to the following embodiments for specific related descriptions.

[0150] In another possible implementation, the cloud 101 distributes a battery assessment program to the vehicle 102. When the vehicle 102 meets the trigger conditions of the battery assessment task, the vehicle 102 automatically executes the battery assessment task to assess the battery status of the vehicle 102 and obtains the battery assessment result of the vehicle 102. The vehicle 102 transmits the battery assessment result of the vehicle 102 to the user equipment 103. Please refer to the following embodiments for specific related descriptions.

[0151] 2 is a schematic flowchart of a battery evaluation method according to an embodiment of the present application. The battery evaluation method may be applied to the scenario shown in FIG. 1. The battery evaluation method may include, but is not limited to, the following steps S201 to S203.

[0152] S201: When the device under test satisfies the trigger condition of the battery evaluation task, the first device controls the device under test to perform a charge / discharge process corresponding to the battery evaluation task, and obtains test data of the device under test in the charge / discharge process.

[0153] In this embodiment of the present application, the device under test is a device having a power battery, and may be an electric vehicle, such as vehicle 102 in Figure 1, or another driving device having the functionality of vehicle 102. This embodiment of the present application is intended to evaluate the battery condition of the device under test.

[0154] In this embodiment of the present application, the first device is a device having a processor that can be configured to execute computer instructions, and in this embodiment of the present application, is configured to execute the battery evaluation method. As an example, the first device may be a server device, such as the cloud 101 in FIG. 1, or another component such as a server or virtual machine having the functionality of the cloud 101, or a device integrated with the cloud 101. In another example, the first device may be a vehicle-end device, such as the vehicle 102 in FIG. 1, or a control component within the vehicle 102, or another driving device having the functionality of the vehicle 102.

[0155] The trigger condition of the battery assessment task is a condition for triggering the first device to assess the battery status of the device under test. The battery status may include, but is not limited to, a battery state of health (SOH) and / or a battery state of energy (SOE). The charge / discharge process corresponding to the battery assessment task is an operation that needs to be performed by the device under test to support the battery assessment task. The charge / discharge process may include at least one discharge process and at least one charge process. The test data of the device under test in the charge / discharge process may be understood as data related to the battery status and is used to assess the battery status.

[0156] Optionally, the first device may detect whether the device under test satisfies a trigger condition of the battery assessment task in real time or periodically. When detecting that the device under test satisfies the trigger condition of the battery assessment task, the first device executes the battery assessment task to assess the battery status of the device under test.

[0157] S202: The first device determines a battery evaluation result based on the test data.

[0158] The first device may evaluate the battery status of the device under test based on the test data and the relationship between the test data and the battery status, and obtain a battery evaluation result for the device under test, which may include, but is not limited to, a battery health and / or a battery energy state.

[0159] S203: The first device transmits the battery evaluation result to the second device.

[0160] In this embodiment of the present application, the second device is a device capable of providing communication services and configured to exchange information with the first device. In one example, the second device may be user equipment, such as user equipment 103 in FIG. 1, or another device having the functionality of user equipment 103. In another example, the second device may be an in-vehicle device, such as a head unit screen in vehicle 102 shown in FIG. 1.

[0161] The first device transmits the battery evaluation result to the second device, and in response, the second device receives the battery evaluation result transmitted by the first device.

[0162] According to the above embodiment, when the device under test satisfies the trigger condition of the battery evaluation task, the first device controls the device under test to perform a charge / discharge process corresponding to the battery evaluation task, obtains test data for the device under test during the charge / discharge process, and determines a battery evaluation result based on the test data. That is, the first device automatically performs the battery evaluation task to obtain a battery evaluation result for the device under test, and then transmits the battery evaluation result to the second device. A user can know the battery evaluation result by viewing the information received by the second device. In this way, the user does not need to send the device under test to a specialized testing facility for battery evaluation. This reduces manual intervention and time costs and improves the efficiency of obtaining battery evaluation results.

[0163] It should be noted that in this embodiment of the present application, the device under test is available during the process of performing battery evaluation, so that the user's temporary use request of the device under test during battery evaluation can be met. For example, when the device under test is performing a charging / discharging process corresponding to a battery evaluation task, if the user wants to use the device under test, the user can actively interrupt the charging / discharging process of the device under test and then use the device under test.

[0164] In a possible embodiment, the first device controlling the device under test to perform a charge / discharge process corresponding to the battery evaluation task may specifically be the first device controlling the device under test to perform a charge / discharge process corresponding to the battery evaluation task when obtaining approval to perform the battery evaluation task.

[0165] In addition to the device under test satisfying the trigger condition of the battery assessment task, the first device must also obtain authorization to perform the battery assessment task, in which case the first device performs the battery assessment task.

[0166] Optionally, after detecting that the device under test satisfies a trigger condition of the battery assessment task, the first device further detects whether the first device has obtained authorization to perform the battery assessment task. When the first device has obtained authorization to perform the battery assessment task, the first device performs the battery assessment task to assess a battery status of the device under test.

[0167] In this embodiment of the present application, the first device executing the battery assessment task when obtaining authorization to execute the battery assessment task may be understood as executing the battery assessment task when the user agrees to provide the authorization, thereby avoiding the first device executing the battery assessment task when the user does not agree to provide the authorization, thereby affecting the use of the device under test.

[0168] In a possible embodiment, when the first device does not obtain authorization to perform the battery evaluation task, the first device sends request information to the second device, and the first device receives authorization information sent by the second device, where the authorization information is used to allow the first device to perform the battery evaluation task.

[0169] When the first device does not obtain authorization to perform the battery assessment task, the first device transmits request information to the second device. The request information is used to transmit a request to a user to obtain authorization to perform the battery assessment task. In response, the second device receives the request information transmitted by the first device and returns information in response to the request information to the first device.

[0170] Optionally, if the user agrees to provide authorization, the second device may send authorization information to the first device. The authorization information is used to allow the first device to perform the battery assessment task. In response, the first device receives the authorization information sent by the second device. When the first device receives the authorization information sent by the second device, this indicates that the first device has obtained authorization to perform the battery assessment task.

[0171] Optionally, if the user does not agree to perform the authorization, the second device may send authorization denial information to the first device. The authorization denial information is used to deny permission for the first device to perform the battery assessment task. In response, the first device may reject the authorization sent by the second device. rejection When the first device receives the authorization denial information sent by the second device, this indicates that the first device has not obtained authorization to perform the battery assessment task.

[0172] According to this embodiment of the present application, when the first device has not obtained authorization to perform the battery assessment task, the first device sends request information to the second device and sends a request to the user to obtain authorization to perform the battery assessment task. When the user agrees to provide authorization, the second device may send authorization information to the first device, and the first device receives the authorization information sent by the second device to obtain authorization to perform the battery assessment task.

[0173] In a possible embodiment, the approval information includes approval count and / or approval duration.

[0174] In one example, the authorization information may include an authorization count, where the authorization count is the number of times the first device is permitted to execute the battery assessment task. The authorization count may be a default number or a number customized by a user. This is not limited to the embodiment of the present application. If the number of times the first device executes the battery assessment task has not reached the authorization count, when the battery assessment task is triggered, the first device does not need to send request information to the second device and can directly execute the battery assessment task. If the number of times the first device executes the battery assessment task has not reached the authorization count, when the battery assessment task is triggered, the first device needs to resend request information to the second device and can execute the battery assessment task only after re-obtaining authentication.

[0175] For example, the number of approvals may be one. In this case, the first device is permitted to execute the battery assessment task only once (i.e., this time). When the battery assessment task is triggered next time, the first device needs to send request information to the second device again, and can execute the battery assessment task only after obtaining approval again. As another example, the number of approvals may be more than one, for example, two. In this case, the first device is permitted to execute the battery assessment task twice (i.e., including this time and the next time). When the battery assessment task is triggered next time, the first device does not need to send request information to the second device again. In this case, the first device is permitted to directly execute the battery assessment task.

[0176] In another example, the authorization information may include an authorization period, which is a period during which the first device is permitted to perform the battery assessment task. The authorization period may be a period set by default or may be a period customized by a user. This is not limited to the embodiments of the present application. If the current period does not exceed the authorization period, when the battery assessment task is triggered, the first device does not need to send request information to the second device and can directly perform the battery assessment task. If the current period exceeds the authorization period, when the battery assessment task is triggered, the first device needs to resend request information to the second device and can only perform the battery assessment task after re-obtaining authentication.

[0177] For example, the authorization period may be one month. In this case, the first device is permitted to execute the battery assessment task within one month. If the battery assessment task is triggered within one month, the first device does not need to send request information to the second device. In this case, the first device is permitted to execute the battery assessment task directly. If the battery assessment task is triggered after one month has passed, the first device needs to resend request information to the second device, and can execute the battery assessment task only after re-obtaining authentication.

[0178] In yet another example, the authorization information may include both the authorization count and the authorization period. Optionally, if the number of times the first device executes the battery assessment task has not reached the authorization count and the current period has not exceeded the authorization period, when the battery assessment task is triggered, the first device does not need to send the request information to the second device and can directly execute the battery assessment task. If the number of times the first device executes the battery assessment task has not reached the authorization count or the current period has not exceeded the authorization period, when the battery assessment task is triggered, the first device needs to resend the request information to the second device and can execute the battery assessment task only after re-obtaining authentication.

[0179] In this embodiment of the present application, the authorization information may include an authorization number, or may include an authorization period, or may include both an authorization number and an authorization period, so that the user can flexibly set the number and / or period for allowing the first device to perform the battery assessment task based on actual requirements.

[0180] In a possible embodiment, the trigger condition includes being able to accurately obtain the state of charge of the device under test.

[0181] The state of charge (SOC) of the device under test may be understood as the ratio of the remaining power to the rated capacity of the battery of the device under test, and may be expressed as a percentage. The value range of the SOC is 0 to 100%. When the SOC is 0, this indicates that the battery is fully discharged. When the SOC is 100%, this indicates that the battery is fully charged.

[0182] In one example, the first device receives the charging state reported by the device under test to obtain the charging state of the device under test. The closer the charging state is to the endpoint value (0% or 100%), the higher the reliability of the charging state reported by the device under test, i.e., the closer the reported charging state is to the actual charging state, so the first device can obtain the charging state of the device under test more accurately. It may be understood that the charging state reported by the device under test is 100%, which is easy to implement in practical applications. For example, when the device under test is fully charged, the charging state reported by the device under test is 100%.

[0183] In a possible embodiment, the trigger condition includes the device under test being in a fully charged state.

[0184] The first device may detect the charging behavior of the device under test, and when it detects that the device under test has been fully charged, determine that the device under test satisfies the trigger condition of the battery evaluation task. When the charge state of the device under test in the fully charged state is 100%, the charge state is reliable.

[0185] According to this embodiment of the present application, when the device under test is in a fully charged state, the first device is triggered to perform the battery evaluation task, so that the stability and reliability of the trigger can be ensured, and the first device can start performing the battery evaluation task at a stable and reliable opportunity.

[0186] In possible embodiments, the trigger conditions include the cumulative mileage of the device under test being greater than a preset mileage and / or the cumulative number of times the device under test has been charged being greater than a preset number.

[0187] In one example, the trigger condition may include a cumulative mileage of the device under test being greater than a preset mileage. The cumulative mileage of the device under test may be used to estimate a battery decay status of the device under test. A greater cumulative mileage indicates a higher probability of battery decay. If the cumulative mileage is greater than the preset mileage, the device under test may be considered to have been used for a long period of time, and as a result, the battery may have decayed to some extent. When the device under test is in a fully charged state and the cumulative mileage of the device under test is greater than the preset mileage, the device under test is determined to satisfy the trigger condition of the battery evaluation task.

[0188] In another example, the trigger condition may include the device under test having accumulated charge counts greater than a preset number of charge counts. The accumulated charge counts of the device under test can estimate the battery decay status of the device under test. A larger accumulated charge count indicates a higher probability of battery decay. If the accumulated charge counts of the device under test are greater than a preset number, it may be assumed that the device under test has been used for a long period of time, and as a result, the battery may have decayed to some extent. When the device under test is fully charged and the accumulated charge counts of the device under test are greater than a preset number, the device under test is determined to satisfy the trigger condition of the battery assessment task.

[0189] In yet another example, the trigger condition may include that the cumulative mileage of the device under test is greater than a predetermined mileage and that the cumulative number of times the device under test has been charged is greater than a predetermined number. When the device under test is in a fully charged state, the cumulative mileage of the device under test is greater than the predetermined mileage, and the cumulative number of times the device under test has been charged is greater than the predetermined number, the device under test is determined to satisfy the trigger condition of the battery evaluation task.

[0190] It should be understood that the specific values ​​of the preset running distance and number of times may be set based on actual requirements, which are not limited in the embodiments of the present application.

[0191] According to this embodiment of the present application, when the cumulative mileage of the device under test is greater than a preset mileage and / or the cumulative number of times the device under test has been charged is greater than a preset number, the battery of the device under test may be decayed to a certain extent. In this case, it may be deemed necessary to evaluate the battery status of the device under test, and then the first device is triggered to perform a battery evaluation task. In this way, the first device can reduce unnecessary battery evaluation tasks, thereby saving computing resources.

[0192] In a possible embodiment, the first device controls the device under test to perform a charge / discharge process corresponding to the battery evaluation task, and acquiring test data for the device under test during the charge / discharge process may specifically include: the first device controls the device under test to discharge, and acquiring a first charge state after the device under test completes discharging; and the first device acquiring a second charge state and charge amount of the device under test, where the second charge state corresponds to a second charge state acquired when the device under test is charged until a charge termination condition is met, and the charge amount corresponds to a charge amount of the device under test that is charged after completing discharging and until the charge termination condition is met. The test data includes the first charge state, the second charge state, and the charge amount.

[0193] The first device controls the device under test to perform a charge / discharge process corresponding to the battery evaluation task. The charge / discharge process includes a discharge process and a charge process. The first device controls the device under test to perform a discharge and then a charge, so that the device under test first performs a discharge and then is charged after the discharge is completed.

[0194] The first charge state corresponds to the charge state obtained after the device under test has finished discharging, i.e., the charge state obtained when the device under test starts charging. The second charge state corresponds to the charge state obtained when the device under test is charged until the charge termination condition is met, i.e., the charge state obtained when the device under test finishes charging. The charge amount corresponds to the charge amount of the device under test from the end of discharging to the time when the device under test is charged until the charge termination condition is met, i.e., the charge amount of the device under test during the charging process. The charge amount may be obtained by using current data in the charging process according to the ampere-hour integration method.

[0195] According to this embodiment of the present application, the available electrical quantity of the battery can be accurately reflected based on the first state of charge, the second state of charge and the charge amount, and a highly accurate battery evaluation result is determined based on the available electrical quantity of the battery.

[0196] In a possible embodiment, the first device controlling the device under test to perform discharging may specifically include the first device controlling the device under test to perform self-discharge until a discharge termination condition is met, and / or the first device sending first reminder information to the second device, wherein the first reminder information reminds the user to discharge the device under test until a discharge termination condition is met.

[0197] The discharge termination condition may be understood as a condition for triggering the device under test to terminate the discharge process. When the device under test discharges until the discharge termination condition is met, the first device controls the device under test to terminate the discharge process.

[0198] In one example, the first device may control the device under test to self-discharge until a discharge termination condition is met, i.e., the device under test autonomously discharges without manual intervention until the discharge termination condition is met. Using an electric vehicle as an example, for example, the electric vehicle may automatically turn on its onboard air conditioner to perform autonomous discharge.

[0199] In another example, the first device may alternatively send first reminder information to the second device, where the first reminder information reminds the user to discharge the device under test until the discharge termination condition is met. In response, the second device receives the first reminder information sent by the first device. The user may discharge the device under test by using it. After the user finishes using the device under test, the first device detects whether the device under test discharges until the discharge termination condition is met. If it is detected that the discharge termination condition is not met, this indicates that the amount of discharge of the device under test is insufficient. In this case, the first device may control the device under test to self-discharge, and the device under test continues to discharge until the discharge termination condition is met.

[0200] According to this embodiment of the present application, the first device may control the device under test to self-discharge until the discharge termination condition is met. In this way, the discharge process of the device under test is implemented automatically without manual intervention. Alternatively, the first device may send first reminder information to the second device, reminding the user to discharge the device under test until the discharge termination condition is met. In this way, the user can determine whether to discharge the device under test by using the device under test based on actual needs. This helps to effectively utilize the battery level of the device under test.

[0201] In a possible embodiment, the discharge termination condition comprises the state of charge of the device under test being below a first threshold.

[0202] The first threshold indicates a low state of charge. For example, the first threshold may be set to 20%. A state of charge of the device under test below the first threshold may be understood as the device under test discharging to a low state of charge, in which case the state of charge is reliable.

[0203] In the discharge process of the device under test, the first device may detect the charge state of the device under test, and when the charge state of the device under test is detected to be less than a first threshold, the first device determines that the device under test has discharged until a discharge termination condition is met, and enables the device under test to terminate the discharge.

[0204] According to this embodiment of the present application, when the charge state of the device under test is less than the first threshold, the device under test terminates discharging, which may result in the device under test entering a low battery state after the discharge is terminated. In this case, the charge state of the device under test is used as the charge state obtained when the device under test starts charging. This helps to ensure the reliability of the charge state obtained when the device under test starts charging.

[0205] In a possible embodiment, the first device monitors parameter data of the device under test during the process of controlling the device under test to perform self-discharge, and upon detecting that an exception occurs in the parameter data, the first device sends warning information to the second device and controls the device under test to terminate self-discharge.

[0206] During the self-discharge process of the device under test, the first device may monitor parameter data of the device under test in real time. When the monitored parameter data exceeds a corresponding normal data range, it may be considered that an exception has occurred in the parameter data. Optionally, the parameter data includes current data and / or temperature data of the battery.

[0207] When detecting that an exception occurs in the parameter data, the first device sends warning information to the second device, where the warning information notifies a user of the exception. In response, the second device receives the warning information sent by the first device. When detecting that an exception occurs in the parameter data, the first device can further control the device under test to terminate self-discharge to avoid possible security risks.

[0208] According to this embodiment of the present application, in the process of controlling the device under test to perform self-discharge, when detecting that an exception occurs in the parameter data of the device under test, the first device sends alarm information to the second device, so that the user can be notified of the exception in a timely manner. In addition, the first device controls the device under test to end self-discharge, which helps to avoid security risks in a timely manner.

[0209] In a possible embodiment, obtaining the first charge state after the device under test has finished discharging may specifically include the first device obtaining a first open-circuit voltage of the device under test after the device under test has finished discharging and remained in an idle state for a first period of time, and the first device obtaining the first charge state based on the charge state corresponding to the first open-circuit voltage.

[0210] There is a correspondence relationship between the state of charge (SOC) and the open-circuit voltage (OCV) of a battery. The state of charge corresponding to the open-circuit voltage of the device under test at a certain moment, i.e., the state of charge of the device under test at that moment, can be obtained based on the open-circuit voltage and the correspondence relationship. Optionally, the correspondence relationship may be a relationship curve (SOC-OCV curve) between the state of charge and the open-circuit voltage obtained in advance through data fitting.

[0211] During a period after the device under test finishes discharging, the open-circuit voltage of the device under test is unstable, and an accurate open-circuit voltage can be obtained after the device under test remains in an idle state for a certain period. In this case, after the device under test finishes discharging and remains in an idle state for a first period, the first device acquires the open-circuit voltage of the device under test, where the open-circuit voltage is indicated as a first open-circuit voltage. The first period indicates a predetermined idle period, and the first open-circuit voltage may be considered as an actual open-circuit voltage corresponding to the current state of charge. Then, a state of charge corresponding to the first open-circuit voltage is obtained as a first state of charge based on the first open-circuit voltage and the correspondence relationship.

[0212] According to this embodiment of the present application, the first open-circuit voltage is first obtained after the device under test finishes discharging and remains in an idle state for a certain period of time, and then the first state of charge is obtained based on the state of charge corresponding to the first open-circuit voltage, so that the obtained first state of charge is highly accurate.

[0213] In a possible embodiment, the first device acquiring the second charge state and charge amount of the device under test may specifically be, after the device under test finishes discharging and remains in an idle state for a first period, the first device controls the device under test to be charged and acquires the second charge state and charge amount of the device under test.

[0214] After the device under test has finished discharging and remained in an idle state for a first period of time, the first device controls the device under test to be charged until a charge termination condition is met. The charge termination condition may be understood as a condition for triggering the device under test to terminate the charging process. When the device under test has been charged until the charge termination condition is met, the first device controls the device under test to terminate the charging process.

[0215] The first device acquires a charge state after the device under test finishes discharging and remains in an idle state for a first period of time, and uses the charge state as the charge state that will be obtained when the device under test starts charging. The first device acquires a charge state when the device under test is charged until a charge termination condition is met, and uses the charge state as the charge state that will be obtained when the device under test terminates charging. The first device acquires current data of the device under test in the charging process, and performs an ampere-hour integration method by using the current data to obtain a charge amount, where the charge amount is used as the charge amount of the device under test in the charging process.

[0216] According to this embodiment of the present application, after the device under test finishes discharging and remains in an idle state for a first period, the first device controls the device under test to start charging. Since the charge state after the device under test finishes discharging and remains in an idle state for the first period can be accurately obtained based on the open-circuit voltage, this charge state is used as the charge state obtained when the device under test starts charging. This can improve the reliability of the charge state obtained when the device under test starts charging.

[0217] In a possible embodiment, the first device controlling the device under test to be charged may specifically be that when the device under test is connected to a charging pile, the first device turns on a charging switch of the device under test to allow the device under test to be charged until a charging termination condition is met.

[0218] When the device under test is connected to the charging pile, this indicates that the device under test is ready to be charged, in which case the first device can turn on the charging switch of the device under test, thereby charging the device under test.

[0219] According to this embodiment of the present application, when the device under test is connected to the charging pile, the first device can turn on the charging switch of the device under test, allowing the device under test to be charged until a charging termination condition is met. In this way, the charging process of the device under test is implemented automatically without manual intervention.

[0220] In a possible embodiment, the first device controlling the device under test to be charged may specifically be the first device sending second reminder information to the second device when the device under test is connected to a charging pile, wherein the second reminder information reminds the user to turn on the charging switch of the device under test to allow the device under test to be charged until a charging termination condition is met.

[0221] When the device under test is connected to the charging pile, the first device may alternatively send second reminder information to the second device, where the second reminder information reminds the user to turn on the charging switch of the device under test. The user may turn on the charging switch of the device under test by using the second device, so that the device under test can start charging. In response, the second device receives the second reminder information sent by the first device, and turns on the charging switch of the device under test to allow the device under test to be charged until the charging termination condition is met.

[0222] According to this embodiment of the present application, when the device under test is connected to the charging pile, the first device can send second reminder information to the second device to remind the user to turn on the charging switch of the device under test, thereby satisfying the user's need to control the moment when charging starts.

[0223] In a possible embodiment, the charge termination condition includes being able to accurately obtain the state of charge of the device under test.

[0224] The first device may receive the charging state reported by the device under test to obtain the charging state of the device under test, where the closer the charging state is to 100%, the more reliable the charging state reported by the device under test is, i.e., the closer the reported charging state is to the actual charging state, so that the first device can obtain the charging state of the device under test more accurately.

[0225] In a possible embodiment, the charge termination condition includes the state of charge of the device under test being greater than a second threshold.

[0226] The second threshold indicates a high state of charge. For example, the second threshold may be set to 90%. When the state of charge of the device under test is greater than the second threshold, it may be understood that the device under test has been charged to a high state of charge. In this case, the state of charge is reliable.

[0227] During the charging process of the device under test, the first device may detect the charging state of the device under test, and when detecting that the charging state of the device under test is greater than the second threshold, No. 1 The device determines that the device under test has been charged until a charge termination condition is met, and allows the device under test to terminate charging.

[0228] The state of charge when the device under test terminates charging may be obtained based on the open-circuit voltage. Specifically, after the device under test terminates charging and remains in an idle state for a second period, the first device obtains a second open-circuit voltage of the device under test, and obtains the state of charge that will be obtained when the device under test terminates charging based on the state of charge corresponding to the second open-circuit voltage.

[0229] In a possible embodiment, the charge termination condition includes the device under test reaching a fully charged state.

[0230] When the charge state of the device under test reaches a full charge state, the charge state is reliable when the charge state is 100%. During the charging process of the device under test, the first device can detect whether the device under test has reached a full charge state. When the first device detects that the device under test has reached a full charge state, it determines that the device under test has been charged until a charge termination condition is met and allows the device under test to terminate charging.

[0231] According to this embodiment of the present application, the device under test will terminate charging when it reaches a fully charged state, so the charge state obtained when the device under test terminates charging is 100%, and the charge state is reliable, which helps to ensure the reliability of the charge state obtained when the device under test terminates charging.

[0232] In a possible embodiment, the first device controlling the device under test to be charged further includes the first device sending third reminder information to the second device when the device under test is not connected to the charging pile, wherein the third reminder information reminds a user to connect the device under test to the charging pile.

[0233] If the device under test is not connected to the charging pile, this indicates that the device under test is not ready for charging. In this case, the device under test needs to be connected to the charging pile, and then the charging switch of the device under test will be turned on, so that the device under test can be charged.

[0234] When the device under test is not connected to the charging pile, the first device sends third reminder information to the second device, where the third reminder information reminds the user to connect the device under test to the charging pile, and in response, the second device receives the third reminder information sent by the first device.

[0235] According to this embodiment of the present application, when the device under test is not connected to the charging pile, the first device sends third reminder information to the second device to remind the user to connect the device under test to the charging pile, so that when the device under test is connected to the charging pile, the charging switch of the device under test is turned on.

[0236] In a possible embodiment, the first device determining a battery evaluation result based on the test data may specifically include the first device determining a maximum available electrical capacity of the device under test based on the charge amount and the difference between the first charging state and the second charging state, and the first device determining a battery health of the device under test based on a ratio of the maximum available electrical capacity of the device under test to the rated electrical capacity of the device under test, wherein the battery evaluation result includes the battery status of the device under test.

[0237] The maximum available electrical power of the device under test can be calculated as follows: Q max =Q c / (SOC2-SOC1), where Q max , SOC1, SOC2 and Q c where Q denotes the maximum available charge, the first state of charge, the second state of charge, and the charge amount of the device under test, respectively. The battery health of the device under test can be calculated as follows: SOH=Q max / Q0, where SOH and Q0 indicate the battery state of health and the rated electrical quantity of the device under test, respectively.

[0238] According to this embodiment of the present application, the first device evaluates the maximum available charge of the device under test based on the charge amount and the difference between the first state of charge obtained when the device under test starts charging and the second state of charge obtained when the device under test stops charging, and then evaluates the battery health of the device under test based on the ratio of the maximum available charge of the device under test to the rated charge of the device under test. This method of evaluating battery health uses "first principles," i.e., evaluates battery health by using physical quantities directly related to battery health and their logical relationships, which are easier to interpret. In this way, the evaluated battery health has high accuracy, and the evaluated value is close to the real value.

[0239] The above describes the methods in the embodiments of the present application in detail. The following provides an apparatus for implementing any of the methods in the embodiments of the present application.

[0240] FIG. 3 is a diagram of the structure of a battery evaluation device according to an embodiment of the present application.

[0241] 3, the battery evaluation device 300 may include a processing unit 301 and a transceiver unit 302. The processing unit 301 and the transceiver unit 302 may be software, hardware, or a combination of software and hardware.

[0242] The transceiver unit 302 may implement a transmitting function and / or a receiving function, and the transceiver unit 302 may also be described as a communication unit. Alternatively, the transceiver unit 302 may be a unit integrating an acquiring unit and a transmitting unit. The acquiring unit is configured to implement the receiving function, and the transmitting unit is configured to implement the transmitting function. Optionally, the transceiver unit 302 may be configured to receive information transmitted by another device, and may be further configured to transmit information to another device.

[0243] In a possible design, the battery evaluation apparatus 300 may correspond to the first device in the embodiment of the method shown in FIG. 2. For example, the battery evaluation apparatus 300 may be the first device or a chip within the first device. The battery evaluation apparatus 300 may include units for performing the operations performed by the first device in the embodiment of the method shown in FIG. 2. In addition, the units within the battery evaluation apparatus 300 are separately configured to implement the operations performed by the first device in the embodiment of the method shown in FIG. 2. The units are described below.

[0244] The processing unit 301 is configured to, when the device under test satisfies a trigger condition of the battery evaluation task, control the device under test to perform a charge / discharge process corresponding to the battery evaluation task, obtain test data of the device under test in the charge / discharge process, and determine a battery evaluation result based on the test data.

[0245] The transceiver unit 302 is configured to transmit the battery assessment result to the second device.

[0246] In a possible implementation, when controlling the device under test to perform a charge / discharge process corresponding to the battery evaluation task, the processing unit 301 is specifically configured to control the device under test to perform a charge / discharge process corresponding to the battery evaluation task when obtaining approval to perform the battery evaluation task.

[0247] In a possible implementation, the transceiver unit 302 is further configured to: send request information to the second device when authorization to perform the battery evaluation task has not been obtained, and receive authorization information sent by the second device, where the authorization information is used to allow the first device to perform the battery evaluation task.

[0248] In a possible implementation, the authorization information includes the number of authorizations and / or the authorization period.

[0249] In a possible implementation, the trigger condition includes being able to accurately obtain the state of charge of the device under test.

[0250] In a possible implementation, the trigger condition includes the device under test being in a fully charged state.

[0251] In a possible implementation, the trigger condition includes the cumulative mileage of the device under test being greater than a preset mileage and / or the cumulative number of times the device under test has been charged being greater than a preset number.

[0252] In a possible implementation, when controlling the device under test to perform a charge / discharge process corresponding to a battery evaluation task and acquiring test data for the device under test in the charge / discharge process, the processing unit 301 is specifically configured to control the device under test to perform discharging, acquire a first charge state after the device under test finishes discharging, and acquire a second charge state and charge amount of the device under test, where the second charge state corresponds to the charge state obtained when the device under test is charged until a discharge termination condition is met, and the charge amount corresponds to the charge amount of the device under test from finishing discharging to charging until the charge termination condition is met. The test data includes the first charge state, the second charge state, and the charge amount.

[0253] In a possible implementation, when controlling the device under test to perform discharging, the processing unit 301 is specifically configured to control the device under test to perform self-discharge until a discharge termination condition is met.

[0254] In a possible implementation, the transceiver unit 302 is further configured to send first reminder information to the second device, where the first reminder information reminds the user to discharge the device under test until a discharge termination condition is met.

[0255] In a possible implementation, the discharge termination condition includes the state of charge of the device under test being below a first threshold.

[0256] In a possible implementation, the processing unit 301 is further configured to monitor parameter data of the device under test in the process of controlling the device under test to perform self-discharge, and control the device under test to terminate self-discharge when detecting that an exception occurs in the parameter data. The transceiver unit 302 is further configured to send alarm information to the second device when detecting that an exception occurs in the parameter data.

[0257] In a possible implementation, when the device under test acquires a first charge state after the device under test finishes discharging, the processing unit 301 is specifically configured to acquire a first open-circuit voltage of the device under test after the device under test finishes discharging and remains in an idle state for a first period of time, and acquire the first charge state based on the charge state corresponding to the first open-circuit voltage.

[0258] In a possible implementation, when obtaining the second charge state and charge amount of the device under test, the processing unit 301 is specifically configured to control the device under test to be charged after the device under test finishes discharging and is in an idle state for a first period of time, and obtain the second charge state and charge amount of the device under test.

[0259] In a possible implementation, when controlling the device under test to be charged, the processing unit 301 is specifically configured to turn on a charging switch of the device under test when the device under test is connected to a charging pile, and allow the device under test to be charged until a charging termination condition is met.

[0260] In a possible implementation, the transceiver unit 302 is further configured to send second reminder information to the second device when the device under test is connected to the charging pile, where the second reminder information reminds the user to turn on the charging switch of the device under test to allow the device under test to be charged until a charging termination condition is met.

[0261] In a possible implementation, the charge termination condition includes being able to accurately obtain the state of charge of the device under test.

[0262] In a possible implementation, the charge termination condition includes the device under test reaching a fully charged state.

[0263] In a possible implementation, the transceiver unit 302 is further configured to send third reminder information to the second device when the device under test is not connected to the charging pile, where the third reminder information reminds the user to connect the device under test to the charging pile.

[0264] In a possible implementation, when determining a battery evaluation result based on the test data, the processing unit 301 is specifically configured to determine a maximum available electrical capacity of the device under test based on the charge amount and the difference between the first charging state and the second charging state, and determine a battery health of the device under test based on a ratio of the maximum available electrical capacity of the device under test to a rated electrical capacity of the device under test, wherein the battery evaluation result includes the battery health of the device under test.

[0265] In another possible design, the battery evaluation apparatus 300 may correspond to the second device in the embodiment of the method shown in FIG. 2. For example, the battery evaluation apparatus 300 may be the second device or a chip in the second device. The battery evaluation apparatus 300 may include units for performing the operations performed by the second device in the embodiment of the method shown in FIG. 2. In addition, the units in the battery evaluation apparatus 300 are separately configured to implement the operations performed by the second device in the embodiment of the method shown in FIG. 2. The units are described as follows:

[0266] The transceiver unit 302 is configured to receive a battery evaluation result sent by the first device, where the battery evaluation result is determined by the first device based on test data of the device under test in a charging / discharging process corresponding to a battery evaluation task, and the charging / discharging process is performed by the device under test under the control of the first device when the device under test satisfies a trigger condition of the battery evaluation task.

[0267] In a possible implementation, the transceiver unit 302 is further configured to receive request information sent by the first device when the first device has not obtained authorization to perform the battery evaluation task, and send authorization information to the first device, where the authorization information is used to allow the first device to perform the battery evaluation task.

[0268] In a possible implementation, the authorization information includes the number of authorizations and / or the authorization period.

[0269] In a possible implementation, the trigger condition includes being able to accurately obtain the state of charge of the device under test.

[0270] In a possible implementation, the trigger condition includes the device under test being in a fully charged state.

[0271] In a possible implementation, the trigger condition includes the cumulative mileage of the device under test being greater than a preset mileage and / or the cumulative number of times the device under test has been charged being greater than a preset number.

[0272] In a possible implementation, the transceiver unit is further configured to receive first reminder information sent by the first device when the first device controls the device under test to perform discharging, wherein the first reminder information reminds the user to discharge the device under test until a discharge termination condition is met.

[0273] In a possible implementation, the discharge termination condition includes the state of charge of the device under test being below a first threshold.

[0274] In a possible implementation, the transceiver unit 302 is further configured to receive alarm information sent by the first device when the first device detects that an exception has occurred in the parameter data of the device under test during the process of controlling the device under test to perform self-discharge.

[0275] In a possible implementation, the transceiver unit 302 is further configured to receive second reminder information sent by the first device when the first device controls the device under test to be charged and the device under test is connected to a charging pile, where the second reminder information reminds a user to turn on a charging switch of the device under test to allow the device under test to be charged until a charging termination condition is met. The processing unit 301 is configured to turn on the charging switch of the device under test to allow the device under test to be charged until a charging termination condition is met.

[0276] In a possible implementation, the charge termination condition includes being able to accurately obtain the state of charge of the device under test.

[0277] In a possible implementation, the charge termination condition includes the device under test reaching a fully charged state.

[0278] In a possible implementation, the transceiver unit 302 is further configured to receive second reminder information sent by the first device when the first device controls the device under test to be charged and the device under test is not connected to the charging pile, where the third reminder information reminds the user to connect the device under test to the charging pile.

[0279] In a possible implementation, the test data includes a first state of charge, a second state of charge, and a charge amount, where the first state of charge corresponds to a charge state obtained after the device under test has terminated discharging, the second state of charge corresponds to a charge state obtained when the device under test is charged until a charge termination condition is met, and the charge amount corresponds to a charge amount of the device under test from the end of discharging to the end of charging until the charge termination condition is met.

[0280] In a possible implementation, the battery assessment result includes a battery health of the device under test, the battery health of the device under test being determined based on a ratio of a maximum available amount of electricity of the device under test to a rated amount of electricity of the device under test, and the maximum available amount of electricity of the device under test being determined based on a charge amount and a difference between a first state of charge and a second state of charge.

[0281] According to this embodiment of the present application, the units in the device shown in FIG. 3 may be individually or entirely combined with one or more other units, or one or more units in the device may be further divided into multiple units with more detailed functions. This can implement the same operation without affecting the implementation of the technical effect of this embodiment of the present application. The above units are obtained through division based on logical functions. During actual application, the function of one unit may be implemented by multiple units, or the function of multiple units may be implemented by one unit. In other embodiments of the present application, the electronic device may further include other units. During actual application, the function may alternatively be implemented with the assistance of other units, or may be implemented by multiple units working together.

[0282] It should be appreciated that for the implementation of the unit, please refer to the corresponding description of the method embodiment shown in FIG.

[0283] For the implementation and advantageous effects of the unit in the battery evaluation device, please refer to the corresponding descriptions in the aforementioned method embodiments, and the details will not be described again here.

[0284] 4 is a diagram of a structure of an electronic device 400 according to an embodiment of the present application. The electronic device 400 may include a memory 401 and a processor 402. Furthermore, optionally, the electronic device 400 may further include a communication interface 403 and a bus 404. The memory 401, the processor 402, and the communication interface 403 implement an intercommunication connection via the bus 404. The communication interface 403 is configured to exchange data with another device.

[0285] The memory 401 is configured to provide storage space that may store data such as an operating system and computer programs, including, but not limited to, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), or compact disc read-only memory (CD-ROM).

[0286] Processor 402 is a module that performs arithmetic and logical operations and may be one or a combination of processing modules such as a central processing unit (CPU), a graphics processing unit (GPU), or a microprocessor unit (MPU). Processor 402 may alternatively be another general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component, etc. A general-purpose processor may be a microprocessor, or the processor may be any conventional processor, etc.

[0287] In a possible design, the electronic device 400 may correspond to the first device in the embodiment of the method shown in FIG. 2. For example, the electronic device 400 may be the first device or a chip within the first device. The electronic device 400 may include components configured to perform the operations performed by the first device in the embodiment of the method. In addition, the components within the electronic device 400 are separately configured to implement the operations performed by the first device in the embodiment of the method, and the processor 402 invokes a computer program stored in the memory 401 to perform the battery evaluation method shown in FIG. 2. Details will be described below.

[0288] When the device under test satisfies the trigger condition of the battery evaluation task, the first device controls the device under test to perform a charge / discharge process corresponding to the battery evaluation task, obtains test data of the device under test in the charge / discharge process, the first device determines a battery evaluation result based on the test data, and the first device transmits the battery evaluation result to the second device.

[0289] In a possible implementation, the first device controlling the device under test to perform a charge / discharge process corresponding to the battery evaluation task includes, when obtaining authorization to perform the battery evaluation task, the first device controlling the device under test to perform a charge / discharge process corresponding to the battery evaluation task.

[0290] In a possible implementation, the method further includes, when the first device has not obtained authorization to perform the battery evaluation task, sending request information to the second device, and the first device receiving authorization information sent by the second device, wherein the authorization information is used to allow the first device to perform the battery evaluation task.

[0291] In a possible implementation, the authorization information includes the number of authorizations and / or the authorization period.

[0292] In a possible implementation, the trigger condition includes being able to accurately obtain the state of charge of the device under test.

[0293] In a possible implementation, the trigger condition includes the device under test being in a fully charged state.

[0294] In a possible implementation, the trigger condition includes the cumulative mileage of the device under test being greater than a preset mileage and / or the cumulative number of times the device under test has been charged being greater than a preset number.

[0295] In a possible implementation, the first device controls the device under test to perform a charge / discharge process corresponding to the battery evaluation task, and acquiring test data for the device under test in the charge / discharge process includes the first device controlling the device under test to discharge, acquiring a first charge state after the device under test completes discharging, and the first device acquiring a second charge state and charge amount of the device under test, where the second charge state corresponds to the charge state obtained when the device under test is charged until a charge termination condition is met, and the charge amount corresponds to the charge amount of the device under test from the end of discharging to the time when the device is charged until the charge termination condition is met. The test data includes the first charge state, the second charge state, and the charge amount.

[0296] In a possible implementation, the first device controlling the device under test to discharge includes the first device controlling the device under test to self-discharge until a discharge termination condition is met, and / or the first device sending first reminder information to the second device, wherein the first reminder information reminds a user to discharge the device under test until a discharge termination condition is met.

[0297] In a possible implementation, the discharge termination condition includes the state of charge of the device under test being below a first threshold.

[0298] In one possible implementation, the method further includes the first device monitoring parameter data of the device under test during the process of controlling the device under test to perform self-discharge, and upon detecting that an exception has occurred in the parameter data, the first device transmits alarm information to the second device and controls the device under test to terminate self-discharge.

[0299] In a possible implementation, acquiring the first state of charge after the device under test has finished discharging includes the first device acquiring a first open-circuit voltage of the device under test after the device under test has finished discharging and remained in an idle state for a first period of time, and the first device acquiring the first state of charge based on the state of charge corresponding to the first open-circuit voltage.

[0300] In a possible implementation, the first device acquiring the second charge state and charge amount of the device under test includes, after the device under test finishes discharging and remains in an idle state for a first period of time, the first device controls the device under test to be charged and acquires the second charge state and charge amount of the device under test.

[0301] In a possible implementation, the first device controlling the device under test to be charged includes, when the device under test is connected to the charging pile, the first device turning on a charging switch of the device under test to allow the device under test to be charged until a charging termination condition is met.

[0302] In a possible implementation, the first device controlling the device under test to be charged includes the first device sending second reminder information to the second device when the device under test is connected to the charging pile, wherein the second reminder information reminds a user to turn on a charging switch of the device under test to allow the device under test to be charged until a charging termination condition is met.

[0303] In a possible implementation, the charge termination condition includes being able to accurately obtain the state of charge of the device under test.

[0304] In a possible implementation, the charge termination condition includes the device under test reaching a fully charged state.

[0305] In a possible implementation, the first device controlling the device under test to be charged further includes the first device sending third reminder information to the second device when the device under test is not connected to the charging pile, wherein the third reminder information reminds a user to connect the device under test to the charging pile.

[0306] In a possible implementation, the first device determining a battery evaluation result based on the test data includes the first device determining a maximum available electrical capacity of the device under test based on the charge amount and the difference between the first charging state and the second charging state, and the first device determining a battery health of the device under test based on a ratio of the maximum available electrical capacity of the device under test to a rated electrical capacity of the device under test, wherein the battery evaluation result includes the battery health of the device under test.

[0307] For specific details of the method executed by the processor 402, please refer to Figure 2. The details will not be described again here.

[0308] Correspondingly, the processor 402 may be further configured to call a computer program stored in the memory 401 and execute steps of a method performed by units in the battery evaluation device 300 shown in Fig. 3. For specific contents, please refer to Fig. 3. The details will not be described again here.

[0309] In another possible design, the electronic device 400 may correspond to the second device in the embodiment of the method shown in FIG. 2 . For example, the electronic device 400 may be the second device or a chip within the second device. The electronic device 400 may include components configured to perform operations performed by the second device in the embodiment of the method. In addition, the components within the electronic device 400 are individually configured to implement the operations performed by the second device in the embodiment of the method, and the processor 402 invokes a computer program stored in the memory 401 to perform the battery evaluation method shown in FIG. 2 . Details may be described below.

[0310] The second device receives the battery evaluation result sent by the first device, wherein the battery evaluation result is determined by the first device based on test data of the device under test in a charge / discharge process corresponding to the battery evaluation task, and the charge / discharge process is executed by the device under test under the control of the first device when the device under test satisfies the trigger condition of the battery evaluation task.

[0311] In a possible implementation, the method further includes the second device receiving request information sent by the first device when the first device has not obtained authorization to perform the battery evaluation task, and the second device sending authorization information to the first device, wherein the authorization information is used to allow the first device to perform the battery evaluation task.

[0312] In a possible implementation, the authorization information includes the number of authorizations and / or the authorization period.

[0313] In a possible implementation, the trigger condition includes being able to accurately obtain the state of charge of the device under test.

[0314] In a possible implementation, the trigger condition includes the device under test being in a fully charged state.

[0315] In a possible implementation, the trigger condition includes the cumulative mileage of the device under test being greater than a preset mileage and / or the cumulative number of times the device under test has been charged being greater than a preset number.

[0316] In a possible implementation, the method further includes the second device receiving first reminder information sent by the first device when the first device controls the device under test to perform discharging, wherein the first reminder information reminds the user to discharge the device under test until a discharge termination condition is met.

[0317] In a possible implementation, the discharge termination condition includes the state of charge of the device under test being below a first threshold.

[0318] In a possible implementation, the method further includes the second device receiving alarm information transmitted by the first device when the first device detects that an exception has occurred in the parameter data of the device under test during the process of controlling the device under test to perform self-discharge.

[0319] In a possible implementation, the method further includes: when the first device controls the device under test to be charged and the device under test is connected to the charging pile, the second device receives second reminder information sent by the first device, wherein the second reminder information reminds a user to turn on a charging switch of the device under test to allow the device under test to be charged until a charging termination condition is met; and the second device turns on the charging switch of the device under test to allow the device under test to be charged until the charging termination condition is met.

[0320] In a possible implementation, the charge termination condition includes being able to accurately obtain the state of charge of the device under test.

[0321] In a possible implementation, the charge termination condition includes the device under test reaching a fully charged state.

[0322] In a possible implementation, the method further includes the first device controlling the device under test to be charged, and when the device under test is not connected to the charging pile, the second device receiving second reminder information sent by the first device, wherein the third reminder information reminds the user to connect the device under test to the charging pile.

[0323] In a possible implementation, the test data includes a first state of charge, a second state of charge, and a charge amount, where the first state of charge corresponds to a charge state obtained after the device under test has terminated discharging, the second state of charge corresponds to a charge state obtained when the device under test is charged until a charge termination condition is met, and the charge amount corresponds to a charge amount of the device under test from the end of discharging to the end of charging until the charge termination condition is met.

[0324] In a possible implementation, the battery assessment result includes a battery health of the device under test, the battery health of the device under test being determined based on a ratio of a maximum available amount of electricity of the device under test to a rated amount of electricity of the device under test, and the maximum available amount of electricity of the device under test being determined based on a charge amount and a difference between a first state of charge and a second state of charge.

[0325] For specific details of the method executed by the processor 402, please refer to Figure 2. The details will not be described again here.

[0326] Correspondingly, the processor 402 may be further configured to call a computer program stored in the memory 401 and execute steps of a method performed by units in the battery evaluation device 300 shown in Fig. 3. For specific contents, please refer to Fig. 3. The details will not be described again here.

[0327] For cases where the electronic device may be a chip or a chip system, please refer to the diagram of the chip structure shown in FIG.

[0328] 5, the chip 500 includes a processor 501 and an interface 502. It should be noted that there may be one or more processors 501 and there may be multiple interfaces 502. The functions corresponding to the processor 501 and the interface 502 may be implemented by using a hardware design, or may be implemented by using a software design, or may be implemented by using a combination of software and hardware, which is not limited herein.

[0329] Optionally, the chip 500 may further include a memory 503, which is configured to store necessary program instructions and data.

[0330] In the present application, the processor 501 may be configured to call a program for implementing a battery evaluation method provided in one or more embodiments of the present application on an electronic device from the memory 503 and execute instructions included in the program. The interface 502 may be configured to output an execution result of the processor 501. In the present application, the interface 502 may specifically be configured to output each message or information of the processor 501.

[0331] For the battery evaluation method provided in one or more embodiments of the present application, please refer to the embodiment shown in Figure 2. The details will not be described again here.

[0332] According to the method provided in the embodiment of the present application, the embodiment of the present application further provides a computer-readable storage medium, which stores a computer program, and when the computer program is executed on one or more processors, the method shown in FIG.

[0333] According to the method provided in the embodiment of the present application, the embodiment of the present application further provides a computer program product, which includes a computer program, which, when executed on a processor, can implement the method shown in FIG.

[0334] The embodiment of the present application further provides a vehicle end, which includes at least one battery evaluation device 300, electronic device 400 or chip 500.

[0335] An embodiment of the present application further provides a system, which includes a vehicle end and at least one battery assessment apparatus 300, electronic device 400, or chip 500 configured to perform the steps performed by the corresponding device in any embodiment of FIG.

[0336] An embodiment of the present application further provides a system, the system including a first device and a second device, the first device configured to perform the steps performed by the first device in any embodiment of FIG. 2, and the second device configured to perform the steps performed by the second device in any embodiment of FIG. 2.

[0337] It can be understood that the memory in the embodiments of the present application may be volatile memory or nonvolatile memory, or may include volatile memory and nonvolatile memory. The nonvolatile memory may be a hard disk drive (HDD), a solid-state drive (SSD), a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM) used as an external cache. By way of example and not limitation, many forms of RAM may be used, such as static random access memory (static RAM, SRAM), dynamic random access memory (dynamic RAM, DRAM), synchronous dynamic random access memory (synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous link dynamic random access memory (synchlink DRAM, SLDRAM), and direct rambus dynamic random access memory (direct rambus RAM, DR RAM). Note that memory as described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0338] All or part of the above-described embodiments may be implemented using software, hardware, firmware, or any combination thereof. When software is used for implementation, all or part of the embodiments may be implemented in the form of a computer program product. The computer program product includes one or more computer programs or instructions. When the computer programs or instructions are loaded into a computer and executed, all or part of the procedures or functions in the embodiments of the present application are performed. The computer may be a general-purpose computer, a special-purpose computer, a computer network, a network device, user equipment, or another programmable device. The computer program or instructions may be stored in a computer-readable storage medium or transmitted from a computer-readable storage medium to another computer-readable storage medium. For example, the computer program or instructions may be transmitted from a website, computer, server, or data center to another website, computer, server, or data center via wired or wireless communication. The computer-readable storage medium may be any available medium accessible by a computer, or a data storage device integrating one or more available media, such as a server or data center. The available media may be magnetic media, such as floppy disks, hard disks, or magnetic tapes; optical media, such as digital video disks; or semiconductor media, such as solid-state drives. The computer-readable storage media may be volatile or non-volatile storage media, or may include both types of storage media: volatile and non-volatile storage media.

[0339] It may be understood that in the embodiments of the present application, the electronic device may perform some or all of the steps in the embodiments of the present application. These steps or operations are merely examples. In the embodiments of the present application, other operations or various variations of operations may be performed. In addition, steps may be performed in a sequence different from the sequence presented in the embodiments of the present application, and all operations in the embodiments of the present application may not be performed.

[0340] Those skilled in the art may recognize that the units and algorithm steps in the examples described with reference to the embodiments provided herein may be implemented by electronic hardware or a combination of computer software and electronic hardware. Whether a function is performed by hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art may implement the described functions using different methods for each specific application, but such implementation should not be considered to go beyond the scope of this application.

[0341] For the sake of convenience and concise description, for the detailed operation processes of the aforementioned systems, devices and units, please refer to the corresponding processes in the aforementioned method embodiments, and the details will not be described again here.

[0342] In some embodiments provided in this application, it should be understood that the disclosed systems, devices, and methods may be implemented in other ways. For example, the described device embodiment is merely an example. For example, the division into units is merely a logical division of function, and other divisions may be used in actual implementation. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not implemented. In addition, mutual couplings or direct couplings or communication connections shown or discussed may be implemented via some interfaces. Indirect couplings or communication connections between devices or units may be implemented in electronic, mechanical, or other forms.

[0343] Units described as separate components may or may not be physically separate, and parts shown as units may or may not be physical units, and may be located in one location or distributed across multiple network units. Some or all of the units may be selected based on actual requirements to achieve the objectives of the solutions in the embodiments.

[0344] In addition, the functional units in the embodiments of the present application may be integrated into one processing unit, or each of the units may exist physically alone, or two or more units may be integrated into one unit.

[0345] When a function is implemented in the form of a software functional unit and sold or used as an independent product, the function may be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application may essentially be implemented, or a part contributing to the present technology, or some of the technical solutions may be implemented in the form of a software product. A computer software product is stored in a storage medium and includes some instructions for instructing a computer device (which may be a personal computer, a server, a network device, etc.) to perform all or some of the steps in the method described in the embodiments of the present application. The aforementioned storage medium includes any medium capable of storing program code, such as a USB flash drive, a removable hard disk, a ROM, a RAM, a magnetic disk, or an optical disk.

[0346] The above description is merely a specific implementation of the present application and is not intended to limit the protection scope of the present application. Any variations or replacements that can be easily understood by those skilled in the art within the technical scope disclosed in the present application shall be included in the protection scope of the present application.

Claims

1. 1. A battery evaluation method, comprising: When a device under test satisfies a trigger condition of a battery evaluation task, controlling the device under test by a first device to perform a charge / discharge process corresponding to the battery evaluation task, and acquiring test data of the device under test in the charge / discharge process; determining, by the first device, a battery evaluation result based on the test data; transmitting, by the first device, the battery assessment result to a second device; A battery evaluation method comprising:

2. controlling, by the first device, the device under test to perform the charge / discharge process corresponding to the battery evaluation task, and controlling, by the first device, the device under test to perform the charge / discharge process corresponding to the battery evaluation task when authorization to perform the battery evaluation task has been obtained. The method of claim 1.

3. The method comprises: sending, by the first device, request information to the second device when authorization to perform the battery assessment task has not been obtained; receiving, by the first device, authorization information sent by the second device, the authorization information being used to authorize the first device to perform the battery assessment task; The method of claim 2 further comprising:

4. The approval information includes the number of approvals and / or the approval period. The method of claim 3.

5. the trigger condition includes the device under test being fully charged; 5. The method according to any one of claims 1 to 4.

6. The trigger condition includes: a cumulative mileage of the device under test being greater than a preset mileage; and / or a cumulative number of times the device under test has been charged being greater than a preset number of times.

6. The method according to any one of claims 1 to 5.

7. controlling, by the first device, the device under test to perform the charge / discharge process corresponding to the battery evaluation task, and obtaining the test data of the device under test during the charge / discharge process; controlling the device under test to discharge by the first device, and obtaining a first charge state after the device under test has finished discharging; acquiring, by the first device, a second state of charge and a charge amount of the device under test, the second state of charge corresponding to a state of charge obtained when the device under test is charged until a charge termination condition is met, and the charge amount corresponding to a charge amount of the device under test from when discharge is terminated until charging until the charge termination condition is met; the test data includes the first state of charge, the second state of charge, and the charge amount.

7. The method according to claim 5 or 6.

8. controlling the device under test to discharge by the first device includes: controlling the device under test to self-discharge by the first device until a discharge termination condition is met; and / or sending, by the first device, first reminder information to the second device, the first reminder information reminding a user to discharge the device under test until the discharge termination condition is met; The method of claim 7, comprising:

9. the discharge termination condition includes the state of charge of the device under test being less than a first threshold; The method of claim 8.

10. The method comprises: monitoring parameter data of the device under test during the process of controlling the device under test to self-discharge by the first device; When detecting that an exception occurs in the parameter data, the first device sends warning information to the second device and controls the device under test to terminate self-discharge; 10. The method of claim 8 or 9, further comprising:

11. Obtaining the first state of charge after the device under test has finished discharging includes: acquiring, by the first device, a first open circuit voltage of the device under test after the device under test has finished discharging and remained in an idle state for a first period of time; obtaining, by the first device, the first state of charge based on a state of charge corresponding to the first open circuit voltage; 11. The method of any one of claims 7 to 10, comprising:

12. acquiring the second state of charge and the amount of charge of the device under test by the first device; controlling the device under test to be charged by the first device after the device under test has finished discharging and remained in an idle state for the first period of time, and obtaining the second charge state and the charge amount of the device under test; 12. The method of any one of claims 7 to 11, comprising:

13. controlling the device under test to be charged by the first device, When the device under test is connected to a charging pile, turning on a charging switch of the device under test by the first device to allow the device under test to be charged until the charging termination condition is met; or transmitting, by the first device, second reminder information to the second device; the second reminder information reminding a user to turn on a charging switch of the device under test to allow the device under test to be charged until the charging termination condition is met.

13. The method according to any one of claims 7 to 12.

14. the charging termination condition includes the device under test reaching a fully charged state; The method of claim 13.

15. controlling the device under test to be charged by the first device, and further comprising: when the device under test is not connected to a charging pile, sending third reminder information by the first device to the second device, the third reminder information reminding a user to connect the device under test to the charging pile.

15. The method according to any one of claims 7 to 14.

16. determining, by the first device, the battery evaluation result based on the test data; determining, by the first device, a maximum available amount of electricity of the device under test based on the amount of charge and a difference between the first state of charge and the second state of charge; determining, by the first device, a battery health of the device under test based on a ratio of a maximum available amount of electricity of the device under test to a rated amount of electricity of the device under test; wherein the battery assessment result includes the battery health of the device under test.

16. The method according to any one of claims 7 to 15.

17. 1. A battery evaluation method, comprising: receiving, by a second device, a battery assessment result sent by a first device, the battery assessment result being determined by the first device based on test data of a device under test in a charge / discharge process corresponding to a battery assessment task, the charge / discharge process being executed by the device under test under the control of the first device when the device under test satisfies a trigger condition of the battery assessment task; A battery evaluation method comprising:

18. The method comprises: receiving, by the second device, request information sent by the first device when the first device has not obtained authorization to perform the battery assessment task; transmitting, by the second device, authorization information to the first device, the authorization information being used to authorize the first device to perform the battery assessment task; 20. The method of claim 17, further comprising:

19. The approval information includes the number of approvals and / or the approval period.

20. The method of claim 18.

20. The method comprises: receiving, by the second device, first reminder information transmitted by the first device when the first device controls the device under test to discharge, the first reminder information reminding a user to discharge the device under test until a discharge termination condition is met; 20. The method of any one of claims 17 to 19, further comprising:

21. The method comprises: receiving alarm information transmitted by the first device when the first device detects that an exception has occurred in parameter data of the device under test during the process of controlling the device under test to perform self-discharge by the second device; 21. The method of any one of claims 17 to 20, further comprising:

22. The method comprises: receiving second reminder information sent by the first device when the second device controls the device under test to be charged and the device under test is connected to a charging pile, the second reminder information reminding a user to turn on a charging switch of the device under test to allow the device under test to be charged until a charging termination condition is met; turning on the charging switch of the device under test by the second device to allow the device under test to be charged until the charging termination condition is met; 22. The method of any one of claims 17 to 21, further comprising:

23. The method comprises: receiving third reminder information sent by the first device when the second device controls the device under test to be charged and the device under test is not connected to a charging pile, the third reminder information reminding a user to connect the device under test to the charging pile; 23. The method of any one of claims 17 to 22, further comprising:

24. A battery evaluation device, a processing unit configured to, when a device under test satisfies a trigger condition of a battery evaluation task, control the device under test to perform a charge / discharge process corresponding to the battery evaluation task, obtain test data of the device under test in the charge / discharge process, and determine a battery evaluation result based on the test data; a transceiver unit configured to transmit the battery assessment result to a second device; A battery evaluation device comprising:

25. A battery evaluation device, a transceiver unit configured to receive a battery evaluation result transmitted by a first device, the battery evaluation result being determined by the first device based on test data of a device under test in a charge / discharge process corresponding to a battery evaluation task, the charge / discharge process being performed by the device under test under the control of the first device when the device under test satisfies a trigger condition of the battery evaluation task; Battery evaluation device.

26. 1. An electronic device comprising: a processor; An electronic device, wherein the method of any one of claims 1 to 16 or the method of any one of claims 17 to 23 is performed when the processor invokes a computer program or instruction in a memory.

27. 24. A computer readable storage medium storing a computer program or instructions which, when executed, implements the method of any one of claims 1 to 16 or 17 to 23.

28. A computer program product comprising a computer program or instructions, which when executed implements the method of any one of claims 1 to 16 or 17 to 23.

29. 24. A system comprising a first device and a second device, wherein the first device is configured to perform the method of any one of claims 1 to 16 and the second device is configured to perform the method of any one of claims 17 to 23.

Images