IP Library › Granted Patent US 11,777,745
Granted Patent B2
US 11,777,745 · App. 17/885,556 · Granted Oct 3, 2023

Cloud-side collaborative multi-mode private data circulation method based on smart contract

Inventors: Feng Gao (Zhejiang, CN); Wenyuan Bai (Zhejiang, CN)
Assignee: Zhejiang Lab
H04L9/3268H04L9/30H04L9/50
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 11,777,745
App. No.
17/885,556
Granted
Oct 3, 2023
Kind
B2
Abstract

The present invention discloses a cloud-side collaborative multi-mode private data circulation method based on a smart contract, including: S 1 , a system is initialized; S 2 , the original data are encrypted into private data, an encryption certificate z′ for storage is generated, and z′ includes metadata and a data certificate key′; S 3 , the DO calls a smart contract program to realize uplink of the encryption certificate z′ and releases z′ to a block chain through a smart contract, wherein the smart contract is open to all user accounts; S 4 , rapid data circulation is realized: when DO releases the data certificate, DU has been identified, a DU's account ID DU is set through an access policy, the DU obtains an encryption key for data access by executing a smart contract and a key algorithm, private data are obtained through metadata and decrypted to obtain a plaintext; and S 5 , the data circulation is confirmed.

Claims (27)

1. A cloud-side collaborative multi-mode private data circulation method based on a smart contract, comprising:

initializing a system:

initializing, by the system, a key algorithm of a Key-Policy as a Service (KaaS) to obtain a public system key (PSK) and a master secret key (MSK); and

creating, by the system, a user account for each user, wherein the user account comprises a user account identifier (ID), a corresponding public key ID pub-key , a private key ID pri-key , a data owner (DO), a data user (DU), and a user profile comprising an account ID SC , a public key SC pub-key , and a private key SC pri-key ;

encrypting, by the DO, original data into private data and generating an encryption certificate, wherein the encryption certificate comprises metadata and a data certificate key:

applying to the KaaS, by the DO, for the PSK; and

obtaining, by the DO, the data certificate key according to the PSK, an encryption key, and an access policy, comprising:

generating the metadata based on the original data to form the private data by generating a random number as the encryption key of the original data and encrypting the original data through the encryption key to form the private data, and storing the private data in a cloud storage space; and

generating the access policy based on the user account ID and generating the data certificate key based on the key algorithm according to a key of a message to be encrypted, the PSK and the access policy;

uploading, by the DO, the encryption certificate to a block chain by using a smart contract which is accessible to all user accounts;

determining, by the DO, a data circulation in response to identifying the DU, wherein the determining comprises:

in response to releasing the data certificate key, setting an account ID DU through the access policy, wherein the DU obtains the encryption key by executing the smart contract and the key algorithm, and the DU obtains the private data through the metadata and decrypts the private data to obtain a plaintext, comprising:

obtaining the encryption certificate by executing the smart contract for the account ID DU ;

sending a request to the KaaS through the smart contract to apply for a user secret key (USK), wherein the USK is generated by the KaaS based on the key algorithm according the PSK, the MSK, and the account ID DU , and the USK is encrypted by a public key DU pub-key of the DU and uploaded to a block chain through the smart contract which is only accessible to the DU;

executing the smart contract to obtain the encrypted USK and obtaining the USK from the encrypted USK through a private key DU pri-key of the DU by the DU;

decrypting the data certificate key in the encryption certificate by the USK to obtain the encryption key; and

obtaining the private data through the metadata in the encryption certificate and decrypting the private data through the encryption key to obtain the original data;

determining, by the DO, the data circulation in response to not identifying the DU and releasing the data certificate key, wherein the DU retrieves the block chain, browses the metadata, and publishes a file reading request through the smart contract, comprising:

calling the smart contract, retrieving the block chain, and browsing the metadata;

sending an access request to the DO through the smart contract, wherein the DO submits a policy with a time attribute to the block chain, the time attribute is associated with a current contract execution time t, a circulation cycle start time start , and a circulation cycle ending time end , wherein the user profile is used to execute the smart contract, obtain a policy from the block chain, verify a validity of the policy, and informs the DU if the validity is fail, wherein the USK is generated by the KaaS based on the key algorithm according the PSK, the MSK, and the access policy, and the USK is encrypted by the public key DU pub-key of the DU and uploaded to the block chain through the smart contract which is only accessible to the DU; and

obtaining the encryption key based on the key algorithm according to the PSK, the USK, and the data certificate key through decryption as long as the account ID DU satisfies an enabling characteristic in the access policy within an effective time limit, obtaining the private data through the metadata in the encryption certificate, and decrypting the private data through the encryption key to obtain the original data, wherein the data circulation is completed if an authority passes a review after the DO executes the smart contract; and

submitting a transaction certificate of the data circulation and confirming that the data circulation is completed by the DO.

2. The cloud-side collaborative multi-mode private data circulation method based on the smart contract of claim 1 , wherein the PSK and the MSK are generated from a parameter γ associated with the access policy, and therein the access policy is further associated with an attribute space U.

3. The cloud-side collaborative multi-mode private data circulation method based on the smart contract of claim 1 , wherein the original data are encrypted into the private data by the DO and saved on a cloud side, and the encryption certificate for cloud storage is generated, wherein the DU obtains the private data from the cloud side through the metadata and decrypts the private data to obtain the plaintext.

4. The cloud-side collaborative multi-mode private data circulation method based on the smart contract of claim 1 , wherein the obtained USK is saved by the DU, wherein whether the USK based on the key algorithm is saved is checked in the account ID DU , if the USK is not saved, a request is sent to the KaaS by the DU through the smart contract to apply for the USK; if the USK is saved, the decrypting the data certificate key in the encryption certificate by the USK to obtain the encryption key is executed by the DU.

5. The cloud-side collaborative multi-mode private data circulation method based on the smart contract of claim 1 , wherein the policy is associated with the account ID DU and the account ID SC .

6. The cloud-side collaborative multi-mode private data circulation method based on the smart contract of claim 1 , wherein the policy is associated with the account ID SC .

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 14, 2022
From: GAO, FENG; BAI, WENYUAN
To: ZHEJIANG LAB
Reel/Frame 060802/0035 →
Priority Claims (1)
CN 202110886663.8 · Aug 3, 2021 · national
Continuity (2)
Continuation PCTCN2022091909 · May 10, 2022
Related Publication 20230041862A1 · Feb 9, 2023