Battery data management method

Abstract

The present disclosure relates to a battery data management method, and the technical problem to be solved is to provide a battery data management method ensuring immutability and transparency of data, and guaranteeing confidentiality and integrity of data by applying encryption and digital signing. To this end, the present disclosure provides the steps in which: a main battery management system collects data of a battery and generates a hash value of the data; a blockchain network generates a block header and generates a block structure in which the data is included in the block header; the blockchain network generates a Merkle root on the basis of the hash value of the data; the blockchain network validates a blockchain transaction and performs proof-of-work on the basis of a preset target difficulty; and the blockchain network verifies the validity of the block structure and adds a new block to the blockchain network on the basis of the verification result.

Description

Battery Data Management Method

[0001] The present disclosure relates to a battery data management method.

[0002] Generally, lithium-ion batteries are primarily used for electric vehicles. Lithium-ion batteries are installed in the form of large-scale battery packs consisting of hundreds of individual cells.

[0003] A Battery Management System (BMS) is essential for optimizing the condition and performance of a battery. The BMS monitors and controls the battery's voltage, current, temperature, State of Charge (SOC), and State of Health (SOH) in real time.

[0004] Recently, the introduction of Cloud Battery Management Systems (Cloud BMS) utilizing cloud technology has enabled more sophisticated data collection and analysis. Battery performance varies depending on usage duration, charge / discharge patterns, and environmental conditions, which directly impact the driving range and overall lifespan of electric vehicles. Therefore, accurately recording and analyzing all data generated throughout the battery's lifecycle is critical. Consequently, ensuring data integrity and reliability has emerged as a major challenge, serving as a key factor in various fields such as battery performance evaluation, quality assurance, and valuation in the used battery market.

[0005] The information described above disclosed in the background technology of this invention is intended only to enhance understanding of the background of the present invention and may therefore include information that does not constitute prior art.

[0006] The purpose of the present invention is to provide a battery data management method that secures data immutability and transparency by utilizing blockchain, a distributed ledger technology, and guarantees data confidentiality and integrity by applying encryption and digital signatures.

[0007] However, the technical problems that the present invention aims to solve are not limited to those described above, and other unmentioned problems can be clearly understood by those skilled in the art from the description of the invention below.

[0008] A battery data management method according to an embodiment of the present invention for solving the above technical problem comprises: a step in which a main battery management system collects battery data and generates a hash value of the data; a step in which a blockchain network generates a block header and includes the data in the block header to generate a block structure; a step in which the blockchain network generates a Merkle root based on the hash value of the data; a step in which the blockchain network verifies a blockchain transaction and performs proof of work based on a preset target difficulty; and a step in which the blockchain network verifies the validity of the block structure and adds a new block to the blockchain network according to the verification result.

[0009] In the step of generating a hash value of the data according to the present invention, the main battery management system is characterized by normalizing the data and generating a hash value of the data using a hash function.

[0010] In the step of generating the Merkle root of the present invention, the blockchain network is characterized by using the hash value of the data as a leaf node and connecting and hashing the hash value of the data to generate the Merkle root.

[0011] In the step of performing the proof of work of the present invention, the blockchain network is characterized by determining whether the hash value of the block header satisfies a pre-set condition.

[0012] In the step of performing the proof of work of the present invention, the blockchain network initializes the nonce of the block header to 0 and calculates the hash value of the block header, and compares the hash value of the block header with a preset target difficulty level and, depending on the comparison result, completes the proof of work or increases the nonce of the block header by 1 to calculate the hash value of the block header.

[0013] In the step of adding a new block to the blockchain network of the present invention, the blockchain network is characterized by generating the new block when the proof of work is completed, verifying the new block, and adding the new block according to the verification result.

[0014] The present invention is characterized by further including the step of, when the blockchain network receives a data access request through a blockchain API (Application Programming Interface), verifying the integrity of the data and providing the data whose integrity has been verified.

[0015] In the step of verifying the integrity of the data and providing the data whose integrity has been verified according to the present invention, the blockchain network identifies a block containing the data requested through the blockchain API, calculates the Merkle path of the data in the Merkle tree of the identified block, recalculates the Merkle root using the Merkle path, and verifies the integrity of the data by comparing the recalculated Merkle root with the Merkle root of the block header to determine whether they match.

[0016] A battery data management method according to an embodiment of the present invention for solving the above technical problem comprises the steps of: a main battery management system collecting battery data, encrypting and signing the collected data, generating a token using a pre-assigned API (Application Programming Interface) key, and then transmitting the generated token and the encrypted data to a blockchain API; the blockchain API verifying the token and verifying the integrity of the encrypted data, and generating a blockchain transaction according to the verification result; a validation node verifying the validity of the blockchain transaction; the blockchain network generating a new block and updating the block according to the result of the validation of the blockchain transaction; and the blockchain API checking the status of the blockchain transaction to generate a response to a data request and transmitting the generated response to the main battery management system.

[0017] In the step of transmitting the token and the encrypted data of the present invention to a blockchain API, the main battery management system is characterized by normalizing the data to generate a hash value, signing the generated hash value of the data with the private key of the main battery management system, and then packaging the data and the hash value of the data to generate packaged data.

[0018] In the step of transmitting the token and the encrypted data of the present invention to a blockchain API, the main battery management system is characterized by including the token in the HTTPS request header and including the identification information of the local battery management system and the packaging data in the HTTPS request body and transmitting them to the blockchain API.

[0019] In the step of generating the blockchain transaction of the present invention, the blockchain API is characterized by verifying the signature using the public key of the main battery management system and recalculating the hash value of the data to check whether it matches the hash value of the data generated by the main battery management system.

[0020] In the step of generating the blockchain transaction of the present invention, the blockchain API is characterized by converting the data into a blockchain transaction format and adding a timestamp and a unique identifier to the blockchain transaction.

[0021] In the step of verifying the validity of the blockchain transaction of the present invention, the validation node verifies the validity of the blockchain transaction and newly selects a node to include the blockchain transaction in the new block.

[0022] In the step of the blockchain network of the present invention creating a new block and updating the block, the selected node creates the new block and propagates it to the nodes of the blockchain network, and the nodes of the blockchain network verify the validity of the new block and add the new block according to the verification result to synchronize.

[0023] According to the present invention, by using blockchain, a distributed ledger technology, to ensure the immutability and transparency of data, and by applying encryption technology and digital signatures to guarantee the confidentiality and integrity of data, the accuracy of battery performance evaluation and lifespan prediction can be improved, and the risk of data leakage and tampering can be reduced.

[0024] According to the present invention, data is selectively recorded on a blockchain to enable rapid and accurate monitoring of battery status.

[0025] According to the present invention, a unique identifier is assigned to a battery on a blockchain, and the history of the battery is traceable by linking it with all data throughout the battery's entire lifecycle.

[0026] However, the effects obtainable through the present invention are not limited to those described above, and other unmentioned technical effects will be clearly understood by those skilled in the art from the description of the invention below.

[0027] The following drawings attached to this specification illustrate preferred embodiments of the present invention and serve to further enhance understanding of the technical concept of the present invention together with the detailed description of the invention provided below; therefore, the present invention should not be interpreted as being limited only to the matters described in such drawings.

[0028] FIG. 1 is a block diagram of a battery data management system according to one embodiment of the present invention.

[0029] FIG. 2 is a flowchart illustrating the operation process of a blockchain network that guarantees the integrity of battery data in a battery data management method according to an embodiment of the present invention.

[0030] FIG. 3 is a flowchart of a data collection and preprocessing process according to an embodiment of the present invention.

[0031] FIG. 4 is a flowchart of a data hash value generation process according to one embodiment of the present invention.

[0032] FIG. 5 is a flowchart of a block structure generation process according to one embodiment of the present invention.

[0033] FIG. 6 is a flowchart of a Merkle tree generation process according to one embodiment of the present invention.

[0034] FIG. 7 is a flowchart of a work proof process according to one embodiment of the present invention.

[0035] FIG. 8 is a flowchart of a data integrity verification process according to one embodiment of the present invention.

[0036] FIG. 9 is a flowchart of the process of data transmission and reflection to a blockchain network of a battery data management method according to one embodiment of the present invention.

[0037] Preferred embodiments of the present invention will be described in detail below with reference to the attached drawings. Prior to this, terms and words used in this specification and claims should not be interpreted as being limited to their ordinary or dictionary meanings. Instead, based on the principle that the inventor may appropriately define the concepts of terms to best describe his invention, they should be interpreted in a meaning and concept consistent with the technical spirit of the present invention. Therefore, it should be understood that the embodiments described in this specification and the configurations illustrated in the drawings are merely some of the most preferred embodiments of the present invention and do not represent all of the technical spirit of the present invention; thus, various equivalents and modifications that can replace them may exist at the time of filing this application. Furthermore, as used in this specification, "comprise" or "include" and / or "comprising" or "including" specify the presence of the mentioned features, numbers, steps, actions, parts, elements, and / or groups thereof, and do not exclude the presence or addition of one or more other features, numbers, actions, parts, elements, and / or groups. In addition, when describing embodiments of the present invention, "can" and "can" may include "one or more embodiments of the present invention."

[0038] Additionally, to aid in understanding the invention, the attached drawings are not drawn to actual scale, and the dimensions of some components may be exaggerated. Furthermore, the same reference numerals may be assigned to identical components in different embodiments.

[0039] The statement that two subjects of comparison are 'identical' means that they are 'substantially identical.' Therefore, substantial identity may include deviations considered low in the industry, for example, deviations within 5%. Additionally, the statement that a parameter is uniform in a given area may mean that it is uniform from an average perspective.

[0040] Although terms such as "first," "second," etc., are used to describe various components, it goes without saying that these components are not limited by these terms. These terms are used merely to distinguish one component from another, and unless specifically stated otherwise, the first component may also be the second component.

[0041] Throughout the specification, unless specifically stated otherwise, each component may be singular or plural.

[0042] The fact that any configuration is placed on the "upper (or lower)" of a component or on the "upper (or lower)" of a component may mean not only that any configuration is placed in contact with the upper (or lower) surface of said component, but also that another configuration may be interposed between said component and any configuration placed on (or below) said component.

[0043] Furthermore, where it is stated that one component is "connected," "coupled," or "connected" to another component, it should be understood that while said components may be directly connected or connected to each other, another component may be "interposed" between each component, or that each component may be "connected," "coupled," or "connected" through another component. Additionally, when it is stated that a part is electrically coupled with another part, this includes not only cases where they are directly connected but also cases where they are connected with another component in between.

[0044] Throughout the specification, "A and / or B" means A, B, or A and B unless specifically stated otherwise. That is, "and / or" includes any combination or any combination of the enumerated items. "C to D" means C or more and D or less, unless specifically stated otherwise.

[0045] FIG. 1 is a block diagram of a battery data management system according to one embodiment of the present invention.

[0046] Referring to FIG. 1, a battery data management system according to one embodiment of the present invention may include a local battery management system (Local BMS) (100), a main battery management system (Main BMS) (200), a blockchain API (Blockchain Application Programming Interface) (300), a blockchain network (300), and a validation node (500).

[0047] The local battery management system (100) can transmit data of the battery, such as the battery status, to the main battery management system (200). The local battery management system (100) may be a vehicle battery management system installed in the electric vehicle (10) to manage the battery of the electric vehicle (10).

[0048] The battery may be a lithium-ion battery and may be mounted on an electric vehicle (10) in the form of a large battery pack consisting of hundreds of individual battery cells.

[0049] The local battery management system (100) can transmit data collected from the battery to the main battery management system (200) via a communication network. In this case, the local battery management system (100) can preprocess or compress the data, and after applying encryption and a digital signature to the compressed data, transmit it to the main battery management system (200).

[0050] Communication networks may utilize 3GPP (3rd Generation Partnership Project), LTE (Long Term Evolution), 5G (Generation), WIMAX (World Interoperability for Microwave Access), wired and wireless internet, LAN (Local Area Network), Wireless LAN (Wireless Local Area Network), WAN (Wide Area Network), PAN (Personal Area Network), Bluetooth, Wifi (Wireless Fidelity), etc., but are not specifically limited.

[0051] The main battery management system (200) may be a cloud battery management system (Cloud BMS) utilizing cloud technology.

[0052] The main battery management system (200) can collect data from the local battery management system (100) and an external agency server (not shown).

[0053] Data collected by the main battery management system (200) may include battery status, battery identifier, battery manufacturing date, battery manufacturer, battery inspection results, battery history, battery owner, and battery recall list.

[0054] Battery status may be collected from a local battery management system (100). Battery status may include, but is not specifically limited to, the battery's voltage, current, temperature, State of Charge (SOC), and State of Health (SOH). Battery status may be stored along with a battery unique identifier and a timestamp.

[0055] The battery identifier, battery manufacturing date, and battery manufacturer may be generated at the time of battery manufacturing. The battery identifier, battery manufacturing date, and battery manufacturer may be collected from the battery manufacturer server or from the local battery management system (100).

[0056] Battery inspection results may be collected from an inspection agency server, such as a repair shop or manufacturer server that maintains the electric vehicle (10), or from a local battery management system (100). The battery inspection results may include a battery identifier, inspection time, inspection type, and inspection result, but are not specifically limited.

[0057] The battery recall list may be the battery identifier of the battery requiring recall.

[0058] The main battery management system (200) can normalize data collected from the local battery management system (100) or an external agency server, generate a hash for the data, and then sign the generated hash with the private key of the main battery management system (200).

[0059] The main battery management system (200) can access the blockchain network (400) through the blockchain API (300). In this case, the main battery management system (200) can generate a token, i.e., a JSON Web Token (JWT), using an assigned API key, and transmit the encrypted data and the JWT to the blockchain API (300).

[0060] The main battery management system (200) can remotely monitor and manage the battery in response to a request from a user. For example, the main battery management system (200) can request data from a blockchain API (300) in response to a request from a user terminal (not shown), and receive a response from the blockchain API (300) in response to the request from the user terminal and transmit it to the user terminal. In this case, the main battery management system (200) can provide data to the user terminal or report an error as a response to the user request.

[0061] The main battery management system (200) can manage data collected from the local battery management system (100) in conjunction with the blockchain network (400). By managing data through the blockchain network (400), the main battery management system (200) can store and analyze relatively more data compared to the local battery management system (100), and can also improve the accuracy of battery analysis.

[0062] The main battery management system (200) can provide various services based on data stored in the blockchain network (400).

[0063] First, the main battery management system (200) can manage the battery lifecycle based on data stored in the blockchain network (400). For example, the main battery management system (200) can store the battery identifier, battery manufacturing date, and battery manufacturer generated at the time of battery manufacturing in the blockchain network (400). The main battery management system (200) can collect battery status and store it in the blockchain network (400). The main battery management system (200) can store battery inspection results in the blockchain network (400). The main battery management system (200) can evaluate the health status of the battery and predict its expected lifespan based on the data stored in the blockchain network (400).

[0064] Additionally, the main battery management system (200) can support used battery trading based on data stored in the blockchain network (400). For example, the main battery management system (200) can query the battery history stored in the blockchain network (400) based on the battery identifier and provide it to the user terminal. The main battery management system (200) can evaluate the current value of the battery by analyzing the battery history stored in the blockchain network (400). The current value of the battery can be evaluated based on at least one of the battery's usage period, number of charge / discharge cycles, temperature exposure history, and maintenance records. The main battery management system (200) can identify the battery owner stored in the blockchain network (400) and transfer ownership of the battery to a new owner.

[0065] Additionally, the main battery management system (200) can manage battery regulatory compliance and recalls based on data stored in the blockchain network (400). The main battery management system (200) can collect battery performance data from the blockchain network (400) in response to a request from a battery management agency server. The main battery management system (200) can analyze the collected battery performance data to generate a report and transmit the generated report to the battery management agency server. The report may include the average performance of the battery, the frequency of abnormal occurrences, and stability indicators, but is not specifically limited to these. Additionally, the main battery management system (200) can collect a list of battery recalls from the blockchain in response to a battery recall request from a manufacturer server. The main battery management system (200) can collect battery owners of batteries included in the battery recall list from the blockchain network (400) and send recall notifications to the corresponding battery owners.

[0066] The blockchain API (300) can provide an interface between the main battery management system (200) and the blockchain network (400). For example, the blockchain API (300) can enable the creation and verification of blockchain transactions, provide smart contracts, or manage tokens.

[0067] The blockchain network (400) is a distributed digital ledger system capable of storing and verifying data. Through this, the blockchain network (400) can record blockchain transactions to prevent tampering with the data.

[0068] A validation node (500) receives a transaction via the blockchain API (300) and can validate the validity of the transaction. Subsequently, the validation node (500) can select a node to include the transaction in a new block according to a consensus algorithm. The selected node (not shown) can create a block, add the transaction, and then broadcast the block to the blockchain network (400). In this case, other nodes of the blockchain network (400) can validate the validity of the block, and if the validity is confirmed, add the new block to a local copy of the blockchain, thereby synchronizing the blockchain network (400).

[0069] Hereinafter, a battery data management method according to an embodiment of the present invention will be described with reference to FIGS. 2 to 9.

[0070] FIG. 2 is a flowchart illustrating the operation process of a blockchain network that guarantees the integrity of battery data according to an embodiment of the present invention.

[0071] Referring to FIG. 2, the main battery management system (200) can collect and preprocess data (S10).

[0072] FIG. 3 is a flowchart of a data collection and preprocessing process according to an embodiment of the present invention.

[0073] Referring to FIG. 3, the main battery management system (200) can collect data from a local battery management system (100) or an external agency server (S11).

[0074] The main battery management system (200) can normalize the collected data (S12). In this case, the main battery management system (200) can convert all numeric values ​​into fixed-point notation and standardize timestamps based on UTC (Universal Time Coordinated).

[0075] The main battery management system (200) can generate a hash value of the preprocessed data (S20).

[0076] FIG. 4 is a flowchart of a data hash value generation process according to one embodiment of the present invention.

[0077] Referring to FIG. 4, the main battery management system (200) can apply a hash function, for example, a SHA-256 hash function, to normalized data (S21) and generate a hash value of the data based on this (S22).

[0078] The main battery management system (200) can transmit preprocessed data and hash values ​​to the blockchain network (400) via the blockchain API (300).

[0079] A blockchain network (400) can create a block structure using the received data (S30).

[0080] FIG. 5 is a flowchart of a block structure generation process according to one embodiment of the present invention.

[0081] Referring to FIG. 5, the blockchain network (400) can generate a block header (S31). The block header may include a version, a previous block hash value, a Merkle root, a difficulty, and a timestamp. Subsequently, the blockchain network (400) can include data in the block header (S32). An example of a block structure is as follows.

[0082] {

[0083] "block_header": {

[0084] "version": "1.0",

[0085] "previous_block_hash":"0000a2b8aal8...f4clac2cc4",

[0086] "merkle_root": "",

[0087] "timestamp": 1629456800,

[0088] "difficulty_target": "0000001000...00000000",

[0089] "nonce": 0

[0090] },

[0091] "battery_data": [

[0092] {

[0093] "data_hash":"8alc3b5f2e4d7a9b6c8f0e2d4a6b8c0e2d4a6b8c

[0094] 0e2d4a6b8c0e2d4a6b8c0e2",

[0095] "timestamp": 1629456790,

[0096] "nonce": 1234567890

[0097] },

[0098] / ... more battery data

[0099] ]

[0100] }

[0101]

[0102] A blockchain network (400) can generate a Merkel tree that represents multiple data as a single hash value (S40). The Merkel tree can be used to ensure data integrity and prevent tampering.

[0103] FIG. 6 is a flowchart of a Merkle tree generation process according to one embodiment of the present invention.

[0104] Referring to FIG. 6, the blockchain network (400) can generate leaf nodes (S41). In this case, the blockchain network (400) can use the hash value of the data as a leaf node. By generating leaf nodes, the blockchain network (400) can generate a tree structure for generating a Merkle root (S42). That is, the blockchain network (400) can calculate the Merkle root by repeating the process of connecting and hashing the hash values ​​of two child nodes to generate a parent node (new hash value) until a root node is generated (S43). The mathematical formula for calculating the Merkle root is as follows.

[0105] Merkle root = H(H(H(leaf1 || leaf2) || H(leaf3 || leaf4)) || ...)

[0106] Here, H is the SHA-256 hash function, || is the concatenation operator, and leaf is a leaf node.

[0107] The blockchain network (400) can perform proof of work to authenticate transactions and create new blocks in the blockchain network (400) (S50).

[0108] FIG. 7 is a flowchart of a work proof process according to one embodiment of the present invention.

[0109] Referring to FIG. 7, the blockchain network (400) can set a target difficulty. Then, the blockchain network (400) can initialize the nonce of the block header to 0 (S51). Once the initial nonce is set, the blockchain network (400) can calculate the hash value of the block header (S52). Then, the blockchain network (400) can determine whether the difficulty of the block header satisfies a pre-set condition (S53). In this case, the blockchain network (400) compares the difficulty of the block header with the pre-set target difficulty; if the difficulty of the block header is less than the target difficulty, it completes the proof of work, and if the difficulty of the block header is greater than or equal to the target difficulty, it increases the nonce by 1 and returns to step S52 to recalculate the hash value of the block header (S54).

[0110] When the proof of work is completed, each node of the blockchain network (400) can verify the validity of the block (S60). Each node can verify the validity of the block structure and check the accuracy of the previous block hash. Additionally, each node can recalculate and verify the Merkle root and verify the validity of the proof of work. Furthermore, when a new block is created, the node can broadcast it to the blockchain network (400) and perform the block verification process. At this time, if more than half of the nodes determine that the block is valid, the node adds the block to the blockchain network (400) (S70), and the blockchain network (400) can be synchronized (S80).

[0111] On the other hand, if a majority of nodes determine that a block is invalid, the nodes can re-examine the validity of the proof of work.

[0112] Next, the blockchain network (400) can check whether there is a data access request from the blockchain API (300) (S90). The data access request can be made in the following format.

[0113] {

[0114] "battery_id": "BT12345",

[0115] "timestamp_range": {

[0116] "start": 1629456000,

[0117] "end": 1629457000

[0118] }

[0119] }

[0120]

[0121] When there is a data access request, the blockchain network (400) can verify the data integrity (S100).

[0122] FIG. 8 is a flowchart of a data integrity verification process according to one embodiment of the present invention.

[0123] Referring to FIG. 8, the blockchain network (400) can identify a block containing the requested data and calculate the Merkle path of the data in the Merkle tree of the block (S101).

[0124] The processor can recalculate the Merkle root using the Merkle path (S102).

[0125] A Merkle tree is a binary hash tree structure that manages multiple blockchain transactions in a blockchain network (400) by condensing them into a single hash value. Merkle paths can be used to verify the integrity of data, specifically to confirm whether the data is actually recorded in the blockchain network. For example, if 8 pieces of data are stored in a block, these become 8 leaf nodes of the Merkle tree. The hash value of each piece of data becomes a leaf node, and the process of calculating the hash value of the parent node by connecting the hash values ​​of two child nodes is repeated until a single Merkle root is finally created.

[0126] A Merkle path is a set of hash values ​​required to reach the Merkle root from a specific leaf node (data). For example, to verify the integrity of the first piece of data, the hash value of the second node paired with that data, and the hash values ​​of the other node paired with their parent node, constitute the Merkle path.

[0127] In the Merkle root recalculation process, the hash value of the data to be verified is sequentially combined with hash values ​​along the Merkle path to calculate the hash value of the parent node, a process that can be repeated. At each step, two hash values ​​are concatenated and hashed again to generate the hash value of the parent node. Repeating this process up to the top of the tree ultimately calculates the Merkle root. If the calculated Merkle root matches the original Merkle root stored in the block header, it proves that the battery data is identical to the original and has not been tampered with.

[0128] The efficiency of this verification method using Merkle paths lies in the fact that data integrity can be verified without verifying the entire dataset. Since the amount of data required for verification increases on a logarithmic scale according to the depth of the Merkle tree, large amounts of battery data can be verified efficiently.

[0129] The blockchain network (400) can verify the integrity of the data based on whether the recalculated Merkle root and the Merkle root of the block header match by comparing (S103) the recalculated Merkle root and the Merkle root of the block header.

[0130] When the integrity of the data is verified, the blockchain network (400) provides the data to the user terminal via the blockchain API (300) (S110), and when the integrity of the data is not verified, it can report an error to the user terminal (S120).

[0131] Hereinafter, the process of transmitting and reflecting data to the blockchain network (400) will be explained with reference to FIG. 9.

[0132] FIG. 9 is a flowchart of the process of data transmission and reflection to a blockchain network according to one embodiment of the present invention.

[0133] Referring to FIG. 9, first, the local battery management system (100) can transmit data to the main battery management system (200) (S210).

[0134] The main battery management system (200) can normalize the collected data (S220). In this case, the main battery management system (200) can convert all numeric values ​​into fixed-point notation and standardize timestamps based on UTC.

[0135] The main battery management system (200) can encrypt and sign data (S230). The main battery management system (200) can possess a unique asymmetric key pair (public key / private key). The main battery management system (200) can serialize normalized data into JSON format, generate a SHA-256 hash for the serialized data, and sign the generated hash with the private key of the main battery management system (200). The main battery management system (200) can package the data and the signature together.

[0136] The main battery management system (200) can generate a JWT using an assigned API key (S240).

[0137] Next, the main battery management system (200) can prepare an HTTP (HyperText Transfer Protocol) request using a JWT. That is, the main battery management system (200) can include the generated JWT in the HTTPS header and include identification information of the local battery management system (100) and an encrypted data package in the HTTPS body. The main battery management system (200) can send an HTTP POST request to the blockchain API (300) (S250).

[0138] The blockchain API (300) can verify the HTTP POST request by verifying the JWT as it receives the HTTP POST request from the main battery management system (200) (S260).

[0139] The blockchain API (300) can verify the integrity of the received data package (S270). In this case, the blockchain API (300) can verify the signature using the public key of the main battery management system (200), recalculate the hash value of the data, and verify whether the recalculated hash value of the data matches the signed hash value.

[0140] As the integrity of the data package is verified, the blockchain API (300) can generate a blockchain transaction (S280). In this case, the blockchain API (300) can convert the verified data into a blockchain transaction format and add a timestamp and a unique identifier to the converted blockchain transaction. The structure of the blockchain transaction is as follows.

[0141] {

[0142] "transaction_id": "0x1234...5678",

[0143] "timestamp": 1629456790,

[0144] "bms_id": "CBMS12345",

[0145] "data": {

[0146] "battery_id": "BT12345",

[0147] "timestamp": 1629456789,

[0148] "voltage": 3.7000,

[0149] "current": 2.1000,

[0150] "temperature": 25.5000,

[0151] "charge_cycles": 150,

[0152] "state_of_charge": 0.7500,

[0153] "health_indicator": 0.9500

[0154] },

[0155] "signature": "MEUCIQDkM9xw4L8dHZX5O4UeqkH8Ul0lwXwqrxylaQo6xIwAAQIgQbFHn0nKxH6AqU / j2ql4tWvE3elyev"

[0156] VXTq6p_CXHI="

[0157] }

[0158]

[0159] Next, the blockchain network (400) can broadcast the blockchain transaction received from the blockchain API (300) to the validation node (500) (S290).

[0160] A validation node (500) can validate the validity of a blockchain transaction by verifying the data format, signature, and timestamp (S300).

[0161] A validator node (500) can select a node to include a blockchain transaction in a new block through a consensus process using a consensus algorithm, such as proof of work or proof of stake (S310).

[0162] The selected node can create a new block (S320) and propagate the created block to the blockchain network (400) (S330).

[0163] Nodes of the blockchain network (400) can receive a new block and update the block (S340). That is, other nodes of the blockchain network (400) can verify the validity of the new block, and if the validity is verified, the new block can be added to each node's local copy of the blockchain. Through this, the entire blockchain network (400) can be synchronized.

[0164] The blockchain network (400) can check whether a transaction has been successfully included in a block (S350).

[0165] Accordingly, the blockchain API (300) can check the status of the blockchain transaction to generate a response to the data request and transmit the generated response to the main battery management system (200) (S360). The generated response is as follows.

[0166] {

[0167] "transaction_id": "0x1234...5678",

[0168] "timestamp": 1629456790,

[0169] "bas_id": "CBMS12345",

[0170] "data": {

[0171] "battery_id": "BT12345",

[0172] "timestamp": 1629456789,

[0173] "voltage": 3.7000,

[0174] "current": 2.1000,

[0175] "temperature": 25.5000,

[0176] }

[0177] "charge_cycles": 150,

[0178] "state_of_charge": 0.7500,

[0179] "health_indicator": 0.9500

[0180] "signature": "MEUCIQDkM9xw4L8dHZX5O4UeqkH8Ul0lwXwqrxylaQo6xIwAAQIgQbFHn0nKxH6AqU / j2ql4tWvE3elyev"

[0181] VXTq6p_CXHI

[0182] }

[0183]

[0184] As described above, a battery data management system and method according to one embodiment of the present invention can improve the accuracy of battery performance evaluation and lifespan prediction, and reduce the risk of data leakage and tampering by using blockchain, a distributed ledger technology, to ensure the immutability and transparency of data, and by applying encryption technology and digital signatures to ensure the confidentiality and integrity of data.

[0185] A battery data management system and method according to one embodiment of the present invention enables rapid and accurate battery status monitoring by selectively recording data on a blockchain.

[0186] A battery data management system and method according to one embodiment of the present invention assigns a unique identifier to a battery on a blockchain and enables history tracking of the battery by linking it with all data over the entire lifecycle of the battery.

[0187] Although the present invention has been described above by limited embodiments and drawings, the present invention is not limited thereto, and it is obvious that various modifications and variations are possible within the scope of the technical spirit of the present invention and the equivalent scope of the claims described below by those skilled in the art to which the present invention belongs.

Claims

1. A step in which the main battery management system collects battery data and generates a hash value of the said data; A step in which a blockchain network generates a block header and includes the data in the block header to generate a block structure; The step of the blockchain network generating a Merkle root based on the hash value of the data; A step in which the blockchain network verifies blockchain transactions and performs proof of work based on a pre-set target difficulty; and A battery data management method comprising the step of the blockchain network verifying the validity of a block structure and adding a new block to the blockchain network according to the verification result.

2. In Paragraph 1, In the step of generating the hash value of the above data, The above main battery management system is a battery data management method that normalizes the data and generates a hash value of the data using a hash function.

3. In Paragraph 1, In the step of generating the above Merkle root, A battery data management method in which the blockchain network uses the hash value of the data as a leaf node and connects and hashes the hash value of the data to generate the Merkle root.

4. In Paragraph 1, In the step of performing the above proof of work, The above-described blockchain network is a battery data management method that determines whether the hash value of the block header satisfies a pre-set condition.

5. In Paragraph 4, In the step of performing the above proof of work, A battery data management method in which the blockchain network initializes the nonce of the block header to 0 and calculates the hash value of the block header, compares the hash value of the block header with a preset target difficulty, and, depending on the comparison result, completes the proof of work or increases the nonce of the block header by 1 to calculate the hash value of the block header.

6. In Paragraph 1, In the step of adding a new block to the above blockchain network, A battery data management method in which the blockchain network creates a new block upon completion of the proof of work, verifies the new block, and adds the new block according to the verification result.

7. In Paragraph 1, A battery data management method further comprising the step of verifying the integrity of the data and providing the data whose integrity has been verified when the blockchain network receives a data access request through a blockchain API (Application Programming Interface).

8. In Paragraph 7, In the step of verifying the integrity of the above data and providing the above data whose integrity has been verified, A battery data management method in which the blockchain network identifies a block containing the data requested through the blockchain API, calculates the Merkle path of the data in the Merkle tree of the identified block, recalculates the Merkle root using the Merkle path, and verifies the integrity of the data by comparing the recalculated Merkle root with the Merkle root of the block header to determine whether they match.

9. A step in which the main battery management system collects battery data, encrypts and signs the collected data, generates a token using a pre-assigned API (Application Programming Interface) key, and then transmits the generated token and the encrypted data to a blockchain API; A step in which the blockchain API verifies the token and verifies the integrity of the encrypted data, and generates a blockchain transaction according to the verification result; A step in which a validation node validates the validity of the blockchain transaction; A step in which the blockchain network creates a new block and updates the block based on the result of validating the blockchain transaction; and A battery data management method comprising the step of the blockchain API checking the status of the blockchain transaction to generate a response to a data request and transmitting the generated response to the main battery management system.

10. In Paragraph 9, In the step of transmitting the above token and the above encrypted data to the blockchain API, A battery data management method in which the main battery management system normalizes the data to generate a hash value, signs the generated hash value of the data with the private key of the main battery management system, and then packages the data and the hash value of the data to generate packaged data.

11. In Paragraph 10, In the step of transmitting the above token and the above encrypted data to the blockchain API, A battery data management method in which the main battery management system includes the token in the HTTPS request header and includes the identification information of the local battery management system and the packaging data in the HTTPS request body, and transmits them to the blockchain API.

12. In Paragraph 10, In the step of generating the above blockchain transaction, A battery data management method in which the blockchain API verifies the signature using the public key of the main battery management system and recalculates the hash value of the data to check whether it matches the hash value of the data generated by the main battery management system.

13. In Paragraph 9, In the step of generating the above blockchain transaction, A battery data management method in which the above blockchain API converts the above data into a blockchain transaction format and adds a timestamp and a unique identifier to the above blockchain transaction.

14. In Paragraph 9, In the step of verifying the validity of the above blockchain transaction, A battery data management method in which the above validation node verifies the validity of the blockchain transaction and newly selects a node to include the blockchain transaction in the new block.

15. In Paragraph 14, In the step where the above blockchain network creates a new block and updates the block, A battery data management method in which the selected node generates the new block and propagates it to the nodes of the blockchain network, and the nodes of the blockchain network verify the validity of the new block and add the new block according to the verification result to synchronize.

Images