An event-driven based power battery chain asset management method and system

Abstract

The application discloses a kind of power battery chain asset management method and system based on event-driven, belong to the field of blockchain technology and internet of things traceability.The method includes: active oracle under blockchain obtains current state parameter of battery, based on health state cumulative drift rule and remaining life span crossing rule is calculated, only when threshold condition is satisfied, trigger single on-chain transaction;Smart contract on blockchain receives transaction, executes the check based on hash pointer, uses "snapshot-log" hybrid storage mechanism, only maintains the latest state snapshot in state tree, historical trajectory data is sunk to the event log of blockchain.The application is filtered and minimalist storage design by end chain cooperation on demand, under the premise of strictly guaranteeing data tamper-proof and time sequence continuity, successfully eliminates invalid redundant interaction in gentle period, greatly reduces long-term operating cost, solves the contradiction of high on-chain storage and gas consumption cost in power battery long-period traceability.

Description

Technical Field

[0001] This invention relates to the fields of blockchain technology, Internet of Things, and data storage and traceability technology. Specifically, it relates to an event-driven on-chain asset management method and system for power batteries. Background Technology

[0002] Against the backdrop of the rapid development of the new energy vehicle industry, establishing a trusted data management system for the entire lifecycle of power batteries, from production, use, secondary utilization to recycling and dismantling, is of great significance for ensuring battery safety, assessing residual value, and promoting resource recycling. Blockchain technology, due to its decentralized, immutable, and traceable characteristics, is widely considered a potential solution for building trust infrastructure in multi-party scenarios.

[0003] Currently, common technical approaches to applying blockchain to battery traceability fall into two main categories. The first approach focuses on building a complete traceability chain, such as integrating all stakeholders in the battery production process through a consortium blockchain and storing data from each stage on the blockchain. While this approach aims to ensure data integrity, it typically requires writing a large amount, or even all, of condition monitoring data to the blockchain, resulting in high on-chain storage and computation costs (in public blockchains such as Ethereum, this cost manifests as gas consumption, i.e., blockchain transaction fees). For power batteries with lifecycles spanning several years and high-frequency condition monitoring, this cost is often unsustainable. The second approach focuses on using data models for advanced analysis of battery condition, such as predicting battery capacity degradation trends and implementing load balancing control through algorithms. However, the prediction and decision-making logic of this approach usually runs entirely within a centralized system under the blockchain, and its processes and results lack the immutability and verifiability provided by the blockchain, making it difficult to directly serve as a reliable basis for subsequent asset transactions, insurance pricing, or policy subsidies.

[0004] Furthermore, existing blockchain-based implementations often suffer from limitations in smart contract design. For example, to trace history, contracts often use arrays or mappings to store all historical state records, causing the contract state data volume to continuously expand over time (i.e., the "state bloat" problem), further increasing long-term operation and maintenance costs. At the same time, data storage and business logic are often coupled in the same contract, making system upgrades and strategy adjustments extremely difficult.

[0005] Therefore, existing technologies have failed to effectively resolve the contradiction between high-frequency data and high-cost storage on the blockchain, as well as the disconnect between intelligent decision-making and trusted execution on the blockchain. There is an urgent need for an innovative technological solution that can reliably anchor key business events throughout the battery lifecycle to the blockchain in an economically feasible manner, triggering complex on-chain value logic. Summary of the Invention

[0006] To address the shortcomings of existing technologies, this invention provides an event-driven on-chain asset management method and system for power batteries. This invention aims to resolve engineering challenges in power battery traceability, such as data redundancy caused by fixed-frequency storage, on-chain state bloat, and high gas consumption interaction costs, through the atomic collaboration of intelligent sensing filtering under the blockchain and a simplified hash-based evidence storage architecture on the blockchain.

[0007] To solve the above-mentioned technical problems, the present invention adopts the following technical solution:

[0008] In a first aspect, the present invention provides an event-driven on-chain asset management method for power batteries, which is executed collaboratively by an active oracle deployed on the blockchain and smart contracts deployed on the blockchain. The method includes: The active oracle acquires the current state parameters of the power battery; The active oracle makes a judgment based on the current state parameters and preset triggering rules; If the triggering rules are met, the active oracle initiates a single transaction to the blockchain network, invoking the smart contract; In response to the call, the smart contract performs atomic operations, which include: Based on the hash value of the preceding record contained in the transaction, perform a tamper-proof verification of the cryptographic hash pointer; after the tamper-proof verification passes, update the latest state snapshot of the power battery on the blockchain based on the current state parameters; Historical trajectory data containing information about this status change will be uploaded to the event log of the blockchain to complete a reliable traceability record of the power battery's status throughout its entire life cycle.

[0009] Furthermore, the triggering rules include health status decline rules and remaining lifespan crossing rules; The health status decay rule is as follows: the active oracle continuously calculates the cumulative state drift between the current health status assessment value of the power battery and the latest health status value stored on the blockchain. When the cumulative state drift exceeds the preset decay threshold, the trigger condition is determined to be met. The remaining lifespan crossing rule is as follows: a preset key lifespan set is defined. When the current remaining lifespan prediction value of the power battery crosses any lifespan node in the key lifespan set downwards, it is determined that the trigger condition is met. Specifically, the triggering rule is determined to be satisfied when either the health status decline rule or the remaining lifespan crossing rule is met.

[0010] Furthermore, the triggering rules also include a risk threshold fallback rule; If the current health status assessment value or the current remaining lifespan prediction value in the current status parameters is lower than the preset risk threshold, it is determined that the triggering condition is met.

[0011] Furthermore, the degradation threshold, the critical lifetime set, and the risk threshold are dynamically configurable parameters.

[0012] Furthermore, the smart contract employs a hybrid "snapshot-log" evidence storage mechanism: The latest state snapshot is stored in the state tree of the blockchain and contains only the current state information of the power battery; the historical trajectory data is not written to the state tree of the blockchain, but is instead pushed down to the event log through the log opcode of the virtual machine.

[0013] Furthermore, the tamper-proof verification of the cryptographic hash pointer includes: Assume that the hash value of the preceding record in the transaction is equal to the hash value of the current record in the latest state snapshot stored on the blockchain; and verify that the number of cycles of the power battery in the transaction is greater than the number of cycles stored on the blockchain. If any assertion or verification fails, the transaction is rolled back.

[0014] Furthermore, before the active oracle initiates a transaction, the method further includes converting the floating-point type current state parameter into an integer value with a preset precision; and before the smart contract updates the latest state snapshot, the method further includes verifying that the integer value is within a valid physical value range.

[0015] Secondly, the present invention provides an event-driven on-chain asset management system for power batteries, comprising: The active oracle module, deployed on the blockchain, is used to obtain current state parameters and initiate transaction calls based on triggering rules; The smart contract module, deployed on the blockchain, integrates a hash verification unit and a state tracing unit. The hash verification unit is used to verify the consistency between the temporal monotonicity and the previous hash pointer, and the state tracing unit is used to update the latest state snapshot and generate the blockchain's event log after the verification is passed.

[0016] Thirdly, the present invention provides an electronic device including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor, when executing the program, implements the method as described in any of the first aspects.

[0017] Fourthly, the present invention provides a computer-readable storage medium having a computer program stored thereon that, when executed by a processor, implements the method as described in any of the first aspects.

[0018] The beneficial effects of this invention are: 1. Significantly Reduced Operation and Storage Costs on the Blockchain: This invention breaks away from the traditional model of fixed-frequency, full-volume on-chain data for IoT traceability. By introducing business value perception rules such as health status decline thresholds and remaining lifespan spans on the blockchain, low-value redundant data during the gradual degradation period of batteries is effectively eliminated. Compared to traditional periodic on-chain strategies, this invention can independently reduce redundant blockchain interactions and gas consumption by approximately 16%. Simultaneously, the "snapshot-log" hybrid structure on the blockchain sinks massive historical trajectories to the blockchain's event log, completely avoiding the problem of smart contract state tree bloat.

[0019] 2. Enhanced absolute data consistency and tamper-proof capabilities: This invention employs a smart contract architecture, packaging tamper-proof hash verification, snapshot updates, and blockchain event logs into atomic operations within a single transaction. Combined with a one-way chain dependency mechanism based on cryptographic hash pointers, any tampering of historical data or attempts to replay attacks will result in forced assertion failure and transaction rollback, thus providing a high level of traceability security for cross-entity collaboration with minimal evidence storage overhead.

[0020] 3. Adaptive sampling distribution with risk awareness: Thanks to the threshold triggering mechanism, the system's data sampling exhibits an adaptive characteristic of being sparse during healthy periods and dense during dangerous periods. While ensuring that no critical degradation events are missed in the tracking of core battery assets, it achieves refined and differentiated tracking management of assets with different degradation modes, improving the economic feasibility and risk control capabilities of the traceability system. Attached Figure Description

[0021] Figure 1 This is a schematic diagram of the overall architecture provided for one embodiment of the present invention.

[0022] Figure 2 A flowchart for triggering judgment of business value perception is provided in one embodiment of the present invention.

[0023] Figure 3 This is a schematic diagram comparing the traditional storage mode and the event tracing storage mode provided in one embodiment of the present invention.

[0024] Figure 4 This is a schematic diagram comparing the total Gas consumption under different schemes provided in one embodiment of the present invention.

[0025] Figure 5 A scatter plot comparing the sampling distribution of different schemes provided in the embodiments of the present invention. Detailed Implementation

[0026] To make the objectives, technical solutions, and advantages of this invention clearer, the specific embodiments of this invention will be described in detail below with reference to the accompanying drawings. It should be understood that the specific embodiments described herein are only for explaining this invention and are not intended to limit the scope of protection of this invention. All other embodiments obtained by those skilled in the art based on the embodiments of this invention without inventive effort are within the scope of protection of this invention.

[0027] Example 1: End-to-End Collaboration Architecture and Single-Contract Atomic Traceability Main Process This embodiment corresponds to the core system architecture of the present invention and the method defined by the present invention, and describes the basic workflow of the present invention.

[0028] See Figure 1 The present invention adopts a layered decoupled architecture, which mainly includes an active oracle deployed under the blockchain and a smart contract deployed on the blockchain.

[0029] At the underlying perception layer of the blockchain, the active oracle connects to the power battery or its backend management system to obtain the current state parameters of the power battery. These current state parameters primarily include the current state of health (SOH) assessment value, which characterizes the degree of battery aging, and the current remaining useful life (RUL) prediction value.

[0030] After acquiring the data, the active oracle does not write all time-series data into the blockchain at high frequency, but filters and selects based on pre-set triggering rules (see Example 2 for details).

[0031] The active oracle generates and initiates a single transaction to the blockchain network only if the triggering rule is met.

[0032] At the blockchain layer, a smart contract responsible for evidence storage and traceability is deployed. Responding to the aforementioned call, this smart contract rigorously executes atomic operations within a transaction context of a blockchain execution environment such as the Ethereum Virtual Machine. These atomic operations ensure that the following steps either all succeed or are rolled back entirely in the event of an exception: Step 1: Perform tamper-proof verification based on cryptographic hash pointers.

[0033] Step 2: If the verification passes, use the current state parameters to overwrite and update the latest state snapshot of the power battery in the state tree.

[0034] Step 3: Using the virtual machine's log opcodes, the data containing complete details of this update is pushed down to the blockchain's event log, completing the persistence of trusted traceability records.

[0035] By atomically executing a single smart contract, this invention completely eliminates the overhead of cross-smart contract calls, and physically guarantees the consistency of state transitions and data storage on the blockchain.

[0036] Example 2: Multi-level Triggering Algorithm for Active Oracles in Blockchain This embodiment further details the specific structure of the triggering rules based on state transitions in an active oracle.

[0037] like Figure 2 As shown, to filter redundant data during the smooth period of the Internet of Things (IoT), the triggering rule includes two independent state transition rules and a safety fallback rule: (1) Health Status Decline Rule: Considering the non-linear and gradual evolution of the State of Health (SOH) of the power battery during its life cycle, the active oracle continuously calculates the cumulative state drift (ΔSOH) between the current SOH assessment value of the power battery and the latest successfully anchored SOH assessment value on the blockchain. Only when the cumulative state drift exceeds the set decline threshold is the trigger condition determined and an on-chain request initiated. Under actual engineering constraints, this embodiment preferably sets the decline threshold to 0.01 (i.e., 1% of the rated capacity decay) to achieve the best trade-off between tracking accuracy and interaction cost.

[0038] (2) Remaining Lifetime Crossing Rule: To prevent single-point tracking errors from causing missed critical nodes during the final stage of battery aging (the "drop-in" phase), the proactive oracle introduces a milestone crossing detection mechanism. This invention predefines a set of critical lifetimes containing multiple integer cycle counts (e.g., 100, 75, 50, 25, 0 cycles). This set of critical lifetimes can be dynamically configured according to battery characteristics or business needs, for example, setting differentiated milestone nodes for different battery chemistry systems (e.g., lithium iron phosphate, ternary lithium). When the predicted current remaining lifetime (RUL) of the power battery crosses any of the aforementioned critical lifetime nodes downwards, the trigger condition is deemed met. This rule ensures that the frequency of state verification automatically increases as the battery approaches the end of its lifespan.

[0039] (3) Risk threshold fallback rule: If the current health status (SOH) assessment value or the current remaining useful life (RUL) prediction value in the current status parameters is lower than the preset risk threshold (e.g., the current health status (SOH) assessment value is lower than the scrapping standard), the above drift amount will be ignored, and the on-chain transaction will be forcibly triggered to ensure the reliable anchoring of the high-risk status of the asset.

[0040] It should be noted that the degradation threshold, critical life set, and risk threshold are all dynamically configurable parameters that can be adjusted according to different battery models, application scenarios, or operational strategies. This invention does not impose any specific limitations on them.

[0041] Example 3: A Hash Chain Anti-Tampering and Lightweight Hybrid Evidence Storage Structure on the Blockchain This embodiment elaborates on the storage optimization design and security verification mechanism of smart contracts on the blockchain.

[0042] See Figure 3 In the traditional storage model, smart contracts need to store all historical data (including state record 1 to state record N). As the power battery operates throughout its entire life cycle, the amount of data continues to accumulate, resulting in huge on-chain storage overhead and high gas consumption costs.

[0043] The event tracing storage mode of this invention adopts a "snapshot-log" hybrid evidence storage mechanism based on event tracing: Latest State Snapshot: Only the latest state snapshot of the power battery (such as the current health status assessment value, the current remaining service life prediction value, and the current record hash value) is stored in the blockchain state tree, and only the latest item is retained. This approach ensures that the core state is always available, and the storage cost remains constant, unaffected by the growth of historical data.

[0044] Virtual machine event log chain: Complete historical trajectory data of state changes is stored at the bottom and recorded in the blockchain event log through the log opcode of the blockchain virtual machine. Each new event log not only contains the information of this change, but also the hash value of the previous record, forming a one-way hash pointer chain. Thus, while storing the data at the bottom, the immutability, temporal continuity and end-to-end traceability of the data are still guaranteed.

[0045] To address the problem of excessive data bloat in smart contract state caused by traditional full array storage, this invention employs a "snapshot-log" hybrid evidence storage mechanism based on event sourcing. In the expensive state tree of a blockchain, the smart contract maintains only one up-to-date state snapshot for each power battery's unique device identifier on the blockchain. This snapshot includes the current cycle count, the current State of Health (SOH) assessment value / current Remaining Lifetime (RUL) prediction value, and the current record hash value. Historical trajectory data is not written to the state tree but is instead stored in a storage medium beneath the blockchain. This storage medium utilizes the Ethereum Virtual Machine's Event Logs, achieving low-cost storage through log opcodes (such as the emit instruction in the Solidity language).

[0046] To ensure the cryptographically immutable nature of data sinking to the event log, this invention constructs a hash chain mechanism. Before each transaction is initiated, an active oracle retrieves the hash value of the current record from the latest state snapshot on the blockchain through a query interface, and uses this hash value as the preceding hash parameter for the next on-chain transaction. Current record hash value The calculation rules are as follows: ; in, This represents a pre-defined cryptographic one-way hash function operation. For the hash value of the preceding record, This represents a byte string concatenation operation. This represents the unique device identifier of the power battery on the blockchain. This indicates the number of charge-discharge cycles of the power battery in its current state. This represents the current health status assessment value submitted by the active oracle, after being converted to fixed-point precision. This represents the current remaining lifetime prediction value submitted by the active oracle, after being rounded down. This indicates the timestamp of the current block when the current state update transaction was initiated.

[0047] Before updating to the latest state snapshot, the smart contract performs anti-tampering verification: First, it forcibly asserts that the hash value of the preceding record of the transaction must be strictly equal to the hash value of the current record in the latest state snapshot already stored on the blockchain; second, it forcibly verifies that the number of loops in the transaction is strictly greater than the number of loops already stored on the blockchain. If either assertion or verification fails, the smart contract triggers a transaction rollback, rejecting the current state update. This verification mechanism ensures that any attempt to tamper with historical data or launch a replay attack will fail the verification, thus guaranteeing the cryptographical immutability of the data under a minimalist evidence storage architecture.

[0048] Furthermore, to adapt to the security requirements of the limited instruction set and fixed-point arithmetic of the blockchain virtual machine, the active oracle converts the floating-point prediction value into an integer value with a preset precision before initiating a transaction (for example, converting the health status assessment value into a thousandth of a integer in the range of 0 to 1000). Before the smart contract receives the transaction and executes atomic operations and updates the latest state snapshot, the method also includes: performing domain constraint verification on the physical legality of the integer value to determine whether it is within a reasonable range allowed by the battery's physical characteristics, in order to prevent integer overflow attacks caused by abnormal data.

[0049] Example 4: Experimental Results and Verification To verify the technical effectiveness of this invention, controlled experiments and prototype verification were conducted on the Ethereum Sepolia testnet. The tests comprehensively compared the threshold-triggered event-driven architecture of this invention with the current industry baseline solution (i.e., a forced on-chain strategy every 10 fixed periods).

[0050] The experiment tracks battery lifecycle data and records gas consumption for on-chain transactions. For example... Figure 4 As shown in the bar chart comparing the total cumulative Gas consumption, the event-driven strategy of this invention demonstrates a significant cost reduction advantage compared to the traditional fixed-frequency strategy. Data indicates that, while ensuring the average error of state tracking meets engineering risk control constraints, the solution of this invention effectively eliminates redundant data during the battery health plateau, reducing the number of interactions on the blockchain by approximately 16%. The corresponding total Gas consumption decreases from 0.1717 ETH to 0.1442 ETH, saving 16.02% of on-chain costs.

[0051] At the same time, such as Figure 5 As shown in the scatter plot comparing the sampling distribution, the adaptive sampling distribution of this invention exhibits a significant "risk perception" characteristic: sparse sampling occurs during healthy and gradual degradation periods when the health status assessment value is greater than 80%; while significantly increased sampling frequency occurs during capacity-draining periods when the health status assessment value is below 80%, forming a refined tracking mode of "sparse during healthy periods and dense during dangerous periods." This fully demonstrates that this invention, while minimizing on-chain storage and gas consumption in long-term IoT assets, rigorously ensures reliable and tamper-proof tracking of key degradation characteristics and high-risk asset states.

[0052] The above description is merely a specific embodiment of the present invention, but the scope of protection of the present invention is not limited thereto. Any person skilled in the art, within the technical scope disclosed in this invention, can easily conceive of various equivalent modifications or substitutions (e.g., adjusting the specific value of the trigger threshold, changing the conversion precision of the fixed-point number, or adopting equivalent hash verification instructions with different underlying blockchain architectures, etc.), all of which should be covered within the scope of protection of this invention. Therefore, the scope of protection of this invention should be determined by the claims.

Claims

1. An event-driven method for managing assets on a power battery chain, characterized in that, The method, executed collaboratively by an active oracle deployed on the blockchain and smart contracts deployed on the blockchain, includes: The active oracle acquires the current state parameters of the power battery; The active oracle determines whether the triggering rules are met based on the current state parameters and preset triggering rules. If the triggering rules are met, the active oracle initiates a single transaction to the blockchain network, invoking the smart contract; In response to the call, the smart contract performs atomic operations, which include: Based on the hash value of the preceding record contained in the transaction, perform a tamper-proof verification of the cryptographic hash pointer; after the tamper-proof verification passes, update the latest state snapshot of the power battery on the blockchain based on the current state parameters; Historical trajectory data containing information about this status change will be uploaded to the event log of the blockchain to complete a reliable traceability record of the power battery's status throughout its entire life cycle.

2. The method according to claim 1, characterized in that, The triggering rules include health status decline rules and remaining lifespan crossing rules; The health status decay rule is as follows: the active oracle continuously calculates the cumulative state drift between the current health status assessment value of the power battery and the latest health status value stored on the blockchain. When the cumulative state drift exceeds the preset decay threshold, the trigger condition is determined to be met. The remaining lifespan crossing rule is as follows: a preset key lifespan set is defined. When the current remaining lifespan prediction value of the power battery crosses any lifespan node in the key lifespan set downwards, it is determined that the trigger condition is met. Specifically, the triggering rule is determined to be satisfied when either the health status decline rule or the remaining lifespan crossing rule is met.

3. The method according to claim 2, characterized in that, The triggering rules also include a risk threshold fallback rule; If the current health status assessment value or the current remaining lifespan prediction value in the current status parameters is lower than the preset risk threshold, it is determined that the triggering condition is met.

4. The method according to claim 3, characterized in that, The degradation threshold, the critical lifetime set, and the risk threshold are dynamically configurable parameters.

5. The method according to claim 1, characterized in that, The smart contract employs a hybrid "snapshot-log" evidence storage mechanism: The latest state snapshot is stored in the state tree of the blockchain and contains only the current state information of the power battery; the historical trajectory data is not written to the state tree of the blockchain, but is instead pushed down to the event log through the log opcode of the virtual machine.

6. The method according to claim 1, characterized in that, The tamper-proof verification of the cryptographic hash pointer includes: Assume that the hash value of the preceding record in the transaction is equal to the hash value of the current record in the latest state snapshot stored on the blockchain; and verify that the number of cycles of the power battery in the transaction is greater than the number of cycles stored on the blockchain. If any assertion or verification fails, the transaction will be rolled back.

7. The method according to claim 1, characterized in that, Before the active oracle initiates a transaction, the method further includes converting the floating-point type current state parameter into an integer value with a preset precision; and before the smart contract updates the latest state snapshot, the method further includes verifying that the integer value is within a valid physical value range.

8. An event-driven on-chain asset management system for power batteries, used to execute an event-driven on-chain asset management method for power batteries as described in any one of claims 1-7, characterized in that, include: The active oracle module, deployed on the blockchain, is used to obtain current state parameters and initiate transaction calls based on triggering rules; The smart contract module, deployed on the blockchain, integrates a hash verification unit and a state tracing unit. The hash verification unit is used to verify the consistency between the temporal monotonicity and the previous hash pointer, and the state tracing unit is used to update the latest state snapshot and generate the blockchain's event log after the verification is passed.

9. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the program, it implements the method as described in any one of claims 1 to 7.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the program is executed by the processor, it implements the method as described in any one of claims 1 to 7.

Images