Algorithm development platform, method and device, electronic equipment and readable storage medium

Abstract

The invention discloses an algorithm development platform, method and device, electronic equipment and a readable storage medium. The algorithm development platform comprises an algorithm development system and an algorithm library. Wherein the algorithm library comprises at least one of an algorithm template library and an algorithm component library; the algorithm template library is used for storing battery algorithm templates, and the algorithm component library is used for storing battery algorithm components; the algorithm development system is configured with a function of developing a battery algorithm module based on the selected battery algorithm template and / or battery algorithm component; the development of a battery algorithm module can be realized, the development period of a battery algorithm in a traditional development mode is greatly shortened, the development difficulty is reduced, and the management efficiency and effect of battery service are improved.

Description

Algorithm development platform, method, device, electronic device and readable storage medium Technical Field

[0001] The present application relates to the field of software development technology, and in particular to an algorithm development platform, method, device, electronic device and readable storage medium. Background Art

[0002] In the field of new energy battery research and development, the research and development time of battery service-related algorithms is too long, seriously lagging behind the needs of battery management business; even if the algorithms have been developed, they need to be adjusted and optimized in a timely manner according to the ever-changing business scenarios; thus, the management of battery services is inefficient and ineffective.

[0003] Summary of the Invention

[0004] According to various embodiments of the present application, an algorithm development platform, method, apparatus, electronic device, and readable storage medium are provided.

[0005] In a first aspect, the present application provides an algorithm development platform, including an algorithm development system and an algorithm library; wherein the algorithm library includes: at least one of an algorithm template library and an algorithm component library; the algorithm template library is used to store battery algorithm templates, and the algorithm component library is used to store battery algorithm components; the algorithm development system is configured with: the function of developing a battery algorithm module based on the selected battery algorithm template and / or battery algorithm component.

[0006] In the above method, the algorithm development system directly develops the battery algorithm module based on the selected battery algorithm template and / or battery algorithm component; further development of the battery algorithm module can be achieved in a low-code environment based on the existing battery algorithm component or battery algorithm template, thereby greatly shortening the development cycle of the battery algorithm in the traditional development method and reducing the development difficulty, thereby improving the management efficiency and effectiveness of battery services.

[0007] In a possible implementation of the first aspect, in the battery algorithm module development, the algorithm development system is further configured with functions for developing the battery algorithm module including: a function for arranging selected battery algorithm templates and / or battery algorithm components.

[0008] Through the above method, based on the orchestration processing of the algorithm development platform, secondary development can be carried out based on existing battery algorithm components or battery algorithm templates to obtain more complex battery algorithm templates, which can be applied to more battery service application scenarios, improving the development efficiency of the battery algorithm module while improving the flexibility of the battery algorithm module in the process of managing battery services.

[0009] In a possible implementation of the first aspect, the algorithm development system is configured to support the function of organizing the selected battery algorithm template and / or battery algorithm component: the selected battery algorithm template and / or battery algorithm component are organized in series and / or in parallel to obtain the organized battery algorithm template.

[0010] In the above method, the battery algorithm templates and / or battery algorithm components are arranged in series and / or parallel, so that the output of one or more battery algorithms can be used as the input of another or multiple battery algorithms to obtain a newly developed battery algorithm, thereby realizing the secondary development of the battery algorithm and greatly improving the development efficiency of the battery algorithm.

[0011] In a possible implementation of the first aspect, the algorithm development system is further configured to develop a battery algorithm module and further includes: an algorithm publishing function;

[0012] The algorithm publishing function supports: debugging and verifying the battery algorithm to be debugged, and publishing the successfully verified battery algorithm as a battery algorithm component or battery algorithm template in the algorithm library; the selected battery algorithm includes the battery algorithm template and / or battery algorithm component to be debugged; the battery algorithm template and / or battery algorithm component to be debugged includes the uploaded battery algorithm template and / or battery algorithm component, or the compiled battery algorithm template.

[0013] In a possible implementation of the first aspect, debugging and verifying the battery algorithm to be debugged is as follows:

[0014] Debug and verify the uploaded battery algorithm template and / or battery algorithm component based on preset input parameters, output parameters, and algorithm thresholds; and / or

[0015] The battery algorithm template obtained by programming is debugged and verified based on the adjustment of input parameters, output parameters, associated parameters and programming sequence.

[0016] In the above method, during the arrangement process of secondary development of battery algorithm components and / or battery algorithm templates, the data in the database can be directly loaded, and the arranged battery algorithm template can be debugged and verified to complete the secondary development of the battery algorithm, which reduces the difficulty and complexity of battery algorithm development and improves the efficiency of battery algorithm development.

[0017] In a possible implementation of the first aspect, the algorithm publishing function further supports: the function of submitting the battery algorithm after successful verification for review; publishing the battery algorithm after successful verification as a battery algorithm component or a battery algorithm template in the algorithm library: publishing the algorithm after successful verification and review as a battery algorithm component or a battery algorithm template in the algorithm library.

[0018] Through the above method, the battery algorithm uploaded to the algorithm development platform is debugged, verified, reviewed and released, which can shorten the battery algorithm debugging and verification cycle and improve the debugging and verification efficiency of the battery algorithm; and through verification and review, the reliability of the battery algorithm is improved, thereby providing users with a usable and stable battery algorithm interface, ensuring the rationality and integrity of the battery algorithm published in the algorithm library.

[0019] In a possible implementation of the first aspect, the algorithm development platform further includes: a database, the database containing battery indicator data that supports the algorithm development system call, and the database is used to provide data support for the development of the battery algorithm module.

[0020] Through the above methods, the database of the algorithm development platform can provide rich, deterministic and diverse data support during the development of the battery algorithm, thereby improving the flexibility of the battery algorithm during development and the scalability of battery services.

[0021] In a possible implementation manner of the first aspect, the function of developing the battery algorithm module further supports: providing data support for debugging and verification of the selected battery algorithm template and / or battery algorithm component based on a database.

[0022] In a possible implementation of the first aspect, the functions of the algorithm development system configured for battery algorithm module development include: a data recovery function; the data recovery function supports: obtaining target data in the battery algorithm module development, and storing the target data as battery indicator data in the database.

[0023] Through the above method, the data generated during the development of the battery algorithm can be continuously recycled into the database as input parameters or output parameters of the algorithm platform when developing new battery algorithms; based on the data of the algorithm development process, the data in the database is enriched and optimized, and based on the continuously enriched and optimized database, the iterative efficiency of the battery algorithm in the development process is improved.

[0024] In a possible implementation of the first aspect, the data recovery function supports: obtaining the first indicator data uploaded by the user and / or the second indicator data obtained by executing the battery algorithm based on the existing battery indicator data in the database, and using the first indicator data and / or the second indicator data as the target data.

[0025] In a possible implementation of the first aspect, the data recovery function further supports: based on the existing battery indicator data in the database, performing at least one of algorithm training, algorithm debugging, algorithm verification, algorithm testing, algorithm tuning and algorithm iteration to obtain second indicator data.

[0026] In a possible implementation of the first aspect, the data recovery function also supports: based on the battery indicator data already in the database, executing at least one of algorithm training, algorithm debugging, algorithm verification, algorithm testing, algorithm tuning and algorithm iteration to obtain an execution result; based on the execution result, updating the battery indicator data already in the database to obtain second indicator data.

[0027] For example, the data in the database can come from users' sharing and uploading, or it can be data obtained during the execution of the battery algorithm, it can be data accessed in real time in the application, or it can be time series data imported offline; when the algorithm development platform executes the above process, it supports both the analysis of real-time data and the analysis of historical data.

[0028] In a possible implementation of the first aspect, the data recovery function further supports:

[0029] Based on the execution result, in response to a marking instruction input by the user, marking the existing battery indicator data in the database to obtain marked second indicator data; and / or

[0030] Based on the execution result, in response to the filtering instruction input by the user, the battery indicator data already in the database is filtered to obtain filtered second indicator data.

[0031] Through the above methods, the database can provide rich application scenarios and massive data support for the development of battery algorithms. While supporting the access and storage of multi-application data, the algorithm development platform completes the debugging and verification of battery algorithms, and realizes adaptive cycle optimization of the database to obtain a database that is more in line with actual applications. Based on this database, it can realize the rapid deduction and update of uploaded battery algorithms and secondary developed battery algorithms, thereby improving the efficiency and flexibility of battery algorithm development.

[0032] In a possible implementation of the first aspect, the algorithm development system is further configured to develop a battery algorithm module, further comprising: a function of registering an uploaded battery algorithm, and a function of deploying the registered battery algorithm.

[0033] Through the above method, the algorithm development platform provides an interface for registering battery algorithms, accepts users' registration of battery algorithms, and completes deployment, so as to provide more battery algorithms for more users, facilitate further secondary development of battery algorithms, and improve the development efficiency of more complex or difficult algorithms based on more selectable battery algorithms.

[0034] In a possible implementation of the first aspect, the algorithm development platform also includes: a visual reporting system; the visual reporting system is configured with: a function of calling and executing battery algorithm templates and / or battery algorithm components published in the algorithm library, and presenting the execution results in a visual manner.

[0035] Through the above methods, based on different battery application scenarios, the algorithm development platform can also output statistical reports that can guide actual business or assist business decision-making; thereby greatly improving battery management efficiency in various application scenarios.

[0036] In a possible implementation of the first aspect, the visual reporting system is configured with: the function of organizing the selected report templates and / or report components; the functional support for organizing the selected report templates and / or report components: generating an organized report template based on the selected report templates and / or report components; the report template is used to call and execute the battery algorithm template and / or battery algorithm component published in the algorithm library, and present the execution results in a visual manner.

[0037] The above method can meet the personalized needs of different users through the customized development of visual statistical report templates; based on different statistical report templates, a variety of statistical reports can be generated, which is more in line with actual business scenarios.

[0038] In a second aspect, the present application provides an algorithm development method, which is applied to an algorithm development platform, which includes an algorithm development system and an algorithm library; the method includes: based on the selected battery algorithm template and / or battery algorithm component in the algorithm library, developing a battery algorithm module through the algorithm development system; wherein, the algorithm template library in the algorithm library is used to store the battery algorithm template, and the algorithm component library in the algorithm library is used to store the battery algorithm component.

[0039] In a possible implementation of the second aspect, developing a battery algorithm module through an algorithm development system based on the selected battery algorithm template and / or battery algorithm component includes:

[0040] In response to the algorithm arrangement instruction, the battery algorithm template and / or the battery algorithm component are arranged to obtain an arranged battery algorithm template.

[0041] In a possible implementation of the second aspect, in response to the algorithm arrangement instruction, the battery algorithm template and / or the battery algorithm component are arranged to obtain an arranged battery algorithm template, including:

[0042] In response to the algorithm arrangement instruction, the selected battery algorithm template and / or battery algorithm component is arranged in series and / or in parallel to obtain an arranged battery algorithm template.

[0043] In a possible implementation of the second aspect, the selected battery algorithm template and / or battery algorithm component includes a battery algorithm uploaded by a user; and developing a battery algorithm module through an algorithm development system based on the selected battery algorithm template and / or battery algorithm component includes:

[0044] The battery algorithm to be debugged is debugged and verified, and the battery algorithm after successful verification is published in the algorithm library as a battery algorithm component or battery algorithm template; wherein the selected battery algorithm includes the battery algorithm template and / or battery algorithm component to be debugged; the battery algorithm template and / or battery algorithm component to be debugged includes the uploaded battery algorithm template and / or battery algorithm component, or the compiled battery algorithm template.

[0045] In a possible implementation of the second aspect, debugging and verifying the battery algorithm to be debugged includes:

[0046] Debug and verify the uploaded battery algorithm template and / or battery algorithm component based on preset input parameters, output parameters, and algorithm thresholds; and / or

[0047] The battery algorithm template obtained by programming is debugged and verified based on the adjustment of input parameters, output parameters, associated parameters and programming sequence.

[0048] In a possible implementation of the second aspect, after debugging and verifying the battery algorithm to be debugged, the method further includes:

[0049] Submit the successfully verified battery algorithm for review and release it in the algorithm library as a battery algorithm component or battery algorithm template, including:

[0050] The battery algorithm that has been successfully verified and reviewed will be published in the algorithm library as a battery algorithm component or battery algorithm template.

[0051] In a possible implementation of the second aspect, the algorithm development platform further includes a database; and developing a battery algorithm module through the algorithm development system further includes:

[0052] Call the battery indicator data in the database; develop the battery algorithm module based on the battery indicator data.

[0053] In a possible implementation of the second aspect, developing a battery algorithm module based on battery indicator data includes:

[0054] Based on the battery indicator data, the selected battery algorithm template and / or the battery algorithm component are debugged and verified.

[0055] In a possible implementation of the second aspect, developing a battery algorithm module using an algorithm development system further includes:

[0056] The target data is obtained during the development of the battery algorithm module, and the target data is stored in the database as battery indicator data.

[0057] In a possible implementation of the second aspect, the target data includes the first indicator data and / or the second indicator data; and obtaining the target data in developing the battery algorithm module includes:

[0058] Obtain first indicator data uploaded by a user; and / or obtain second indicator data obtained by executing a battery algorithm based on existing battery indicator data in a database.

[0059] In a possible implementation of the second aspect, obtaining second indicator data obtained by executing a battery algorithm based on existing battery indicator data in a database includes:

[0060] Based on the existing battery indicator data in the database, at least one of algorithm training, algorithm debugging, algorithm verification, algorithm testing, algorithm tuning and algorithm iteration is performed to obtain second indicator data.

[0061] In a possible implementation of the second aspect, obtaining second indicator data obtained by executing a battery algorithm based on existing battery indicator data in a database includes:

[0062] Based on the existing battery indicator data in the database, perform at least one of algorithm training, algorithm debugging, algorithm verification, algorithm testing, algorithm tuning and algorithm iteration to obtain an execution result; based on the execution result, update the existing battery indicator data in the database to obtain second indicator data.

[0063] In a possible implementation of the second aspect, based on the execution result, updating the existing battery indicator data in the database to obtain the second indicator data includes:

[0064] Based on the execution result, in response to a marking instruction input by the user, marking the existing battery indicator data in the database to obtain marked second indicator data; and / or

[0065] Based on the execution result, in response to the filtering instruction input by the user, the battery indicator data already in the database is filtered to obtain filtered second indicator data.

[0066] In a possible implementation of the second aspect, the selected battery algorithm template and / or battery algorithm component includes a battery algorithm uploaded by a user; and developing a battery algorithm module through an algorithm development system based on the selected battery algorithm template and / or battery algorithm component further includes:

[0067] Register the battery algorithm uploaded by the user and deploy the registered battery algorithm.

[0068] In a possible implementation of the second aspect, the algorithm development platform further includes a visual reporting system; and the method further includes:

[0069] Through the visual reporting system, the battery algorithm templates and / or battery algorithm components published in the algorithm library are called and executed, and the execution results are presented in a visual manner.

[0070] In a possible implementation of the second aspect, the method further includes:

[0071] In response to the report editing instruction input by the user, the report components in the report component library are edited to obtain an edited report template.

[0072] In a possible implementation of the second aspect, a visual reporting system is used to call and execute a battery algorithm template and / or battery algorithm component published in an algorithm library, and to present the execution results in a visual manner, including:

[0073] In response to the report execution instruction, based on the selected report template, the battery algorithm template and / or battery algorithm component in the algorithm library is called and executed, and the execution result is presented in a visual manner.

[0074] In a third aspect, the present application provides an algorithm development device, which is applied to an algorithm development platform. The algorithm development platform includes an algorithm development system and an algorithm library. The algorithm development device includes:

[0075] An acquisition unit, configured to acquire a battery algorithm template and / or a battery algorithm component;

[0076] a development unit, configured to develop a battery algorithm module through the algorithm development system based on the selected battery algorithm template and / or the battery algorithm component;

[0077] The algorithm template library in the algorithm library is used to store the battery algorithm templates, and the algorithm component library in the algorithm library is used to store the battery algorithm components.

[0078] In a possible implementation of the third aspect, the development unit includes an algorithm orchestration module;

[0079] The algorithm arrangement module is used to arrange the battery algorithm template and / or battery algorithm component in response to the algorithm arrangement instruction to obtain the arranged battery algorithm template.

[0080] In a possible implementation of the third aspect, the algorithm arrangement module is further used to arrange the selected battery algorithm template and / or battery algorithm component in series and / or parallel in response to the algorithm arrangement instruction to obtain the arranged battery algorithm template.

[0081] In a possible implementation of the third aspect, the development unit further includes a publishing module;

[0082] The publishing module is used to debug and verify the battery algorithm to be debugged, and publish the successfully verified battery algorithm as a battery algorithm component or battery algorithm template in the algorithm library; wherein, the selected battery algorithm includes the battery algorithm template and / or battery algorithm component to be debugged; the battery algorithm template and / or battery algorithm component to be debugged includes the uploaded battery algorithm template and / or battery algorithm component, or the compiled battery algorithm template.

[0083] In a possible implementation of the third aspect, the publishing module is further used to debug and verify the uploaded battery algorithm template and / or battery algorithm component based on preset input parameters, output parameters and algorithm thresholds; and / or debug and verify the arranged battery algorithm template based on the adjustment of input parameters, output parameters, associated parameters and arrangement order.

[0084] In a possible implementation of the third aspect, the publishing module is further configured to submit the successfully verified battery algorithm for review and publish the successfully verified and reviewed battery algorithm as a battery algorithm component or a battery algorithm template in the algorithm library.

[0085] In a possible implementation of the third aspect, the algorithm development platform further includes a database; the development unit is further configured to call battery indicator data in the database; and develop the battery algorithm module based on the battery indicator data.

[0086] In a possible implementation of the third aspect, the publishing module in the development unit is further configured to debug and verify the selected battery algorithm template and / or battery algorithm component based on the battery indicator data.

[0087] In a possible implementation of the third aspect, the development unit further includes a data recovery module;

[0088] The data recovery module is used to obtain target data during the development of the battery algorithm module and store the target data as battery indicator data in the database.

[0089] In a possible implementation of the third aspect, the target data includes first indicator data and / or second indicator data; the data recovery module is also used to obtain the first indicator data uploaded by the user; and / or obtain the second indicator data obtained by executing the battery algorithm based on the battery indicator data already in the database.

[0090] In a possible implementation of the third aspect, the data recovery module is further used to perform at least one of algorithm training, algorithm debugging, algorithm verification, algorithm testing, algorithm tuning and algorithm iteration based on the battery indicator data already in the database to obtain second indicator data.

[0091] In a possible implementation of the third aspect, the data recovery module is further used to perform at least one of algorithm training, algorithm debugging, algorithm verification, algorithm testing, algorithm tuning and algorithm iteration based on the battery indicator data already in the database to obtain an execution result; based on the execution result, the battery indicator data already in the database is updated to obtain second indicator data.

[0092] In a possible implementation of the third aspect, the data recovery module is further configured to:

[0093] Based on the execution result, in response to the marking instruction input by the user, the battery indicator data already in the database is marked to obtain the marked second indicator data; and / or based on the execution result, in response to the filtering instruction input by the user, the battery indicator data already in the database is filtered to obtain the filtered second indicator data.

[0094] In a possible implementation of the third aspect, the selected battery algorithm template and / or the battery algorithm component includes a battery algorithm uploaded by a user; the development unit further includes a registration module and a deployment module;

[0095] The registration module is used to register the battery algorithm uploaded by the user; the deployment module is used to deploy the registered battery algorithm.

[0096] In a possible implementation of the third aspect, the algorithm development platform further includes a visual reporting system;

[0097] The development unit is also used to call and execute the battery algorithm templates and / or battery algorithm components published in the algorithm library through a visual reporting system, and present the execution results in a visual manner.

[0098] In a possible implementation of the third aspect, the development unit further includes a report compilation module;

[0099] The report editing module is used to edit the report components in the report component library in response to the report editing instruction input by the user to obtain the edited report template.

[0100] In a possible implementation of the third aspect, the development unit further includes a report generation module;

[0101] The report generation module is used to call and execute the battery algorithm template and / or battery algorithm component in the algorithm library in response to the report running instruction based on the selected report template, and present the execution result in a visual manner.

[0102] In a fourth aspect, the present application provides an electronic device comprising a memory and a processor, wherein the memory stores a computer program, and the processor implements the steps of any one of the methods described in the second aspect when executing the computer program.

[0103] In a fifth aspect, the present application provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the steps of any one of the methods in the second aspect.

[0104] In a sixth aspect, the present application provides a computer program product, which, when executed on an electronic device, enables the electronic device to execute the steps of any one of the methods described in the second aspect above.

[0105] It can be understood that the beneficial effects of the second to sixth aspects mentioned above can be found in the relevant description of the first aspect mentioned above, and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0106] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the following briefly introduces the drawings required for use in the embodiments or the description of the prior art. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0107] FIG1 is a schematic diagram of the architecture of the algorithm development platform provided in an embodiment of the present application;

[0108] FIG2 is a functional schematic diagram of an algorithm development system provided in an embodiment of the present application;

[0109] FIG3 is a functional schematic diagram of an algorithm development system provided by another embodiment of the present application;

[0110] FIG4 is a functional schematic diagram of an algorithm development system provided by another embodiment of the present application;

[0111] FIG5 is a schematic diagram of the architecture of the algorithm development platform provided in an embodiment of the present application;

[0112] FIG6 is a functional schematic diagram of an algorithm development system provided by another embodiment of the present application;

[0113] FIG7 is a schematic diagram of the algorithm arrangement provided in an embodiment of the present application:

[0114] FIG8 is a schematic diagram of an algorithm arrangement interface provided in an embodiment of the present application;

[0115] FIG9 is a functional schematic diagram of an algorithm development system provided by another embodiment of the present application;

[0116] FIG10 is a schematic diagram of the architecture of the algorithm development platform provided in an embodiment of the present application;

[0117] FIG11 is a functional schematic diagram of an algorithm development system provided by another embodiment of the present application;

[0118] FIG12 is a functional schematic diagram of an algorithm development system provided by another embodiment of the present application;

[0119] FIG13 is a schematic diagram of a data recovery function provided in an embodiment of the present application;

[0120] FIG14 is a schematic diagram of an interface providing a data set management function according to an embodiment of the present application;

[0121] FIG15 is a schematic diagram of an interface of an algorithm development platform provided in an embodiment of the present application;

[0122] FIG16 is a schematic diagram of an interface of an algorithm development platform provided in an embodiment of the present application;

[0123] FIG17 is a schematic diagram of the architecture of the algorithm development platform provided in an embodiment of the present application;

[0124] FIG18 is a schematic diagram of the architecture of an algorithm development platform provided in another embodiment of the present application;

[0125] FIG19 is a schematic diagram of an interface of a visual report provided in an embodiment of the present application;

[0126] FIG20 is a schematic diagram of the detailed architecture of an algorithm development platform provided in another embodiment of the present application;

[0127] FIG21 is a schematic diagram of the overall implementation process of the algorithm development method provided in an embodiment of the present application;

[0128] FIG22 is a schematic diagram of an implementation flow of an algorithm development method according to an embodiment of the present application;

[0129] FIG23 is a schematic structural diagram of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0130] The following embodiments of the technical solution of the present application will be described in detail with reference to the accompanying drawings. The following embodiments are only used to more clearly illustrate the technical solution of the present application and are therefore only examples and are not intended to limit the scope of protection of the present application.

[0131] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by those skilled in the art to which this application belongs; the terms used herein are only for the purpose of describing specific embodiments and are not intended to limit this application; the terms "including" and "having" and any variations thereof in the specification and claims of this application and the above-mentioned figure descriptions are intended to cover non-exclusive inclusions.

[0132] In the description of the embodiments of this application, the technical terms "first" and "second" are used only to distinguish different objects and should not be understood to indicate or imply relative importance or implicitly specify the quantity, specific order, or primary and secondary relationship of the indicated technical features. In the description of the embodiments of this application, the meaning of "plurality" is more than two, unless otherwise clearly and specifically defined.

[0133] References herein to "embodiments" mean that a particular feature, structure, or characteristic described in connection with the embodiments may be included in at least one embodiment of the present application. The appearance of this phrase in various places in the specification does not necessarily refer to the same embodiment, nor does it constitute an independent or alternative embodiment that is mutually exclusive of other embodiments. It is understood, both explicitly and implicitly, by those skilled in the art that the embodiments described herein may be combined with other embodiments.

[0134] In the description of the embodiments of this application, the term "and / or" is simply a description of the association relationship between associated objects, indicating that three relationships can exist. For example, A and / or B can represent the following three situations: A exists alone, A and B exist simultaneously, and B exists alone. In addition, the character " / " in this document generally indicates that the associated objects are in an "or" relationship.

[0135] In the description of the embodiments of the present application, the term "multiple" refers to more than two (including two). Similarly, "multiple groups" refers to more than two groups (including two groups), and "multiple pieces" refers to more than two pieces (including two pieces).

[0136] In the description of the embodiments of the present application, the technical terms "center", "longitudinal", "lateral", "length", "width", "thickness", "up", "down", "front", "back", "left", "right", "vertical", "horizontal", "top", "bottom", "inside", "outside", "clockwise", "counterclockwise", "axial", "radial", "circumferential", etc., indicating the orientation or position relationship, are based on the orientation or position relationship shown in the accompanying drawings, and are only for the convenience of describing the embodiments of the present application and simplifying the description, and do not indicate or imply that the device or element referred to must have a specific orientation, be constructed and operated in a specific orientation, and therefore cannot be understood as a limitation on the embodiments of the present application.

[0137] In the description of the embodiments of the present application, unless otherwise expressly specified or limited, technical terms such as "installed," "connected," "connected," and "fixed" should be understood in a broad sense. For example, they can refer to fixed connections, detachable connections, or integration; mechanical connections or electrical connections; direct connections or indirect connections through an intermediate medium; internal connections between two components or interactions between two components. Those skilled in the art can understand the specific meanings of the above terms in the embodiments of the present application based on specific circumstances.

[0138] With the continuous development of the new energy field, power batteries have also been widely used in this field. In order to ensure the safe and stable application of batteries, it is necessary to use a battery management system to monitor the batteries in real time and manage the batteries in the new energy field.

[0139] Battery management relies on various battery algorithms to estimate and analyze battery status and performance. As the application scenarios of new energy batteries become increasingly complex, the requirements for stable, accurate, and efficient battery management are also becoming increasingly stringent.

[0140] However, the traditional battery algorithm development process is cumbersome and has a long development cycle. For example, a large number of people are needed in the early stage to determine the target objects and acceptance criteria; and then conduct preliminary research on the algorithm, including: the formation of algorithm logic, algorithm documentation, interface form, test data set determination, and task decomposition based on the development cycle; then, based on a large number of experiments, the battery algorithm is developed, tested and optimized in stages, and algorithm integration, test report formation, vulnerability repair, problem feedback and subsequent delivery work are carried out; therefore, the entire development process requires a lot of manpower, material resources and time, which makes the development efficiency of the battery algorithm low, seriously affecting the efficiency of battery management.

[0141] Moreover, the capabilities of the main bodies developing battery algorithms (merchants on the B-side or consumers on the C-side) vary widely. Even if an excellent battery operator is developed, it is just an information island, limited by insufficient data sets for algorithm verification or lack of joint debugging and verification with related operators, making it impossible to solve practical problems in battery management in a closed loop.

[0142] To address the above shortcomings, the embodiments of the present application provide a shareable low-code algorithm development platform that integrates algorithm registration, deployment, debugging, verification, release, and upgrade, which is used to accelerate the development process of battery algorithms so that they can be quickly applied to various application scenarios of battery management and improve battery management efficiency.

[0143] Please refer to Figure 1, which is a schematic diagram of the architecture of the algorithm development platform provided in an embodiment of the present application. As shown in Figure 1, the algorithm development platform 10 may include an algorithm development system 101 and an algorithm library 102. The algorithm library 102 includes at least one of an algorithm template library and an algorithm component library. The algorithm template library is used to store battery algorithm templates, and the algorithm component library is used to store battery algorithm components. The algorithm development system 101 is configured to develop battery algorithm modules based on selected battery algorithm templates and / or battery algorithm components.

[0144] In some embodiments, the selected battery algorithm template and battery algorithm component can be a battery algorithm stored in the algorithm library 102 or a battery algorithm uploaded by a user. The battery algorithm stored in the algorithm library 102 can be an algorithm provided by the algorithm development platform or an algorithm approved and published by the algorithm development platform; the battery algorithm uploaded by the user can be an algorithm to be debugged or verified. Thus, the algorithm development system 101 of the algorithm development platform 10 can further develop the battery algorithm uploaded by the user or the published and stored battery algorithm.

[0145] Exemplarily, the battery algorithm component can be various basic battery algorithms or models required for different battery application scenarios and training tasks, such as the ampere-hour integration algorithm, open circuit voltage algorithm and Kalman filter algorithm for evaluating the battery state of charge (SOC). The above algorithms can be encapsulated as battery algorithm components and stored in the algorithm component library in the algorithm library 102.

[0146] Exemplarily, the battery algorithm template can be various types of battery algorithms or models based on battery algorithm components or existing battery algorithm template combinations. For example, a battery algorithm template for evaluating battery consistency can include battery algorithms corresponding to multiple battery indicators: a battery state of charge (SOC) estimation algorithm, a battery state of health (SOH) estimation algorithm, and a battery state of function (SOF) estimation algorithm. The estimation algorithms of various battery indicators can be packaged and combined as a battery algorithm template for evaluating battery consistency and stored in the algorithm template library in the algorithm library 102. In addition, the battery algorithm template can also be packaged as a component for storage.

[0147] The embodiments of the present application may include but are not limited to the existence forms of the above-mentioned battery algorithms; the battery algorithm template and the battery algorithm component only differ in their existence forms. For the convenience of description, the battery algorithm template and the battery algorithm component may both be referred to as battery algorithms.

[0148] Exemplarily, the battery algorithm component or battery algorithm template in the algorithm library 102 can be a battery algorithm already available on the algorithm development platform 10, or a battery algorithm uploaded and approved by other users (such as B-end users or C-end users).

[0149] Exemplarily, the algorithm development system 101 develops a battery algorithm module based on a selected battery algorithm template or battery algorithm component, and can develop a battery algorithm through low code based on the selected battery algorithm template or battery algorithm component.

[0150] Exemplarily, the development of the battery algorithm module may include secondary rapid development based on an existing battery algorithm, or further upgrading or updating the existing battery algorithm; thereby, rapid and convenient development can be achieved based on the selected battery algorithm, thereby coping with more complex and diverse battery application scenarios, improving the development efficiency of the battery algorithm, and improving the efficiency of battery management based on the battery algorithm.

[0151] In some embodiments, in the battery algorithm module development, the algorithm development system 101 is also configured with functions for battery algorithm module development including: the function of orchestrating the selected battery algorithm template and / or battery algorithm components; that is, the algorithm development system 101 is configured with an orchestration function.

[0152] As shown in Figure 2, the algorithm development system 101 arranges the selected battery algorithm templates and / or battery algorithm components in the algorithm library 102 to obtain a battery algorithm template, and continues to store the battery algorithm template in the algorithm library 102, such as the algorithm template library stored in the algorithm library 102.

[0153] Exemplarily, the process of the algorithm development system 101 performing the arrangement processing may be to combine the battery algorithm components and / or battery algorithm templates in series or in parallel, that is, to use the output of one battery algorithm as the input of the next battery algorithm.

[0154] As shown in FIG7 , corresponding input parameters are set, such as input parameter 1 and input parameter 2, as inputs to battery algorithm component 1 (and / or battery algorithm template 1) and battery algorithm component 2 (and / or battery algorithm template 2), respectively. The outputs of battery algorithm component 1 (and / or battery algorithm template 1) and battery algorithm component 2 (and / or battery algorithm template 2) are used as inputs to battery algorithm component 3 (and / or battery algorithm template 3), and the outputs of battery algorithm component 3 (and / or battery algorithm template 3) are used as inputs to battery algorithm component 4 (and / or battery algorithm template 4). Each battery algorithm in the combination is executed to obtain the final output result; the output result can be used to monitor and evaluate battery performance or status. Thus, the entire combination after the arrangement process can be used as a new battery algorithm template, encapsulated and stored in the algorithm template library in the algorithm library 102.

[0155] Please refer to Figure 8, which is a schematic diagram of the interface of the algorithm arrangement provided in an embodiment of the present application. The algorithm development platform 10 can be a web page or application app on an electronic device. As shown in Figure (a) in Figure 8, the display interface after the algorithm development platform 10 is started can be displayed as a low-code development platform. The display interface can include menu items such as "Template Library", "Component Library", "Dataset", "My Application" and "Developer Center", each of which supports different functions.

[0156] Exemplarily, in response to the user clicking on the "My Application" menu, the display interface shown in Figure 8 (a) is entered. The display interface may include controls corresponding to components of various categories, such as "general components", "special components" and user-developed components, etc.; among them, "general components" can be various components used for statistics, "special components" can be various battery algorithm components, and "user-developed components" can include algorithm components and other types of components.

[0157] For example, on the display interface shown in FIG8 (a), a user is received to click on a battery algorithm component under "Specialized Components", such as operation 1 corresponding to the "Battery Fault Diagnosis" component; as shown in FIG8 (b), in response to the instruction, the algorithm development platform 10 displays a specific battery algorithm component at the next level of the "Battery Fault Diagnosis" category, such as the "Cell Voltage Outlier Diagnosis" component. The algorithm development platform 10 then receives an instruction for the specific battery algorithm component, such as operation 2 corresponding to the "Cell Voltage Outlier Diagnosis" component. Operation 2 can be an operation of dragging the selected component to the next display box, or a new operation of dragging the selected component to the next display box; in response to the operation, the selected component is created in the next display box. Correspondingly, the algorithm development platform 10 receives instructions for other components, such as operation 3 corresponding to the "output diagnosis results" component; operation 3 can be an operation of dragging the component to the next display box after selecting it, or an operation of creating a new component in the next display box by dragging it after selecting it; in response to the instruction, the selected component is created in the next display box.

[0158] Then, after creating a new component in the next display box, a connection relationship between multiple components can be established, and multiple battery algorithm components can be arranged based on the connection relationship to form a new battery algorithm template; at the same time, model information corresponding to the new battery algorithm template is generated. The model information may include model name, creation time, update time, and original model profile, provider, and other information. After creating a new component in the next display box, "Save" and "Run" controls can be displayed; in response to the user clicking the "Save" control input instruction, the formed battery algorithm template and the corresponding model information can be saved, for example, saved to the template library; in response to the user clicking the "Run" control input instruction, the arranged battery algorithm template can be run in the actual application scenario, and the operation results corresponding to the actual application scenario can be obtained, such as using the cell voltage outlier diagnosis model to diagnose the vehicle to be tested, and obtaining the diagnosis results of the vehicle to be tested.

[0159] Exemplarily, the algorithm arrangement instructions received by the algorithm development platform 10 may include: in the display interface shown in Figure (b) of Figure 8, receiving an instruction to select and drag the algorithm component to the next display box, and an instruction to establish a connection between the selected algorithm component.

[0160] It is understandable that in the display interface shown in FIG8 , the component types displayed under the “My Application” menu may include algorithm components and report components. The algorithm components here may be components obtained by encapsulating the above-mentioned battery algorithm components or battery algorithm templates. For ease of description, the components in this display interface are collectively referred to as algorithm components or report components. In the display interface shown in FIG8 , the template library may include an algorithm template library, and the component library may include an algorithm component library; in the background of the algorithm development platform, the algorithm template library and the algorithm component library may belong to the algorithm library; through the menu items of the template library and the component library provided by the algorithm development platform 10 in the display interface, the battery algorithm template and the battery algorithm component in the algorithm library may be called respectively.

[0161] It should also be understood that the content displayed on the above display interface can be set as needed, and the display method of various components can also be set according to the actual application scenario. The above display method is only an example. The embodiment of the present application is intended to illustrate that the platform can support visual orchestration of algorithm components, reduce the difficulty and complexity of battery algorithm development, improve the development efficiency of battery algorithms, and thereby improve the management efficiency of battery services. The layout of the display interface includes but is not limited to the above display method.

[0162] Through the above method, the battery algorithm development platform provided by the embodiment of the present application can support low-code secondary development of battery algorithms. By receiving algorithm orchestration instructions generated by selection and dragging operations, the selected and verified battery algorithms (battery algorithm components and / or battery algorithm templates) in the algorithm library are dragged onto the algorithm orchestration canvas, and the data set is directly loaded. The input and output parameters and algorithm thresholds of the battery algorithm are configured to complete the development of the battery algorithm; based on the numerous battery algorithms publicly released by the algorithm development platform 10, more advanced battery algorithms are developed to manage more complex battery services, and the closed loop realizes the development of battery algorithms based on complex computing logic.

[0163] Due to the traditional battery algorithm process, the average time required for each algorithm development is about 7 days; while using the low-code secondary development platform in the embodiment of this application to develop a battery algorithm, it is only necessary to drag the verified battery algorithm template or battery algorithm component in the component library to the algorithm arrangement canvas to complete the algorithm development process. The entire development time can be controlled within one minute; therefore, the algorithm development efficiency of the embodiment of this application has been exponentially improved (it can be improved by about times the development speed), shortening the entire development cycle of the battery algorithm and significantly improving the development efficiency of the battery algorithm.

[0164] In some embodiments, as shown in FIG3 , the algorithm development system 101 configured to develop a battery algorithm module further includes an algorithm publishing function. That is, the algorithm development system 101 is also configured with an algorithm publishing function. The algorithm publishing function supports debugging and verification of a battery algorithm to be debugged, and publishes a successfully verified battery algorithm as a battery algorithm component or battery algorithm template in the algorithm library.

[0165] Exemplarily, the selected battery algorithm includes a battery algorithm template and / or battery algorithm component to be debugged; the battery algorithm template and / or battery algorithm component to be debugged includes an uploaded battery algorithm template and / or battery algorithm component, or an orchestrated battery algorithm template.

[0166] In some embodiments, the debugging and verification of the battery algorithm to be debugged are as follows: debugging and verification are performed on the uploaded battery algorithm template and / or battery algorithm component based on preset input parameters, output parameters and algorithm thresholds; and / or debugging and verification is performed on the arranged battery algorithm template based on the adjustment of input parameters, output parameters, associated parameters and arrangement order.

[0167] Exemplarily, the battery algorithm debugging process includes debugging the uploaded battery algorithm based on preset debugging parameters and debugging tasks, and adjusting the battery algorithm logic based on the debugging results to improve algorithm accuracy and operating efficiency. When the debugging results meet preset conditions, such as the algorithm accuracy meets preset requirements, the debugged battery algorithm is verified using other verification data to verify the feasibility and correctness of the battery algorithm. The verified battery algorithm is then published to the algorithm library 102 as a battery algorithm component or battery algorithm template.

[0168] In some embodiments, as shown in Figure 4, the algorithm publishing function of the algorithm development system 101 also supports: submitting the battery algorithm for review after successful verification; accordingly, publishing the battery algorithm after successful verification as a battery algorithm component or battery algorithm template in the algorithm library 102 is: publishing the algorithm that has been successfully verified and passed the review as a battery algorithm component or battery algorithm template in the algorithm library 102.

[0169] For example, only after the battery algorithm has been reviewed and approved by the algorithm development platform can it be publicly released on the platform for use by other users to ensure the availability and reliability of the battery algorithm.

[0170] It is understandable that the battery algorithm uploaded by the user can be a separate battery algorithm (battery algorithm component), such as an ampere-hour integration algorithm for evaluating the battery SOC, or it can be a battery algorithm template to be debugged formed by the arrangement and combination of multiple separate battery algorithms, such as a battery algorithm template for battery consistency evaluation.

[0171] The algorithm development platform provided in the embodiment of the present application can support the debugging and verification of the battery algorithm, reduce the time for preparing and organizing test specifications, test cases and test reports during the debugging process, and greatly improve the debugging and verification efficiency of the battery algorithm; at the same time, after verification and review, the probability of errors and security vulnerabilities in the battery algorithm is reduced, the reliability, availability and compliance of the battery algorithm are guaranteed, and it is ensured that the battery algorithm can normally support applications and meet user requirements.

[0172] In some embodiments, as shown in FIG5 , the algorithm development platform 10 further includes a database 103 . The database 103 contains battery indicator data that supports the algorithm development system 101 to call. The database 103 is used to provide data support for the development of the battery algorithm module.

[0173] Exemplarily, the database 103 provides data sets that support debugging and verification of various battery algorithms, and manages various instance data involved in algorithm execution.

[0174] In the above manner, the algorithm development platform 10 debugs and verifies the various uploaded battery algorithms (battery algorithm components and / or battery algorithm templates) or the battery algorithm templates obtained after arrangement through the data sets and various instance data of the database 103, which can reduce the preparation time for test cases and test data sets during the debugging and verification process. At the same time, the database 103 can also meet the requirements for data diversity in the debugging and verification process; through the rich and diverse database 103, in the development process of the battery algorithm module, the iteration efficiency of the battery algorithm such as the algorithm model / analysis model / prediction model is exponentially improved, thereby improving the efficiency of battery algorithm development and optimization.

[0175] In some embodiments, as shown in FIG6 , the algorithm publishing function further supports: debugging and verifying the compiled battery algorithm template, and publishing the successfully verified battery algorithm template in the algorithm library 102 .

[0176] Accordingly, as shown in FIG9 , the database 103 is also used to provide data support for debugging and verifying the compiled battery algorithm template; and to submit the battery algorithm template for review after successful verification; and to publish the battery algorithm template that has been successfully verified and passed the review in the algorithm library 102 .

[0177] For example, based on the same implementation principles as the uploaded battery algorithm, and with the data support of database 103, the compiled algorithm template is also debugged, verified, reviewed, and released. The compiled battery algorithm template is directly loaded into the dataset in database 103, and the operator input and output parameters and algorithm thresholds are configured to complete the debugging and verification of the battery algorithm template.

[0178] Through the above method, for the battery algorithm template that is secondary developed after the arrangement, the original battery algorithm used for the arrangement (the battery algorithm component or battery algorithm template in the algorithm library 102) is released only after being debugged and verified. The debugging and verification process of the arranged battery algorithm template can only be targeted at joint debugging and algorithm parameter adjustment, which reduces the dependence on test specifications, test cases and test reports, and greatly improves the efficiency of algorithm testing and verification.

[0179] Since the debugging and verification cycle of the traditional battery algorithm development process generally takes about 7 days, through the embodiment of the present application, the original battery algorithms used for programming are all debugged and verified. The debugging and verification work after the algorithm programming only involves joint debugging and algorithm parameter adjustment. The entire test verification time can be controlled to be completed within 5 minutes; therefore, the algorithm testing and verification efficiency has been exponentially improved, and the improvement rate can be about times.

[0180] In some embodiments, the algorithm development system 101 includes a data recovery function for developing battery algorithm modules. As shown in FIG10 , the database 103 not only provides data support for debugging and verifying uploaded and compiled battery algorithms, but also acquires target data during battery algorithm module development and stores the target data as battery indicator data in the database 103 .

[0181] Exemplarily, the above data recovery function supports: obtaining first indicator data uploaded by the user and / or second indicator data obtained by executing a battery algorithm based on existing battery indicator data in the database 103, and using the first indicator data and / or the second indicator data as target data.

[0182] Exemplarily, as shown in FIG11 , the second indicator data may include: data generated during the debugging and verification process of the uploaded battery algorithm and the programmed battery algorithm template; and as shown in FIG12 , it may also include data generated in actual applications when the published algorithm is applied to the battery service system.

[0183] For example, as shown in FIG13 , the first indicator data in the database 103 may include original data or optimized data sets provided by the algorithm development platform, B-end and C-end developers and users in the market.

[0184] Accordingly, when these data are used as input to the battery algorithm, the results obtained after calculation may not meet (or partially meet) the expected values ​​of the battery algorithm. Therefore, more data sets that can characterize the characteristics of the data are adjusted or simulated based on the calculation results and incorporated into the calculation of the battery algorithm again.

[0185] Exemplarily, as shown in FIG13 , the data generated during the debugging and verification process of the uploaded battery algorithm and the programmed battery algorithm template may be data obtained by performing at least one of algorithm training, algorithm debugging, algorithm verification, algorithm testing, algorithm tuning, and algorithm iteration based on the existing battery indicator data in the database.

[0186] In one possible implementation, based on the existing battery indicator data in the database, at least one of algorithm training, algorithm debugging, algorithm verification, algorithm testing, algorithm tuning and algorithm iteration is performed, and the obtained data is directly fed back to the database as a new data set as the second indicator data; in another possible implementation, according to the execution result obtained by performing at least one of algorithm training, algorithm debugging, algorithm verification, algorithm testing, algorithm tuning and algorithm iteration, the input data in the database is updated to obtain an updated data set as the second indicator data.

[0187] In some embodiments, the data recovery function also supports: based on the execution result, in response to the marking instruction input by the user, marking the battery indicator data already in the database to obtain the marked second indicator data; and / or based on the execution result, in response to the filtering instruction input by the user, filtering the battery indicator data already in the database to obtain the filtered second indicator data.

[0188] Exemplarily, updating the data in the database based on the execution results may include: marking or filtering the data in the database to obtain data for different test cases, such as a test data set for a battery failure case, for analyzing whether the battery is operating normally; it may also include analyzing or eliminating the data in the database, so that the data in the database can be continuously optimized to provide a more reliable and more adaptable data set for the development of the battery algorithm module.

[0189] For example, after successful battery algorithm verification, it is reviewed and released. As shown in Figure 12, the battery algorithms (battery algorithm components and / or battery algorithm templates) in the algorithm library 102 can also be applied to the battery service system. During the application of the algorithm in the battery service system, the data generated can be further fed back to the database 103 as battery indicator data.

[0190] As shown in FIG13 , the battery algorithm components and / or battery algorithm templates (e.g., Algorithms A to N) that have passed the review can be split and decoupled for deployment to form a variety of product forms. They can be integrated into other service systems in the form of an Application Programming Interface (API) or a Software Development Kit (SDK). They can also be provided as algorithm services for systems such as Platform as a Service (PAAS) or Software as a Service (SAAS) in wired or wireless form, or integrated into service systems such as PAAS and SAAS in the form of components; thereby, the development flexibility and service scalability of the battery algorithm are very high. Accordingly, the data generated during the application algorithm service process of each system can also be fed back to the database 103.

[0191] It should be noted that the above-mentioned battery algorithm, after passing the review, provides algorithm services for other services for illustrative purposes only, including but not limited to the above-mentioned methods.

[0192] Through the above method, the original data undergoes multiple internal loops, continuously analyzes data features, and undergoes layer-by-layer training and optimization to obtain a new data set. This new data set is then further incorporated into the calculation of the battery algorithm to complete the debugging and verification of the battery algorithm, achieving dynamic adaptive loop optimization of data between the database and algorithm development. This breaks the limitation of related technologies that software systems based on complex calculations cannot quickly deduce and refresh algorithm models; based on a continuously optimized database, the iterative efficiency of algorithm models / analysis models / prediction models can be exponentially improved, achieving battery algorithm optimization while greatly improving the efficiency of algorithm debugging and verification.

[0193] Since the optimization iteration cycle of the traditional battery algorithm takes about 14 days; the optimization iteration of the battery algorithm achieved by the embodiment of the present application only requires replacing the battery algorithm component / template or adjusting the connection order of the battery algorithm component / template on the battery algorithm arrangement canvas, and then loading the data set, configuring the input and output parameters and the battery algorithm threshold, the iterative optimization of the battery algorithm can be completed; the iterative optimization time of the entire algorithm can be controlled to be completed within one minute; therefore, the algorithm iteration efficiency can be exponentially improved, and the improvement rate can reach about times.

[0194] In one possible implementation, the algorithm development platform 10 supports access and storage of multiple application data. As shown in FIG14 , the display interface of the algorithm development platform 10 may include a “Developer Center” menu item and a “Dataset” menu item. As shown in FIG14 (a), the display interface may include various categories of data sets, such as general data, special data, and user-uploaded data. Among them, general data may include data sets for evaluating various general performance indicators of batteries, such as SOH evaluation data sets, SOP evaluation data sets, and SOF evaluation data sets; special data may include data required for test cases for battery application scenarios, such as failure case data sets, fault diagnosis data sets, and safety detection data sets.

[0195] The display interface shown in Figure 14 (a) can receive instructions entered by the user by clicking the "Create Dataset" menu to create a new dataset, receive real-time data uploaded by the user or historical data imported offline, and generate corresponding dataset information; in addition, based on the selected existing category of dataset, it can also receive instructions entered by the user by clicking the "Update Dataset" control to update the selected dataset; when updating the dataset, the data content or dataset information of the dataset can be updated.

[0196] As shown in Figure 14(b), the display interface corresponding to the dataset control may include a "manage" control for operating the dataset. This display interface receives user input by clicking on the "manage" control, allowing management of various instance data in the database participating in the algorithm calculation, such as deleting or reclassifying the dataset.

[0197] It should be noted that the above-mentioned users include but are not limited to administrative users of the low-code development platform, B-end and C-end developers in the market, users such as users; the form in which the low-code development platform receives user instructions and the actions in response to the instructions include but are not limited to the above-mentioned implementation methods, and can also be other operation methods, such as for a selected dataset category, receiving a double-click on a dataset of that category and executing an action to update the dataset; or in the interface for managing datasets, receiving an instruction to select a dataset and drag it to the delete control and executing an action to delete the dataset, etc. The classification form of the above-mentioned datasets is also only illustrative, and can also be displayed in other classification forms and interface layout modes, including but not limited to the above-mentioned methods.

[0198] Through this approach, the algorithm development platform can process both real-time data from IoT device sensors and time-series data imported offline, based on dynamic, adaptive loop optimization between algorithm development and database data, as well as access to real-time data or offline historical data import. This adaptive loop optimization allows for analysis of both real-time and historical data. Multi-application data access and storage provide a rich set of application scenarios and massive data support for battery algorithm development, laying the foundation for low-code development platforms to deliver more universal, high-precision algorithms.

[0199] In some embodiments, the battery algorithm module development function configured by the algorithm development system 101 further includes: a function of registering the uploaded battery algorithm, and a function of deploying the registered battery algorithm.

[0200] As shown in Figures 15 and 16, the display interface of the algorithm development platform provided in the embodiment of the present application, in the "Developer Center" interface of the display interface, supports the management of algorithm components, algorithm templates, and report templates built by developers, as well as the completion of algorithm registration, deployment, debugging, verification, testing, approval, release and upgrade operations.

[0201] As shown in Figure 15 (a), the display interface corresponding to the "Developer Center" may include controls for creating various battery algorithm components and controls for registering battery algorithm components.

[0202] Exemplarily, in response to the user clicking the instruction input by the "Create Algorithm Component" control, an interface for uploading a battery algorithm component is provided, and the battery algorithm component uploaded by the user is received based on the interface; instructions for registering and deploying the battery algorithm component are continued to be received, or after receiving the uploaded battery algorithm component, the algorithm registration and deployment operations are directly performed; and then the deployed battery algorithm can be debugged and verified by calling the data set of the database, and after the verification is passed, it can be reviewed and published in the component library.

[0203] Accordingly, the display interface corresponding to the "Component Library" shown in Figure 15 (b) includes controls for managing algorithm components; this display interface may include a variety of battery algorithm components, such as components of the SOH evaluation algorithm, components of the SOP evaluation algorithm, and components of the SOF evaluation algorithm. In this display interface, an instruction to delete or update a selected battery algorithm component may be received, and the operation of deleting or updating the selected battery algorithm component may be executed, thereby realizing the management of different categories of battery algorithm components.

[0204] It should be noted that the above-mentioned battery algorithm components are separate battery algorithms and are essential elements for forming a complete algorithm, such as the ampere-hour integration algorithm for evaluating battery SOC.

[0205] As shown in FIG. 16 ( a ), the display interface corresponding to the “Developer Center” may include controls for creating various battery algorithm templates and controls for registering battery algorithm templates.

[0206] Exemplarily, in response to the user clicking the "Create Algorithm Template" control input instruction, an interface for uploading a battery algorithm template is provided, and based on the interface, the battery algorithm template uploaded by the user is received; instructions for registering and deploying the battery algorithm template are continued to be received, or after receiving the uploaded battery algorithm template, the algorithm registration and deployment operations are directly performed; and then the deployed battery algorithm can be debugged and verified by calling the data set in the database, and after the verification is passed, it can be reviewed and published in the template library. In addition, for the battery algorithm template obtained through arrangement, the data set in the database can also be called to debug and verify the arranged battery algorithm template, and after the verification is passed, it can be reviewed and published in the template library.

[0207] Accordingly, the display interface corresponding to the "Template Library," as shown in Figure 16(b), includes controls for managing algorithm templates. This display interface can include multiple battery algorithm templates, such as a battery consistency assessment template. This display interface can receive instructions to delete or update a selected battery algorithm template, and execute the deletion or update operation on the selected battery algorithm template, thereby enabling management of different categories of battery algorithm templates.

[0208] It should be noted that the user corresponding to the "Developer Center" on the display interface of the algorithm development platform can be the subject of self-developed battery algorithms (such as B-end or C-end developers). The low-code development platform receives instructions from developers to register self-developed algorithms through the developer center. Based on the algorithm orchestration capabilities of the low-code development platform, combined with battery algorithm templates or battery algorithm components released by other developers, a more powerful battery algorithm is formed. Then, based on the algorithm deployment, debugging, verification, testing, review and release process provided by the low-code development platform, the one-stop battery algorithm development process of the developer center is completed.

[0209] Through the above method, based on the implementation of this low-code development platform, it can be applied to the development of various complex algorithm applications in the field of battery research and development, providing unique and professional battery algorithm components and battery algorithm templates, filling the gap in battery algorithms in the field of low-code technology.

[0210] In some embodiments, as shown in FIG17 , the algorithm development platform 10 further includes a visualization reporting system 104 , which is configured to call and execute the selected battery algorithm template and / or battery algorithm component and present the execution results in a visual manner.

[0211] As shown in FIG. 18 , the algorithm development platform 10 may include an algorithm development system 101 , an algorithm library 102 , a database 103 , and a visualization reporting system 104 .

[0212] In some embodiments, the visual reporting system is configured with: the function of organizing the selected report templates and / or report components; the function of organizing the selected report templates and / or report components supports: generating an organized report template based on the selected report templates and / or report components; the report template is used to call and execute the battery algorithm template and / or battery algorithm component published in the algorithm library, and present the execution results in a visual manner.

[0213] Please refer to Figure 19, which is a schematic diagram of the interface for report compilation provided in an embodiment of the present application. As shown in Figure 19 (a), after the algorithm development platform 10 is started, the display interface can be displayed as a low-code development platform. The display interface can include menu items such as "Template Library", "Component Library", "Dataset", "My Applications", and "Developer Center", each of which supports different functions.

[0214] For example, in response to the user clicking on the "My Application" menu, a display interface as shown in Figure 19 (a) is entered, which may include controls corresponding to various categories of components, such as "general components", "special components" and user-developed components, etc. Among them, "general components" can be various components used for statistics, such as "pie charts", "bar charts", "line charts", "funnel charts", "tabs" and "text boxes".

[0215] For example, on the display interface shown in FIG. 19 (a), a user clicks on a "general component" and receives an instruction, such as operation 1 corresponding to the "general component". In response to the instruction, the algorithm development platform 10 displays the specific components for reporting statistics contained under the "general component". Then, as shown in FIG. 19 (b), on the canvas for creating a "general template for statistical report", the algorithm development platform 10 receives an instruction for the specific component, such as operation 2 corresponding to the "histogram" component. Operation 2 can be an operation of dragging the component to the next display frame (canvas) after selecting it, or an operation of creating a new component by dragging the component in the next display frame (canvas) after selecting it. In response to the operation, the selected component is newly created in the next display frame (canvas).

[0216] Correspondingly, the algorithm development platform 10 receives instructions for other components, such as operation 3 corresponding to the "text box" component; operation 3 can be an operation of dragging the component to the next display box (canvas) after selecting it, or an operation of creating a new component in the next display box (canvas) by dragging it after selecting it; in response to the instruction, the selected component is created in the next display box (canvas).

[0217] After a new report component is created in the next display box (canvas), the corresponding report template, such as a general statistical report template, is generated and displayed by receiving the user's instruction to click the "Save" or "Preview" control; at the same time, template information corresponding to the report template is generated, which may include template name, creation time, template introduction, creator and other information.

[0218] Accordingly, in actual applications, the corresponding algorithm execution results can be called through the created report template, and the algorithm execution results can be visualized using report templates based on various categories or required by users.

[0219] Exemplarily, before creating a report template, the algorithm development platform 10 can also respond to a creation instruction input by the user, pop up a control for selecting the report template type, for the user to select a template type, such as a general template, a special template, etc.; receive a user click on a general template or a special template, create a blank canvas for the report template and generate a report component for creating the report template on one side of the display box, thereby completing the creation of the report template based on the operation shown in Figure (b) of Figure 19.

[0220] It can be understood that in the display interface shown in Figure 19, the component types displayed in the "My Application" menu item may include algorithm components and report components. The report components here can be the above-mentioned basic component units (such as pie charts, bar charts, text boxes, etc.), or they can be report templates created and saved by basic component units based on user needs (that is, new report templates can be further compiled based on existing report templates) so as to be applicable to various complex and multiple practical application scenarios in battery management services; for ease of description, the components in this display interface are collectively referred to as algorithm components or report components.

[0221] For example, as shown in the display interface of Figure 15 (a), the display interface corresponding to the "Developer Center" may include a control for creating a report component; in response to the user clicking the instruction to create the report component, the corresponding report component is generated, so that more types of report components can be continuously developed based on the needs of actual applications. The report components shown here can be basic unit components, such as waveform graphs, stereograms and other basic components. As shown in the display interface of Figure 15 (b), the component library can also include report components, such as process components, text components and icon components; the display interface may include a control for managing the component library. By receiving the instruction of the user clicking the management control, the report components of the component library can be deleted or updated, so that the report components in the component library can be continuously upgraded and optimized, providing users with richer report components suitable for actual application scenarios.

[0222] For example, as shown in the display interface of Figure 16 (a), the template library may also include report templates. In the display interface corresponding to the "Developer Center", a control for creating a report template may be included; in response to the user clicking the instruction to create the report component, the display interface corresponding to the "My Application" control is entered, and based on the arrangement operation shown in Figure 19 (b), a corresponding report template is generated, so that more types of report templates can be continuously created and saved based on the needs of actual applications. As shown in the display interface of Figure 16 (b), the template library may also include report templates, such as general templates and special templates; the display interface may include a control for managing the template library, and by receiving the instruction of the user clicking the management control, the report template of the template library can be deleted or updated, so that the report templates in the component library can be continuously upgraded and optimized, providing users with richer report templates that are more suitable for actual application scenarios.

[0223] It can be understood that the content displayed on the above display interface can be set as needed, and the display method of various components and templates can also be set according to the actual application scenario. The above display method is only an example. The embodiment of the present application is intended to illustrate that the platform can support visual editing and processing of report components, so as to output statistical reports based on different battery application scenarios and battery algorithms to guide actual business or assist business decision-making; the layout of the display interface includes but is not limited to the above display method.

[0224] Through the above methods, the algorithm development platform 10 supports statistical reports based on different battery application scenarios and combined with battery algorithms to guide actual business operations or assist in business decision-making. The algorithm development platform supports user-defined report templates, so that statistical reports with different characteristics can be output based on different battery application scenarios. This low-code secondary development platform not only supports secondary development of battery algorithms, but also supports the custom development of visual statistical report templates to meet the personalized needs of various users in actual battery service application scenarios and improve battery management efficiency.

[0225] In the traditional battery algorithm development process, it takes nearly 80 days from the beginning of algorithm development to actual application and output of algorithm visualization report to launch two algorithms online. However, through the low-code development platform of the embodiment of this application, it can complete the launch of two battery algorithms and output visualization report within 10 minutes. This will exponentially improve the battery management efficiency, and the improvement rate can reach about times.

[0226] It should be noted that the component library and template library displayed in the display interface of the algorithm development platform 10 do not conflict with the aforementioned algorithm library and the algorithm component library and algorithm template library in the algorithm library. It is just that the definitions and the ownership of various components and templates are different. For example, the component library displayed on the display interface may include an algorithm component and a report component. The algorithm component corresponds to the battery algorithm (battery algorithm component) in the algorithm component library in the algorithm library; the report component in the component library corresponds to the component used to compile report templates in the visual reporting system. For example, the template library displayed on the display interface may include an algorithm template and a report template. The algorithm template corresponds to the battery algorithm (battery algorithm template) in the algorithm template library in the algorithm library; the report template in the template library corresponds to the report template in the visual reporting system; that is, the algorithm development platform can be divided based on different module architectures, including but not limited to the above-mentioned forms of expression.

[0227] As shown in Figures 20 and 21, the overall process of implementing algorithm development on the algorithm development platform 10 is further explained in combination with the two figures. Based on the same implementation principle as the above embodiment, the specific implementation principle will not be repeated. As shown in Figure 21, the overall implementation process may include the following steps:

[0228] S2101: After the user logs in, an algorithm application is generated.

[0229] Exemplarily, the above-mentioned users include but are not limited to developers of the B-end and C-end as shown in Figure 20, or users of the B-end and C-end, or internal users or operators and maintainers of the algorithm development platform 10.

[0230] For example, as shown in FIG20 , developers on the B-end or C-end can provide a battery algorithm to the algorithm development platform 10, provide a data set for the database 103 of the algorithm development platform 10, and implement secondary development of the battery algorithm based on the algorithm library and report component library of the algorithm development platform 10, such as arranging the algorithm components to obtain a new algorithm template, or arranging the report components to obtain a visual report template. Users on the B-end or C-end can log in to use the battery algorithm or visual report template in the algorithm library.

[0231] For example, the display interface corresponding to "My Application" in the algorithm development platform 10 receives an instruction from the user to click on a control to create an application, and generates an algorithm application in response to the instruction, such as an application for determining whether 1,000 vehicles will have a certain fault.

[0232] S2102, determine whether to use the algorithm template of the low-code development platform.

[0233] Exemplarily, the algorithm development platform 10 may be a low-code development platform. After receiving an instruction to create an application, the algorithm application is generated, and a prompt is given to indicate whether to select an algorithm template of the low-code development platform. The selection instruction input by the user is received; if yes, S2104 is executed; if no, S2103 is executed.

[0234] S2103, enter the blank secondary development interface.

[0235] For example, if the algorithm template of the algorithm development platform 10 is not selected, the interface shown in FIG8 (a) is entered, which displays a blank canvas for secondary development. The display interface of this canvas supports secondary development of the battery algorithm based on the battery algorithm component shown in FIG15 (b).

[0236] S2104, enter the secondary development interface of the algorithm template.

[0237] For example, if an algorithm template from the algorithm development platform 10 is selected, a secondary development interface containing the algorithm template is entered. In response to the selection instruction, a secondary development canvas for the algorithm template is displayed. This canvas display interface supports secondary development of battery algorithms based on the battery algorithm template (e.g., a battery consistency assessment template) shown in FIG. 16 (b).

[0238] S2105, drag and drop algorithm components to complete algorithm development.

[0239] For example, as shown in Figure 8 (b), the development of the battery algorithm is completed by receiving instructions from the user to drag the algorithm component; the algorithm component here may include the battery algorithm component as shown in Figure 15 (b), and may also include the component corresponding to the battery algorithm template as shown in Figure 16 (b).

[0240] S2106: Register and deploy the algorithm in the developer center, call the dataset to complete the algorithm debugging and verification, and publish it to the algorithm library after review and approval.

[0241] S2107, determine the algorithm output report template.

[0242] Exemplarily, an instruction for selecting a report template input by a user is received, and in response to the instruction, an interface for creating a report template as shown in FIG. 19 ( a ) is entered.

[0243] S2108: Determine whether the user has selected the default report template.

[0244] For example, when entering the interface for creating a report template, a selection pop-up window is displayed, prompting the user whether to use the default algorithm report template, and receiving the selection instruction input by the user; if the selection instruction is yes, execute S2110; if the selection instruction is no, execute S2109.

[0245] S2109, custom report template based on low-code development platform.

[0246] For example, when the user does not use the platform's default report template, the operation shown in Figure 19 (b) is performed to receive the user's customized report template operation, organize the report components, and obtain a customized report template.

[0247] S2110 , calling the battery algorithm and generating a report on the execution of the algorithm.

[0248] Exemplarily, the algorithm development platform can support calling the corresponding battery algorithm (such as the cell voltage outlier diagnosis algorithm) based on a new report template or a default report template, running the battery algorithm and obtaining the execution results, that is, obtaining a report on the algorithm execution, and displaying it in a visual interface.

[0249] S2111, save the report locally and end the execution of this application.

[0250] The series of battery algorithms provided in the embodiments of the present application can be obtained based on the research and development of actual business scenarios. Based on this series of battery algorithms, developers of low-code development platforms can be effectively guided to develop more accurate battery algorithms that are suitable for various application scenarios of battery services; based on the needs of various applications, algorithm applications that are adapted to the scenarios are created, and based on the created algorithm applications, the management of battery services is realized, thereby greatly improving battery management efficiency.

[0251] As shown in Figure 22, a flow chart of the algorithm development method provided in the embodiment of the present application is provided. Based on the same implementation principle as the above embodiment, the specific implementation principle will not be repeated. As shown in Figure 22, the overall implementation process may include the following steps:

[0252] S2201: Obtain a battery algorithm template and / or a battery algorithm component.

[0253] S2202: Develop a battery algorithm module through an algorithm development system based on the selected battery algorithm template and / or battery algorithm component.

[0254] The algorithm development platform includes an algorithm development system and an algorithm library, the battery algorithm template is stored in the algorithm template library in the algorithm library, and the battery algorithm component is stored in the algorithm component library in the algorithm library.

[0255] In some embodiments, based on the selected battery algorithm template and / or battery algorithm component, developing a battery algorithm module through an algorithm development system includes:

[0256] In response to the algorithm arrangement instruction, the battery algorithm template and / or the battery algorithm component are arranged to obtain an arranged battery algorithm template.

[0257] In some embodiments, in response to the algorithm arrangement instruction, the battery algorithm template and / or the battery algorithm component are arranged to obtain an arranged battery algorithm template, including:

[0258] In response to the algorithm arrangement instruction, the selected battery algorithm template and / or battery algorithm component is arranged in series and / or in parallel to obtain an arranged battery algorithm template.

[0259] In some embodiments, based on the selected battery algorithm template and / or battery algorithm component, developing a battery algorithm module through an algorithm development system includes:

[0260] The battery algorithm to be debugged is debugged and verified, and the battery algorithm after successful verification is published in the algorithm library as a battery algorithm component or battery algorithm template; wherein the selected battery algorithm includes the battery algorithm template and / or battery algorithm component to be debugged; the battery algorithm template and / or battery algorithm component to be debugged includes the uploaded battery algorithm template and / or battery algorithm component, or the compiled battery algorithm template.

[0261] In some embodiments, debugging and verifying the battery algorithm to be debugged includes:

[0262] The uploaded battery algorithm template and / or battery algorithm component is debugged and verified based on the preset input parameters, output parameters and algorithm thresholds; and / or the arranged battery algorithm template is debugged and verified based on the adjustment of input parameters, output parameters, associated parameters and arrangement order.

[0263] In some embodiments, after debugging and verifying the battery algorithm to be debugged, the method further includes:

[0264] Submit the successfully verified battery algorithm for review and processing; publish the successfully verified battery algorithm as a battery algorithm component or battery algorithm template in the algorithm library, including:

[0265] The battery algorithm that has been successfully verified and reviewed will be published in the algorithm library as a battery algorithm component or battery algorithm template.

[0266] In some embodiments, the algorithm development platform further includes a database; and developing a battery algorithm module using the algorithm development system further includes:

[0267] Call the battery indicator data in the database; develop the battery algorithm module based on the battery indicator data.

[0268] In some embodiments, a battery algorithm module is developed based on battery indicator data, including:

[0269] Based on the battery indicator data, the selected battery algorithm template and / or battery algorithm component is debugged and verified.

[0270] In some embodiments, developing a battery algorithm module using an algorithm development system further includes:

[0271] The target data is obtained during the development of the battery algorithm module, and the target data is stored in the database as battery indicator data.

[0272] In some embodiments, the target data includes first indicator data and / or second indicator data; obtaining the target data in the development of the battery algorithm module includes:

[0273] Obtain first indicator data uploaded by a user; and / or obtain second indicator data obtained by executing a battery algorithm based on existing battery indicator data in a database.

[0274] In some embodiments, obtaining second indicator data obtained by executing a battery algorithm based on existing battery indicator data in a database includes:

[0275] Based on the existing battery indicator data in the database, at least one of algorithm training, algorithm debugging, algorithm verification, algorithm testing, algorithm tuning and algorithm iteration is performed to obtain second indicator data.

[0276] In some embodiments, obtaining second indicator data obtained by executing a battery algorithm based on existing battery indicator data in a database includes:

[0277] Based on the existing battery indicator data in the database, perform at least one of algorithm training, algorithm debugging, algorithm verification, algorithm testing, algorithm tuning and algorithm iteration to obtain an execution result; based on the execution result, update the existing battery indicator data in the database to obtain second indicator data.

[0278] In some embodiments, based on the execution result, updating the existing battery indicator data in the database to obtain the second indicator data includes:

[0279] Based on the execution result, in response to the marking instruction input by the user, the battery indicator data already in the database is marked to obtain the marked second indicator data; and / or based on the execution result, in response to the filtering instruction input by the user, the battery indicator data already in the database is filtered to obtain the filtered second indicator data.

[0280] In some embodiments, the selected battery algorithm template and / or battery algorithm component includes a battery algorithm uploaded by a user; and developing a battery algorithm module through an algorithm development system based on the selected battery algorithm template and / or battery algorithm component further includes:

[0281] Register the battery algorithm uploaded by the user and deploy the registered battery algorithm.

[0282] In some embodiments, the algorithm development platform further comprises a visual reporting system; and the method further comprises:

[0283] Through the visual reporting system, the battery algorithm templates and / or battery algorithm components published in the algorithm library are called and executed, and the execution results are presented in a visual manner.

[0284] In some embodiments, the method further comprises:

[0285] In response to the report editing instruction input by the user, the report components in the report component library are edited to obtain an edited report template.

[0286] In some embodiments, a visual reporting system is used to call and execute battery algorithm templates and / or battery algorithm components published in an algorithm library, and to present the execution results in a visual manner, including:

[0287] In response to the report execution instruction, based on the selected report template, the battery algorithm template and / or battery algorithm component in the algorithm library is called and executed, and the execution result is presented in a visual manner.

[0288] It should be understood that the size of the serial numbers of the steps in the above embodiments does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0289] Corresponding to the method described in the above embodiment, the embodiment of the present application provides an algorithm development device, which is applied to an algorithm development platform. The algorithm development platform includes an algorithm development system and an algorithm library. The algorithm development device includes:

[0290] An acquisition unit, configured to acquire a battery algorithm template and / or a battery algorithm component;

[0291] A development unit, configured to develop a battery algorithm module through an algorithm development system based on a selected battery algorithm template and / or battery algorithm component;

[0292] Among them, the algorithm template library in the algorithm library is used to store battery algorithm templates, and the algorithm component library in the algorithm library is used to store battery algorithm components.

[0293] In one possible implementation, the development unit includes an algorithm orchestration module;

[0294] The algorithm arrangement module is used to arrange the battery algorithm template and / or battery algorithm component in response to the algorithm arrangement instruction to obtain the arranged battery algorithm template.

[0295] In one possible implementation, the algorithm arrangement module is further configured to arrange the selected battery algorithm templates and / or battery algorithm components in series and / or in parallel in response to the algorithm arrangement instruction to obtain an arranged battery algorithm template.

[0296] In a possible implementation, the development unit further includes a publishing module;

[0297] A publishing module is used to debug and verify the battery algorithm to be debugged, and publish the successfully verified battery algorithm as a battery algorithm component or battery algorithm template in the algorithm library; wherein the selected battery algorithm includes the battery algorithm template and / or battery algorithm component to be debugged; the battery algorithm template and / or battery algorithm component to be debugged includes the uploaded battery algorithm template and / or battery algorithm component, or the compiled battery algorithm template.

[0298] In one possible implementation, the publishing module is also used to debug and verify the uploaded battery algorithm template and / or battery algorithm component based on preset input parameters, output parameters and algorithm thresholds; and / or debug and verify the arranged battery algorithm template based on the adjustment of input parameters, output parameters, associated parameters and arrangement order.

[0299] In a possible implementation, the publishing module is further used to submit the successfully verified battery algorithm for review and publish the successfully verified and reviewed battery algorithm as a battery algorithm component or battery algorithm template in the algorithm library.

[0300] In a possible implementation, the algorithm development platform also includes a database; the development unit is further used to call the battery indicator data in the database; and develop the battery algorithm module based on the battery indicator data.

[0301] In a possible implementation, the release module in the development unit is further configured to debug and verify the selected battery algorithm template and / or battery algorithm component based on the battery indicator data.

[0302] In a possible implementation, the development unit further includes a data recovery module;

[0303] The data recovery module is used to obtain target data during the development of the battery algorithm module and store the target data as battery indicator data in the database.

[0304] In one possible implementation, the target data includes first indicator data and / or second indicator data; the data recovery module is also used to obtain the first indicator data uploaded by the user; and / or obtain the second indicator data obtained by executing the battery algorithm based on the battery indicator data already in the database.

[0305] In one possible implementation, the data recovery module is further used to perform at least one of algorithm training, algorithm debugging, algorithm verification, algorithm testing, algorithm tuning and algorithm iteration based on the existing battery indicator data in the database to obtain second indicator data.

[0306] In one possible implementation, the data recovery module is also used to perform at least one of algorithm training, algorithm debugging, algorithm verification, algorithm testing, algorithm tuning and algorithm iteration based on the battery indicator data already in the database to obtain an execution result; based on the execution result, the battery indicator data already in the database is updated to obtain second indicator data.

[0307] In a possible implementation, the data recovery module is further configured to:

[0308] Based on the execution result, in response to the marking instruction input by the user, the battery indicator data already in the database is marked to obtain the marked second indicator data; and / or based on the execution result, in response to the filtering instruction input by the user, the battery indicator data already in the database is filtered to obtain the filtered second indicator data.

[0309] In one possible implementation, the selected battery algorithm template and / or the battery algorithm component includes a battery algorithm uploaded by a user; the development unit further includes a registration module and a deployment module;

[0310] Registration module, used to register the battery algorithm uploaded by the user;

[0311] The deployment module is used to deploy the registered battery algorithm.

[0312] In one possible implementation, the algorithm development platform also includes a visual reporting system;

[0313] The development unit is also used to call and execute the battery algorithm templates and / or battery algorithm components published in the algorithm library through a visual reporting system, and present the execution results in a visual manner.

[0314] In a possible implementation, the development unit further includes a report compilation module;

[0315] The report editing module is used to edit the report components in the report component library in response to the report editing instruction input by the user to obtain the edited report template.

[0316] In a possible implementation, the development unit further includes a report generation module;

[0317] The report generation module is used to call and execute the battery algorithm template and / or battery algorithm component in the algorithm library in response to the report running instruction based on the selected report template, and present the execution result in a visual manner.

[0318] FIG23 shows a schematic diagram of the hardware structure of the electronic device 23 .

[0319] As shown in FIG23 , the electronic device 23 of this embodiment includes: at least one processor 230 (only one is shown in FIG23 ), and a memory 231. The memory 231 stores a computer program 232 that can be executed on the processor 230. When the processor 230 executes the computer program 232, it implements the steps of the above-mentioned method embodiment, such as S2201 to S2202 shown in FIG22 . Alternatively, when the processor 230 executes the computer program 232, it implements the functions of each module / unit in the above-mentioned device embodiments.

[0320] It should be understood that the structure illustrated in the embodiments of the present application does not constitute a specific limitation on the electronic device 23. In other embodiments of the present application, the electronic device 23 may include more or fewer components than shown, or may combine or separate certain components, or arrange the components differently. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

[0321] The electronic device 23 can be a computing device such as a desktop computer, laptop, PDA, or cloud server. The electronic device 23 can include, but is not limited to, a processor 230 and a memory 231. Those skilled in the art will appreciate that FIG23 is merely an example of the electronic device 23 and does not limit the electronic device 23. The electronic device 23 can include more or fewer components than shown, or a combination of certain components, or different components. For example, the server can also include an input and transmission device, a network access device, a bus, etc.

[0322] The processor 230 may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field-programmable gate arrays (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or any conventional processor.

[0323] Processor 230 may also include a memory for storing instructions and data. In some embodiments, the memory in processor 230 is a cache memory. This memory can store instructions or data that have just been used or are being recycled by processor 230. If processor 230 needs to use the same instruction or data again, it can directly access the memory. This avoids duplicate accesses, reduces processor 230 latency, and thus improves system efficiency.

[0324] In some embodiments, the memory 231 may be an internal storage unit of the electronic device 23, such as a hard disk or memory of the electronic device 23. The memory 231 may also be an external storage device of the electronic device 23, such as a plug-in hard disk, a smart media card (SMC), a secure digital (SD) card, a flash card, etc. equipped on the electronic device 23. Furthermore, the memory 231 may include both an internal storage unit of the electronic device 23 and an external storage device. The memory 231 is used to store an operating system, application programs, a boot loader, data, and other programs, such as program code of a computer program. The memory 231 may also be used to temporarily store data that has been sent or is about to be sent.

[0325] In addition, the functional units in the various embodiments of the present application may be integrated into a single processing unit, or each unit may exist physically separately, or two or more units may be integrated into a single unit. The aforementioned integrated units may be implemented in the form of hardware or software functional units.

[0326] It should be noted that the structure of the above-mentioned electronic device is only illustrative, and based on different application scenarios, it may also include other physical structures, and the physical structure of the electronic device is not limited here.

[0327] In the above embodiments, the description of each embodiment has its own focus. For parts that are not described or recorded in detail in a certain embodiment, reference can be made to the relevant description of other embodiments.

[0328] An embodiment of the present application further provides a computer-readable storage medium, which stores a computer program. When the computer program is executed by a processor, it can implement the steps in the above-mentioned various method embodiments.

[0329] An embodiment of the present application provides a computer program product. When the computer program product runs on a server, the server can implement the steps in the above-mentioned method embodiments when executing the computer program product.

[0330] If the integrated module / unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the present application implements all or part of the process in the above-mentioned embodiment method, and can also be completed by instructing the relevant hardware through a computer program. The computer program can be stored in a computer-readable storage medium, and the computer program can implement the steps of the above-mentioned various method embodiments when executed by the processor. Among them, the computer program includes computer program code, and the computer program code can be in source code form, object code form, executable file or some intermediate form, etc. Computer-readable media may include: any entity or device that can carry computer program code, recording medium, U disk, mobile hard disk, magnetic disk, optical disk, computer memory, read-only memory (ROM), random access memory (RAM), electric carrier signal, telecommunication signal and software distribution medium, etc.

[0331] The algorithm development platform, electronic device, computer storage medium, and computer program product provided in the above-mentioned embodiments of the present application are all used to execute the methods provided above. Therefore, the beneficial effects that can be achieved can refer to the corresponding beneficial effects of the methods provided above, and will not be repeated here.

[0332] It should be understood that the above is only to help those skilled in the art better understand the embodiments of the present application, and is not intended to limit the scope of the embodiments of the present application. Based on the above examples given, those skilled in the art can obviously make various equivalent modifications or changes. For example, certain steps in each embodiment of the above detection method may be unnecessary, or certain new steps may be added. Or a combination of any two or any multiple embodiments described above. Such modifications, changes, or combined solutions also fall within the scope of the embodiments of the present application.

[0333] The technical features of the above embodiments can be combined arbitrarily. To make the description concise, 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.

[0334] It should be understood that the above is only to help those skilled in the art better understand the embodiments of the present application, and is not intended to limit the scope of the embodiments of the present application. Based on the above examples given, those skilled in the art can obviously make various equivalent modifications or changes. For example, certain steps in each embodiment of the above detection method may be unnecessary, or certain new steps may be added. Or a combination of any two or any multiple embodiments described above. Such modifications, changes, or combined solutions also fall within the scope of the embodiments of the present application.

[0335] It should also be understood that the division of the modes, situations, categories and embodiments in the embodiments of the present application is only for the convenience of description and should not constitute a special limitation. The features of various modes, categories, situations and embodiments can be combined without contradiction.

[0336] It should also be understood that in the various embodiments of the present application, unless otherwise specified or there is a logical conflict, the terms and / or descriptions between different embodiments are consistent and can be referenced to each other, and the technical features in different embodiments can be combined to form new embodiments according to their internal logical relationships.

[0337] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0338] In the embodiments provided in this application, it should be understood that the disclosed devices / network equipment and methods can be implemented in other ways. For example, the device / network equipment embodiments described above are merely illustrative. For example, the division of the modules or units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0339] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of these units may be selected to achieve the purpose of this embodiment according to actual needs.

[0340] The above-described embodiments are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some of the technical features therein. These modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the various embodiments of the present application, and should all be included in the scope of protection of the present application.

[0341] Finally, it should be noted that the above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any changes or substitutions within the technical scope disclosed in this application should be included in the scope of protection of this application. Therefore, the scope of protection of this application should be based on the scope of protection of the claims.

Claims

1. An algorithm development platform, characterized in that: Including algorithm development system and algorithm library; The algorithm library includes: at least one of an algorithm template library and an algorithm component library; The algorithm template library is used to store battery algorithm templates, and the algorithm component library is used to store battery algorithm components; The algorithm development system is configured with the function of developing a battery algorithm module based on a selected battery algorithm template and / or battery algorithm component.

2. The algorithm development platform according to claim 1, characterized in that: In the battery algorithm module development, the functions of the algorithm development system configuration for battery algorithm module development include: a function of arranging selected battery algorithm templates and / or battery algorithm components.

3. The algorithm development platform according to claim 2, characterized in that: The algorithm development system is configured to support the function of arranging the selected battery algorithm template and / or battery algorithm component: the selected battery algorithm template and / or battery algorithm component is arranged in series and / or parallel to obtain the arranged battery algorithm template.

4. The algorithm development platform according to any one of claims 1 to 3, characterized in that: The functions of the algorithm development system for developing battery algorithm modules also include: algorithm publishing function; The algorithm publishing function supports: debugging and verifying the battery algorithm to be debugged, and publishing the successfully verified battery algorithm as a battery algorithm component or a battery algorithm template in the algorithm library; Among them, the selected battery algorithm includes the battery algorithm template and / or battery algorithm component to be debugged; the battery algorithm template and / or battery algorithm component to be debugged includes the uploaded battery algorithm template and / or battery algorithm component, or the arranged battery algorithm template.

5. The algorithm development platform according to claim 4, characterized in that: The battery algorithm to be debugged is debugged and verified as follows: Debug and verify the uploaded battery algorithm template and / or battery algorithm component based on preset input parameters, output parameters and algorithm thresholds; and / or The battery algorithm template obtained by programming is debugged and verified based on the adjustment of input parameters, output parameters, associated parameters and programming sequence.

6. The algorithm development platform according to claim 4 or 5, characterized in that: The algorithm publishing function also supports: the function of submitting the battery algorithm for review after successful verification; The method of publishing the successfully verified battery algorithm as a battery algorithm component or a battery algorithm template in the algorithm library is: publishing the successfully verified and audited algorithm as a battery algorithm component or a battery algorithm template in the algorithm library.

7. The algorithm development platform according to any one of claims 1 to 6, characterized in that: Also includes: A database, wherein the database contains battery indicator data that supports the algorithm development system to call, and the database is used to provide data support for the development of the battery algorithm module.

8. The algorithm development platform according to claim 7, characterized in that: The function of developing a battery algorithm module also supports: based on the database, providing data support for debugging and verifying the selected battery algorithm template and / or battery algorithm component.

9. The algorithm development platform according to claim 7 or 8, characterized in that: The functions of the algorithm development system configured to develop the battery algorithm module include: data recovery function; The data recovery function supports: obtaining the target data in the battery algorithm module development and The index data is stored in the database as the battery index data.

10. The algorithm development platform according to claim 9, characterized in that: The data recovery function supports: obtaining first indicator data uploaded by a user and / or second indicator data obtained by executing a battery algorithm based on existing battery indicator data in the database, and using the first indicator data and / or the second indicator data as the target data.

11. The algorithm development platform according to claim 10, characterized in that: The data recovery function also supports: based on the existing battery indicator data in the database, performing at least one of algorithm training, algorithm debugging, algorithm verification, algorithm testing, algorithm tuning and algorithm iteration to obtain the second indicator data.

12. The algorithm development platform according to claim 10 or 11, characterized in that: The data recovery function also supports: based on the existing battery indicator data in the database, executing at least one of algorithm training, algorithm debugging, algorithm verification, algorithm testing, algorithm tuning and algorithm iteration to obtain an execution result; based on the execution result, updating the existing battery indicator data in the database to obtain the second indicator data.

13. The algorithm development platform according to claim 12, characterized in that: The data recovery function also supports: Based on the execution result, in response to a marking instruction input by a user, marking the existing battery indicator data in the database to obtain the marked second indicator data; and / or Based on the execution result, in response to a filtering instruction input by a user, the battery indicator data already in the database is filtered to obtain the filtered second indicator data.

14. The algorithm development platform according to any one of claims 1 to 13, characterized in that: The algorithm development system is also configured with functions for developing a battery algorithm module, including: a function for registering an uploaded battery algorithm, and a function for deploying a registered battery algorithm.

15. The algorithm development platform according to any one of claims 1 to 14, characterized in that: The algorithm development platform also includes: a visual reporting system; The visualization reporting system is configured to have the functions of calling and executing the battery algorithm template and / or battery algorithm component published in the algorithm library, and presenting the execution result in a visualization manner.

16. The algorithm development platform according to claim 15, characterized in that: The visual reporting system is configured with: a function of arranging selected report templates and / or report components; The function of arranging the selected report template and / or report component supports: generating an arranged report template based on the selected report template and / or report component; The report template is used to call and execute the battery algorithm template and / or battery algorithm component published in the algorithm library, and present the execution result in a visual manner.

17. An algorithm development method, characterized in that: Applied to an algorithm development platform, the algorithm development platform includes an algorithm development system and an algorithm library; the method includes: Obtain a battery algorithm template and / or a battery algorithm component; Based on the selected battery algorithm template and / or the battery algorithm component, developing a battery algorithm module through the algorithm development system; Among them, the algorithm template library in the algorithm library is used to store the battery algorithm templates, and the algorithm component library in the algorithm library is used to store the battery algorithm components.

18. The algorithm development method according to claim 17, characterized in that: The developing of a battery algorithm module based on the selected battery algorithm template and / or the battery algorithm component through the algorithm development system includes: In response to the algorithm arrangement instruction, the battery algorithm template and / or the battery algorithm component are arranged to obtain an arranged battery algorithm template.

19. The algorithm development method according to claim 18, characterized in that: The step of performing arrangement processing on the battery algorithm template and / or the battery algorithm component in response to the algorithm arrangement instruction to obtain an arranged battery algorithm template includes: In response to the algorithm arrangement instruction, the selected battery algorithm template and / or battery algorithm component is arranged in series and / or in parallel to obtain an arranged battery algorithm template.

20. The algorithm development method according to any one of claims 17 to 19, characterized in that: The developing of a battery algorithm module based on the selected battery algorithm template and / or the battery algorithm component through the algorithm development system includes: Debugging and verifying the battery algorithm to be debugged, and publishing the successfully verified battery algorithm as the battery algorithm component or the battery algorithm template in the algorithm library; Among them, the selected battery algorithm includes the battery algorithm template and / or battery algorithm component to be debugged; the battery algorithm template and / or battery algorithm component to be debugged includes the uploaded battery algorithm template and / or battery algorithm component, or the arranged battery algorithm template.

21. The algorithm development method according to claim 20, characterized in that: The debugging and verification of the battery algorithm to be debugged includes: Debugging and verifying the uploaded battery algorithm template and / or battery algorithm component based on preset input parameters, output parameters and algorithm thresholds; and / or The battery algorithm template obtained by programming is debugged and verified based on the adjustment of input parameters, output parameters, associated parameters and programming sequence.

22. The algorithm development method according to claim 20 or 21, characterized in that: After debugging and verifying the battery algorithm to be debugged, the method further includes: Submit the successfully verified battery algorithm for review and processing; The step of publishing the successfully verified battery algorithm as the battery algorithm component or the battery algorithm template in the algorithm library includes: The battery algorithm that has been successfully verified and approved is published in the algorithm library as a battery algorithm component or a battery algorithm template.

23. The algorithm development method according to any one of claims 17 to 22, characterized in that: The algorithm development platform also includes a database; the battery algorithm module development through the algorithm development system also includes: Retrieving battery indicator data from the database; Based on the battery indicator data, the battery algorithm module is developed.

24. The algorithm development method according to claim 23, characterized in that: The developing of the battery algorithm module based on the battery indicator data includes: Based on the battery indicator data, the selected battery algorithm template and / or the battery algorithm component is debugged and verified.

25. The algorithm development method according to claim 23 or 24, characterized in that: The development of the battery algorithm module by the algorithm development system also includes: The target data in the development process of the battery algorithm module is acquired, and the target data is stored in the database as the battery indicator data.

26. The algorithm development method according to claim 25, characterized in that: The target data includes first indicator data and / or second indicator data; the step of obtaining the target data in the development of the battery algorithm module includes: Obtaining the first indicator data uploaded by the user; and / or Acquire second indicator data obtained by executing a battery algorithm based on the existing battery indicator data in the database.

27. The algorithm development method according to claim 26, characterized in that: The obtaining of second indicator data obtained by executing a battery algorithm based on the existing battery indicator data in the database includes: Based on the existing battery indicator data in the database, at least one of algorithm training, algorithm debugging, algorithm verification, algorithm testing, algorithm tuning and algorithm iteration is performed to obtain the second indicator data.

28. The algorithm development method according to claim 26 or 27, characterized in that: The obtaining of second indicator data obtained by executing a battery algorithm based on the existing battery indicator data in the database includes: Based on the existing battery indicator data in the database, perform at least one of algorithm training, algorithm debugging, algorithm verification, algorithm testing, algorithm tuning and algorithm iteration to obtain an execution result; Based on the execution result, the existing battery indicator data in the database is updated to obtain the second indicator data.

29. The algorithm development method according to claim 28, characterized in that: The updating, based on the execution result, of the existing battery indicator data in the database to obtain the second indicator data comprises: Based on the execution result, in response to a marking instruction input by a user, marking the existing battery indicator data in the database to obtain the marked second indicator data; and / or Based on the execution result, in response to a filtering instruction input by a user, the battery indicator data already in the database is filtered to obtain the filtered second indicator data.

30. The algorithm development method according to any one of claims 17 to 29, characterized in that: The selected battery algorithm template and / or the battery algorithm component includes a battery algorithm uploaded by a user; the battery algorithm module development is performed through the algorithm development system based on the selected battery algorithm template and / or the battery algorithm component, and further includes: Register the battery algorithms uploaded by users and deploy the registered battery algorithms.

31. The algorithm development method according to any one of claims 17 to 30, characterized in that: The algorithm development platform also includes a visual reporting system; the method also includes: Through the visual reporting system, the battery algorithm template and / or battery algorithm component published in the algorithm library is called and executed, and the execution result is presented in a visual manner.

32. The algorithm development method according to claim 31, characterized in that: The method further comprises: In response to the report editing instruction input by the user, the report components in the report component library are edited to obtain an edited report template.

33. The algorithm development method according to claim 32, characterized in that: The visual reporting system is used to call and execute the battery algorithm template and / or battery algorithm component published in the algorithm library, and present the execution result in a visual manner, including: In response to the report running instruction, based on the selected report template, the battery algorithm template and / or battery algorithm component in the algorithm library is called and executed, and the execution result is presented in a visual manner.

34. An algorithm development device, characterized in that: Applied to an algorithm development platform, the algorithm development platform comprising an algorithm development system and an algorithm library; The algorithm development device comprises: An acquisition unit, used to acquire a battery algorithm template and / or a battery algorithm component; A development unit, configured to develop a battery algorithm module through the algorithm development system based on the selected battery algorithm template and / or the battery algorithm component; Among them, the algorithm template library in the algorithm library is used to store the battery algorithm templates, and the algorithm component library in the algorithm library is used to store the battery algorithm components.

35. The algorithm development device according to claim 34, characterized in that: The development unit includes an algorithm arrangement module; The algorithm arrangement module is used to arrange the battery algorithm template and / or the battery algorithm component in response to the algorithm arrangement instruction to obtain the arranged battery algorithm template.

36. The algorithm development device according to claim 35, characterized in that: The algorithm arrangement module is also used to respond to the algorithm arrangement instruction to arrange the selected battery algorithm template and / or battery algorithm component in series and / or in parallel to obtain an arranged battery algorithm template.

37. The algorithm development device according to any one of claims 34 to 36, characterized in that: The development unit also includes a publishing module; The publishing module is used to debug and verify the battery algorithm to be debugged, and publish the successfully verified battery algorithm as the battery algorithm component or the battery algorithm template in the algorithm library; Among them, the selected battery algorithm includes the battery algorithm template and / or battery algorithm component to be debugged; the battery algorithm template and / or battery algorithm component to be debugged includes the uploaded battery algorithm template and / or battery algorithm component, or the arranged battery algorithm template.

38. The algorithm development device according to claim 37, characterized in that: The publishing module is further used to debug and verify the uploaded battery algorithm template and / or battery algorithm component based on preset input parameters, output parameters and algorithm thresholds; and / or The battery algorithm template obtained by programming is debugged and verified based on the adjustment of input parameters, output parameters, associated parameters and programming sequence.

39. The algorithm development device according to claim 37 or 38, characterized in that: The publishing module is also used to submit the successfully verified battery algorithm for review and publish the successfully verified and reviewed battery algorithm as a battery algorithm component or a battery algorithm template in the algorithm library.

40. The algorithm development device according to any one of claims 34 to 39, characterized in that: The algorithm development platform also includes a database; the development unit is further used to call the battery indicator data in the database; and develop the battery algorithm module based on the battery indicator data.

41. The algorithm development device according to claim 40, characterized in that: The publishing module in the development unit is also used to debug and verify the selected battery algorithm template and / or the battery algorithm component based on the battery indicator data.

42. The algorithm development device according to claim 40 or 41, characterized in that: The development unit also includes a data recovery module; The data recovery module is used to obtain target data during the development of the battery algorithm module, and store the target data as the battery indicator data in the database.

43. The algorithm development device according to claim 42, characterized in that: The target data includes first indicator data and / or second indicator data; the data recovery module is also used to obtain the first indicator data uploaded by the user; and / or obtain the second indicator data obtained by executing a battery algorithm based on the battery indicator data already in the database.

44. The algorithm development device according to claim 43, characterized in that: The data recovery module is further used to perform at least one of algorithm training, algorithm debugging, algorithm verification, algorithm testing, algorithm tuning and algorithm iteration based on the existing battery indicator data in the database to obtain the second indicator data.

45. The algorithm development device according to claim 43 or 44, characterized in that: The data recovery module is further used to perform at least one of algorithm training, algorithm debugging, algorithm verification, algorithm testing, algorithm tuning and algorithm iteration based on the existing battery indicator data in the database to obtain an execution result; based on the execution result, update the existing battery indicator data in the database to obtain the second indicator data.

46. ​​The algorithm development device according to claim 45, characterized in that: The data recovery module is also used for: Based on the execution result, in response to a marking instruction input by a user, marking the existing battery indicator data in the database to obtain the marked second indicator data; and / or Based on the execution result, in response to a filtering instruction input by a user, the battery indicator data already in the database is filtered to obtain the filtered second indicator data.

47. The algorithm development device according to any one of claims 34 to 46, characterized in that: The selected battery algorithm template and / or the battery algorithm component includes a battery algorithm uploaded by a user; the development unit further includes a registration module and a deployment module; The registration module is used to register the battery algorithm uploaded by the user; The deployment module is used to deploy the registered battery algorithm.

48. The algorithm development device according to any one of claims 34 to 47, characterized in that: The algorithm development platform also includes a visual reporting system; The development unit is also used to call and execute the battery algorithm template and / or battery algorithm component published in the algorithm library through the visual reporting system, and present the execution result in a visual manner.

49. The algorithm development device according to claim 48, characterized in that: The development unit also includes a report compilation module; The report editing module is used to edit the report components in the report component library in response to the report editing instruction input by the user to obtain the edited report template.

50. The algorithm development device according to claim 49, characterized in that: The development unit also includes a report generation module; The report generation module is used to respond to the report running instruction, call and execute the battery algorithm template and / or battery algorithm component in the algorithm library based on the selected report template, and present the execution result in a visual manner.

51. An electronic device, characterized in that: The method comprises a memory and a processor, wherein the memory stores a computer program, and the processor implements the steps of the method according to any one of claims 17 to 33 when executing the computer program.

52. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 17 to 33 are implemented.

Images