Construction machinery whole life cycle data credible evidence method and system

Abstract

The application provides a kind of engineering machinery full life cycle data credible evidence storage method and system, it is related to data evidence storage technical field.The method includes: node identification step, according to the equipment category attribute of target engineering machinery loads corresponding category node configuration template, identify whether current business node is evidence storage node, if yes, then according to field mapping rule extraction core field;Abstract generation step, after splicing core field, add file number and time stamp to generate abstract string, generate verification abstract using cryptography abstract algorithm;Evidence storage step, verification abstract, file number, time stamp and identity authentication signature are packaged and written into tamper-proof distributed storage network;Archiving binding step, evidence storage voucher is associated with file number and fuselage legal number, and is written into full life cycle electronic archives.The application is suitable for the full life cycle data credible evidence storage of various engineering machinery.

Description

Technical Field

[0001] This invention relates to the field of data storage technology, specifically to a reliable data storage method and system for the entire lifecycle of engineering machinery. Background Technology

[0002] The core pain point for digital end-to-end services in the construction machinery aftermarket is data credibility. Construction machinery encompasses a wide variety of categories, each with significantly different regulatory rules: forklifts are subject to mandatory biennial inspections as special equipment, excavators require environmental emission testing, and cranes require annual safety device calibration. These cross-category regulatory differences lead to varying certification milestones for different categories. Existing certification solutions are all custom-developed for each category, requiring a completely new certification process for each new category, resulting in costs increasing linearly with the number of categories.

[0003] On the other hand, the entire lifecycle data of construction machinery, covering new vehicle manufacturing, use, maintenance, annual inspection, leasing, transfer of ownership, and scrapping, is easily tampered with. Maintenance records, usage duration, and accident history can be manually modified, resulting in extremely high trust costs in second-hand transactions. Existing evidence preservation solutions are usually independent third-party systems, and the evidence preservation certificates cannot be directly linked to the electronic files of the equipment; queries require redirection to a third-party platform. At the same time, uploading all data to the blockchain is extremely costly and poses a risk of data privacy leaks, while storing only the final result cannot cover the verification needs of the entire process.

[0004] In addition, the scrapping cycle of construction machinery is usually 10 to 25 years, and it changes hands 3 to 5 times on average. After the transfer of ownership, the validity of the certificate is difficult to continue, and the certificate chain is easy to break.

[0005] To address the aforementioned issues, several blockchain-based evidence storage solutions have been proposed. For example, CN116091082A discloses a blockchain-based tower crane equipment integrated management system, which uses a distributed ledger to monitor and store evidence throughout the entire lifecycle of tower cranes. However, this solution only applies to a single tower crane category, with category-specific nodes hard-coded, making cross-category reuse impossible. CN111125141A discloses a power grid asset summary evidence storage solution, employing a combination of on-chain feature summaries and a collaborative database of original data, but it does not address category-specific differences or the continuation of transfer evidence storage. CN119337416A discloses an industrial equipment certification data management method, which writes the hash value of the certification data into the blockchain and uses multi-signature access control, but similarly fails to solve the architectural problem of unified evidence storage across categories.

[0006] Therefore, there is an urgent need in this field for a reliable data storage solution that can cover all categories of construction machinery, support unified cross-category storage, be cost-controllable, and ensure the validity of the stored data throughout its entire lifecycle. Summary of the Invention

[0007] Therefore, the technical problem to be solved by the present invention is to provide a reliable data storage method and system for the entire life cycle of construction machinery, so as to solve the technical problems in the prior art that cross-category data storage cannot be unified, new categories need to be redeveloped, storage is disconnected from electronic files, storage breaks after transfer of ownership, and there is a contradiction between storage cost and data privacy.

[0008] In a first aspect, the present invention provides a method for reliable data storage and verification throughout the entire lifecycle of construction machinery, comprising: The node identification step involves loading a category node configuration template corresponding to the equipment category based on the equipment category attributes of the target construction machinery. The category node configuration template includes evidence storage nodes and field mapping rules corresponding to each evidence storage node. The evidence storage nodes are key business event nodes that require data evidence storage throughout the entire life cycle of the construction machinery. The system identifies whether the current business node is the evidence storage node based on the category node configuration template. If so, it extracts the core fields from the current business data according to the field mapping rules corresponding to the evidence storage node. The abstract generation step involves concatenating the extracted core fields in a predetermined order, adding the file number and timestamp of the target construction machinery, and generating a string to be abstracted. The file number is a globally unique identifier that adapts to the electronic archives of the construction machinery throughout its entire life cycle. A cryptographic digest algorithm is then used to process the string to be abstracted to generate a verification digest. The evidence preservation step involves packaging the verification digest, the file number, the timestamp, and the identity authentication information of the participating entities, and writing them into an immutable distributed storage network to obtain an evidence preservation transaction identifier and evidence preservation certificate. The archiving and binding step involves associating the evidence certificate with the file number and the legal serial number of the target construction machinery, and writing it into the electronic archive of the target construction machinery throughout its entire life cycle.

[0009] Furthermore, in the category node configuration template, the evidence storage nodes include general evidence storage nodes and category-specific evidence storage nodes; The general evidence storage nodes include at least one of the following: new vehicle filing node, initial registration node, maintenance node, transfer node, used vehicle appraisal node, and scrapping and dismantling node; The category-specific evidence storage nodes are configured according to the regulatory rules of different categories, and include at least one of the following: special equipment periodic inspection nodes for forklifts, environmental emission testing nodes for excavators, and safety device verification nodes for cranes.

[0010] Furthermore, the category node configuration template includes a node type identifier, field mapping information, and field concatenation order rules; the field mapping information defines the names of the core fields to be extracted for each device category under each evidence storage node and their data source paths; the field concatenation order rules define the order in which each core field is arranged when generating the string to be digested.

[0011] Furthermore, the equipment category attribute is managed by a remote mapping service and obtained by querying the remote mapping service through the file number; the file number adopts an encoding structure that does not contain category information, and neither the generation of the verification digest nor the packaged data of the evidence storage step contains category information.

[0012] Furthermore, when the target construction machinery is documented, an equipment ownership record is created in the immutable distributed storage network. The equipment ownership record includes the equipment identifier, the current owner identifier, and the ownership creation timestamp.

[0013] Furthermore, the certificate of evidence is associated with both the file number and the legal serial number of the aircraft.

[0014] Furthermore, the method also includes a trusted verification step: In response to a user's request for verification of the target construction machinery, the certificate of the node to be verified is obtained from the electronic archive of the entire life cycle based on the file number of the target construction machinery. Based on the file number, query the remote mapping service to obtain the equipment category attribute of the target construction machinery, and load the corresponding category node configuration template; Based on the field mapping rules in the category node configuration template, the core fields are extracted from the original business data saved in the node to be verified, and the verification summary is regenerated. The regenerated verification digest is compared with the verification digest corresponding to the evidence credential obtained from the immutable distributed storage network. If they match, the verification passes; otherwise, the verification fails.

[0015] Furthermore, the method also includes a transfer continuation step: When the target construction machinery is documented, an equipment ownership record is created in the immutable distributed storage network. The equipment ownership record includes the equipment identifier, the current owner identifier, and the ownership creation timestamp. In response to an ownership transfer request, the original owner signs an ownership transfer transaction in the immutable distributed storage network. The server verifies the legality of the ownership transfer transaction according to preset transfer rules. After verification, the server updates the current owner identifier in the device ownership record. After the ownership transfer is completed, the notarization step of the transfer node is automatically triggered, and the transfer information is written into the tamper-proof distributed storage network.

[0016] Furthermore, in the evidence preservation step, when the current business node involves joint endorsement by multiple participating entities, after each participating entity passes the platform identity authentication, its operation record is bound to the operator's identity identifier and jointly written into the evidence preservation data.

[0017] Secondly, this invention provides a trusted data storage system for the entire lifecycle of construction machinery, comprising: The node identification module is used to load the category node configuration template corresponding to the equipment category based on the equipment category attributes of the target construction machinery. The category node configuration template includes the evidence storage node and the field mapping rules corresponding to each evidence storage node. The evidence storage node is the key business event node that needs to be evidenced by data in the entire life cycle of the construction machinery. The system identifies whether the current business node is the evidence storage node based on the category node configuration template. If so, it extracts the core fields from the current business data according to the field mapping rules corresponding to the evidence storage node. The abstract generation module is used to concatenate the extracted core fields in a predetermined order, add the file number and timestamp of the target construction machinery, and generate a string to be abstracted. The file number is a globally unique identifier that adapts to the electronic archives of the construction machinery throughout its entire life cycle. A cryptographic digest algorithm is used to operate on the string to be abstracted to generate a verification digest. The evidence storage module is used to package the verification digest, the file number, the timestamp, and the identity authentication information of the participating entities, and write them into an immutable distributed storage network to obtain an evidence storage transaction identifier and evidence storage certificate. The archiving and binding module is used to associate and bind the evidence certificate with the file number and the legal serial number of the target construction machinery, and write it into the electronic archive of the target construction machinery throughout its entire life cycle. Beneficial effects

[0018] Through the architectural design that separates the category node configuration template from the general evidence storage process, a single evidence storage system covers all categories of construction machinery. When adding a new category, only a template needs to be created, and the evidence storage process remains unchanged, which greatly reduces the system development and maintenance costs.

[0019] The category attribute is carried by the remote mapping service. The file number adopts an encoding structure that does not contain category information. Neither the verification summary nor the evidence package data contains category information. The evidence data does not expose the category, further protecting the privacy of device information.

[0020] Ownership transfer is achieved through automatic contract execution, the evidence preservation chain continues automatically after equipment transfer, and historical evidence preservation records are complete and traceable, solving the problem of evidence preservation breakage after multiple transfers of construction machinery.

[0021] The certificate of authenticity is automatically bound to the file number and the legal serial number of the device, and is directly connected to the electronic archive system. One-click verification does not require redirection to a third-party platform.

[0022] Verification digests are generated and stored only for the core fields of key nodes, while the original data is kept on a private cloud platform. The total cost of evidence storage for a single device throughout its entire lifecycle can be kept at a very low level, while avoiding the leakage of sensitive business data.

[0023] It supports joint evidence preservation by multiple entities such as inspection agencies, maintenance providers, and trading platforms, and the preserved evidence has stronger legal credibility and is traceable throughout the entire chain. Attached Figure Description

[0024] To make the content of this invention easier to understand, the invention will be further described in detail below with reference to specific embodiments and accompanying drawings.

[0025] Figure 1 This is a flowchart of the trusted data storage method for the entire life cycle of engineering machinery according to Embodiment 1 of the present invention. Detailed Implementation

[0026] The present invention will now be described in detail with reference to the accompanying drawings and embodiments. The principles and features of the present invention are described below with reference to the accompanying drawings. It should be noted that, unless otherwise specified, the embodiments and features described in these embodiments can be combined with each other. The embodiments given are only for explaining the present invention and are not intended to limit the scope of the present invention.

[0027] This invention investigates the core pain point of data credibility faced by the digital end-to-end service in the construction machinery aftermarket: Unified certification is impossible for equipment across different categories: regulatory rules vary significantly across categories. Forklifts are subject to mandatory periodic inspections as special equipment, excavators require environmental emission testing, and cranes require safety device calibration, resulting in different certification stages. Existing solutions are all customized for single categories, requiring redevelopment for each new category, leading to a linear increase in cost with the number of categories.

[0028] Data throughout the entire lifecycle is easily tampered with: maintenance records, usage duration, and accident history can be manually modified, resulting in extremely high trust costs in secondhand transactions.

[0029] The evidence storage and electronic archives cannot be integrated: the existing evidence storage solution is an independent third-party system, and the evidence storage certificate cannot be directly linked to the device's electronic archive. The query requires redirection to the third-party platform.

[0030] There is a conflict between the cost of evidence storage and data privacy: putting all data on the blockchain is extremely costly and can leak sensitive data, while storing only the final result cannot cover the entire process.

[0031] The validity of the certificate cannot be continued after the transfer of ownership: The scrapping cycle of construction machinery is 10-25 years, and it changes hands 3-5 times on average. After the transfer, the certificate preservation chain is broken.

[0032] The following methods can be used to solve the problem of unified evidence storage across product categories: 1) The category node configuration template and the general evidence storage process are separated into an architecture, with one system covering all categories; 2) Only key nodes are verified and stored as digests, suitable for large-scale deployment with tens of millions of devices; 3) The certificate of evidence is automatically bound to the file number and the legal serial number of the device, and is directly connected to the electronic archive; 4) After the transfer of ownership, the ownership transfer is executed automatically through the contract, and the validity of the evidence is automatically extended; 5) Only the digest is verified and stored; the original data is retained on the private cloud platform. 6) Category information is carried by a remote mapping service. Terminology used in this invention: Tamper-proof evidence storage: A method that uploads the verification digest of key data to an immutable distributed storage network to generate verifiable evidence storage certificates, thereby ensuring data credibility.

[0033] File Number: A globally unique identifier that adapts to the electronic files of the entire life cycle of construction machinery. It adopts a four-segment 17-bit coding structure. The category attributes are obtained by remote mapping service. The code itself does not contain category information.

[0034] Machine body legal number: The unique legal identification code for construction machinery as stipulated by the state or the original manufacturer. For forklifts, it is the VIN (Vehicle Identification Number), and for excavators, it is the PIN (Product Identification Code).

[0035] Full lifecycle data: Covers all business data of construction machinery from new vehicle manufacturing, use, maintenance, annual inspection, leasing, transfer of ownership to scrapping.

[0036] Hash digest: A method for converting data of arbitrary length into a fixed-length unique string using a cryptographic algorithm, used to verify that the data has not been tampered with.

[0037] Category Node Configuration Template: Defines the data structure for configuring certification nodes for a specific category of construction machinery. It includes general certification nodes and category-specific certification nodes. When adding a new category, you only need to create a new template without modifying the certification process.

[0038] Construction machinery: including but not limited to forklifts, excavators, loaders, cranes, road rollers, concrete machinery and other types of machinery and equipment used in construction operations. Example 1

[0039] This embodiment presents a method for reliable data storage and verification throughout the entire lifecycle of construction machinery, such as... Figure 1 As shown, this method includes the following steps: Step 1: Identification of key business nodes throughout the entire lifecycle Based on the equipment category attributes of the target construction machinery, load the category node configuration template corresponding to the equipment category; the category node configuration template includes the evidence storage node and the field mapping rules corresponding to each evidence storage node. The evidence storage node is the key business event node that needs to be evidenced by data in the entire life cycle of the construction machinery.

[0040] The system identifies whether the current business node is a certificate storage node based on the category node configuration template. If so, it extracts the core fields from the current business data according to the field mapping rules corresponding to the certificate storage node.

[0041] The universal evidence storage nodes are shared by all categories, including new vehicle filing, initial registration, each maintenance, each transfer of ownership, used vehicle appraisal, and scrapping / dismantling.

[0042] Category-specific evidence storage nodes, configured according to templates, include, for example: forklift Special equipment periodic inspection nodes Special Equipment Safety Technical Specifications excavator Environmental emission monitoring nodes Ecological and environmental supervision requirements crane Safety device verification node Special Equipment Safety Technical Specifications + National Standards Loader Environmental emission monitoring nodes Ecological and environmental supervision requirements Core design principles of category node configuration template: Separation of general and specific: The evidence storage process only deals with the abstract concept of nodes and does not perceive specific categories.

[0043] Category attribute externalization: Category attributes are carried by a remote mapping service and do not appear in the evidence storage transaction.

[0044] Node field mapping abstraction: Differences are configured by the mapping table, dynamically extracted, and not hard-coded.

[0045] Compared with the prior art, the category node configuration template of the present invention has the following characteristics: (1) Differences in product category supervision not only lead to differences in what is stored, but also to differences in the field structure and verification rules of each node; (2) The existing solution hardcodes the category logic into the evidence storage process, not because it does not want to decouple, but because it cannot do so; (3) It requires cross-category abstract modeling capabilities, not just simple configuration table replacement.

[0046] Step 2: Node Data Verification Digest Generation The core fields, along with the file number and timestamp, are concatenated according to the template field mapping order to generate the string to be summarized.

[0047] Cryptographic hash algorithms, such as SHA-256, SM3, or any equivalent algorithm, are used to generate checksums, while the original data is retained in the private cloud.

[0048] In nodes with multiple endorsements, after all entities have passed the platform's identity authentication, their operation records are bound to the operator's identity identifier and jointly written into the evidence storage data.

[0049] Category information does not need to be embedded. The core fields of different categories are naturally different, and with the global uniqueness of the file number, there is no risk of cross-category collision.

[0050] The system reserves a data correction interface to handle compliance corrections of stored data in specific scenarios.

[0051] Step 3: Anti-tampering evidence storage Package the verification summary, file number, timestamp, and authentication information and upload them to a trusted evidence storage service (such as consortium blockchain, notary office evidence storage, third-party timestamp authentication, etc.).

[0052] The storage network generates a unique notarized transaction identifier and notarized certificate.

[0053] It is jointly maintained by industry organizations, platforms, and regulators, balancing credibility and privacy.

[0054] Unified cross-category certification: All categories are certified on the same network, and category information is obtained remotely through file number mapping. The certification data does not require a category identifier field.

[0055] Step 4: Evidence storage, binding, and archiving The document number associated with the certificate and the legal serial number of the aircraft are written into the electronic archive, realizing the dual unique identity binding and archiving.

[0056] Each node stores local original data and evidence, which can be verified with one click within the electronic archive system.

[0057] The complete evidence preservation chain is linked in sequence from new vehicle to scrapped vehicle.

[0058] Different product categories use the same archiving interface.

[0059] As an optional implementation, step 4 may also include full lifecycle state aggregation anchoring: A Merkle tree is constructed using the verification digests of all currently certified nodes of the target construction machinery as leaf nodes; the root hash of the Merkle tree is calculated and written into the immutable distributed storage network as the unique anchor point for the certification status of the target construction machinery throughout its entire life cycle; when a new certified node is added, only the hash value on the path from the new leaf node to the root node is updated.

[0060] After each evidence storage node completes its archiving and binding process, the system performs a full lifecycle state aggregation step, compressing all historical evidence storage nodes of the target engineering machinery into a unified cryptographic anchor.

[0061] Specifically, once the target construction machinery completes the archiving and binding of any certified node, the system obtains the verification digests of all currently certified nodes of the equipment. Each node's verification digest is used as a leaf node, arranged from left to right according to the node's timestamp order, to construct a Merkle Tree.

[0062] Let the current number of nodes with verified certificates be n, and the verification digest of each node be... , …, The Merkle tree is constructed as follows: Leaf nodes: = , where H is a cryptographic digest algorithm; Internal nodes: = That is, the hash values ​​of the left and right child nodes are concatenated and then hashed again; Root node: R = H(N_left || N_right), which is the root hash value of the entire tree.

[0063] The system writes the calculated root hash value into the immutable distributed storage network, which serves as the unique anchor point for the full lifecycle record status of the target engineering machinery up to the current moment.

[0064] When a new verification node is added, the system does not need to rebuild the entire tree. Instead, it performs an incremental update: the verification digest of the new node is used as the new leaf node, and only the hash values ​​on the path from the leaf node to the root node are recalculated. Let the new leaf node be L_new, and its sibling node be L_sibling. Then the new root hash R' = H(H(L_new || L_sibling) || the hash value of the original parent node's sibling, ...), and so on, updating upwards to the root node. The hash values ​​of intermediate nodes involved in the update process are all cached locally, without needing to query on-chain data. The time complexity of the incremental update is O(log n), where n is the total number of currently verified nodes.

[0065] In subsequent trusted verification steps, when a user needs to verify whether a specific node has been included in the full lifecycle evidence storage state, the system provides the node's Merkle Proof, including the hash values ​​of all sibling nodes on the path from the node to the root node. The verifier recalculates the root hash based on the path proof and compares it with the anchor root hash written to the immutable distributed storage network; if they match, it proves that the node has been included in the full lifecycle evidence storage state and has not been tampered with.

[0066] Through the Merkle tree aggregation mechanism described above, the system compresses dozens to hundreds of independent evidence storage nodes that may arise during the entire lifecycle of a single device into a unified root hash value. Compared to verifying each independent node one by one, this scheme has a significant advantage in verification efficiency, while providing each device with an indivisible overall evidence storage status identifier, further enhancing the credibility and integrity of the evidence storage data.

[0067] Step 5: Trusted Verification Process The process includes: user-initiated verification, system query of category attributes, loading of category node configuration template, extraction of original core fields, regeneration of verification summary, comparison with the summary in storage, and output of verification results and report.

[0068] Step 6: Continuation of Transfer Certificate On-chain ownership transfer: When the device is registered, a device ownership record is created; when the device is transferred, the original owner signs the transfer transaction; and the owner's identifier is updated after automatic contract verification. Evidence is not transferred: Historical evidence is a permanent record, and the transfer of ownership only changes the management rights; Add a new transfer certificate storage node: automatically triggered after the transfer is completed, following the time sequence. The new owner can fully trace all historical evidence nodes; Cross-category transfer applicable: The same set of automatic contracts and continuation rules applies to all categories.

[0069] This example illustrates the method using the entire lifecycle of an internal combustion forklift. The equipment is a 5-ton internal combustion forklift of a certain brand, with VIN LCCJ5AB5GK1000123, and registered in XX city.

[0070] 1.1 New vehicle registration and filing (1) The node identification module queries the remote mapping service based on the file number and loads the forklift category node configuration template; (2) Match the general evidence storage node "New Vehicle File Creation"; (3) Extract the core fields and concatenate them into a string to be digested; (4) Generate a checksum using the SHA-256 algorithm; (5) Verify the summary, file number, and timestamp, package and upload them to the consortium blockchain. In this embodiment, the underlying layer is a permissioned blockchain. (6) The document number and VIN associated with the certificate are written into the electronic file; (7) Create equipment ownership records.

[0071] 1.2 Periodic inspection and certification of special equipment is a unique milestone for this category. (1) After 2 years of use, conduct a periodic inspection of the special equipment in accordance with TSG 81-2022; (2) Identified as a node specific to the forklift category; (3) Extract core fields: inspection time, result, institution qualification number, certificate number; (4) Multi-subject joint evidence storage is carried out by binding operator identity tags; (5) Verify the digest and double signature before uploading it to the consortium blockchain; (6) Archive binding.

[0072] 1.3 Certificate of Preservation (1) Match general maintenance nodes; (2) Extract core fields: maintenance time, project, replacement parts list, and maintenance provider information; (3) Joint storage of maintenance provider identity authentication mark; (4) Evidence preservation and archiving.

[0073] 1.4 Continuation of Certificate of Transfer of Ownership (1) When the original owner transfers the vehicle, the smart contract is triggered, and the server automatically verifies the legality of the transfer according to the preset transfer rules; (2) The original owner signed the ownership transfer transaction using the private key ECDSA; (3) The transfer node will be automatically triggered for evidence storage after the transfer; (4) New car owners can fully trace all historical records; (5) Subsequent evidence shall be recorded under the ownership of the new vehicle owner.

[0074] 1.5 Residual Value Assessment Verification (1) It enters the second-hand market after 12 years of use; (2) Regenerate the checksum node by node and compare it with the chain; (3) If all are consistent, export the verification report with the evidence mark.

[0075] 1.6 Scrap dismantling and preservation of evidence (1) According to GB / T 44679-2024, it has reached the 15-year scrapping age limit; (2) Matching common nodes for scrapping and dismantling; (3) Evidence preservation and archiving, a closed loop throughout the entire life cycle.

[0076] This invention is not limited to the specific embodiments described above, and the following substitutions can be made: 1) The hash algorithm can be replaced with SHA-256, SM3, SHA-3 or any equivalent algorithm; 2) An option to encrypt and preserve all data can be added; 3) Evidence storage nodes can be added or removed as needed; 4) Category information can be redundantly stored off-chain for fast retrieval; 5) Ownership transfer can be achieved through different types of automatically executed contracts.

[0077] This invention has the following characteristics: (1) Unified cross-category architecture for category node configuration templates and general evidence storage process A single evidence preservation system covers all product categories. Adding a new product category only requires creating a template, and the evidence preservation process remains unchanged.

[0078] (2) Architectural design for externalizing category information Category attributes are carried by a remote mapping service and are not treated as independent fields in coding, summaries, or evidence storage transactions.

[0079] (3) Dual unique identity binding archiving mechanism The certificate of authenticity is automatically bound to the file number and the legal serial number of the device, and one-click verification is available without redirection.

[0080] (4) End-to-end evidence storage and automatic contract transfer continuation mechanism It covers all key nodes in the process, automatically executes the contract to transfer ownership during the transfer, and ensures uninterrupted historical data.

[0081] (5) Layered evidence storage scheme for key nodes Only key nodes and core fields are validated and stored as evidence, balancing cost and credibility. Example 2

[0082] This embodiment is a trusted data storage system for the entire lifecycle of construction machinery, including: The node identification module is used to load the category node configuration template corresponding to the equipment category based on the equipment category attributes of the target construction machinery. The category node configuration template includes the evidence storage node and the field mapping rules corresponding to each evidence storage node. The evidence storage node is the key business event node that needs to be evidenced by data in the entire life cycle of the construction machinery. The system identifies whether the current business node is the evidence storage node based on the category node configuration template. If so, it extracts the core fields from the current business data according to the field mapping rules corresponding to the evidence storage node. The abstract generation module is used to concatenate the extracted core fields in a predetermined order, add the file number and timestamp of the target construction machinery, and generate a string to be abstracted. The file number is a globally unique identifier that adapts to the electronic archives of the construction machinery throughout its entire life cycle. A cryptographic digest algorithm is used to operate on the string to be abstracted to generate a verification digest. The evidence storage module is used to package the verification digest, the file number, the timestamp, and the identity authentication information of the participating entities, and write them into an immutable distributed storage network to obtain an evidence storage transaction identifier and evidence storage certificate. The archiving and binding module is used to associate and bind the evidence certificate with the file number and the legal serial number of the target construction machinery, and write it into the electronic archive of the target construction machinery throughout its entire life cycle.

[0083] Obviously, the above embodiments are merely illustrative examples for clear explanation and are not intended to limit the implementation. Those skilled in the art will recognize that other variations or modifications can be made based on the above description. It is neither necessary nor possible to exhaustively list all possible implementations here. However, obvious variations or modifications derived therefrom are still within the scope of protection of this invention.

Claims

1. A method for reliable data storage and verification throughout the entire lifecycle of construction machinery, characterized in that, include: The node identification step involves loading the category node configuration template corresponding to the equipment category based on the equipment category attributes of the target construction machinery. The category node configuration template includes evidence storage nodes and field mapping rules corresponding to each evidence storage node. The evidence storage nodes are key business event nodes for data evidence storage of construction machinery throughout its entire life cycle. The system identifies whether the current business node is the evidence storage node based on the category node configuration template. If so, it extracts the core fields from the current business data according to the field mapping rules corresponding to the evidence storage node. The abstract generation step involves concatenating the extracted core fields in a predetermined order, adding the file number and timestamp of the target construction machinery, and generating a string to be abstracted. The file number is a globally unique identifier that is adapted to the electronic archives of the entire life cycle of the construction machinery. A cryptographic digest algorithm is used to process the string to be digested to generate a verification digest; The evidence preservation step involves packaging the verification digest, the file number, the timestamp, and the identity authentication information of the participating entities, and writing them into an immutable distributed storage network to obtain an evidence preservation transaction identifier and evidence preservation certificate. The archiving and binding step involves associating the evidence certificate with the file number and the legal serial number of the target construction machinery, and writing it into the electronic archive of the target construction machinery throughout its entire life cycle.

2. The method according to claim 1, characterized in that, In the category node configuration template, the evidence storage nodes include general evidence storage nodes and category-specific evidence storage nodes; The general evidence storage nodes include at least one of the following: new vehicle filing node, initial registration node, maintenance node, transfer node, used vehicle appraisal node, and scrapping and dismantling node; The category-specific evidence storage nodes are configured according to the regulatory rules of different categories, and include at least one of the following: special equipment periodic inspection nodes for forklifts, environmental emission testing nodes for excavators, and safety device verification nodes for cranes.

3. The method according to claim 2, characterized in that, The category node configuration template includes a node type identifier, field mapping information, and field concatenation order rules; the field mapping information defines the names of the core fields to be extracted for each device category under each evidence storage node and their data source paths; the field concatenation order rules define the order in which each core field is arranged when generating the string to be digested.

4. The method according to claim 1, characterized in that, The equipment category attributes are managed by a remote mapping service and obtained by querying the remote mapping service through the file number; the file number adopts an encoding structure that does not contain category information, and neither the generation of the verification digest nor the packaged data of the evidence storage step contains category information.

5. The method according to claim 1, characterized in that, When the target construction machinery is documented, an equipment ownership record is created in the immutable distributed storage network. The equipment ownership record includes the equipment identifier, the current owner identifier, and the ownership creation timestamp.

6. The method according to claim 1, characterized in that, The certificate of evidence is associated with both the file number and the legal serial number of the aircraft.

7. The method according to claim 1, characterized in that, The method also includes a trusted verification step: In response to a user's request for verification of the target construction machinery, the certificate of the node to be verified is obtained from the electronic archive of the entire life cycle based on the file number of the target construction machinery. Based on the file number, query the remote mapping service to obtain the equipment category attribute of the target construction machinery, and load the corresponding category node configuration template; Based on the field mapping rules in the category node configuration template, the core fields are extracted from the original business data saved in the node to be verified, and the verification summary is regenerated. The regenerated verification digest is compared with the verification digest corresponding to the evidence credential obtained from the immutable distributed storage network. If they match, the verification passes; otherwise, the verification fails.

8. The method according to claim 2, characterized in that, The method also includes a transfer continuation step: When the target construction machinery is documented, an equipment ownership record is created in the immutable distributed storage network. The equipment ownership record includes the equipment identifier, the current owner identifier, and the ownership creation timestamp. In response to an ownership transfer request, the original owner signs an ownership transfer transaction in the immutable distributed storage network. The server verifies the legality of the ownership transfer transaction according to preset transfer rules. After verification, the server updates the current owner identifier in the device ownership record. After the ownership transfer is completed, the notarization step of the transfer node is automatically triggered, and the transfer information is written into the tamper-proof distributed storage network.

9. The method according to claim 1, characterized in that, In the evidence preservation step, when the current business node involves joint endorsement by multiple participating entities, each participating entity, after being authenticated by the platform, binds its operation record with the operator's identity identifier and writes it together into the evidence preservation data.

10. A trusted data storage system for the entire lifecycle of construction machinery, characterized in that, include: The node identification module is used to load the category node configuration template corresponding to the equipment category based on the equipment category attributes of the target construction machinery; The category node configuration template includes evidence storage nodes and field mapping rules corresponding to each evidence storage node. The evidence storage nodes are key business event nodes for data evidence storage of construction machinery throughout its entire life cycle. The system identifies whether the current business node is the evidence storage node based on the category node configuration template. If so, it extracts the core fields from the current business data according to the field mapping rules corresponding to the evidence storage node. The abstract generation module is used to concatenate the extracted core fields in a predetermined order, add the file number and timestamp of the target construction machinery, and generate a string to be abstracted. The file number is a globally unique identifier that is adapted to the electronic archives of the entire life cycle of the construction machinery. A cryptographic digest algorithm is used to process the string to be digested to generate a verification digest; The evidence storage module is used to package the verification digest, the file number, the timestamp, and the identity authentication information of the participating entities, and write them into an immutable distributed storage network to obtain an evidence storage transaction identifier and evidence storage certificate. The archiving and binding module is used to associate and bind the evidence certificate with the file number and the legal serial number of the target construction machinery, and write it into the electronic archive of the target construction machinery throughout its entire life cycle.

Images