Aircraft manufacturing supply chain cross-domain data sharing method based on alliance chain
By adopting a cross-domain data sharing method based on alliance chain in the aircraft manufacturing supply chain, using zero-knowledge proof and digital signature technology, the risk of data being tampered during the delivery process and the inefficient data sharing are solved, and the data is realized Safety, integrity and consistency.
Patent Information
- Application Number
- CN202411661676.5
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-11-20
- Publication Date
- 2025-02-25
AI Technical Summary
There is a risk that data will be tampered with when delivered by multiple parties in the aircraft manufacturing supply chain, and it is impossible to distinguish whether the tampered data is the delivery party or the receiver, which leads to the threat of data security and the existing data sharing methods are inefficient. Problems with damage and loss of physical media.
The cross-domain data sharing method of aircraft manufacturing supply chain based on alliance chain is adopted, and the processed data sharing process is ensured through zero-knowledge proof, digital signature technology and alliance chain.
It ensures the privacy, integrity and consistency of data, improves data processing speed and alliance chain data storage efficiency, and enhances data reliability and rights protection.
Smart Images
Figure CN119513202A_ABST
Abstract
Description
Technical Field
[0001] The present invention belongs to the technical field of data between upstream and downstream of a supply chain, and relates to a cross-domain data sharing method for an aircraft manufacturing supply chain based on an alliance chain. Background Art
[0002] The aircraft manufacturing process is a multi-party collaborative process. From raw material selection, parts production, assembly and integration, it requires collaborative cooperation among multiple organizations and standardized collaborative management. Collaborative management is a relatively complex system. In actual operation, it will face many problems. For example, the collaborators are deployed in different networks, and there is a risk of data being tampered with when delivered by multiple parties. It is impossible to distinguish whether the tampered data is a problem with the delivery party or the recipient. At present, data supervision is often supervised independently by each enterprise, and the data transmission process between enterprises has not yet been fully controlled, and data security is threatened. At present, in view of the problem of cross-enterprise data transmission in the entire process of aircraft manufacturing, an effective mechanism is urgently needed to ensure the collaboration between enterprises, achieve the goal of secure cross-domain delivery, and solve the data privacy and security issues in the delivery process. It is necessary to supervise the data throughout the process from the conceptual design of the aircraft to the mass production process to the final verification to ensure the security of the data.
[0003] In addition, aircraft manufacturing data may be lost or tampered with during the cross-collaboration process. To avoid such problems, enterprises use physical media such as paper materials or CDs to complete data sharing and delivery. This method is inefficient and has problems with physical media damage and loss. In addition, it is difficult to mine the relationship between data when stored in this way, resulting in loss of data value. Blockchain technology can effectively ensure the security of data. Research on cross-chain data sharing methods in physically isolated networks is of great significance to data sharing management within organizations and data transmission between collaborators. It can effectively ensure the integrity and consistency of data delivery between collaborators.
[0004] The application of alliance chain in current blockchain technology within organizations is relatively mature and widespread. The distributed storage and tamper-proof nature of blockchain itself also ensure the security of internal data and the traceability of data records. This patent intends to design a cross-domain data sharing method for aircraft manufacturing supply chain based on alliance chain to ensure the integrity and consistency of data between upstream and downstream of the supply chain, effectively solve the problem of cross-chain data transmission, and assist cross-enterprise collaboration and sharing. Summary of the invention
[0005] The technical problem to be solved by the present invention is to provide a cross-domain data sharing method for aircraft manufacturing supply chain based on alliance chain in view of the above-mentioned deficiencies in the prior art. In view of the use scenario of cross-domain data sharing in aircraft manufacturing supply chain, a cross-chain data sharing method is proposed by using zero-knowledge proof, digital signature technology and alliance chain to streamline the data sharing process, thereby ensuring the consistency and integrity of data sharing between collaborating parties. The defects of data integrity, consistency and reliability in existing cross-domain data sharing are overcome.
[0006] To solve the above problems, the technical solution adopted by the present invention is:
[0007] A cross-domain data sharing method for aircraft manufacturing supply chain based on alliance chain, specifically including:
[0008] Enterprises participating in data sharing build data management systems based on alliance chains;
[0009] The user roles participating in the alliance chain-based data management system are divided into three categories: management accounts, data accounts, and cross-enterprise accounts. Among them, the management account is responsible for approving data users and cross-enterprise accounts that join the system, and also serves as the consensus node of the underlying alliance chain. The data account is the account for uploading, downloading, and using data within the enterprise. The cross-enterprise account is the account for other enterprises to share data with the enterprise.
[0010] Further, the cross-enterprise account submits a join request to the system;
[0011] The cross-enterprise account submits a request to join the system, which includes a request to obtain an identity and a request to participate in sharing data. The management account in the system verifies the identity of the account and the request it submits. After the verification is passed, the account is given the identity of "cross-enterprise account" and the data permissions involved in the request are opened. A pair of public and private keys are allocated to the account for identification and communication. At the same time, the system allocates a pair of public and private keys for data encryption to the data account that participates in sharing data with the cross-enterprise account.
[0012] The specific method for realizing data sharing between the cross-enterprise data sharing account and the data account in the system is:
[0013] Step 1: The data account pre-processes the data to be shared;
[0014] The data account uses the public key used for data encryption to encrypt the data and upload the encrypted data to the Interstellar File System (IPFS). The data node obtains the returned hash value from IPFS and uploads the hash value to the system. The management account in the system verifies the data. After passing the verification, the data storage is completed through consensus on the underlying alliance chain.
[0015] Step 2: Verify the data to be shared across enterprise accounts;
[0016] When a cross-enterprise account applies to verify relevant sensitive technical data uploaded by a data account, the cross-enterprise account initiates a verification request to the system. After receiving the verification request, the data account generates a corresponding zero-knowledge proof for the relevant information of the sensitive technical data to prove its ownership of the sensitive technical data, and delivers the generated zero-knowledge proof to the cross-enterprise account. The cross-enterprise account verifies the ownership of the shared data through the zero-knowledge proof result and transmits the verification result back to the system.
[0017] Step 3: Data accounts share data;
[0018] After the data node receives the successful verification result returned by the verification node in the system, it digitally signs the decryption key of the shared data and the hash address of the data on IPFS with the identity public key, packages it together with the identity public key, and then encrypts it with the public key of the verification node and uploads it to the system.
[0019] Step 4: Obtain shared data across enterprise accounts;
[0020] Cross-enterprise accounts download the data address and decryption key uploaded by the data account from the system, verify the data integrity through the data account's identity public key, and obtain shared data after verification.
[0021] Furthermore, the specific method for cross-domain transmission of the shared data obtained by the cross-enterprise account is:
[0022] After the cross-enterprise account obtains the shared data in the system where the data account is located, it returns to the enterprise's system to synchronize the shared data. By synchronizing information to the management account in the enterprise system, including the digital signature and public key of the obtained data account, after verification, the shared data storage is completed through consensus with other consensus nodes in the underlying alliance chain.
[0023] Furthermore, the specific method for accessing shared data by data accounts in the system where the cross-enterprise account is located is:
[0024] The data account in the system where the cross-enterprise account is located initiates an access request to the system. The management account in the system verifies the identity of the account initiating the request. After verification, the data node is granted access rights. The data node can download shared data through the hash address and decryption key to achieve cross-domain data sharing.
[0025] Beneficial effects of the present invention
[0026] The present invention encrypts data during storage to ensure data privacy. At the same time, IPFS storage is used to improve data processing speed and alliance chain data storage efficiency, and distributed information also ensures storage reliability.
[0027] The present invention adopts zero-knowledge proof technology in the data verification process, which guarantees the ownership of the data and further strengthens the rights and interests protection of aircraft manufacturing data.
[0028] The present invention adopts digital signature technology when sharing data, thereby ensuring the integrity of the data.
[0029] The present invention assigns identity distinctions to different nodes on the alliance chain to ensure consistency in cross-domain data sharing.
[0030] Instruction Manual
[0031] Figure 1 A flowchart of a cross-domain data sharing method for an aircraft manufacturing supply chain based on an alliance chain provided by an embodiment of the present invention;
[0032] Figure 2 A framework diagram of data accounts and data sharing between cross-enterprise accounts provided in an embodiment of the present invention;
[0033] Figure 3 A framework diagram for cross-domain data account access to data provided by an embodiment of the present invention. DETAILED DESCRIPTION
[0034] The specific implementation of the present invention is further described in detail below in conjunction with the accompanying drawings and examples. The following examples are used to illustrate the present invention, but are not intended to limit the scope of the present invention.
[0035] In this embodiment, a cross-domain data sharing method for aircraft manufacturing supply chain based on alliance chain is provided. Figure 1 As shown, the specific steps include:
[0036] Step 1: Build a data management system based on the alliance chain within the organization to store internal data;
[0037] The key nodes within each organization in the aircraft manufacturing supply chain serve as the management account of the system and jointly maintain the underlying alliance chain of the system. The data uploader initiates a sharing request to the system. The system assigns the data uploader a "data account" identity and records it in the alliance chain, and assigns a pair of public and private keys to the account. In addition, a pair of public and private keys for data encryption is assigned to the data account. Considering that storing a large amount of data on the alliance chain will take up storage space and increase consensus costs, the data account will store the shared data in the InterPlanetary File System (IPFS) after public key encryption, which improves data storage efficiency while ensuring the data's anti-counterfeiting and anti-tampering properties. The data account obtains the return hash value from IPFS and uploads the hash value to the system. The management account completes consensus in the alliance chain to store data.
[0038] Step 2: Submit a request to join the system across enterprise accounts;
[0039] The data account of enterprise N initiates a request to join the alliance chain-based data management system of enterprise M. The management account in the M enterprise system verifies the identity of the node. After the verification is passed, the data account of enterprise N is granted the identity of a "cross-enterprise account" and a pair of public and private keys are assigned to the account for verification and communication processes.
[0040] Step 3: Enterprise M's data account shares data with cross-enterprise accounts, such as Figure 2 As shown;
[0041] Step 3.1: Verify shared data across enterprise accounts;
[0042] When cross-enterprise account B applies to verify the relevant sensitive technical data uploaded by data account A, B initiates a verification request to the management account in the system. After passing the verification, it is broadcast in the alliance chain. After the data account receives the verification request broadcast by the alliance chain in the system, it generates a corresponding zero-knowledge proof for the relevant information of the sensitive technical data to prove that it has ownership of the sensitive technical data, and submits the generated zero-knowledge proof to the system. The management account in the system records it in the alliance chain. After cross-enterprise account B receives the proof in the system,
[0043] Ownership is verified through zero-knowledge proof results, and the verification results are transmitted back to the system. The management account in the system stores the results in the consortium chain.
[0044] Step 3.2: Obtain shared data across enterprise accounts;
[0045] When data account A receives the verification result successfully uploaded by cross-enterprise account B in step 3, it digitally signs the data decryption key and the hash address of the data on IPFS with the identity public key, packages it together with the identity public key, encrypts it with the public key of cross-enterprise account B, and uploads it to the system. Cross-enterprise account B downloads the data address and decryption key from the system, verifies the data integrity with A's identity public key, and obtains the shared data after the verification is passed.
[0046] Step 4: Cross-domain data sharing;
[0047] After the cross-enterprise account B obtains the shared data of data account A in organization M, it returns to organization N. In organization N, B, as the management account of organization N, uploads the digital signature of data account A and A's identity public key to the system of organization N, and completes the storage in the underlying alliance chain through consensus.
[0048] Step 5: Access shared data across domains;
[0049] The data account in organization N initiates a data access request to the internal system of organization N. The management account in the system verifies the request. After verification, the access right is granted to data account C. Data account C downloads the data through the hash address and obtains the shared data with A's decryption key to complete the data access. Figure 2 .
[0050] The present invention uses complete zero-knowledge proof generation and verification technology in the verification process of aircraft manufacturing shared data. During the entire process, sensitive technical file information will not be disclosed at all during the transmission process and can be verified to be effective, thereby avoiding data leakage due to force majeure factors. Digital signature technology is used when sharing data to ensure the integrity of the data. In addition, the data is stored in IPFS in the form of ciphertext to avoid access to the data by unauthorized data, thereby improving the storage efficiency of alliance chain data. At the same time, storage in a distributed manner also ensures that the data is not easily lost or destroyed, thereby ensuring the integrity of the data.
Claims
1. A cross-domain data sharing method for aircraft manufacturing supply chain based on alliance chain, characterized in that: include: Enterprises participating in data sharing build data management systems based on alliance chains; The user roles participating in the alliance chain-based data management system are divided into three categories: management accounts, data accounts, and cross-enterprise accounts. Among them, the management account is responsible for approving data users and cross-enterprise accounts that join the system, and also serves as the consensus node of the underlying alliance chain. The cross-enterprise account submits a joining request to the system; The cross-enterprise account submits a request to join the system, which includes a request to obtain an identity and a request to participate in sharing data. The management account in the system verifies the identity of the account and the request it submits. After the verification is passed, the account is granted the "cross-enterprise account" identity and the data permissions involved in the request are opened. A pair of public and private keys are allocated to the account for identification and communication. At the same time, the system allocates a pair of public and private keys for data encryption to the data account that participates in sharing data with the cross-enterprise account.
2. The cross-domain data sharing method for aircraft manufacturing supply chain based on alliance chain as claimed in claim 1 is characterized in that: The specific method for sharing data across enterprise accounts and data accounts in the system to achieve data sharing is: Step 1: The data account pre-processes the data to be shared; The data account uses the public key used for data encryption to encrypt the data and upload the encrypted data to the Interstellar File System (IPFS); the data node obtains the returned hash value from IPFS and uploads the hash value to the system. The management account in the system verifies the data. After passing the verification, the data storage is completed through consensus on the underlying alliance chain; Step 2: Verify the data to be shared across enterprise accounts; When a cross-enterprise account applies to verify the relevant sensitive technical data uploaded by a data account, the cross-enterprise account initiates a verification request to the system. After receiving the verification request, the data account generates a corresponding zero-knowledge proof for the relevant information of the sensitive technical data to prove that it has ownership of the sensitive technical data, and delivers the generated zero-knowledge proof to the cross-enterprise account. The cross-enterprise account verifies the ownership of the shared data through the zero-knowledge proof result and returns the verification result to the system; Step 3: Data accounts share data; After receiving the successful verification result returned by the verification node in the system, the data node digitally signs the decryption key of the shared data and the hash address of the data on IPFS with the identity public key, packages it together with the identity public key, and then encrypts it with the public key of the verification node and uploads it to the system; Step 4: Obtain shared data across enterprise accounts; Cross-enterprise accounts download the data address and decryption key uploaded by the data account from the system, verify the data integrity through the data account's identity public key, and obtain shared data after the verification is passed.
3. The cross-domain data sharing method for aircraft manufacturing supply chain based on alliance chain as described in claim 1 or 2, characterized in that: The specific method for cross-domain transmission of shared data obtained by cross-enterprise accounts is: After the cross-enterprise account obtains the shared data in the system where the data account is located, it returns to the enterprise's system to synchronize the shared data; by synchronizing information to the management account in the enterprise system, including the digital signature and identity public key of the obtained data account, after verification, it completes the shared data storage through consensus with other consensus nodes in the underlying alliance chain.
4. The cross-domain data sharing method for aircraft manufacturing supply chain based on alliance chain as described in claim 1 or 2, characterized in that: The specific method for accessing shared data by a data account in the system where the cross-enterprise account is located is: The data account in the system where the cross-enterprise account is located initiates an access request to the system. The management account in the system verifies the identity of the account initiating the request. After verification, the data node is granted access rights. The data node can download shared data through the hash address and decryption key to achieve cross-domain data sharing.
5. The cross-domain data sharing method for aircraft manufacturing supply chain based on alliance chain as claimed in claim 3 is characterized in that: The specific method for accessing shared data by a data account in the system where the cross-enterprise account is located is: The data account in the system where the cross-enterprise account is located initiates an access request to the system. The management account in the system verifies the identity of the account initiating the request. After verification, the data node is granted access rights. The data node can download shared data through the hash address and decryption key to achieve cross-domain data sharing.
6. The cross-domain data sharing method for aircraft manufacturing supply chain based on alliance chain as described in claim 1, 2 or 5, characterized in that: The data account mentioned is the account used to upload, download and use data within the enterprise; Cross-enterprise accounts are accounts used by other enterprises to share data with this enterprise.
7. The cross-domain data sharing method for aircraft manufacturing supply chain based on alliance chain as described in claim 1, 2 or 5, characterized in that: The data account mentioned is the account used to upload, download and use data within the enterprise; Cross-enterprise accounts are accounts used by other enterprises to share data with this enterprise.
8. The cross-domain data sharing method for aircraft manufacturing supply chain based on alliance chain as described in claim 1, 2 or 5, characterized in that: The data account mentioned is the account used to upload, download and use data within the enterprise; Cross-enterprise accounts are accounts used by other enterprises to share data with this enterprise.