A method for supervisors to share sensitive data in a consortium chain scenario based on group negotiation keys
By adopting a group negotiation key-based method in the alliance chain scenario, the problem of difficulty in building trust and inefficiency when the regulator group shares sensitive data is solved, and efficient and secure data sharing is achieved.
Patent Information
- Application Number
- CN202111330315.9
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2021-11-11
- Publication Date
- 2025-05-16
- Estimated Expiration
- 2041-11-11
Smart Images

Figure CN114239048B_ABST
Abstract
Description
Technical Field
[0001] Embodiments of the present invention relate to the technical field of alliance chain content supervision, and in particular, to a method for supervisors to share sensitive data in an alliance chain scenario based on group negotiated keys. Background Art
[0002] The content supervision of alliance chain is divided according to the organizational structure and the mode of implementation. Blockchain can be divided into three types: public chain, alliance chain and private chain. Among them, the nodes in the public chain are completely equal, and the nodes' ability to manage information is extremely limited; the nodes in the private chain are strictly restricted, and the write permission is controlled by a certain organization and institution.
[0003] The existing publication number CN108055274A is a method and system for encrypting and sharing data based on alliance chain storage, which proposes and solves the technical defects of existing data encryption methods and sharing. However, the trust building problem has gradually become a pain point in the industry. On the one hand, centralized institutions generally have high costs, low efficiency, and insecure data storage. On the other hand, it is difficult for groups that do not trust each other in the network to quickly establish trust at a low cost, which affects the efficient, orderly, and reliable conduct of digital economic activities. The supervisor is usually not a single node, but multiple nodes from different interest groups share the supervisory responsibility to prevent control by strong organizations and avoid single point failures. Therefore, there is a scenario where multiple supervisors need to know the private data of a transaction, which brings about the efficiency problem of session key sharing. For this reason, we propose a method for supervisors to share sensitive data in an alliance chain scenario based on group negotiation keys.
[0004] Embodiments of the invention
[0005] In response to the above problems, an embodiment of the present invention provides a method for regulators to share sensitive data in a consortium chain scenario based on group negotiated keys, which has the effect of enabling a group of regulators to share sensitive data in a flexible and efficient manner. In order to enable a group of regulators to share sensitive data in a consortium chain scenario in a flexible and efficient manner, the present invention is based on group negotiated keys to enable a set of regulator nodes to generate a shared key through negotiation. The shared key can be used in subsequent encryption and decryption processes. A session key is encrypted once with the shared key and can be distributed to multiple regulators after broadcasting.
[0006] The technical solution of an embodiment of the present invention is: a method for supervisors to share sensitive data in a consortium chain scenario based on group negotiation keys, comprising the steps of:
[0007] S1: The authentication center generates system parameters and submits the relevant system parameters to the alliance chain;
[0008] S2: The regulator group joins the alliance chain network and completes their own key registration and generation based on the system parameters and other information on the chain, and then submits public information such as public keys and registration identification information to the alliance chain;
[0009] S3: Each regulator obtains the public information from the alliance chain, calculates the corresponding broadcast information and uploads it to the chain, and saves the private message value locally;
[0010] S4: Each supervisor forms a key generation matrix with the broadcast messages of the group members, and after verifying the integrity and correctness of the public messages, calculates the shared group encryption key and the respective group decryption keys;
[0011] S5: Ordinary users agree on a session key to encrypt sensitive data in the transaction. If the group of regulators requires sensitive data in the transaction, the session key is encrypted with the group encryption key and broadcast to the blockchain network. Each regulator can decrypt it with their own group decryption key to obtain the session key and finally obtain the sensitive data.
[0012] In a further technical solution, step S1 includes the following sub-steps:
[0013] S1.1: Build a consortium chain network;
[0014] S1.2: The authentication center generates relevant system parameters params based on the bilinear pairing of the elliptic curve group;
[0015] S1.3: The authentication center submits the relevant system parameters params to the alliance chain.
[0016] In a further technical solution, step S2 includes the following sub-steps:
[0017] S2.1: n regulators who need to obtain sensitive data of a transaction form a group U = {u1,u2,…,u n}, join the alliance chain network built in step S1;
[0018] S2.2: Regulator u i For example, first obtain the system parameters issued by the authentication center on the chain, and then combine it with the identity information ID randomly selected by yourself i and a random number x i Calculate your own public and private key pair (pk i ,sk i ), which is expressed as follows:
[0019] pk i =(Q i ,P i ),sk i =(Di ,x i )
[0020] Where Q i By ID i And system parameters params are calculated, D i By Q i And params calculated, P i By x i Calculated with params;
[0021] S2.3: Regulator u i For example, after completing key registration and generation, submit the public key, registration identification information and other public content to the chain, and save your own private key and other private information locally;
[0022] S2.4: All supervisors in the group perform S2.2 to S2.3.
[0023] In a further technical solution, step S3 specifically includes the following sub-steps:
[0024] S3.1: All supervisors select common session state information theta;
[0025] S3.2: Taking the regulator as an example, first select a random number, then obtain the public information of other users in the group from the chain, and combine the system parameter params and session state information theta, all users calculate the broadcast information s i,j (1≤j≤n) and R i ;
[0026] S3.3: With the regulator R i For example, R i The message value is stored secretly locally, and the message list σ i =(R i ,s i,1 ,s i,2 ,…,s i,n(i≠j) ) is stored on the chain;
[0027] S3.4: All supervisors in the group execute S3.2 to S3.3.
[0028] In a further technical solution, step S4 specifically includes the following sub-steps:
[0029] S4.1: Taking the supervisor as an example, the broadcast message list on the chain is read according to the registration identification information of each user in the group, and a key generation matrix is formed;
[0030] S4.2: Taking the regulator as an example, first verify the integrity and correctness of the broadcast message obtained. If the verification is correct, then generate the key matrix and its own private key and private message value s i,i The group encryption key GEK is calculated using the same information i and group decryption key GDK i ;
[0031] S4.3: All supervisors in the group execute S4.1 to S4.2.
[0032] The group encryption key GEK of all supervisors i(1≤i≤n) The same group decryption key GDK i(1≤i≤n) Each is different.
[0033] In a further technical solution, step S5 specifically includes the following sub-steps:
[0034] S5.1: A transaction is to be conducted between ordinary users, and a session key is mutually agreed upon. The sensitive data in the transaction is encrypted with the session key. The transaction including the plaintext and ciphertext parts is submitted to the consortium chain;
[0035] S5.2: The regulatory group makes regulatory requirements for the transaction and sends the group encryption key to the initiator of the transaction;
[0036] S5.3: After the initiator of the transaction obtains the group encryption key, he encrypts the session key with the group key and broadcasts it to the blockchain network;
[0037] S5.4: Each supervisor uses his or her own group decryption key to obtain the session key, and combines it with the transaction data on the chain to decrypt the completed transaction data including the plaintext and the decrypted ciphertext.
[0038] The beneficial effects of the embodiments of the present invention are:
[0039] 1. The embodiment of the present invention proposes a blockchain with the characteristics of decentralization, difficulty in tampering, and traceability. It can realize the secure sharing of ledger data in an open network environment without centralized authorization by using data encryption, timestamps, distributed consensus, and economic incentives;
[0040] 2. The embodiment of the present invention proposes that nodes and on-chain data need to be reasonably supervised under the premise of protecting privacy, so as to ensure the healthy and sustainable development of the blockchain industry;
[0041] 3. The embodiment of the present invention proposes that the alliance chain retains the decentralized and tamper-resistant characteristics of the blockchain on the one hand, and on the other hand has an access mechanism and a role similar to that of a regulator to intervene in the storage of transaction data, so it is more in line with the needs of content supervision of various applications based on blockchain technology in the current network environment;
[0042] 4. An embodiment of the present invention proposes that transaction sensitive data is encrypted by a session key agreed upon by transaction-related parties. Each regulator forms a group and generates a common group encryption key and their own group decryption key. The session key will be encrypted once by the group encryption key and broadcast to the blockchain network. Each regulator can use its own group decryption key to obtain the session key, and then use the session key to decrypt the transaction sensitive data, thereby realizing the transaction ciphertext authorization process. BRIEF DESCRIPTION OF THE DRAWINGS
[0043] Figure 1 It is a flow chart of a method for supervisors to share sensitive data in a consortium chain scenario based on group negotiation keys according to the present invention;
[0044] Figure 2 This is the transaction sensitive data authorization scenario described in the present invention. DETAILED DESCRIPTION
[0045] The embodiments of the present invention are further described below in conjunction with the accompanying drawings.
[0046] Embodiment 1:
[0047] The present invention proposes a method for supervisors to share sensitive data in a consortium chain scenario based on group negotiation keys. The flow chart is as follows: Figure 1 As shown, node P1 and node P2 conduct a transaction, and the specific transaction information is divided into a plain text part D1 and a cipher text part D2, wherein D2 is encrypted by a session key agreed upon by P1 and P2.
[0048] The method of the present invention comprises the following steps:
[0049] S1: The authentication center generates system parameters and submits the relevant system parameters to the alliance chain;
[0050] S2: The regulator group joins the alliance chain network and completes their own key registration and generation based on the system parameters and other information on the chain, and then submits public information such as public keys and registration identification information to the alliance chain;
[0051] S3: Each regulator obtains the public information from the alliance chain, calculates the corresponding broadcast information and uploads it to the chain, and saves the private message value locally;
[0052] S4: Each supervisor forms a key generation matrix with the broadcast messages of the group members, and after verifying the integrity and correctness of the public messages, calculates the shared group encryption key and the respective group decryption keys;
[0053] S5: Ordinary users agree on a session key to encrypt sensitive data in the transaction. If the regulator group requires access to sensitive data in the transaction, the session key is encrypted with the group encryption key and broadcast to the blockchain network.
[0054] In Embodiment 1, a shared key can be generated through negotiation, and the shared key can be used in subsequent encryption and decryption processes. A session key is encrypted once with the shared key and can be distributed to multiple regulators after broadcasting.
[0055] Embodiment 2:
[0056] The present invention provides a method for supervisors to share sensitive data in a consortium chain scenario based on group negotiation keys. The transaction sensitive data authorization scenario discussed is as follows: Figure 2 As shown, there are n supervisors {u1,u2,…,u n}, each supervisor needs to obtain the session key used to encrypt the sensitive data D2.
[0057] Specifically, the present invention has the following steps:
[0058] S1: The authentication center generates system parameters and submits the relevant system parameters to the alliance chain;
[0059] The sub-steps are:
[0060] S1.1: Build a consortium chain network;
[0061] S1.2: The authentication center generates relevant system parameters params based on the bilinear pairing of the elliptic curve group;
[0062] S1.3: The authentication center submits the relevant system parameters params to the alliance chain.
[0063] S2: The regulator group joins the alliance chain network and completes their own key registration and generation based on the system parameters and other information on the chain, and then submits public information such as public keys and registration identification information to the alliance chain;
[0064] The sub-steps are:
[0065] S2.1: n regulators who need to obtain sensitive data of a transaction form a group U = {u1,u2,…,u n}, join the alliance chain network built in step S1;
[0066] S2.2: Regulator ui For example, first obtain the system parameters issued by the authentication center on the chain, and then combine it with the identity information ID randomly selected by yourself i and a random number x i Calculate your own public and private key pair (pk i ,sk i ), which is expressed as follows:
[0067] pk i =(Q i ,P i ),sk i =(D i ,x i )
[0068] Where Q i By ID i And system parameters params are calculated, D i By Q i And params calculated, P i By x i Calculated with params;
[0069] S2.3: Regulator u i For example, after completing key registration and generation, submit the public key, registration identification information and other public content to the chain, and save your own private key and other private information locally;
[0070] S2.4: All supervisors in the group perform S2.2 to S2.3.
[0071] S3: Each regulator obtains the public information from the alliance chain, calculates the corresponding broadcast information and uploads it to the chain, and saves the private message value locally;
[0072] The sub-steps are:
[0073] S3.1: All supervisors select common session state information theta;
[0074] S3.2: Taking the regulator as an example, first select a random number, then obtain the public information of other users in the group from the chain, and combine the system parameter params and session state information theta, all users calculate the broadcast information s i,j (1≤j≤n) and R i ;
[0075] S3.3: With the regulator R i For example, R i The message value is stored secretly locally, and the message list σ i =(R i ,s i,1 ,si,2 ,…,s i,n(i≠j) ) is stored on the chain;
[0076] S3.4: All supervisors in the group execute S3.2 to S3.3.
[0077] S4: Each supervisor forms a key generation matrix with the broadcast messages of the group members, and after verifying the integrity and correctness of the public messages, calculates the shared group encryption key and the respective group decryption keys;
[0078] The sub-steps are:
[0079] S4.1: Taking the supervisor as an example, the broadcast message list on the chain is read according to the registration identification information of each user in the group, and a key generation matrix is formed;
[0080] S4.2: Taking the regulator as an example, first verify the integrity and correctness of the broadcast message obtained. If the verification is correct, then generate the key matrix and its own private key and private message value s i,i The group encryption key GEK is calculated using the same information i and group decryption key GDK i ;
[0081] S4.3: All supervisors in the group execute S4.1 to S4.2.
[0082] The group encryption key GEK of all supervisors i(1≤i≤n) The same group decryption key GDK i(1≤i≤n) Each is different.
[0083] S5: Ordinary users agree on a session key to encrypt sensitive data in the transaction. If the regulator group requires sensitive data in the transaction, the session key is encrypted with the group encryption key and broadcast to the blockchain network. Each regulator can decrypt it with their own group decryption key to obtain the session key and finally obtain the sensitive data.
[0084] The sub-steps are:
[0085] S5.1: A transaction is to be conducted between ordinary users, and a session key is mutually agreed upon. The sensitive data in the transaction is encrypted with the session key. The transaction including the plaintext and ciphertext parts is submitted to the consortium chain;
[0086] S5.2: The regulatory group makes regulatory requirements for the transaction and sends the group encryption key to the initiator of the transaction;
[0087] S5.3: After the initiator of the transaction obtains the group encryption key, he encrypts the session key with the group key and broadcasts it to the blockchain network;
[0088] S5.4: Each supervisor uses his or her own group decryption key to obtain the session key, and combines it with the transaction data on the chain to decrypt the completed transaction data, including the plaintext and the decrypted ciphertext.
[0089] Embodiment 2 is more complete than embodiment 1, and each supervisor can use his own decryption key to decrypt, obtain the session and obtain sensitive data.
[0090] The above embodiments only express the specific implementation methods of the embodiments of the present invention, and the descriptions thereof are relatively specific and detailed, but they cannot be understood as limiting the patent scope of the embodiments of the present invention. It should be pointed out that, for ordinary technicians in this field, several variations and improvements can be made without departing from the concept of the embodiments of the present invention, and these all belong to the protection scope of the embodiments of the present invention.
Claims
1. A method for supervisors to share sensitive data in a consortium chain scenario based on group negotiation keys, characterized in that: Includes steps: S1: The authentication center generates system parameters and submits them to the alliance chain network; S2: The regulator group joins the alliance chain network and completes their own key registration and generation according to the system parameter information on the chain, and then submits the public key and registration identification information to the alliance chain; S3: Each regulator obtains the public information from the alliance chain, calculates the corresponding broadcast information and uploads it to the chain, and saves the private message value locally; S4: Each supervisor forms a key generation matrix with the broadcast messages of group members, and after verifying the integrity and correctness of the public messages, calculates the shared group encryption key and their own group decryption key; S5: Ordinary users agree on a session key to encrypt sensitive data in the transaction. The regulator group requires sensitive data in the transaction. The session key is encrypted with the group encryption key and broadcast to the blockchain network. Each regulator decrypts it with their own group decryption key to obtain the session key and finally obtain the sensitive data. The step S1 comprises the following sub-steps: S1.1: Build a consortium chain network; S1.2: The authentication center generates system parameters params based on the bilinear pairing of the elliptic curve group; S1.3: The authentication center submits the system parameters params to the alliance chain network; The step S2 comprises the following sub-steps: S2.1: n regulators who need to obtain sensitive data of a transaction form a group U = {u1,u2,…,u i ,…,u n }, join the alliance chain network built in step S1; S2.2: Each supervisor u i Perform the following steps. First, obtain the system parameter params published by the authentication center on the chain, and then combine it with the identity information ID you randomly selected. i and a random number x i Calculate your own public and private key pair (pk i ,sk i ), which is expressed as follows: pk i =(Q i ,P i ),sk i =(D i ,x i ) Where Q i By ID i And system parameters params calculated, D i By Q i And params calculated, P i By x i Calculated with params; S2.3: Each supervisor u i Perform the following steps. After completing key registration and generation, submit the public key and registration identification information to the chain, and save your private key privacy information locally; S2.4: All supervisors in the group perform S2.2 to S2.3 operations; The step S3 specifically includes the following sub-steps: S3.1: All supervisors select common session state information theta; S3.2: Each regulator u i Perform the following steps. First, select a random number. Then, obtain the public information of other users in the group from the chain. Combined with the system parameter params and the session status information theta, all users calculate the broadcast information s i,j and broadcast information R i , 1≤j≤n; S3.3: Each supervisor u i Perform the following steps to save the private message value locally and write the message list σ i =(R i ,s i,1 ,s i,2 ,…,s i,n ) is stored on the chain, i≠j; S3.4: All supervisors in the group execute S3.2 to S3.
3.
2. According to claim 1, a method for supervisors to share sensitive data in a consortium chain scenario based on group negotiation keys is characterized in that: The step S4 specifically includes the following sub-steps: S4.1: Each supervisor u i Perform the following steps to read the broadcast message list on the chain according to the registration identification information of each user in the group and form a key generation matrix; S4.2: Each supervisor u i Perform the following steps. First, verify the integrity and correctness of the broadcast message. If the verification is correct, generate the key matrix and your own private key and private message value s. i,i The information is calculated to obtain the group encryption key GEK i and group decryption key GDK i ; S4.3: All supervisors in the group perform S4.1 to S4.2; The group encryption key GEK of all supervisors i are the same, 1≤i≤n, group decryption key GDK i Each is different, 1≤i≤n.
3. According to claim 1, a method for supervisors to share sensitive data in a consortium chain scenario based on group negotiation keys is characterized in that: The step S5 specifically includes the following sub-steps: S5.1: A transaction is to be conducted between ordinary users, and a session key is mutually agreed upon. The sensitive data in the transaction is encrypted with the session key. The transaction including the plaintext and ciphertext parts is submitted to the consortium chain; S5.2: The regulatory group makes regulatory requirements for the transaction and sends the group encryption key to the initiator of the transaction; S5.3: After the initiator of the transaction obtains the group encryption key, he encrypts the session key with the group encryption key and broadcasts it to the blockchain network; S5.4: Each supervisor uses his or her own group decryption key to obtain the session key, and combines it with the transaction data on the chain to decrypt the completed transaction data including the plaintext and the decrypted ciphertext.
Citation Information
Patent Citations
Encryption and sharing method and system based on alliance chain storage data
CN108055274A
Asymmetric group key negotiation method based on block chain
CN110266482A
Alliance chain privacy protection method based on group signature and homomorphic encryption
CN111654363A