Description:TECHNICAL FIELD
[0001] The present subject matter relates generally to one or more batteries. More particularly but not exclusively, the present invention relates to a method of traceability of each component of one or more batteries of a battery module.
BACKGROUND
[0002] Traditionally, there is no way to track the internal components of the battery and no way to trace certain parameters of the battery over the complete lifecycle of the battery.
[0003] Only a serial number for the battery is available, however there is no way that the authenticity and traceability of the battery along the complete lifecycle of the battery could be tracked. Further, there is no traceability for battery components and secure way of auditing. Additionally, the batch code is only with the manufacturer and can be edited if any mishap happens. Auditability for the same is not available.
[0004] Ideally, each battery manufactured should have a traceability document in which the details of cells, Battery Management System (hereinafter referred to as BMS), charger used along with serial/batch number, charge discharge data values etc. should be maintained with the Rechargeable energy storage system (hereinafter referred to as REESS) manufacturer. Traditionally, there is no way to track the internal components of the battery and no way to trace certain parameters of the battery over the complete lifecycle of the battery. Only a serial number for the battery is available for access and reference, however, there is no way that we can track the authenticity and traceability of the battery along the complete lifecycle of the battery.
SUMMARY OF THE INVENTION
[0005] In one embodiment, a method for generating a traceability document in a distributed ledger network is disclosed. The method comprises receiving, by a plurality of nodes in the distributed ledger network, a plurality of parameters from a Battery management system (BMS) of an energy storage device. The method further comprises identifying, by one of the plurality of nodes in the distributed ledger network, a set of participating nodes from the plurality of nodes within the distributed ledger network using at least one consensus technique. The method further comprises creating, by the set of participating nodes of the plurality of nodes in the distributed ledger network, an unverified block in a local ledger of each of the set of participating nodes. In an embodiment, the unverified block comprises at least one new transaction in the distributed ledger network. In an embodiment, the least one new transaction comprises the plurality of parameters of the energy storage device. The method further comprises computing, by each of the set of participating nodes, a hash value for each of the at least one new transaction in the distributed ledger network. The method further comprises performing, by each of the set of participating nodes, consensus based on the computed hash value for identifying a set of valid transactions in the unverified blocks created by each of the set of participating nodes. The method further comprises creating, by a consensus node of the set of participating nodes, a verified block comprising the set of valid transactions. In an embodiment, the consensus node identifies the set of valid transactions in the shortest time when compared with the remaining set of participating nodes. The method further comprises committing, by the consensus node of the set of participating nodes, the verified block to a distributed ledger in the distributed ledger network. The method further comprises generating, by one of the plurality of nodes in the distributed ledger network, an energy storage device traceability document based on the verified block after successful authentication. In an embodiment, the energy storage device traceability document comprises information stored in the set of verified blocks of the plurality of verified blocks in the distributed ledger which is associated with a unique code of the energy storage device.
[0006] In one embodiment, a system to generate a traceability document in a distributed ledger network is disclosed. In one example, the system may include a processor and a computer-readable medium communicatively coupled to the processor. The computer-readable medium may store processor-executable instructions, which, on execution, cause the processor to receive, by a plurality of nodes in the distributed ledger network, a plurality of parameters from a Battery management system (BMS) of an energy storage device. The processor-executable instructions, on execution, further cause the processor to identify, by one of the plurality of nodes in the distributed ledger network, a set of participating nodes from the plurality of nodes within the distributed ledger network using at least one consensus technique. The processor-executable instructions, on execution, further cause the processor to create, by the set of participating nodes of the plurality of nodes in the distributed ledger network, an unverified block in a local ledger of each of the set of participating nodes, wherein the unverified block comprises at least one new transaction in the distributed ledger network. In an embodiment, the least one new transaction comprises the plurality of parameters of the energy storage device. The processor-executable instructions, on execution, further cause the processor to compute, by each of the set of participating nodes, a hash value for each of the at least one new transaction in the distributed ledger network. The processor-executable instructions, on execution, further cause the processor to perform, by each of the set of participating nodes, consensus based on the computed hash value for identifying a set of valid transactions in the unverified blocks created by each of the set of participating nodes. The processor-executable instructions, on execution, further cause the processor to create, by a consensus node of the set of participating nodes, a verified block comprising the set of valid transactions. In an embodiment, the consensus node identifies the set of valid transactions in the shortest time when compared with the remaining set of participating nodes. The processor-executable instructions, on execution, further cause the processor to commit, by the consensus node of the set of participating nodes, the verified block to a distributed ledger in the distributed ledger network. The processor-executable instructions, on execution, further cause the processor to generate, by one of the plurality of nodes in the distributed ledger network, an energy storage device traceability document based on the verified block after successful authentication. In an embodiment, the energy storage device traceability document comprises information stored in the set of verified blocks of the plurality of verified blocks in the distributed ledger which is associated with a unique code of the energy storage device.
BRIEF DESCRIPTION OF THE DRAWINGS
[0007] The detailed description is described with reference to the accompanying figures. The same numbers are used throughout the drawings to reference like features and components.
[0008] FIGURE 1 is a block diagram that illustrates a system environment 100 in which various embodiments of the method and the system may be implemented, in accordance with at least one embodiment.
[0009] FIGURE 2 illustrates a block diagram of a node of the distributed ledger network that is configured for generating the traceability document in the distributed ledger network, in accordance with an embodiment.
[00010] FIGURE 3 illustrates a block diagram of a sample block structure in the distributed ledger network, in accordance with an embodiment of the invention.
[00011] FIGURE 4 illustrates a sample diagram of three block structure in the distributed ledger network, in accordance with an embodiment of the invention.
[00012] FIGURE 5 illustrates a flowchart of a method for generating the traceability document in the distributed ledger network is illustrated, in accordance with an embodiment.
[00013] FIGURE 6 illustrates a flowchart of a method performed by a user computing device for generating the traceability document in the distributed ledger network is illustrated, in accordance with an embodiment.
DETAILED DESCRIPTION
[00014] As of today, there is no secure way of tracing the battery. Batch code is with only manufacturer and can be edited if any mishap happens. No auditability has been associated with tracing of battery packs.
[00015] Blockchain-based EV battery tracking is a system that uses blockchain technology to record and track the history of electric vehicle (EV) batteries. By using a decentralized and immutable ledger, the system can provide a transparent and secure record of a battery's ownership, usage, maintenance, and performance. This can help increase the trust and confidence in the reliability and safety of EV batteries, which is important for the wider adoption of electric vehicles.
[00016] Blockchain-based EV battery tracking is a system that uses blockchain technology to record and track the history of electric vehicle (EV) batteries. By using a decentralized and immutable ledger, the system can provide a transparent and secure record of a battery's ownership, usage, maintenance, and performance. This can help increase the trust and confidence in the reliability and safety of EV batteries, which is important for the wider adoption of electric vehicles.
[00017] To track rechargeable batteries using blockchain in accordance with the present disclosure, we can follow these general steps:
[00018] In a first step, assign a unique digital identity to each battery using a unique identifier such as a QR code or RFID tag.
[00019] In a second step, use sensors or battery management systems (BMS) to collect data on the battery's usage, performance, and maintenance history, such as the charge/discharge cycles, temperature, and voltage levels.
[00020] In a third step, store the data on a blockchain network, which can be accessed and verified by authorized parties such as the battery manufacturer, owner, or service provider.
[00021] In a fourth step, use smart contracts to automate the tracking and management of the battery's lifecycle, such as the transfer of ownership, warranty claims, and recycling/disposal.
[00022] In a fifth step, use encryption and secure access controls to protect the privacy and security of the data, and ensure compliance with relevant regulations.
[00023] By using blockchain technology, the battery tracking system can provide a transparent, secure, and tamper-proof record of the battery's history, which can improve trust and confidence in the battery's reliability and safety. Additionally, the system can enable more efficient and sustainable management of the battery lifecycle, such as extending the battery's lifespan and reducing waste.
[00024] FIGURE 1 is a block diagram that illustrates a system environment 100 in which various embodiments of the method and the system may be implemented, in accordance with at least one embodiment. The system environment 100 may include a distributed ledger network 102 comprising a plurality of nodes 106, a communication network 108, and a user-computing device 110. Each of the plurality of nodes 106 are communicatively coupled to a distributed ledger 104. The distributed ledger 104 comprises of one or more blocks 104a, 104b and 104c. The plurality of nodes 106 and the user-computing device 110 may be communicatively coupled with each other via the communication network 108. In an embodiment, the plurality of nodes 106 may communicate with the user-computing device 110 using one or more protocols such as, but not limited to, Open Database Connectivity (ODBC) protocol and Java Database Connectivity (JDBC) protocol.
[00025] In one embodiment, the distributed ledger network 104, in which various embodiments may be employed, is illustrated in FIG. 1. It will be apparent to a person skilled in the art that the invention is not limited to the distributed ledger network 104 and is relevant to all variations and implementations of the distributed ledger network 104, for example, Blockchain network, Hyperledger, Directed Acyclic Graphs (DAG), Holochain, Hashgraph, Tangle, Lattice, and the like.
[00026] The distributed ledger network 104 also includes the plurality of nodes, for example, a node 106a, a node 106b, a node 106c, a node 106d, a node 106e, and a node 106f. It will be apparent to a person skilled in the art that each of the plurality nodes 106 are technically similar to each other and only differ byway of the performed functionalities. Each of the plurality of nodes 106 is capable of running one or more applications and establishing communication with other computing nodes. Examples of nodes may include, but are not limited to a computer, a smart phone, a Personal Digital Assistant (PDA), a laptop, a tablet and so forth.
[00027] In order to initiate a transaction, the node 106a uses cryptographic tools to digitally sign a proposed update to the distributed ledger 104 (which is shared as a copy with each of the plurality of nodes). It may be noted that the distributed ledger 104 may be a database of sequential blocks that record state of each transactions in the distributed ledger network 102. As depicted in FIG. 1, the distributed ledger 104 includes a set of blocks 104 a, 104 b, and 104 c, each of which is immutable. A block may include a plurality of transactions received within a predefined time interval. However, a new block is not committed to the distributed ledger 104 unless a consensus algorithm is executed. Upon obtaining a consensus, the distributed ledger 104 is updated with the new block. In an exemplary scenario, the transaction may correspond to receiving a plurality of parameters received from a Battery management system (BMS) of an energy storage device by the plurality of nodes in the distributed ledger network. In such a scenario, the distributed ledger 104 may be used for creating an immutable record of the energy storage device data in the distributed ledger 104. In an embodiment, IoT based sensors may be implemented in the BMS for transmitting data to the plurality of nodes.
[00028] Upon receiving the plurality of parameters received from a BMS, each of the plurality of nodes may authenticate identity of a sender node and may validate the transaction by checking that the sender node has necessary cryptographic credentials to make an update to the distributed ledger 104. Validation of the transaction may include obtaining a consensus (majority approval) from the plurality of nodes regarding validity of the transaction using a consensus technique. Upon obtaining the consensus, one of the plurality of nodes may create a verified block including the transaction and add the verified block to the copy of the distributed ledger 104 associated with the one of the plurality of computing nodes. Further, the copy of the distributed ledger 104 associated with the one of the plurality of nodes may be broadcasted within the distributed ledger network 102.
[00029] In an embodiment, the plurality of nodes 106 may refer to a computing device or a software framework hosting an application or a software service. In an embodiment, the plurality of nodes 106 may be implemented to execute procedures such as, but not limited to, programs, routines, or scripts stored in one or more memories for supporting the hosted application or the software service. In an embodiment, the hosted application or the software service may be configured to perform one or more predetermined operations. The plurality of nodes 106 may host one or more application servers which may be realized through various types of application servers such as, but are not limited to, a Java application server, a .NET framework application server, a Base4 application server, a PHP framework application server, or any other application server framework.
[00030] In an embodiment, some of the plurality of nodes in the distributed ledger network 102 at a particular time may be at least one of an identifying node, participating node, a consensus node. The identifying node may adaptively select a set of participating nodes for computing a hash value for each of the at least one new transaction in the distributed ledger network. The set of participating nodes is configured to perform consensus based on the computed hash value for identifying a set of valid transactions in the unverified blocks created by each of the set of participating nodes.
[00031] The consensus node is configured to create a verified block comprising the set of valid transactions based on a plurality of predefined node parameters and sampling. Further, the consensus node may validate each block before committing the block to the distributed ledger 104. In an embodiment, each of the plurality of nodes is configured to generate an energy storage device traceability document based on the verified block after successful authentication after receiving a request from an electronic device.
[00032] In an embodiment, the communication network 108 may correspond to a communication medium through which the plurality of nodes 106, and the user-computing device 110 may communicate with each other. Such a communication may be performed, in accordance with various wired and wireless communication protocols. Examples of such wired and wireless communication protocols include, but are not limited to, Transmission Control Protocol and Internet Protocol (TCP/IP), User Datagram Protocol (UDP), Hypertext Transfer Protocol (HTTP), File Transfer Protocol (FTP), ZigBee, EDGE, infrared IR), IEEE 802.11, 802.16, 2G, 3G, 4G, 5G, 6G cellular communication protocols, and/or Bluetooth (BT) communication protocols. The communication network 104 may include, but is not limited to, the Internet, a cloud network, a Wireless Fidelity (Wi-Fi) network, a Wireless Local Area Network (WLAN), a Local Area Network (LAN), a telephone line (POTS), and/or a Metropolitan Area Network (MAN).
[00033] In an embodiment, the user-computing device 110 may refer to a computing device used by a user. The user-computing device 110 may comprise of one or more processors and one or more memories. The one or more memories may include computer readable code that may be executable by the one or more processors to perform predetermined operations. In an embodiment, the user-computing device 110 may present a web user interface to scan a unique code of the energy storage device. Further, the user-computing device 110 may be configured to securely authenticate at least one user using an encrypted private key for providing access to the generated energy storage device traceability document after successful authentication. Examples of the user-computing device 106 may include, but are not limited to, a personal computer, a laptop, a personal digital assistant (PDA), a mobile device, a tablet, or any other computing device. In an embodiment, the data on the distributed ledger network, can be accessed and verified by authorized parties such as the battery manufacturer, owner, or service provider using the user-computing device 110. Further, encryption and secure access controls may be implemented on the user-computing device 110 to protect the privacy and security of the data on the distributed ledger network, and ensure compliance.
[00034] Referring now to FIG. 2, a block diagram of a node 106 of the distributed ledger network 102 that is configured for generating the traceability document in the distributed ledger network 102, in accordance with an embodiment.
[00035] The node 106 may be analogous to each of the plurality of nodes 106a, 106b, 106c, 106d, 106e, 106f. The node 106 includes a processor 202 that is coupled to a memory 204. The memory 204 stores instructions for the processor 202, which, on execution, causes the processor 202 to perform desired operations. The processor 202 may be implemented based on a number of processor technologies known in the art. Some examples of the processor 202 may include, but are not limited to, an X86-based processor, a Reduced Instruction Set Computing (RISC) processor, an Application-Specific Integrated Circuit (ASIC) processor, a Complex Instruction Set Computing (CISC) processor, and the like.
[00036] The processor 202 may be configured to identifying a set of participating nodes from the plurality of nodes within the distributed ledger network using at least one consensus technique. The processor 202 may be configured to create an unverified block in a local ledger of each of the set of participating nodes. The processor 202 may be configured to updating, by the consensus node of the set of participating nodes, in real time at least one of the plurality of parameters based on the real-time date received from the BMS of the energy storage device.
[00037] The memory 204 may be a non-volatile memory or a volatile memory. Examples of the non-volatile memory, may include, but are not limited to a flash memory, a Read Only Memory (ROM), a Programmable ROM (PROM), Erasable PROM (EPROM), and Electrically EPROM (EEPROM) memory. Examples of volatile memory may include, but are not limited to Dynamic Random Access Memory (DRAM), and Static Random-Access memory (SRAM).
[00038] The transceiver 206 may include suitable logic, circuitry, interfaces, and/or code that may be configured to receive data from the user-computing device 110. The transceiver 206 may further be configured to transmit generated traceability document to the user-computing device 110, via the communication network 108. The transceiver 206 may further be configured to broadcast the verified block to the plurality of nodes in the distributed ledger network after committing the verified block to the distributed ledger.
[00039] The transceiver 206 may implement one or more known technologies to support wired or wireless communication with the communication network 108. In an embodiment, the transceiver 206 may include, but is not limited to, an antenna, a radio frequency (RF) transceiver, one or more amplifiers, a tuner, one or more oscillators, a digital signal processor, a Universal Serial Bus (USB) device, a coder-decoder (CODEC) chipset, a subscriber identity module (SIM) card, and/or a local buffer. The transceiver 206 may communicate via wireless communication with networks, such as the Internet, an Intranet and/or a wireless network, such as a cellular telephone network, a wireless local area network (LAN) and/or a metropolitan area network (MAN). The wireless communication may use any of a plurality of communication standards, protocols and technologies, such as: Global System for Mobile Communications (GSM), Enhanced Data GSM Environment (EDGE), wideband code division multiple access (W-CDMA), code division multiple access (CDMA), time division multiple access (TDMA), Bluetooth, Wireless Fidelity (Wi-Fi) (e,g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g and/or IEEE 802.11n), voice over Internet Protocol (VoIP), Wi-MAX, a protocol for email, instant messaging, and/or Short Message Service (SMS).
[00040] The input/output unit 208 may include suitable logic, circuitry, interfaces, and/or code that may be configured to receive an input or transmit an output to the user-computing device 110. The input/output unit 208 may include various input and output devices that are configured to communicate with the processor 202. Examples of the Input devices include, but are not limited to, a keyboard, a mouse, a joystick, a touch screen, a microphone, a camera, and/or a docking station. Examples of the output devices include, but are not limited to, a display screen and/or a speaker.
[00041] The authentication unit 210 may include suitable logic, circuitry, interfaces, and/or code that may be configured to verify/authenticate each of the plurality of nodes based on an encrypted key generated based on a Media Access Control address (MAC address) and a digital signature of the user operating the computing node.
[00042] The code generation unit 212 may include suitable logic, circuitry, interfaces, and/or code that may be configured to register the energy storage device onto the distributed ledger network. The code generation unit 212 may be configured to generating the unique code associated with the energy storage device based on the received plurality of parameters, wherein the unique code is stored in a form of a 2-dimensional code, wherein the 2-dimensional code comprises at least one of a bar code, RFID tag, and a QR code
[00043] The validation unit 214 may include suitable logic, circuitry, interfaces, and/or code that may be configured to compute a hash value for each of the at least one new transaction in the distributed ledger network. The validation unit 214 may be configured to perform consensus based on the computed hash value for identifying a set of valid transactions in the unverified blocks created by each of the set of participating nodes.
[00044] The block creation unit 216 may include suitable logic, circuitry, interfaces, and/or code that may be configured to create a verified block comprising the set of valid transactions. In an embodiment, the consensus node identifies the set of valid transactions in a shortest time when compared with remaining set of participating nodes. The block creation unit 216 may configured to commit the verified block to a distributed ledger in the distributed ledger network
[00045] The traceability document creation unit 218 may include suitable logic, circuitry, interfaces, and/or code that may be configured to generate an energy storage device traceability document based on the verified block after successful authentication. In an embodiment, the energy storage device traceability document comprises information stored in the set of verified blocks of the plurality of verified blocks in the distributed ledger which is associated with a unique code of the energy storage device.

[00046] In operation, the code generation unit 212 may register the energy storage device onto the distributed ledger network. In an embodiment, the distributed ledger network is a private blockchain network or a public blockchain network. Further, the code generation unit 212 may generate the unique code associated with the energy storage device based on the received plurality of parameters. In an embodiment, the unique code is stored in a form of a 2-dimensional code. The 2-dimensional code comprises at least one of a bar code, RFID tag, and a QR code.
[00047] A plurality of nodes in the distributed ledger network is configured to receive a plurality of parameters from a Battery management system (BMS) of an energy storage device. In an embodiment , the plurality of parameters comprises information on the energy storage device’s ownership including date and location of purchase, transfer of ownership, warranty claims, disputes, battery usage details, battery performance, maintenance history, charge/discharge cycles, temperature, voltage levels of the battery, auxiliary performance metrics that can provide insights into the energy storage device’s health and condition, records of any maintenance or repair work done on the energy storage device, including a date, location, and type of work performed. In an embodiment, the distributed ledger comprises a plurality of verified blocks which comprises the plurality of parameters of the energy storage device. By storing the plurality of parameters i.e., battery data on a distributed ledger network, the data becomes a tamper-proof and secure record that can be easily accessed and shared with relevant parties. This can help improve trust and transparency in the battery ecosystem, and enable more efficient and sustainable management of the battery lifecycle.
[00048] In an embodiment, one or more smart contracts or a set of specialized instructions for automatic tracking and management of the energy storage device’s lifecycle may be defined using solidity language. Below is a sample smart contract written in Solidity, which is the most used programming language for developing smart contracts on the Ethereum blockchain for tracking EV batteries on the distributed ledger network.
pragma solidity ^0.8.0;
contract EVBatteryTracking {
// Define a struct to represent a battery's data
struct Battery {
string batteryId;
string owner;
uint256 capacity;
uint256 cycles;
string lastMaintenanceDate;
}
// Define an array to store all the batteries
Battery[] public batteries;
// Define a mapping to keep track of each battery's location in the array
mapping(string => uint256) batteryIndex;

// Event that is emitted when a new battery is registered
event NewBatteryRegistered(string batteryId, string owner);

// Event that is emitted when a battery's data is updated
event BatteryDataUpdated(string batteryId, string owner, uint256 capacity, uint256 cycles, string lastMaintenanceDate);

// Register a new battery on the blockchain
function registerBattery(string memory batteryId, string memory owner) public {
// Check if the battery already exists
require(batteryIndex[batteryId] == 0, "Battery already registered");

// Create a new Battery struct and add it to the array
Battery memory newBattery = Battery(batteryId, owner, 0, 0, "");
batteries.push(newBattery);

// Update the mapping to keep track of the new battery's location in the array
batteryIndex[batteryId] = batteries.length;

// Emit the NewBatteryRegistered event
emit NewBatteryRegistered(batteryId, owner);
}

// Update a battery's data on the blockchain
function updateBatteryData(string memory batteryId, uint256 capacity, uint256 cycles, string memory lastMaintenanceDate) public {
// Check if the battery exists
require(batteryIndex[batteryId] != 0, "Battery not registered");

// Update the battery's data in the array
Battery storage battery = batteries[batteryIndex[batteryId] - 1];
battery.capacity = capacity;
battery.cycles = cycles;
battery.lastMaintenanceDate = lastMaintenanceDate;

// Emit the BatteryDataUpdated event
emit BatteryDataUpdated(batteryId, battery.owner, capacity, cycles, lastMaintenanceDate);
}

// Get a battery's data from the blockchain
function getBatteryData(string memory batteryId) public view returns (string memory, string memory, uint256, uint256, string memory) {
// Check if the battery exists
require(batteryIndex[batteryId] != 0, "Battery not registered");

// Return the battery's data
Battery storage battery = batteries[batteryIndex[batteryId] - 1];
return (battery.batteryId, battery.owner, battery.capacity, battery.cycles, battery.lastMaintenanceDate);
}
}
[00049] The above smart contract defines a Battery struct that represents the data for each EV battery, including its unique identifier (batteryId), owner, capacity, number of charge/discharge cycles, and last maintenance date. It also defines an array to store all the batteries and a mapping to keep track of each battery's location in the array.
[00050] The smart contract includes three functions: registerBattery, updateBatteryData, and getBatteryData. The registerBattery function is used to add a new battery to the array, the updateBatteryData function is used to update a battery's data, and the getBatteryData function is used to retrieve a battery.
[00051] Further, one of the plurality of nodes in the distributed ledger network is configured to identify a set of participating nodes from the plurality of nodes within the distributed ledger network using at least one consensus technique.
[00052] After the identification, the set of participating nodes of the plurality of nodes in the distributed ledger network is configured to create an unverified block in a local ledger of each of the set of participating nodes. In an embodiment, the unverified block comprises at least one new transaction in the distributed ledger network. In an embodiment, the least one new transaction comprises the plurality of parameters of the energy storage device. Further, each of the set of participating nodes is configured to compute a hash value for each of the at least one new transaction in the distributed ledger network.
[00053] After computing the hash value, each of the set of participating nodes is configured to perform consensus based on the computed hash value for identifying a set of valid transactions in the unverified blocks created by each of the set of participating nodes. Further, a consensus node of the set of participating nodes is configured to create a verified block comprising the set of valid transactions. In an embodiment, the consensus node identifies the set of valid transactions in a shortest time when compared with remaining set of participating nodes.
[00054] The consensus node may be configured to implement one or more consensus algorithms to verify and validate transactions before they can be added to the distributed ledger. In an embodiment, the one or more consensus algorithms comprise Proof of Work (PoW), Proof of Stake (PoS), Delegated Proof of Stake (DPoS), Practical Byzantine Fault Tolerance (PBFT).
[00055] Proof of Work (PoW) requires participating nodes to solve complex mathematical puzzles to validate transactions and add blocks to the blockchain. Proof of Stake (PoS) nodes to stake a certain amount of cryptocurrency as collateral, which they may lose if they attempt to validate fraudulent transactions. Delegated Proof of Stake (DPoS) requires nodes to be elected by token holders to validate transactions and add blocks to the blockchain. Practical Byzantine Fault Tolerance (PBFT) require participants to be authorized by a central authority. It allows for fast transaction processing and high throughput, but may be less decentralized than other consensus algorithms.
[00056] In a best mode implementation, Proof of Authority (PoA), is used in private or consortium blockchain networks where a small number of trusted nodes are responsible for validating transactions and creating blocks. In a PoA system, participating nodes are authorized and identified by a central authority, and they take turns creating new blocks based on a predetermined order or schedule.
[00057] In another implementation, for tracing EV batteries Proof of Elapsed Time (PoET) is used, which is designed to minimize the computational resources required for consensus by using a lottery-based system to select the next block creator. In a PoET system, participating nodes compete to be selected as the next block creator, but only one node is chosen at random to create each block. This approach can help reduce the energy consumption associated with consensus in blockchain systems, making it an attractive option for tracking EV batteries.
[00058] In another implementation, for tracing EV batteries Proof of Space-Time (PoST), Proof of Burn (PoB), and Proof of History (PoH), may also be implemented depending on the specific needs and requirements of the EV battery tracing system. Further, Proof of Stake (PoS), is an alternative to the energy-intensive Proof of Work (PoW). PoS requires participants to hold a certain amount of cryptocurrency as a stake, which they can lose if they act maliciously on the network. This incentivizes participants to act honestly and reduces the energy consumption required for consensus.
[00059] Another consensus technique that may offer a good balance of decentralization, speed, energy efficiency, and security is Delegated Proof of Stake (DPoS). DPoS is a variant of PoS that involves electing a small number of trusted nodes to validate transactions and create new blocks. This approach can offer high throughput and low energy consumption while maintaining a high degree of decentralization. Other consensus technique that may be implemented include Practical Byzantine Fault Tolerance (PBFT), which is designed for permissioned blockchain networks and can offer fast transaction processing and high throughput.
[00060] The consensus node of the set of participating nodes commits the verified block to a distributed ledger in the distributed ledger network. After the verified block is created, the consensus node of the set of participating nodes may broadcast the verified block to the plurality of nodes in the distributed ledger network after committing the verified block to the distributed ledger. The consensus node of the set of participating nodes further updates in real time at least one of the plurality of parameters based on the real-time date received from the BMS of the energy storage device and updating the block to include the real time updates after successful consensus.
[00061] Any one of the nodes may be configured to receiving a request by scanning the 2-dimensional code by at least one user. In an embodiment, the at least one user is an energy storage device manufacturer, an owner of the energy storage device, a service provider, or a buyer of the energy storage device.
[00062] In response to the scanning, securely authenticating the at least one user using an encrypted private key is performed and the encrypted private key is used to provide access to a set of verified blocks of the plurality of verified blocks in the distributed ledger which is associated with the unique code of the energy storage device. The set of verified blocks provides a tamper-proof and secure record associated with the energy storage device.
[00063] In an embodiment, access to a set of verified blocks of the plurality of verified blocks in the distributed ledger for EV battery tracing can be provided through a variety of methods, depending on the specific requirements and design. For example, in a public distributed ledger network, the set of verified blocks may be accessed through a publicly available interface or API. This can allow anyone to access and view the data stored on the blockchain, provided they have the necessary authentication credentials. In a private distributed ledger network, the access to the set of verified blocks may be restricted to authorized users and nodes within the network. This can help to provide enhanced security and privacy for sensitive battery data, such as manufacturing or usage data. Further, a hybrid distributed ledger network can provide the benefits of both public and private distributed ledger network. In a hybrid system, certain parts of the distributed ledger data can be made public, while other parts are kept private and accessible only to authorized users.
[00064] Further, to make it easier for stakeholders to access and understand the set of verified blocks stored on the distributed ledger, data visualization tools can be used to display the data in a user-friendly way. This can include dashboards, charts, graphs, and other visual aids that make it easier to analyze and interpret the data. In an embodiment, Application Programming Interfaces (APIs) may be used to provide access to specific parts of the distributed ledger, allowing developers to build custom applications and tools that use the data for various purposes.
[00065] Post successful authentication, generating, by one of the plurality of nodes in the distributed ledger network, an energy storage device traceability document based on the verified block. In an embodiment, the traceability document is associated with a rechargeable battery. In an embodiment, the energy storage device traceability document comprises information stored in the set of verified blocks of the plurality of verified blocks in the distributed ledger which is associated with a unique code of the energy storage device. The energy storage device traceability document provides a transparent, secure, and tamper-proof record of the energy storage device’s history, which improves trust and confidence in the energy storage device’s reliability and safety.
[00066] In an embodiment, the traceability document for EV battery using the set of verified blocks on the distributed ledger may be created and may be provided with secure authentication to necessary stakeholders.
[00067] Below is an example of a traceability document for an EV battery that uses data (set of verified blocks) stored on a distributed ledger:
EV Battery Traceability Document:
Battery Serial Number: ABC12345
Manufacturer: XYZ Inc.
Production Date: 01/01/2022
Block Height: 1122334455
Block Hash: 1a2b3c4d5e6f7g8h9i0j
Previous Block Hash: 9i8h7g6f5e4d3c2b1a
Blockchain Node: Node 123
Chain of Custody:
• Battery cells were manufactured by ABC Cell Co. on 12/15/2021.
• Battery cells were assembled into a battery pack by XYZ Inc. on 01/01/2022.
• Battery pack was sold to EV manufacturer ABC Motors on 02/01/2022.
• Battery pack was installed in EV model XYZ on 03/01/2022.
• Battery pack was maintained and serviced by authorized dealer DEF Services on 04/01/2022.
• Battery pack was sold to second-hand buyer GHI Consumer on 05/01/2023.
• Battery pack was maintained and serviced by authorized dealer JKL Services on 06/01/2023.
• Current owner: GHI Consumer.

Battery Status:
• Battery cells were manufactured by ABC Cell Co. on 12/15/2021.
• Battery pack was assembled by XYZ Inc. on 01/01/2022.
• Battery pack includes 96 cells with serial/batch number: 1234-5678.
• Battery pack is equipped with a Battery Management System (BMS) with serial number: BMS-9876.
• Battery pack was charged using an EV charger with serial number: CH-54321.
• Battery pack was discharged with values ranging from 10% to 90% of its capacity.
• Battery has been in use for 1 year and 1 month.
• Battery has been maintained and serviced according to manufacturer's recommendations.
• Battery has been previously used and is now in the possession of GHI Consumer.
• Battery is functioning properly and is currently at 80% capacity.
• Battery has been previously owned and maintained by DEF Services and JKL Services.
• Full battery history, maintenance records, cell information, BMS, and charger details can be accessed through the blockchain node at Node 123.
[00068] This traceability document provides a detailed history of the EV battery cells, pack assembly, BMS, charger, and usage information, along with a comprehensive chain of custody and maintenance records. By using data stored on a blockchain, the document can provide an accurate and tamper-proof record of the battery's history and performance, which can be useful for ensuring the battery has been properly manufactured, assembled, and maintained throughout its lifecycle. Further, this can be useful for tracking the battery's performance, identifying any issues or anomalies.
[00069] FIGURE 3 illustrates a block diagram of a sample block structure in the distributed ledger network, in accordance with an embodiment of the invention.
[00070] In this block diagram, the Block Header contains metadata about the block, such as a timestamp and a reference to the previous block in the chain. The Transaction Data section contains information about the EV batteries being tracked, such as their unique identification numbers, their location, and their status in the battery lifecycle. This data is verified and recorded on the blockchain, creating a permanent and tamper-proof record of the battery's history.
[00071] The Merkle Root is a hash of all the transaction data in the block, which is used to verify the integrity of the data. The Nonce is a random number that is added to the block during the mining process to help ensure the security of the blockchain. Together, these elements create a secure and transparent ledger that can be used to trace the history of EV batteries.
[00072] Fig. 4 illustrates a sample diagram of three block structure in the distributed ledger network, in accordance with an embodiment of the invention.

[00073] These blocks contain example data that could be used to trace an EV battery throughout its lifecycle. Block 1 records the battery's initial manufacture and location, while Block 2 records the battery's movement to a new location. Block 3 records the battery's use at a charging station, including the user and start time. This information provides a detailed history of the battery's lifecycle, which can help stakeholders better understand its condition, usage patterns, and other important information.
[00074] In a blockchain-based system for tracing EV batteries, the blocks will be created by the nodes participating in the network. These nodes can be computers or devices connected to the network that are responsible for verifying and recording transactions on the blockchain. In the case of tracing EV batteries, the nodes could be owned and operated by a variety of stakeholders, including battery manufacturers, EV manufacturers, logistics companies, charging station operators, and regulators.
[00075] Each time a transaction occurs in the battery lifecycle, a new block will be created and added to the blockchain by the participating nodes. These nodes use complex algorithms to verify and record the transactions in a secure and tamper-proof way, ensuring that the battery's history is accurately recorded on the blockchain.
[00076] Ultimately, the creation of blockchain blocks in an EV battery tracing system is a collaborative effort involving all of the stakeholders in the battery ecosystem. By working together and using blockchain technology, these stakeholders can create a transparent, secure, and efficient system for tracking the lifecycle of EV batteries.
[00077] Referring now to FIG. 5, a flowchart of a method 500 for generating the traceability document in the distributed ledger network is illustrated, in accordance with an embodiment.
[00078] Method starts at step 502 and proceeds to step 504.
[00079] At step 504, registering the energy storage device onto the distributed ledger network;
[00080] At step 506, generating the unique code associated with the energy storage device based on the received plurality of parameters, wherein the unique code is stored in a form of a 2-dimensional code, wherein the 2-dimensional code comprises at least one of a bar code, RFID tag, and a QR code; and
[00081] At step 506, receiving, by a plurality of nodes in the distributed ledger network, a plurality of parameters from a Battery management system (BMS) of an energy storage device. In an embodiment, the distributed ledger comprises a plurality of verified blocks which comprises the plurality of parameters of the energy storage device. The plurality of nodes in the distributed ledger network is configured to execute a set of specialized instructions for automatic tracking and management of the energy storage device’s lifecycle, the transfer of ownership, warranty claims, recycling, and disposal of the energy storage device.
[00082] At step 508, identifying, by one of the plurality of nodes in the distributed ledger network, a set of participating nodes from the plurality of nodes within the distributed ledger network using at least one consensus technique;
[00083] At step 510, creating, by the set of participating nodes of the plurality of nodes in the distributed ledger network, an unverified block in a local ledger of each of the set of participating nodes, wherein the unverified block comprises at least one new transaction in the distributed ledger network, wherein the least one new transaction comprises the plurality of parameters of the energy storage device;
[00084] At step 512, computing, by each of the set of participating nodes, a hash value for each of the at least one new transaction in the distributed ledger network;
[00085] At step 514, performing, by each of the set of participating nodes, consensus based on the computed hash value for identifying a set of valid transactions in the unverified blocks created by each of the set of participating nodes;
[00086] At step 516, creating, by a consensus node of the set of participating nodes, a verified block comprising the set of valid transactions, wherein the consensus node identifies the set of valid transactions in a shortest time when compared with remaining set of participating nodes;
[00087] At step 518, committing, by the consensus node of the set of participating nodes, the verified block to a distributed ledger in the distributed ledger network; and
[00088] At step 520, broadcasting, by the consensus node of the set of participating nodes, the verified block to the plurality of nodes in the distributed ledger network after committing the verified block to the distributed ledger.
[00089] At step 522, updating, by the consensus node of the set of participating nodes, in real time at least one of the plurality of parameters based on the real-time date received from the BMS of the energy storage device and updating the block to include the real time updates after successful consensus.
[00090] At step 524, receiving a request by scanning the 2-dimensional code by at least one user, wherein the at least one user is an energy storage device manufacturer, an owner of the energy storage device, a service provider, or a buyer of the energy storage device;
[00091] At step 526, securely authenticating the at least one user using an encrypted private key, wherein the encrypted private key is used to provide access to a set of verified blocks of the plurality of verified blocks in the distributed ledger which is associated with the unique code of the energy storage device.
[00092] At step 528, generating, by one of the plurality of nodes in the distributed ledger network, an energy storage device traceability document based on the verified block after successful authentication. The traceability document is associated with a rechargeable battery. The energy storage device traceability document comprises information stored in the set of verified blocks of the plurality of verified blocks in the distributed ledger which is associated with a unique code of the energy storage device.
[00093] Control passes to end step 530.
[00094] Referring now to FIG. 6, a flowchart of a method 600 performed by a user computing device 110 for generating the traceability document in the distributed ledger network is illustrated, in accordance with an embodiment.
[00095] Method starts at step 602 and proceeds to step 604.
[00096] At step 604, scanning the 2-dimensional code by at least one user, wherein the at least one user is an energy storage device manufacturer, an owner of the energy storage device, a service provider, or a buyer of the energy storage device;
[00097] At step 606, securely authenticating the at least one user using an encrypted private key, wherein the encrypted private key is used to provide access to a set of verified blocks of the plurality of verified blocks in the distributed ledger which is associated with the unique code of the energy storage device; and
[00098] At step 608, receiving access to an energy storage device traceability document after successful authentication. In an embodiment, the energy storage device traceability document comprises information stored in the set of verified blocks of the plurality of verified blocks in the distributed ledger which is associated with the unique code of the energy storage device
[00099] Control passes to end step 610.
Advantages
[000100] Blockchain-based EV battery tracking is a system that uses blockchain technology to record and track the history of electric vehicle (EV) batteries. By using a decentralized and immutable ledger, the claimed system can provide a transparent and secure record of a battery's ownership, usage, maintenance, and performance. This can help increase the trust and confidence in the reliability and safety of EV batteries, which is important for the wider adoption of electric vehicles.
[000101] By using distributed ledger technology, the battery tracking system can provide a transparent, secure, and tamper-proof record of the battery's history, which can improve trust and confidence in the battery's reliability and safety. Additionally, the system can enable more efficient and sustainable management of the battery lifecycle, such as extending the battery's lifespan and reducing waste.
[000102] The claimed system provides a transparent, secure, and tamper-proof record of the battery's history, which can improve trust and confidence in the battery's reliability and safety.
[000103] The claimed system of using a distributed ledger network for tracing of EV batteries using the generated traceability document provides a technological advance as elaborated below.
• Immutable and transparent distributed ledger: Distributed ledger network provides a tamper-proof and transparent ledger that can be used to record the entire lifecycle of EV batteries. This allows stakeholders to trace the history of a battery, from its manufacture to its disposal, with confidence that the data has not been tampered with.
• Decentralized network trust: Distributed ledger network is a decentralized network, meaning that there is no central authority or single point of failure. This makes it more difficult for bad actors to tamper with the data or manipulate the tracing process. This can help to increase trust in the system, reduce the risk of fraud, and improve the efficiency of the tracing process.
• Secure and private data: Distributed ledger network provides a high level of security and privacy for sensitive data, such as battery information. This helps protect against data breaches or other security risks that can compromise the integrity of the tracing process. The claimed system uses cryptography to secure and validate transactions, which can help to prevent unauthorized access, tampering, or manipulation of data. This can provide enhanced security for sensitive battery data, such as the battery's manufacturing history, maintenance records, and usage patterns.
• Improved efficiency: Distributed ledger network helps to streamline the tracing process by automating tasks and reducing the need for intermediaries, which can save time and resources for stakeholders. It can also provide real-time access to battery data, making it easier to identify and address issues as they arise.
• Standardization: By using a standardized format for battery data and events, the claimed distributed ledger network system helps to improve interoperability and data sharing between different stakeholders in the EV battery ecosystem. This can lead to more efficient supply chains, better maintenance and repair practices, and improved overall battery performance.
[000104] The claimed distributed ledger network for tracing of EV batteries using the generated traceability document provides tracing of EV batteries provides a more secure, transparent, and efficient way to track the history of batteries throughout their lifecycle.
, C , Claims:I/We claim:
1. A method for generating a traceability document in a distributed ledger network, the method comprising:
receiving, by a plurality of nodes in the distributed ledger network, a plurality of parameters from a Battery management system (BMS) of an energy storage device;
identifying (508), by one of the plurality of nodes in the distributed ledger network, a set of participating nodes from the plurality of nodes within the distributed ledger network using at least one consensus technique;
creating (510), by the set of participating nodes of the plurality of nodes in the distributed ledger network, an unverified block in a local ledger of each of the set of participating nodes, wherein the unverified block comprises at least one new transaction in the distributed ledger network, wherein the least one new transaction comprises the plurality of parameters of the energy storage device;
computing (512), by each of the set of participating nodes, a hash value for each of the at least one new transaction in the distributed ledger network;
performing (514), by each of the set of participating nodes, consensus based on the computed hash value for identifying a set of valid transactions in the unverified blocks created by each of the set of participating nodes;
creating (516), by a consensus node of the set of participating nodes, a verified block comprising the set of valid transactions, wherein the consensus node identifies the set of valid transactions in a shortest time when compared with remaining set of participating nodes;
committing (518), by the consensus node of the set of participating nodes, the verified block to a distributed ledger in the distributed ledger network; and
generating (528), by one of the plurality of nodes in the distributed ledger network, an energy storage device traceability document based on the verified block after successful authentication, wherein the energy storage device traceability document comprises information stored in the set of verified blocks of the plurality of verified blocks in the distributed ledger which is associated with a unique code of the energy storage device.
2. The method for generating the traceability document in the distributed ledger network as claimed in claim 1, comprising broadcasting (528), by the consensus node of the set of participating nodes, the verified block to the plurality of nodes in the distributed ledger network after committing (518) the verified block to the distributed ledger.
3. The method for generating the traceability document in the distributed ledger network as claimed in claim 1, comprising updating (522), by the consensus node of the set of participating nodes, in real time at least one of the plurality of parameters based on the real-time date received from the BMS of the energy storage device.
4. The method for generating the traceability document in the distributed ledger network as claimed in claim 1, wherein the distributed ledger comprises a plurality of verified blocks which comprises the plurality of parameters of the energy storage device.
5. The method for generating the traceability document in the distributed ledger network as claimed in claim 1, wherein the plurality of nodes in the distributed ledger network is configured to execute a set of specialized instructions for automatic tracking and management of the energy storage device’s lifecycle, the transfer of ownership, warranty claims, recycling, and disposal of the energy storage device.

6. The method for generating the traceability document in the distributed ledger network as claimed in claim 1, comprising:
Registering (504) the energy storage device onto the distributed ledger network;
generating the unique code (506) associated with the energy storage device based on the received plurality of parameters, wherein the unique code is stored in a form of a 2-dimensional code, wherein the 2-dimensional code comprises at least one of a bar code, RFID tag, and a QR code; and
providing access to the distributed ledger using the unique code.
7. The method for generating the traceability document in the distributed ledger network as claimed in claim 6, wherein providing access comprises:
scanning the 2-dimensional code by at least one user, wherein the at least one user is an energy storage device manufacturer, an owner of the energy storage device, a service provider, or a buyer of the energy storage device;
securely authenticating (526) the at least one user using an encrypted private key, wherein the encrypted private key is used to provide access to a set of verified blocks of the plurality of verified blocks in the distributed ledger which is associated with the unique code of the energy storage device; and
generating (528) an energy storage device traceability document after successful authentication, wherein the energy storage device traceability document comprises information stored in the set of verified blocks of the plurality of verified blocks in the distributed ledger which is associated with the unique code of the energy storage device.

8. The method for generating the traceability document in the distributed ledger network as claimed in claim 1, wherein the energy storage device traceability document provides a transparent, secure, and tamper-proof record of the energy storage device’s history, which improves trust and confidence in the energy storage device’s reliability and safety.
9. The method for generating the traceability document in the distributed ledger network as claimed in claim 1, wherein the set of verified blocks provides a tamper-proof and secure record associated with the energy storage device.
10. The method for generating the traceability document in the distributed ledger network as claimed in claim 1, wherein the plurality of parameters comprises information on the energy storage device’s ownership including date and location of purchase, transfer of ownership, warranty claims, disputes, battery usage details, battery performance, maintenance history, charge/discharge cycles, temperature, voltage levels of the battery, auxiliary performance metrics that can provide insights into the energy storage device’s health and condition, records of any maintenance or repair work done on the energy storage device, including a date, location, and type of work performed.
11. The method for generating the traceability document in the distributed ledger network as claimed in claim 1, wherein the traceability document is associated with a rechargeable battery.
12. The method for generating the traceability document in the distributed ledger network as claimed in claim 1, wherein the distributed ledger network is a private blockchain network or a public blockchain network.
13. A system to generate a traceability document in a distributed ledger network (102), the system comprising:
a processor (202); and
a computer-readable medium communicatively coupled to the processor (202), wherein the computer-readable medium stores processor-executable instructions, which when executed by the processor (202), cause the processor (202) to:
receive, by a plurality of nodes (106) in the distributed ledger network (102), a plurality of parameters from a Battery management system (BMS) of an energy storage device;
identify, by one of the plurality of nodes (106) in the distributed ledger network (102), a set of participating nodes from the plurality of nodes within the distributed ledger network using at least one consensus technique;
create, by the set of participating nodes (106) of the plurality of nodes (106) in the distributed ledger network (102), an unverified block in a local ledger of each of the set of participating nodes, wherein the unverified block comprises at least one new transaction in the distributed ledger network, wherein the least one new transaction comprises the plurality of parameters of the energy storage device;
compute, by each of the set of participating nodes (106), a hash value for each of the at least one new transaction in the distributed ledger network;
perform, by each of the set of participating nodes (106), consensus based on the computed hash value for identifying a set of valid transactions in the unverified blocks created by each of the set of participating nodes (106);
create, by a consensus node of the set of participating nodes (106), a verified block comprising the set of valid transactions, wherein the consensus node identifies the set of valid transactions in a shortest time when compared with remaining set of participating nodes (106);
commit, by the consensus node of the set of participating nodes (106), the verified block to a distributed ledger in the distributed ledger network (102); and
generate, by one of the plurality of nodes in the distributed ledger network (102), an energy storage device traceability document based on the verified block after successful authentication, wherein the energy storage device traceability document comprises information stored in the set of verified blocks of the plurality of verified blocks in the distributed ledger which is associated with a unique code of the energy storage device.
14. The system to generate the traceability document in the distributed ledger network as claimed in claim 13, wherein the processor (202) of the consensus node of the set of participating nodes (106) is configured to broadcast the verified block to the plurality of nodes in the distributed ledger network (102) after committing the verified block to the distributed ledger.
15. The system to generate the traceability document in the distributed ledger network (102) as claimed in claim 13, wherein the processor (202) of the consensus node of the set of participating nodes is configured to update in real time at least one of the plurality of parameters based on the real-time date received from the BMS of the energy storage device.
16. The system to generate the traceability document in the distributed ledger network (102) as claimed in claim 13, wherein the distributed ledger comprises a plurality of verified blocks which comprises the plurality of parameters of the energy storage device.
17. The system to generate the traceability document in the distributed ledger network as claimed in claim 13, wherein the plurality of nodes in the distributed ledger network (102) is configured to execute a set of specialized instructions for automatic tracking and management of the energy storage device’s lifecycle, the transfer of ownership, warranty claims, recycling, and disposal of the energy storage device.
18. The system to generate the traceability document in the distributed ledger network as claimed in claim 13, wherein the processor of the plurality of participating nodes is configured to:
register the energy storage device onto the distributed ledger network;
generate the unique code associated with the energy storage device based on the received plurality of parameters, wherein the unique code is stored in a form of a 2-dimensional code, wherein the 2-dimensional code comprises at least one of a bar code, RFID tag, and a QR code; and
provide access to the distributed ledger using the unique code.
19. The system to generate the traceability document in the distributed ledger network as claimed in claim 18, wherein the processor of an electronic device communicatively coupled with the distributed ledger network is configured to:
Scan the 2-dimensional code (604) by at least one user, wherein the at least one user is an energy storage device manufacturer, an owner of the energy storage device, a service provider, or a buyer of the energy storage device;
securely authenticate (606) the at least one user using an encrypted private key, wherein the encrypted private key is used to provide access to a set of verified blocks of the plurality of verified blocks in the distributed ledger which is associated with the unique code of the energy storage device; and
generate an energy storage device traceability document after successful authentication, wherein the energy storage device traceability document comprises information (608) stored in the set of verified blocks of the plurality of verified blocks in the distributed ledger which is associated with the unique code of the energy storage device.
20. The system to generate the traceability document in the distributed ledger network as claimed in claim 13, wherein the energy storage device traceability document provides a transparent, secure, and tamper-proof record of the energy storage device’s history, which improves trust and confidence in the energy storage device’s reliability and safety.
21. The system to generate the traceability document in the distributed ledger network as claimed in claim 13, wherein the set of verified blocks provides a tamper-proof and secure record associated with the energy storage device.
22. The system to generate the traceability document in the distributed ledger network as claimed in claim 13, wherein the plurality of parameters comprises information on the energy storage device’s ownership including date and location of purchase, transfer of ownership, warranty claims, disputes, battery usage details, battery performance, maintenance history, charge/discharge cycles, temperature, voltage levels of the battery, auxiliary performance metrics that can provide insights into the energy storage device’s health and condition, records of any maintenance or repair work done on the energy storage device, including a date, location, and type of work performed.
23. The system to generate the traceability document in the distributed ledger network as claimed in claim 13, wherein the traceability document is associated with a rechargeable battery.
24. The system to generate the traceability document in the distributed ledger network as claimed in claim 13, wherein the distributed ledger network is a private blockchain network or a public blockchain network.