Data processing method based on alliance chain, server and medium

Abstract

The invention provides a data processing method based on an alliance chain, a server and a medium, and relates to the technical field of big data. According to the method, in response to a file application request, sub-hash value information sent by each authorized approval party of the file application request after successful approval is obtained, and the sub-hash value information comprises sub-homomorphic hash values of partial data files corresponding to the authorized approval parties and secondary sub-hash values of the sub-homomorphic hash values; the partial data files form a to-be-applied file corresponding to the file application request; performing approval verification on the file application request according to the sub-hash value information sent by each authorized approval party; and if the approval verification is passed, sending a file authorization instruction to each authorization approval party, the file authorization instruction being used for instructing the authorization approval party to send a part of data files stored by the authorization approval party to the data application party, so that the data application party integrates the part of data files to obtain a to-be-applied file. According to the method provided by the invention, the security and reliability of data during multi-party collaborative management are improved.

Description

Technical Field

[0001] The present application relates to the field of big data technology, and in particular to a data processing method, server and medium based on alliance chain. Background Art

[0002] With the rapid development of big data technology, multi-party collaborative management of big data files is becoming more and more common. Various organizations and departments can jointly participate in the management and utilization of data to achieve higher business efficiency and better decision-making support while ensuring data security and compliance.

[0003] In related technologies, when multiple parties collaborate to manage big data files, the data holder can upload the big data files to the blockchain and set authorization conditions through smart contracts. The data applicant can initiate a file application request to the blockchain through a smart contract, and the blockchain can notify the authorized reviewer to review it through the preset authorization conditions. If the blockchain receives the information that the authorized reviewer has successfully reviewed it, the big data file stored in the block can be sent to the data applicant.

[0004] However, this multi-party collaborative management approach cannot guarantee the security and reliability of data. Summary of the invention

[0005] The embodiments of the present application provide a data processing method, server and medium based on alliance chain, which can improve the security and reliability of data during collaborative management by multiple parties.

[0006] In a first aspect, an embodiment of the present application provides a method, comprising:

[0007] In response to the file application request initiated by the data applicant, after obtaining the approval success information sent by each authorized reviewer on the alliance chain, obtain the sub-hash value information uploaded to the alliance chain by each authorized reviewer, the sub-hash value information includes the sub-homomorphic hash value of the partial data file corresponding to the authorized reviewer and the secondary sub-hash value of the sub-homomorphic hash value, and the partial data files corresponding to each authorized reviewer constitute the to-be-applied file corresponding to the file application request;

[0008] Verify the file application request based on the sub-hash value information uploaded to the alliance chain by each authorized reviewer;

[0009] If the approval verification is passed, a file authorization instruction is sent to each authorized approving party, and the file authorization instruction is used to instruct the authorized approving party to send the respective stored partial data files to the data applicant, so that the data applicant can integrate the partial data files to obtain the file to be applied for.

[0010] In a possible implementation, the verification of the file application request based on the sub-hash value information uploaded to the alliance chain by each authorized reviewer includes:

[0011] For each authorized reviewer, perform secondary hash calculation on the sub-homomorphic hash value uploaded by the authorized reviewer to the alliance chain to obtain the first secondary sub-hash value, and compare the first secondary sub-hash value with the secondary sub-hash value corresponding to the authorized reviewer stored in the alliance chain. If they are consistent, the preliminary approval is passed;

[0012] If each authorized reviewer passes the preliminary approval, a homomorphic sum calculation is performed on the sub-homomorphic hash values ​​uploaded to the alliance chain by each authorized reviewer to obtain a first homomorphic hash value; it is determined whether the first homomorphic hash value is equal to the homomorphic hash value of the file to be applied for stored in the alliance chain; if they are equal, the file application request is approved and verified; if they are not equal, the file application request is not approved and verified.

[0013] In a possible implementation, in response to the file application request initiated by the data applicant, after obtaining the approval success information sent by each authorized approver on the alliance chain, obtaining the sub-hash value information uploaded to the alliance chain by each authorized approver includes:

[0014] Acquire first identity information sent by a data applicant, generate a corresponding first key certificate according to the first identity information, and send the first key certificate to the data applicant;

[0015] Obtain a file verification request sent by the data applicant after successfully performing identity authentication according to the first key certificate, and send hash value information of the file to be applied for corresponding to the file verification request to the data applicant, wherein the hash value information includes a homomorphic hash value of the file to be applied for and a secondary hash value of the homomorphic hash value;

[0016] In response to a file application request initiated by the data applicant after successfully verifying the legitimacy of the file according to the hash value information, the file application request is sent to each authorized reviewer of the file to be applied for on the alliance chain;

[0017] After obtaining the approval success information sent by each authorized reviewer on the alliance chain, obtain the sub-hash value information uploaded to the alliance chain by each authorized reviewer.

[0018] In a possible implementation manner, the file application request is initiated by the data applicant using a smart contract after performing a secondary hash calculation on the homomorphic hash value to obtain a first secondary hash value and determining that the first secondary hash value is consistent with the secondary hash value of the homomorphic hash value;

[0019] The authorized approving party determines that the approval is successful after successfully authenticating the data applicant and successfully verifying the legitimacy of the file based on the sub-homomorphic hash value and the secondary sub-hash value stored by the authorized approving party.

[0020] In a possible implementation, the homomorphic hash value of the document to be applied for stored in the consortium chain is obtained in the following manner:

[0021] Obtaining second identity information sent by the data holder of the to-be-applied document, generating a corresponding second key certificate according to the second identity information, and sending the second key certificate to the data holder;

[0022] Obtaining the file to be applied for, the homomorphic hash value of the file to be applied for, and the secondary hash value of the homomorphic hash value, which are sent by the data holder after successful identity authentication according to the second key certificate;

[0023] The secondary hash value is uploaded to the alliance chain. After the block information on the alliance chain is confirmed, the homomorphic hash value is uploaded to the alliance chain.

[0024] In a possible implementation manner, the sub-hash value information stored in the authorization and approval party is obtained in the following manner:

[0025] For each authorized reviewer of the application document on the alliance chain, obtain the third identity information sent by the authorized reviewer, generate a corresponding third key certificate according to the third identity information, and send the third key certificate to the authorized reviewer;

[0026] Divide the application document into multiple partial data files according to a preset order, and calculate the sub-homomorphic hash value of each partial data file, wherein the partial data files correspond to the authorized reviewer one by one;

[0027] After the identity of each authorized reviewer is successfully authenticated through the third key certificate, the partial data file and the sub-homomorphic hash value of the partial data file are respectively sent to the corresponding authorized reviewer, so that the authorized reviewer performs a secondary hash calculation on the sub-homomorphic hash value to obtain the corresponding secondary sub-hash value, and uploads the sub-homomorphic hash value and the secondary sub-hash value to the alliance chain.

[0028] In a possible implementation manner, after sending the partial data files and the sub-homomorphic hash values ​​of the partial data files to corresponding authorized reviewers respectively, the method further includes:

[0029] Delete the pending application documents sent by the data holder.

[0030] In a second aspect, an embodiment of the present application provides a server, including:

[0031] An acquisition module is used to respond to a file application request initiated by a data applicant, and after obtaining approval success information sent by each authorized approver on the alliance chain, obtain sub-hash value information uploaded to the alliance chain by each authorized approver, wherein the sub-hash value information includes a sub-homomorphic hash value of a part of the data file corresponding to the authorized approver and a secondary sub-hash value of the sub-homomorphic hash value, and the part of the data file corresponding to each authorized approver constitutes the to-be-applied file corresponding to the file application request;

[0032] The processing module is used to verify the file application request based on the sub-hash value information uploaded to the alliance chain by each authorized reviewer; if the approval verification is passed, a file authorization instruction is sent to each authorized reviewer, and the file authorization instruction is used to instruct the authorized reviewers to send their respective stored partial data files to the data applicant, so that the data applicant can integrate the partial data files to obtain the file to be applied for.

[0033] In a third aspect, an embodiment of the present application provides another server, including:

[0034] A processor, and a memory communicatively connected to the processor;

[0035] Memory is used to store computer executable instructions;

[0036] The processor is used to execute the computer-executable instructions stored in the memory, so that the processor executes the above-mentioned first aspect and / or various possible implementations of the first aspect.

[0037] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, in which computer-executable instructions are stored. When the computer-executable instructions are executed by a processor, they are used to implement the above-mentioned first aspect and / or various possible implementation methods of the first aspect.

[0038] In a fifth aspect, an embodiment of the present application provides a computer program product, including a computer program, which, when executed by a processor, is used to implement the above-mentioned first aspect and / or various possible implementation methods of the first aspect.

[0039] The embodiment of the present application provides a data processing method, server and medium based on the alliance chain, which can form the authorized review and approval party of the big data file with multiple nodes pre-set in the alliance chain. Each authorized review and approval party participates in the authorization and approval of the big data file, and stores the partial files that constitute the big data file and the key information of the partial files, that is, the sub-homomorphic hash value and the secondary sub-hash value of the sub-homomorphic hash value. After the server receives the file application request initiated by the data applicant, the file application request can be sent to each authorized review and approval party, and each authorized review and approval party can approve the file application request. Only after each authorized review and approval party has successfully approved, the server will perform approval verification according to the sub-hash value information sent by each authorized review and approval party to further determine the legitimacy of the file. If the approval verification is passed, each authorized review and approval party can send the partial data files stored by each party to the data applicant, so that the data applicant can integrate the files to be applied for according to each partial data file. Through such a setting, multiple authorized review and approval parties can be formed by using multiple nodes pre-set in the alliance chain, and each authorized review and approval party can only approve partial data files, which greatly disperses the approval authority and improves the security and reliability of data during multi-party collaborative management. Furthermore, after each authorized reviewer has successfully approved the application, the server will also perform approval verification based on the sub-hash value information sent by each authorized reviewer, further improving the security and reliability of data during multi-party collaborative management while ensuring data privacy. BRIEF DESCRIPTION OF THE DRAWINGS

[0040] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.

[0041] Figure 1 A system architecture diagram of an embodiment of the present application;

[0042] Figure 2 This is a flow chart of a data processing method based on a consortium chain according to an embodiment of the present application;

[0043] Figure 3 This is a flowchart of a data processing method based on a consortium chain according to another embodiment of the present application;

[0044] Figure 4 A schematic diagram of the structure of a server according to an embodiment of the present application;

[0045] Figure 5 This is a schematic diagram of the structure of a server according to another embodiment of the present application.

[0046] The above drawings have shown clear embodiments of the present application, which will be described in more detail later. These drawings and text descriptions are not intended to limit the scope of the present application in any way, but to illustrate the concept of the present application to those skilled in the art by referring to specific embodiments. DETAILED DESCRIPTION

[0047] Exemplary embodiments will be described in detail herein, examples of which are shown in the accompanying drawings. When the following description refers to the drawings, the same numbers in different drawings represent the same or similar elements unless otherwise indicated. The implementations described in the following exemplary embodiments do not represent all implementations consistent with the present application. Instead, they are merely examples of devices and methods consistent with some aspects of the present application as detailed in the appended claims.

[0048] The terms "first", "second", "third", "fourth", etc. (if any) in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable where appropriate, so that the embodiments of the present application described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any variations are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device that includes a series of steps or units is not necessarily limited to those steps or units that are clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0049] In the technical solution of this application, the collection, storage, use, processing, transmission, provision and disclosure of information such as financial data or user data involved shall comply with the provisions of relevant laws and regulations and shall not violate public order and good morals.

[0050] It should be noted that in the embodiments of the present application, certain software, components, models and other existing solutions in the industry may be mentioned, and they should be regarded as exemplary. Their purpose is only to illustrate the feasibility of implementing the technical solution of the present application, but it does not mean that the applicant has or will necessarily use the solution.

[0051] It should also be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with relevant laws, regulations and standards, and provide corresponding operation entrances for users to choose to authorize or refuse.

[0052] The alliance chain-based data processing method, server and medium of the present application can be used in the field of big data technology, and can also be used in any field other than the field of big data technology, such as the field of data processing, etc. The application field of the alliance chain-based data processing method, server and medium of the present application is not limited.

[0053] The alliance chain-based data processing method, server and medium of the present application can be applied to scenarios where multi-party collaborative management of big data files is performed based on the alliance chain. Any scenario involving the management of big data files in the alliance chain can apply the alliance chain-based data processing method, server and medium of the present application.

[0054] First, the terms involved in this application are explained:

[0055] Blockchain: It is a distributed ledger technology that forms an unalterable and traceable record by packaging data into blocks and linking them into chains through cryptographic technology. Each block contains a certain amount of transaction data, and each block is linked to the previous block to form a chain structure. Blockchain has the characteristics of decentralization, transparency and unalterability.

[0056] Consortium chain: It is a variant of blockchain, in which a consortium of multiple pre-selected nodes jointly manages and maintains the ledger. This chain structure is usually used within enterprises or institutions that require higher privacy and higher transaction speeds. By setting different permission levels, the consortium chain can control who can read and write data, thereby improving data privacy.

[0057] Smart contract: Executable code on the alliance chain automatically executes contract terms through the alliance chain, reducing intermediary and transaction costs. The alliance chain also completes the update of alliance member ledger information by executing smart contracts.

[0058] Public Key Infrastructure (PKI): A platform that provides public key encryption and digital signature services, manages keys and certificates, and is authoritative because certificates are issued by Certificate Authority (CA).

[0059] Asymmetric encryption algorithm: encryption and decryption use different keys, that is, public and private key pairs. Encryption uses the other party's public key, and signature uses its own private key. Generally used to verify certificates and transmit keys.

[0060] Symmetric encryption algorithm: The same key is used for encryption and decryption, and is generally used to transmit data after verifying the certificate.

[0061] Homomorphic hash functions: Homomorphic hash functions are a class of hash functions that have specific mathematical properties that make them useful when working with certain types of data and operations. Specifically, these hash functions allow specific operations to be performed on hash values, so that the result can still be inferred without knowing the original data. Homomorphic hash functions have the following property: h(x)⊕h(y)=h(x⊙y) where ⊕ and ⊙ are two operators, defined in the hash value space and input value space respectively.

[0062] With the rapid development of big data technology, processing and managing massive data has become more feasible. Efficient network and communication technologies make data transmission between distributed systems faster and more stable, creating a good basic environment for multi-party collaborative management. Enterprises are increasingly relying on data to make decisions and optimize business processes. Through multi-party collaborative management of big data files, data from different sources can be integrated to provide enterprises with more comprehensive analysis and insights, supporting data-driven decision-making.

[0063] Multi-party collaborative management of big data files is an important way of modern data management. It combines advanced technical means and business needs to provide efficient, secure and reliable data processing and storage solutions. In this way, various organizations and departments can jointly participate in the management and utilization of data to achieve higher business efficiency and better decision support, while ensuring data security and compliance.

[0064] In related technologies, when multiple parties collaborate to manage big data files, the data holder can upload the big data files to the blockchain and set authorization conditions through smart contracts. The data applicant can initiate a file application request to the blockchain through a smart contract, and the blockchain can notify the authorized reviewer to review it through the preset authorization conditions. If the blockchain receives the information that the authorized reviewer has successfully reviewed it, the big data file stored in the block can be sent to the data applicant.

[0065] However, the approval authority of this type of multi-party collaborative management is very concentrated. Authorization approval is generally done step by step, but there is usually only one person at each level, and each authorized approver can see the complete big data file, which can easily lead to data tampering during authorization approval, making the data security and reliability low during multi-party collaborative management.

[0066] Based on the above technical problems, the inventive concept of this application is: how to provide a data processing solution based on a consortium chain that can improve the security and reliability of data during collaborative management by multiple parties.

[0067] The embodiment of the present application provides a data processing method, server and medium based on the alliance chain, which can make multiple nodes pre-set in the alliance chain constitute the authorized review and approval party of the big data file, each authorized review and approval party participates in the authorization and approval of the big data file, and only stores some files that constitute the big data file and the key information of some files, which greatly disperses the approval authority. Only after each authorized review and approval party has successfully approved, the server will perform approval verification according to the sub-hash value information sent by each authorized review and approval party, further improving the security and reliability of data during multi-party collaborative management on the basis of ensuring data privacy.

[0068] The technical solution of the present application and how the technical solution of the present application solves the above-mentioned technical problems are described in detail below with specific embodiments. The following specific embodiments can be combined with each other, and the same or similar concepts or processes may not be repeated in some embodiments. The embodiments of the present application will be described below in conjunction with the accompanying drawings.

[0069] Figure 1 This is a system architecture diagram of an embodiment of the present application, such as Figure 1 As shown, the server including CA and alliance chain communicates with the data holder, data applicant and authorized reviewer respectively. The server responds to the file application request initiated by the data applicant, and after obtaining the approval success information sent by each authorized reviewer on the alliance chain, obtains the sub-hash value information uploaded to the alliance chain by each authorized reviewer, the sub-hash value information includes the sub-homomorphic hash value of the partial data file corresponding to the authorized reviewer and the secondary sub-hash value of the sub-homomorphic hash value, and the partial data files corresponding to each authorized reviewer constitute the to-be-applied file corresponding to the file application request; the file application request is approved and verified according to the sub-hash value information uploaded to the alliance chain by each authorized reviewer; if the approval verification is passed, a file authorization instruction is sent to each authorized reviewer, and the file authorization instruction is used to instruct the authorized reviewer to send the partial data files stored by each of them to the data applicant, so that the data applicant can integrate the partial data files to obtain the to-be-applied file.

[0070] Figure 2 This is a flowchart of a data processing method based on a consortium chain according to an embodiment of the present application. This embodiment uses the execution subject as a server to illustrate the file storage process in the data processing method based on the consortium chain. Figure 2 As shown, the data processing method based on the alliance chain may include the following steps:

[0071] S201: Acquire the second identity information sent by the data holder of the file to be applied for, generate a corresponding second key certificate according to the second identity information, and send the second key certificate to the data holder.

[0072] In this embodiment, the data holder of the file to be applied for (data applicant) can send identity information to the certificate authority (CA) of the server for registration. The CA will record the identity information of the data holder and distribute a second key certificate containing a public-private key pair to the data holder.

[0073] In this embodiment, the server may include two parts: CA and alliance chain.

[0074] S202: Obtain the file to be applied for, the homomorphic hash value of the file to be applied for, and the secondary hash value of the homomorphic hash value, which are sent by the data holder after successful identity authentication according to the second key certificate.

[0075] In this embodiment, after receiving the second key certificate, the data holder uses a homomorphic hash algorithm to calculate the homomorphic hash value H(F) of the file F to be applied for, and uses a hash function algorithm to calculate the secondary hash value Hash(H(F)) of the homomorphic hash value H(F).

[0076] In this embodiment, the data holder can use the public-private key pair in the second key certificate to authenticate the data, that is, after the signature verification by the CA is successful, the symmetric encryption algorithm can be used for encrypted transmission, and the file to be applied F, the homomorphic hash value H(F) of the file to be applied F, and the secondary hash value Hash(H(F)) can be sent to the CA together.

[0077] In this embodiment, the specific implementation method of the data holder using the public-private key pair in the second key certificate to perform signature verification can refer to the relevant existing technology and will not be described in detail here.

[0078] S203: Upload the secondary hash value to the alliance chain. After the block information on the alliance chain is confirmed, upload the homomorphic hash value to the alliance chain.

[0079] In this embodiment, after CA receives the data sent by the data holder, it can first upload the secondary hash value Hash(H(F)) to the alliance chain. After the block information on the alliance chain confirms that Hash(H(F)) has not been tampered with, the homomorphic hash value H(F) can be uploaded to the alliance chain.

[0080] S204: For each authorized reviewer of the application document on the alliance chain, obtain the third identity information sent by the authorized reviewer, generate a corresponding third key certificate according to the third identity information, and send the third key certificate to the authorized reviewer.

[0081] In this embodiment, multiple preset nodes constituting the alliance chain can serve as authorized reviewers of the documents to be applied for, and multiple authorized reviewers can perform authorized review with equal authority, thereby dispersing the review authority.

[0082] In this embodiment, each authorized reviewer can send identity information to the CA for registration. The CA will record the identity information of the authorized reviewer and distribute a third key certificate containing a public-private key pair to each authorized reviewer.

[0083] S205: Divide the application document into multiple partial data files according to a preset order, and calculate the sub-homomorphic hash value of each partial data file, and the partial data files correspond to the authorized reviewer one by one.

[0084] In this embodiment, CA can divide the application file F into multiple partial data files F1, F2, ..., FN in a specific order, which is expressed in formal language as F = F1+F2+...+FN, and calculate the sub-homomorphic hash value H(FN) of each partial data file at the same time.

[0085] In this embodiment, the number of partial data files corresponds to the number of authorized reviewers, that is, one authorized reviewer corresponds to only one partial data file.

[0086] S206: After the identity authentication of each authorized reviewer is successfully carried out through the third key certificate, the partial data files and the sub-homomorphic hash values ​​of the partial data files are respectively sent to the corresponding authorized reviewers, so that the authorized reviewers perform secondary hash calculations on the sub-homomorphic hash values ​​to obtain the corresponding secondary sub-hash values, and upload the sub-homomorphic hash values ​​and the secondary sub-hash values ​​to the alliance chain.

[0087] In this embodiment, the CA can use the public-private key pair in the third key certificate to authenticate the identity of the authorized approver. That is, after the CA successfully verifies the signature, it can use the symmetric encryption algorithm for encrypted transmission and send the partial data file FN and the sub-homomorphic hash value H (FN) of the partial data file to the corresponding authorized approver.

[0088] In this embodiment, after the authorized reviewer receives and decrypts the partial data file FN and the sub-homomorphic hash value H(FN) of the partial data file, in order to ensure the data integrity of the sub-homomorphic hash value of each partial data file, the secondary sub-hash value Hash(H(FN)) of the sub-homomorphic hash value H(FN) can be calculated.

[0089] In this embodiment, the authorized reviewer can first upload the secondary sub-hash value Hash (H (FN)) to the alliance chain. After the block information on the alliance chain confirms that Hash (H (FN)) has not been tampered with, the sub-homomorphic hash value H (FN) can be uploaded to the alliance chain to complete the data storage process.

[0090] It should be noted that when storing data on a consortium chain, all processes involving data transmission require signature verification using key certificates and encrypted transmission using symmetric encryption algorithms to ensure the reliability, security and integrity of data during data transmission.

[0091] It should also be noted that the same hash function algorithm can be used when performing secondary hash calculations on each homomorphic hash value.

[0092] In this embodiment, when storing data on the alliance chain, the data holder can first register with the CA to obtain a key certificate so that the data holder can use the key certificate for identity authentication when uploading data later. After receiving the data sent by the data holder, the CA can first upload the secondary hash value Hash (H (F)) to the alliance chain. After the block information on the alliance chain confirms that Hash (H (F)) has not been tampered with, the homomorphic hash value H (F) can be uploaded to the alliance chain. In addition, multiple nodes pre-set in the alliance chain can also be used to form the authorized reviewer of the big data file, and each authorized reviewer also registers with the CA to obtain a key certificate so that the key certificate can be used for identity authentication when the CA transmits data to the authorized reviewer later. CA can divide the application file F into multiple partial data files in a specific order, so that each authorized reviewer only stores the corresponding partial data files and the sub-hash value information of the partial data files, which greatly disperses the approval authority and improves the security and reliability of data during multi-party collaborative management.

[0093] In a possible implementation, after the partial data files and the sub-homomorphic hash values ​​of the partial data files are sent to the corresponding authorized reviewer in the above step S206, the following may also be included:

[0094] Delete pending application documents sent by the data holder.

[0095] In this embodiment, after CA sends part of the data files and the sub-homomorphic hash values ​​of part of the data files to the corresponding authorized reviewer, it can delete the pending application files sent by the data holder. CA does not store the complete large data files, thereby improving the security and reliability of data storage.

[0096] Figure 3 This is a flowchart of a data processing method based on a consortium chain according to another embodiment of the present application. This embodiment uses the execution subject as a server to illustrate the file approval process in the data processing method based on a consortium chain. Figure 3 As shown, the data processing method based on the alliance chain may include the following steps:

[0097] S301: Acquire first identity information sent by a data applicant, generate a corresponding first key certificate according to the first identity information, and send the first key certificate to the data applicant.

[0098] In this embodiment, the data applicant can send identity information to the certificate authority (CA) of the server for registration. The CA will record the identity information of the data holder and distribute a first key certificate containing a public-private key pair to the data holder.

[0099] In this embodiment, the server may include two parts: CA and alliance chain.

[0100] S302: Obtain a file verification request sent by the data applicant after successfully performing identity authentication according to the first key certificate, and send the hash value information of the file to be applied for corresponding to the file verification request to the data applicant, wherein the hash value information includes the homomorphic hash value of the file to be applied for and the secondary hash value of the homomorphic hash value.

[0101] In this embodiment, the data applicant can use the public-private key pair in the first key certificate to authenticate the identity. That is, after the CA successfully verifies the signature, the CA can use a symmetric encryption algorithm for encrypted transmission and send the homomorphic hash value H(F) and the secondary hash value Hash(H(F)) of the file F to be applied for to the data applicant.

[0102] In this embodiment, the specific implementation method of the data applicant using the public-private key pair in the first key certificate to perform signature verification can refer to the relevant existing technology and will not be described in detail here.

[0103] S303: In response to the file application request initiated by the data applicant after successfully verifying the legitimacy of the file according to the hash value information, the file application request is sent to each authorized reviewer of the file to be applied for on the alliance chain.

[0104] In this embodiment, the data applicant can use the hash function algorithm to calculate the first and second hash values ​​Hash'(H(F)) of the homomorphic hash value H(F). If H(F)=Hash'(H(F)), the legitimacy of the file is successfully verified.

[0105] In this embodiment, if the data applicant successfully verifies the legitimacy of the file, it can initiate a proposal to obtain the big data file through the smart contract, that is, a file application request. After receiving it, the CA can send the file application request to each authorized reviewer of the file to be applied for on the alliance chain.

[0106] S304: After obtaining the approval success information sent by each authorized reviewer on the alliance chain, obtain the sub-hash value information uploaded to the alliance chain by each authorized reviewer.

[0107] In this embodiment, the sub-hash value information may include the sub-homomorphic hash value of the partial data file corresponding to the authorized reviewer and the secondary sub-hash value of the sub-homomorphic hash value. The partial data files corresponding to each authorized reviewer constitute the files to be applied for corresponding to the file application request.

[0108] In this embodiment, after the authorized reviewer receives the file application request, he can execute the data file approval process, that is, verify the identity of the applicant and query the legality of the file. After the verification is successful, the approval success information is uploaded to the alliance chain.

[0109] In this embodiment, after receiving the approval success information sent by each authorized approver, the CA can obtain the sub-hash value information related to the application document uploaded to the alliance chain by each authorized approver during the data storage phase, namely H(FN) and Hash(H(FN)).

[0110] S305: The file application request is approved and verified according to the sub-hash value information uploaded to the alliance chain by each authorized approver.

[0111] In this embodiment, after CA obtains H(FN) and Hash(H(FN)) uploaded to the alliance chain by each authorized reviewer, it can use H(FN) and Hash(H(FN)) to perform review and approval verification to determine whether the data has been tampered with during the storage process.

[0112] S306: If the approval verification is passed, a file authorization instruction is sent to each authorized approver.

[0113] In this embodiment, the file authorization instruction can be used to instruct the authorized reviewer to send the respective stored partial data files to the data applicant, so that the data applicant can integrate the partial data files to obtain the file to be applied for.

[0114] In this embodiment, if the approval verification is passed, it means that the partial data files stored by each authorized approval party are legal and have not been tampered with. The CA can send a file authorization instruction to each authorized approval party, so that each authorized approval party sends the partial data files stored by each party to the applicant through a symmetric encryption algorithm. After receiving the partial data files, the applicant can use the key of the symmetric encryption algorithm to decrypt them and combine the partial data files to obtain a complete file to be applied for.

[0115] It should be noted that when conducting data approval on the alliance chain, each process involving data transmission requires the use of key certificates for signature verification and the use of symmetric encryption algorithms for encrypted transmission to ensure the reliability, security and integrity of data during data transmission.

[0116] It should also be noted that the same hash function algorithm can be used when performing secondary hash calculations on each homomorphic hash value.

[0117] In this embodiment, multiple nodes pre-set in the alliance chain can be composed of authorized reviewers of big data files. Each authorized reviewer participates in the authorization review of big data files and stores partial files that constitute big data files and key information of partial files, namely, sub-homomorphic hash values ​​and secondary sub-hash values ​​of sub-homomorphic hash values. After the server receives the file application request initiated by the data applicant, it can send the file application request to each authorized reviewer, and each authorized reviewer can review the file application request. Only after each authorized reviewer has successfully reviewed the file, the server will verify the review based on the sub-hash value information sent by each authorized reviewer to further determine the legitimacy of the file. If the review is successful, each authorized reviewer can send the stored partial data files to the data applicant, so that the data applicant can integrate the partial data files to obtain the application file. Through such a setting, multiple nodes pre-set in the alliance chain can be used to form multiple authorized reviewers, and each authorized reviewer can only review partial data files, which greatly disperses the review authority and improves the security and reliability of data during multi-party collaborative management. Furthermore, after each authorized reviewer has successfully approved the application, the server will also perform approval verification based on the sub-hash value information sent by each authorized reviewer, further improving the security and reliability of data during multi-party collaborative management while ensuring data privacy.

[0118] In one possible implementation, the file application request in the above step S301 is initiated by the data applicant using a smart contract after performing a secondary hash calculation on the homomorphic hash value to obtain a first secondary hash value and determining that the first secondary hash value is consistent with the secondary hash value of the homomorphic hash value.

[0119] The authorized approver determines that the approval is successful after successfully authenticating the data applicant and successfully verifying the legitimacy of the file based on the sub-homomorphic hash value and the secondary sub-hash value stored by the authorized approver.

[0120] In this embodiment, when the data applicant verifies the legitimacy of the file based on the hash value information, the hash function algorithm can be used to calculate the first and second hash values ​​Hash'(H(F)) of the homomorphic hash value H(F). If Hash'(H(F)) = the stored Hash(H(F)), the legitimacy of the file is successfully verified.

[0121] In this embodiment, after receiving the file application request, the authorized reviewer can execute the data file review process, that is, verify the identity of the applicant and the legitimacy of the file. Specifically, the public and private key pairs in the key certificate can be used to authenticate the identity and verify the legitimacy of the file: the secondary sub-hash value Hash'(H(FN)) of the stored sub-homomorphic hash value H(FN) is calculated using the hash function algorithm. If Hash'(H(FN)) = the stored Hash(H(FN)), the legitimacy of the file is successfully verified.

[0122] In this embodiment, the data applicant will use the smart contract to initiate a file application request only after successfully verifying the legitimacy of the file using the homomorphic hash value and the secondary hash value sent by the CA. After receiving the file application request, the authorized reviewer will use the public and private key pairs in the key certificate to authenticate the identity, and will send the approval success information to the CA only after successfully verifying the legitimacy of the file using the stored sub-homomorphic hash value and the secondary sub-hash value. Through such a setting, the security and reliability of the data can be further improved.

[0123] In a possible implementation, the above step S302 performs approval verification on the file application request according to the sub-hash value information uploaded to the alliance chain by each authorized approver, which may include:

[0124] For each authorized reviewer, a secondary hash calculation is performed on the sub-homomorphic hash value uploaded by the authorized reviewer to the alliance chain to obtain the first and second sub-hash values, and the first and second sub-hash values ​​are compared with the secondary sub-hash values ​​corresponding to the authorized reviewer stored in the alliance chain. If they are consistent, the preliminary approval is passed.

[0125] If each authorized reviewer passes the preliminary approval, the sub-homomorphic hash values ​​uploaded by each authorized reviewer to the alliance chain are homomorphically added and calculated to obtain the first homomorphic hash value; it is determined whether the first homomorphic hash value is equal to the homomorphic hash value of the application file stored in the alliance chain; if they are equal, the file application request is approved and verified; if they are not equal, the file application request is not approved and verified.

[0126] In this embodiment, after CA obtains H(FN) and Hash(H(FN)) uploaded to the alliance chain by each authorized reviewer during the data storage phase, in order to ensure the data integrity of the homomorphic hash value stored in the alliance chain, the first and second sub-hash values ​​Hash'(H(FN)) of the sub-homomorphic hash value H(FN) can be calculated using the hash function algorithm. If Hash'(H(FN)) = the obtained Hash(H(FN)), the data stored in the alliance chain has not been tampered with, and the preliminary approval is successful. If the data stored in the alliance chain has been tampered with, it means that it has been attacked and the preliminary approval has failed.

[0127] In this implementation, if each authorized reviewer has passed the preliminary review, that is, the data stored in the alliance chain has not been tampered with, then the homomorphic hash values ​​of some data files are driven by the smart contract to perform homomorphic addition operations to obtain a new first homomorphic hash value H'(F) of the complete data file, H'(F) = H(F1)+H(F2)+…+H(FN). If H'(F) = H(F) stored in the alliance chain, the file application request is approved and verified.

[0128] In this implementation, the approval results of each authorized approver can be recorded on the alliance chain, which cannot be tampered with, and the approval records are distributedly stored to avoid single point failures.

[0129] In this embodiment, homomorphic hashing algorithms and hashing algorithms can be used to ensure the privacy of key data file information on the alliance chain, and to drive the effective aggregation and verification of multi-party approval results with smart contracts to ensure the legitimacy of the data stored in the alliance chain.

[0130] The following is an explanation of the data processing method based on the alliance chain of the present application with a specific embodiment.

[0131] In a specific embodiment, when multiple parties collaborate to manage, the specific process of data processing by a consortium chain is as follows:

[0132] In the first step, the data holder sends the second identity information to the server's certificate authority (CA) for registration. The CA records the data holder's identity information and distributes the second key certificate containing the public-private key pair to the data holder.

[0133] In the second step, the data holder uses the homomorphic hash algorithm to calculate the homomorphic hash value H(F) of the big data file F, and uses the hash function algorithm to calculate the secondary hash value Hash(H(F)) of the homomorphic hash value H(F).

[0134] In the third step, the data holder uses the public-private key pair in the second key certificate to authenticate the data, and then uses a symmetric encryption algorithm for encrypted transmission, and sends the big data file F, the homomorphic hash value H(F) of the big data file F, and the secondary hash value Hash(H(F)) to the CA.

[0135] In the fourth step, CA uploads Hash (H (F)) to the alliance chain. After the block information on the alliance chain is confirmed, H (F) is uploaded to the alliance chain.

[0136] In the fifth step, multiple authorized reviewers that constitute the alliance chain send the third-party identity information to the CA for registration. The CA records the identity information of the authorized reviewers and distributes the third-party key certificates containing the public-private key pairs to each authorized reviewer.

[0137] In the sixth step, CA divides the application document into multiple partial data files according to the preset order, and calculates the sub-homomorphic hash value H (FN) of each partial data file.

[0138] In the seventh step, after the CA successfully authenticates the identity of each authorized reviewer through the third key certificate, it sends the partial data file FN and the sub-homomorphic hash value H (FN) of the partial data file to the corresponding authorized reviewer.

[0139] In the eighth step, the authorized reviewer calculates the secondary sub-hash value Hash(H(FN)) of the sub-homomorphic hash value H(FN), uploads Hash(H(FN)) to the alliance chain, and uploads Hash(H(FN)) to the alliance chain after the block information on the alliance chain confirms that Hash(H(FN)) has not been tampered with.

[0140] In the ninth step, the data applicant sends the first identity information to the CA for registration. The CA records the identity information of the data holder and distributes the first key certificate containing the public-private key pair to the data holder.

[0141] In the eleventh step, after the data applicant successfully authenticates his / her identity using the public-private key pair in the first key certificate, the CA uses a symmetric encryption algorithm for encrypted transmission and sends the homomorphic hash value H(F) and the secondary hash value Hash(H(F)) of the large data file F to the data applicant.

[0142] In the twelfth step, the data applicant successfully verifies the legitimacy of the file based on H(F) and Hash(H(F)) and initiates a file application request through a smart contract. After receiving the request, the CA sends the file application request to each authorized reviewer of the file to be applied for on the alliance chain.

[0143] In the thirteenth step, after the authorized reviewer receives the file application request, it executes the data file approval process, that is, verifies the identity of the applicant and the legitimacy of the file. After successful verification, the approval success information is uploaded to the alliance chain.

[0144] In the fourteenth step, after receiving the approval success information sent by each authorized reviewer, CA obtains H (FN) and Hash (H (FN)) uploaded to the alliance chain by each authorized reviewer.

[0145] In the fifteenth step, CA verifies the file application request based on H (FN) and Hash (H (FN)) uploaded to the alliance chain by each authorized reviewer. After the approval verification is passed, the CA sends the file authorization instruction to each authorized reviewer.

[0146] In the sixteenth step, after receiving the data, the authorized reviewer sends the partial data files stored by each party to the data applicant, and the data applicant integrates the partial data files to obtain the big data file F.

[0147] Figure 4 This is a schematic diagram of the structure of a server according to an embodiment of the present application. Figure 4 As shown, the server includes: an acquisition module 41, which is used to respond to the file application request initiated by the data applicant, and after obtaining the approval success information sent by each authorized approver on the alliance chain, obtain the sub-hash value information uploaded to the alliance chain by each authorized approver, the sub-hash value information includes the sub-homomorphic hash value of the partial data file corresponding to the authorized approver and the secondary sub-hash value of the sub-homomorphic hash value, and the partial data files corresponding to each authorized approver constitute the files to be applied for corresponding to the file application request; a processing module 42, which is used to verify the file application request according to the sub-hash value information uploaded to the alliance chain by each authorized approver; if the approval verification is passed, a file authorization instruction is sent to each authorized approver, and the file authorization instruction is used to instruct the authorized approver to send the partial data files stored by each of them to the data applicant, so that the data applicant can obtain the files to be applied for according to the integration of each partial data file.

[0148] The server provided in the embodiment of the present application can execute the technical solution shown in the above method embodiment, and its implementation principle and beneficial effects are similar, which will not be repeated here.

[0149] Figure 5 This is a schematic diagram of the structure of a server according to another embodiment of the present application. Figure 5 As shown, the server includes: a processor 501, and a memory 502 communicatively connected to the processor 501; the memory 502 stores computer execution instructions; the processor 501 executes the computer execution instructions stored in the memory 502 to implement the steps of the data processing method based on the alliance chain in the above-mentioned method embodiments.

[0150] In the above server, the memory 502 and the processor 501 are electrically connected directly or indirectly to realize data transmission or interaction. For example, these elements can be electrically connected to each other through one or more communication buses or signal lines, such as through a bus connection. The memory 502 stores computer-executable instructions for implementing the data access control method, including at least one software function module that can be stored in the memory 502 in the form of software or firmware. The processor 501 executes various functional applications and data processing by running the software programs and modules stored in the memory 502.

[0151] The memory 502 may be, but is not limited to, a random access memory (RAM), a read only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electric erasable programmable read-only memory (EEPROM), etc. The memory 502 is used to store programs, and the processor 501 executes the programs after receiving the execution instruction. Furthermore, the software programs and modules in the above-mentioned memory 502 may also include an operating system, which may include various software components and / or drivers for managing system tasks (such as memory management, storage device control, power management, etc.), and may communicate with various hardware or software components to provide an operating environment for other software components.

[0152] The processor 501 may be an integrated circuit chip having the ability to process signals. The processor 501 may be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), etc. The methods, steps, and logic diagrams disclosed in the embodiments of the present application may be implemented or executed. The general-purpose processor may be a microprocessor or any conventional processor.

[0153] An embodiment of the present application further provides a computer-readable storage medium, in which computer-executable instructions are stored. When the computer-executable instructions are executed by a processor, they are used to implement the steps of each method embodiment of the present application.

[0154] An embodiment of the present application further provides a computer program product, including a computer program, which implements the steps of each method embodiment of the present application when executed by a processor.

[0155] It should be noted that, for the aforementioned method embodiments, for the sake of simplicity, they are all expressed as a series of action combinations, but those skilled in the art should be aware that the present application is not limited by the described order of actions, because according to the present application, certain steps can be performed in other orders or simultaneously. Secondly, those skilled in the art should also be aware that the embodiments described in the specification are all optional embodiments, and the actions and modules involved are not necessarily required by the present application.

[0156] It should be further noted that, although the various steps in the flowchart are displayed in sequence according to the indication of the arrows, these steps are not necessarily executed in sequence in the order indicated by the arrows. Unless there is a clear description in this article, the execution of these steps is not strictly limited in order, and these steps can be executed in other orders. Moreover, at least a portion of the steps in the flowchart may include multiple sub-steps or multiple stages, and these sub-steps or stages are not necessarily executed at the same time, but can be executed at different times, and the execution order of these sub-steps or stages is not necessarily to be carried out in sequence, but can be executed in turn or alternately with other steps or at least a portion of the sub-steps or stages of other steps.

[0157] It should be understood that the above-mentioned device embodiments are only illustrative, and the device of the present application can also be implemented in other ways. For example, the division of units / modules in the above-mentioned embodiments is only a logical function division, and there may be other division methods in actual implementation. For example, multiple units, modules or components can be combined, or can be integrated into another system, or some features can be ignored or not executed.

[0158] In addition, unless otherwise specified, each functional unit / module in each embodiment of the present application may be integrated into one unit / module, each unit / module may exist physically separately, or two or more units / modules may be integrated together. The above-mentioned integrated unit / module may be implemented in the form of hardware or in the form of a software program module.

[0159] In the above embodiments, the description of each embodiment has its own emphasis. For the part not described in detail in a certain embodiment, please refer to the relevant description of other embodiments. The technical features of the above embodiments can be combined arbitrarily. In order to make the description concise, all possible combinations of the technical features in the above embodiments are not described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0160] Those skilled in the art will readily appreciate other embodiments of the present application after considering the specification and practicing the invention disclosed herein. The present application is intended to cover any modification, use or adaptation of the present application, which follows the general principles of the present application and includes common knowledge or customary techniques in the art that are not disclosed in the present application. The specification and examples are intended to be exemplary only, and the true scope and spirit of the present application are indicated by the appended claims.

[0161] It should be understood that the present application is not limited to the precise structures that have been described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the present application is limited only by the appended claims.

Claims

1. A data processing method based on alliance chain, characterized in that: include: In response to the file application request initiated by the data applicant, after obtaining the approval success information sent by each authorized reviewer on the alliance chain, obtain the sub-hash value information uploaded to the alliance chain by each authorized reviewer, the sub-hash value information includes the sub-homomorphic hash value of the partial data file corresponding to the authorized reviewer and the secondary sub-hash value of the sub-homomorphic hash value, and the partial data files corresponding to each authorized reviewer constitute the to-be-applied file corresponding to the file application request; Verify the file application request based on the sub-hash value information uploaded to the alliance chain by each authorized reviewer; If the approval verification is passed, a file authorization instruction is sent to each authorized approving party, and the file authorization instruction is used to instruct the authorized approving party to send the respective stored partial data files to the data applicant, so that the data applicant can integrate the partial data files to obtain the file to be applied for.

2. The data processing method based on alliance chain according to claim 1 is characterized in that: The approval and verification of the file application request according to the sub-hash value information uploaded to the alliance chain by each authorized reviewer includes: For each authorized reviewer, perform secondary hash calculation on the sub-homomorphic hash value uploaded by the authorized reviewer to the alliance chain to obtain the first secondary sub-hash value, and compare the first secondary sub-hash value with the secondary sub-hash value corresponding to the authorized reviewer stored in the alliance chain. If they are consistent, the preliminary approval is passed; If each authorized reviewer passes the preliminary approval, a homomorphic sum calculation is performed on the sub-homomorphic hash values ​​uploaded to the alliance chain by each authorized reviewer to obtain a first homomorphic hash value; it is determined whether the first homomorphic hash value is equal to the homomorphic hash value of the file to be applied for stored in the alliance chain; if they are equal, the file application request is approved and verified; if they are not equal, the file application request is not approved and verified.

3. The data processing method based on alliance chain according to claim 1 is characterized in that: The responding to the file application request initiated by the data applicant, after obtaining the approval success information sent by each authorized approver on the alliance chain, obtains the sub-hash value information uploaded to the alliance chain by each authorized approver, including: Acquire first identity information sent by a data applicant, generate a corresponding first key certificate according to the first identity information, and send the first key certificate to the data applicant; Obtain a file verification request sent by the data applicant after successfully performing identity authentication according to the first key certificate, and send hash value information of the file to be applied for corresponding to the file verification request to the data applicant, wherein the hash value information includes a homomorphic hash value of the file to be applied for and a secondary hash value of the homomorphic hash value; In response to a file application request initiated by the data applicant after successfully verifying the legitimacy of the file according to the hash value information, the file application request is sent to each authorized reviewer of the file to be applied for on the alliance chain; After obtaining the approval success information sent by each authorized reviewer on the alliance chain, obtain the sub-hash value information uploaded to the alliance chain by each authorized reviewer.

4. The data processing method based on alliance chain according to claim 3 is characterized in that: The file application request is initiated by the data applicant using a smart contract after performing a secondary hash calculation on the homomorphic hash value to obtain a first secondary hash value and determining that the first secondary hash value is consistent with the secondary hash value of the homomorphic hash value; The authorized approving party determines that the approval is successful after successfully authenticating the data applicant and successfully verifying the legitimacy of the file based on the sub-homomorphic hash value and the secondary sub-hash value stored by the authorized approving party.

5. The data processing method based on the alliance chain according to any one of claims 1 to 4, characterized in that: The homomorphic hash value of the document to be applied for stored in the alliance chain is obtained in the following way: Obtaining second identity information sent by the data holder of the to-be-applied document, generating a corresponding second key certificate according to the second identity information, and sending the second key certificate to the data holder; Obtaining the file to be applied for, the homomorphic hash value of the file to be applied for, and the secondary hash value of the homomorphic hash value, which are sent by the data holder after successful identity authentication according to the second key certificate; The secondary hash value is uploaded to the alliance chain. After the block information on the alliance chain is confirmed, the homomorphic hash value is uploaded to the alliance chain.

6. The data processing method based on alliance chain according to claim 5 is characterized in that: The sub-hash value information stored in the authorization and approval party is obtained in the following manner: For each authorized reviewer of the application document on the alliance chain, obtain the third identity information sent by the authorized reviewer, generate a corresponding third key certificate according to the third identity information, and send the third key certificate to the authorized reviewer; Divide the application document into multiple partial data files according to a preset order, and calculate the sub-homomorphic hash value of each partial data file, wherein the partial data files correspond to the authorized reviewer one by one; After the identity of each authorized reviewer is successfully authenticated through the third key certificate, the partial data file and the sub-homomorphic hash value of the partial data file are respectively sent to the corresponding authorized reviewer, so that the authorized reviewer performs a secondary hash calculation on the sub-homomorphic hash value to obtain the corresponding secondary sub-hash value, and uploads the sub-homomorphic hash value and the secondary sub-hash value to the alliance chain.

7. The data processing method based on alliance chain according to claim 6 is characterized in that: After sending the partial data files and the sub-homomorphic hash values ​​of the partial data files to the corresponding authorized reviewer respectively, the method further includes: Delete the pending application documents sent by the data holder.

8. A server, characterized in that: include: An acquisition module is used to respond to a file application request initiated by a data applicant, and after obtaining approval success information sent by each authorized approver on the alliance chain, obtain sub-hash value information uploaded to the alliance chain by each authorized approver, wherein the sub-hash value information includes a sub-homomorphic hash value of a part of the data file corresponding to the authorized approver and a secondary sub-hash value of the sub-homomorphic hash value, and the part of the data file corresponding to each authorized approver constitutes the to-be-applied file corresponding to the file application request; The processing module is used to verify the file application request based on the sub-hash value information uploaded to the alliance chain by each authorized reviewer; if the approval verification is passed, a file authorization instruction is sent to each authorized reviewer, and the file authorization instruction is used to instruct the authorized reviewers to send their respective stored partial data files to the data applicant, so that the data applicant can integrate the partial data files to obtain the file to be applied for.

9. A server, characterized in that: include: A processor, and a memory communicatively connected to the processor; The memory is used to store computer-executable instructions; The processor is used to execute the computer execution instructions stored in the memory, so that the processor executes the alliance chain-based data processing method as described in any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer-executable instructions, which, when executed by a processor, are used to implement the alliance chain-based data processing method according to any one of claims 1 to 7.

Images