Blockchain-based aviation equipment history data tracing system and method
The blockchain-based aviation equipment history data traceability system enables transparent and traceable aviation equipment history data throughout its entire lifecycle, solving the problems of low data management efficiency and information silos in existing technologies, and improving data reliability and security.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- AIR FORCE UNIV PLA
- Filing Date
- 2022-06-08
- Publication Date
- 2026-06-05
AI Technical Summary
The existing aviation equipment history data management model consumes a lot of human and material resources, has a slow update speed, is prone to incomplete data and difficulty in searching, and has difficulties in synchronizing data between different institutions, resulting in information silos and unclear responsibilities.
The system adopts a blockchain-based aviation equipment history data traceability system, which includes a user management module, a history data management module, a synchronization module, a query module, and a comparison module. It achieves data sharing and immutability through a blockchain network and uses smart contracts and a gateway center for data verification and management.
It enables transparent and traceable aviation equipment history data throughout its entire lifecycle, prevents data tampering, improves data reliability and security, solves the problems of information silos and high human error rates in registration, and enhances data sharing and management efficiency.
Smart Images

Figure CN115222072B_ABST
Abstract
Description
Technical Field
[0001] This invention relates to the field of blockchain technology, and in particular to a blockchain-based system and method for tracing the history of aviation equipment. Background Technology
[0002] Currently, aviation equipment log documents record the technical status of equipment throughout its entire life cycle, including overhaul records, troubleshooting records, refurbishment, and modification information. At present, these are still based on logbooks, which are filled out manually. The completed logbooks are kept in a designated place by designated personnel. The use of log data is obtained by submitting an application and being distributed by designated personnel. After use, the logbooks are returned to their original location.
[0003] However, with the continuous expansion of aviation equipment, this manual record-keeping method consumes a large amount of manpower, material resources, and financial resources. Furthermore, the update speed is slow, and the error rate from human input is high. When aviation equipment manufacturers, users, and air force units need to access historical data records for maintenance or other reasons, a series of practical problems arise, such as incomplete information, difficulty in retrieval, and damaged paper. Moreover, the various agencies managing the records cannot communicate and exchange information on changes to the records data, resulting in a lack of synchronization between management agencies regarding changes in the technical status of the records data. In the actual use of aviation equipment, especially during testing, evaluation, and in-service assessment, data exchange between the test units, manufacturing plants, and research institutes is hindered. Some design, material, and aircraft performance issues, even when discovered by the test maintenance personnel, cannot be immediately resolved from the source of the records chain, and even lead to unclear responsibilities.
[0004] Therefore, how to prevent resume data from being altered without authorization and improve the reliability and security of resume data information is a technical problem that needs to be solved by those skilled in the art. Summary of the Invention
[0005] To overcome the problem of information silos in existing aviation equipment history storage and management, this invention provides a blockchain-based aviation equipment history data traceability system, comprising: a user management module, a history data management module, a synchronization module, a comparison module, a query module, terminal equipment, and a gateway center; wherein...
[0006] Terminal equipment: Terminal equipment refers to the equipment used by the user;
[0007] User Management Module: When a user logs in via a terminal device, the user management module determines whether the user's login information has passed identity verification upon receiving the user's login information. After logging in via the terminal device, the user management module sends a resume data query request to the resume data management module. When the synchronization module synchronizes resume data, it needs to receive instructions from the user management module and manage the user nodes.
[0008] Resume Data Management Module: The User Management Module initiates resume data requests to all nodes deployed on the blockchain network through the Resume Data Management Module; after receiving the resume data request instruction from the User Management Module, the Resume Data Management Module sends a resume data query instruction to the Query Module.
[0009] Query module: When it receives a resume query request from the resume data management module, it determines the target index value based on the resume query request from the resume data management module; the query module queries the corresponding target resume data from the user nodes registered on the user management module based on the target index value, and transmits the two to the comparison module;
[0010] Synchronization Module: Based on the instructions of the user management module, the equipment history data and target index value transmitted from the query module via the comparison module are uploaded to all user nodes, so that other user nodes deployed on the blockchain can complete the history data synchronization operation.
[0011] Comparison Module: Based on the target index value from the query module, it queries the blockchain for the corresponding history data in the query request. It compares the hash value of the corresponding history data of all nodes deployed on the blockchain network with the hash value of the queried history data to determine whether they are consistent. The comparison result is then sent to the synchronization module and fed back to the gateway center.
[0012] Gateway Center: Responsible for verifying the ID information of newly joined users and registering the sending and receiving keys, receiving feedback information sent by the comparison module, analyzing the creditworthiness of user nodes based on the feedback information, and supervising the blockchain operation behavior of terminal devices.
[0013] This invention also provides a blockchain-based data security verification method, which specifically includes the following steps:
[0014] Step 1: Once registered, users log in via their terminal devices using the key and permissions granted by the gateway center, and after being authorized by the user management module, they send a request for resume data through the blockchain of the resume data management module.
[0015] Step 2: When the query module receives a request for resume data from the resume data management module, the query module determines whether the access request is approved. If approved, the query module obtains the query instruction. The terminal device downloads the required resume data from other user nodes registered and managed by the user management module according to the access time, security level, and access scope restrictions of the query instruction, and sends the resume data to the comparison module.
[0016] Step 3: Compare the user's retrieved resume data with the corresponding resume data of other user nodes using the comparison module. The comparison module calculates the similarity of the resume information. The formula for calculating the similarity is: Where Z is the number of nodes with identical data, and N is the total number of nodes in the system;
[0017] Step 4: If the similarity is less than 95%, the resume data in the resume data management module is considered to be incorrect or has been tampered with. It is referred to as "erroneous resume data" and is not adopted. The blockchain network is traced through the erroneous resume data, and a proposal to modify the erroneous resume data is sent to the gateway center. After receiving the proposal, the gateway center distributes it to other user nodes in the user management module. User nodes vote on whether to modify the block. When the number of votes is greater than or equal to 51%, the decision takes effect. The synchronization module is responsible for modifying the erroneous resume data of the block to correct the resume data and attaching the timestamp of the modification. The resume data of all nodes in the user management module is also updated synchronously.
[0018] If the similarity is higher than 95%, the comparison module will broadcast the retrieved resume data to the blockchain network for verification. When the blockchain nodes receive the verification message, and after judgment, when the consensus verification of all blockchain nodes is greater than or equal to 51%, the requested resume data will be pushed to the query terminal. After confirmation by the user management module, a download service will be provided, as well as communication services for other user nodes.
[0019] Step 5: Under the action of the smart contract, the requesting user node broadcasts the operation record, and all user nodes deployed on the blockchain network back up the operation record.
[0020] In one embodiment of the present invention, the history data includes technical parameters, fault diagnosis information, overhaul process records, and repair records.
[0021] In one specific embodiment of the present invention, A = 95%.
[0022] In another specific embodiment of the invention, B = 51%.
[0023] In another embodiment of the present invention, the method further includes a gateway center monitoring method, the gateway center monitoring method comprising the following steps:
[0024] Step 1: For nodes applying to join the network, users first apply for an ID through the user management module. After receiving the information, the gateway center initiates a vote to the blockchain nodes (A, B, C, D, E, F) that have already joined the network.
[0025] Step 2: If the consensus verification rate of all blockchain nodes is greater than or equal to 51%, a private key is issued to the user. The gateway center queries the user's identity information through the user management module and assigns a certain initial credibility value. a and computing power b We obtain a certain weighted value, and the weighting formula is:
[0026] F(a, b) = (a*γ + b*β)*t (1)
[0027] In the formula, γ is the system-set reputation weight ratio, β is the system-set computing power weight ratio, t is the user node's entry time into the system, and the reputation reward formula is:
[0028]
[0029] In the formula, α represents the contribution, and the subscript h indicates the address. h This indicates the contribution at address h;
[0030] α=λ*X (3)
[0031] In the formula, X is 1 when the data is verified as correct and 0 when it is incorrect, and λ is the weight set by the system.
[0032] If the consensus verification rate of all blockchain nodes is less than 51%, the private key will not be issued to the user, and the network access will fail.
[0033] Once a node successfully joins the network, it is sorted in the blockchain system according to a weighted value. If a blockchain node requests verification before accessing other nodes' data, it must send an application to the gateway center. The gateway center verifies the node's permissions. If the node is ranked in the bottom 49%, it cannot access other data; if it is ranked in the top 51%, it can access the node.
[0034] This invention enables the traceability of aviation equipment history data throughout its entire lifecycle, ensuring that the history data is transparent to nodes within the blockchain and is tamper-proof. It addresses the shortcomings of the current aviation equipment history data management model, and solves problems such as insufficient sharing of aircraft maintenance data, high error rate of manual registration, and high storage costs. This invention provides a blockchain-based aviation equipment history data traceability system that is more suitable for modern aviation equipment history books.
[0035] The aviation equipment history data management method provided by this invention involves each blockchain network node participating in history recording deploying its own file on the blockchain system according to a smart contract. This blockchain system not only enables data sharing, but also records and shares data operation logs simultaneously, offering the following advantages:
[0036] If a node failure leads to damage to the equipment record file, the method of this invention can recover the record file from the blockchain system, avoiding data loss due to accidents (downtime, viruses, malicious attacks, etc.). In this embodiment, equipment record data is stored in the blockchain. When a node in the blockchain system modifies the record file, the modification is broadcast to all nodes in the network for authentication, and the modification record is recorded and stored. Users with permissions on each node can view data information from nodes other than their own, achieving data sharing and breaking down information silos. The immutability of data stored on the blockchain prevents unauthorized alteration of record data, improving the reliability and security of aviation equipment information. Attached Figure Description
[0037] Figure 1 This diagram illustrates the architecture of the blockchain-based aviation equipment history data traceability system of the present invention.
[0038] Figure 2 A schematic diagram of the structure of the blockchain-based aviation equipment history data traceability system of the present invention is shown.
[0039] Figure 3 A flowchart illustrating the blockchain-based aviation equipment history data traceability method of the present invention is shown.
[0040] Figure 4 The flowchart illustrates the gateway center supervision of the blockchain-based aviation equipment history data traceability system of the present invention. Detailed Implementation
[0041] I. Blockchain-based Aviation Equipment History Data Traceability System
[0042] The aviation equipment history traceability blockchain system consists of nodes registered by multiple equipment history management agencies. All nodes deployed on the blockchain system store all archives of history data for a certain type of aviation equipment. The nodes of the aviation equipment history traceability blockchain system are interconnected through a communication network. Each node of the aviation equipment history traceability blockchain system has interconnected and synchronously updated blocks. The operation records of each blockchain node on the aviation equipment history traceability blockchain are recorded by the blockchain system. Every operation on the blockchain node of the system is broadcast to other blockchain nodes in the blockchain system in a timely manner. All blockchain nodes on the system will record the operation records.
[0043] The above principles are implemented by system modules and are well known to those skilled in the art, so they will not be elaborated further.
[0044] To achieve the above objectives, the present invention provides a blockchain-based aviation equipment history data traceability system, comprising: a user management module, a history data management module, a synchronization module, a comparison module, a query module, terminal equipment, and a gateway center.
[0045] Terminal equipment: Terminal equipment refers to the equipment used by users.
[0046] User Management Module: When a user logs in via a terminal device, the module checks if the login information has passed identity verification. If so, it determines the data query permissions corresponding to the user's login information and, based on these permissions, determines the terminal device's resume data query permissions and scope. If not, login is denied. After logging in, the user management module sends a resume data query request to the resume data management module. When the synchronization module synchronizes resume data, it needs instructions from the user management module and manages the user nodes.
[0047] The Record Data Management Module: The User Management Module initiates record data requests to all nodes deployed on the blockchain network through the Record Data Management Module. Upon receiving a record data request instruction from the User Management Module, the Record Data Management Module sends a record data query instruction to the Query Module. The record data includes equipment record technical status information and timestamps.
[0048] Query Module: When a resume query request is received from the resume data management module, the query module determines the target index value based on the request. The query module then queries the corresponding target resume data from the user nodes registered in the user management module based on the target index value and transmits the two data to the comparison module.
[0049] Synchronization Module: Based on the instructions of the user management module, the equipment history data and target index value transmitted from the query module via the comparison module are uploaded to all user nodes, so that other user nodes deployed on the blockchain can complete the history data synchronization operation.
[0050] Comparison Module: Based on the target index value from the query module, it queries the blockchain for the corresponding history data. It compares the hash value of the corresponding history data deployed on all nodes on the blockchain network with the hash value of the queried history data to determine whether they are consistent. The comparison result is then sent to the synchronization module and fed back to the gateway center.
[0051] Gateway Center: Responsible for verifying the ID information of newly joined users and registering the sending and receiving keys; receiving feedback information from the comparison module; analyzing the user node reputation based on the feedback information; and supervising the blockchain's operation behavior of terminal devices. The specific implementation of analyzing user node reputation based on feedback information is determined according to the actual situation and is well known to those skilled in the art, and will not be elaborated further.
[0052] History data includes technical parameters, fault diagnosis information, overhaul process records, refurbishment records, and other history information. This recorded history information is uploaded to the system blockchain via system blockchain nodes. The communication network upon which this invention is based includes one or a combination of the Internet, cellular mobile networks, and wireless sensor networks.
[0053] II. Blockchain-based method for tracing aviation equipment history data
[0054] This invention provides a blockchain-based method for managing aviation equipment records. The user management module records data including technical status parameters, operator, operation time, operating organization, and operating terminal ID. To achieve the above objectives, this invention also provides a blockchain-based data security verification method, which includes the following steps: Figure 3 As shown:
[0055] Step 1: Once registered, users log in via their terminal devices after being granted permission by the user management module, using the key and permissions provided by the gateway center. They then send a request for resume data through the blockchain in the resume data management module.
[0056] Step 2: When the query module receives a request for resume data from the resume data management module, the query module determines whether the access request is approved. If approved, the query module obtains the query instruction. The terminal device downloads the required resume data from other user nodes registered and managed by the user management module according to the access time, security level, and access scope restrictions of the query instruction, and sends the resume data to the comparison module.
[0057] Step 3: Compare the user's retrieved resume data with the corresponding resume data of other user nodes using the comparison module. The comparison module calculates the similarity of the resume information. The formula for calculating the similarity is: Where Z represents the number of nodes with identical data, and N represents the total number of nodes in the system.
[0058] Step 4: If the similarity is less than 95%, the history data in the history data management module is considered incorrect or has been tampered with (referred to as "erroneous history data") and will not be adopted. The blockchain network will be traced through the erroneous history data, and a proposal to modify the erroneous history data will be sent to the gateway center. After receiving the proposal, the gateway center will distribute it to other user nodes in the user management module. User nodes will vote on whether to modify the block. When the number of votes is greater than or equal to 51%, the decision will take effect. The synchronization module will be responsible for modifying the erroneous history data of the block to correct history data and attaching a timestamp of the modification. The history data of all nodes in the user management module will be updated synchronously.
[0059] If the similarity is higher than 95%, the comparison module broadcasts the retrieved resume data to the blockchain network for verification. Upon receiving the verification message, blockchain nodes, after a consensus verification rate of 51% or higher across all blockchain nodes, will push the requested resume data to the query terminal. The user management module then provides a download service and communication services with other user nodes after confirmation.
[0060] Step 5: Under the action of the smart contract (because user nodes are deployed on the blockchain network, user node communication needs to be carried out in accordance with the blockchain network protocol, which is called a smart contract), the requesting user node broadcasts the operation record, and all user nodes deployed on the blockchain network back up the operation record.
[0061] To achieve the above objectives, the blockchain-based data security verification method further includes a gateway center monitoring method, which comprises the following steps: Figure 4 As shown:
[0062] Step 1: For nodes applying to join the network, users first apply for an ID through the user management module. After receiving the information, the gateway center initiates a vote on the blockchain nodes that have already joined the network (e.g., nodes A, B, C, D, E, F).
[0063] Step 2: If the consensus verification rate of all blockchain nodes is greater than or equal to 51%, a private key is issued to the user. The gateway center queries the user's identity information through the user management module and assigns a certain initial credibility value. a and computing power b We obtain a certain weighted value, and the weighting formula is:
[0064] F(a, b) = (a*γ + b*β)*t (1)
[0065] In the formula, γ is the system-set reputation weight ratio, β is the system-set computing power weight ratio, t is the user node's entry time into the system, and the reputation reward formula is:
[0066]
[0067] In the formula, α represents the contribution, and the subscript h indicates the address. h This represents the contribution at address h.
[0068] α=λ*X (3)
[0069] In the formula, X is 1 when the data is verified as correct and 0 when it is incorrect, and λ is the weight set by the system.
[0070] If the consensus verification rate of all blockchain nodes is less than 51%, the private key will not be issued to the user, and the network access will fail.
[0071] Once a node successfully joins the network, it is sorted in the blockchain system according to a weighted value. If a blockchain node requests verification before accessing other nodes' data, it must send an application to the gateway center. The gateway center verifies the node's permissions. If the node is ranked in the bottom 49%, it cannot access other data; if it is ranked in the top 51%, it can access the node. Specific Implementation
[0073] The aviation equipment is airborne radar. Example 1 involves tracing the historical data of Factory B, the manufacturer of a certain type of airborne radar sub-equipment, for an air force unit. (Reference) Figure 1 A blockchain-based aviation equipment history data traceability system includes: a user management module, a history data management module, a synchronization module, a comparison module, a query module, terminal equipment, and a gateway center.
[0074] The airborne radar history data traceability blockchain network includes six aviation equipment history traceability blockchain nodes: air force units, radar manufacturing plants, design institutes, overhaul plants, airborne radar sub-equipment manufacturing plant A, and airborne radar sub-equipment manufacturing plant B. Each blockchain node is registered and together they form the system blockchain network. The blockchain nodes are interconnected through a communication network. Each blockchain node can connect with other blockchain nodes to send and receive data. Each blockchain node has interconnected and synchronously updated blocks.
[0075] refer to Figure 2 Blockchain nodes are interconnected via, for example, Ethernet, forming a logical data exchange bus. When the blockchain system is operational, six blockchain nodes register on the blockchain network, with their IDs being IDI, ID2, ID3, ID4, ID5, and ID6. The gateway center is responsible for generating and reclaiming the private keys Sk1, Sk2, Sk3, Sk4, Sk5, and Sk6 for nodes ID1-ID6. After the private keys are issued, users can access the relevant node's history data according to the permissions granted by the private key. The network creates a blockchain database belonging to these blockchain nodes. Each ID is bound to the corresponding blockchain node's access permissions to the history data within the blockchain and the permissions to set the access to local history data.
[0076] After logging into node B of the airborne radar sub-equipment manufacturing plant, users can authorize access to the blockchain database by tracing the assigned ID in the aviation equipment history blockchain, and can also set permissions for the historical history data of the airborne radar in the blockchain network to which they belong.
[0077] Within the blockchain database, airborne radar history data is grouped according to its confidentiality level. Grouping criteria are defined by keywords, establishing a mapping relationship between these keywords and the grouped data. When other members of the blockchain wish to access the database, they need to input the keywords and request to query the history data from the relevant member nodes. Access to the database is based on a smart contract, which serves as the access protocol. Through this protocol, nodes in the aviation equipment history tracing blockchain are allowed to access the history data of other nodes on the blockchain. Based on the requester's permission level, the appropriate grouped data is returned according to the input keywords and mapping relationships.
[0078] refer to Figure 3 An air force unit requested access to the historical data of Factory B, a sub-equipment manufacturer for a certain type of airborne radar. The blockchain, through its historical data request module, sent the request to the blockchain network. Once a node verifies the access request, it obtains the query instruction and downloads the required historical data from the blockchain node based on the query instruction's restrictions on access time, security level, and access scope. This historical data is then sent to the comparison module, which compares the historical information and calculates the similarity between the three. The calculation formula is...
[0079] Z represents the number of nodes with identical data, and N represents the total number of nodes in the system. If the number is less than 95%, the record data is considered to be incorrect or has been tampered with, and will not be adopted. A proposal to modify the record data will be sent to the blockchain nodes. After receiving the verification proposal, each blockchain node will vote on whether to modify the block. When the number of votes is greater than or equal to 51%, the resolution will take effect, and the record data of the block will be edited, such as appending the information and attaching a timestamp of the modified record.
[0080] When the similarity of the three is higher than 95%, the airborne radar history data is sent to the comparison module for further consensus verification. The comparison module broadcasts the obtained history information to the blockchain network for verification. When the number of votes is greater than or equal to 51% of the nodes respond, the airborne radar history data is packaged and sent to the query terminal, thereby completing the traceability of the history data.
[0081] At the same time, the message of the resume data retrieval initiated by the air force unit is broadcast to all blockchain nodes of the blockchain network and a timestamp is attached. Therefore, all blockchain nodes in the system save the record of this resume query.
[0082] Air force units can obtain the usage status of each piece of equipment on the aircraft they maintain, troubleshooting status, etc., by receiving the history data of the airborne radar sub-equipment manufacturer B. The accuracy is very high. Moreover, since the airborne radar history data is stored in blocks, it can effectively prevent malicious alteration of the data by criminals in the later stages, thereby improving the reliability of the entire traceability system.
[0083] By using blockchain to store existing aircraft maintenance information, and then verifying the accuracy and timeliness of the traceability information through the aircraft maintenance traceability blockchain network, the reliability and stability of the entire system are improved. This makes it suitable for development and utilization based on blockchain technology.
[0084] To ensure the security and integrity of nodes joining the network, the gateway center plays a crucial role. Although blockchain is decentralized, data reliability and confidentiality are still required internally; therefore, the gateway center acts as a supervisory body.
[0085] refer to Figure 4 If node G applies to join the network, it first sends an authentication request to the gateway center. The gateway center performs the first step of verification based on its identity information. After the identity verification is successful, it initiates a vote with the blockchain nodes to decide whether to approve the network access.
[0086] After the blockchain nodes vote, they send the results back to the gateway center. If the vote is greater than or equal to 51%, the key Sk7 is issued as a successful network access request; if it is less than 51%, the network access fails.
[0087] If the network access is successful and a key is issued, a certain initial credibility value is assigned to node G based on the identity information. a and computing power b We obtain a certain weighted value, and the weighting formula is as described above.
[0088] Nodes are sorted in the blockchain system based on weighted values. Nodes in the top 51% can access data, while those in the bottom 49% cannot access other data.
[0089] This invention proposes a blockchain-based system and method for tracing the history of aviation equipment. By adopting blockchain, a decentralized effect is achieved, which means that numerous nodes are distributed in the blockchain network. Nodes can freely connect to exchange data and information, thereby effectively improving the transmission of aviation equipment history data, increasing processing efficiency, and perfecting the standards for user information and equipment information status. This can effectively avoid conflicts caused by non-compliance during the handover of aviation equipment, making the process of tracing aviation equipment history data more efficient, standardized, and rigid.
[0090] This blockchain-based logistics return information system and method utilizes the unique PBFT consensus mechanism of the blockchain system. Its unique openness and distributed network make users' reading, writing, appending, and modifying information and related processing information public and transparent, greatly reducing unnecessary risks caused by non-compliance during the handover process.
[0091] This invention relates to a blockchain-based information system and method for tracing the history of aviation equipment. The system records and stores information related to the equipment's history through a data statistics system. Furthermore, the blockchain system establishes a reputation and computing power evaluation mechanism for each node. If a node's reputation or computing power is compromised within the blockchain, its ranking will be lowered, resulting in the loss of corresponding permissions. For example, it may only be able to compare data and not vote. This effectively prevents the provision of false information that could lead to maintenance difficulties and the irresponsible evasion of responsibility in violating modification rules.
[0092] Of course, any product implementing this invention does not necessarily need to achieve all of the advantages described above at the same time.
Claims
1. A blockchain-based aviation equipment history data traceability system, characterized in that, include: User management module, resume data management module, synchronization module, comparison module, query module, terminal devices, gateway center; in Terminal equipment: Terminal equipment refers to the equipment used by the user; User Management Module: When a user logs in via a terminal device, the user management module determines whether the user's login information has passed identity verification upon receiving the user's login information. After logging in via the terminal device, the user management module sends a resume data query request to the resume data management module. When the synchronization module synchronizes resume data, it needs to receive instructions from the user management module and manage the user nodes. Resume Data Management Module: The User Management Module initiates resume data requests to all nodes deployed on the blockchain network through the Resume Data Management Module; after receiving the resume data request instruction from the User Management Module, the Resume Data Management Module sends a resume data query instruction to the Query Module. Query module: When it receives a resume query request from the resume data management module, it determines the target index value based on the resume query request from the resume data management module; the query module queries the corresponding target resume data from the user nodes registered on the user management module based on the target index value, and transmits the two to the comparison module; Synchronization Module: Based on the instructions of the user management module, the equipment history data and target index value transmitted from the query module via the comparison module are uploaded to all user nodes, so that other user nodes deployed on the blockchain can complete the history data synchronization operation. Comparison Module: Based on the target index value from the query module, it queries the blockchain for the corresponding history data in the query request. It compares the hash value of the corresponding history data of all nodes deployed on the blockchain network with the hash value of the queried history data to determine whether they are consistent. The comparison result is then sent to the synchronization module and fed back to the gateway center. Gateway Center: Responsible for verifying the ID information of newly joined users and registering the sending and receiving keys, receiving feedback information sent by the comparison module, analyzing the creditworthiness of user nodes based on the feedback information, and supervising the blockchain operation behavior of terminal devices.
2. A data security verification method based on blockchain, characterized in that, Specifically, the following steps are included: Step 1: Once registered, users log in via their terminal devices using the key and permissions granted by the gateway center, and after being authorized by the user management module, they send a request for resume data through the blockchain of the resume data management module. Step 2: When the query module receives a request for resume data from the resume data management module, the query module determines whether the access request is approved. If approved, the query module obtains the query instruction. The terminal device downloads the required resume data from other user nodes registered and managed by the user management module according to the access time, security level and access scope of the query instruction, and sends the resume data to the comparison module. Step 3: Compare the user's retrieved resume data with the corresponding resume data of other user nodes using the comparison module. The comparison module calculates the similarity of the resume information. The formula for calculating the similarity is: Where Z is the number of nodes with identical data, and N is the total number of nodes in the system; Step 4: If the similarity is less than 95%, the resume data in the resume data management module is considered to be incorrect or has been tampered with. It is referred to as "erroneous resume data" and is not adopted. The blockchain network is traced through the erroneous resume data, and a proposal to modify the erroneous resume data is sent to the gateway center. After receiving the proposal, the gateway center distributes it to other user nodes in the user management module. User nodes vote on whether to modify the blockchain. When the number of votes is greater than or equal to 51%, the decision takes effect. The synchronization module is responsible for modifying the erroneous resume data in the blockchain, modifying it to correct resume data and attaching the timestamp of the modification. The resume data of all nodes in the user management module is also updated synchronously. If the similarity is higher than 95%, the comparison module will broadcast the retrieved resume data to the blockchain network for verification. When the blockchain nodes receive the verification message, and after judgment, when the consensus verification of all blockchain nodes is greater than or equal to 51%, the requested resume data will be pushed to the query terminal. After confirmation by the user management module, download services are provided, as well as communication services for other user nodes; Step 5: Under the action of the smart contract, the requesting user node broadcasts the operation record, and all user nodes deployed on the blockchain network back up the operation record.
3. The data security verification method based on blockchain as described in claim 2, characterized in that, History data includes technical parameters, fault diagnosis information, overhaul process records, and repair records.
4. The blockchain-based data security verification method as described in claim 2, further comprising a gateway center monitoring method, the gateway center monitoring method comprising the following steps: Step 1: For nodes applying to join the network, users first apply for IDs through the user management module. After receiving the information, the gateway center initiates a vote on the blockchain nodes A, B, C, D, E, and F that have already joined the network. Step 2: If the consensus verification rate of all blockchain nodes is greater than or equal to 51%, then a private key is issued to the user. The gateway center queries the user's identity information through the user management module, assigns a certain initial reputation value 'a' and computing power value 'b', and obtains a certain weighted value. The weighting formula is as follows: F(a, b) = (a*γ + b*β)*t (1) In the formula, γ is the system-set reputation weight ratio, β is the system-set computing power weight ratio, t is the user node's entry time into the system, and the reputation reward formula is: In the formula, α represents the contribution, and the subscript h indicates the address. h This indicates the contribution at address h; α=λ*X (3) In the formula, X is 1 when the data is verified as correct and 0 when it is incorrect, and λ is the weight set by the system. If the consensus verification rate of all blockchain nodes is less than 51%, the private key will not be issued to the user, and the network access will fail. Once a node successfully joins the network, it is sorted in the blockchain system according to a weighted value. If a blockchain node requests verification before accessing other nodes' data, it must send an application to the gateway center. The gateway center verifies the node's permissions. If the node is ranked in the bottom 49%, it cannot access other data; if it is ranked in the top 51%, it can access the node.