A user-centric data retrieval and sharing method in cloud computing environment

By designing a collaborative working mode based on authoritative organizations and cloud servers in a cloud computing environment, and using algorithms to generate keys and ciphertexts, the secure retrieval and sharing of data is realized, and the problem of low data sharing and retrieval efficiency in cloud computing is solved. Reduces computing burden and ensures data security.

CN118611987BActive Publication Date: 2024-12-06HUNTERON NETWORK TECH (SHANGHAI) CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202411074272.6
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2024-08-07
Publication Date
2024-12-06
Estimated Expiration
2044-08-07

AI Technical Summary

Technical Problem

In the cloud computing environment, when sharing and retrieving data, how to improve data user retrieval efficiency and reduce computing burden while ensuring data security and access control, especially when multi-user authorization and large data volumes, The prior art is difficult to effectively solve.

Method used

A collaborative working mode based on authoritative organizations, cloud query servers and cloud storage servers is designed, and the system master key, attribute key, index, ciphertext, pre-decryption key and re-encryption key are generated and used through algorithms to realize Secure retrieval and sharing of data, supports fine-grained access control, and delegates re-encryption tasks to cloud servers.

Benefits of technology

It realizes that data users can obtain all the data they are interested in, improves the friendliness of encrypted data retrieval and sharing in cloud computing environments, reduces the decryption calculation time of data users, and reduces the computing burden of data owners, while ensuring Data security.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118611987B_ABST
    Figure CN118611987B_ABST
Patent Text Reader

Abstract

The present application discloses a user-centric data retrieval and sharing scheme in a cloud computing environment, where an authority generates attribute keys for users; data owners use keywords to generate indexes, ciphertexts, trapdoors, and re-encryption keys and send them to cloud servers; data users generate pre-decryption keys and trapdoors based on attribute keys; cloud query servers perform trapdoor matching and check access policies to generate pre-decrypted ciphertexts of original ciphertexts and pre-decrypted ciphertexts of re-encrypted ciphertexts; data users decrypt two pre-decrypted ciphertexts to obtain plaintext. The combination of proxy re-encryption and attribute-based searchable strategies enables data owners to delegate re-encryption and pre-decryption to cloud servers without compromising security, thereby reducing the computational burden on data owners and data users.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the field of network and information security, and specifically to a user-centric data retrieval and sharing solution in a cloud computing environment. Background Art

[0002] The rapid development of cloud computing has provided convenience for many users and devices with limited computing power. Users and devices can let cloud servers take on part of the computing responsibility to achieve more complex functions. However, cloud servers are generally semi-trusted. In this case, directly outsourcing data without any processing to cloud servers is equivalent to giving up control over the data. Since the data usually contains sensitive information, there is a risk of privacy leakage. Therefore, in order to protect the data, the data owner usually encrypts the data before outsourcing it to the cloud server.

[0003] There are many ways to outsource data encryption. One typical solution is attribute-based encryption, which can perform precise access control. In a cloud-based system, users encrypt information using specific attributes before uploading it to the cloud, thereby protecting the confidentiality of the data and ensuring that only authorized users can access it. However, when the number of users who need to be authorized increases, how to share data safely and efficiently becomes a challenge. One approach is for users to decrypt and re-encrypt data for each user who needs to be authorized, but this approach significantly increases the computational burden on the user himself. Another approach is to entrust the user's attribute key to the cloud server, which decrypts and re-encrypts on behalf of the user. This approach requires the cloud server to be fully trusted, but in practice, cloud servers are usually semi-trusted, so this approach requires too much trust in the cloud server, and proxy re-encryption provides a feasible solution to these problems.

[0004] In the process of data sharing, data retrieval is also a key step. The search process for plaintext data is relatively simple. When data is stored in the cloud in ciphertext form, data retrieval becomes complicated. A common solution is to create a data table to record data information, but as the amount of data increases, the cost of maintaining the data table also increases. Public key-based searchable encryption and attribute-based searchable encryption provide a way to solve this problem. Although there have been many advances in research on data sharing, current research still cannot fully meet the needs of data users in data search and sharing. For example, users want to obtain all the data they are interested in, which includes not only the data they have access to, but also the data they are interested in but do not have access to. In addition, users hope to be able to decrypt the acquired data at a very low cost, which is also a problem to be solved. Summary of the invention

[0005] In order to solve the above technical problems, this application proposes the following technical solutions:

[0006] Call from authority The algorithm inputs security parameters and attribute space for initialization, obtains the system master key and discloses system parameters, and the user submits an attribute set to the authority, which calls (), input the master key and attribute set, obtain the attribute key and send it to the data owner and data user.

[0007] The data owner selects a set of keywords and calls the algorithm Generate the index and intermediate secret value; then, the data owner uses the plaintext, access policy, and intermediate secret value to call The algorithm generates ciphertext and uploads the index and ciphertext to the cloud storage server.

[0008] When a data user wants to obtain the data of interest, he calls algorithm, using the attribute key to generate pre-decryption key and decryption key; data users call The algorithm generates a trapdoor; then, the data user sends a query request to the cloud query server.

[0009] After receiving the request from the data user, the cloud query server calls The algorithm uses trapdoors, data indexes, and matching thresholds to generate , record the data items that meet the data user's interests in List 1; if successful, output , then call The algorithm first determines whether the attribute complies with the access policy. If it does not comply, the data entry in List 1 is deleted; if it complies, the data entry is entered. , pre-decryption key generation and original ciphertext generation pre-decrypted ciphertext; It should be noted that List 1 and List 2 match all data matched by the interests of data users; List 1 contains data that matches the interests of data users and they can access, while List 2 contains data that matches the interests of data users but they cannot access.

[0010] After receiving the request from the data user, the data owner calls The algorithm inputs its own attribute key and access policy, and outputs the re-encryption key to be sent to the cloud storage server.

[0011] After receiving the re-encryption key from the data user, the cloud query server calls The algorithm inputs the pre-decryption key, the re-encrypted ciphertext and the re-encryption key to generate the pre-decrypted ciphertext and send it to the data user.

[0012] After receiving the pre-decrypted ciphertext of the original ciphertext and the pre-decrypted ciphertext of the re-encrypted ciphertext, the data user uses the two ciphertexts and the decryption key as and The input of the algorithm is used to verify whether the original ciphertext and the re-encrypted ciphertext have been tampered with, and the plaintext is output.

[0013] The specific algorithms mentioned in the process are:

[0014] Algorithm 1, initialization : The authority AU will and attribute space As input, the algorithm chooses a prime number The bilinear group of , define the bilinear map as ;definition , , , , , , As a hash function; randomly selected , , ; Output system master key and public parameters .

[0015] Algorithm 2, key generation : When a user submits a property set When the authority AU uses the master key and attribute sets As input to the algorithm; this algorithm randomly selects ,calculate For attribute sets Each attribute in calculate Recalculate , .

[0016] Final output attribute key .

[0017] Algorithm 3: Index Generation :When the data owner DO uploads the data to the cloud, he selects a set of keywords As input to the algorithm, the algorithm randomly selects , ,make calculate right Each keyword in the calculation , and finally output the index and the intermediate secret value .

[0018] Algorithm 4: Data encryption : After the index is generated, the data owner DO will , Access Policy , intermediate secret value and As the algorithm input, for The algorithm randomly selects ,calculate , randomly selected Composition vector ,for calculate , randomly selected ,calculate , , then calculate , , , , , the final output After running Algorithms 3 and 4, the data owner DO will index and ciphertext Upload the CSS to the cloud storage server.

[0019] Algorithm 5: Pre-decryption key generation :When a data user DU wants to obtain the data of interest, it will use its attribute key As input; the algorithm randomly selects ,calculate , for the attribute set in the attribute key Each attribute of calculate ,make ;Finally output the pre-decryption key and the decryption key .

[0020] Algorithm 6, trapdoor generation :After generating the pre-decryption key and decryption key, the data user DU will use its attribute key , decryption key , keywords As input; the algorithm randomly selects ,for The keywords are calculated in sequence , , , ; then randomly select ,for The keywords are calculated in sequence , , , ; Then calculate ,set up ; Final output trapdoor .

[0021] The data user DU submits a query request to the cloud query server CQS, and the request includes a trapdoor , pre-decryption key and matching threshold .

[0022] Algorithm 7, Trapdoor Matching :After receiving the request from the data user DU, the cloud query server CQS will , different data indexes And the matching threshold As input; the algorithm defines the counter and one that records the last successful match between the keyword in the trapdoor and the keyword in the index ; Algorithm calculation And judge and Are they equal? ​​If not, continue searching until all searches are completed. If they are equal, set the counter +1, and record the matching trapdoor keyword position and index keyword position ; After the search is completed, determine whether the value of the counter reaches the threshold If it is not reached, then output , if the threshold is reached, then calculate , .

[0023] Final output of the algorithm ,At the same time, the cloud query server CQS records the data entries that meet the interests of the data user in List 1.

[0024] Algorithm 8: Pre-decryption of original ciphertext :If Algorithm 7 succeeds, output , then the cloud query server CQS will and the pre-decryption key , original ciphertext Together as the input of this algorithm; algorithm judgment Properties in Is it satisfied? The access policy in .

[0025] If not satisfied, output directly ; At this time, the cloud query server CQS deletes the data entry in list 1 and adds it to list 2; if satisfied, then set , randomly selected , so that ;calculate , , ; The algorithm outputs the original ciphertext and the pre-decrypted ciphertext .

[0026] Algorithm 9: Re-encryption key generation :When the data owner DO receives the request from the data user DU, DO will use its attribute key and the access policy that satisfies the DU attribute key As input to the algorithm; the algorithm randomly selects ,calculate , , , for each attribute in the attribute key calculate ; then calculate , ; Random selection ,for All columns in the calculation , randomly selected ,calculate Final output re-encryption key .

[0027] Algorithm 10: Ciphertext re-encryption :After the cloud query server CQS receives the re-encryption key obtained by the data user DU from the data owner DO, it converts the original ciphertext and re-encryption key As the input of the algorithm; the algorithm assumes .

[0028] Random Selection , so that ;calculate ;Finally output the re-encrypted ciphertext .

[0029] Algorithm 11: Pre-decryption and re-encryption of ciphertext :The cloud query server CQS obtains the re-encrypted ciphertext through algorithm 10 and uses the pre-decryption key , re-encrypt the ciphertext and re-encryption keys As the input of this algorithm; algorithm judgment Properties in Is it satisfied? If the access policy is not satisfied, it will be output directly. If satisfied, then set , randomly selected , so that ;calculate ;make , and finally output the pre-decrypted ciphertext of the re-encrypted ciphertext .

[0030] Algorithm 12: Decrypting the original ciphertext to obtain the pre-decrypted ciphertext :Data user DU receives the pre-decrypted ciphertext of the original ciphertext returned by the cloud query server CQS and the decryption key As input to the algorithm; the algorithm performs the following calculations , , .

[0031] like This indicates that the ciphertext has not been tampered with, and the plaintext is output. , otherwise output .

[0032] Algorithm 13: Decrypting the pre-decrypted ciphertext of the re-encrypted ciphertext :Data user DU receives the pre-decrypted ciphertext of the re-encrypted ciphertext returned by the cloud query server CQS and the decryption key As input to the algorithm. The algorithm performs calculations , , , .

[0033] like , it indicates that the ciphertext has not been tampered with, and the plaintext is output , otherwise output .

[0034] This solution designs a unique data retrieval, verification and sharing solution, which ensures that data users can obtain all the data they are interested in, thereby improving the user-friendliness of encrypted data retrieval and sharing operations in the cloud computing environment.

[0035] While ensuring data security, cloud computing servers are used to pre-decrypt data, thereby reducing the decryption computing time of data users. At the same time, the scheme supports fine-grained access control, allowing data owners to delegate re-encryption tasks to cloud servers without compromising data security, thereby reducing the computing burden of data owners.

[0036] Compared with the prior art, the present invention has the following technical effects:

[0037] In the existing data sharing and encryption schemes, it is impossible to ensure security while ensuring that the cloud server can effectively retrieve and share data. The present invention adopts proxy re-encryption and encryption strategies based on attributes and keywords, and designs a unique data retrieval, verification and sharing scheme. The scheme ensures that data users can obtain all the data they are interested in, thereby improving the user-friendliness of encrypted data retrieval and sharing operations in the cloud computing environment. While ensuring data security, cloud computing servers are used to pre-decrypt data, thereby reducing the decryption calculation time of data users. At the same time, the scheme supports fine-grained access control, allowing data owners to delegate re-encryption tasks to cloud servers without compromising data security, thereby reducing the computing burden of data owners. BRIEF DESCRIPTION OF THE DRAWINGS

[0038] Figure 1 A schematic diagram of a physical process of a user-centric data retrieval and sharing solution in a cloud computing environment provided in an embodiment of the present application.

[0039] Figure 2 A schematic diagram of a remote medical data privacy protection system provided in an embodiment of the present application. DETAILED DESCRIPTION

[0040] The present solution is described below in conjunction with the accompanying drawings and specific implementation methods.

[0041] Figure 1 A schematic diagram of a user-centric data retrieval and sharing solution in a cloud computing environment provided by an embodiment of the present application, see Figure 1 , the entities include:

[0042] Authority (AU): A fully trusted entity that is primarily responsible for generating the system's master keys and public parameters, and creating and securely distributing user keys based on the needs of system users.

[0043] Cloud Query Server (CQS): A semi-trusted entity that is primarily responsible for processing user requests, pre-decryption of ciphertext, and re-encryption of data; unlike other models that typically combine these services together, this solution explicitly separates data storage from query services to reduce the workload of the cloud server.

[0044] Cloud Storage Server (CSS): A semi-trusted entity. There are relatively few cloud storage servers, and their main responsibilities are data retrieval and storage of encrypted data.

[0045] Data owner (DO): A fully trusted entity for the data they own. The data owner is the controller of access rights to encrypted data in the cloud.

[0046] Data Users (DUs): Entities that access ciphertext stored on the cloud; they obtain data by providing search trapdoors and pre-decryption keys to the cloud query server; when data users access authorized data, they are considered fully trusted, and this trust means that they are expected not to disclose the obtained data to unauthorized third parties.

[0047] First, the authority performs initial configuration and calls Algorithm; when a user registers, call () algorithm generates an attribute key for the user and sends it to the user; the data owner calls and The algorithm generates the index and ciphertext and sends them to the cloud storage server; the data user calls After the trapdoor is generated, the cloud storage server sends the ciphertext and the trapdoor. The cloud storage server matches the trapdoor and then returns lists 1 and 2 according to the access policy. If they match, the pre-decrypted ciphertext is generated. The data user calls The algorithm generates its own re-encryption key and sends it to the cloud server, which then calls Generate pre-decrypted ciphertext and send it to data user again; data user calls and The algorithm decrypts two ciphertexts to obtain plaintext.

[0048] Corresponding to the user-centric data retrieval and sharing solution in a cloud computing environment provided by the above embodiment, the algorithm diagram included in the specific process is shown in FIG. Figure 2 , the specific process and algorithm are:

[0049] The scheme includes 13 algorithms in total, including initialization, key generation, index generation, data encryption, pre-decryption key generation, trapdoor generation, trapdoor matching, pre-decryption of original ciphertext, re-encryption key generation, ciphertext re-encryption, pre-decryption of re-encrypted ciphertext, pre-decryption of original ciphertext, and pre-decryption of re-encrypted ciphertext.

[0050] Algorithm 1, initialization .

[0051] The authority AU will and attribute space As input, the algorithm chooses a prime number The bilinear group of , define the bilinear map as ;definition , , , , , , As a hash function; randomly selected , , ; Output system master key and public parameters .

[0052] Algorithm 2, key generation .

[0053] When a user submits a property set When the authority AU uses the master key and attribute sets As input to the algorithm; this algorithm randomly selects ,calculate For attribute sets Each attribute in calculate Recalculate , .

[0054] Final output attribute key .

[0055] Algorithm 3: Index Generation .

[0056] When the data owner DO uploads the data to the cloud, he selects a set of keywords As input to the algorithm, the algorithm randomly selects , ,make calculate right Each keyword in the calculation .

[0057] Final output index and intermediate secret value .

[0058] Algorithm 4: Data encryption .

[0059] After the index is generated, the data owner DO will , Access Policy , intermediate secret value and As the algorithm input, for The algorithm randomly selects ,calculate , randomly selected Composition vector ,for calculate , randomly selected ,calculate , , then calculate , , , , , the final output After running Algorithms 3 and 4, the data owner DO will index and ciphertext Upload the CSS to the cloud storage server.

[0060] Algorithm 5: Pre-decryption key generation .

[0061] When a data user DU wants to obtain the data of interest, it will use its attribute key As input, the algorithm randomly selects ,calculate , for the attribute set in the attribute key Each attribute of calculate ,make .

[0062] Final output pre-decryption key and the decryption key .

[0063] Algorithm 6, trapdoor generation .

[0064] After generating the pre-decryption key and decryption key, the data user DU uses its attribute key , decryption key , keywords As input; the algorithm randomly selects ,for The keywords are calculated in sequence , , , ; then randomly select ,for The keywords are calculated in sequence , , , . Then calculate ,set up .

[0065] Final output trapdoor .

[0066] The data user DU submits a query request to the cloud query server CQS, and the request includes a trapdoor , pre-decryption key and matching threshold .

[0067] Algorithm 7, Trapdoor Matching .

[0068] After receiving the request from the data user DU, the cloud query server CQS will , different data indexes And the matching threshold As input; the algorithm defines the counter and one that records the last successful match between the keyword in the trapdoor and the keyword in the index ; Algorithm calculation And judge and Are they equal? ​​If not, continue searching until all searches are completed. If they are equal, set the counter +1, and record the matching trapdoor keyword position and index keyword position ; After the search is completed, determine whether the value of the counter reaches the threshold If it is not reached, then output , if the threshold is reached, then calculate , .

[0069] Final output of the algorithm ,At the same time, the cloud query server CQS records the data entries that meet the interests of the data user in List 1.

[0070] Algorithm 8: Pre-decryption of original ciphertext .

[0071] If Algorithm 7 successfully outputs , then the cloud query server CQS will and the pre-decryption key , original ciphertext Together as the input of this algorithm; algorithm judgment Properties in Is it satisfied? The access policy in .

[0072] If not satisfied, output directly ; At this time, the cloud query server CQS deletes the data entry in list 1 and adds it to list 2; if satisfied, then set , randomly selected , so that ;calculate , , .

[0073] Algorithm outputs original ciphertext pre-decrypted ciphertext .

[0074] Algorithm 9: Re-encryption key generation .

[0075] When the data owner DO receives the request from the data user DU, DO sends its attribute key and the access policy that satisfies the DU attribute key As input to the algorithm; the algorithm randomly selects ,calculate , , , for each attribute in the attribute key calculate ; then calculate , ; Random selection ,for All columns in the calculation , randomly selected ,calculate .

[0076] Final output re-encryption key .

[0077] Algorithm 10: Ciphertext re-encryption .

[0078] After the cloud query server CQS receives the re-encryption key obtained by the data user DU from the data owner DO, it converts the original ciphertext and re-encryption key As the input of the algorithm; the algorithm assumes .

[0079] Random Selection , so that ;calculate .

[0080] The final output is the re-encrypted ciphertext .

[0081] Algorithm 11: Pre-decryption and re-encryption of ciphertext .

[0082] The cloud query server CQS obtains the re-encrypted ciphertext through algorithm 10 and then uses the pre-decryption key , re-encrypt the ciphertext and re-encryption keys As the input of this algorithm; algorithm judgment Properties in Is it satisfied? If the access policy is not satisfied, it will be output directly. If satisfied, then set , randomly selected , so that ;calculate .

[0083] make , and finally output the pre-decrypted ciphertext of the re-encrypted ciphertext .

[0084] Algorithm 12: Decrypting the original ciphertext to obtain the pre-decrypted ciphertext .

[0085] The data user DU receives the pre-decrypted ciphertext of the original ciphertext returned by the cloud query server CQS and the decryption key As input to the algorithm; the algorithm performs the following calculations , , .

[0086] like This indicates that the ciphertext has not been tampered with, and the plaintext is output. , otherwise output .

[0087] Algorithm 13: Decrypting the pre-decrypted ciphertext of the re-encrypted ciphertext .

[0088] The data user DU receives the pre-decrypted ciphertext of the re-encrypted ciphertext returned by the cloud query server CQS and the decryption key As input to the algorithm; the algorithm performs calculations , , , .

[0089] like , it indicates that the ciphertext has not been tampered with, and the plaintext is output , otherwise output .

[0090] The above are only preferred embodiments of the present invention. It should be pointed out that a person skilled in the art can make several modifications and improvements without departing from the inventive concept of the present invention, and these all fall within the protection scope of the present invention.

Claims

1. A user-centric data retrieval and sharing method in a cloud computing environment, based on proxy re-encryption and attribute-based searchable encryption technology, characterized in that: The method comprises: The authority performs initial configuration, obtains the system master key and discloses system parameters; the user submits an attribute set to the authority, and the authority generates an attribute key based on the master key and the attribute set and sends it to the data owner and data user; the authority AU takes the security parameter κ and the attribute space U as input, selects a bilinear group G with an order of prime number p, and defines a bilinear mapping as e: G×G→G T ;Define H: {0, 1} * →G T , H0: {0, 1} κ →G, H1:G T →{0, 1} κ , H2:G T →{0, 1} * , H4: {0, 1} * →{0, 1} κ , As a hash function; randomly selected g,Q∈G,h1,...,h U ∈G; output system master key MK = {α, β, a, b, c} and public parameter Para = {p, g, Q, G, G T ,e,H,H0,H1,H2,H3,H4,H5,g a , g b , g abc , g β , e(g, g) α , h1,…,h U }; When the user submits a property set When the authority AU uses the master key MK and attribute set As input; randomly selected Calculate d1 = ac, d2 = bc, AK1 = g α g βu , AK2=g u For attribute sets Each attribute in Calculate AK x =(H(x)) u Recalculate Output attribute key The data owner selects a set of keywords, generates indexes and ciphertexts, and sends them to the cloud storage server; when the data owner DO uploads the data to the cloud, he selects a set of keywords ω n As input; randomly select D∈{0,1} κ , Let v t =v1+v2 calculation Yes n Each keyword in the calculation Output index and intermediate secret value I = {L1, L2, {I 1,i , I 2,i , L 3,i } i∈[1,n] },v t , D; After generating the index, the data owner DO will write the plaintext m, access policy Intermediate secret value v t and D as input, where for Matrix; randomly select k DO ∈{0, 1} k ,calculate Random Selection Composition vector for calculate Random Selection calculate Then calculate Final Output Afterwards, the data owner DO uploads the index I and ciphertext CT to the cloud storage server CSS; When a data user wants to obtain the data of interest, he generates a pre-decryption key and a decryption key based on the attribute key; then he generates a trapdoor and sends a query request to the cloud query server; when the data user DU wants to obtain the data of interest, he uses its attribute key sk as input; randomly selects calculate For attribute set in attribute key Each attribute of calculate Let DecK = z; output the pre-decryption key and decryption key DecK = z; after generating the pre-decryption key and decryption key, the data user DU will use its attribute key sk, decryption key DecK, keyword As input; randomly selected For the keywords i∈[1,n1], calculate them in sequence Then randomly select t5∈[1,n1] and calculate the keywords of j∈[1,t5] in sequence Then calculate Set n2 = n1 + t5; output trapdoor The data user DU submits a query request to the cloud query server CQS, which includes the trapdoor TD, the pre-decryption key PreK and the matching threshold t u ∈[1-(1 / n2+1),1 / 2]; After receiving the request from the data user, the cloud query server matches the trapdoor with the index and records the data entries that meet the data user's interest in list 1; if the output is successful, it determines whether the attribute in the pre-decryption key meets the access policy of the ciphertext. If not, the data entry is deleted from list 1 and saved in list 2; if it meets, (D, E) and the pre-decryption key and the ciphertext are used to generate the pre-decrypted ciphertext of the original ciphertext; wherein, after receiving the request from the data user DU, the cloud query server CQS matches the trapdoor TD, different data indexes I and matching threshold t u As input; define counter count = 0 and an item j that records the successful match of the keyword in the last trapdoor and the keyword in the index respectively. c =0,i c =0; algorithm calculation And judge H2(C i,j ) and I 2,i Are they equal? ​​If not, continue searching until all searches are completed. If they are equal, set the counter count+1 and record the matching item trapdoor keyword position j c = j and index key position i c =i; after the search is completed, determine whether the value of the counter reaches the threshold t u n2, if the threshold is reached, then calculate Output (D, E), and the cloud query server CQS records the data items that meet the data user's interest in List 1; if (D, E) is successfully output, the cloud query server CQS uses (D, E) together with the pre-decryption key PreK and the original ciphertext CT as the input of this algorithm; determine the attribute in PreK Whether the access policy in CT is satisfied; if not, the cloud query server CQS deletes the data entry in list 1 and adds it to list 2; if it is satisfied, then set Random Selection Make calculate Output original ciphertext pre-decrypted ciphertext After receiving the request from the data user, the data owner uses the data owner's attribute key and the access policy that satisfies the data user's attribute key to generate a re-encryption key and sends it to the data user; After receiving the re-encryption key from the data user, the cloud query server generates a re-encrypted ciphertext using the re-encryption key and the ciphertext, and generates a pre-decrypted ciphertext of the re-encrypted ciphertext using the pre-decryption key, the re-encrypted ciphertext and the re-encryption key and sends the pre-decrypted ciphertext to the data user; After receiving the pre-decrypted ciphertext of the original ciphertext and the pre-decrypted ciphertext of the re-encrypted ciphertext, the data user decrypts the two ciphertexts and the decryption key respectively to obtain the plaintext.

2. According to claim 1, a user-centric data retrieval and sharing method in a cloud computing environment is characterized in that: After receiving the request from the data user, the data owner generates a re-encryption key using the data owner's attribute key and an access policy that satisfies the data user's attribute key and sends the re-encryption key to the data user, including: When the data owner DO receives the request from the data user DU, DO sends its attribute key sk and the access policy that satisfies the attribute key of DU. As input; randomly selected calculate For each property in property key calculate Then calculate rk5 = γ·e(g, g) αr′ , rk6=g r′ ; Random selection For all columns in M′, calculate Random Selection calculate Output re-encryption key 3. According to claim 2, a user-centric data retrieval and sharing method in a cloud computing environment is characterized in that: After receiving the re-encryption key from the data user, the cloud query server generates a re-encrypted ciphertext using the re-encryption key and the ciphertext, and generates a pre-decrypted ciphertext of the re-encrypted ciphertext using the pre-decryption key, the re-encrypted ciphertext and the re-encryption key and sends the pre-decrypted ciphertext to the data user, including: After the cloud query server CQS receives the re-encryption key obtained by the data user DU from the data owner DO, it takes the original ciphertext CT and the re-encryption key rk as input; let Random Selection Make calculate Output re-encrypted ciphertext After the cloud query server CQS obtains the re-encrypted ciphertext, it takes the pre-decryption key PreK, the re-encrypted ciphertext CT′ and the re-encryption key rk as input; the algorithm determines the attributes in PreK Does it satisfy the access policy in CT′? If so, then set Random Selection So that∑ j∈J θ j ·M′ j =(1, 0, ..., 0); calculate Let C Re =rk5, output the pre-decrypted ciphertext CT of the re-encrypted ciphertext RPreDec ={C0, C, C R , C Re , W}.

4. The user-centric data retrieval and sharing method in a cloud computing environment according to claim 3, characterized in that: After receiving the pre-decrypted ciphertext of the original ciphertext and the pre-decrypted ciphertext of the re-encrypted ciphertext, the data user decrypts the two ciphertexts and the decryption key to obtain plaintexts including: The data user DU receives the pre-decrypted ciphertext CT of the original ciphertext returned by the cloud query server CQS OPreDec and decryption key DecK as input; calculate like It indicates that the ciphertext has not been tampered with, and the plaintext m is output; The data user DU receives the pre-decrypted ciphertext CT of the re-encrypted ciphertext returned by the cloud query server CQS RPreDec and decryption key DecK as input; calculate like This indicates that the ciphertext has not been tampered with, and the plaintext m is output.