Battery state parameter determination method, apparatus, device, medium and program product

Abstract

A battery state parameter determination method, a device, a medium and a program product. The method is applied to a requester and comprises: transmitting an algorithm request to a target smart contract in a blockchain network and, when the requester itself satisfies an authorization condition of the target smart contract, receiving a target battery state parameter estimation algorithm transmitted by the target smart contract; and, on the basis of the target battery state parameter estimation algorithm, acquiring measurement data, so that a target authorization controller in the requester uses the measurement data and the target battery state parameter estimation algorithm to calculate battery state parameters on the basis of authorization configuration information. In the solution disclosed in the present application, the requester requests calling the algorithm from the blockchain network and, after having been authorized, locally calls the algorithm for calculation to obtain a calculation result, thereby not only improving the calculation efficiency and accuracy stability of battery state parameters and achieving calculation standardization, but also allowing participants and algorithm providers to efficiently collaborate with each other on the basis of the blockchain network.

Description

Battery state parameter determination methods, apparatus, equipment, media and procedures products

[0001] Cross-reference to related applications

[0002] This application claims priority to Chinese Patent Application No. 202412000036.6, filed on December 31, 2024, entitled “Method, Apparatus, Device, Medium and Procedure Product for Determining Battery State Parameters”, the entire contents of which are incorporated herein by reference. Technical Field

[0003] This application relates to the field of battery data application technology, specifically to a method, apparatus, device, medium, and program product for determining battery state parameters. Background Technology

[0004] Predicting battery state parameters helps extend battery life, reduce battery usage costs, and improve device performance and safety. These battery state parameters include, but are not limited to, SOH (State of Health), SOC (State of Charge), EOL (End of Life), and RUL (Remaining Useful Life).

[0005] Battery lifecycle data is scattered across different stakeholders, making it difficult to provide valuable data to third parties. For example, an accurate battery algorithm cannot provide accurate battery state estimates to all automakers and requesters. Currently, battery state parameter estimation is mainly achieved through static measurement, which is time-consuming, labor-intensive, and suffers from inconsistent accuracy and lacks standardized methods.

[0006] In summary, improving the efficiency, accuracy, and stability of battery state parameter calculation is a technical problem that urgently needs to be solved by those skilled in the art. Summary of the Invention

[0007] In view of the above problems, this application provides a method, apparatus, device, medium and program product for determining battery state parameters, which can improve the calculation efficiency and accuracy stability of battery state parameters.

[0008] In a first aspect, this application provides a method for determining battery state parameters, applied to a requesting party, comprising: sending an algorithm request to a target smart contract in a blockchain network, and receiving a target battery state parameter estimation algorithm sent from the target smart contract when the requesting party meets the authorization conditions of the target smart contract; obtaining measurement data according to the target battery state parameter estimation algorithm, so that a target authorization controller in the requesting party can calculate battery state parameters using the measurement data and the target battery state parameter estimation algorithm according to authorization configuration information.

[0009] The technical solution disclosed in this application is based on a blockchain distributed system. The algorithm provider stores the battery state parameter estimation algorithm in a smart contract on the blockchain network. The requesting party sends an algorithm request to the target smart contract in the blockchain network. When the target smart contract determines that the requesting party meets the authorization conditions of the target smart contract, it downloads the target battery state parameter estimation algorithm to the requesting party. Then, the requesting party obtains measurement data based on the target battery state parameter estimation algorithm downloaded to the requesting party. The target authorized controller in the requesting party calculates the battery state parameters using the measurement data and the battery state parameter estimation algorithm according to the authorization configuration information. Therefore, this application builds a collaborative ecosystem based on the blockchain network. The requesting party can request to call the battery state parameter estimation algorithm in the blockchain network, and after authorization, call the battery state parameter estimation algorithm locally to obtain the algorithm calculation result. This not only improves the efficiency and stability of battery state parameter calculation accuracy and standardizes battery state parameter calculation, but also enables different participants and algorithm providers to conduct distributed and efficient collaboration based on a trusted and verifiable blockchain network, breaking down data silos throughout the battery's entire lifecycle and realizing the value of the data.

[0010] In some embodiments, the algorithm request includes an algorithm request interface and algorithm request parameters; wherein, the algorithm request parameters include the requester's ID, algorithm information, and a first signature; the algorithm information includes the algorithm name and / or algorithm code.

[0011] The above method enables the determination of the target smart contract and the estimation algorithm of the target battery state parameters based on the algorithm request. This facilitates the determination of whether the requester meets the authorization conditions of the target smart contract based on the algorithm request, and ensures data integrity, authenticity, non-repudiation, security, and supports data traceability and auditing through the first signature.

[0012] In some embodiments, before acquiring measurement data according to the target battery state parameter estimation algorithm, so that the target authorization controller in the requesting party can use the measurement data and the target battery state parameter estimation algorithm to calculate the battery state parameter according to the authorization configuration information, the method further includes: acquiring the target authorization controller, so that the target authorization controller can initialize the authorization configuration information according to the authorization information requested and agreed upon by the requesting party, and initialize the identity information and local key.

[0013] The reliability and accuracy of obtaining authorization configuration information are improved by initializing authorization configuration information based on authorization information requested and agreed upon by the requester, and privacy protection is enhanced by initializing identity information and local keys.

[0014] In some embodiments, the algorithm request includes an algorithm request interface and algorithm request parameters; wherein, the algorithm request parameters include the requester's ID, algorithm information, authorization information, and a first signature; the algorithm information includes an algorithm name and / or algorithm code, the authorization information includes an authorization type and an authorization scope, and the authorization scope includes at least one of a device ID list, an effective time, an expiration time, a number of calls, and a total quantity.

[0015] The above method not only includes authorization information in the algorithm request, but also ensures data integrity, authenticity, non-repudiation, security, and supports data traceability and auditing through the first signature.

[0016] In some embodiments, before obtaining measurement data according to the target battery state parameter estimation algorithm, the method further includes: mapping the parameter fields configured in the target battery state parameter estimation algorithm to the parameter fields in the measurement database;

[0017] Obtaining measurement data according to the target battery state parameter estimation algorithm includes: obtaining the measurement data corresponding to the target battery state parameter estimation algorithm from the measurement database according to the mapping result.

[0018] The above process enables the requesting party to request the algorithm provider's algorithm based on a unified data standard and model, thereby improving the accuracy of the measurement data acquisition corresponding to the battery state parameter estimation algorithm.

[0019] In some embodiments, receiving the target battery state parameter estimation algorithm sent from the target smart contract includes: receiving the encrypted target battery state parameter estimation algorithm sent by the target smart contract; the target smart contract includes a first algorithm decryption key parameter;

[0020] The method further includes: receiving the first algorithm decryption key parameter sent by the target smart contract, generating a second algorithm decryption key parameter based on the first algorithm decryption key parameter, having the target authorization controller verify the second algorithm decryption key parameter, and decrypting the encrypted target battery state parameter estimation algorithm using the second algorithm decryption key parameter after successful verification; or, receiving the second algorithm decryption key parameter sent by the target smart contract, having the target authorization controller verify the second algorithm decryption key parameter, and decrypting the encrypted target battery state parameter estimation algorithm using the second algorithm decryption key parameter after successful verification; the second algorithm decryption key parameter is generated by the target smart contract based on the first algorithm decryption key parameter.

[0021] The above method ensures that the target battery state parameter estimation algorithm is authorized and protected during remote operation, thereby improving the security and reliability of the target battery state parameter estimation algorithm and thus improving the accuracy and stability of battery state parameter calculation.

[0022] In some embodiments, before acquiring measurement data according to the target battery state parameter estimation algorithm, the method further includes: configuring corresponding computing resources to the target authorization controller in response to the resource requirements of the target battery state parameter estimation algorithm.

[0023] The above methods ensure that the target authorization controller in the requesting party has sufficient computing resources to run the target battery state parameter estimation algorithm, achieve reasonable allocation of computing resources and avoid competition for computing resources, thereby improving the reliability, efficiency and stability of the target battery state parameter estimation algorithm and improving resource utilization efficiency.

[0024] In some embodiments, before sending an algorithm request to a target smart contract in the blockchain network, the method further includes: joining the blockchain network after the user has been authenticated by the blockchain network.

[0025] Sending an algorithm request to a target smart contract in a blockchain network includes: sending the algorithm request to the target smart contract in the blockchain network through a blockchain interface.

[0026] By first verifying the identity of the requester, and then adding them to the blockchain network and sending algorithmic requests to the corresponding smart contract through the blockchain interface, the legality and validity of the transaction are ensured, as well as the immutability and traceability of the transaction.

[0027] In some embodiments, obtaining measurement data according to the target battery state parameter estimation algorithm, and then having the target authorization controller in the requesting party calculate battery state parameters using the measurement data and the target battery state parameter estimation algorithm based on authorization configuration information, includes: obtaining a device ID list from a measurement database according to the target battery state parameter estimation algorithm, so that the target authorization controller in the requesting party determines a valid device ID list based on the device ID list and the authorization configuration information; obtaining corresponding measurement data from the measurement database based on the valid device ID list, so that the target authorization controller calls the target battery state parameter estimation algorithm and calculates battery state parameters using the target battery state parameter estimation algorithm and the measurement data.

[0028] The above method enables the target authorized controller to authorize the device ID list sent by the scheduler based on the authorization configuration information, and to call the target battery state parameter estimation algorithm to calculate the battery state parameters, thereby improving the security of data and calculation and preventing data leakage.

[0029] In some embodiments, the target authorization controller in the requesting party determines a valid list of device IDs based on the device ID list and the authorization configuration information, including: the target authorization controller in the requesting party performs a cross-validation operation based on the device ID list and the authorization configuration information to determine a valid list of device IDs.

[0030] The above methods can improve the accuracy of determining the list of valid device IDs.

[0031] In some embodiments, after the target authorization controller in the requesting party performs a cross-validation operation based on the device ID list and the authorization configuration information, the method further includes: the target authorization controller in the requesting party updating the corresponding authorization configuration information in the configuration database based on the cross-validation operation result.

[0032] The above methods can improve the accuracy of the corresponding authorization configuration information records in the configuration database, thereby improving the accuracy of authorization calculations for the requesting party, and thus enhancing the reliability and security of authorization calculations.

[0033] In some embodiments, after the target authorization controller in the requesting party determines the valid device ID list based on the device ID list and the authorization configuration information, the method further includes: the target authorization controller in the requesting party sends the valid device ID list and a second signature obtained by signing the valid device ID list to the scheduler in the requesting party.

[0034] After obtaining the corresponding measurement data from the measurement database based on the valid device ID list, the method further includes: the target authorization controller in the requesting party receives the measurement data, the verified device ID list and the second signature sent by the scheduler in the requesting party, verifies the second signature, and after the signature is verified, executes the step of calling the target battery state parameter estimation algorithm, and calculates the battery state parameters using the target battery state parameter estimation algorithm and the measurement data.

[0035] The scheduler signs the list of valid device IDs by the target authorization controller, and then sends the list of device IDs and their signatures along with the measurement data to the target authorization controller. The signature verification by the target authorization controller can improve the reliability and security of authorization and calculation.

[0036] In some embodiments, after the target authorization controller in the requesting party determines the valid device ID list based on the device ID list and the authorization configuration information, the method further includes: the target authorization controller in the requesting party sends the device ID list, an identifier indicating whether each device ID in the device ID list is valid, a timestamp, and a third signature obtained by signing the device ID list, the identifier, and the timestamp to the scheduler in the requesting party.

[0037] After obtaining the corresponding measurement data from the measurement database based on the valid device ID list, the process further includes: the target authorization controller in the requesting party receiving the measurement data, the device ID list, the identifier, the timestamp, and the third signature sent by the scheduler in the requesting party; verifying the third signature; verifying whether the device ID of the measurement data and the device ID of the identifier that has passed verification are consistent; verifying whether the timestamp is within a preset range; and after all verifications are passed, executing the step of calling the target battery state parameter estimation algorithm and calculating the battery state parameters using the target battery state parameter estimation algorithm and the measurement data.

[0038] The above process can improve the reliability and security of authorization and computation.

[0039] In some embodiments, obtaining a list of device IDs from a measurement database according to the target battery state parameter estimation algorithm includes: generating a DAG plan according to the target battery state parameter estimation algorithm, and obtaining a list of device IDs from the measurement database according to the DAG plan.

[0040] The above process enables the orderly acquisition of the device ID list and the orderly calculation of tasks, thereby improving the efficiency of battery status parameter calculation.

[0041] Secondly, this application provides a battery state parameter determination device, applied to a requesting party, comprising: a sending module, configured to send an algorithm request to a target smart contract in a blockchain network, and, when it meets the authorization conditions of the target smart contract, receive a target battery state parameter estimation algorithm sent from the target smart contract; and an acquisition module, configured to acquire measurement data according to the target battery state parameter estimation algorithm, so that a target authorization controller in the requesting party can calculate battery state parameters using the measurement data and the target battery state parameter estimation algorithm based on authorization configuration information.

[0042] Thirdly, this application provides an electronic device, including: a memory for storing a computer program; and a processor for executing the computer program to implement the steps of the battery state parameter determination method as described in any of the preceding claims.

[0043] Fourthly, this application provides a readable storage medium storing a computer program that, when executed by a processor, implements the steps of the battery state parameter determination method as described in any of the preceding claims.

[0044] Fifthly, this application provides a computer program product, including a computer program that, when executed by a processor, implements the steps of the battery state parameter determination method as described in any of the preceding claims.

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

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

[0047] Figure 1 is a flowchart of a battery state parameter determination method according to some embodiments of this application;

[0048] Figure 2 is a schematic diagram of the structure of a battery state parameter determination system according to some embodiments of this application;

[0049] Figure 3 is a flowchart of algorithm authorization and invocation in some embodiments of this application;

[0050] Figure 4 is a schematic diagram of the structure of a battery state parameter determination device according to some embodiments of this application. Detailed Implementation

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

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

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

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

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

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

[0057] In the description of the embodiments of this application, the technical terms "center," "longitudinal," "lateral," "length," "width," "thickness," "upper," "lower," "front," "rear," "left," "right," "vertical," "horizontal," "top," "bottom," "inner," "outer," "clockwise," "counterclockwise," "axial," "radial," and "circumferential" indicate the orientation or positional relationship based on the orientation or positional relationship shown in the accompanying drawings. They are only for the convenience of describing the embodiments of this application and simplifying the description, and are not intended to indicate or imply that the device or element referred to must have a specific orientation, or be constructed and operated in a specific orientation. Therefore, they should not be construed as limitations on the embodiments of this application.

[0058] In the description of the embodiments of this application, unless otherwise expressly specified and limited, technical terms such as "installation," "connection," "joining," and "fixing" should be interpreted broadly. For example, they can refer to a fixed connection, a detachable connection, or an integral part; they can refer to a mechanical connection or an electrical connection; they can refer to a direct connection or an indirect connection through an intermediate medium; they can refer to the internal communication of two components or the interaction between two components. For those skilled in the art, the specific meaning of the above terms in the embodiments of this application can be understood according to the specific circumstances.

[0059] Because data silos exist throughout the entire battery lifecycle, managing and applying this data is difficult. The entire battery lifecycle, from battery manufacturing to applications in electric vehicles or energy storage, to secondary use and recycling, generates a vast amount of data, which is owned by various companies across the industry chain. Due to factors such as data security, privacy protection, regulations, and commercial interests, companies are unwilling or unable to directly share this data with other parties.

[0060] Battery data enables effective state estimation, fault warning, and lifespan management of batteries. However, because battery data is scattered among different stakeholders, it is difficult to provide data to third parties for valuable use. For example, an accurate battery algorithm (such as a battery SOH algorithm) cannot provide accurate SOH estimates to all car manufacturers and users.

[0061] Battery state parameters include SOH, SOC, EOL, and RUL. Currently, the estimation of battery state parameters is mainly achieved through static measurement, which is very time-consuming and labor-intensive, with inconsistent accuracy and lack of standardized methods, resulting in less than optimal battery utilization.

[0062] To this end, the applicant proposes a method, apparatus, device, medium, and program product for determining battery state parameters. Based on a blockchain distributed system, the algorithm provider stores the battery state parameter estimation algorithm in a smart contract on the blockchain network. The requesting party sends an algorithm request to the target smart contract in the blockchain network. When the target smart contract determines that the requesting party meets the authorization conditions of the target smart contract, it downloads the target battery state parameter estimation algorithm to the requesting party. Then, the requesting party obtains measurement data according to the target battery state parameter estimation algorithm downloaded to the requesting party, and the target authorized controller in the requesting party calculates the battery state parameters using the measurement data and the target battery state parameter estimation algorithm according to the authorization configuration information. Thus, this application builds a collaborative ecosystem based on the blockchain network. The requesting party can request to call the battery state parameter estimation algorithm in the blockchain network, and after authorization, call the battery state parameter estimation algorithm locally to obtain the algorithm calculation results. This not only improves the efficiency and stability of battery state parameter calculation accuracy and achieves standardization of battery state parameter calculation, but also enables different participants and algorithm providers to conduct distributed and efficient collaboration based on a trusted and verifiable blockchain network, breaking down data silos in the entire battery life cycle and realizing the value of data.

[0063] Referring to Figures 1 and 2, where Figure 1 is a flowchart of a battery state parameter determination method according to some embodiments of this application, and Figure 2 is a structural schematic diagram of a battery state parameter determination system according to some embodiments of this application. According to some embodiments of this application, the battery state parameter determination method can be applied to the requesting party, and the method includes the following steps:

[0064] S11: Send an algorithm request to the target smart contract in the blockchain network, and receive the target battery state parameter estimation algorithm sent by the target smart contract when it meets the authorization conditions of the target smart contract.

[0065] A battery state parameter determination system may include a blockchain network and at least one smart contract located within the blockchain network, and may also include participants. Participants may include multiple data participants (for providing battery measurement data) and / or service providers (for providing services to users, such as battery data, battery state parameters, etc.), and may also include an algorithm provider (for providing a battery state parameter estimation algorithm), wherein data participants or service providers may, as requesting parties, request the invocation of the battery state parameter estimation algorithm in the smart contract.

[0066] Based on a blockchain distributed system, the algorithm provider stores its verified, high-precision battery state parameter estimation algorithm in a smart contract. This provides a standardized battery state parameter estimation algorithm, facilitating the uniformity and stability of battery state parameter estimation accuracy. The smart contract not only contains the battery state parameter estimation algorithm but may also include an authorization contract and an authorization controller. The authorization contract contains authorization rules (e.g., the requester is on a whitelist, and authorization fees have been paid), while the authorization controller is used for authorization configuration, authorization control, and algorithm scheduling calculations.

[0067] When a requester wants to invoke a target battery state parameter estimation algorithm (such as the State of Health (SOH) algorithm or the State of Charge (SOC) algorithm), it can send an algorithm request to the target smart contract (i.e., the smart contract containing the target battery state parameter estimation algorithm) in the blockchain network. In other words, it can request the target battery state parameter estimation algorithm from the corresponding target smart contract. The algorithm request sent by the requester can include the requester's ID (Identity Document) and the algorithm information of the requested target battery state parameter estimation algorithm (such as the algorithm name, algorithm code, etc., where the algorithm code is the algorithm's number; for example, the algorithm code for the SOH algorithm could be 001, the algorithm code for the SOC algorithm could be 002, and the algorithm code for the battery consensus algorithm could be 003). Alternatively, the requester may not be a member of the blockchain. In this case, before requesting the algorithm, the blockchain network can authenticate the requester. After authentication, the requester can join the blockchain network and then request the corresponding battery state parameter estimation algorithm through the blockchain interface and the corresponding smart contract. Alternatively, the requester may have already joined the blockchain network. In this case, the requester can request the target battery state parameter estimation algorithm from the target smart contract through the blockchain interface. Alternatively, the requester can request the target battery state parameter estimation algorithm from the target smart contract through an intermediary that has joined the blockchain network. That is, the intermediary can act as a proxy to interact with the target smart contract, meaning that the intermediary can provide an interface within its internal system to forward the algorithm request sent by the requester to the target smart contract in the blockchain network.

[0068] Upon receiving an algorithm request from a requester, the target smart contract in the blockchain network can determine whether the requester meets the authorization conditions of the target smart contract (e.g., being on a whitelist, having paid the authorization fee, etc.). Specifically, it can determine whether the requester meets the authorization conditions within the target smart contract. If it is determined that the requester meets the authorization conditions (i.e., the requester meets the authorization contract conditions), the target battery state parameter estimation algorithm corresponding to the algorithm request can be downloaded to the requester (specifically, downloaded to the requester's local runtime environment). Correspondingly, the requester can receive the target battery state parameter estimation algorithm sent from the target smart contract when it meets the authorization conditions, allowing it to calculate battery state parameters locally. This enables the sharing of battery state parameter estimation algorithms through the blockchain network, breaking down data silos and eliminating the need for static measurement methods for battery state parameter estimation, thereby improving the efficiency, accuracy, and stability of battery state parameter calculations.

[0069] S12: Obtain measurement data according to the target battery state parameter estimation algorithm, so that the target authorized controller in the requesting party can calculate the battery state parameters using the measurement data and the target battery state parameter estimation algorithm based on the authorized configuration information.

[0070] In this embodiment, the requesting party may pre-deploy a target authorization controller corresponding to the target smart contract. Alternatively, when the target smart contract determines that the requesting party meets the authorization conditions of the target smart contract, the target authorization controller may be downloaded to the requesting party (specifically, the target smart contract may download the target battery state parameter estimation algorithm and the target authorization controller together to the requesting party). This allows the target authorization controller in the requesting party to initialize the authorization configuration locally to obtain the authorization configuration information. When the requesting party requests authorization from the target authorization controller in the requesting party with a list of device IDs, the authorization configuration information is updated based on the authorization operation, and authorization control and algorithm scheduling calculations are performed.

[0071] Additionally, the requester may include a scheduler (specifically a local scheduler, also known as a task manager) for task management and coordination, retrieving measurement data from the measurement database (used to store raw measurement data), mapping the parameter fields configured in the algorithm to the parameter fields in the local measurement database, and preprocessing the measurement data, etc.

[0072] If the requesting party wants to use a target battery state parameter estimation algorithm downloaded locally to calculate battery state parameters, the requesting party can obtain the corresponding measurement data based on the target battery state parameter estimation algorithm. Specifically, the measurement data is obtained by calculating the necessary parameters according to the corresponding battery state parameter estimation algorithm. Taking the battery state parameter estimation algorithm as an example, the necessary parameters and interfaces for the algorithm calculation are: device ID, voltage, current, timestamp, and other auxiliary fields such as driving conditions, charging conditions, and cumulative charging times. Furthermore, after obtaining the measurement data corresponding to the target battery state parameter estimation algorithm, the measurement data can be preprocessed to improve data quality, thereby improving the reliability and accuracy of battery state parameter calculation. For example, this includes deleting or filling missing values, removing or correcting abnormal data, etc.

[0073] Specifically, the scheduler in the requesting party can obtain the corresponding measurement data based on the target battery state parameter estimation algorithm and preprocess the measurement data. When a data participant acts as the requesting party, its scheduler can obtain measurement data from its local measurement database based on the target battery state parameter estimation algorithm. This ensures that the data does not leave the local machine of the data participant throughout the entire calculation process, and the data participant does not need to share data, thus achieving data protection while realizing data value utilization. When the service provider acts as the requester, the scheduler within the requester can request data on the blockchain network or directly from the data participants. The service provider can obtain measurement data from the data participants via the blockchain network or offline and pay the corresponding fees. Alternatively, the service provider can request authorization from the data participants for a period of time to use the measurement data within that authorized timeframe. Or, to protect data security, the data requester can request an algorithm from the data participants, download the target battery state parameter estimation algorithm to their local machine, and perform data acquisition, authorization, and algorithm invocation calculations locally. Then, the data participants send the calculated battery state parameters to the service provider, which then provides the data participants with the corresponding fees and provides the calculated battery state parameters to the relevant users.

[0074] After the requesting party obtains the measurement data, the target authorized controller within the requesting party can calculate the battery state parameters using the measurement data and the target battery state parameter estimation algorithm based on the authorized configuration information. Specifically, if the scheduler within the requesting party obtains the measurement data, it can send the acquired measurement data to the target authorized controller within the requesting party. Then, the target authorized controller can calculate the battery state parameters using the measurement data and the target battery state parameter estimation algorithm based on the authorized configuration information, and send the calculated battery state parameters to the scheduler within the requesting party so that the scheduler can be aware of the battery state parameters. This enables the requesting party to request the algorithm provider's algorithm call, and after authorization, to call the smart contract algorithm locally to calculate and obtain the battery algorithm result. This ensures the uniformity and stability of the battery state parameter estimation accuracy, improves the efficiency of battery state estimation, and achieves standardization, authorization, shared computing, efficient collaboration and application of the battery state parameter estimation algorithm, while also ensuring a fair and reasonable value distribution.

[0075] As can be seen from the above process, this application embodiment builds a collaborative ecosystem based on a blockchain network. Each participant can apply for a public battery state parameter estimation algorithm based on basic battery data. The algorithm is then run based on the authorized application, achieving a unified evaluation standard for battery state estimation. Furthermore, it enables different participants and algorithm providers to conduct distributed and efficient collaboration based on a trusted and verifiable blockchain network, thereby achieving efficient industry collaboration and maximizing the value of data. Moreover, this application embodiment, based on a blockchain network, can meet the requirements of audit trustworthiness and regulatory friendliness.

[0076] Through the embodiments of this application, the battery state parameter estimation algorithm is standardized, authorized, shared, efficiently collaborated, and applied based on a distributed system and data standards, under the premise of compliance, data security, and privacy protection, and using full life-cycle data of multiple batteries and related devices owned by multiple parties, and a fair and reasonable value distribution is achieved.

[0077] The technical solution disclosed in this application is based on a blockchain distributed system. The algorithm provider stores the battery state parameter estimation algorithm in a smart contract on the blockchain network. The requesting party sends an algorithm request to the target smart contract in the blockchain network. When the target smart contract determines that the requesting party meets the authorization conditions of the target smart contract, it downloads the target battery state parameter estimation algorithm to the requesting party. Then, the requesting party obtains measurement data based on the target battery state parameter estimation algorithm downloaded to the requesting party. The target authorized controller in the requesting party calculates the battery state parameters using the measurement data and the battery state parameter estimation algorithm according to the authorization configuration information. Therefore, this application builds a collaborative ecosystem based on the blockchain network. The requesting party can request to call the battery state parameter estimation algorithm in the blockchain network, and after authorization, call the battery state parameter estimation algorithm locally to obtain the algorithm calculation result. This not only improves the efficiency and stability of battery state parameter calculation accuracy and standardizes battery state parameter calculation, but also enables different participants and algorithm providers to conduct distributed and efficient collaboration based on a trusted and verifiable blockchain network, breaking down data silos throughout the battery's entire lifecycle and realizing the value of the data.

[0078] According to some embodiments of this application, the algorithm request may include an algorithm request interface and algorithm request parameters;

[0079] The algorithm request parameters may include the requester's ID, algorithm information, and first signature; the algorithm information may include the algorithm name and / or algorithm code.

[0080] In this embodiment, the algorithm request sent by the requester may specifically include an algorithm request interface and algorithm request parameters. The algorithm request interface is used to send a request and its parameters to the target smart contract from the requester. The algorithm request parameters may include the requester's ID, algorithm information, and a first signature. The requester's ID can be used by the target smart contract to determine whether the requester meets the authorization conditions of the target smart contract. The algorithm information may specifically include an algorithm name and / or algorithm code to facilitate the determination of the target smart contract and the target battery state parameter estimation algorithm based on the algorithm information. The first signature may be obtained by signing the requester's ID and the algorithm information to ensure data integrity, authenticity, non-repudiation, security, and support for data traceability and auditing.

[0081] For example, the interface and parameters for an algorithm request can be: request Algorithm(requester ID, algorithm name, algorithm code, first signature).

[0082] The above method enables the determination of the target smart contract and the estimation algorithm of the target battery state parameters based on the algorithm request. This facilitates the determination of whether the requester meets the authorization conditions of the target smart contract based on the algorithm request, and ensures data integrity, authenticity, non-repudiation, security, and supports data traceability and auditing through the first signature.

[0083] According to some embodiments of this application, before acquiring measurement data according to a target battery state parameter estimation algorithm, and before the target licensee in the requesting party calculates battery state parameters using the measurement data and the target battery state parameter estimation algorithm based on license configuration information, the process may further include:

[0084] Obtain the target authorization controller, which will initialize the authorization configuration information based on the authorization information requested and agreed upon by the requester, and initialize the identity information and local key.

[0085] In this embodiment, the requesting party obtains measurement data based on the target battery state parameter estimation algorithm. Before the target authorized controller in the requesting party calculates the battery state parameters using the measurement data and the target battery state parameter estimation algorithm based on the authorized configuration information, the requesting party can obtain the target authorized controller. Specifically, the requesting party may pre-deploy a target authorized controller corresponding to the target smart contract. In this case, the requesting party can call the target authorized controller pre-deployed in itself. Alternatively, when the target smart contract determines that the requesting party meets the authorization conditions of the target smart contract, it downloads the target authorized controller to the requesting party. In this case, when the requesting party itself meets the authorization conditions of the target smart contract, it receives the target authorized controller sent by the target smart contract.

[0086] Alternatively, the requester can also request authorization from the blockchain network. Specifically, the requester can send an authorization request to the target smart contract in the blockchain network. The authorization information in the authorization request can be included in the algorithm request; that is, the algorithm request can contain not only algorithm information but also authorization information to reduce the number of requests made by the requester. Alternatively, the authorization request can be sent separately by the requester to the target smart contract. After receiving the authorization request, the target smart contract can determine whether the requester's authorization request meets the smart contract's authorization conditions. If it does, it can determine that the authorization information requested by the requester has been agreed to. Alternatively, the target smart contract can forward the authorization request sent by the requester to the algorithm provider, who can then decide whether to agree to the authorization information requested by the requester. If the algorithm provider agrees, it can send an agreement message to the target smart contract, thus confirming that the authorization information requested by the requester has been agreed to. Afterward, the target smart contract can inform the target authorization controller (at this point, the target authorization controller may already be located within the requester) of the requested and agreed-upon authorization information.

[0087] Then, the target authorization controller in the requesting party can initialize the authorization configuration information according to the authorization information requested and agreed upon by the requesting party, so that the target authorization controller can perform authorization control and algorithm calculation based on the authorization configuration information.

[0088] In addition, the target authorization controller in the requesting party can initialize identity information and a local key. Specifically, the identity information can be the binding relationship between the target authorization controller's identity information and the requesting party's identity information, ensuring the traceability of the operation, thereby enhancing trust and transparency, and improving privacy protection. The local key is used to encrypt the target data (which includes at least one of authorization configuration information and battery status parameters) before the target authorization controller records it during the algorithm calculation process, ensuring the security of the target data. For example, before uploading the target data to the blockchain network, the target authorization controller can use the initialized local key to encrypt the target data, and then upload the encrypted target data to the blockchain network, ensuring not only the security but also the traceability of the target data. Before recording the target data in the configuration database (used to record the target authorization controller's authorization configuration information, algorithm calculation results, etc.), the target authorization controller can use the initialized local key to encrypt the target data to prevent the data recorded in the configuration database from being tampered with, ensuring data security.

[0089] The reliability and accuracy of obtaining authorization configuration information are improved by initializing authorization configuration information based on authorization information requested and agreed upon by the requester, and privacy protection is enhanced by initializing identity information and local keys.

[0090] According to some embodiments of this application, the algorithm request may include an algorithm request interface and algorithm request parameters;

[0091] The algorithm request parameters may include the requester's ID, algorithm information, authorization information, and first signature; the algorithm information may include the algorithm name and / or algorithm code, the authorization information may include the authorization type and authorization scope, and the authorization scope may include at least one of the following: device ID list, validity period, expiration time, number of calls, and total quantity.

[0092] In this embodiment, the algorithm request sent by the requester may specifically include an algorithm request interface and algorithm request parameters. The algorithm request parameters may include the requester's ID, algorithm information, authorization information, and a first signature; that is, the authorization information requested by the requester may be included in the algorithm request. The algorithm information may specifically include the algorithm name and / or algorithm code. The authorization information may include the authorization type and authorization scope; the authorization type may include: permanent authorization, subscription authorization, and floating authorization; the authorization scope may include: a list of device IDs, valid time, expiration time, number of calls, and total quantity, meaning these authorization scopes can be used in combination. The first signature may be obtained by signing the requester ID, algorithm information, and authorization information to ensure data integrity, authenticity, non-repudiation, security, and support for data traceability and auditing.

[0093] For example, the interface and parameters of the algorithm request can be: requestAlgorithm(requester ID, algorithm name, algorithm code, authorization type, authorization scope, first signature). The authorization scope includes options such as device ID list, validity period, expiration time, number of calls, and total number. These authorization scope options can be used in combination.

[0094] The above method not only includes authorization information in the algorithm request, but also ensures data integrity, authenticity, non-repudiation, security, and supports data traceability and auditing through the first signature.

[0095] According to some embodiments of this application, before obtaining measurement data based on the target battery state parameter estimation algorithm, the following may also be included:

[0096] Map the parameter fields configured in the target battery state parameter estimation algorithm to the parameter fields in the measurement database;

[0097] The measurement data obtained based on the target battery state parameter estimation algorithm may include:

[0098] Based on the mapping results, obtain the measurement data corresponding to the battery state parameter estimation algorithm from the measurement database.

[0099] In this embodiment, considering that the parameter fields in the measurement database may differ from those configured in the battery state parameter estimation algorithm—for example, for the voltage field, the voltage field configured in the battery state parameter estimation algorithm may be Vol, while the actual voltage field in the measurement database may be V—in order to accurately obtain the measurement data corresponding to the battery state parameter estimation algorithm, the scheduler in the requesting party can perform mapping based on the algorithm requirements and the configuration of the actual data model before obtaining the measurement data according to the target battery state parameter estimation algorithm. Specifically, the parameter fields configured in the target battery state parameter estimation algorithm (these parameter fields are used to input the battery state parameter estimation algorithm for battery state parameter calculation) are mapped to the parameter fields in the measurement database to obtain the mapping result. Then, the scheduler in the requesting party can obtain the measurement data corresponding to the target battery state parameter estimation algorithm from the measurement database according to the mapping result, thereby improving the accuracy of obtaining the measurement data corresponding to the target battery state parameter estimation algorithm.

[0100] Through the above process, the requesting party can request the algorithm provider's algorithm call based on a unified data standard and model, ensuring data security and privacy protection. After authorization, the algorithm can be called locally to calculate the battery algorithm result. The data does not leave the local machine during the entire calculation process, thus ensuring data security and privacy.

[0101] According to some embodiments of this application, receiving a target battery state parameter estimation algorithm sent from a target smart contract may include:

[0102] Receive the encrypted target battery state parameter estimation algorithm sent by the target smart contract; the target smart contract may include the first algorithm decryption key parameter;

[0103] Methods for determining battery state parameters may also include:

[0104] The system receives the first algorithm decryption key parameter sent by the target smart contract, generates the second algorithm decryption key parameter based on the first algorithm decryption key parameter, verifies the second algorithm decryption key parameter by the target authorization controller, and decrypts the encrypted target battery state parameter estimation algorithm using the second algorithm decryption key parameter after the verification is passed.

[0105] or,

[0106] The target smart contract receives the second algorithm decryption key parameter sent by the target smart contract. The target authorization controller verifies the second algorithm decryption key parameter and, after successful verification, uses the second algorithm decryption key parameter to decrypt the encrypted target battery state parameter estimation algorithm. The second algorithm decryption key parameter is generated by the target smart contract based on the first algorithm decryption key parameter.

[0107] In this embodiment, the algorithm provider can encrypt and store the verified, high-precision battery state parameter estimation algorithm in a smart contract. That is, the battery state parameter estimation algorithm is encrypted and stored in the smart contract by the algorithm provider, meaning the smart contract contains the encrypted battery state parameter estimation algorithm to protect it and ensure its security. Additionally, the smart contract also includes a first algorithm decryption key parameter corresponding to the encrypted battery state parameter estimation algorithm. This first key parameter is used to generate a second algorithm decryption key parameter, which is then used to decrypt the encrypted battery state parameter estimation algorithm. It should be noted that, in some embodiments of this application, the cryptographic algorithms for encrypting and decrypting the battery state parameter estimation algorithm, signing (first signature, subsequent second signature and third signature), and protecting the algorithm can employ secure cryptographic algorithms and sufficiently strong key lengths. For example, the encryption algorithm can use AES (Advanced Encryption Standard), SM (Commercial Cryptography) 2, SM4, etc., and the key length can be no less than 256 bits. The RSA (Rivest-Shamir-Adleman algorithm) can use 4096 bits, and the hash algorithm can use Sha256 or higher to ensure the security of the algorithm encryption and signing.

[0108] Building upon the above, the target smart contract downloads the target battery state parameter estimation algorithm to the requester, specifically by downloading an encrypted version of the algorithm, thus protecting it. Correspondingly, the requester receives the encrypted target battery state parameter estimation algorithm sent by the target smart contract.

[0109] Furthermore, considering that the first algorithm decryption key parameter is stored in the smart contract, other parties may also be able to obtain the first algorithm decryption key parameter and decrypt the encrypted target battery state parameter estimation algorithm. Therefore, to further enhance the protection and security of the target battery state parameter estimation algorithm, after determining that the requester meets the authorization conditions, the target smart contract can generate a second algorithm decryption key parameter based on the first algorithm decryption key parameter, and download the second algorithm decryption key parameter along with the encrypted target battery state parameter estimation algorithm to the requester. Alternatively, after determining that the requester meets the authorization conditions, the target smart contract can download the first algorithm decryption key parameter along with the encrypted target battery state parameter estimation algorithm to the requester, and then the requester can generate the second algorithm decryption key parameter based on the first algorithm decryption key parameter.

[0110] Accordingly, before calculating the battery state parameters using measurement data and the target battery state parameter estimation algorithm based on the authorization configuration information, the target authorization controller in the requesting party can also verify the second algorithm decryption key parameter. For example, the verification can be achieved through at least one of the following methods: decryption test (i.e., decrypting the encrypted target battery state parameter estimation algorithm using the second algorithm decryption key parameter), the characteristics of the second algorithm decryption key parameter itself, or professional tools. If the second algorithm decryption key parameter passes the verification, it indicates that the second algorithm decryption key parameter is valid and correct. At this point, the target authorization controller in the requesting party can generate the corresponding local authorization and use the second algorithm decryption key parameter to decrypt the encrypted target battery state parameter estimation algorithm to obtain the decrypted target battery state parameter estimation algorithm. Then, the battery state parameters can be calculated using measurement data and the decrypted target battery state parameter estimation algorithm based on the authorization configuration information.

[0111] The above method ensures that the target battery state parameter estimation algorithm is authorized and protected during remote operation, thereby improving the security and reliability of the target battery state parameter estimation algorithm and thus improving the accuracy and stability of battery state parameter calculation.

[0112] As can be seen from the above embodiments of this application, this application is based on a blockchain distributed system. The algorithm provider encrypts and protects the verified, highly accurate battery state parameter estimation algorithm in a smart contract. The requesting party, based on a unified data standard and model, and with data security and privacy protection, requests the algorithm provider's algorithm call. After authorization, the requesting party calls the smart contract algorithm locally to calculate the battery algorithm result. The data does not leave the local machine during the entire calculation process. The algorithm is authorized and protected during remote operation, ensuring both algorithm security and data privacy. This enables different participants and algorithm providers to conduct distributed and efficient collaboration based on a trusted and verifiable blockchain network, thereby maximizing the value of the data.

[0113] Furthermore, this application, based on distributed systems and data standards, utilizes the full lifecycle data of multiple batteries and related devices owned by multiple parties, under the premise of compliance, data security, and privacy protection, to achieve standardization, authorization and protection, shared computing, efficient collaboration and application of battery state parameter estimation algorithms, and to complete a fair and reasonable value distribution.

[0114] According to some embodiments of this application, before obtaining measurement data based on the target battery state parameter estimation algorithm, the following may also be included:

[0115] In response to the resource requirements of the target battery state parameter estimation algorithm, the corresponding computing resources are configured to the target authorized controller.

[0116] In this embodiment, before acquiring measurement data based on the battery state parameter estimation algorithm, the requesting party can configure corresponding computing resources to the target authorized controller according to the resource requirements of the target battery state parameter estimation algorithm (specifically, the types of resources required and the magnitude of various resource requirements, etc.). Specifically, the scheduler in the requesting party can request corresponding computing resources from the requesting party based on the resource requirements of the target battery state parameter estimation algorithm, and configure the corresponding computing resources to the target authorized controller. This ensures that the target authorized controller in the requesting party has sufficient computing resources to run the target battery state parameter estimation algorithm, achieves reasonable allocation of computing resources, avoids competition for computing resources, thereby improving the reliability, efficiency, and stability of the target battery state parameter estimation algorithm and improving resource utilization efficiency.

[0117] According to some embodiments of this application, before sending an algorithm request to a target smart contract in a blockchain network, the following may also be included:

[0118] After its identity is verified by the blockchain network, it joins the blockchain network;

[0119] Sending an algorithm request to a target smart contract in a blockchain network can include:

[0120] Send algorithm requests to the target smart contract in the blockchain network through the blockchain interface.

[0121] In this embodiment of the application, before the requester sends an algorithm request to the target smart contract in the blockchain network, the blockchain network can authenticate the requester. If the requester passes the authentication, the requester can join the blockchain network. Then, the requester can send the algorithm request to the target smart contract in the blockchain network through the blockchain interface.

[0122] The above methods can ensure the legality and validity of transactions, as well as their immutability and traceability.

[0123] According to some embodiments of this application, obtaining measurement data based on a target battery state parameter estimation algorithm, and then having a target authorization controller in the requesting party calculate battery state parameters using the measurement data and the target battery state parameter estimation algorithm based on authorization configuration information, may include:

[0124] The target battery state parameter estimation algorithm is used to obtain a list of device IDs from the measurement database, so that the target authorized controller in the requesting party can determine a valid list of device IDs based on the list of device IDs and the authorized configuration information.

[0125] The corresponding measurement data is obtained from the measurement database based on the list of valid device IDs, so that the target authorized controller can call the target battery state parameter estimation algorithm and use the target battery state parameter estimation algorithm and measurement data to calculate the battery state parameters.

[0126] In this embodiment of the application, the process by which the requesting party obtains measurement data according to the target battery state parameter estimation algorithm, and the target authorized controller in the requesting party calculates the battery state parameters using the measurement data and the target battery state parameter estimation algorithm based on the authorized configuration information, can be as follows:

[0127] Step 100: The scheduler in the requesting party prefetches a list of device IDs that need to be executed from the measurement database based on the target battery state parameter estimation algorithm, and the measurement database returns the list of device IDs that need to be executed to the scheduler in the requesting party.

[0128] Step 101: The scheduler in the requesting party requests the target authorized controller in the requesting party with a list of device IDs and algorithm information (e.g., algorithm code) of the target battery state parameter estimation algorithm as parameters.

[0129] Step 102: After receiving a request from the scheduler with a list of device IDs and algorithm information as parameters, the target authorization controller in the requesting party retrieves the authorization configuration information corresponding to the parameters contained in the request from the configuration database.

[0130] Step 103: The target authorization controller in the requesting party verifies the list of device IDs based on the authorization configuration information, determines the list of valid device IDs (i.e. the list of device IDs that have been verified), and returns the list of valid device IDs to the scheduler.

[0131] Specifically, the target authorization controller in the requesting party can read the device_id list and authorization summary table from the configuration database. Based on the device_id list and authorization summary table in the configuration database, as well as the algorithm information and device ID list sent by the scheduler, it determines the list of valid device IDs from the device ID list sent by the scheduler. The list of valid device IDs may contain valid device IDs, or it may contain the device ID list sent by the scheduler and an identifier indicating whether each device ID in the list is valid. Furthermore, if the device ID list sent by the scheduler to the target authorization controller also includes information such as the number of device ID request calls and / or the request call time, the list of valid device IDs returned by the target authorization controller to the scheduler may correspondingly include the number of valid calls and / or the verified call time.

[0132] Step 104: The scheduler obtains valid device IDs based on the list of valid device IDs returned by the target authorized controller, retrieves the measurement data corresponding to the valid device IDs from the measurement database, and the measurement database returns the measurement data corresponding to the valid device IDs to the scheduler.

[0133] Step 105: The scheduler sends the acquired measurement data to the target authorized controller.

[0134] Step 106: The target authorization controller calls the corresponding target battery state parameter estimation algorithm and uses the target battery state parameter estimation algorithm and measurement data to calculate the battery state parameters.

[0135] The above method enables the target authorized controller to authorize the device ID list sent by the scheduler based on the authorization configuration information, and to call the target battery state parameter estimation algorithm to calculate the battery state parameters, thereby improving the security of data and calculation and preventing data leakage.

[0136] According to some embodiments of this application, the target authorization controller in the requesting party determines a valid list of device IDs based on a device ID list and authorization configuration information, which may include:

[0137] The target authorization controller in the requesting party performs a cross-validation operation based on the device ID list and authorization configuration information to determine the valid device ID list.

[0138] In this embodiment, after the target authorization controller obtains the corresponding authorization configuration information from the configuration database, it can specifically perform a cross-validation operation on the authorization configuration information and the device ID list sent by the scheduler. That is, it can compare and analyze the authorization configuration information and the device ID list to find common parts, and then determine the valid device ID list based on the cross-validation operation results.

[0139] For example, if the device ID list sent by the scheduler contains three device IDs A, B, and C, and the authorization configuration information contains five device IDs A, B, C, D, and E, then the cross-validation result is that device IDs A, B, and C are valid, meaning these three device IDs in the device ID list are valid and authorization is granted. Alternatively, if device ID A in the device ID list sent by the scheduler has 5 request calls, and the authorization configuration information contains 2 authorization calls for device ID A, then the cross-validation result is that device ID A has 2 valid call calls. In this case, the valid device ID list returned by the authorization controller to the scheduler can contain device ID A with 2 valid call calls.

[0140] The above methods can improve the accuracy of determining the list of valid device IDs.

[0141] According to some embodiments of this application, after the target authorization controller in the requesting party performs a cross-validation operation based on the device ID list and authorization configuration information, it may further include:

[0142] The target authorization controller in the requesting party updates the corresponding authorization configuration information in the configuration database based on the cross-validation operation results.

[0143] After the target authorization controller in the requesting party performs a cross-validation operation based on the device ID list and authorization configuration information, it can also update the corresponding authorization configuration information in the configuration database according to the cross-validation operation results. This improves the accuracy of the corresponding authorization configuration information records in the configuration database, thereby improving the accuracy of authorization calculation for the requesting party and enhancing the reliability and security of authorization calculation.

[0144] According to some embodiments of this application, after the target authorization controller in the requesting party determines the valid list of device IDs based on the device ID list and authorization configuration information, it may further include:

[0145] The target authorization controller in the requesting party sends a valid list of device IDs and a second signature obtained by signing the valid list of device IDs to the scheduler in the requesting party.

[0146] After retrieving the corresponding measurement data from the measurement database based on a valid list of device IDs, it may also include:

[0147] The target authorized controller in the requesting party receives the measurement data, the list of verified device IDs, and the second signature sent by the scheduler in the requesting party. It verifies the second signature and, after successful verification, executes the steps of calling the target battery state parameter estimation algorithm and calculating the battery state parameters using the target battery state parameter estimation algorithm and the measurement data.

[0148] In this embodiment, after the target authorization controller in the requesting party determines the valid device ID list based on the device ID list and authorization configuration information, it can sign the valid device ID list to obtain a second signature. Then, the target authorization controller can send the valid device ID list and the second signature together to the scheduler in the requesting party.

[0149] After obtaining the list of valid device IDs and the second signature sent by the target authorized controller, the scheduler can retrieve the valid device IDs based on the list of valid device IDs returned by the target authorized controller and obtain the measurement data corresponding to the valid device IDs from the measurement database. Then, when sending the measurement data to the target authorized controller, the scheduler can specifically send the measurement data, the list of valid device IDs, and the second signature together.

[0150] Before invoking the target battery state parameter estimation algorithm, the target authorization controller can verify the second signature by decrypting it. If decryption fails, the second signature is invalid; if decryption succeeds, the original hash value indicates the second signature is valid. The controller then hashes the list of valid device IDs sent by the scheduler to obtain a new hash value. If the original hash value matches the new hash value, the list of valid device IDs has not been tampered with; otherwise, it indicates the list has been tampered with. Verification fails if the second signature decryption fails, or if the second signature decryption succeeds but the original hash value does not match the new hash value. Verification succeeds if the second signature decryption succeeds and the original hash value matches the new hash value. If verification fails, it indicates the second signature is invalid or the list of valid device IDs may have been tampered with. To ensure the reliability and security of the authorization, the authorization controller can refuse to execute the call to the target battery state parameter estimation algorithm and proceed with the steps of calculating the battery state parameters using the target battery state parameter estimation algorithm and measurement data. If the signature verification is successful, it indicates that the second signature is legitimate and the device ID list has not been tampered with. At this point, the authorized controller can execute the steps of calling the target battery state parameter estimation algorithm and using the target battery state parameter estimation algorithm and measurement data to calculate the battery state parameters.

[0151] The scheduler signs the list of valid device IDs by the target authorization controller, and then sends the list of device IDs and their signatures along with the measurement data to the target authorization controller. The signature verification by the target authorization controller can improve the reliability and security of authorization and calculation.

[0152] When verifying the second signature, the target authorization controller can also determine whether the device ID of the measurement data matches the valid device IDs in the list of valid device IDs. If they match, it indicates that the scheduler has indeed obtained measurement data with a valid device ID. In this case, if the signature verification is successful and the device ID of the measurement data matches the valid device IDs in the list of valid device IDs, the target authorization controller executes the steps of calling the target battery state parameter estimation algorithm and calculating the battery state parameters using the target battery state parameter estimation algorithm and the measurement data. If the verification fails, it indicates that the scheduler has not obtained measurement data with a valid device ID. Therefore, if the signature verification fails and / or the device ID of the measurement data does not match the valid device IDs in the list of valid device IDs, the target authorization controller refuses to execute the steps of calling the target battery state parameter estimation algorithm and calculating the battery state parameters using the target battery state parameter estimation algorithm and the measurement data.

[0153] Additionally, after the target authorization controller sends the list of valid device IDs and the second signature to the scheduler, the scheduler can also verify the second signature. If the verification is successful, the step of retrieving the measurement data corresponding to the valid device ID from the measurement database is executed; if the verification fails, the step of retrieving the measurement data corresponding to the valid device ID from the measurement database is refused to be executed, thus ensuring the security of the measurement data.

[0154] According to some embodiments of this application, after the target authorization controller in the requesting party determines the valid list of device IDs based on the device ID list and authorization configuration information, it may further include:

[0155] The target authorization controller in the requesting party sends a list of device IDs, an identifier indicating whether each device ID in the list is valid, a timestamp, and a third signature obtained by signing the list of device IDs, the identifier, and the timestamp to the scheduler in the requesting party.

[0156] After retrieving the corresponding measurement data from the measurement database based on a valid list of device IDs, it may also include:

[0157] The target authorized controller in the requesting party receives the measurement data, device ID list, identifier, timestamp and third signature sent by the scheduler in the requesting party. It verifies the third signature, verifies whether the device ID of the measurement data and the device ID of the identifier that has been verified are consistent, and verifies whether the timestamp is within the preset range. After all verifications are passed, it executes the steps of calling the target battery state parameter estimation algorithm and using the target battery state parameter estimation algorithm and measurement data to calculate the battery state parameters.

[0158] In this embodiment, after determining a valid list of device IDs based on the device ID list and authorization configuration information, the target authorization controller in the requesting party can determine whether each device ID in the list is valid, generate an identifier indicating whether each device ID is valid, generate a timestamp, and sign the device ID list, the identifier indicating whether each device ID is valid, and the timestamp to generate a third signature. Then, the target authorization controller can send the device ID list, the identifier indicating whether each device ID in the list is valid, the timestamp, and the third signature generated by signing the first three items to the scheduler in the requesting party.

[0159] After receiving the information sent by the target authorized controller, the scheduler can obtain valid devices based on the device ID list returned by the target authorized controller and retrieve the measurement data corresponding to the valid device IDs from the measurement database. Then, when sending the measurement data to the target authorized controller, the scheduler can send the measurement data, the device ID list, an identifier indicating whether each device ID in the device ID list is valid, a timestamp, and a third signature together with the target authorized controller.

[0160] Based on the above, the target authorized controller can also verify the third signature before calling the target battery state parameter estimation algorithm; and it can verify whether the device ID of the measurement data is consistent with the device ID identified as valid; moreover, it can verify whether the timestamp is within a preset range. The preset range can be set in advance based on experience or needs, for example, it can be 10 minutes, so as to avoid the time spent on the series of actions of sending the device ID list, identification and other information to the scheduler, the scheduler obtaining the measurement data, and the scheduler sending the measurement data to the target authorized controller.

[0161] If the signature verification is successful, the device ID and identifier of the measurement data match a valid device ID, and the timestamp is within a preset range, it indicates that the third signature is valid, the device ID list, identifier, and timestamp have not been tampered with, and the scheduler has indeed obtained measurement data with valid device IDs, along with the device ID list, identifier, and other information, which are then sent to the scheduler. If the time spent on this series of actions—sending the measurement data to the target authorized controller—is within a reasonable range, the target authorized controller can then execute the steps of calling the target battery state parameter estimation algorithm and calculating the battery state parameters using the algorithm and the measurement data. If at least one of the following occurs: signature verification fails, the device ID and identifier of the measurement data do not match, or the timestamp is outside the preset range, the target authorized controller will refuse to execute the steps of calling the target battery state parameter estimation algorithm and calculating the battery state parameters using the algorithm and the measurement data.

[0162] The target authorization controller signs the device ID list, the validity identifier of each device ID in the device ID list, and the timestamp. The scheduler sends the device ID list, the validity identifier of each device ID in the device ID list, the timestamp, and the signature along with the measurement data to the target authorization controller. The signature verification by the target authorization controller can improve the reliability and security of authorization and calculation.

[0163] According to some embodiments of this application, obtaining a list of device IDs from a measurement database based on a target battery state parameter estimation algorithm may include:

[0164] A DAG plan is generated based on the target battery state parameter estimation algorithm, and a list of device IDs is obtained from the measurement database based on the DAG plan.

[0165] In this embodiment of the application, the specific process of obtaining the device ID list from the measurement database according to the target battery state parameter estimation algorithm can be as follows: First, a DAG (Directed Acyclic Graph) plan can be generated according to the task scheduling information configured by the target battery state parameter estimation algorithm. Then, the device ID list can be obtained from the measurement database according to the DAG plan, so as to achieve orderly acquisition of the device ID list and orderly task calculation, thereby improving the efficiency of battery state parameter calculation.

[0166] In addition, after authorizing the calculation and obtaining the battery status parameters, the scheduler in the requesting party can save a record of the task scheduling throughout the process (such as the scheduling of the device corresponding to the device ID, the acquisition of measurement data, and multiple tasks corresponding to the battery status parameter estimation algorithm, etc.), and support statistical call details and billing.

[0167] For example, referring to Figure 3, which is a flowchart of algorithm authorization and invocation in some embodiments of this application, the algorithm authorization and invocation process can specifically be as follows:

[0168] ① Initialize configuration;

[0169] Specifically, the authorization controller initializes identity information and authorization configuration information in the configuration database;

[0170] ② Authorization controller local key initialization;

[0171] ③ The local scheduler generates the DAG plan;

[0172] ④ This scheduler prefetches a list of device IDs from the measurement database based on the DAG plan;

[0173] ⑤ The measurement database returns a list of device IDs for which the algorithm needs to be executed;

[0174] ⑥ The local scheduler requests authorization from the controller with a list of device IDs and algorithm codes as parameters;

[0175] ⑦ The authorization controller reads authorization configuration information data from the configuration database;

[0176] Specifically, the authorization controller reads the device_id list and the authorization summary table from the configuration database to return a valid list of device IDs and the signature of the list, and then verifies the validity of the signature.

[0177] ⑧ The authorization controller performs cross-validation on the read authorization configuration information data and the device ID list;

[0178] ⑨ Update the data in the configuration database based on the cross-validation results;

[0179] ⑩ The authorized controller returns a list of device IDs, an indicator indicating whether each device ID has been verified, a timestamp, and a signature for the first three items;

[0180] Specifically, the authorization controller can return: {[device_id1,flag],[device_id2,flag],[device_id3,flag],,,},timestamp,signature;

[0181] The local scheduler verifies the devices based on the device ID list returned by the authorized controller and retrieves the corresponding measurement data from the measurement database.

[0182] The local scheduler obtains measurement data from the verified devices from the measurement database;

[0183] Steps The obtained measurement data and the list of steps 10, along with a signature, are used as parameters to call the authorization controller to start algorithm scheduling;

[0184] The authorized controller verifies the signature field in the parameters; whether the device ID in the measurement data matches the device ID in the signature field; and whether the timestamp is within a reasonable range (e.g., 10 minutes).

[0185] If they match, the algorithm will be invoked for further processing;

[0186] The algorithm's calculation results are returned to the local scheduler. The local scheduler stores task scheduling records and supports statistics on call details and billing.

[0187] This application also provides a battery state parameter determination device, applied to a requester. Referring to Figure 4, which is a structural schematic diagram of a battery state parameter determination device according to some embodiments of this application, the battery state parameter determination device 40 may include: a sending module 41, used to send an algorithm request to a target smart contract in the blockchain network, and receive a target battery state parameter estimation algorithm sent from the target smart contract when it meets the authorization conditions of the target smart contract; and an acquisition module 42, used to acquire measurement data according to the target battery state parameter estimation algorithm, so that the target authorization controller in the requester can calculate the battery state parameters using the measurement data and the target battery state parameter estimation algorithm according to the authorization configuration information.

[0188] According to some embodiments of this application, the algorithm request may include an algorithm request interface and algorithm request parameters;

[0189] The algorithm request parameters may include the requester's ID, algorithm information, and first signature; the algorithm information may include the algorithm name and / or algorithm code.

[0190] According to some embodiments of this application, the battery state parameter determination device 40 may further include: an acquisition module, configured to acquire a target authorization controller before acquiring measurement data according to a target battery state parameter estimation algorithm, so that the target authorization controller in the requesting party can calculate the battery state parameters using the measurement data and the target battery state parameter estimation algorithm based on the authorization configuration information. The target authorization controller initializes the authorization configuration information and initializes the identity information and local key according to the authorization information requested and agreed upon by the requesting party.

[0191] According to some embodiments of this application, the algorithm request may include an algorithm request interface and algorithm request parameters;

[0192] The algorithm request parameters may include the requester's ID, algorithm information, authorization information, and first signature; the algorithm information may include the algorithm name and / or algorithm code, the authorization information may include the authorization type and authorization scope, and the authorization scope may include at least one of the following: device ID list, validity period, expiration time, number of calls, and total quantity.

[0193] According to some embodiments of this application, the battery state parameter determination device 40 may further include: a mapping module, used to map the parameter fields configured by the target battery state parameter estimation algorithm to the parameter fields in the measurement database before acquiring measurement data according to the target battery state parameter estimation algorithm;

[0194] The acquisition module 42 may include: a first acquisition submodule, used to acquire the measurement data corresponding to the battery state parameter estimation algorithm from the measurement database according to the mapping result.

[0195] According to some embodiments of this application, the sending module 41 may include: a first receiving submodule, used to receive an encrypted target battery state parameter estimation algorithm sent by the target smart contract; the target smart contract may include a first algorithm decryption key parameter.

[0196] The sending module 41 may further include: a second receiving submodule, configured to receive the first algorithm decryption key parameter sent by the target smart contract, generate a second algorithm decryption key parameter based on the first algorithm decryption key parameter, have the second algorithm decryption key parameter verified by the target authorization controller, and, after successful verification, use the second algorithm decryption key parameter to decrypt the encrypted target battery state parameter estimation algorithm; or, receive the second algorithm decryption key parameter sent by the target smart contract, have the second algorithm decryption key parameter verified by the target authorization controller, and, after successful verification, use the second algorithm decryption key parameter to decrypt the encrypted target battery state parameter estimation algorithm; the second algorithm decryption key parameter is generated by the target smart contract based on the first algorithm decryption key parameter.

[0197] According to some embodiments of this application, the battery state parameter determination device 40 may further include: a configuration module, configured to configure corresponding computing resources to the target authorization controller in response to the resource requirements of the target battery state parameter estimation algorithm before acquiring measurement data according to the target battery state parameter estimation algorithm.

[0198] According to some embodiments of this application, the battery state parameter determination device 40 may further include: a joining module, used to join the blockchain network after its own identity verification by the blockchain network before sending an algorithm request to the target smart contract in the blockchain network;

[0199] The sending module 41 may include: a first sending submodule, used to send an algorithm request to a target smart contract in the blockchain network through a blockchain interface.

[0200] According to some embodiments of this application, the acquisition module 42 may include: a second acquisition submodule, configured to acquire a list of device IDs from a measurement database according to a target battery state parameter estimation algorithm, so that the target authorization controller in the requesting party can determine a valid list of device IDs based on the list of device IDs and authorization configuration information; and a third acquisition submodule, configured to acquire corresponding measurement data from a measurement database according to the valid list of device IDs, so that the target authorization controller can call the target battery state parameter estimation algorithm and calculate the battery state parameters using the target battery state parameter estimation algorithm and the measurement data.

[0201] According to some embodiments of this application, the target authorization controller in the requesting party determines a valid list of device IDs based on a device ID list and authorization configuration information, which may include:

[0202] The target authorization controller in the requesting party performs a cross-validation operation based on the device ID list and authorization configuration information to determine the valid device ID list.

[0203] According to some embodiments of this application, after the target authorization controller in the requesting party performs a cross-validation operation based on the device ID list and authorization configuration information, it may further include:

[0204] The target authorization controller in the requesting party updates the corresponding authorization configuration information in the configuration database based on the cross-validation operation results.

[0205] According to some embodiments of this application, after the target authorization controller in the requesting party determines the valid list of device IDs based on the device ID list and authorization configuration information, it may further include:

[0206] The target authorization controller in the requesting party sends a valid list of device IDs and a second signature obtained by signing the valid list of device IDs to the scheduler in the requesting party.

[0207] After retrieving the corresponding measurement data from the measurement database based on a valid list of device IDs, it may also include:

[0208] The target authorized controller in the requesting party receives the measurement data, the list of verified device IDs, and the second signature sent by the scheduler in the requesting party. It verifies the second signature and, after successful verification, executes the steps of calling the target battery state parameter estimation algorithm and calculating the battery state parameters using the target battery state parameter estimation algorithm and the measurement data.

[0209] According to some embodiments of this application, after the target authorization controller in the requesting party determines the valid list of device IDs based on the device ID list and authorization configuration information, it may further include:

[0210] The target authorization controller in the requesting party sends a list of device IDs, an identifier indicating whether each device ID in the list is valid, a timestamp, and a third signature obtained by signing the list of device IDs, the identifier, and the timestamp to the scheduler in the requesting party.

[0211] After retrieving the corresponding measurement data from the measurement database based on a valid list of device IDs, it may also include:

[0212] The target authorized controller in the requesting party receives the measurement data, device ID list, identifier, timestamp and third signature sent by the scheduler in the requesting party. It verifies the third signature, verifies whether the device ID of the measurement data and the device ID of the identifier that has been verified are consistent, and verifies whether the timestamp is within the preset range. After all verifications are passed, it executes the steps of calling the target battery state parameter estimation algorithm and using the target battery state parameter estimation algorithm and measurement data to calculate the battery state parameters.

[0213] According to some embodiments of this application, the second acquisition submodule may include: an acquisition unit, configured to generate a DAG plan based on a target battery state parameter estimation algorithm, and acquire a list of device IDs from a measurement database based on the DAG plan.

[0214] This application also provides an electronic device that may include a memory and a processor. The memory stores a computer program; the processor executes the computer program stored in the memory to implement the steps of any of the battery state parameter determination methods described above.

[0215] This application also provides a readable storage medium storing a computer program, which, when executed by a processor, can implement the steps of any of the above-described battery state parameter determination methods.

[0216] This application also provides a computer program product, which may include a computer program that, when executed by a processor, can implement the steps of any of the above-described battery state parameter determination methods.

[0217] For a description of the relevant parts of the battery state parameter determination device, apparatus, readable storage medium and computer program product provided in this application, please refer to the detailed description of the corresponding parts of the battery state parameter determination method provided in this application, and will not be repeated here.

[0218] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of this application, and not to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some or all of the technical features therein. These modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of this application, and they should all be covered within the scope of the claims and specification of this application. In particular, as long as there is no structural conflict, the various technical features mentioned in the embodiments can be combined in any way. This application is not limited to the specific embodiments disclosed herein, but includes all technical solutions falling within the scope of the claims.

Claims

1. A method for determining battery state parameters, characterized in that, Applied to the requester, including: Send an algorithm request to the target smart contract in the blockchain network, and when it meets the authorization conditions of the target smart contract, receive the target battery state parameter estimation algorithm sent by the target smart contract; Measurement data is obtained based on the target battery state parameter estimation algorithm, and the target authorization controller in the requesting party calculates the battery state parameters using the measurement data and the target battery state parameter estimation algorithm based on the authorization configuration information.

2. The method for determining battery state parameters according to claim 1, characterized in that, The algorithm request includes an algorithm request interface and algorithm request parameters; The algorithm request parameters include the requester's ID, algorithm information, and first signature; the algorithm information includes the algorithm name and / or algorithm code.

3. The method for determining battery state parameters according to claim 1 or 2, characterized in that, Before acquiring measurement data according to the target battery state parameter estimation algorithm, and before the target authorization controller in the requesting party calculates the battery state parameters using the measurement data and the target battery state parameter estimation algorithm based on the authorization configuration information, the process further includes: Obtain the target authorization controller, so that the target authorization controller initializes the authorization configuration information according to the authorization information requested and agreed upon by the requester, and initializes the identity information and local key.

4. The method for determining battery state parameters according to claim 3, characterized in that, The algorithm request includes an algorithm request interface and algorithm request parameters; The algorithm request parameters include the requester's ID, algorithm information, authorization information, and a first signature; the algorithm information includes the algorithm name and / or algorithm code; the authorization information includes the authorization type and authorization scope; and the authorization scope includes at least one of the following: a list of device IDs, an effective time, an expiration time, the number of calls, and the total number.

5. The method for determining battery state parameters according to any one of claims 1 to 4, characterized in that, Before obtaining measurement data according to the target battery state parameter estimation algorithm, the method further includes: Map the parameter fields configured in the target battery state parameter estimation algorithm to the parameter fields in the measurement database; Measurement data is obtained based on the target battery state parameter estimation algorithm, including: Based on the mapping results, the measurement data corresponding to the target battery state parameter estimation algorithm is obtained from the measurement database.

6. The method for determining battery state parameters according to any one of claims 1 to 5, characterized in that, The target battery state parameter estimation algorithm received from the target smart contract includes: The system receives the encrypted target battery state parameter estimation algorithm sent by the target smart contract; the target smart contract includes a first algorithm decryption key parameter. The method further includes: The system receives the first algorithm decryption key parameter sent by the target smart contract, generates a second algorithm decryption key parameter based on the first algorithm decryption key parameter, verifies the second algorithm decryption key parameter by the target authorization controller, and decrypts the encrypted target battery state parameter estimation algorithm using the second algorithm decryption key parameter after the verification is passed. or, The target authorization controller receives the second algorithm decryption key parameter sent by the target smart contract, verifies the second algorithm decryption key parameter, and decrypts the encrypted target battery state parameter estimation algorithm using the second algorithm decryption key parameter after the verification is successful; the second algorithm decryption key parameter is generated by the target smart contract based on the first algorithm decryption key parameter.

7. The method for determining battery state parameters according to any one of claims 1 to 6, characterized in that, Before obtaining measurement data based on the target battery state parameter estimation algorithm, the method further includes: In response to the resource requirements of the target battery state parameter estimation algorithm, corresponding computing resources are configured for the target authorization controller.

8. The method for determining battery state parameters according to any one of claims 1 to 7, characterized in that, Before sending an algorithm request to the target smart contract in the blockchain network, the following steps are also included: After its identity is verified by the blockchain network, it joins the blockchain network; Sending algorithmic requests to the target smart contract in the blockchain network, including: The algorithm request is sent to the target smart contract in the blockchain network through the blockchain interface.

9. The method for determining battery state parameters according to any one of claims 1 to 8, characterized in that, Measurement data is obtained according to the target battery state parameter estimation algorithm, and the target authorization controller in the requesting party calculates battery state parameters using the measurement data and the target battery state parameter estimation algorithm based on the authorization configuration information, including: The target battery state parameter estimation algorithm is used to obtain a list of device IDs from the measurement database, so that the target authorization controller in the requesting party can determine a valid list of device IDs based on the list of device IDs and the authorization configuration information. Based on the list of valid device IDs, the corresponding measurement data is obtained from the measurement database, so that the target authorized controller can call the target battery state parameter estimation algorithm and use the target battery state parameter estimation algorithm and the measurement data to calculate the battery state parameters.

10. The method for determining battery state parameters according to claim 9, characterized in that, The target authorization controller in the requesting party determines a valid list of device IDs based on the device ID list and the authorization configuration information, including: The target authorization controller in the requesting party performs a cross-validation operation based on the device ID list and the authorization configuration information to determine the valid device ID list.

11. The method for determining battery state parameters according to claim 10, characterized in that, After the target authorization controller in the requesting party performs a cross-validation operation based on the device ID list and the authorization configuration information, it also includes: The target authorization controller in the requesting party updates the corresponding authorization configuration information in the configuration database based on the cross-validation operation result.

12. The method for determining battery state parameters according to any one of claims 9 to 11, characterized in that, After the target authorization controller in the requesting party determines the valid device ID list based on the device ID list and the authorization configuration information, it also includes: The target authorization controller in the requesting party sends a valid list of device IDs and a second signature obtained by signing the valid list of device IDs to the scheduler in the requesting party. After retrieving the corresponding measurement data from the measurement database based on the valid device ID list, the process also includes: The target authorization controller in the requesting party receives the measurement data, the list of verified device IDs, and the second signature sent by the scheduler in the requesting party, verifies the second signature, and executes the step of calling the target battery state parameter estimation algorithm and calculating the battery state parameters using the target battery state parameter estimation algorithm and the measurement data after the signature is verified.

13. The method for determining battery state parameters according to any one of claims 9 to 11, characterized in that, After the target authorization controller in the requesting party determines the valid device ID list based on the device ID list and the authorization configuration information, it also includes: The target authorization controller in the requesting party sends the device ID list, an identifier indicating whether each device ID in the device ID list is valid, a timestamp, and a third signature obtained by signing the device ID list, the identifier, and the timestamp to the scheduler in the requesting party. After retrieving the corresponding measurement data from the measurement database based on the valid device ID list, the process also includes: The target authorization controller in the requesting party receives the measurement data, the device ID list, the identifier, the timestamp, and the third signature sent by the scheduler in the requesting party. It verifies the third signature, checks whether the device ID of the measurement data and the device ID of the identifier that has passed verification are consistent, and verifies whether the timestamp is within a preset range. After all verifications are passed, it executes the step of calling the target battery state parameter estimation algorithm and calculating the battery state parameters using the target battery state parameter estimation algorithm and the measurement data.

14. The method for determining battery state parameters according to any one of claims 9 to 13, characterized in that, The target battery state parameter estimation algorithm is used to obtain a list of device IDs from the measurement database, including: A DAG plan is generated based on the target battery state parameter estimation algorithm, and a list of device IDs is obtained from the measurement database based on the DAG plan.

15. A battery state parameter determination device, characterized in that, Applied to the requester, including: The sending module is used to send algorithm requests to the target smart contract in the blockchain network, and when it meets the authorization conditions of the target smart contract, it receives the target battery state parameter estimation algorithm sent by the target smart contract. The acquisition module is used to acquire measurement data according to the target battery state parameter estimation algorithm, so that the target authorization controller in the requesting party can use the measurement data and the target battery state parameter estimation algorithm to calculate the battery state parameters according to the authorization configuration information.

16. An electronic device, characterized in that, include: Memory, used to store computer programs; A processor, configured to execute the computer program to implement the steps of the battery state parameter determination method as described in any one of claims 1 to 14.

17. A readable storage medium, characterized in that, The readable storage medium stores a computer program that, when executed by a processor, implements the steps of the battery state parameter determination method as described in any one of claims 1 to 14.

18. A computer program product, characterized in that, It includes a computer program, which, when executed by a processor, implements the steps of the battery state parameter determination method as described in any one of claims 1 to 14.

Images