JP7222106B2 - Privacy data uplink method, device and storage medium - Google Patents

Description

TECHNICAL FIELD The present application relates to the technical field of alliance chain, specifically to privacy data uplink method, device and storage medium.

Compared to public chains, many data privacy-conscious companies, banks and other business entities usually choose the architecture of alliance chains. For example, a plurality of banks, a plurality of insurance companies, a plurality of shipping companies, etc. form an alliance, and each enterprise has an alliance chain node to form an alliance chain, adopting the BFT consensus protocol. At the same time, it supports the main node of each round of switching consensus, allowing all nodes to participate in the block generation process, and ensuring the fairness of alliance members.

The above alliance chain scheme guarantees data privacy for non-alliance members, but in the actual commercial scene, data privacy is required even within the alliance. For example, in the above alliance, shipping company A and bank B have business data, and shipping company A wishes to disclose the business data to nodes other than shipping company A's node a and bank B's node b. Otherwise, the above alliance chain scheme cannot meet this demand.

In view of the above deficiencies and shortcomings of the prior art, a privacy data uplink method, a device and a storage medium are provided, which can record privacy data in the uplink and meet the demand for internal data privacy that is disclosed only to the business side. It is desirable to

In a first aspect, the present invention provides a privacy data uplink method suitable for a user end, which comprises:
respectively encrypting the privacy data based on the public keys of the current user and some other business party to generate at least two pieces of encrypted information;
packaging and generating a first cryptographic transaction based on each cryptographic information, transmitting to alliance chain nodes for broadcasting, packaging and executing;
including.

A main ledger and a sub-ledger are arranged in the database of the Alliance Chain node, the main ledger is used to store the execution result of each ordinary unencrypted transaction, and the sub-ledger is a kept secret. A key is used to store the execution result of a cryptographic transaction that successfully decrypts the cryptographic information in one transaction, and the Merkle Tree Root of the Alliance Chain Block is generated based on the main ledger.

In a second aspect, the present invention provides a privacy data uplink method suitable for alliance chain nodes, which comprises:
When executing the first block, for each first transaction in the first block, respectively:
determining whether the first transaction is a cryptographic transaction;
If it is not an encrypted transaction, directly execute the first transaction, store the execution result in the main ledger,
If it is an encrypted transaction, decrypt each encrypted information in the first transaction based on the held second private key, and determine whether the decryption of one encrypted information was successful. ,
if not successful, do not execute the first transaction;
if successful, executing the first transaction after successful decryption and storing the execution result in a sub-ledger;
after each first transaction is processed, generating a Merkle tree root for the first block based on the main ledger;
including
The encrypted transaction is generated by the first user end respectively encrypting the privacy data based on each business party's public key to generate at least two pieces of encrypted information and then packaging.

In a third aspect, the present invention further provides a device comprising one or more processors and memory for storing one or more programs, wherein the memory comprises one or more or instructions executed by a plurality of processors to enable the one or more processors to perform the privacy data uplink methods provided by embodiments of the present invention.

In a fourth aspect, the present invention further provides a storage medium having a computer program stored thereon, the computer program executing the privacy data uplink method provided by the embodiments of the present invention. It can be so.

The privacy data uplink methods, devices, and storage media provided by many embodiments of the present invention allow the disclosure of each business side by adding sub-ledgers to alliance chain node databases that do not affect consensus. After encrypting the privacy data with the key, it is packaged into an encrypted transaction, so that the node on the business side can successfully decrypt it, record the execution result of the encrypted transaction in the sub-ledger, and base it on the main ledger. Make a consensus, non-business side nodes cannot decrypt and execute cryptocurrency transactions, so privacy data is recorded in the uplink to meet the demand for internal data privacy only open to the business side be able to.

Other features, objects and advantages of the present application will become more apparent upon reading the detailed description of the non-limiting examples made with reference to the following drawings.
4 is a flowchart of a privacy data uplink method provided by an embodiment of the present invention; 4 is a flowchart of another privacy data uplink method provided by an embodiment of the present invention; 1 is a structural schematic diagram of a device provided by one embodiment of the present invention; FIG.

Hereinafter, the present application will be described in more detail in combination with the drawings and examples. It should be noted that the specific embodiments described herein are only used to interpret the relevant inventions and are not limitations on the present invention. For ease of explanation, only the parts related to the present application are shown in the drawings.

It should be noted that the embodiments in the present application and the features in the embodiments can be combined with each other if they do not conflict. Hereinafter, the present application will be described in detail in combination with embodiments with reference to the drawings.

FIG. 1 is a flowchart of a privacy data uplink method provided by one embodiment of the present invention.

As shown in Fig. 1, in this embodiment, the present invention provides a privacy data uplink method suitable for the user end, which includes: a.
At S11, the privacy data are respectively encrypted based on the current user's and some other business' public keys to generate at least two pieces of encrypted information.
At S13, a first cryptographic transaction is packaged and generated based on each cryptographic information, sent to the alliance chain nodes for broadcasting, packaged and executed.

A main ledger and a sub-ledger are arranged in the database of the Alliance Chain node, the main ledger is used to store the execution result of each ordinary unencrypted transaction, and the sub-ledger is a kept secret. A key is used to store the execution result of a cryptographic transaction that successfully decrypts the cryptographic information in one transaction, and the Merkle Tree Root of the Alliance Chain Block is generated based on the main ledger.

In the following, one node is allocated to each of AC Bank and DG Company to form an alliance chain of 7 nodes, and the alliance chain registers privacy data according to the method shown in FIG. , the method shown in FIG. 1 will be exemplified.

If Company E, Company F, and Bank B have made a transaction that needs to be recorded in the uplink and generates some privacy _data that we do not want to disclose to other banks or companies within the alliance. , a user terminal a of an employee of company E executes step S11 according to the operation of the employee to obtain public keys P _E , P F , and P _B of company E, company _F , and bank B. , P _E , P _F and P _B to generate encrypted information P _E ( _{data m )} , P _F (data _m ) and P _B (data _m ), respectively.

In step S13, based on P _E (data _m ), P _F (data _m ), and P _B (data _m ), package and generate an encrypted transaction tx1 and send it to node e located at company E. do. In this embodiment, when the user terminal a packages the encrypted transaction tx1, each encrypted information P _E (data _m ), P _F (data _m ), P _B (data _m ) is stored in the payload field of tx1. remembered. In more embodiments, those skilled in the art can store each encryption information in different fields of tx1 according to actual needs.

After receiving the cryptographic transaction tx1, node e broadcasts tx1 to other Alliance Chain nodes, and each Alliance Chain node packages tx1 into block block1 and executes it according to the consensus mechanism of the Alliance Chain .

When alliance chain node a located in Bank A executes tx1, it determines that tx1 is an encrypted transaction, and based on the held private key p _A , encrypts information _PE (data _m ) , P _F (data _m ) and P _B (data _m ) respectively, and if all the decryptions fail, node a determines that tx1 is an encrypted transaction not associated with it, Skip tx1 and then execute the next transaction in block1.

Similarly, alliance chain nodes c, d, and g located in Bank C, Company D, and Company G do not execute tx1 when executing block1.

When the Alliance Chain node b located in Bank B executes tx1, it similarly determines that tx1 is an encrypted transaction, and based on the held private key _pB , the encrypted information P _E ( data _m ), P _F (data _m ), and P _B (data _m ) are decoded respectively, and the data _m is obtained by successfully decoding PB(datam), and node b determines that tx1 is itself , convert encrypted transaction tx1 into encrypted transaction tx1′ after decryption based on data _m obtained by decryption, execute tx1′, and execute tx1 ' is stored in the subledger of node b.

Similarly, the alliance chain node e located at Company E decrypts P _E (data _m ) based on the held private key p _E , and when the decryption is successful, executes tx1′, Store the execution result of tx1′ in the subledger of node e. The alliance chain node f located at Company F decrypts P _F (data _m ) based on the held private key p _F , and when the decryption is successful, executes tx1′ and executes tx1′. Store the execution result in the subledger of node f.

After each node ag executes each transaction of block1, generate the Merkle tree root of block1 based on the main ledger to ensure that the consensus of block1 is not affected by cryptographic transactions and subledgers .

In a preferred embodiment, the cryptographic information is structured as a key-value pair, the key of the key-value pair is structured as the first public key to perform the encryption, and the value of the key-value pair is is constructed as the encryption result of encrypting the privacy data with the first public key.

Similarly, taking the example of the alliance chain of the above seven nodes posting privacy data, in this embodiment, data _m is generated by encrypting data m by P _E , P _F , and P _B , respectively. The encrypted information is three kv-pairs: key ₁ : P _E , value ₁ : P _E (data _m ), key ₂ : P _F , value ₂ : P _F (data _m ), and key ₃ : P _B , value ₃ : P _B (data _m ).

Accordingly, if tx1 is determined to be a cryptographic transaction by one Alliance Chain node, P _E (data _m ), P _F (data _m ), P _B (data _m ), it is only necessary to search for the existence of its own public key in the key value of each encrypted information. For example, node a does not execute tx1 if it is determined that P _A does not exist in key ₁ -key ₃ . Node b decodes value ₃ based on p _B if it finds that P _B exists in key ₁ -key ₃ .

In some other embodiments, those skilled in the art can also adopt several different configurations according to actual needs, for example, the key of the above key-value pair is a cryptographic Although it is configured as a first address corresponding to the first public key to be authenticated, the same technical effect can be achieved by any of them, so they are not exemplified here.

In the above embodiment, by adding a sub-ledger that does not affect consensus to the database of the alliance chain node, the privacy data is encrypted with the public key of each business and then packaged into an encrypted transaction. Ensuring that the business-side node successfully decrypts, records the execution result of the cryptographic transaction in the sub-ledger, makes consensus based on the main ledger, and the non-business-side node performs the decryption and cryptographic transaction can not be performed, so the privacy data can be recorded in the uplink to meet the demand for internal data privacy that is only open to the business side.

FIG. 2 is a flowchart of another privacy data uplink method provided by one embodiment of the present invention. The method shown in FIG. 2 can be performed in conjunction with the method shown in FIG.

As shown in Fig. 2, in this embodiment, the present invention further provides a privacy data uplink method suitable for alliance chain nodes, which includes the following steps.
When executing the first block, perform the following steps for each first transaction in the first block, respectively.
At S211, it is determined whether the first transaction is an encrypted transaction.
If the first transaction is not an encrypted transaction, directly execute the first transaction and store the execution result in the main ledger (step S212).
If the first transaction is an encrypted transaction, each encrypted information in the first transaction is decrypted based on the held second secret key (step S213), and one encrypted information It is determined whether or not the decoding has succeeded (step S214).
In step S214, if NO, do not execute the first transaction (step S215); if YES, execute the first transaction after successful decryption; is stored in the sub-ledger (step S216).
After each first transaction is processed, generate the Merkle tree root of the first block based on the main ledger (step S22).

The encrypted transaction is generated by the first user end respectively encrypting the privacy data based on each business party's public key to generate at least two pieces of encrypted information and then packaging.

Preferably, the encryption information is configured as a key-value pair, the key of the key-value pair configured as a first public key for encryption, and the value of the key-value pair configured as a first public key for encryption. It is configured as an encryption result obtained by encrypting privacy data with a public key of No. 1.

Steps S213-S214 include:
Each encrypted information in the first transaction is searched for a second public key corresponding to the second private key. If not, any encrypted information in the first transaction cannot be decrypted. If so, decrypt the value corresponding to the second public key based on the second private key.

Preferably, each cryptographic information is stored in the payload field of the first cryptographic transaction.

The privacy data uplink principle of the method shown in FIG. 2 can refer to the method shown in FIG. 1, which is not repeated here.

FIG. 3 is a structural schematic diagram of a device provided by one embodiment of the present invention.

As shown in FIG. 3, in another aspect, the present application further provides a device 300 comprising one or more central processing units (CPUs) 301, which are stored in a read-only memory (ROM) 302. Various operations and processes can be performed based on programs or programs loaded from storage portion 308 into random access memory (RAM) 303 . The RAM 303 also stores various programs and data necessary for operating the device 300 . The CPU 301 , ROM 302 and RAM 303 are interconnected via a bus 304 . Input/output (I/O) interface 305 is also connected to bus 304 .

An input section 306 including a keyboard, mouse, etc., an output section 307 including a cathode ray tube (CRT), a liquid crystal display (LCD) and speakers, etc., a storage section 308 including a hard disk, and a network interface such as a LAN card, modem, etc. Components such as communication portion 309 , including cards, are connected to I/O interface 305 . The communication portion 309 performs communication processing via a network such as the Internet. Drivers 310 may be connected to I/O interfaces 305 as desired. A removable medium 311 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc. may be attached to the driver 310 as necessary, and a computer program read from this may be installed in the storage section 308 as necessary. good.

In particular, according to embodiments of the present application, the methods described in any of the above embodiments may be implemented as computer software programs. For example, an embodiment of the present application includes a computer program product, which includes a computer program tangibly embodied on a machine-readable medium, the computer program including program code for performing any of the methods described above. In such embodiments, the computer program may be downloaded and installed from a network by communications portion 309 and/or installed from removable media 311 .

As yet another aspect, the present application further provides a computer-readable storage medium, which may be a computer-readable storage medium included in the apparatus of the above embodiments, or may exist as a single unit. It may well be a computer-readable storage medium that is not assembled into a device. A computer-readable storage medium may store one or more programs, and the programs may execute methods according to the present application by one or more processors.

The flowcharts and block diagrams in the accompanying drawings illustrate possible system architectures, functionality, and operation of systems, methods and computer program products according to various embodiments of the present invention. In this regard, each block in a flowchart or block diagram can represent a module, program segment, or portion of code that implements a given logical function. contains one or more executable instructions for It should also be noted that, in some implementations, the functions marked in the block may occur out of the order marked in the drawings. For example, two blocks shown in succession may, in fact, be executed substantially concurrently or may be executed in the reverse order depending on the functionality involved. Each block in the block diagrams and/or flowchart illustrations, and combinations of blocks in the block diagrams and/or flowchart illustrations, can be implemented by means of dedicated hardware for the given function or operation, or by means of dedicated hardware and computer instructions. It should be noted that it can be realized by combining with

Units or modules according to embodiments of the present application may be implemented in the form of software or may be implemented in the form of hardware. The described units or modules may be provided in a processor, for example each unit may be provided in a software program in a computer or mobile smart device, or may be a hardware device configured as a single unit. . However, the names of these units or modules do not constitute limitations to the units or modules themselves under certain circumstances.

The foregoing description is merely that of preferred embodiments and applicable technical principles of the present application. A person skilled in the art will understand that the scope of the invention pertaining to the present application is not limited to a technical proposal based on a specific combination of the above technical features, and the above technical features or equivalent features can be used arbitrarily within the scope of the concept of the present application. It should be understood that other technical solutions formed in combination with are also included. For example, the above features and the technical features disclosed in the present application (but not limited to) having similar functions may be technical proposals formed by replacing each other.

Claims (6)

A privacy data uplink method suitable for a user end, comprising:
respectively encrypting the privacy data based on public keys of the current user and some other business party to generate at least two pieces of encrypted information;
packaging and generating a first cryptographic transaction based on each of said cryptographic information and transmitting to said alliance chain nodes for broadcast, packaging and execution by alliance chain nodes;
including
A main ledger and a sub-ledger are arranged in the database of the Alliance Chain node, the main ledger is used to store unencrypted execution results of each transaction, and the sub-ledger is maintained. The private key is used to store the execution result of a cryptographic transaction that successfully decrypts one cryptographic information in the transaction, and the Merkle tree root of the alliance chain block is generated based on the main ledger. ,
A privacy data uplink method characterized by: The encryption information is configured as a key-value pair, the key of the key-value pair configured as a first public key for encryption, and the value of the key-value pair configured as the first public key for encryption. 1 as an encryption result of encrypting the privacy data with a public key of 1,
The privacy data uplink method according to claim 1, characterized in that: each said cryptographic information is stored in a payload field of said first cryptographic transaction;
The privacy data uplink method according to claim 1 or 2, characterized in that: A privacy data uplink method suitable for alliance chain nodes, comprising:
When executing a first block, for each first transaction in said first block, respectively:
determining whether the first transaction is an encrypted transaction;
if it is not an encrypted transaction, directly execute the first transaction and store the execution result in the main ledger;
If it is an encrypted transaction, decrypt each encrypted information in the first transaction based on the held second secret key, and determine whether the decryption of one encrypted information is successful. death,
If unsuccessful, do not execute the first transaction;
if successful, executing the first transaction after successful decryption and storing the execution result in a sub-ledger;
after each said first transaction is processed, generating a Merkle tree root for said first block based on said main ledger;
including
wherein the encrypted transaction is generated by the first user end encrypting the privacy data respectively based on the public key of each business side to generate at least two pieces of encrypted information and then packaging;
A privacy data uplink method characterized by: The encryption information is configured as a key-value pair, the key of the key-value pair configured as a first public key for encryption, and the value of the key-value pair configured as the first public key for encryption. configured as an encryption result of encrypting the privacy data with a public key of 1,
Decrypting each encrypted information in the first transaction based on the held second private key and determining whether one encrypted information was successfully decrypted,
searching whether each encrypted information in the first transaction includes a second public key corresponding to the second private key;
otherwise, any encrypted information in the first transaction cannot be decrypted;
if included, decrypting a value corresponding to said second public key based on said second private key;
The privacy data uplink method according to claim 4, characterized in that: each said cryptographic information is stored in a payload field of a first cryptographic transaction;
The privacy data uplink method according to claim 4 or 5, characterized in that:

Images