Automobile parts information storage method, device and equipment based on alliance blockchain

Abstract

The application discloses a kind of based on alliance block chain's automobile parts information storage method, device and equipment, is related to block chain technology, information storage technical field, the method includes creating alliance block chain, according to the subject involved in the whole life cycle of parts sets the node of alliance block chain, and part node is specified as authorized node;Each subject collects parts information and is written into alliance block chain after using preset processing mode processing, forms to be chained data;To be chained data is divided into block data, and after preliminary verification and final verification of block data based on preset verification rule by authorized node, the chain storage of block data in alliance block chain is completed.This application can adapt to the whole life cycle characteristics of automobile parts, consider data credibility and storage efficiency, realize the credible evidence of parts whole-process information, safe sharing and fine authority control.

Description

Technical Field

[0001] This application relates to the fields of blockchain technology and information storage technology, specifically to a method, device, and equipment for storing automotive parts information based on a consortium blockchain. Background Technology

[0002] As a core component of the automotive industry, the quality and safety of automotive parts directly affect the performance of the entire vehicle and the lives of its occupants. With the deepening of globalization in the automotive industry, the parts supply chain is characterized by "multi-level, cross-regional, and complex participants." From design and R&D, production and manufacturing, warehousing and logistics, vehicle assembly to after-sales maintenance, it involves several types of participants, including R&D units, factories, logistics providers, and repair shops. The entire lifecycle data is scattered in centralized systems at each stage, leading to many challenges for traditional traceability models, such as insufficient data credibility, susceptibility to tampering and forgery, severe information silos, and low efficiency in cross-stage traceability.

[0003] Therefore, how to achieve reliable data storage, efficient cross-stage traceability, and a balance between transparency and privacy protection for automotive parts information throughout its entire lifecycle, and provide effective technical support for automotive parts information management, has become an urgent problem to be solved. Summary of the Invention

[0004] This application provides a method, device, and equipment for storing automotive parts information based on consortium blockchain, which can adapt to the characteristics of the entire life cycle of automotive parts, take into account both data credibility and storage efficiency, and realize the trusted storage, secure sharing, and refined access control of parts information throughout the entire process.

[0005] In a first aspect, embodiments of this application provide a method for storing automotive parts information based on a consortium blockchain, the method comprising: Create a consortium blockchain, set up the nodes of the consortium blockchain according to the main entities involved in the entire life cycle of the parts, designate some nodes as authorized nodes, and the nodes connected to the consortium blockchain hold digital certificates generated in the form of SBT. Each entity collects component information, processes it using a preset processing method, and then writes it into the consortium blockchain to form data to be uploaded to the chain. The data to be uploaded to the blockchain is divided into blocks. Authorized nodes perform preliminary and final verification of the block data based on preset verification rules, and then complete the chain storage of the block data on the consortium blockchain.

[0006] In conjunction with the first aspect, in one implementation, the creation of the consortium blockchain involves setting up nodes for the consortium blockchain based on the entities involved in the entire lifecycle of the component, designating some nodes as authorized nodes, and ensuring that nodes accessing the consortium blockchain hold digital certificates generated in SBT form. Specifically, this includes: Based on the entities involved in the entire lifecycle of parts design and development, production and manufacturing, warehousing and logistics, vehicle assembly and after-sales maintenance, nodes for accessing the consortium blockchain are set up. These entities include OEMs, regulatory agencies, R&D units, factories, logistics departments and after-sales departments. The nodes where the OEMs and regulatory agencies are located are designated as authorized nodes; In this context, nodes connected to the consortium blockchain hold digital certificates generated in the form of SBTs. These digital certificates are non-transferable NFTs, and their metadata includes a node ID, a role identifier array, and an issuer signature. The node's address is also bound to the digital certificate.

[0007] In conjunction with the first aspect, in one implementation, the entities collect component information, process it using a preset processing method, and then write it into the consortium blockchain to form data to be uploaded to the chain. Specifically, when the R&D unit and the factory collect component information, the process includes: After the components are manufactured by the R&D unit and the factory, a component UID is generated and basic component information is collected. The basic component information includes design parameters, production information, and quality assurance information. After encapsulating the component UID and basic component information according to the preset data format of the consortium blockchain, the storage access contract is called. The data integrity and node permission validity are verified based on the storage access contract. After the verification is passed, the core fields of the component UID and basic information of the component, as well as the hash value of the component UID and basic information of the component, are written into the consortium blockchain. For unstructured data in the basic information of components, an encryption algorithm is used to encrypt the data and then store it in fragments in the factory's local encrypted database and distributed file system. The fragment hash value and file index are written into the consortium blockchain. The encryption algorithm is an encryption method in which the encryption parameters change with multi-dimensional dynamic factors, specifically K=KDF(Hprev⊕Pad(T)||C||R), where K represents the dynamic encryption parameters, KDF represents the key derivation function, Hprev represents the ciphertext hash of the last data recorded on the chain, Pad(T) represents the timestamp of the current data recorded on the chain, C represents the verification value of the business key field in the data to be encrypted, and R represents a one-time random number generated by the smart contract.

[0008] In conjunction with the first aspect, in one implementation, each entity collects component information, processes it using a preset processing method, and then writes it into the consortium blockchain to form data to be uploaded to the chain. Specifically, when the logistics department collects component information, it includes: Collect logistics data for parts during the parts transportation process; After the storage access contract verifies that the logistics data format is compliant, the core fields of the logistics data and the hash value of the logistics data are written into the consortium blockchain; The raw logistics data is encrypted and stored in the logistics department's local database, and the data storage path index is written into the consortium blockchain.

[0009] In conjunction with the first aspect, in one implementation, each entity collects component information, processes it using a preset processing method, and then writes it into the consortium blockchain to form data to be uploaded to the chain. Specifically, when the OEM collects component information, it includes: In the OEM assembly process, component assembly information is collected, including component UID, corresponding vehicle VIN code, assembly time, and assembly quality inspection results. The access control contract requests the hash value of the evidence information of the parts on the consortium blockchain to perform a consistency check before assembly. After the check is passed, the part UID and the vehicle VIN code are uniquely bound together. The structured data in the component assembly information is encrypted using a hash algorithm and stored in the OEM's local encrypted database. The hash value of the structured data is then written into the consortium blockchain.

[0010] In conjunction with the first aspect, in one implementation, each entity collects component information, processes it using a preset processing method, and then writes it into the consortium blockchain to form data to be uploaded to the chain. Specifically, when the after-sales department collects component information, it includes: When parts malfunction during the after-sales process, non-sensitive data is packaged in the after-sales data format, and after verifying compliance by calling the storage access contract, it is written to the consortium blockchain. Sensitive and private data are encrypted using a hash algorithm and stored in the after-sales department's local database and IPFS distributed nodes. The hash values ​​of sensitive and private data, along with access permission identifiers, are written into the consortium blockchain.

[0011] In conjunction with the first aspect, in one implementation, the process of dividing the data to be uploaded to the blockchain into blocks, and then authorizing nodes to perform preliminary and final verification of the block data based on preset verification rules, completes the chained storage of the block data on the consortium blockchain, specifically including: Based on data type and sensitivity level, the data to be uploaded to the blockchain is classified and divided into blocks to form block data. Each block data includes a block header and a block body. The authorized node where the OEM is located verifies the data format and integrity of the block data, as well as the identity of the node corresponding to the block data. After the verification is successful, the authorized node where the OEM is located sends the block data to the sorting node of the consortium blockchain. The sorting node is deployed by the OEM's dedicated server. Block data enters the information pool to be packaged. The sorting node sorts all the block data in the information pool to be packaged according to the timestamp. The information pool to be packaged has multiple partitions according to data type. The authorized node where the OEM is located broadcasts the block data to all authorized nodes through the consortium blockchain P2P network; Each authorized node receives block data and performs final verification. After the final verification is passed, each node updates its local blockchain ledger and appends the block data to the end of the local ledger blockchain according to the sequence number, forming a chain storage structure. The final verification involves checking whether the hash of the previous block in the current block header is consistent with the hash of the last block in the local ledger, and whether the Merkle root hash of the current block body is consistent with the block header record.

[0012] In conjunction with the first aspect, in one embodiment, the automotive component information storage method further includes: When data tracing is required, the querying party initiates a tracing request, submits its own identity identifier and query target, and verifies the querying party's identity and query permissions through an access control contract. Once the verification is successful, the traceability contract is invoked to locate the corresponding data hash value and storage index stored on the consortium blockchain based on the query target. When the query target is core field data stored on the consortium blockchain, the traceability contract returns directly, forming a traceability log.

[0013] Secondly, embodiments of this application provide an automotive parts information storage device based on a consortium blockchain, the automotive parts information storage device based on a consortium blockchain comprising: The creation module is used to create a consortium blockchain. It sets up the nodes of the consortium blockchain according to the main entities involved in the entire life cycle of the component, designates some nodes as authorized nodes, and the nodes connected to the consortium blockchain hold digital certificates generated in the form of SBT. The writing module is used to process the component information collected by each entity using a preset processing method and then write it into the consortium blockchain to form data to be uploaded to the chain. The on-chain module is used to divide the data to be on-chain into blocks, so that authorized nodes can perform preliminary and final verification of the block data based on preset verification rules, and then complete the on-chaining of the block data on the consortium blockchain.

[0014] Thirdly, this application provides an automotive parts information storage device based on a consortium blockchain. The automotive parts information storage device based on a consortium blockchain includes a processor, a memory, and an automotive parts information storage program based on a consortium blockchain stored in the memory and executable by the processor. When the automotive parts information storage program based on a consortium blockchain is executed by the processor, it implements the steps of the automotive parts information storage method based on a consortium blockchain described above.

[0015] The beneficial effects of the technical solutions provided in this application include: By creating a consortium blockchain, nodes are set up according to the main entities involved in the entire life cycle of automotive parts, and some nodes are designated as authorized nodes. Each entity then collects part information, processes it using preset methods, and writes it into the consortium blockchain to form data to be uploaded to the chain. This data is then divided into blocks to form block data. Authorized nodes perform preliminary and final verification of the block data based on preset verification rules, thus completing the chained storage of the block data on the consortium blockchain. This approach can adapt to the characteristics of the entire life cycle of automotive parts, balance data credibility and storage efficiency, and achieve trusted evidence storage, secure sharing, and refined access control of part information throughout the entire process. Attached Figure Description

[0016] Figure 1 This is a flowchart illustrating the automotive parts information storage method based on consortium blockchain proposed in this application. Figure 2 A schematic diagram illustrating the traceability of automotive parts information; Figure 3 This is a schematic diagram of the functional modules of the automotive parts information storage device based on consortium blockchain in this application; Figure 4 This is a schematic diagram of the hardware structure of the automotive parts information storage device based on consortium blockchain in this application. Detailed Implementation

[0017] To enable those skilled in the art to better understand the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present application, and not all embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of the present application.

[0018] To make the objectives, technical solutions, and advantages of this application clearer, the embodiments of this application will be described in further detail below with reference to the accompanying drawings.

[0019] In the first aspect, the embodiments of this application provide a method for storing automotive parts information based on consortium blockchain. In response to the problems of difficulty in traceability and insufficient data credibility in the current storage of automotive parts information throughout its entire life cycle, a consortium blockchain information storage scheme is proposed that adapts to the characteristics of the entire life cycle of automotive parts and takes into account both data credibility and storage efficiency, so as to realize the trusted evidence storage, secure sharing and refined permission control of the entire process information of parts.

[0020] In one embodiment, reference is made to Figure 1 , Figure 1 This is a flowchart illustrating the automotive parts information storage method based on consortium blockchain proposed in this application. Figure 1 As shown, the method for storing automotive parts information based on consortium blockchain includes: S1: Create a consortium blockchain, set up the nodes of the consortium blockchain according to the main entities involved in the entire life cycle of the component, designate some nodes as authorized nodes, and the nodes connected to the consortium blockchain hold digital certificates generated in the form of SBT. S2: Each entity collects component information and processes it using a preset processing method before writing it into the consortium blockchain to form data to be uploaded to the chain. S3: The data to be uploaded to the blockchain is divided into blocks. Authorized nodes perform preliminary and final verification of the block data based on preset verification rules, and then complete the uploading of the block data to the consortium blockchain.

[0021] Furthermore, in one embodiment, a consortium blockchain is created, and the nodes of the consortium blockchain are set according to the entities involved in the entire life cycle of the component. Some nodes are designated as authorized nodes, and the nodes connected to the consortium blockchain hold digital certificates generated in the form of SBT. Specifically, this includes: S101: Based on the entities involved in the entire lifecycle of parts design and development, production and manufacturing, warehousing and logistics, vehicle assembly and after-sales maintenance, the nodes connected to the consortium blockchain are set up. These entities include OEMs, regulatory agencies, R&D units, factories, logistics departments and after-sales departments. S102: Designate the nodes where the OEM and regulatory agencies are located as authorized nodes; In this system, nodes connected to the consortium blockchain hold digital certificates generated in the form of SBT (Soulbound Token). These digital certificates are non-transferable NFTs (Non-Fungible Tokens), and the metadata of the digital certificate includes the node ID, role identifier array, and issuer signature. The node's address is bound to the digital certificate, and the on-chain access right is automatically granted after the holding relationship is verified through a smart contract.

[0022] Specifically, all stakeholders throughout the entire lifecycle of a vehicle, from component design and development, production and manufacturing, warehousing and logistics, vehicle assembly to after-sales maintenance, are assigned corresponding nodes on the consortium blockchain. Authorized nodes are jointly managed by OEMs and regulatory agencies. R&D units, factories, logistics departments, and after-sales departments have the right to legally access the consortium blockchain P2P network after completing certification. In other words, OEMs act as authorized nodes, and regulatory agencies also act as authorized nodes.

[0023] Furthermore, in one embodiment, each entity collects component information, processes it using a preset processing method, and then writes it into the consortium blockchain to form data to be uploaded to the chain. Specifically, when the R&D unit and the factory collect component information, the process includes: S201: After the parts are manufactured by the R&D unit and the factory, a part UID is generated and basic part information is collected. The basic part information includes design parameters, production information and quality assurance information. S202: After encapsulating the component UID and basic component information according to the preset data format of the consortium blockchain, call the storage access contract; S203: Verify data integrity and node permission legality based on storage access contract. After verification, write the core fields of component UID and component basic information, as well as the overall hash value of component UID and component basic information, into the consortium blockchain. For unstructured data in the basic information of components, an encryption algorithm is used to encrypt the data and then store it in fragments in the factory's local encrypted database and distributed file system. The fragment hash value and file index are written into the consortium blockchain. The encryption algorithm is an encryption method in which the encryption parameters change with multi-dimensional dynamic factors, specifically K=KDF(Hprev⊕Pad(T)||C||R), where K represents the dynamic encryption parameters, KDF represents the key derivation function, Hprev represents the ciphertext hash of the last data recorded on the chain, Pad(T) represents the timestamp of the current data recorded on the chain, C represents the verification value of the business key field in the data to be encrypted, and R represents a one-time random number generated by the smart contract.

[0024] The encryption algorithm in this application employs encryption parameters that vary with multi-dimensional dynamic factors. During encryption, the key (or encryption parameters) simultaneously depends on: block height / timestamp, the ciphertext hash of the previous on-chain data, the business field verification value of the data to be encrypted, and a random number generated by the smart contract. This prevents attackers from predicting the encryption parameters, and each piece of on-chain information has a unique encryption context. Then, K is used to symmetrically encrypt the data to be encrypted, D, to obtain ciphertext E. D and E are stored on the blockchain, and the hash of this ciphertext is recorded as Hprev for the next on-chain data.

[0025] Specifically, after the components are manufactured by the R&D unit and the factory, a UID (e.g., ENG-P202405-1715000000-SM2 supplier signature value) is generated for the components. Simultaneously, basic component information, including design parameters, production information, and quality assurance information, is collected. The UID and basic information are then encapsulated according to the pre-set data format of the consortium blockchain. A storage access contract is then invoked, and the contract automatically verifies data integrity and node permission legitimacy. Upon successful verification, the UID, core fields of the basic information (i.e., key information, which can be manually determined as needed), and the hash value of the overall data calculated using SM3 are written to the consortium blockchain. Unstructured data in the basic information, such as design drawings and high-definition quality inspection images, are encrypted using an algorithm and stored in shards in the factory's local encrypted database and distributed file system (IPFS). Only the shard hash values ​​and file indexes are stored on the blockchain. In this application, SM3 and SM4 represent hash algorithms.

[0026] It's important to clarify that a consortium blockchain is essentially a distributed ledger, where each full node stores a complete copy of the data. A high-resolution quality inspection image is typically 10MB to 50MB, while a set of design drawings can be in the gigabyte range. Directly uploading these files to the blockchain would severely hinder transactions due to the limited block time and block size. The server disks of all participants (OEMs, suppliers, logistics providers) would quickly become full, preventing them from joining the network. By using encryption, sharding, and a hybrid storage approach of storing hashes on-chain and full-text data off-chain, the storage and consensus load of the consortium blockchain is reduced, while achieving tamper-proof notarization of large file data, privacy protection, and efficient retrieval on the factory side, balancing security and engineering feasibility.

[0027] Furthermore, in one embodiment, each entity collects component information, processes it using a preset processing method, and then writes it into the consortium blockchain to form data to be uploaded to the chain. Specifically, when the logistics department collects component information, it includes: S211: Collect logistics data for parts during the parts transportation process; S212: After the storage access contract verifies that the logistics data format is compliant, the core fields of the logistics data and the hash value of the logistics data are written into the consortium blockchain; The raw logistics data is encrypted and stored in the logistics department's local database, and the data storage path index is written into the consortium blockchain.

[0028] Specifically, in the parts transportation process, logistics data, including transportation origin and destination information, is collected. Then, the data format is verified to be compliant by the access contract. The core fields of the logistics data and the SM3 hash value of the logistics data are written into the consortium blockchain. The original logistics data is encrypted (using a hash algorithm for encryption) and stored in the local database of the logistics department. The data storage path index is stored synchronously on the chain.

[0029] Furthermore, in one embodiment, each entity collects component information, processes it using a preset processing method, and then writes it into the consortium blockchain to form data to be uploaded to the chain. Specifically, when the OEM collects component information, it includes: S221: During the assembly process at the OEM, collect component assembly information, which includes component UID, the corresponding vehicle VIN code of the component, assembly time, and assembly quality inspection results. S222: Request the hash value of the evidence information of the parts on the consortium blockchain through the permission control contract, perform consistency verification before assembly, and bind the part UID and the vehicle VIN code uniquely after the verification is passed. S223: The structured data in the component assembly information is encrypted using a hash algorithm and stored in the OEM's local encrypted database. The hash value of the structured data is then written into the consortium blockchain.

[0030] Specifically, in the OEM assembly process, component assembly information is collected, including component UID, corresponding vehicle VIN, assembly time, and assembly quality inspection results. The hash value of the on-chain evidence information of the component is requested through the permission control contract to complete the consistency verification before assembly. After the verification is passed, the component UID is uniquely bound to the vehicle VIN. The structured data such as assembly time and assembly inspection results are encrypted using the SM4 algorithm and stored in the OEM's local encrypted database. The hash value of the structured data is calculated using SM3 and written to the consortium blockchain.

[0031] Furthermore, in one embodiment, each entity collects component information, processes it using a preset processing method, and then writes it into the consortium blockchain to form data to be uploaded to the chain. Specifically, when the after-sales department collects component information, it includes: S231: When a component fails during the after-sales process, non-sensitive data is encapsulated in the after-sales data format, and after verifying compliance by calling the storage access contract, it is written to the consortium blockchain. S232: Sensitive and private data are encrypted using a hash algorithm and stored in the after-sales department's local database and IPFS (a distributed file system) distributed nodes. The hash values ​​of sensitive and private data and access permission identifiers are written into the consortium blockchain.

[0032] Specifically, when a component malfunctions during the after-sales process, non-sensitive data such as the component's UID, quality inspection results, fault records, and replacement results are encapsulated in an after-sales data format. After verifying compliance by calling the storage access contract, the data is directly written to the consortium blockchain. Sensitive data such as fault diagnosis reports and repair videos, along with privacy data, are encrypted using the SM4 algorithm and stored in the after-sales department's local database and IPFS distributed nodes. Only the data hash value and access permission identifier are stored on the blockchain.

[0033] Furthermore, in one embodiment, after the data to be uploaded to the blockchain is divided into blocks, the authorized node performs preliminary and final verification of the block data based on preset verification rules, and then completes the chain storage of the block data on the consortium blockchain, specifically including: S301: Classify the data to be uploaded to the blockchain based on data type and sensitivity level, and divide the data to be uploaded to the blockchain into blocks to form block data. Each block data includes a block header and a block body. It should be noted that in the consortium blockchain, all information to be uploaded to the chain adopts a classified and block-based storage strategy: first, it is classified according to data type (structured data / unstructured data) and sensitivity level (public data / internal data). Smaller block sizes and faster block times are set for highly sensitive data blocks to ensure they are prioritized for consensus confirmation and reduce the risk of exposure in the mempool. Larger capacity (e.g., 2MB) is used for low-sensitivity data blocks, focusing on throughput. When storing information, it is first divided into blocks, each including a block header and a block body. Current component-related data is stored in the block body. Only after passing the storage access contract verification can it enter the block packaging process. The block header includes information such as hash value and timestamp. S302: The authorized node where the OEM is located verifies the data format and integrity of the block data, as well as the identity of the node corresponding to the block data (i.e., the upload node corresponding to the current block data). After the verification is successful, the authorized node where the OEM is located sends the block data to the sorting node of the consortium blockchain. The sorting node is deployed by the OEM's dedicated server. Specifically, for the block data submitted by each entity, the core node, which is the OEM, first performs dual verification: first, node identity verification, and second, data format and integrity verification; after the dual verification is passed, the core node sends the block data to the consortium blockchain. S303: Block data enters the information pool to be packaged. The sorting node sorts all the block data in the information pool to be packaged according to the timestamp. The information pool to be packaged has multiple partitions according to data type. Specifically, block data enters the information pool to be packaged. The information pool is divided into independent partitions according to data type, namely R&D data area, production data area, logistics data area, assembly data area and after-sales data area, to avoid low query efficiency caused by mixed storage of different types of data; the sorting node sorts all block data in the information pool according to the information submission timestamp to generate an ordered transaction set to avoid block data chaos. S304: The authorized node where the OEM is located broadcasts the block data to all authorized nodes through the consortium blockchain P2P network; S305: Each authorized node receives block data and performs final verification to ensure the continuity and integrity of the chain. After the final verification is passed, each node updates its local blockchain ledger and appends the block data to the end of the local ledger blockchain according to the sequence number, forming a chain storage structure. The final verification involves checking whether the hash of the previous block in the current block header is consistent with the hash of the last block in the local ledger, and whether the Merkle root hash of the current block body is consistent with the block header record.

[0034] Furthermore, the automotive parts information storage method of this application also includes: S51: When data tracing is required, the querying party initiates a tracing request, submits its own identity identifier and query target, and verifies the querying party's identity and query permissions through the access control contract; S52: After verification, call the traceability contract to locate the corresponding data hash value and storage index stored on the consortium blockchain according to the query target; When the query target is core field data stored on the consortium blockchain, the traceability contract returns directly, forming a traceability log.

[0035] See Figure 2 The diagram illustrates the process of tracing automotive parts information. When data tracing is required, the querying party initiates a tracing request, submitting its own identity and query target. The access control contract verifies the querying party's identity and query permissions. Once the permission verification is successful, the tracing contract is invoked to locate the corresponding data hash value and storage index stored on the blockchain based on the query target. For core field data directly stored on the blockchain (which can be predefined based on actual conditions, such as privacy and importance), the tracing contract returns the data directly, forming a tracing log.

[0036] The automotive parts information storage method based on consortium blockchain proposed in this application achieves 100% reliable evidence storage of parts' full lifecycle data through the immutability and encryption algorithm of consortium blockchain. By classifying and categorizing data and using on-chain and off-chain collaborative storage, the storage cost of consortium blockchain is reduced, the data read and write response speed is improved to the second level, and the use of smart contracts for automated management reduces manual intervention, thereby reducing compliance costs. It is adaptable to all types of parts scenarios, compatible with existing systems, and has strong scalability.

[0037] Secondly, embodiments of this application also provide an automotive parts information storage device based on a consortium blockchain.

[0038] In one embodiment, reference is made to Figure 3 , Figure 3 This is a schematic diagram of the functional modules of the automotive parts information storage device based on consortium blockchain, as described in this application. Figure 3 As shown, the automotive parts information storage device based on consortium blockchain includes: a creation module, a writing module, and an on-chain module.

[0039] The creation module is used to create a consortium blockchain. It sets up the nodes of the consortium blockchain according to the main entities involved in the entire life cycle of the component, and designates some nodes as authorized nodes. The nodes connected to the consortium blockchain hold digital certificates generated in the form of SBT. The writing module is used to process the component information collected by each entity using a preset processing method and write it into the consortium blockchain to form data to be uploaded to the chain. The uploading module is used to divide the data to be uploaded to the chain into blocks, so that the authorized nodes can perform preliminary verification and final verification of the block data based on preset verification rules, and then complete the uploading of the block data to the consortium blockchain.

[0040] Thirdly, this application provides an automotive parts information storage device based on a consortium blockchain. The automotive parts information storage device based on a consortium blockchain can be a personal computer (PC), a laptop, a server, or other device with data processing capabilities.

[0041] Reference Figure 4 , Figure 4 This is a schematic diagram of the hardware structure of an automotive parts information storage device based on a consortium blockchain, as described in an embodiment of this application. In this embodiment, the automotive parts information storage device based on a consortium blockchain may include a processor, a memory, a communication interface, and a communication bus.

[0042] The communication bus can be of any type and is used to interconnect the processor, memory, and communication interface.

[0043] The communication interface includes input / output (I / O) interfaces, physical interfaces, and logical interfaces used for interconnecting components within the blockchain-based automotive parts information storage device, as well as interfaces used for interconnecting the blockchain-based automotive parts information storage device with other devices (such as other computing devices or user devices). Physical interfaces can be Ethernet interfaces, fiber optic interfaces, ATM interfaces, etc.; user devices can be displays, keyboards, etc.

[0044] Memory can be various types of storage media, such as random access memory (RAM), read-only memory (ROM), non-volatile RAM (NVRAM), flash memory, optical storage, hard disk, programmable ROM (PROM), erasable PROM (EPROM), electrically erasable PROM (EEPROM), etc.

[0045] The processor can be a general-purpose processor, which can call the automotive parts information storage program based on the consortium blockchain stored in the memory and execute the automotive parts information storage method based on the consortium blockchain provided in the embodiments of this application. For example, the general-purpose processor can be a central processing unit (CPU). The method executed when the automotive parts information storage program based on the consortium blockchain is called can refer to the various embodiments of the automotive parts information storage method based on the consortium blockchain of this application, and will not be repeated here.

[0046] Those skilled in the art will understand that Figure 4 The hardware structure shown does not constitute a limitation of this application and may include more or fewer components than shown, or combine certain components, or have different component arrangements.

[0047] The terms "comprising" and "having," and any variations thereof, in the specification, claims, and accompanying drawings of this application are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or apparatus that includes a series of steps or units is not limited to the listed steps or units, but may optionally include steps or units not listed, or may optionally include other steps or units inherent to such process, method, product, or apparatus. The terms "first," "second," and "third," etc., are used to distinguish different objects, etc., and do not indicate a sequence, nor do they limit "first," "second," and "third" to different types.

[0048] In the description of the embodiments of this application, terms such as "exemplary," "for example," or "for instance" are used to indicate examples, illustrations, or explanations. Any embodiment or design described as "exemplary," "for example," or "for instance" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or designs. Specifically, the use of terms such as "exemplary," "for example," or "for instance" is intended to present the relevant concepts in a concrete manner.

[0049] In the description of the embodiments of this application, unless otherwise stated, " / " means "or". For example, A / B can mean A or B. The "and / or" in the text is merely a description of the relationship between related objects, indicating that there can be three relationships. For example, A and / or B can mean: A exists alone, A and B exist simultaneously, and B exists alone. In addition, in the description of the embodiments of this application, "multiple" means two or more.

[0050] In some processes described in the embodiments of this application, multiple operations or steps are included in a specific order. However, it should be understood that these operations or steps may not be executed in the order they appear in the embodiments of this application, or they may be executed in parallel. The sequence number of the operation is only used to distinguish different operations, and the sequence number itself does not represent any execution order. In addition, these processes may include more or fewer operations, and these operations or steps may be executed sequentially or in parallel, and these operations or steps may be combined.

[0051] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) as described above, and includes several instructions to cause a terminal device to execute the methods described in the various embodiments of this application.

[0052] The above are merely preferred embodiments of this application and do not limit the patent scope of this application. Any equivalent structural or procedural transformations made using the content of this application's specification and drawings, or direct or indirect applications in other related technical fields, are similarly included within the patent protection scope of this application.

Claims

1. A method for storing automotive parts information based on consortium blockchain, characterized in that, The method for storing automotive parts information based on consortium blockchain includes: Create a consortium blockchain, set up the nodes of the consortium blockchain according to the main entities involved in the entire life cycle of the parts, designate some nodes as authorized nodes, and the nodes connected to the consortium blockchain hold digital certificates generated in the form of SBT. Each entity collects component information, processes it using a preset processing method, and then writes it into the consortium blockchain to form data to be uploaded to the chain. The data to be uploaded to the blockchain is divided into blocks. Authorized nodes perform preliminary and final verification of the block data based on preset verification rules, and then complete the chain storage of the block data on the consortium blockchain.

2. The method for storing automotive parts information based on consortium blockchain as described in claim 1, characterized in that, The creation of the consortium blockchain involves setting up nodes based on the entities involved in the entire lifecycle of the component, designating some nodes as authorized nodes, and ensuring that nodes connected to the consortium blockchain hold digital certificates generated in SBT format. Specifically, this includes: Based on the entities involved in the entire lifecycle of parts design and development, production and manufacturing, warehousing and logistics, vehicle assembly and after-sales maintenance, nodes for accessing the consortium blockchain are set up. These entities include OEMs, regulatory agencies, R&D units, factories, logistics departments and after-sales departments. The nodes where the OEMs and regulatory agencies are located are designated as authorized nodes; In this context, nodes connected to the consortium blockchain hold digital certificates generated in the form of SBTs. These digital certificates are non-transferable NFTs, and their metadata includes a node ID, a role identifier array, and an issuer signature. The node's address is also bound to the digital certificate.

3. The method for storing automotive parts information based on consortium blockchain as described in claim 2, characterized in that, Each entity collects component information, processes it using a preset method, and then writes it into the consortium blockchain to form data to be uploaded to the chain. Specifically, the component information collection process by R&D units and factories includes: After the components are manufactured by the R&D unit and the factory, a component UID is generated and basic component information is collected. The basic component information includes design parameters, production information, and quality assurance information. After encapsulating the component UID and basic component information according to the preset data format of the consortium blockchain, the storage access contract is called. The data integrity and node permission validity are verified based on the storage access contract. After the verification is passed, the core fields of the component UID and basic information of the component, as well as the hash value of the component UID and basic information of the component, are written into the consortium blockchain. For unstructured data in the basic information of components, an encryption algorithm is used to encrypt the data and then store it in fragments in the factory's local encrypted database and distributed file system. The fragment hash value and file index are written into the consortium blockchain. The encryption algorithm is an encryption method in which the encryption parameters change with multi-dimensional dynamic factors, specifically K=KDF(Hprev⊕Pad(T)||C||R), where K represents the dynamic encryption parameters, KDF represents the key derivation function, Hprev represents the ciphertext hash of the last data recorded on the chain, Pad(T) represents the timestamp of the current data recorded on the chain, C represents the verification value of the business key field in the data to be encrypted, and R represents a one-time random number generated by the smart contract.

4. The method for storing automotive parts information based on consortium blockchain as described in claim 2, characterized in that, Each entity collects component information, processes it using a preset method, and then writes it into the consortium blockchain to form data to be uploaded to the chain. Specifically, when the logistics department collects component information, it includes: Collect logistics data for parts during the parts transportation process; After the storage access contract verifies that the logistics data format is compliant, the core fields of the logistics data and the hash value of the logistics data are written into the consortium blockchain; The raw logistics data is encrypted and stored in the logistics department's local database, and the data storage path index is written into the consortium blockchain.

5. The method for storing automotive parts information based on consortium blockchain as described in claim 2, characterized in that, Each entity collects component information, processes it using a preset method, and then writes it into the consortium blockchain to form data to be uploaded to the chain. Specifically, when the OEM collects component information, it includes: In the OEM assembly process, component assembly information is collected, including component UID, corresponding vehicle VIN code, assembly time, and assembly quality inspection results. The access control contract requests the hash value of the evidence information of the parts on the consortium blockchain to perform a consistency check before assembly. After the check is passed, the part UID and the vehicle VIN code are uniquely bound together. The structured data in the component assembly information is encrypted using a hash algorithm and stored in the OEM's local encrypted database. The hash value of the structured data is then written into the consortium blockchain.

6. The method for storing automotive parts information based on consortium blockchain as described in claim 2, characterized in that, Each entity collects component information, processes it using a preset method, and then writes it into the consortium blockchain, forming data to be uploaded to the chain. Specifically, when the after-sales department collects component information, it includes: When parts malfunction during the after-sales process, non-sensitive data is packaged in the after-sales data format, and after verifying compliance by calling the storage access contract, it is written to the consortium blockchain. Sensitive and private data are encrypted using a hash algorithm and stored in the after-sales department's local database and IPFS distributed nodes. The hash values ​​of sensitive and private data, along with access permission identifiers, are written into the consortium blockchain.

7. The method for storing automotive parts information based on consortium blockchain as described in claim 2, characterized in that, The process involves dividing the data to be uploaded to the blockchain into blocks. Authorized nodes then perform preliminary and final verification of the block data based on preset verification rules, completing the chained storage of the block data on the consortium blockchain. Specifically, this includes: Based on data type and sensitivity level, the data to be uploaded to the blockchain is classified and divided into blocks to form block data. Each block data includes a block header and a block body. The authorized node where the OEM is located verifies the data format and integrity of the block data, as well as the identity of the node corresponding to the block data. After the verification is successful, the authorized node where the OEM is located sends the block data to the sorting node of the consortium blockchain. The sorting node is deployed by the OEM's dedicated server. Block data enters the information pool to be packaged. The sorting node sorts all the block data in the information pool to be packaged according to the timestamp. The information pool to be packaged has multiple partitions according to data type. The authorized node where the OEM is located broadcasts the block data to all authorized nodes through the consortium blockchain P2P network; Each authorized node receives block data and performs final verification. After the final verification is passed, each node updates its local blockchain ledger and appends the block data to the end of the local ledger blockchain according to the sequence number, forming a chain storage structure. The final verification involves checking whether the hash of the previous block in the current block header is consistent with the hash of the last block in the local ledger, and whether the Merkle root hash of the current block body is consistent with the block header record.

8. The method for storing automotive parts information based on consortium blockchain as described in claim 1, characterized in that, The method for storing automotive component information also includes: When data tracing is required, the querying party initiates a tracing request, submits its own identity identifier and query target, and verifies the querying party's identity and query permissions through an access control contract. Once the verification is successful, the traceability contract is invoked to locate the corresponding data hash value and storage index stored on the consortium blockchain based on the query target. When the query target is core field data stored on the consortium blockchain, the traceability contract returns directly, forming a traceability log.

9. A device for storing automotive parts information based on a consortium blockchain, characterized in that, The automotive parts information storage device based on consortium blockchain includes: The creation module is used to create a consortium blockchain. It sets up the nodes of the consortium blockchain according to the main entities involved in the entire life cycle of the component, designates some nodes as authorized nodes, and the nodes connected to the consortium blockchain hold digital certificates generated in the form of SBT. The writing module is used to process the component information collected by each entity using a preset processing method and then write it into the consortium blockchain to form data to be uploaded to the chain. The on-chain module is used to divide the data to be on-chain into blocks, so that authorized nodes can perform preliminary and final verification of the block data based on preset verification rules, and then complete the on-chaining of the block data on the consortium blockchain.

10. A storage device for automotive parts information based on consortium blockchain, characterized in that, The automotive parts information storage device based on consortium blockchain includes a processor, a memory, and an automotive parts information storage program based on consortium blockchain stored on the memory and executable by the processor, wherein when the automotive parts information storage program based on consortium blockchain is executed by the processor, it implements the steps of the automotive parts information storage method based on consortium blockchain as described in any one of claims 1 to 8.

Images