Delivery method and system supporting transaction fallback and ownership synchronous updating, and medium

Abstract

The invention discloses a delivery method and system supporting transaction rollback and ownership synchronous updating, and a medium, and belongs to the technical field of data security. The exchange is composed of a storage management server, an ownership management server and a key management server. The storage management server stores the data ciphertext for a long time; and under the assistance of the ownership management server, the key management server provides a key use service for a legal user in a trusted execution environment and trustingly deletes the use permission of the buyer when the service life expires so as to realize cross-domain extension access control of the data seller to the data. Core functions such as key management, data encryption and decryption, data use and the like are performed in an isolated safe environment, a buyer needs to legally use a key and data according to a strategy, and the key and data cache are immediately cleared after the data is used, so that the data is prevented from being illegally held, used and even resold, and the risk of data leakage and abuse is remarkably reduced.

Description

Technical Field

[0001] The present invention relates to the field of data security technology, and in particular to a delivery method, system and medium that support transaction rollback and synchronous update of ownership. Background Art

[0002] The orderly circulation of data elements is the foundation for the high-quality development of the digital economy. The data trading platform facilitates the orderly circulation of data elements. At present, my country's data trading platform is in the early stages of construction and still has many shortcomings. Specifically, in actual data trading, especially for data sets, data trading usually adopts the method of off-platform delivery, lacks the function of on-platform delivery, resulting in low delivery efficiency, cumbersome operation, lack of unified standards, and the authenticity, reliability and regulatory nature of data transactions are difficult to guarantee. Secondly, in actual data trading, data trading rollback is not supported. The simple use of traditional e-commerce transaction rollback methods will make it impossible to return the data ownership synchronously when the data transaction is rolled back, and lack of functions such as data verifiable deletion, resulting in unclear data ownership. After the transaction is rolled back, the buyer can claim that he has deleted the purchased data, but privately retains a copy of the data, making it difficult for the data seller to protect his own legitimate rights and interests.

[0003] The present invention designs a reliable data delivery method within the field that supports transaction rollback and synchronous update of ownership, thereby achieving orderly circulation of data elements and ensuring that the rights and interests of data delivery stakeholders are not infringed. Summary of the invention

[0004] The purpose of the present invention is to overcome the deficiencies of the prior art and to provide a delivery method, system and medium that support transaction rollback and synchronous update of ownership.

[0005] The object of the present invention is achieved through the following technical solutions: The first aspect of the present invention provides: a delivery method that supports transaction rollback and synchronous update of ownership, the exchange includes a storage management server, an ownership management server and a key management server; specifically includes the following steps: S1: Generate system public parameters based on security parameters; S2: User registers on the exchange; S3: The seller encrypts the data and uploads the ciphertext to the exchange. The exchange stores it on the storage management server and uploads the key to the exchange's key management server. The key management server uses the trusted execution environment to store the key and the corresponding key usage policy for a long time. S4: The seller submits a request to the exchange to modify the ownership, and the exchange modifies the ownership on the ownership management server; S5: The seller accesses the key management server and modifies the key usage policy so that the buyer has the right to use the key within the usage period; S6: When using data, the buyer accesses the key management server to obtain the key and uses the data in a trusted execution environment and under policy restrictions; S7: If the buyer cancels the transaction, trusted deletion of data is achieved based on the trusted execution environment and policy.

[0006] Preferably, the system common parameters are: ; in p is a prime number in the finite field defined by the elliptic curve, G represents the 𝑛-order additive cyclic group of points on the elliptic curve, 𝑔 is the generator of 𝐺, 𝑛 is the order of the generator 𝑔, H ( ) is a hash function from G Map to Z p , Enc ( )and Dec ( ) is a pair of public key encryption algorithms, E ( )and D ( ) is a pair of symmetric encryption algorithms, Sig ( )and Ver ( ) is a pair of digital signature algorithms; Exchange ownership management server RM Create a Equity Table l The table is used to record the owner and user of each piece of data. DE and Key Management Server KM Generate a first key pair for encryption and decryption bound to the identity and a second key pair for signature verification , and the public key used for encryption epk DE , epk KM and for signature verification spk DE , spk KM Public; in Key Manager KM Use Intel's SGX technology to generate a secure zone locally enclave KM , ensuring long-term trusted storage of keys and allowing users u Following the right strategy policy KM Get the key; in the user u Use Intel's SGX technology to generate a secure zone locally enclave u , ensuring that the key is discarded after use and according to the policy policyu Usage data; in Key Manager KM and users u There are also Quoting Enclave , Quoting Enclave Is a trusted special enclave , which is used to apply enclave Provided to prove enclave The report that the code and data are correctly instantiated in the code is converted into a structure that can be verified externally, called Quote .

[0007] Preferably, the specific steps of S1 are as follows: 1) Each user u Register at the exchange to obtain a user identity ID ; 2) Each user u Generate the first key pair for encryption and decryption and a second key pair for signature verification , the public key used for encryption epk u and for signature verification spk u Upload to the exchange, the exchange will epk u and spk u The corresponding user identity ID The binding is stored at the storage management server and made public.

[0008] Preferably, the specific steps of S3 are as follows: 1) The seller randomly generates a symmetric encryption key locally ek , using a symmetric encryption key ek Data data Encrypt to get ciphertext C 1= E ( ek , data ), and the ciphertext C 1Sign and get the ciphertext signature , and then the ciphertext C 1 and ciphertext signature Upload to the exchange, and the exchange will store it on the storage management server; 2) The seller randomly generates a private key for the Diffie-Hellman (DH) key exchange protocol locally , and then calculate the public key , generate a timestamp of the current time tag 1. Use a key manager KM The encrypted public key epkKM ,right ppk s and tag 1 Encrypt to get ciphertext C 2= , using your own signature public key ssk s Ciphertext C 2Sign and get the signature , to the key manager KM Request service, send ciphertext C 2 and signature Send to KM And to KM Issue a challenge to verify enclave KM Correct instantiation of ; 3) KM After receiving the request, first use Verify the signature , calculated after verification get ppk s and tag 1, tag 1Access the Ownership Manager after verification RM Check if the seller is the owner of the modified data, and if so, accept the challenge. enclave KM Randomly generate the private key for the DH key exchange protocol , and then calculate the public key , generate a timestamp of the current time tag 2. Use the seller's public key to the public key ppk KM , Timestamp tag 2 Calculate the ciphertext ,right C 3Sign with your own private key to get the signature ,calculate Get the session key ck 1. Generate a report report , containing the ciphertext C 3. Signature , enclave KM identity and status information; 4) KM Will report Send to Quoting Enclave Authentication within and using hardware-specific ECDSA The private key signs it and generates Quote ; 5) The generated Quote Sent to Intel's remote attestation serviceIAS , IAS right Quote Perform verification and generate a verification report. KM Send verification report to seller; 6) The seller receives and checks the verification report to confirm KM on enclave Is it initialized correctly and running safely? After confirming, first use Verify the signature , calculated after verification get ppk KM and tag 2, tag 2 Calculation after verification Get the session key ck 1. Generate key usage strategy policy ek , using the session key ck 1 pair of symmetric encryption keys ek and key usage policy policy ek Encrypt to get ciphertext Then use your own signature public key ssk s Ciphertext C 4Sign and get signature , the ciphertext C 4 and Signature Send to KM ; 7) KM First use Verify the signature After verification, enclave Use session keys ck 1 Calculation Get the symmetric encryption key ek and key usage policy policy ek ,exist enclave Medium- and long-term trusted storage of symmetric encryption keys ek and the corresponding key usage policy policy ek .

[0009] Preferably, the specific steps of S4 are as follows: 1) The seller generates a timestamp of the current time tag 3. Use exchanges DE The encrypted public key epk DE , a request to modify the buyer to be the user of the purchased data request and timestamp tag3 Encrypt to get ciphertext , using your own signature public key ssk s Ciphertext C 5Sign and get signature , to the exchange DE Request service, send ciphertext C 5 and signature Send to DE ; 2) DE After receiving the request, first query the ownership management server RM Verify whether the seller is the owner of the modified data. Verify the signature , calculated after verification Get modification request request and tag 3. tag 3 After verification, the ownership management server RM According to the modification request request Modify the data ownership of the corresponding data, and generate the timestamp of the current time after the modification is completed tag 4. Modify the successful message response Encrypt with the seller's public key to get the ciphertext ,right C 6Sign with private key to get signature , the ciphertext C 6 and Signature Send to the seller; 3) After receiving the reply message, the seller first uses Verify the signature , calculated after verification Get a reply response and tag 4. tag 4View the response after verification response , and obtain the ownership modification result.

[0010] Preferably, the specific steps of S5 are as follows: 1) The seller generates a timestamp of the current time tag 5. Use a key manager KM The encrypted public key epk KM , to modify the key usage policy of the key that the buyer is authorized to use policy ek and timestamp tag 5 Encrypt to get ciphertext , using your own signature public key ssk s Ciphertext C7Sign and get signature , the ciphertext C 7 and Signature Send to KM ; 2) KM After receiving the request, first use Verify the signature , calculated after verification get policy ek and tag 5. tag 5 Access the Ownership Manager after verification RM Check whether the seller is the owner of the data key usage policy to be modified. If yes, enclave KM Update key usage policy policy ek After the modification is completed, a timestamp of the current time is generated tag 6. Modification results res Encrypt with the seller's public key to get the ciphertext ,right C 8Sign with private key to get signature , the ciphertext C 8 and Signature Send to the seller; 3) After receiving the reply message, the seller first uses Verify the signature , calculated after verification Get the result res and tag 6. tag 6 Check the results after verification res , and obtain the key usage policy update result.

[0011] Preferably, the specific steps of S6 are as follows: 1) The buyer downloads data from the storage management server data The corresponding ciphertext C 1 and digital signature , calculated using the seller's signature public key Verify the signature , after verification, a timestamp of the current time is generated tag 7. Use a key manager KM The encrypted public key epk KM , using data encryption key ek Request request ek and timestamp tag 7 Encrypt to get ciphertext , using your own signature public keyssk b Ciphertext C 9Sign and get signature , the ciphertext C 9 and Signature Send to KM ; 2) KM After receiving the request, first use Verify the signature , calculated after verification get request ek and tag 7, tag 7 Access the Ownership Manager after verification RM Check whether the buyer is the legitimate user of the data key to be used. If yes, enclave KM Key Usage Policy policy ek Determine the buyer's key usage authority and randomly generate a private key for the DH key exchange protocol after the determination is completed , and then calculate the public key , generate a timestamp of the current time tag 8. Use the buyer’s public key to encrypt the ciphertext ,right C 10 Sign with private key to get signature , the ciphertext C 10 and signature Sent to the buyer and challenged to verify enclave b Correct instantiation of ; 3) After receiving the request, the buyer first uses Verify the signature , calculated after verification get rpk KM and tag 8. tag 8After verification, accept the challenge and enclave b Randomly generate the private key for the DH key exchange protocol , and then calculate the public key , generate a timestamp of the current time tag 9. Use your own public key to the public key rpk b , Timestamp tag 9Calculate the ciphertext ,right C 11 Sign with private key to get signature ,calculate Get the session key ck 2. Generate a report report , containing the ciphertext C 11 ,sign , enclave b identity and status information; 4) The buyer will report Send to Quoting Enclave Authentication and use ECDSA The private key signs it and generates Quote ; 5) The generated Quote Sent to Intel's remote attestation service IAS , IAS right Quote Verify and generate a verification report, which the buyer sends to KM ; 6) KM Receive and review verification reports to confirm the buyer's enclave Is it initialized correctly and running safely? After confirming, first use Verify the signature , calculated after verification get rpk b and tag 9. tag 9 Calculate after verification Get the session key ck 2. Use session key ck 2 pairs of symmetric encryption keys ek and key usage policy policy ek Encrypt to get ciphertext Then use your own private key ssk KM Ciphertext C 12 Sign Get Signature , the ciphertext C 12 and signature Send to the buyer; 7) The buyer first uses Verify the signature After verification, enclave Use session keys ck 2 Calculation Get the symmetric encryption key ek and key usage policy policy ek ,existenclave According to the key usage policy policy ek Trusted use of symmetric encryption keys ek .

[0012] Preferably, the specific steps of S7 are as follows: 1) After the buyer's application is approved, the exchange will RM Modify the data ownership of the corresponding data, revoke the buyer's use rights, and generate a timestamp of the current time after the modification is completed tag 10 , to revoke the certificate proof 1 Use the seller's public key to encrypt the ciphertext ,right C 13 Sign with private key to get signature , the ciphertext C 13 and signature Send to the seller; 2) The seller receives the message first Verify the signature , calculated after verification Get revocation certificate proof 1 and tag 10 , tag 10 After verification, keep the revocation certificate properly proof 1; 3) The seller generates a timestamp of the current time tag 11 , using the key manager KM The encrypted public key epk KM , request to revoke the buyer's key usage rights rev and timestamp tag 11 Encrypt to get ciphertext , using your own signature public key ssk s Ciphertext C 14 Sign Get Signature , the ciphertext C 14 and signature Send to KM ; 4) KM After receiving the request, first use Verify the signature , calculated after verification get rev and tag11 , tag 11 Access the Ownership Manager after verification RM Check whether the seller is the data owner and whether the buyer has been revoked of the right to use the data. enclave KM Update key usage policy policy ek After the modification is completed, a timestamp of the current time is generated tag 12 , to revoke the certificate proof 2. Encrypt the ciphertext using the seller's public key ,right C 15 Sign with private key to get signature , the ciphertext C 15 and signature Send to the seller; 5) After receiving the reply message, the seller first uses Verify the signature , calculated after verification Get revocation certificate proof 2 and tag 12 , tag 12 After verification, keep the revocation certificate properly proof 2. Data key from the buyer ek In a trusted execution environment and based on policy policy Use, so that after each use the data key ek The decrypted data will be discarded and the decrypted data will be strictly restricted from leaving the domain in plain text, so the buyer needs to re-register the key manager every time he uses the data. KM Requesting a data key ek By modifying the ownership and key usage policy on the key manager, the buyer is no longer entitled to the data key. ek , achieving trusted deletion of data after the buyer cancels the transaction.

[0013] The second aspect of the present invention provides: a delivery system supporting transaction rollback and synchronous update of ownership, which is used to implement any of the above-mentioned delivery methods supporting transaction rollback and synchronous update of ownership, including: A parameter generation module, used to generate system common parameters according to security parameters; Registration module, used to register on the exchange; The encryption module is used to encrypt data and upload the ciphertext to the exchange, which stores it on the storage management server and uploads the key to the key management server of the exchange. The key management server uses the trusted execution environment to store the key and the corresponding key usage policy in a long-term trusted manner; The ownership modification module is used to submit a request to the exchange to modify the ownership, and the exchange modifies the ownership at the ownership management server; A key permission modification module is used to access the key management server and modify the key usage policy so that the buyer has the right to use the key within the usage period; A key acquisition module is used to access a key management server to obtain a key when using data, and use data in a trusted execution environment and under policy restrictions; Trusted deletion module, used to implement trusted deletion of data based on the trusted execution environment and policy when the buyer cancels the transaction; The exchange includes a storage management server, a property management server and a key management server.

[0014] The third aspect of the present invention provides: a computer-readable storage medium, wherein the computer-readable storage medium stores computer-executable instructions, and when the computer-executable instructions are loaded and executed by a processor, any of the above-mentioned delivery methods supporting transaction rollback and synchronous update of ownership is implemented.

[0015] The beneficial effects of the present invention are: 1) Intel Software Guard Extensions (SGX) is used to provide hardware-level isolation protection for data. Core functions such as data encryption and decryption operations and key management are performed in an isolated secure environment. Keys and data are used legally and compliantly in accordance with policies. Keys and data caches are cleared immediately after data use to prevent data from being illegally held, used, or even resold, significantly reducing the risk of data leakage and abuse. In addition, the use of SGX reduces the trust cost of data owners in key management servers, so that data keys can still be securely stored even in untrusted environments. The trust model can be reduced to semi-trusted, which ensures that exchanges cannot illegally obtain user data keys and then obtain user data for profit.

[0016] 2) At each stage of data delivery, data ownership information is updated synchronously to ensure that data ownership is consistent with the actual transaction status, improve transaction transparency, provide a reliable basis for disputes, and reduce legal disputes caused by data delivery. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] Figure 1 The present invention is a flowchart of an embodiment of the data delivery method. DETAILED DESCRIPTION

[0018] The technical solution of the present invention will be clearly and completely described below in conjunction with the embodiments. Obviously, the described embodiments are only part of the embodiments of the present invention, rather than all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative work are within the scope of protection of the present invention.

[0019] See also Figure 1 The present invention provides a technical solution: The first aspect of the present invention provides: a delivery method that supports transaction rollback and synchronous update of ownership, the exchange includes a storage management server, an ownership management server and a key management server; specifically includes the following steps: S1: Generate system public parameters based on security parameters; S2: User registers on the exchange; S3: The seller encrypts the data and uploads the ciphertext to the exchange. The exchange stores it on the storage management server and uploads the key to the exchange's key management server. The key management server uses the trusted execution environment to store the key and the corresponding key usage policy for a long time. S4: The seller submits a request to the exchange to modify the ownership, and the exchange modifies the ownership on the ownership management server; S5: The seller accesses the key management server and modifies the key usage policy so that the buyer has the right to use the key within the usage period; S6: When using data, the buyer accesses the key management server to obtain the key and uses the data in a trusted execution environment and under policy restrictions; S7: If the buyer cancels the transaction, trusted deletion of data is achieved based on the trusted execution environment and policy.

[0020] In some embodiments, the system common parameters are: ; in p is a prime number in the finite field defined by the elliptic curve, G represents the 𝑛-order additive cyclic group of points on the elliptic curve, 𝑔 is the generator of 𝐺, 𝑛 is the order of the generator 𝑔, H ( ) is a hash function from G Map to Z p , Enc ( )and Dec ( ) is a pair of public key encryption algorithms, E ( )and D ( ) is a pair of symmetric encryption algorithms, Sig ( )and Ver ( ) is a pair of digital signature algorithms; Exchange ownership management serverRM Create a Equity Table l The table is used to record the owner and user of each piece of data. DE and Key Management Server KM Generate a first key pair for encryption and decryption bound to the identity and a second key pair for signature verification , and the public key used for encryption epk DE , epk KM and for signature verification spk DE , spk KM Public; in Key Manager KM Use Intel's SGX technology to generate a secure zone locally enclave KM , ensuring long-term trusted storage of keys and allowing users u Following the right strategy policy KM Get the key; in the user u Use Intel's SGX technology to generate a secure zone locally enclave u , ensuring that the key is discarded after use and according to the policy policy u Usage data; in Key Manager KM and users u There are also Quoting Enclave , Quoting Enclave Is a trusted special enclave , which is used to apply enclave Provided to prove enclave The report that the code and data are correctly instantiated in the code is converted into a structure that can be verified externally, called Quote .

[0021] In some embodiments, the S1 includes the following steps: 1) Each user u Register at the exchange to obtain a user identity ID ; 2) Each user u Generate the first key pair for encryption and decryption and a second key pair for signature verification , the public key used for encryption epk u and for signature verification spk u Upload to the exchange, the exchange will epku and spk u The corresponding user identity ID The binding is stored at the storage management server and made public.

[0022] In some embodiments, the S3 described above comprises the following specific steps: 1) The seller randomly generates a symmetric encryption key locally ek , using a symmetric encryption key ek Data data Encrypt to get ciphertext C 1= E ( ek , data ), and the ciphertext C 1Sign and get the ciphertext signature , and then the ciphertext C 1 and ciphertext signature Upload to the exchange, and the exchange will store it on the storage management server; 2) The seller randomly generates a private key for the Diffie-Hellman (DH) key exchange protocol locally , and then calculate the public key , generate a timestamp of the current time tag 1. Use a key manager KM The encrypted public key epk KM ,right ppk s and tag 1 Encrypt to get ciphertext C 2= , using your own signature public key ssk s Ciphertext C 2Sign and get the signature , to the key manager KM Request service, send ciphertext C 2 and signature Send to KM And to KM Issue a challenge to verify enclave KM Correct instantiation of ; 3) KM After receiving the request, first use Verify the signature , calculated after verification get ppk s and tag 1, tag 1Access the Ownership Manager after verification RM Check if the seller is the owner of the modified data, and if so, accept the challenge. enclave KM Randomly generate the private key for the DH key exchange protocol , and then calculate the public key , generate a timestamp of the current time tag 2. Use the seller's public key to the public key ppk KM , Timestamp tag 2 Calculate the ciphertext ,right C 3Sign with your own private key to get the signature ,calculate Get the session key ck 1. Generate a report report , containing the ciphertext C 3. Signature , enclave KM identity and status information; 4) KM Will report Send to Quoting Enclave Authentication within and using hardware-specific ECDSA The private key signs it and generates Quote ; 5) The generated Quote Sent to Intel's remote attestation service IAS , IAS right Quote Perform verification and generate a verification report. KM Send verification report to seller; 6) The seller receives and checks the verification report to confirm KM on enclave Is it initialized correctly and running safely? After confirming, first use Verify the signature , calculated after verification get ppk KM and tag 2, tag 2 Calculation after verification Get the session key ck 1. Generate key usage strategy policy ek , using the session key ck 1 pair of symmetric encryption keys ek and key usage policy policy ek Encrypt to get ciphertext Then use your own signature public key ssk s Ciphertext C 4Sign and get signature , the ciphertext C 4 and Signature Send to KM ; 7) KM First use Verify the signature After verification, enclave Use session keys ck 1 Calculation Get the symmetric encryption key ek and key usage policy policy ek ,exist enclave Medium- and long-term trusted storage of symmetric encryption keys ek and the corresponding key usage policy policy ek .

[0023] In some embodiments, the S4 comprises the following specific steps: 1) The seller generates a timestamp of the current time tag 3. Use exchanges DE The encrypted public key epk DE , a request to modify the buyer to be the user of the purchased data request and timestamp tag 3 Encrypt to get ciphertext , using your own signature public key ssk s Ciphertext C 5Sign and get signature , to the exchange DE Request service, send ciphertext C 5 and signature Send to DE ; 2) DE After receiving the request, first query the ownership management server RM Verify whether the seller is the owner of the modified data. Verify the signature , calculated after verification Get modification request request and tag 3. tag 3 After verification, the ownership management server RM According to the modification request request Modify the data ownership of the corresponding data, and generate the timestamp of the current time after the modification is completed tag 4. Modify the successful message response Encrypt with the seller's public key to get the ciphertext ,right C 6Sign with private key to get signature , the ciphertext C 6 and Signature Send to the seller; 3) After receiving the reply message, the seller first uses Verify the signature , calculated after verification Get a reply response and tag 4. tag 4View the response after verification response , and obtain the ownership modification result.

[0024] In some embodiments, the S5 described above comprises the following specific steps: 1) The seller generates a timestamp of the current time tag 5. Use a key manager KM The encrypted public key epk KM , to modify the key usage policy of the key that the buyer is authorized to use policy ek and timestamp tag 5 Encrypt to get ciphertext , using your own signature public key ssk s Ciphertext C 7Sign and get signature , the ciphertext C 7 and Signature Send to KM ; 2) KM After receiving the request, first use Verify the signature , calculated after verification get policy ek and tag 5. tag 5 Access the Ownership Manager after verification RM Check whether the seller is the owner of the data key usage policy to be modified. If yes, enclave KM Update key usage policy policy ek After the modification is completed, a timestamp of the current time is generated tag 6. Modification results res Encrypt with the seller's public key to get the ciphertext ,right C 8Sign with private key to get signature , the ciphertext C8 and Signature Send to the seller; 3) After receiving the reply message, the seller first uses Verify the signature , calculated after verification Get the result res and tag 6. tag 6 Check the results after verification res , and obtain the key usage policy update result.

[0025] In some embodiments, the S6 described above comprises the following specific steps: 1) The buyer downloads data from the storage management server data The corresponding ciphertext C 1 and digital signature , calculated using the seller's signature public key Verify the signature , after verification, a timestamp of the current time is generated tag 7. Use a key manager KM The encrypted public key epk KM , using data encryption key ek Request request ek and timestamp tag 7 Encrypt to get ciphertext , using your own signature public key ssk b Ciphertext C 9Sign and get signature , the ciphertext C 9 and Signature Send to KM ; 2) KM After receiving the request, first use Verify the signature , calculated after verification get request ek and tag 7, tag 7 Access the Ownership Manager after verification RM Check whether the buyer is the legitimate user of the data key to be used. If yes, enclave KM Key Usage Policy policy ek Determine the buyer's key usage authority and randomly generate a private key for the DH key exchange protocol after the determination is completed , and then calculate the public key , generate a timestamp of the current time tag 8. Use the buyer’s public key to encrypt the ciphertext ,right C 10 Sign with private key to get signature , the ciphertext C 10 and signature Sent to the buyer and challenged to verify enclave b Correct instantiation of ; 3) After receiving the request, the buyer first uses Verify the signature , calculated after verification get rpk KM and tag 8. tag 8After verification, accept the challenge and enclave b Randomly generate the private key for the DH key exchange protocol , and then calculate the public key , generate a timestamp of the current time tag 9. Use your own public key to the public key rpk b , Timestamp tag 9Calculate the ciphertext ,right C 11 Sign with private key to get signature ,calculate Get the session key ck 2. Generate a report report , containing the ciphertext C 11 ,sign , enclave b identity and status information; 4) The buyer will report Send to Quoting Enclave Authentication and use ECDSA The private key signs it and generates Quote ; 5) The generated Quote Sent to Intel's remote attestation service IAS , IAS right Quote Verify and generate a verification report, which the buyer sends to KM ; 6) KM Receive and review verification reports to confirm the buyer's enclave Is it initialized correctly and running safely? After confirming, first use Verify the signature , calculated after verification get rpk b and tag 9. tag 9 Calculate after verification Get the session key ck 2. Use session key ck 2 pairs of symmetric encryption keys ek and key usage policy policy ek Encrypt to get ciphertext Then use your own private key ssk KM Ciphertext C 12 Sign Get Signature , the ciphertext C 12 and signature Send to the buyer; 7) The buyer first uses Verify the signature After verification, enclave Use session keys ck 2 Calculation Get the symmetric encryption key ek and key usage policy policy ek ,exist enclave According to the key usage policy policy ek Trusted use of symmetric encryption keys ek .

[0026] In some embodiments, the S7 includes the following specific steps: 1) After the buyer's application is approved, the exchange will RM Modify the data ownership of the corresponding data, revoke the buyer's use rights, and generate a timestamp of the current time after the modification is completed tag 10 , to revoke the certificate proof 1 Use the seller's public key to encrypt the ciphertext ,right C 13 Sign with private key to get signature , the ciphertext C 13 and signature Send to the seller; 2) The seller receives the message first Verify the signature , calculated after verification Get revocation certificate proof 1 and tag 10 , tag 10 After verification, keep the revocation certificate properly proof 1; 3) The seller generates a timestamp of the current time tag 11 , using the key manager KM The encrypted public key epk KM , request to revoke the buyer's key usage rights rev and timestamp tag 11 Encrypt to get ciphertext , using your own signature public key ssk s Ciphertext C 14 Sign Get Signature , the ciphertext C 14 and signature Send to KM ; 4) KM After receiving the request, first use Verify the signature , calculated after verification get rev and tag 11 , tag 11 Access the Ownership Manager after verification RM Check whether the seller is the data owner and whether the buyer has been revoked of the right to use the data. enclave KM Update key usage policy policy ek After the modification is completed, a timestamp of the current time is generated tag 12 , to revoke the certificate proof 2. Encrypt the ciphertext using the seller's public key ,right C 15 Sign with private key to get signature , the ciphertext C 15 and signature Send to the seller; 5) After receiving the reply message, the seller first uses Verify the signature , calculated after verification Get revocation certificate proof 2 and tag 12, tag 12 After verification, keep the revocation certificate properly proof 2. Data key from the buyer ek In a trusted execution environment and based on policy policy Use, so that after each use the data key ek The decrypted data will be discarded and the decrypted data will be strictly restricted from leaving the domain in plain text, so the buyer needs to re-register the key manager every time he uses the data. KM Requesting a data key ek By modifying the ownership and key usage policy on the key manager, the buyer is no longer entitled to the data key. ek , achieving trusted deletion of data after the buyer cancels the transaction.

[0027] The second aspect of the present invention provides: a delivery system supporting transaction rollback and synchronous update of ownership, which is used to implement any of the above-mentioned delivery methods supporting transaction rollback and synchronous update of ownership, including: A parameter generation module, used to generate system common parameters according to security parameters; Registration module, used to register on the exchange; The encryption module is used to encrypt data and upload the ciphertext to the exchange, which stores it on the storage management server and uploads the key to the key management server of the exchange. The key management server uses the trusted execution environment to store the key and the corresponding key usage policy in a long-term trusted manner; The ownership modification module is used to submit a request to the exchange to modify the ownership, and the exchange modifies the ownership at the ownership management server; A key permission modification module is used to access the key management server and modify the key usage policy so that the buyer has the right to use the key within the usage period; A key acquisition module is used to access a key management server to obtain a key when using data, and use data in a trusted execution environment and under policy restrictions; Trusted deletion module, used to implement trusted deletion of data based on the trusted execution environment and policy when the buyer cancels the transaction; The exchange includes a storage management server, a property management server and a key management server.

[0028] The third aspect of the present invention provides: a computer-readable storage medium, wherein the computer-readable storage medium stores computer-executable instructions, and when the computer-executable instructions are loaded and executed by a processor, any of the above-mentioned delivery methods supporting transaction rollback and synchronous update of ownership is implemented.

[0029] The above is only a preferred embodiment of the present invention. It should be understood that the present invention is not limited to the form disclosed herein, and should not be regarded as excluding other embodiments, but can be used in various other combinations, modifications and environments, and can be modified within the scope of the concept described herein through the above teachings or the technology or knowledge of the relevant field. The changes and modifications made by those skilled in the art shall not deviate from the spirit and scope of the present invention, and shall be within the scope of protection of the claims attached to the present invention.

Claims

1. A delivery method that supports transaction rollback and synchronous update of ownership, characterized by: The exchange consists of three parts: storage management server, ownership management server and key management server; specifically, the following steps are included: S1: Generate system public parameters based on security parameters; S2: User registers on the exchange; S3: The seller encrypts the data and uploads the ciphertext to the exchange. The exchange stores it on the storage management server and uploads the key to the exchange's key management server. The key management server uses the trusted execution environment to store the key and the corresponding key usage policy for a long time. S4: The seller submits a request to the exchange to modify the ownership, and the exchange modifies the ownership on the ownership management server; S5: The seller accesses the key management server and modifies the key usage policy so that the buyer has the right to use the key within the usage period; S6: When using data, the buyer accesses the key management server to obtain the key and uses the data in a trusted execution environment and under policy restrictions; S7: If the buyer cancels the transaction, trusted deletion of data is achieved based on the trusted execution environment and policy.

2. The delivery method supporting transaction rollback and synchronous update of ownership according to claim 1 is characterized by: The system common parameters are: ； in p is a prime number in the finite field defined by the elliptic curve, G represents the 𝑛-order additive cyclic group of points on the elliptic curve, 𝑔 is the generator of 𝐺, 𝑛 is the order of the generator 𝑔, H ( ) is a hash function from G Map to Z p , Enc ( )and Dec ( ) is a pair of public key encryption algorithms, E ( )and D ( ) is a pair of symmetric encryption algorithms, Sig ( )and Ver ( ) is a pair of digital signature algorithms; Exchange ownership management server RM Create a Equity Table l And make it public. This table is used to record the owner and user of each piece of data. Exchanges DE and Key Management Server KM Generate a first key pair for encryption and decryption bound to the identity and a second key pair for signature verification , and the public key used for encryption epk DE , epk KM and for signature verification spk DE , spk KM Public; in Key Manager KM Use Intel's SGX technology to generate a secure zone locally Enclave KM , ensuring long-term trusted storage of keys and allowing users u Following the right strategy policy KM Get the key; in the user u Use Intel's SGX technology to generate a secure zone locally Enclave u , ensuring that the key is discarded after use and in accordance with the policy policy u Usage data; in Key Manager KM and users u There are also Quoting Enclave , Quoting Enclave Is a trusted special Enclave , which is used to apply Enclave Provided to prove Enclave The report that the code and data are correctly instantiated in the code is converted into a structure that can be verified externally, called Quote .

3. The delivery method supporting transaction rollback and synchronous update of ownership according to claim 2 is characterized by: The specific steps of S1 are as follows: 1) Each user u Register at the exchange to obtain a user identity ID ; 2) Each user u Generate the first key pair for encryption and decryption and a second key pair for signature verification , the public key used for encryption epk u and for signature verification spk u Upload to the exchange, the exchange will epk u and spk u The corresponding user identity ID The binding is stored at the storage management server and made public.

4. The delivery method supporting transaction rollback and synchronous update of ownership according to claim 3 is characterized by: The specific steps of S3 are as follows: 1) The seller randomly generates a symmetric encryption key locally ek , using a symmetric encryption key ek Data data Encrypt to get ciphertext C 1= E ( ek , data ), and the ciphertext C 1Sign and get the ciphertext signature , and then the ciphertext C 1 and ciphertext signature Upload to the exchange, and the exchange will store it on the storage management server; 2) The seller randomly generates a private key for the Diffie-Hellman (DH) key exchange protocol locally , and then calculate the public key , generate a timestamp of the current time tag 1. Use a key manager KM The encrypted public key epk KM ,right ppk s and tag 1 Encrypt to get ciphertext C 2= , using your own signature public key ssk s Ciphertext C 2Sign and get the signature , to the key manager KM Request service, send ciphertext C 2 and signature Send to KM And to KM Issue a challenge to verify Enclave KM Correct instantiation of ; 3) KM After receiving the request, first use Verify the signature , calculated after verification get ppk s and tag 1, tag 1Access the Ownership Manager after verification RM Check if the seller is the owner of the modified data, and if so, accept the challenge. Enclave KM Randomly generate the private key for the DH key exchange protocol , and then calculate the public key , generate a timestamp of the current time tag 2. Use the seller's public key to the public key ppk KM , Timestamp tag 2 Calculate the ciphertext ,right C 3Sign with your own private key to get the signature ,calculate Get the session key ck 1. Generate a report report , containing the ciphertext C 3. Signature , Enclave KM identity and status information; 4) KM Will report Send to Quoting Enclave Authentication within and using hardware-specific ECDSA The private key signs it and generates Quote ; 5) The generated Quote Sent to Intel's remote attestation service IAS , IAS right Quote Perform verification and generate a verification report. KM Send verification report to seller; 6) The seller receives and checks the verification report to confirm KM on Enclave Is it initialized correctly and running safely? After confirming, first use Verify the signature , calculated after verification get ppk KM and tag 2, tag 2 Calculation after verification Get the session key ck 1. Generate key usage strategy policy ek , using the session key ck 1 pair of symmetric encryption keys ek and key usage policy policy ek Encrypt to get ciphertext Then use your own signature public key ssk s Ciphertext C 4Sign and get signature , the ciphertext C 4 and Signature Send to KM ; 7) KM First use Verify the signature After verification, Enclave Use session keys ck 1 Calculation Get the symmetric encryption key ek and key usage policy policy ek ,exist Enclave Medium- and long-term trusted storage of symmetric encryption keys ek and the corresponding key usage policy policy ek .

5. The delivery method supporting transaction rollback and synchronous update of ownership according to claim 4 is characterized by: The specific steps of S4 are as follows: 1) The seller generates a timestamp of the current time tag 3. Use exchanges DE The encrypted public key epk DE , a request to modify the buyer to be the user of the purchased data request and timestamp tag 3 Encrypt to get ciphertext , using your own signature public key ssk s Ciphertext C 5Sign and get signature , to the exchange DE Request service, send ciphertext C 5 and signature Send to DE ; 2) DE After receiving the request, first query the ownership management server RM Verify whether the seller is the owner of the modified data. Verify the signature , calculated after verification Get modification request request and tag 3. tag 3 After verification, the ownership management server RM According to the modification request request Modify the data ownership of the corresponding data, and generate the timestamp of the current time after the modification is completed tag 4. Modify the successful message response Encrypt with the seller's public key to get the ciphertext ,right C 6Sign with private key to get signature , the ciphertext C 6 and Signature Send to the seller; 3) After receiving the reply message, the seller first uses Verify the signature , calculated after verification Get a reply response and tag 4. tag 4View the response after verification response , and obtain the ownership modification result.

6. The delivery method supporting transaction rollback and synchronous update of ownership according to claim 5 is characterized by: The specific steps of S5 are as follows: 1) The seller generates a timestamp of the current time tag 5. Use a key manager KM The encrypted public key epk KM , to modify the key usage policy of the key that the buyer is authorized to use policy ek and timestamp tag 5 Encrypt to get ciphertext , using your own signature public key ssk s Ciphertext C 7Sign and get signature , the ciphertext C 7 and Signature Send to KM ; 2) KM After receiving the request, first use Verify the signature , calculated after verification get policy ek and tag 5. tag 5 Access the Ownership Manager after verification RM Check whether the seller is the owner of the data key usage policy to be modified. If yes, Enclave KM Update key usage policy policy ek After the modification is completed, a timestamp of the current time is generated tag 6. Modification results res Encrypt with the seller's public key to get the ciphertext ,right C 8Sign with private key to get signature , the ciphertext C 8 and Signature Send to the seller; 3) After receiving the reply message, the seller first uses Verify the signature , calculated after verification Get the result res and tag 6. tag 6 Check the results after verification res , and obtain the key usage policy update result.

7. The delivery method supporting transaction rollback and synchronous update of ownership according to claim 6 is characterized by: The specific steps of S6 are as follows: 1) The buyer downloads data from the storage management server data The corresponding ciphertext C 1 and digital signature , calculated using the seller's signature public key Verify the signature , after verification, a timestamp of the current time is generated tag 7. Use a key manager KM The encrypted public key epk KM , using data encryption key ek Request request ek and timestamp tag 7 Encrypt to get ciphertext , using your own signature public key ssk b Ciphertext C 9Sign and get signature , the ciphertext C 9 and Signature Send to KM ; 2) KM After receiving the request, first use Verify the signature , calculated after verification get request ek and tag 7, tag 7 Access the Ownership Manager after verification RM Check whether the buyer is the legitimate user of the data key to be used. If yes, Enclave KM Key Usage Policy policy ek Determine the buyer's key usage authority and randomly generate a private key for the DH key exchange protocol after the determination is completed , and then calculate the public key , generate a timestamp of the current time tag 8. Use the buyer’s public key to encrypt the ciphertext ,right C 10 Sign with private key to get signature , the ciphertext C 10 and signature Sent to the buyer and challenged to verify Enclave b Correct instantiation of ; 3) After receiving the request, the buyer first uses Verify the signature , calculated after verification get rpk KM and tag 8. tag 8After verification, accept the challenge and Enclave b Randomly generate the private key for the DH key exchange protocol , and then calculate the public key , generate a timestamp of the current time tag 9. Use your own public key to the public key rpk b , Timestamp tag 9Calculate the ciphertext ,right C 11 Sign with private key to get signature ,calculate Get the session key ck 2. Generate a report report , containing the ciphertext C 11 ,sign , Enclave b identity and status information; 4) The buyer will report Send to Quoting Enclave Authentication and use ECDSA The private key signs it and generates Quote ; 5) The generated Quote Sent to Intel's remote attestation service IAS , IAS right Quote Verify and generate a verification report, which the buyer sends to KM ; 6) KM Receive and review verification reports to confirm the buyer's Enclave Is it initialized correctly and running safely? After confirming, first use Verify the signature , calculated after verification get rpk b and tag 9. tag 9 Calculate after verification Get the session key ck 2. Use session key ck 2 pairs of symmetric encryption keys ek and key usage policy policy ek Encrypt to get ciphertext Then use your own private key ssk KM Ciphertext C 12 Sign Get Signature , the ciphertext C 12 and signature Send to the buyer; 7) The buyer first uses Verify the signature After verification, Enclave Use session keys ck 2 Calculation Get the symmetric encryption key ek and key usage policy policy ek ,exist Enclave According to the key usage policy policy ek Trusted use of symmetric encryption keys ek .

8. The delivery method supporting transaction rollback and synchronous update of ownership according to claim 7 is characterized by: The specific steps of S7 are as follows: 1) After the buyer's application is approved, the exchange will RM Modify the data ownership of the corresponding data, revoke the buyer's use rights, and generate a timestamp of the current time after the modification is completed tag 10 , to revoke the certificate proof 1 Use the seller's public key to encrypt the ciphertext ,right C 13 Sign with private key to get signature , the ciphertext C 13 and signature Send to the seller; 2) The seller receives the message first Verify the signature , calculated after verification Get revocation certificate proof 1 and tag 10 , tag 10 After verification, keep the revocation certificate properly proof 1; 3) The seller generates a timestamp of the current time tag 11 , using the key manager KM The encrypted public key epk KM , request to revoke the buyer's key usage rights rev and timestamp tag 11 Encrypt to get ciphertext , using your own signature public key ssk s Ciphertext C 14 Sign Get Signature , the ciphertext C 14 and signature Send to KM ; 4) KM After receiving the request, first use Verify the signature , calculated after verification get rev and tag 11 , tag 11 Access the Ownership Manager after verification RM Check whether the seller is the data owner and whether the buyer has been revoked of the right to use the data. Enclave KM Update key usage policy policy ek After the modification is completed, a timestamp of the current time is generated tag 12 , to revoke the certificate proof 2. Encrypt the ciphertext using the seller's public key ,right C 15 Sign with private key to get signature , the ciphertext C 15 and signature Send to the seller; 5) After receiving the reply message, the seller first uses Verify the signature , calculated after verification Get revocation certificate proof 2 and tag 12 , tag 12 After verification, keep the revocation certificate properly proof 2. Data key from the buyer ek In a trusted execution environment and based on policy policy Use, so that after each use the data key ek The decrypted data will be discarded and the decrypted data will be strictly restricted from leaving the domain in plain text, so the buyer needs to re-register the key manager every time he uses the data. KM Requesting a data key ek By modifying the ownership and key usage policy on the key manager, the buyer is no longer entitled to the data key. ek , achieving trusted deletion of data after the buyer cancels the transaction.

9. A delivery system that supports transaction rollback and synchronous update of ownership, characterized by: A delivery method for implementing the support of transaction rollback and synchronous update of ownership as described in any one of claims 1 to 8, comprising: A parameter generation module, used to generate system common parameters according to security parameters; Registration module, used to register on the exchange; The encryption module is used to encrypt data and upload the ciphertext to the exchange, which stores it on the storage management server and uploads the key to the exchange's key management server. The key management server uses the trusted execution environment to store the key and the corresponding key usage policy in a long-term trusted manner. The ownership modification module is used to submit a request to the exchange to modify the ownership, and the exchange modifies the ownership at the ownership management server; A key permission modification module is used to access the key management server and modify the key usage policy so that the buyer has the right to use the key within the usage period; A key acquisition module is used to access a key management server to obtain a key when using data, and use data in a trusted execution environment and under policy restrictions; Trusted deletion module, used to implement trusted deletion of data based on the trusted execution environment and policy when the buyer cancels the transaction; The exchange includes a storage management server, a property management server and a key management server.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer-executable instructions. When the computer-executable instructions are loaded and executed by the processor, the delivery method supporting transaction rollback and synchronous update of ownership as described in any one of claims 1-8 is implemented.

Images