Cloud-chain combined with privacy protection method for electronic archive data

Abstract

The present invention provides a cloud-chain combined privacy protection method for electronic archive data. S1: construct an electronic archive collection terminal and a cloud-chain terminal respectively; S2: identify the collected electronic archive data through the electronic archive collection terminal and obtain an identification result; S3: the cloud-chain terminal publishes the identification result through blockchain consensus; S4: the cloud-chain terminal records the blockchain consensus conducted by the consensus parties with a timestamp node and stores the blockchain consensus content of the timestamp node on the cloud-chain terminal; S5: the cloud-chain terminal divides the consensus parties into roles with limited permissions; S6: the consensus parties perform corresponding blockchain consensus privacy operations based on the permissions divided by the cloud-chain terminal. The present invention can perform cloud-chain combined operations on electronic archive data and, by controlling the access rights and sharing scope of the data, ensures the security and privacy of the electronic archive data during the sharing process.

Description

Technical Field

[0001] The present invention relates to the technical field of electronic archive privacy protection, and in particular to a cloud-chain combined privacy protection method for electronic archive data. Background Art

[0002] In today's information-based society, electronic archival data has become a crucial basis for daily operations and decision-making across various industries, including businesses and medical institutions. This electronic archival data contains a vast amount of sensitive information, such as personal privacy, commercial secrets, and medical records. Its security and privacy protection are directly linked to individual rights, corporate competitiveness, and social stability. However, with the widespread adoption of cloud computing technology, the storage and processing of electronic archival data has undergone profound changes. Cloud computing, with its powerful data processing capabilities, flexible resource allocation, and convenient service models, has greatly facilitated the centralized management and efficient utilization of electronic archival data. However, data security and privacy protection issues in cloud computing environments are becoming increasingly prominent. Since data is centrally stored in the cloud, a breach of the cloud service provider's defenses could expose a large amount of sensitive data to the risk of leakage. Therefore, a cloud-chain-based privacy protection approach for electronic archival data is proposed to address these issues. Summary of the Invention

[0003] In view of this, the purpose of the present invention is to provide a cloud chain combined with privacy protection method for electronic archive data to at least solve the above problems.

[0004] The technical solution adopted in the present invention is as follows:

[0005] A cloud-chain-based privacy protection method for electronic archive data includes the following steps:

[0006] S1, respectively build the electronic archive collection end and the cloud chain end;

[0007] S2. Identify the collected electronic archive data through the electronic archive collection terminal and obtain an identification result;

[0008] S3. The cloud chain end publishes the recognition results through blockchain consensus;

[0009] S4. The cloud chain end records the timestamp node for the blockchain consensus of the consensus party and stores the timestamp node blockchain consensus content on the cloud chain end;

[0010] S5. The cloud chain end divides the roles and limits the rights of the consensus parties;

[0011] S6. The consensus parties perform corresponding blockchain consensus privacy operations based on the restricted rights assigned by the cloud chain end.

[0012] Furthermore, in step S2, the following sub-steps are included:

[0013] S21, the electronic archive collection terminal identifies the file extension of the electronic archive data as text or table type;

[0014] S22. The electronic archive collection terminal uses OCR recognition technology to editably encapsulate electronic archive data of text and table types and obtains an editable encapsulation key.

[0015] Furthermore, in step S3, the sub-steps are included:

[0016] S31. The cloud chain end will edit the encapsulated key to verify the key format. When the key format verification is successful, the cloud chain end will edit the encapsulated key to publish the blockchain consensus.

[0017] S32. Collect the identity of the consensus party through the cloud chain and perform identity authentication;

[0018] S33. When the consensus party passes the identity authentication, the cloud chain end issues a key to the consensus party to decrypt the editable encapsulated text and table.

[0019] Furthermore, in step S4, the sub-steps are included:

[0020] S41. The consensus parties conduct blockchain consensus on the decrypted and editable encapsulated text and tables;

[0021] S42. When the consensus party reaches a blockchain consensus, the cloud chain extracts the original editable text and table data, and uses a hash algorithm to perform hash calculation on the original editable text and table data to generate an original unique hash value, and records the timestamp of the generation of the original unique hash value;

[0022] S43. The cloud chain end digitally signs the timestamp of the original unique hash value and generates an original timestamp certificate;

[0023] S44. The cloud chain stores the original unique hash value and the original timestamp certificate on the chain;

[0024] S45. The consensus party conducts blockchain consensus on the editable encapsulated text and table. After the blockchain consensus is completed, the cloud chain end extracts the editable text and table data after the blockchain consensus, and uses a hash algorithm to perform hash calculation on the editable text and table data after the blockchain consensus to generate a unique hash value after the blockchain consensus, and records the timestamp of the unique hash value generated after the blockchain consensus;

[0025] S46. The cloud chain end digitally signs the timestamp of the unique hash value after the blockchain consensus and generates a blockchain timestamp certificate after the consensus;

[0026] S47. The cloud chain end stores the unique hash value after blockchain consensus and the timestamp certificate after blockchain consensus on the chain.

[0027] Furthermore, in step S5, the cloud chain end divides the role restrictions for the consensus parties as follows:

[0028] The cloud chain divides consensus parties into high-level roles, mid-level roles, and low-level roles.

[0029] Furthermore, in step S6, the consensus party role performs the corresponding blockchain consensus privacy operations according to the limited rights divided by the cloud chain end, specifically:

[0030] High-level roles have the permission to view, edit, copy, and delete in blockchain consensus privacy operations. Mid-level roles have the permission to view and copy in blockchain consensus privacy operations. Low-level roles have the permission to view in blockchain consensus privacy operations.

[0031] Furthermore, high-level roles can modify the permissions of mid-level and low-level roles in blockchain consensus privacy operations.

[0032] Furthermore, the cloud chain terminal provides an API interface for external users to access and query the original unique hash value and original timestamp certificate data stored on the chain in the cloud chain terminal, the unique hash value after blockchain consensus, and the timestamp certificate data after blockchain consensus.

[0033] Furthermore, in step S32, the identity of the consensus party is collected through the cloud chain end and the identity authentication specifically includes consensus party identification code verification, password verification and face recognition verification.

[0034] Compared with the prior art, the present invention has the following beneficial effects:

[0035] The present invention proposes a cloud-chain combined privacy protection method for electronic archive data. Compared with traditional data security and privacy protection means, such as encryption technology and data backup, it can protect data privacy to a certain extent, but it does not have blockchain technology to record the transaction history of data, verify the integrity and authenticity of data, and prevent data from being tampered with or forged. The present invention proposes a cloud-chain combined privacy protection method for electronic archive data. This method can perform cloud-chain combined operations on electronic archive data. At the same time, by controlling the access rights and sharing scope of the data, the security and privacy of the electronic archive data during the sharing process are ensured. BRIEF DESCRIPTION OF THE DRAWINGS

[0036] In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the following briefly introduces the drawings required for use in the description of the embodiments. Obviously, the drawings described below are only preferred embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.

[0037] Figure 1 This is a schematic diagram of the overall process of the cloud chain combined with privacy protection method for electronic archive data proposed in an embodiment of the present invention.

[0038] Figure 2 It is a schematic diagram of the overall process of the sub-steps of step S4 in the cloud chain combined with privacy protection method for electronic archive data proposed in an embodiment of the present invention. DETAILED DESCRIPTION

[0039] The principles and features of the present invention are described below with reference to the accompanying drawings. The enumerated embodiments are only used to explain the present invention and are not used to limit the scope of the present invention.

[0040] Reference Figure 1 and Figure 2 The present invention provides a cloud chain combined privacy protection method for electronic archive data, the method comprising the following steps:

[0041] S1, respectively build the electronic archive collection end and the cloud chain end;

[0042] S2. Identify the collected electronic archive data through the electronic archive collection terminal and obtain an identification result;

[0043] S3. The cloud chain end publishes the recognition results through blockchain consensus;

[0044] S4. The cloud chain end records the timestamp node for the blockchain consensus of the consensus party and stores the timestamp node blockchain consensus content on the cloud chain end;

[0045] S5. The cloud chain end divides the roles and limits the rights of the consensus parties;

[0046] S6. The consensus parties perform corresponding blockchain consensus privacy operations based on the restricted rights assigned by the cloud chain end.

[0047] For example, in order to ensure the security and privacy of electronic archive data during the sharing process, an electronic archive collection terminal can be built to collect and process electronic archive data. It includes various devices and software, such as scanners, OCR optical character recognition software, etc., which are used to convert paper archives or electronic documents into digital formats and perform preliminary recognition and digital format conversion. A cloud chain terminal can also be built, which is built on a cloud computing platform and integrates blockchain technology. It is responsible for processing the storage, verification, consensus, authority management and other functions of electronic archive data. The recognition results obtained by the electronic archive collection terminal can be published through the blockchain consensus through the cloud chain terminal, so that the consensus parties can enter the company in the blockchain. The blockchain ensures the immutability and decentralization of electronic archive data. When the blockchain network After the nodes in the network reach a consensus, the cloud chain end will record the timestamp of the consensus and store the consensus content on the blockchain. The addition of the timestamp provides proof of the time dimension for the data, enhancing the credibility and traceability of the data. In order to ensure the security and privacy of the data, the cloud chain end will divide the permissions according to the roles and responsibilities of the consensus parties. Different roles have different permissions for viewing, editing, copying, deleting, etc. of data, which helps prevent data leakage and abuse. After obtaining the corresponding permissions, the consensus parties can perform corresponding privacy operations on the blockchain according to their roles. For example, some roles may only be able to view specific electronic file data, while other roles can edit or delete data. All operations will leave records on the blockchain, thereby ensuring the traceability and transparency of the operations.

[0048] In step S2, the following sub-steps are included:

[0049] S21, the electronic archive collection terminal identifies the file extension of the electronic archive data as text or table type;

[0050] S22. The electronic archive collection terminal uses OCR recognition technology to editably encapsulate electronic archive data of text and table types and obtains an editable encapsulation key.

[0051] Exemplarily, the electronic archive collection end obtains the file type of the electronic archive data. The file type is usually identified by the file extension such as .txt, .doc, .docx, .xls, .xlsx, etc., and then determines whether the electronic archive is a text type or a table type based on these extensions. After identifying and converting the data, the electronic archive collection end encapsulates the data into an editable format such as a Word document, Excel table, etc., and provides an editable encapsulation key. The key may be used to protect the encapsulated data from being accessed or modified by unauthorized consensus parties, or for subsequent verification and data recovery.

[0052] In step S3, the sub-steps are included:

[0053] S31. The cloud chain end will edit the encapsulated key to verify the key format. When the key format verification is successful, the cloud chain end will edit the encapsulated key to publish the blockchain consensus.

[0054] S32. Collect the identity of the consensus party through the cloud chain and perform identity authentication;

[0055] S33. When the consensus party passes the identity authentication, the cloud chain end issues a key to the consensus party to decrypt the editable encapsulated text and table.

[0056] For example, the cloud chain end verifies the format of the editable encapsulated key received by the electronic archive collection end to ensure that the format of the key is correct, complete and meets the expected security standards. The key format verification includes checking the key length, encoding method, whether it contains illegal characters, etc. When the key format verification is successful, the cloud chain end uses the consensus mechanism of blockchain technology to publish the key. The blockchain consensus mechanism allows the consensus parties of multiple nodes in the network to reach a consensus on a certain data or status, thereby ensuring the immutability and security of the data. In this scenario, publishing the key to the blockchain can ensure that the storage and distribution of the key will be carried out in a decentralized, secure and traceable environment. After the key is successfully published to the blockchain, the cloud chain end needs to determine which node consensus parties have the right to access and decrypt the key. Identity authentication specifically includes consensus party identification code verification, password verification and face recognition verification. The cloud chain end verifies the authenticity by requiring the consensus party to provide identity authentication. Once the consensus party's identity authentication is passed, the cloud chain end will issue keys to these consensus parties. This key is an editable encapsulated key that has been previously format-verified and published on the blockchain. The consensus party can use this key to decrypt text and table data that was previously editably encapsulated by the electronic archive collection end. Through this process, the cloud chain end not only ensures the security and traceability of the key, but also controls which entities have the right to access and decrypt sensitive data through identity authentication and key distribution mechanisms, which helps to maintain the confidentiality, integrity and availability of electronic archive data.

[0057] In step S4, the sub-steps are included:

[0058] S41. The consensus parties conduct blockchain consensus on the decrypted and editable encapsulated text and tables;

[0059] S42. When the consensus party reaches a blockchain consensus, the cloud chain extracts the original editable text and table data, and uses a hash algorithm to perform hash calculation on the original editable text and table data to generate an original unique hash value, and records the timestamp of the generation of the original unique hash value;

[0060] S43. The cloud chain end digitally signs the timestamp of the original unique hash value and generates an original timestamp certificate;

[0061] S44. The cloud chain stores the original unique hash value and the original timestamp certificate on the chain;

[0062] S45. The consensus party conducts blockchain consensus on the editable encapsulated text and table. After the blockchain consensus is completed, the cloud chain end extracts the editable text and table data after the blockchain consensus, and uses a hash algorithm to perform hash calculation on the editable text and table data after the blockchain consensus to generate a unique hash value after the blockchain consensus, and records the timestamp of the unique hash value generated after the blockchain consensus;

[0063] S46. The cloud chain end digitally signs the timestamp of the unique hash value after the blockchain consensus and generates a blockchain timestamp certificate after the consensus;

[0064] S47. The cloud chain end stores the unique hash value after blockchain consensus and the timestamp certificate after blockchain consensus on the chain.

[0065] Exemplarily, the consensus parties use the consensus mechanism of the blockchain to view, edit, copy, and delete the decrypted editable text and table data, and multiple consensus parties participate in it. They also reach a consensus on the integrity and correctness of the data through proof of work, proof of stake consensus algorithms, etc. At the same time as the consensus parties conduct blockchain consensus, the cloud chain end extracts the original editable text and table data, and uses the hash algorithm to perform hash calculation on the original editable text and table data to generate the original unique hash value, and records the timestamp of the generation of the original unique hash value to prove the existence and timeliness of the data. The cloud chain end verifies the original unique hash value. The timestamp of a hash value is digitally signed to ensure the integrity of the timestamp and the authenticity of the source. The digital signature is usually signed with the private key of the cloud chain end. Any entity holding the public key of the cloud chain end can verify the validity of the signature. The cloud chain end stores the original unique hash value and the original timestamp certificate on the chain, so that the original unique hash value and the original timestamp certificate will be permanently recorded on the blockchain, which is tamper-proof and traceable. After the blockchain consensus is completed, the cloud chain end extracts the editable text and table data that have passed the blockchain consensus again, and uses the same hash algorithm to hash these data to generate a new unique hash value. At the same time, the timestamp of generating the new hash value is recorded, the cloud chain end digitally signs the new timestamp, and generates a timestamp certificate after the blockchain consensus. The cloud chain end stores the unique hash value after the blockchain consensus and the timestamp certificate after the blockchain consensus on the chain. Then there are two versions of hash values ​​and timestamp certificates on the blockchain: one is the hash value and timestamp certificate of the original data, and the other is the hash value and timestamp certificate of the data after the blockchain consensus. The two versions of hash values ​​and timestamp certificates provide a strong guarantee for the integrity and traceability of the data. By comparing the two hash values, it can be verified whether the data has changed during the blockchain consensus process. At the same time, the timestamp certificate proves the existence and status of the data at different time points.

[0066] In step S5, the cloud chain divides the roles and limits the rights of the consensus parties as follows:

[0067] The cloud chain divides consensus parties into high-level roles, mid-level roles, and low-level roles.

[0068] For example, the cloud chain end can better protect the security and privacy of electronic archive data by dividing different consensus parties into different levels of roles, that is, different levels of roles have different authority functions.

[0069] In step S6, the consensus party role performs the corresponding blockchain consensus privacy operations according to the limited rights divided by the cloud chain end:

[0070] High-level roles have the permission to view, edit, copy, and delete in blockchain consensus privacy operations. Mid-level roles have the permission to view and copy in blockchain consensus privacy operations. Low-level roles have the permission to view in blockchain consensus privacy operations.

[0071] For example, high-level role permissions include: View: the ability to view all private data of electronic archive data on the blockchain, including but not limited to transaction records, smart contract content, balances of specific accounts, etc. Edit: the right to modify part or all of the private data of electronic archive data on the blockchain, including correcting incorrect data, updating smart contract logic, or adjusting blockchain parameters, etc. In particular, for modifications on the blockchain, the blockchain can be a permissioned blockchain or a consortium blockchain. Blockchain), and high-level roles in the blockchain have the right to modify. In order not to destroy the immutability and traceability of the blockchain, this permission is only used in very rare cases and requires a strict approval process. Copy: The private data on the blockchain can be copied to the local or other storage media for offline analysis, backup or sharing. Delete: High-level roles may have the right to delete specific private data of electronic archive data on the blockchain. In order not to destroy the integrity and traceability of the blockchain, this permission is only used in very rare cases and requires a strict approval process. Intermediate role permissions: View, Copy: Same as high-level roles, able to view and copy private data of electronic archive data on the blockchain. Low-level role permissions, View: Only have the right to view private data on the blockchain.

[0072] High-level roles can modify the permissions of mid-level and low-level roles in blockchain consensus privacy operations.

[0073] For example, high-level roles can adjust the permissions of mid-level and low-level roles in blockchain consensus privacy operations to adapt to changes in business needs or adjustments to security policies.

[0074] The cloud chain terminal provides an API interface for external users to access and query the original unique hash value and original timestamp certificate data stored on the cloud chain terminal, the unique hash value after blockchain consensus, and the timestamp certificate data after blockchain consensus.

[0075] For example, the API interface provided by the electronic cloud chain provides a convenient way for external users to access and query data on the blockchain, which helps to improve the credibility and traceability of electronic archive data.

[0076] In step S32, the identity of the consensus party is collected through the cloud chain end and the identity authentication specifically includes consensus party identification code verification, password verification and face recognition verification.

[0077] For example, the cloud chain end can verify the authenticity of the consensus party's identity through consensus party identification code verification, password verification and face recognition verification.

[0078] The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present invention should be included in the scope of protection of the present invention.

Claims

1. A cloud-chain-based privacy protection method for electronic archive data, characterized in that: The method comprises the following steps: S1, respectively build the electronic archive collection end and the cloud chain end; S2. Identify the collected electronic archive data through the electronic archive collection terminal and obtain the identification result, including the following sub-steps: S21, the electronic archive collection terminal identifies the file extension of the electronic archive data as text or table type; S22. The electronic archive collection terminal uses OCR recognition technology to encapsulate the electronic archive data of text and table types into editable form and obtains an editable encapsulation key; S3. The cloud chain end publishes the recognition results through blockchain consensus, including sub-steps: S31. The cloud chain end will edit the encapsulated key to verify the key format. When the key format verification is successful, the cloud chain end will edit the encapsulated key to publish the blockchain consensus. S32. Collect the identity of the consensus party through the cloud chain and perform identity authentication; S33. When the consensus party passes the identity authentication, the cloud chain end issues a key to the consensus party to decrypt the editable encapsulated text and table; S4. The cloud chain end records the timestamp node for the blockchain consensus of the consensus party and stores the timestamp node blockchain consensus content on the cloud chain end, including sub-steps: S41. The consensus parties conduct blockchain consensus on the decrypted and editable encapsulated text and tables; S42. When the consensus party reaches a blockchain consensus, the cloud chain extracts the original editable text and table data, and uses a hash algorithm to perform hash calculation on the original editable text and table data to generate an original unique hash value, and records the timestamp of the generation of the original unique hash value; S43. The cloud chain end digitally signs the timestamp of the original unique hash value and generates an original timestamp certificate; S44. The cloud chain stores the original unique hash value and the original timestamp certificate on the chain; S45. The consensus party conducts blockchain consensus on the editable encapsulated text and table. After the blockchain consensus is completed, the cloud chain end extracts the editable text and table data after the blockchain consensus, and uses a hash algorithm to perform hash calculation on the editable text and table data after the blockchain consensus to generate a unique hash value after the blockchain consensus, and records the timestamp of the unique hash value generated after the blockchain consensus; S46. The cloud chain end digitally signs the timestamp of the unique hash value after the blockchain consensus and generates a blockchain timestamp certificate after the consensus; S47. The cloud chain end stores the unique hash value after blockchain consensus and the timestamp certificate after blockchain consensus on the chain; S5. The cloud chain end divides the roles and limits the rights of the consensus parties; S6. The consensus parties perform corresponding blockchain consensus privacy operations based on the restricted rights assigned by the cloud chain end.

2. The cloud-chain-based privacy protection method for electronic archival data according to claim 1 is characterized in that: In step S5, the cloud chain divides the roles and limits the rights of the consensus parties as follows: The cloud chain divides consensus parties into high-level roles, mid-level roles, and low-level roles.

3. The cloud chain combined privacy protection method for electronic archive data according to claim 2 is characterized in that: In step S6, the consensus party role performs the corresponding blockchain consensus privacy operations according to the limited rights divided by the cloud chain end: High-level roles have the permission to view, edit, copy, and delete in blockchain consensus privacy operations. Mid-level roles have the permission to view and copy in blockchain consensus privacy operations. Low-level roles have the permission to view in blockchain consensus privacy operations.

4. The cloud-chain-based privacy protection method for electronic archival data according to claim 3 is characterized in that: High-level roles can modify the permissions of mid-level and low-level roles in blockchain consensus privacy operations.

5. The cloud chain combined privacy protection method for electronic archive data according to claim 1 is characterized in that: The cloud chain terminal provides an API interface for external users to access and query the original unique hash value and original timestamp certificate data stored on the cloud chain terminal, the unique hash value after blockchain consensus, and the timestamp certificate data after blockchain consensus.

6. The cloud chain combined privacy protection method for electronic archive data according to claim 1 is characterized in that: In step S32, the identity of the consensus party is collected through the cloud chain end and the identity authentication specifically includes consensus party identification code verification, password verification and face recognition verification.

Images