Battery detection apparatus and method, and electronic device, storage medium and program product

Abstract

The present application relates to a battery detection apparatus and method, and an electronic device, a storage medium and a program product. The apparatus is configured to: in response to an electronic device not establishing a communication connection with a cloud device, store historical battery data of an electric vehicle to be tested; in response to the electronic device establishing a communication connection with the cloud device, send the historical battery data to the cloud device; and in response to a battery detection instruction, acquire currently collected first battery data of said electric vehicle, and acquire target battery data associated with the first battery data; and send algorithm configuration information, the first battery data and the target battery data to an execution engine module, such that the execution engine module calls, on the basis of a description file and from an algorithm package module, a target detection algorithm corresponding to a battery type of a battery, and determines a detection result of the battery on the basis of the target detection algorithm, the first battery data and the target battery data. Therefore, when storage resources of an electronic device are limited, deep detection is performed on a battery to obtain a detection result, so as to learn the deep performance of the battery on the basis of the detection result.

Description

Battery testing apparatus, methods, electronic devices, storage media, and program products Cross-referencing

[0001] This application incorporates Chinese Patent Application No. 2024120000440, filed on December 31, 2024, entitled “Battery Testing Apparatus, Method, Electronic Device, Storage Medium and Program Product”, which is incorporated herein by reference in its entirety. Technical Field

[0002] This application relates to the field of battery testing technology, and in particular to a battery testing device, method, electronic device, storage medium, and program product. Background Technology

[0003] As one of the core components of electrical devices such as electric vehicles and electric ships, the performance of batteries directly affects the safety of these devices. Therefore, it is necessary to test batteries.

[0004] Currently, basic data about batteries are typically obtained through sensors to perform basic performance tests, such as measuring battery voltage, temperature, and insulation resistance. However, basic performance tests cannot reveal the battery's deeper performance characteristics.

[0005] Therefore, how to perform depth testing on batteries to determine their depth performance has become an urgent problem to be solved in this field. Summary of the Invention

[0006] Therefore, it is necessary to provide a battery testing device, method, electronic device, storage medium, and program product that can perform in-depth testing on batteries to obtain information about their in-depth performance, thereby addressing the aforementioned technical problems.

[0007] In a first aspect, this application provides a battery detection device, which is deployed in an electronic device and includes a business module, an algorithm package module, and an execution engine module;

[0008] The business module is configured to: store historical battery data of the electric vehicle under test in response to the lack of communication connection between the electronic device and the cloud device; send the historical battery data to the cloud device in response to the establishment of a communication connection between the electronic device and the cloud device; and, in response to a battery detection command, acquire the currently collected first battery data of the electric vehicle under test, acquire the target battery data associated with the first battery data, and send the algorithm configuration information, the first battery data, and the target battery data to the execution engine module. The algorithm configuration information includes a description file describing the dependencies between detection algorithms and the parameters of the detection algorithms. The target battery data includes battery data in the historical battery data corresponding to the SOC range where the increase in SOC is greater than or equal to a preset range, where the SOC increase is the difference between the SOC of the electric vehicle under test after charging and the SOC before charging.

[0009] The execution engine module is configured to call the target detection algorithm corresponding to the battery type from the algorithm package module according to the description file, and determine the detection result of the battery based on the target detection algorithm, the first battery data and the target battery data.

[0010] The battery testing device deployed on an electronic device provided in this embodiment can store historical battery data of the electric vehicle under test when the electronic device and the cloud device have not established a communication connection, and send the historical battery data to the cloud device when the electronic device and the cloud device establish a communication connection. This allows the historical battery data to be stored on the electronic device even when storage resources are limited. In response to a battery testing command, it acquires the currently collected first battery data of the electric vehicle under test, acquires target battery data associated with the first battery data, and sends algorithm configuration information, the first battery data, and the target battery data to the execution engine module. This enables the execution engine module to call the target detection algorithm corresponding to the battery type from the algorithm package module according to the description file when battery testing is required. Based on the target detection algorithm, the first battery data, and the target battery data, the battery testing result is determined. This allows for battery testing and result determination even when storage resources are limited on the electronic device, enabling the assessment of the battery's deep performance based on the testing results.

[0011] In one embodiment, the service module is further configured to retrieve target battery data associated with the first battery data from historical battery data stored in the cloud device when the electronic device establishes a communication connection with the cloud device.

[0012] In this embodiment, by establishing a communication connection between the electronic device and the cloud device, target battery data associated with the first battery data is obtained from the historical battery data stored on the cloud device. Because the cloud device has strong data storage capabilities, it can store massive amounts of historical battery data, such as historical battery data generated from at least one charge of hundreds, thousands, or even tens of thousands of electric vehicles. Therefore, the probability of successfully obtaining the target battery data of the electric vehicle under test from the cloud device is greater, thereby increasing the amount of data on which the subsequent target detection algorithm determines the battery detection result and improving the accuracy of the obtained detection result.

[0013] In one embodiment, the service module is further configured to retrieve target battery data associated with the first battery data from historical battery data stored in the electronic device when no communication connection is established between the electronic device and the cloud device.

[0014] In this embodiment, when the electronic device and the cloud device have not established a communication connection, the target battery data associated with the first battery data can be obtained from the historical battery data stored in the electronic device. This can increase the amount of data on which the subsequent target detection algorithm determines the detection result of the battery, and improve the accuracy of the obtained detection result.

[0015] In one embodiment, the apparatus further includes a protocol parsing module;

[0016] The business module is configured to obtain the target vehicle model of the electric vehicle under test, and receive the second battery data of the battery sent by the acquisition device based on the acquisition command corresponding to the target vehicle model, and send the target vehicle model and the second battery data to the protocol parsing module.

[0017] The protocol parsing module is configured to determine the target protocol parsing script corresponding to the target vehicle model based on the target vehicle model and a preset first correspondence, use the target protocol parsing script to parse the second battery data to obtain the first battery data, and send the first battery data to the business module; the first correspondence includes the correspondence between the vehicle model and the protocol parsing script.

[0018] The battery testing device provided in this embodiment determines the target protocol parsing script corresponding to the target vehicle model based on the target vehicle model and the preset first correspondence through the protocol parsing module. The target protocol parsing script is used to parse the second battery data to obtain the first battery data, and the first battery data is sent to the business module, so that the business module can obtain the first battery data and send the first battery data to the execution engine module. Then, the execution engine module performs depth testing on the battery of the electric vehicle under test based on the first battery data and obtains the test results, so as to know the depth performance of the battery based on the test results.

[0019] In one embodiment, the device further includes a user interface module;

[0020] The user interface module is configured to, in response to a first operation instruction for the target vehicle model identifier in the vehicle model interface, determine the target vehicle model corresponding to the target vehicle model identifier and send the target vehicle model to the business module.

[0021] The battery testing device provided in this embodiment responds to a first operation command for the target vehicle model identifier in the vehicle model interface through the user interface module, determines the target vehicle model corresponding to the target vehicle model identifier, and sends the target vehicle model to the business module, thereby enabling the business module to obtain the target vehicle model. Based on the target vehicle model, the business module obtains the first battery data of the battery of the electric vehicle under test, and then the execution engine module performs a depth test on the battery of the electric vehicle under test based on the first battery data and obtains the test results, so as to know the depth performance of the battery based on the test results.

[0022] In one embodiment, the service module is configured to acquire a collection mode, and when the collection mode is used to indicate the collection of dynamic data of the battery, determine a first collection instruction corresponding to the target vehicle model based on the target vehicle model and a preset second correspondence, and send the first collection instruction to the collection device; the second correspondence includes the correspondence between the vehicle model and the first collection instruction;

[0023] The business module is configured to receive dynamic data of the battery sent by the acquisition device based on a first acquisition command; the dynamic data includes at least one of voltage, current and temperature data, the acquisition command includes the first acquisition command, and the second battery data includes the dynamic data.

[0024] The battery testing device provided in this embodiment obtains the acquisition mode through the business module. When the acquisition mode is used to indicate the acquisition of dynamic data of the battery, it determines the first acquisition command corresponding to the target vehicle model according to the target vehicle model and the preset second correspondence, sends the first acquisition command to the acquisition device, and receives the dynamic data of the battery sent by the acquisition device based on the first acquisition command. Then, the execution engine module performs depth testing on the battery of the electric vehicle under test based on the dynamic data as the second battery data and obtains the test results so as to know the depth performance of the battery based on the test results.

[0025] In one embodiment, the service module is configured to, when the acquisition mode is used to indicate the acquisition of target vehicle information and battery dynamic data of the electric vehicle under test, determine the second acquisition command corresponding to the target vehicle model based on the target vehicle model and a preset third correspondence, and send the second acquisition command to the acquisition device; the third correspondence includes the correspondence between the vehicle model and the second acquisition command.

[0026] The business module is configured to receive target vehicle information sent by the acquisition device based on a second acquisition command, and to receive dynamic battery data sent by the acquisition device based on a first acquisition command; the acquisition command includes a first acquisition command and a second acquisition command, and the second battery data includes target vehicle information and dynamic data.

[0027] The battery testing device provided in this embodiment, when the acquisition mode is used to indicate the acquisition of target vehicle information and battery dynamic data of the electric vehicle under test, the business module determines the second acquisition instruction corresponding to the target vehicle model according to the target vehicle model and the preset third correspondence, and sends the second acquisition instruction to the acquisition device. It also receives the target vehicle information sent by the acquisition device based on the second acquisition instruction, and receives the battery dynamic data sent by the acquisition device based on the first acquisition instruction. Then, the execution engine module performs in-depth testing on the battery of the electric vehicle under test and obtains the test results based on the second battery data including dynamic data and target vehicle information, thereby improving the accuracy of the test results and enabling a more accurate understanding of the battery's in-depth performance.

[0028] In one embodiment, the service module is configured to acquire the static data of the battery if the target vehicle information does not include static data of the battery, and use the target vehicle information, dynamic data and static data as second battery data; the static data includes rated capacity and / or battery type.

[0029] The battery testing device provided in this embodiment, if the target vehicle information does not include static battery data, obtains the static battery data through the business module, and uses the target vehicle information, dynamic data, and static data as second battery data. Then, the execution engine module performs depth testing on the battery of the electric vehicle under test based on the second battery data including dynamic data, target vehicle information, and static data, and obtains the test results. Furthermore, it improves the accuracy of the test results so as to obtain the battery's depth performance based on more accurate test results.

[0030] In one embodiment, the device further includes a data storage module;

[0031] The business module is configured to query the static data of the battery from the data storage module based on the target vehicle identifier in the target vehicle information; the data storage module stores the vehicle identifier and the vehicle information corresponding to the vehicle identifier, and the vehicle information includes at least the rated capacity and battery type.

[0032] The battery testing device provided in this embodiment uses a business module to query static battery data from a data storage module based on the target vehicle identifier in the target vehicle information. This completes the static data, and the target vehicle information, dynamic data, and static data are used as second battery data. Then, the execution engine module uses the second battery data, which includes dynamic data, target vehicle information, and static data, to perform in-depth testing of the battery of the electric vehicle under test based on more comprehensive data and obtain the test results, thereby further improving the accuracy of the test results.

[0033] In one embodiment, the business module is configured to, if the battery type is not found, call a battery type identification algorithm based on the battery's dynamic data to determine the battery type.

[0034] The battery testing device provided in this embodiment determines the battery type by calling a battery type identification algorithm based on the battery's dynamic data if the battery type is not found. This allows the battery type data to be supplemented even when the battery type is not found, and further improves the accuracy of the test results by using more comprehensive data to perform in-depth testing of the battery of the electric vehicle under test.

[0035] In one embodiment, the service module is configured to receive the battery's rated capacity, determined based on input operations, from the user interface module if the battery's rated capacity is not found.

[0036] If the rated capacity of the battery is not found in the battery testing device provided in this embodiment, the business module receives the rated capacity of the battery determined based on the input operation sent by the user interface module, thereby completing the data of the rated capacity of the battery. Then, based on more comprehensive data, the battery of the electric vehicle under test is subjected to in-depth testing and the test results are obtained, thereby further improving the accuracy of the test results.

[0037] In one embodiment, the business module is configured to obtain an upgrade configuration file from the server, and determine the upgrade type and the storage address of the upgrade package corresponding to the upgrade type in the server based on the upgrade configuration file; the upgrade type includes at least one of detection algorithm upgrade, vehicle information upgrade, protocol upgrade, and application software upgrade;

[0038] The business module is configured to obtain the upgrade package based on the storage address and use the upgrade package to upgrade the original data packet corresponding to the upgrade type.

[0039] The battery testing device provided in this embodiment obtains an upgrade configuration file from the server through a business module, determines the upgrade type and the storage address of the upgrade package corresponding to the upgrade type in the server based on the upgrade configuration file, and obtains the upgrade package based on the storage address, thereby realizing the upgrade of the original data packet corresponding to the upgrade type using the upgrade package.

[0040] In one embodiment, the business module is configured to receive the detection results sent by the execution engine module and send the detection results to the user interface module;

[0041] The user interface module is configured to display the detection results.

[0042] The battery testing device provided in this application embodiment receives the testing results sent by the execution engine module through the business module and sends the testing results to the user interface module. The user interface module displays the testing results, thereby facilitating the user to view the testing results.

[0043] Secondly, this application also provides a battery testing method. The method is applied to an electronic device and includes:

[0044] In response to the lack of communication between the electronic device and the cloud device, the system stores historical battery data of the electric vehicle under test; in response to the establishment of a communication connection between the electronic device and the cloud device, the system sends the historical battery data to the cloud device; in response to a battery detection command, the system acquires the currently collected first battery data of the electric vehicle under test, acquires the target battery data associated with the first battery data, and acquires algorithm configuration information; the algorithm configuration information includes a description file describing the dependencies between detection algorithms and the parameters of the detection algorithms; the target battery data includes battery data in the historical battery data corresponding to the SOC range where the SOC increase is greater than or equal to a preset range, and the SOC increase range is the difference between the SOC of the electric vehicle under test after charging and the SOC before charging;

[0045] According to the description file, the target detection algorithm corresponding to the battery type is invoked, and the detection result of the battery is determined based on the target detection algorithm, the first battery data, and the target battery data.

[0046] Thirdly, this application also provides an electronic device. The electronic device includes a memory and a processor, the memory storing a computer program, and the processor executing the computer program to implement the steps of any of the methods described above.

[0047] Fourthly, this application also provides a computer-readable storage medium. The computer-readable storage medium stores a computer program thereon, which, when executed by a processor, implements the steps of any of the methods described above.

[0048] Fifthly, this application also provides a computer program product. The computer program product includes a computer program that, when executed by a processor, implements the steps of any of the methods described above.

[0049] The above description is only an overview of the technical solution of this application. In order to better understand the technical means of this application and to implement it in accordance with the contents of the specification, and to make the above and other objects, features and advantages of this application more obvious and understandable, specific embodiments of this application are given below. Attached Figure Description

[0050] Various other advantages and benefits will become apparent to those skilled in the art upon reading the detailed description of the preferred embodiments below. The accompanying drawings are for illustrative purposes only and are not intended to limit the scope of this application. Furthermore, the same reference numerals denote the same parts throughout the drawings. In the drawings:

[0051] Figure 1 is a structural block diagram of a battery detection device provided in an embodiment of this application;

[0052] Figure 2 is a structural block diagram of another battery detection device provided in an embodiment of this application;

[0053] Figure 3 is a schematic diagram of a vehicle brand selection interface provided in an embodiment of this application;

[0054] Figure 4 is a schematic diagram of a vehicle model interface provided in an embodiment of this application;

[0055] Figure 5 is a schematic diagram of dynamic data provided in an embodiment of this application;

[0056] Figure 6 is a schematic diagram of a target vehicle information collection interface provided in an embodiment of this application;

[0057] Figure 7 is a schematic diagram of an upgrade provided in an embodiment of this application;

[0058] Figure 8 is a schematic diagram of a detection report displaying target vehicle information provided in an embodiment of this application;

[0059] Figure 9 is a schematic diagram of a detection report displaying fault detection information provided in an embodiment of this application;

[0060] Figure 10 is a schematic diagram of a test report displaying risk assessment information provided in an embodiment of this application;

[0061] Figure 11 is a schematic diagram of a test report displaying battery performance evaluation information provided in an embodiment of this application;

[0062] Figure 12 is a schematic flowchart of a battery detection method provided in an embodiment of this application;

[0063] Figure 13 is a flowchart illustrating another battery detection method provided in an embodiment of this application;

[0064] Figure 14 is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Detailed Implementation

[0065] The embodiments of the technical solution of this application will now be described in detail with reference to the accompanying drawings. These embodiments are only used to more clearly illustrate the technical solution of this application and are therefore merely examples, and should not be used to limit the scope of protection of this application.

[0066] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application pertains; the terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit the application; the terms “comprising” and “having”, and any variations thereof, in the specification, claims, and foregoing description of the drawings are intended to cover non-exclusive inclusion.

[0067] In the description of the embodiments of this application, technical terms such as "first" and "second" are used only to distinguish different objects and should not be construed as indicating or implying relative importance or implicitly specifying the number, specific order, or primary and secondary relationship of the indicated technical features. In the description of the embodiments of this application, "multiple" means two or more, unless otherwise explicitly defined.

[0068] In this document, the term "embodiment" means that a particular feature, structure, or characteristic described in connection with an embodiment may be included in at least one embodiment of this application. The appearance of this phrase in various places throughout the specification does not necessarily refer to the same embodiment, nor is it a separate or alternative embodiment mutually exclusive with other embodiments. It will be explicitly and implicitly understood by those skilled in the art that the embodiments described herein can be combined with other embodiments.

[0069] In the description of the embodiments in this application, the term "and / or" is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, and B existing alone. Additionally, the character " / " in this document generally indicates that the preceding and following related objects have an "or" relationship.

[0070] In the description of the embodiments of this application, the term "multiple" refers to two or more (including two), similarly, "multiple sets" refers to two or more (including two sets), and "multiple pieces" refers to two or more (including two pieces).

[0071] As one of the core components of electrical devices such as electric vehicles and electric ships, the performance of batteries directly affects the safety of these devices. Therefore, it is necessary to test batteries.

[0072] Currently, basic data about batteries are typically obtained through sensors to perform basic performance tests, such as measuring battery voltage, temperature, and insulation resistance. However, these basic performance tests cannot reveal the deeper performance characteristics of the battery.

[0073] Therefore, how to conduct in-depth testing on batteries to understand their underlying performance has become an urgent problem to be solved in this field.

[0074] To address the aforementioned technical problems, this application provides a battery testing device, as shown in Figure 1. Figure 1 is a structural block diagram of a battery testing device provided in this application embodiment. The battery testing device is deployed on an electronic device and includes a business module 11, an algorithm package module 12, and an execution engine module 13. The testing device can be installed on an electronic device, and the application (APP) for the battery testing method corresponding to the battery testing device can be deployed on the electronic device, which may include desktop computers, laptops, smartphones, tablets, etc. The battery data mentioned in this application embodiment refers to the battery data of the electric vehicle under test.

[0075] The business module 11 is configured to: store historical battery data of the electric vehicle under test in response to the lack of communication connection between the electronic device and the cloud device; send the historical battery data to the cloud device in response to the establishment of communication connection between the electronic device and the cloud device; and, in response to a battery detection command, acquire the currently collected first battery data of the electric vehicle under test, acquire the target battery data associated with the first battery data, and send the algorithm configuration information, the first battery data, and the target battery data to the execution engine module 13. The algorithm configuration information includes a description file describing the dependencies between detection algorithms and the parameters of the detection algorithms. The detection algorithms are used to perform at least one of the following on the battery of the electric vehicle under test: state detection, life detection, thermal management detection, and fault detection. The target battery data includes battery data in the historical battery data corresponding to the SOC range where the increase in State of Charge (SOC) is greater than or equal to a preset range. The SOC increase range is the difference between the SOC of the electric vehicle under test after charging and the SOC before charging.

[0076] The first battery data may include, but is not limited to, battery voltage, current, temperature, and resistance. Subsequent battery data may also include, but is not limited to, battery voltage, current, temperature, and resistance.

[0077] The execution engine module 13 is configured to call the target detection algorithm corresponding to the battery type from the algorithm package module 12 according to the description file, and determine the detection result of the battery based on the target detection algorithm, the first battery data and the target battery data.

[0078] The algorithm configuration information includes a description file describing the dependencies between detection algorithms, and the parameters of the detection algorithms, which include both input and output parameters. The description file includes the topological relationships between the detection algorithms. The output parameter of one detection algorithm can be used as the input parameter of another. The detection algorithms can include at least state detection algorithms, lifetime detection algorithms, thermal management detection algorithms, and fault detection algorithms. Specifically, state detection algorithms are used to detect the battery's state, including but not limited to state of charge (SOC) detection algorithms, single-cell voltage detection algorithms, and charging efficiency detection algorithms; lifetime detection algorithms are used to detect the battery's lifetime, including but not limited to state of health (SOH) detection algorithms; thermal management detection algorithms are used to detect the battery's thermal management, including but not limited to energy conversion efficiency detection algorithms; and fault detection algorithms are used to detect battery faults, including but not limited to voltage sampling failure fault detection algorithms, temperature sampling failure fault detection algorithms, battery overvoltage detection algorithms, battery undervoltage detection algorithms, and low insulation resistance detection algorithms. These detection algorithms enable in-depth battery detection.

[0079] The algorithm package module may include SOH detection algorithm, SOC detection algorithm, fault detection algorithm, battery type identification algorithm, and other detection algorithms.

[0080] The device may also include a data storage module 14, where algorithm configuration information can be stored and the business module 11 can obtain the algorithm configuration information from the data storage module 14, or the algorithm configuration information can be stored in a database server and the business module 11 can obtain the algorithm configuration information from the database server.

[0081] The electric vehicle under test (EVD) can include, but is not limited to, electric vehicles, electric ships, and other electrical devices. The EVD can establish a communication connection with one end of the data acquisition device 18 via a connecting cable, and the other end of the data acquisition device 18 can establish a communication connection with an electronic device via Bluetooth. The data acquisition device 18 can collect battery data from the EVD's battery and send the collected battery data to the service module 11 in the electronic device. The service module 11 can parse the battery data to obtain first battery data. Alternatively, the device can also include a protocol parsing module 15, where the service module 11 sends battery data to the protocol parsing module 15, which then parses the battery data to obtain the first battery data. Alternatively, the service module 11 can send battery data to other devices and receive the first battery data obtained after parsing the battery data from other devices.

[0082] The business module can store historical battery data of the electric vehicle under test when the electronic device and the cloud device have not established a communication connection; and send the historical battery data to the cloud device when the electronic device and the cloud device establish a communication connection, thereby enabling the storage of collected historical battery data in the cloud device even when the storage resources of the electronic device are limited. In response to a battery detection command, it acquires the currently collected first battery data of the electric vehicle under test and acquires the target battery data associated with the first battery data. The detection command is used to trigger the acquisition of the currently collected first battery data of the electric vehicle under test and the acquisition of the target battery data associated with the first battery data. The detection command can be a command triggered by the user interacting with controls on the interface provided by the user interface module, or a detection command generated by the business module when it determines that the increase in the battery's state of charge is not less than a preset range, or a detection command generated by the business module when it determines that the increase in the battery's state of charge is less than a preset range. For example, if the preset range is 50%, and the increase in the battery's state of charge is 50%, a detection command can be generated. The increase is equal to the difference between the battery's current state of charge and the state of charge before charging. For example, if the current state of charge is 80% and the state of charge before charging is 30%, then the increase in the state of charge is equal to 50%.

[0083] It should be noted that if the detection instruction is generated when the business module determines that the increase in the state of charge of the battery is less than a preset range, and if the increase in the state of charge corresponding to the first battery data is less than the preset range, then by acquiring the target battery data, the amount of data on which the subsequent target detection algorithm determines the battery detection result can be increased, thereby improving the accuracy of the obtained detection result.

[0084] The business module can respond to a detection command and retrieve target battery data associated with the first battery data from historical battery data stored on the cloud device. The historical battery data stored on the cloud device can be uniquely identified by the vehicle model of the electric vehicle under test. The business module can retrieve the target battery data associated with the first battery data based on the vehicle model. The target battery data can be battery data within, for example, the aforementioned increment range. That is, when the electronic device and the cloud device have not established a communication connection, the historical battery data of the electric vehicle under test is stored; when a communication connection is established, the historical battery data is sent to the cloud device. If a communication connection has been established between the electronic device and the cloud device, battery data corresponding to a SOC range greater than or equal to a preset increment can be retrieved from the historical battery data stored on the cloud device. This SOC range is used as the target battery data, and the currently collected first battery data of the electric vehicle under test is retrieved. If a communication connection has not been established between the electronic device and the cloud device, battery data corresponding to a SOC range greater than or equal to a preset increment can be retrieved from the historical battery data stored on the electronic device. This SOC range is used as the target battery data. The target battery data may include, but is not limited to, battery voltage, current, temperature, resistance, and other data.

[0085] The SOC range greater than or equal to a preset range refers to the SOC range where the increase in SOC after charging is greater than the increase in SOC before charging. This SOC range corresponds to the interval between the pre-charging SOC and the post-charging SOC. For example, if the pre-charging SOC is 20% and the post-charging SOC is 80%, and the preset range is 50%, then the increase is 60%, and the SOC range with an increase greater than or equal to the preset range is the range from 20% to 80%. Correspondingly, the battery data corresponding to this 20% to 80% range is the target battery data.

[0086] For example, if an electronic device stores historical battery data of two charging cycles of the electric vehicle under test, the historical battery data of the two charging cycles includes first historical battery data and second historical battery data. The SOC range corresponding to the first historical battery data is 20% to 80%, and the SOC range corresponding to the second historical battery data is 40% to 80%. Since the increase in the SOC range corresponding to the first historical battery data is greater than the preset range, the first historical battery data can be used as the target battery data.

[0087] Battery data in the embodiments of this application, such as first battery data, target battery data, and historical battery data, may include, but are not limited to, voltage data, current data, SOC data, power data, and temperature data during the charging process.

[0088] The execution engine module 13 can call the target detection algorithm corresponding to the battery type from the algorithm package module 12 according to the description file, and determine the battery detection result based on the target detection algorithm, the first battery data, and the target battery data. The battery type can include ternary lithium batteries, lithium iron phosphate batteries, etc. One algorithm package corresponds to one battery type, and this algorithm package can include multiple detection algorithms. Different battery types correspond to different algorithm packages, meaning the detection algorithms in the algorithm packages corresponding to different battery types are different. For example, the SOH detection algorithm in the algorithm package corresponding to ternary lithium batteries is different from the SOH detection algorithm in the algorithm package corresponding to lead-acid batteries. There can be multiple target detection algorithms, and these algorithms may have dependencies on each other; that is, the detection result of one target detection algorithm can be used as input parameters for one or more other target detection algorithms.

[0089] Battery test results may include, but are not limited to, SOH, SOC, charging efficiency, and fault detection results, thereby revealing the battery's overall performance.

[0090] The battery testing device deployed on an electronic device provided in this embodiment can store historical battery data of the electric vehicle under test when the electronic device and the cloud device have not established a communication connection, and send the historical battery data to the cloud device when the electronic device and the cloud device establish a communication connection. This allows the historical battery data to be stored on the electronic device even when storage resources are limited. In response to a battery testing command, it acquires the currently collected first battery data of the electric vehicle under test, acquires target battery data associated with the first battery data, and sends algorithm configuration information, the first battery data, and the target battery data to the execution engine module. This enables the execution engine module to call the target detection algorithm corresponding to the battery type from the algorithm package module according to the description file when battery testing is required. Based on the target detection algorithm, the first battery data, and the target battery data, the battery testing result is determined. This allows for battery testing and result determination even when storage resources are limited on the electronic device, enabling the assessment of the battery's deep performance based on the testing results.

[0091] In one embodiment, the service module is further configured to retrieve target battery data associated with the first battery data from historical battery data stored in the cloud device when the electronic device establishes a communication connection with the cloud device.

[0092] When an electronic device establishes a communication connection with a cloud device, it can obtain battery data corresponding to the SOC range with an increase greater than or equal to a preset range from the historical battery data stored in the cloud device, and use the battery data corresponding to the SOC range with an increase greater than or equal to the preset range as the target battery data.

[0093] Alternatively, when an electronic device establishes a communication connection with a cloud device, if the increase in SOC within the SOC range corresponding to the first battery data exceeds a preset range, then at least one historical battery data point can be used as the target battery data associated with the first battery data. For example, if the electronic device stores historical battery data from two charging cycles of the electric vehicle under test, including first historical battery data and second historical battery data, where the SOC range corresponding to the first historical battery data is 20% to 80% and the SOC range corresponding to the second historical battery data is 40% to 80%, then either the first historical battery data or the second historical battery data can be used as the target battery data, or both can be used as the target battery data.

[0094] In this embodiment, by establishing a communication connection between the electronic device and the cloud device, target battery data associated with the first battery data is obtained from the historical battery data stored on the cloud device. Because the cloud device has strong data storage capabilities, it can store massive amounts of historical battery data, such as historical battery data generated from at least one charge of hundreds, thousands, or even tens of thousands of electric vehicles. Therefore, the probability of successfully obtaining the target battery data of the electric vehicle under test from the cloud device is greater, thereby increasing the amount of data on which the subsequent target detection algorithm determines the battery detection result and improving the accuracy of the obtained detection result.

[0095] In one embodiment, the business module is further configured to retrieve target battery data associated with the first battery data from historical battery data stored in the electronic device, in the absence of a communication connection between the electronic device and the cloud device.

[0096] When no communication connection is established between the electronic device and the cloud device, battery data corresponding to a SOC range greater than or equal to a preset range can be obtained from the historical battery data stored in the electronic device, and the battery data corresponding to the SOC range greater than or equal to the preset range can be used as the target battery data.

[0097] The process of obtaining target battery data from electronic devices is similar to the process of obtaining target battery data from historical battery data stored in the cloud, and will not be repeated here. The difference is that the target battery data is obtained from electronic devices.

[0098] In this embodiment, when the electronic device and the cloud device have not established a communication connection, the target battery data associated with the first battery data can be obtained from the historical battery data stored in the electronic device. This can increase the amount of data on which the subsequent target detection algorithm determines the detection result of the battery, and improve the accuracy of the obtained detection result.

[0099] In one embodiment, as shown in FIG2, FIG2 is a structural block diagram of another battery detection device provided in an embodiment of the present application. The battery detection device may further include a protocol parsing module 15.

[0100] The business module 11 is further configured to acquire the target vehicle model of the electric vehicle under test, and receive the second battery data of the battery sent by the acquisition device 18 based on the acquisition command corresponding to the target vehicle model, and send the target vehicle model and the second battery data to the protocol parsing module 15; the second battery data may include, but is not limited to, the initial data such as battery voltage, current, temperature, and resistance collected by the acquisition device, that is, the battery data collected by the acquisition device without any processing. Afterwards, the protocol parsing module can parse the second battery data to obtain the first battery data.

[0101] The protocol parsing module 15 is configured to determine the target protocol parsing script corresponding to the target vehicle model based on the target vehicle model and the preset first correspondence, use the target protocol parsing script to parse the second battery data to obtain the first battery data, and send the first battery data to the service module 11; the first correspondence includes the correspondence between the vehicle model and the protocol parsing script.

[0102] For electric vehicles, the target vehicle model can include vehicle type information, such as model A1, model A2, or model A3 of brand A, or a model from another brand. The battery detection device can also include a user interface module 16. Users can input the vehicle model through the interface provided by the user interface module 16, which will then use the input vehicle model as the target vehicle signal. Alternatively, users can select a vehicle model displayed in the vehicle model interface through clicks or double-clicks, and the user interface module 16 will use the selected vehicle model as the target vehicle model. The user interface module can send the target vehicle model to the business module 11, allowing the business module 11 to obtain the target vehicle model.

[0103] The service module 11 can send acquisition commands to the acquisition device 18 and receive second battery data from the battery sent by the acquisition device 18 based on the acquisition commands. In this embodiment, the service module 11 may include an acquisition command control submodule, which can send acquisition commands to the acquisition device 18, receive second battery data from the battery sent by the acquisition device 18 based on the acquisition commands, and send the second battery data to the protocol parsing module 15. Specifically, the protocol parsing submodule in the service module 11 can send parsing commands to the protocol parsing module 15, which instruct the protocol parsing module 15 to parse the received second battery data.

[0104] The protocol parsing module 15 stores a preset first correspondence, which includes the vehicle model and the corresponding protocol parsing script. Based on this first correspondence, the protocol parsing script corresponding to the target vehicle model can be determined. This target protocol parsing script is then used to parse the second battery data to obtain the first battery data. The protocol parsing script can be an OBD protocol parsing script. Since the OBD data protocols differ for different vehicle models of electric vehicles, customized data reading and parsing are required for each vehicle model. OBD stands for On-Board Diagnostics, referring to the vehicle's automatic diagnostic system. The protocol parsing module 15 is specifically designed to manage protocols for various vehicle models. The protocol parsing module 15 mainly includes multiple vehicle models and the corresponding protocol parsing scripts for each vehicle model, thereby covering most electric vehicle models currently on the market. Moreover, as the number of electric vehicle models increases in the future, it is easy to add protocol parsing scripts for new vehicle models and their corresponding protocol parsing scripts through the protocol parsing module 15 to match the data parsing requirements of the batteries of the newly added electric vehicle models.

[0105] The battery testing device provided in this embodiment determines the target protocol parsing script corresponding to the target vehicle model based on the target vehicle model and the preset first correspondence through the protocol parsing module. The target protocol parsing script is used to parse the second battery data to obtain the first battery data, and the first battery data is sent to the business module, so that the business module can obtain the first battery data and send the first battery data to the execution engine module. Then, the execution engine module performs depth testing on the battery of the electric vehicle under test based on the first battery data and obtains the test results, so as to know the depth performance of the battery based on the test results.

[0106] In one embodiment, as shown in FIG2, the device further includes a user interface module 16;

[0107] The user interface module 16 is configured to, in response to a first operation instruction for the target vehicle model identifier in the vehicle model interface, determine the target vehicle model corresponding to the target vehicle model identifier and send the target vehicle model to the business module 11.

[0108] This embodiment of the application describes the process of determining the target vehicle model in conjunction with Figures 3 and 4. Referring to Figures 3 and 4, Figure 3 is a schematic diagram of a vehicle brand selection interface provided in this embodiment of the application, and Figure 4 is a schematic diagram of a vehicle model interface provided in this embodiment of the application. Users can select the vehicle brand from Figure 3 based on the vehicle brand of the electric vehicle under test. The desired vehicle brand can be selected by clicking, touching, double-clicking, etc. If the desired vehicle brand is not currently displayed in the interface of Figure 3, the user can enter the desired vehicle brand in the input box 301 shown in Figure 3 to find the desired vehicle brand and then select it. The vehicle brands shown in Figure 3 can include brands 1 to 27.

[0109] After selecting the desired vehicle brand, the user will enter the interface shown in Figure 4. Figure 4 displays the various vehicle model identifiers under that brand. The user can select the corresponding vehicle model identifier from the interface shown in Figure 4 based on the vehicle model of the electric vehicle under test. This selection can be made by clicking, touching, double-clicking, or using a stylus. If the desired vehicle model identifier is not currently displayed in Figure 4, the user can enter it in input box 401 shown in Figure 4 to find and select it. Figure 4 shows that the vehicle model identifiers under brand 1 can include vehicle models 11 to 17.

[0110] For example, taking the electric vehicle under test as an electric vehicle, Figure 3 can display the various vehicle brands of the electric vehicle, and Figure 4 can display the vehicle model under the vehicle brand.

[0111] When a user selects a vehicle model identifier, the user interface module 16 can respond to a first operation command for the selected vehicle model identifier in the vehicle model interface, determine the vehicle model corresponding to the vehicle model identifier, and use that vehicle model as the target vehicle model. The first operation command can be an operation command triggered by clicking, touching, double-clicking, stylus touch, etc.

[0112] The battery testing device provided in this embodiment responds to a first operation command for the target vehicle model identifier in the vehicle model interface through the user interface module, determines the target vehicle model corresponding to the target vehicle model identifier, and sends the target vehicle model to the business module, thereby enabling the business module to obtain the target vehicle model. Based on the target vehicle model, the business module obtains the first battery data of the battery of the electric vehicle under test, and then the execution engine module performs a depth test on the battery of the electric vehicle under test based on the first battery data and obtains the test results, so as to know the depth performance of the battery based on the test results.

[0113] In one embodiment, the service module 11 is further configured to acquire a collection mode, and when the collection mode indicates the collection of dynamic data of the battery, determine a first collection instruction corresponding to the target vehicle model based on the target vehicle model and a preset second correspondence, and send the first collection instruction to the collection device 18; the second correspondence includes the correspondence between the vehicle model and the first collection instruction; the collection mode is used to indicate which data the collection device should collect. In this embodiment, the collection mode is used to instruct the collection device to collect dynamic data of the battery.

[0114] The service module 11 is further configured to receive dynamic battery data sent by the acquisition device 18 based on a first acquisition command; the dynamic data includes at least one of voltage, current, and temperature data, the acquisition command includes the first acquisition command, and the second battery data includes the dynamic data. The second battery data is data directly acquired by the acquisition device, that is, raw data acquired by the acquisition device without any processing.

[0115] The acquisition mode can be obtained through the acquisition mode selection interface provided by the user interface module 16. In one possible implementation, the acquisition mode selection interface can display an acquisition mode selection switch. If the user turns on the acquisition mode selection switch, it can be determined that the acquisition mode is used to indicate the acquisition of dynamic data of the battery; if the switch is turned off, it can be determined that the acquisition mode is used to indicate the acquisition of dynamic data of the battery and target vehicle information of the electric vehicle under test. It should be noted that, as shown in Figure 2, the acquisition mode can be obtained through the flow control submodule in the user interface module 16 and sent to the business module 11.

[0116] In another possible implementation, the data acquisition mode selection interface can display a data acquisition mode selection control. This control can include a first control and a second control. The first control corresponds to a data acquisition mode that only acquires dynamic data from the battery. The second control corresponds to a data acquisition mode that acquires both dynamic data from the battery and target vehicle information from the electric vehicle under test. If the user clicks, double-clicks, or touches the first control, the data acquisition mode is determined to be for acquiring dynamic data from the battery; similarly, if the user clicks, double-clicks, or touches the second control, the data acquisition mode is determined to be for acquiring both dynamic data from the battery and target vehicle information from the electric vehicle under test.

[0117] The acquisition instruction control submodule in business module 11 can determine the first acquisition instruction corresponding to the target vehicle model based on the target vehicle model and the preset second correspondence, and send the first acquisition instruction to acquisition device 18. Acquisition device 18 sends the first acquisition instruction to the detection device in the electric vehicle under test. The detection device in the electric vehicle under test receives the first acquisition instruction, parses it to obtain a first parsing result, and performs dynamic data acquisition of the battery based on the first parsing result. It then sends the detected dynamic data to acquisition device 18, and acquisition device 18 sends the battery dynamic data to acquisition instruction control submodule, thereby enabling business module 11 to acquire the battery dynamic data. After acquiring the battery dynamic data, business module 11 can store the battery dynamic data in the dynamic data storage submodule shown in Figure 2.

[0118] The dynamic data of the battery can be seen in Figure 5, which is a schematic diagram of dynamic data provided in an embodiment of this application. Dynamic data acquisition involves obtaining dynamic information such as battery voltage, current, and temperature. The data acquisition frequency of the system design can be less than 10 seconds. During the acquisition process, the total number of individual cells and the voltage of each cell can be displayed through the data display submodule in the user interface module 16 shown in Figure 2, with the highest and lowest voltages identified and the voltage difference between the highest and lowest voltages calculated. As shown in Figure 5, cells 6, 7, and 11 have the highest voltages and can be identified by a certain color; cell 77 has the lowest voltage and can be identified by a different color than cells 6, 7, and 11. The number of temperature sensors and the highest and lowest temperatures of each sensor can also be displayed; the total current curve, SOC value, charging time, etc., can also be displayed. Dynamic data acquisition can be stopped by operating the stop dynamic acquisition control in Figure 5. Operations on the stop dynamic data acquisition control can include, but are not limited to, clicking, double-clicking, and touching.

[0119] The battery testing device provided in this embodiment obtains the acquisition mode through the business module. When the acquisition mode is used to indicate the acquisition of dynamic data of the battery, it determines the first acquisition command corresponding to the target vehicle model according to the target vehicle model and the preset second correspondence, sends the first acquisition command to the acquisition device, and receives the dynamic data of the battery sent by the acquisition device based on the first acquisition command. Then, the execution engine module performs depth testing on the battery of the electric vehicle under test based on the dynamic data as the second battery data and obtains the test results so as to know the depth performance of the battery based on the test results.

[0120] In one embodiment, the business module 11 is further configured to, when the acquisition mode is used to indicate the acquisition of target vehicle information and battery dynamic data of the electric vehicle under test, determine the second acquisition instruction corresponding to the target vehicle model according to the target vehicle model and a preset third correspondence, and send the second acquisition instruction to the acquisition device 18; the third correspondence includes the correspondence between the vehicle model and the second acquisition instruction.

[0121] The service module 11 is further configured to receive target vehicle information sent by the acquisition device 18 based on a second acquisition command, and to receive battery dynamic data sent by the acquisition device 18 based on a first acquisition command. The acquisition command includes a first acquisition command and a second acquisition command, and the second battery data includes target vehicle information and dynamic data. The first acquisition command instructs the acquisition device to acquire target vehicle information in response to the first acquisition command and send the target vehicle information to the service module 11. The second acquisition command instructs the acquisition device to acquire target vehicle information in response to the second acquisition command and send the target vehicle information to the service module 11.

[0122] In this embodiment, the target vehicle information may include the Vehicle Identification Number (VIN) and mileage of the electric vehicle under test, where the VIN is a unique identifier for the electric vehicle under test. The target vehicle information may also include the battery type and rated capacity of the battery in the electric vehicle under test. As shown in Figure 6, Figure 6 is a schematic diagram of a target vehicle information collection interface provided in this embodiment. The collected VIN, mileage, and battery type can be displayed through the target vehicle information collection interface. The collection progress can be indicated by the color of the circle on the left side of the target vehicle information collection interface. For example, when collection is complete, the entire circle is green; when collection is incomplete, the green area indicates the collection progress. When collection is complete, the user can operate the dynamic collection control shown in Figure 6 to trigger the collection of dynamic battery data.

[0123] The acquisition instruction control submodule in business module 11 can determine the second acquisition instruction corresponding to the target vehicle model based on the target vehicle model and a preset third correspondence, and send the second acquisition instruction to acquisition device 18. Acquisition device 18 sends the second acquisition instruction to the detection device in the electric vehicle under test. The detection device in the electric vehicle under test receives the second acquisition instruction, parses it to obtain a second parsing result, and performs acquisition of the target vehicle information of the battery based on the second parsing result. It then sends the detected target vehicle information to acquisition device 18, and acquisition device 18 sends the target vehicle information of the battery to acquisition instruction control submodule, thereby enabling business module 11 to acquire the target vehicle information. After acquiring the target vehicle information, business module 11 can store the target vehicle information in the static data storage submodule shown in Figure 2. The target vehicle information can include three-electric data, i.e., the basic information of the target vehicle, which can include VIN, brand, vehicle model, rated capacity, total voltage, battery type, etc.

[0124] It should be noted that if the target vehicle information does not include battery type and / or rated capacity, that is, if the battery type and / or rated capacity of the battery in the electric vehicle under test has not been collected, then the battery type and / or rated capacity data can be supplemented. The data supplementation scheme will be described later through other embodiments.

[0125] The battery testing device provided in this embodiment, when the acquisition mode is used to indicate the acquisition of target vehicle information and battery dynamic data of the electric vehicle under test, the business module determines the second acquisition instruction corresponding to the target vehicle model according to the target vehicle model and the preset third correspondence, and sends the second acquisition instruction to the acquisition device. It also receives the target vehicle information sent by the acquisition device based on the second acquisition instruction, and receives the battery dynamic data sent by the acquisition device based on the first acquisition instruction. Then, the execution engine module performs in-depth testing on the battery of the electric vehicle under test and obtains the test results based on the second battery data including dynamic data and target vehicle information, thereby improving the accuracy of the test results and enabling a more accurate understanding of the battery's in-depth performance.

[0126] In one embodiment, the business module 11 is further configured to acquire the static data of the battery if the target vehicle information does not include static data of the battery, and use the target vehicle information, dynamic data and static data as second battery data; the static data includes rated capacity and / or battery type.

[0127] In this embodiment, if the target vehicle information does not include static battery data, the static battery data can be obtained through the data completion submodule in the business module 11 to complete the static battery data, so that the target vehicle information, dynamic data and static data can be used as the second battery data in the future.

[0128] The business module 11 can query the static data corresponding to the target vehicle identifier in the target vehicle information from the vehicle information storage submodule in the data storage module 14. If no static data corresponding to the target vehicle identifier is found, for the battery type, the business module 11 can determine the battery type by calling the battery type identification algorithm based on the battery's dynamic data. For the battery's rated capacity, it can receive the battery's rated capacity determined based on the input operation sent by the user interface module 16. Through the above scheme, the static data of the battery can be supplemented.

[0129] The battery testing device provided in this embodiment, if the target vehicle information does not include static battery data, obtains the static battery data through the business module, and uses the target vehicle information, dynamic data, and static data as second battery data. Then, the execution engine module performs depth testing on the battery of the electric vehicle under test based on the second battery data including dynamic data, target vehicle information, and static data, and obtains the test results. Furthermore, it improves the accuracy of the test results so as to obtain the battery's depth performance based on more accurate test results.

[0130] In one embodiment, the device further includes a data storage module 14;

[0131] The business module 11 is further configured to query the static data of the battery from the data storage module 14 based on the target vehicle identifier in the target vehicle information; the data storage module 14 stores the vehicle identifier and the vehicle information corresponding to the vehicle identifier, and the vehicle information includes at least the rated capacity and battery type.

[0132] As shown in Figure 2, the business module 11 may include a data query submodule. This submodule can query the battery's static data from the vehicle information storage submodule within the data storage module 14, based on the target vehicle identifier. The vehicle information storage submodule stores the vehicle identifier and the corresponding vehicle information.

[0133] Among them, the target vehicle identifier in the target vehicle information can be the VIN of the electric vehicle under test.

[0134] If the target vehicle information does not include the battery's rated capacity, the battery's rated capacity is obtained based on the target vehicle identifier in the target vehicle information. The vehicle information corresponding to the target vehicle identifier can be queried from the mapping relationship between vehicle identifiers and vehicle information stored in the data storage module 14, based on the target vehicle identifier in the target vehicle information. The vehicle information includes at least the rated capacity and battery type of the battery in the vehicle corresponding to the vehicle identifier. The rated capacity corresponding to the target vehicle identifier can be queried through exact matching or fuzzy matching, and the queried rated capacity is used as the rated capacity of the battery of the electric vehicle under test. The target vehicle information, dynamic data, and the queried rated capacity are used as the second battery data.

[0135] For example, if the data storage module 14 stores vehicle identifier 1 and vehicle information 1 corresponding to vehicle identifier 1, vehicle identifier 2 and vehicle information 2 corresponding to vehicle identifier 2, and vehicle identifier 3 and vehicle information 3 corresponding to vehicle identifier 3, and if the target vehicle identifier in the target vehicle information is the same as vehicle identifier 3, then the rated capacity in the vehicle information 3 corresponding to vehicle identifier 3 is used as the rated capacity of the battery of the electric vehicle under test. This matching method is a complete match.

[0136] If the target vehicle identifier is different from vehicle identifier 1, vehicle identifier 2, and vehicle identifier 3, but some data in the vehicle identifiers of different vehicles of the same model are the same (for example, the first preset number of data in the VIN code of different vehicles of the same model are the same), the rated capacity of the battery of the electric vehicle under test can be determined by a fuzzy matching method. For example, if the information starting from the first data in the target vehicle identifier is the same as the information starting from the first data in vehicle identifier 1, then the rated capacity in vehicle information 1 can be used as the rated capacity of the battery of the electric vehicle under test. This matching method is fuzzy matching.

[0137] If the target vehicle information does not include the battery type, the battery type is obtained based on the target vehicle identifier in the target vehicle information. The vehicle information corresponding to the target vehicle identifier can be queried from the mapping relationship between vehicle identifiers and vehicle information stored in the data storage module 14, based on the target vehicle identifier in the target vehicle information. The vehicle information includes at least the rated capacity and battery type of the battery in the vehicle corresponding to the vehicle identifier. The battery type corresponding to the target vehicle identifier can be queried using exact matching or fuzzy matching, and the queried battery type is used as the battery type of the electric vehicle under test. The target vehicle information, dynamic data, and the queried battery type are used as the second battery data. The query method is similar to the method described above, so it will not be repeated here.

[0138] If the target vehicle information does not include the battery's rated capacity and battery type, the vehicle information corresponding to the target vehicle identifier can be retrieved from the mapping relationship between vehicle identifiers and vehicle information stored in the data storage module 14, based on the target vehicle identifier in the target vehicle information. The vehicle information at least includes the rated capacity and battery type of the battery in the vehicle corresponding to the vehicle identifier. The battery type and rated capacity corresponding to the target vehicle identifier can be retrieved through exact matching or fuzzy matching. The retrieved battery type and rated capacity are then used as the battery type and rated capacity of the electric vehicle under test, and the target vehicle information, dynamic data, and the retrieved battery type and rated capacity are used as the second battery data. The query method is similar to the method described above, so it will not be repeated here.

[0139] The battery testing device provided in this embodiment uses a business module to query static battery data from a data storage module based on the target vehicle identifier in the target vehicle information. This completes the static data, and the target vehicle information, dynamic data, and static data are used as second battery data. Then, the execution engine module uses the second battery data, which includes dynamic data, target vehicle information, and static data, to perform in-depth testing of the battery of the electric vehicle under test based on more comprehensive data and obtain the test results, thereby further improving the accuracy of the test results.

[0140] In one embodiment, the business module 11 is further configured to, if the battery type is not found, call a battery type identification algorithm based on the battery's dynamic data to determine the battery type.

[0141] The business module 11 may include a scheduling algorithm submodule. If the battery type is not found, the scheduling algorithm submodule can send a first call instruction and the battery's dynamic data to the module docking submodule in the execution engine module 13 to invoke the battery type identification algorithm to determine the battery type. Based on the received first call instruction, the module docking submodule invokes the battery type identification algorithm in the algorithm package module 12 and transmits the battery type identification algorithm and the battery's dynamic data to the execution algorithm submodule in the execution engine module 13. The execution algorithm submodule then uses the battery type identification algorithm to determine the battery type based on the battery's dynamic data.

[0142] It should be noted that the execution engine module 13 may also include a task management submodule, which can monitor the status of the algorithm tasks executed by the execution algorithm submodule.

[0143] The battery testing device provided in this embodiment determines the battery type by calling a battery type identification algorithm based on the battery's dynamic data if the battery type is not found. This allows the battery type data to be supplemented even when the battery type is not found, and further improves the accuracy of the test results by using more comprehensive data to perform in-depth testing of the battery of the electric vehicle under test.

[0144] In one embodiment, the service module 11 is further configured to receive the rated capacity of the battery determined based on the input operation from the user interface module 16 if the rated capacity of the battery is not found.

[0145] The user interface module 16 can provide an input box so that the user can input the rated capacity of the battery, and the input rated capacity will be used as the rated capacity of the battery. Alternatively, the user interface module 16 can provide a rated capacity selection option so that the user can select a rated capacity option and the rated capacity corresponding to the selected rated capacity option will be used as the rated capacity of the battery.

[0146] If the rated capacity of the battery is not found in the battery testing device provided in this embodiment, the business module receives the rated capacity of the battery determined based on the input operation sent by the user interface module, thereby completing the data of the rated capacity of the battery. Then, based on more comprehensive data, the battery of the electric vehicle under test is subjected to in-depth testing and the test results are obtained, thereby further improving the accuracy of the test results.

[0147] In one embodiment, the business module 11 may include a platform API submodule, which can receive historical battery data sent by the cloud device 19 and send target battery data from the historical battery data to the execution engine module 13; where API is short for Application Programming Interface.

[0148] The electronic device can be used independently offline, meaning it can be used without establishing a communication connection with the cloud device. It can also be used in conjunction with the cloud device 19 via a network connection. When the electronic device is connected to the cloud device 19, it can download target battery data from the cloud device, thus providing the target detection algorithm with richer data and improving the accuracy of the detection results. Understandably, the electronic device can also synchronize the collected dynamic data of the target battery, target vehicle information, and detection results to the cloud device 19 through the platform's API submodule, managing the data at the electric vehicle level. This allows the data to be applied to business operations and also enables developers to optimize the detection algorithm.

[0149] In one embodiment, the business module 11 is further configured to obtain an upgrade configuration file from the server, and determine the upgrade type and the storage address of the upgrade package corresponding to the upgrade type in the server based on the upgrade configuration file; the upgrade type includes at least one of detection algorithm upgrade, vehicle information upgrade, protocol upgrade, and application software upgrade.

[0150] The business module 11 is further configured to obtain the upgrade package based on the storage address and use the upgrade package to upgrade the original data packet corresponding to the upgrade type.

[0151] The upgrade types include algorithm upgrades, vehicle information upgrades, protocol upgrades, and app upgrades. Each upgrade type is independent and not coupled. The app on the electronic device can automatically detect whether an upgrade is needed, and the user can choose whether to upgrade the system.

[0152] As shown in Figure 7, which is an upgrade schematic diagram provided in an embodiment of this application, when the APP is launched, an upgrade thread is started. This upgrade thread mainly performs upgrade detection and system upgrade work. After the upgrade thread is started, it connects to the server and communicates via the Hypertext Transfer Protocol (HTTP). The upgrade thread in business module 11 obtains an upgrade configuration file from the server. The upgrade configuration file may include an upgrade information set, which is a list type and supports upgrades of at least one upgrade type at a time. A data element in the upgrade information set includes an upgrade type identifier, an upgrade identifier corresponding to the upgrade type identifier, an upgrade package version identifier, an upgrade package storage address, an upgrade package release time, an upgrade package publisher, and a description of the current upgrade. Among them, the upgrade identifier is used to indicate whether an upgrade is required. It can be a boolean value, where true indicates an upgrade is required and false indicates no upgrade. If this attribute is false, the upgrade process for the upgrade type corresponding to the upgrade identifier can be terminated. The upgrade type identifier can be used to identify the upgrade type. For example, if the upgrade type identifier in a data element is 1, the upgrade type is algorithm upgrade; if the upgrade type identifier is 2, the upgrade type is protocol upgrade; if the upgrade type identifier is 3, the upgrade type is vehicle information upgrade; and if the upgrade type identifier is 4, the upgrade type is APP upgrade.

[0153] The upgrade thread obtains the upgrade configuration file from the upgrade server. It can parse the configuration file to obtain parsed information, and based on this information, determine whether to upgrade at least one data package corresponding to an upgrade type. If an upgrade is required for at least one upgrade type, it determines the storage address of the upgrade package corresponding to that upgrade type on the server, retrieves the upgrade package, and installs it. If multiple upgrade types are involved, it retrieves the upgrade package corresponding to each upgrade type and performs the corresponding upgrade for each type.

[0154] As shown in Figure 2, the server includes a system update service module 17, which is mainly used to update and upgrade the APP, protocol, algorithm, and vehicle information. It mainly includes an algorithm upgrade submodule, a protocol management submodule, a vehicle information update submodule, and an APP update submodule. The algorithm upgrade submodule includes algorithm orchestration, algorithm packaging, and algorithm package push. Through the algorithm upgrade submodule, the topology between detection algorithms can be constructed, and the dependencies between detection algorithms can be determined. The protocol management submodule includes protocol compilation and packaging, and protocol package push. The protocol management submodule can be an OBD protocol management module, through which the OBD protocol parsing script is obtained. The vehicle information update submodule includes vehicle information management and vehicle information push. The APP update submodule includes application compilation and packaging, and APP installation package push, etc. For example, if an algorithm upgrade is required, the business module 11 can obtain the algorithm package upgrade package from the algorithm upgrade submodule to upgrade the detection algorithm. If a protocol upgrade is required, the business module 11 can obtain the protocol parsing script upgrade package from the protocol management submodule to upgrade the protocol parsing script in the protocol parsing module 15. If vehicle information needs to be upgraded, business module 11 can obtain new vehicle information from the vehicle information update submodule to update the vehicle information in the vehicle information storage submodule of data storage module 14. If the APP needs to be upgraded, business module 11 can obtain a new APK package of the APP from the APP update submodule to upgrade the APP.

[0155] Among them, the algorithm upgrade submodule can construct algorithm configuration information and send the algorithm configuration information to the business module 11. The business module 11 can store the algorithm configuration information in the algorithm configuration information storage submodule in the data storage module 14.

[0156] The battery testing device provided in this embodiment obtains an upgrade configuration file from the server through a business module, determines the upgrade type and the storage address of the upgrade package corresponding to the upgrade type in the server based on the upgrade configuration file, and obtains the upgrade package based on the storage address, thereby realizing the upgrade of the original data packet corresponding to the upgrade type using the upgrade package.

[0157] In one embodiment, the business module 11 is further configured to receive the detection result sent by the execution engine module 13 and send the detection result to the user interface module 16;

[0158] The user interface module 16 is configured to display the detection results.

[0159] As shown in Figure 2, the scheduling algorithm submodule in the business module 11 can receive the detection results sent by the execution engine module 13 and send the detection results to the user interface module 16. The report viewing submodule in the user interface module 16 can display the detection results in the form of a detection report, which is convenient for users to view. As shown in Figures 8, 9, 10 and 11, Figure 8 is a schematic diagram of a detection report displaying target vehicle information provided by an embodiment of this application, Figure 9 is a schematic diagram of a detection report displaying fault detection information provided by an embodiment of this application, Figure 10 is a schematic diagram of a detection report displaying risk assessment information provided by an embodiment of this application, and Figure 11 is a schematic diagram of a detection report displaying battery performance assessment information provided by an embodiment of this application. In Figure 9, the gray area represents a faulty cell, and the gray area of ​​the temperature sensor represents the detected temperature abnormality of the corresponding cell.

[0160] It should be noted that the business module 11 can also store the detection results in the detection result storage submodule of the data storage module 14.

[0161] The battery testing device provided in this application embodiment receives the testing results sent by the execution engine module through the business module and sends the testing results to the user interface module. The user interface module displays the testing results, thereby facilitating the user to view the testing results.

[0162] In some embodiments, the data storage module 14 may further include a system configuration information storage submodule, a log information storage submodule, an algorithm configuration information storage submodule, and other data storage submodules. The system configuration information storage submodule may be used to store, for example, the device number of the acquisition device. The algorithm configuration information storage submodule may store the algorithm configuration information of the detection algorithm, so that the business module 11 can obtain the algorithm configuration information of the detection algorithm from the algorithm configuration information storage submodule. The user interface module may further include a system configuration submodule, through which configurations, for example, the device number of the acquisition device, and adding acquisition devices, are configured.

[0163] In one embodiment, as shown in FIG12, FIG12 is a schematic flowchart of a battery detection method provided in an embodiment of the present application. The method is applied to an electronic device and includes the following steps S1201-S1202:

[0164] S1201, in response to the electronic device not establishing a communication connection with the cloud device, storing historical battery data of the electric vehicle under test; in response to the electronic device establishing a communication connection with the cloud device, sending the historical battery data to the cloud device; in response to a battery detection command, acquiring the currently collected first battery data of the electric vehicle under test, acquiring target battery data associated with the first battery data, and acquiring algorithm configuration information; the algorithm configuration information includes a description file used to describe the dependencies between detection algorithms and the parameters of the detection algorithms.

[0165] The target battery data includes battery data from historical battery data that corresponds to the SOC range where the SOC increase is greater than or equal to a preset range. The SOC increase range is the difference between the SOC of the electric vehicle under test after charging and the SOC before charging.

[0166] S1202, according to the description file, call the target detection algorithm corresponding to the battery type, and determine the detection result of the battery based on the target detection algorithm, the first battery data and the target battery data.

[0167] The battery testing method provided in this embodiment can perform depth testing on the battery of the electric vehicle under test and obtain the test results, so as to know the depth performance of the battery based on the test results.

[0168] In one embodiment, when an electronic device establishes a communication connection with a cloud device, target battery data associated with the first battery data is obtained from historical battery data stored in the cloud device.

[0169] In one embodiment, when no communication connection is established between the electronic device and the cloud device, target battery data associated with the first battery data is obtained from the historical battery data stored in the electronic device.

[0170] In one embodiment, obtaining the currently collected first battery data of the electric vehicle under test in S1201 above can be achieved in the following way:

[0171] The system acquires the target vehicle model of the electric vehicle under test and receives second battery data sent by the acquisition device based on the acquisition command corresponding to the target vehicle model. According to the target vehicle model and the preset first correspondence, the system determines the target protocol parsing script corresponding to the target vehicle model and uses the target protocol parsing script to parse the second battery data to obtain the first battery data. The first correspondence includes the correspondence between the vehicle model and the protocol parsing script.

[0172] In one embodiment, the above-mentioned acquisition of the target vehicle model of the electric vehicle under test can be achieved by: in response to a first operation instruction for the target vehicle model identifier in the vehicle model interface, determining the target vehicle model corresponding to the target vehicle model identifier.

[0173] In one embodiment, the second battery data sent by the aforementioned receiving and acquisition device based on the acquisition command corresponding to the target vehicle model can be implemented in the following way:

[0174] The system acquires a data acquisition mode. When the data acquisition mode is used to indicate the acquisition of dynamic data of the battery, it determines the first acquisition command corresponding to the target vehicle model based on the target vehicle model and a preset second correspondence, and sends the first acquisition command to the data acquisition device. The second correspondence includes the correspondence between the vehicle model and the first acquisition command. The system receives dynamic data of the battery sent by the data acquisition device based on the first acquisition command. The dynamic data includes at least one of voltage, current, and temperature data. The acquisition command includes the first acquisition command, and the second battery data includes the dynamic data.

[0175] In one embodiment, the method may further include the following steps:

[0176] In the acquisition mode, when the target vehicle information and battery dynamic data of the electric vehicle under test are to be acquired, the second acquisition command corresponding to the target vehicle model is determined according to the target vehicle model and the preset third correspondence, and the second acquisition command is sent to the acquisition device; the third correspondence includes the correspondence between the vehicle model and the second acquisition command; the target vehicle information sent by the acquisition device based on the second acquisition command is received, as well as the battery dynamic data sent by the acquisition device based on the first acquisition command is received; the acquisition command includes the first acquisition command and the second acquisition command, and the second battery data includes the target vehicle information and the dynamic data.

[0177] In one embodiment, the method may further include the following steps:

[0178] If the target vehicle information does not include static data of the battery, then the static data of the battery is obtained, and the target vehicle information, dynamic data, and static data are used as the second battery data; the static data includes rated capacity and / or battery type.

[0179] In one embodiment, the above-mentioned acquisition of static battery data may further include the following steps:

[0180] Based on the target vehicle identifier in the target vehicle information, query the static data of the battery in the database; the database stores the vehicle identifier and the corresponding vehicle information, which includes at least the rated capacity and battery type.

[0181] In one embodiment, the method may further include the following steps:

[0182] If the battery type is not found, the battery type identification algorithm is called based on the battery's dynamic data to determine the battery type.

[0183] In one embodiment, the method may further include the following steps:

[0184] If the battery's rated capacity is not found, the battery's rated capacity determined based on the input operation is received.

[0185] In one embodiment, the method may further include the following steps:

[0186] The upgrade configuration file is obtained from the server. Based on the upgrade configuration file, the upgrade type and the storage address of the corresponding upgrade package on the server are determined. The upgrade type includes at least one of detection algorithm upgrade, vehicle information upgrade, protocol upgrade, and application software upgrade. The upgrade package is obtained based on the storage address, and the original data packet corresponding to the upgrade type is upgraded using the upgrade package.

[0187] In one embodiment, as shown in FIG13, FIG13 is a schematic flowchart of another battery detection method provided by the present application embodiment. Based on any of the above embodiments, the present application embodiment further describes the overall process of the battery detection method.

[0188] 1) Connecting the device: This step is part of the preparation before data acquisition, which mainly includes connecting the data acquisition device to the OBD port of the electric vehicle via a connecting cable.

[0189] 2) User Login: The system establishes an account system based on the tenant, and users can register accounts and log in.

[0190] 3) System Upgrades: A dedicated system upgrade service module has been built for system upgrades, maintained by administrators and developers. Algorithm upgrades, vehicle information upgrades, protocol upgrades, and APP upgrades are all performed independently and are not coupled. The APP on electronic devices can automatically detect whether an upgrade is needed, and users can choose whether to upgrade the system.

[0191] 4) Obtain the acquisition mode.

[0192] 5) Enter the vehicle model interface.

[0193] 6) In response to the first operation command for the target vehicle model identifier in the vehicle model interface, determine the target vehicle model corresponding to the target vehicle model identifier.

[0194] 7) Is it necessary to collect the target vehicle information of the electric vehicle under test?

[0195] 8) If it is necessary to collect the target vehicle information of the electric vehicle under test, then collect the target vehicle information.

[0196] 9) Is it necessary to complete the target vehicle information through query?

[0197] 10) If data needs to be supplemented through query, then query the static data of the battery from the data storage module.

[0198] 11) If data completion is not required through querying, then determine whether the network is connected.

[0199] 12) If connected to the internet, push the data to the cloud device and store the data in the data storage module. Where data completion is not required through querying, the data in this step includes target vehicle information; where data completion requires querying, the data in this step includes target vehicle information and the retrieved static data.

[0200] 13) Collect dynamic data.

[0201] 14) Is it necessary to complete the battery type by calling the battery type identification algorithm?

[0202] 15) If it is necessary to complete the battery type by calling the battery type identification algorithm, then the battery type identification algorithm will be called to complete the battery type based on the dynamic data.

[0203] 16) Run the target detection algorithm.

[0204] 17) Generate detection results.

[0205] 18) Is the device connected to the internet? If so, the test results and data will be synchronized to the cloud device.

[0206] 19) If there is no internet connection, the process ends.

[0207] The method provided in this embodiment can perform in-depth diagnosis and analysis of electric vehicles in offline or online conditions, and output more comprehensive test reports.

[0208] It should be understood that although the steps in the flowcharts of the embodiments described above are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowcharts of the embodiments described above may include multiple steps or multiple stages. These steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the steps or stages of other steps.

[0209] Based on the same inventive concept, this application also provides a battery testing apparatus for implementing the battery testing method described above. The solution provided by this apparatus is similar to the implementation described in the above method; therefore, the specific limitations in one or more battery testing apparatus embodiments provided below can be found in the limitations of the battery testing method described above, and will not be repeated here.

[0210] Each module in the aforementioned battery testing device can be implemented entirely or partially through software, hardware, or a combination thereof. These modules can be embedded in the processor of the electronic device in hardware form or independent of it, or stored in the memory of the electronic device in software form, so that the processor can call and execute the corresponding operations of each module.

[0211] In one embodiment, as shown in FIG14, FIG14 is a schematic diagram of the structure of an electronic device provided in an embodiment of the present application. The electronic device can be a terminal. The electronic device includes a processor, a memory, a communication interface, a display screen, and an input device connected via a system bus. The processor of the electronic device provides computing and control capabilities. The memory of the electronic device includes a non-volatile storage medium and internal memory. The non-volatile storage medium stores an operating system and computer programs. The internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage medium. The communication interface of the electronic device is used for wired or wireless communication with an external terminal. Wireless communication can be achieved through WIFI, mobile cellular networks, NFC (Near Field Communication), or other technologies. When the computer program is executed by the processor, it implements a battery detection method. The display screen of the electronic device can be a liquid crystal display screen or an e-ink display screen. The input device of the electronic device can be a touch layer covering the display screen, or buttons, a trackball, or a touchpad provided on the casing of the electronic device, or an external keyboard, touchpad, or mouse, etc.

[0212] Those skilled in the art will understand that the structure shown in Figure 14 is merely a block diagram of a portion of the structure related to the present application and does not constitute a limitation on the electronic device to which the present application is applied. The specific electronic device may include more or fewer components than shown in the figure, or combine certain components, or have different component arrangements.

[0213] In one embodiment, an electronic device is provided, including a memory and a processor. The memory stores a computer program, and the processor executes the computer program to implement the technical solutions in the above method embodiments. The implementation principle and technical effects are similar, and will not be repeated here.

[0214] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, it implements the technical solution in the above method embodiment. Its implementation principle and technical effect are similar, and will not be repeated here.

[0215] In one embodiment, a computer program product is provided, including a computer program that, when executed by a processor, implements the technical solutions described in the above method embodiments. The implementation principle and technical effects are similar and will not be repeated here.

[0216] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, data stored, data displayed, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties.

[0217] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium, and when executed, it can include the processes of the embodiments of the above methods. Any references to memory, databases, or other media used in the embodiments provided in this application can include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM). The databases involved in the embodiments provided in this application may include at least one type of relational database and non-relational database. Non-relational databases may include, but are not limited to, blockchain-based distributed databases. The processors involved in the embodiments provided in this application may be general-purpose processors, central processing units, graphics processing units, digital signal processors, programmable logic devices, quantum computing-based data processing logic devices, etc., and are not limited to these.

[0218] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0219] The embodiments described above are merely illustrative of several implementation methods of this application, and while the descriptions are specific and detailed, they should not be construed as limiting the scope of this patent application. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this application, and these all fall within the protection scope of this application. Therefore, the protection scope of this application should be determined by the appended claims.

Claims

1. A battery detection device, the device being deployed in an electronic device, the device comprising a business module, an algorithm package module, and an execution engine module; wherein, The business module is configured to: store historical battery data of the electric vehicle under test in response to the lack of communication connection between the electronic device and the cloud device; send the historical battery data to the cloud device in response to the establishment of a communication connection between the electronic device and the cloud device; and, in response to a battery detection command, acquire the currently collected first battery data of the electric vehicle under test, acquire target battery data associated with the first battery data, and send algorithm configuration information, the first battery data, and the target battery data to the execution engine module. The algorithm configuration information includes a description file describing the dependencies between detection algorithms and the parameters of the detection algorithms. The target battery data includes battery data in the historical battery data corresponding to the SOC range where the SOC increase is greater than or equal to a preset range, wherein the SOC increase is the difference between the SOC of the electric vehicle under test after charging and the SOC before charging. The execution engine module is configured to, according to the description file, call the target detection algorithm corresponding to the battery type of the battery from the algorithm package module, and determine the detection result of the battery based on the target detection algorithm, the first battery data and the target battery data.

2. The apparatus according to claim 1, wherein, The business module is further configured to, when the electronic device establishes a communication connection with the cloud device, retrieve target battery data associated with the first battery data from the historical battery data stored in the cloud device.

3. The apparatus according to claim 1, wherein, The business module is further configured to, in the absence of a communication connection between the electronic device and the cloud device, obtain target battery data associated with the first battery data from the historical battery data stored in the electronic device.

4. The apparatus according to any one of claims 1-3 further includes a protocol parsing module, wherein... The business module is further configured to obtain the target vehicle model of the electric vehicle under test, and receive the second battery data sent by the acquisition device based on the acquisition command corresponding to the target vehicle model, and send the target vehicle model and the second battery data to the protocol parsing module. The protocol parsing module is configured to determine a target protocol parsing script corresponding to the target vehicle model based on the target vehicle model and a preset first correspondence, use the target protocol parsing script to parse the second battery data to obtain the first battery data, and send the first battery data to the service module; the first correspondence includes the correspondence between vehicle model and protocol parsing script.

5. The apparatus according to claim 4, wherein, It also includes a user interface module; The user interface module is configured to, in response to a first operation instruction for a target vehicle model identifier in the vehicle model interface, determine the target vehicle model corresponding to the target vehicle model identifier, and send the target vehicle model to the service module.

6. The apparatus according to claim 4 or 5, wherein, The business module is further configured to acquire a collection mode, and when the collection mode is used to indicate the collection of dynamic data of the battery, determine a first collection instruction corresponding to the target vehicle model according to the target vehicle model and a preset second correspondence, and send the first collection instruction to the collection device; the second correspondence includes the correspondence between the vehicle model and the first collection instruction; The service module is further configured to receive dynamic data of the battery sent by the acquisition device based on the first acquisition instruction; the dynamic data includes at least one of voltage, current, and temperature data, the acquisition instruction includes the first acquisition instruction, and the second battery data includes the dynamic data.

7. The apparatus according to claim 6, wherein, The business module is further configured to, when the acquisition mode is used to indicate the acquisition of target vehicle information of the electric vehicle under test and dynamic data of the battery, determine a second acquisition command corresponding to the target vehicle model based on the target vehicle model and a preset third correspondence, and send the second acquisition command to the acquisition device; the third correspondence includes the correspondence between the vehicle model and the second acquisition command; The service module is further configured to receive the target vehicle information sent by the acquisition device based on the second acquisition instruction, and to receive the dynamic data of the battery sent by the acquisition device based on the first acquisition instruction; the acquisition instruction includes the first acquisition instruction and the second acquisition instruction, and the second battery data includes the target vehicle information and the dynamic data.

8. The apparatus according to claim 7, wherein, The business module is further configured to, if the target vehicle information does not include the static data of the battery, acquire the static data of the battery and use the target vehicle information, the dynamic data, and the static data as the second battery data; the static data includes rated capacity and / or battery type.

9. The apparatus according to claim 8, wherein, It also includes a data storage module; The business module is further configured to query the static data of the battery from the data storage module based on the target vehicle identifier in the target vehicle information; the data storage module stores the vehicle identifier and the vehicle information corresponding to the vehicle identifier, and the vehicle information includes at least the rated capacity and battery type.

10. The apparatus according to claim 9, wherein, The business module is further configured to, if the battery type is not found, use a battery type identification algorithm to determine the battery type based on the battery's dynamic data.

11. The apparatus according to claim 9 or 10, wherein, The business module is further configured to receive the rated capacity of the battery determined based on the input operation from the user interface module if the rated capacity of the battery is not found.

12. The apparatus according to any one of claims 1-11, wherein, The business module is further configured to obtain an upgrade configuration file from the server, and determine the upgrade type and the storage address of the upgrade package corresponding to the upgrade type in the server according to the upgrade configuration file; the upgrade type includes at least one of detection algorithm upgrade, vehicle information upgrade, protocol upgrade, and application software upgrade. The business module is further configured to obtain the upgrade package according to the storage address, and use the upgrade package to upgrade the original data packet corresponding to the upgrade type.

13. The apparatus according to any one of claims 1-12, wherein, The business module is further configured to receive the detection result sent by the execution engine module and send the detection result to the user interface module; The user interface module is further configured to display the detection results.

14. A battery detection method, the method being applied to an electronic device, the method comprising: In response to the failure of the electronic device to establish a communication connection with the cloud device, the historical battery data of the electric vehicle under test is stored; In response to the establishment of a communication connection between the electronic device and the cloud device, the historical battery data is sent to the cloud device; in response to the battery detection command, the system acquires the currently collected first battery data of the electric vehicle under test, acquires the target battery data associated with the first battery data, and acquires algorithm configuration information; the algorithm configuration information includes a description file for describing the dependencies between detection algorithms and the parameters of the detection algorithms; the target battery data includes battery data in the historical battery data corresponding to the SOC interval where the SOC increase is greater than or equal to a preset range, and the SOC increase range is the difference between the SOC of the electric vehicle under test after charging and the SOC before charging; According to the description file, a target detection algorithm corresponding to the battery type of the battery is invoked, and the detection result of the battery is determined based on the target detection algorithm, the first battery data, and the target battery data.

15. The method according to claim 14, wherein, When the electronic device establishes a communication connection with the cloud device, the target battery data associated with the first battery data is obtained from the historical battery data stored in the cloud device.

16. The method of claim 14, wherein, In the absence of a communication connection between the electronic device and the cloud device, target battery data associated with the first battery data is obtained from the historical battery data stored in the electronic device.

17. The method according to any one of claims 14-16, wherein, The acquisition of the currently collected first battery data of the electric vehicle under test includes: Obtain the target vehicle model of the electric vehicle under test, and receive the second battery data sent by the acquisition device based on the acquisition command corresponding to the target vehicle model; Based on the target vehicle model and a preset first correspondence, a target protocol parsing script corresponding to the target vehicle model is determined, and the second battery data is parsed using the target protocol parsing script to obtain the first battery data; the first correspondence includes the correspondence between the vehicle model and the protocol parsing script.

18. The method according to claim 17, wherein, The step of obtaining the target vehicle model of the electric vehicle under test includes: In response to a first operation command for the target vehicle model identifier in the vehicle model interface, the target vehicle model corresponding to the target vehicle model identifier is determined.

19. The method according to claim 17 or 18, wherein, The receiving and acquisition device sends second battery data based on the acquisition command corresponding to the target vehicle model, including: The acquisition mode is obtained. When the acquisition mode is used to indicate the acquisition of dynamic data of the battery, a first acquisition command corresponding to the target vehicle model is determined according to the target vehicle model and a preset second correspondence, and the first acquisition command is sent to the acquisition device; the second correspondence includes the correspondence between the vehicle model and the first acquisition command. The system receives dynamic data of the battery sent by the acquisition device based on the first acquisition command; the dynamic data includes at least one of voltage, current, and temperature data; the acquisition command includes the first acquisition command; and the second battery data includes the dynamic data.

20. The method according to claim 19, wherein, The method further includes: When the acquisition mode is used to indicate the acquisition of target vehicle information of the electric vehicle under test and dynamic data of the battery, a second acquisition command corresponding to the target vehicle model is determined according to the target vehicle model and a preset third correspondence, and the second acquisition command is sent to the acquisition device; the third correspondence includes the correspondence between the vehicle model and the second acquisition command; The system receives target vehicle information sent by the acquisition device based on the second acquisition instruction, and receives dynamic data of the battery sent by the acquisition device based on the first acquisition instruction; the acquisition instruction includes the first acquisition instruction and the second acquisition instruction, and the second battery data includes the target vehicle information and the dynamic data.

21. The method according to claim 20, wherein, The method further includes: If the target vehicle information does not include the static data of the battery, then the static data of the battery is obtained, and the target vehicle information, the dynamic data, and the static data are used as the second battery data; the static data includes the rated capacity and / or battery type.

22. The method according to claim 21, wherein, The step of obtaining the static data of the battery includes: Based on the target vehicle identifier in the target vehicle information, the static data of the battery is queried in the database; the database stores the vehicle identifier and the vehicle information corresponding to the vehicle identifier, and the vehicle information includes at least the rated capacity and battery type.

23. The method according to claim 22, wherein, The method further includes: If the battery type is not found, the battery type identification algorithm is invoked based on the battery's dynamic data to determine the battery type.

24. The method according to claim 22 or 23, wherein, The method further includes: If the rated capacity of the battery is not found, the rated capacity of the battery determined based on the input operation is received.

25. The method according to any one of claims 14-24, wherein, The method further includes: The upgrade configuration file is obtained from the server, and the upgrade type and the storage address of the upgrade package corresponding to the upgrade type in the server are determined according to the upgrade configuration file; the upgrade type includes at least one of detection algorithm upgrade, vehicle information upgrade, protocol upgrade, and application software upgrade. The upgrade package is obtained according to the storage address, and the original data packet corresponding to the upgrade type is upgraded using the upgrade package.

26. An electronic device comprising a memory and a processor, wherein the memory stores a computer program, wherein When the processor executes the computer program, it implements the steps of the method according to any one of claims 14 to 25.

27. A computer-readable storage medium having a computer program stored thereon, wherein, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 14 to 25.

28. A computer program product comprising a computer program, wherein, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 14 to 25.

Images