Data processing method and device, equipment and medium

Abstract

One or more embodiments of the invention provide a data processing method and device, equipment and a medium. In one or more embodiments of the present specification, a database service provider provides services for a plurality of database service users. A database service provider generates a combined key corresponding to each database service user based on a first sub-key provided by the database service provider for each database service user and a second sub-key provided by each database service user for the database service provider; according to the data encryption method and the data encryption device, data interaction with each database service user is carried out based on the combined key corresponding to each database service user, so that data encryption based on multi-key mixing is realized, and the data security is ensured.

Description

Technical Field

[0001] One or more embodiments of the present specification relate to the field of database technology, and in particular, to a data processing method, apparatus, device, and medium. Background Art

[0002] With the popularization of cloud computing technology, cloud databases, as an important tool for data storage and management, have become one of the basic tools used by individual users and various organizations in daily life. Cloud databases carry a large amount of sensitive information such as user data, transaction records, and electronic files. As the scale of data continues to increase, the risk of data leakage, loss, and tampering continues to increase, posing a huge challenge to data security. In order to ensure the confidentiality, integrity, and availability of data, ensuring the security of cloud database data has become a key issue that cannot be ignored in the information age. Summary of the invention

[0003] In view of this, one or more embodiments of the present specification provide a data processing method, apparatus, device, and medium.

[0004] To achieve the above objectives, one or more embodiments of this specification provide the following technical solutions: According to a first aspect of one or more embodiments of this specification, a data processing method is proposed, which is applied to a database service provider, where the database service provider is used to provide services to multiple database service users. The method includes: Generate a combined key corresponding to each database service user based on a first subkey provided by the database service provider for each database service user and a second subkey provided by each database service user for the database service provider; Based on the combined key corresponding to each database service user, data is exchanged with each database service user respectively.

[0005] In the above embodiment, in a scenario where a database service provider provides services to multiple database service users, the database service provider generates a combined key corresponding to each database service user based on the first subkey provided by the database service provider for each database service user and the second subkey provided by each database service user for the database service provider, so as to interact with each database service user based on the combined key corresponding to each database service user, thereby realizing data encryption based on multi-key mixing and ensuring data security.

[0006] According to a second aspect of one or more embodiments of this specification, a data processing method is proposed, which is applied to a database service user, where the services used by the database service user come from multiple database service providers, and the method includes: Obtaining a combined key corresponding to each database service provider, where the combined key corresponding to each database service provider is generated based on a second subkey provided by the database user for each database service provider and a first subkey provided by each database service provider for the database service user; Based on the combined key corresponding to each database service provider, data is exchanged with each database service provider respectively.

[0007] In the above embodiment, when a database service user uses services provided by multiple database service providers, the database service user obtains the combined key corresponding to each database service provider. The combined key corresponding to each database service provider can be generated based on the second subkey provided by the database service user for each database service provider and the first subkey provided by each database service provider for the database service user. Based on the combined key corresponding to each database service provider, data interaction is performed with each database service provider respectively to implement data encryption based on multi-key mixing and ensure data security.

[0008] According to a third aspect of one or more embodiments of this specification, a data processing device is provided, which is applied to a database service provider, wherein the database service provider is used to provide services to multiple database service users, and the device includes: A generating module, configured to generate a combined key corresponding to each database service user based on a first subkey provided by the database service provider for each database service user and a second subkey provided by each database service user for the database service provider; The interaction module is used to interact with each database service user based on the combined key corresponding to each database service user.

[0009] According to a fourth aspect of one or more embodiments of this specification, a data processing device is provided, which is applied to a database service user, where the services used by the database service user come from multiple database service providers, and the device includes: an acquisition module, used to acquire a combined key corresponding to each database service provider, wherein the combined key corresponding to each database service provider is generated based on a second subkey provided by the database user for each database service provider and a first subkey provided by each database service provider for the database service user; The interaction module is used to interact with each database service provider based on the combined key corresponding to each database service provider.

[0010] According to a fifth aspect of one or more embodiments of this specification, a first computing device is provided, where the first computing device serves as a database service provider, including: processor; a memory for storing processor-executable instructions; The processor implements the method described in the first aspect above by running the executable instructions.

[0011] According to a sixth aspect of one or more embodiments of this specification, a second computing device is provided, where the second computing device serves as a database service user, including: processor; a memory for storing processor-executable instructions; The processor implements the method described in the second aspect above by running the executable instructions.

[0012] According to the seventh aspect of one or more embodiments of the present specification, a computer-readable storage medium is proposed, on which computer instructions are stored, and when the computer instructions are executed by a processor, the steps of the method described in the first aspect are implemented, or when the computer instructions are executed by a processor, the steps of the method described in the second aspect are implemented. BRIEF DESCRIPTION OF THE DRAWINGS

[0013] Figure 1 It is a schematic diagram of the system architecture of a data processing system provided by an exemplary embodiment.

[0014] Figure 2 It is a flowchart of a data processing method provided by an exemplary embodiment.

[0015] Figure 3 It is a flowchart of a data processing method provided by an exemplary embodiment.

[0016] Figure 4 It is a flowchart of a data processing method provided by an exemplary embodiment.

[0017] Figure 5 It is an interactive flow chart of a data processing method provided by an exemplary embodiment.

[0018] Figure 6 It is a schematic structural diagram of a first computing device provided by an exemplary embodiment.

[0019] Figure 7 It is a block diagram of a data processing device provided by an exemplary embodiment.

[0020] Figure 8It is a schematic structural diagram of a second computing device provided by an exemplary embodiment.

[0021] Fig. 9 It is a block diagram of a data processing device provided by an exemplary embodiment. DETAILED DESCRIPTION

[0022] Exemplary embodiments will be described in detail herein, examples of which are shown in the accompanying drawings. When the following description refers to the drawings, the same numbers in different drawings represent the same or similar elements unless otherwise indicated. The implementations described in the following exemplary embodiments do not represent all implementations consistent with one or more embodiments of this specification. Instead, they are merely examples of devices and methods consistent with some aspects of one or more embodiments of this specification as detailed in the appended claims.

[0023] It should be noted that: in other embodiments, the steps of the corresponding method are not necessarily performed in the order shown and described in this specification. In some other embodiments, the steps included in the method may be more or less than those described in this specification. In addition, a single step described in this specification may be decomposed into multiple steps for description in other embodiments; and multiple steps described in this specification may be combined into a single step for description in other embodiments.

[0024] The user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this manual are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with the relevant laws, regulations and standards of relevant countries and regions, and provide corresponding operation entrances for users to choose to authorize or refuse.

[0025] This specification provides a data processing method for achieving data security between multiple database service providers and multiple database service users. The database service provider may be a cloud database service provider, and the database service user may be an enterprise or a part of an enterprise, an organization, an individual user, etc., but is not limited thereto.

[0026] See also Figure 1 , Figure 1 is a schematic diagram of a system architecture of a data processing system provided by an exemplary embodiment. Figure 1As shown, taking the data processing system including database service provider 111, database service provider 112, database service provider 113, database service provider 114, database service provider 115, database service provider 116, data service user 121, database service user 122, and database service user 123 as an example, from the perspective of the database service provider, the database service provider 111 can provide services for the database service user 121, the database service user 122, and the database service user 123, the database service provider 112 can provide services for the database service user 121 and the database service user 122, the database service provider 113 can provide services for the database service user 122, and the database service provider Party 114 can provide services for database service user 122, database service provider 115 can provide services for database service user 123, and database service provider 116 can provide services for database service user 123; from the perspective of database service users, database service user 121 can use the services provided by database service providers 111, 112, and 116, database service user 122 can use the services provided by database service providers 112, 113, and 114, and database service user 123 can use the services provided by database service providers 111, 115, and 116.

[0027] It should be noted that Figure 1 This is only an exemplary system architecture. In more possible implementations, the data processing system may also be composed of more or fewer database service providers and more or fewer database service users, and this specification does not limit this.

[0028] Optionally, different database service providers may be different first computing devices, and the first computing device may be a server, such as one server, multiple servers, a server cluster, a cloud computing platform, etc., but is not limited thereto.

[0029] Optionally, different database service users may be different second computing devices, and the second computing device may be a server, such as one server, multiple servers, a server cluster, a cloud computing platform, etc., or the second computing device may be a terminal, such as a desktop computer, a portable computer, a laptop computer, a tablet computer, a smart phone, etc., but not limited to this.

[0030] The above is only an exemplary description of the application scenarios of this specification and does not constitute a limitation on the application scenarios of this specification. In more possible implementations, the solutions provided in this specification can be applied to more database-based data interaction scenarios, and this specification does not limit the specific application scenarios.

[0031] After introducing the application scenarios of this specification, the optional implementation process of this specification is introduced next.

[0032] See also Figure 2 , Figure 2 is a flow chart of a data processing method provided by an exemplary embodiment. Figure 2 As shown, the method can be applied to a database service provider, and the database service provider can be used to provide services to multiple database service users. The method includes: Step 201: Generate a combined key corresponding to each database service user based on a first subkey provided by the database service provider to each database service user and a second subkey provided by each database service user to the database service provider.

[0033] Optionally, the database service provider may provide a first subkey for each database service user, and the first subkeys provided to different database service users may be different. In addition, each database service user may also provide a second subkey for the database service provider, and the second subkeys provided to different database service users may be different.

[0034] Optionally, for any database service user among multiple database service users, a combined key corresponding to the database service user can be generated based on a first subkey provided by the database service provider to the database service user and a second subkey provided by the database service user to the database service provider.

[0035] Step 202: Based on the combined key corresponding to each database service user, data is exchanged with each database service user respectively.

[0036] It should be noted that each database service user will have a corresponding combined key. When the database service provider interacts with any database service user, it can use the combined key corresponding to the database service user to encrypt or decrypt the interactive data to ensure data security.

[0037] In introducing Figure 2 After the basic implementation of the illustrated embodiment, various optional embodiments are introduced below.

[0038] In some embodiments, the database service provider may generate a first master key, and then generate a first subkey for each database service user based on the first master key, and different database service users may have different corresponding first subkeys.

[0039] In some embodiments, when generating the first master key, the first master key may be generated based on a first encryption algorithm and a first random number.

[0040] Optionally, a first encryption algorithm may be used to process the first random number to obtain a first master key.

[0041] Optionally, the first random number may be generated by a random number generator of a database service provider, but is not limited thereto.

[0042] Optionally, the first encryption algorithm may be a symmetric encryption algorithm, such as an Advanced Encryption Standard (AES) encryption algorithm, but not limited thereto; or, the first encryption algorithm may be an asymmetric encryption algorithm, such as a Rivest–Shamir–Adleman (RSA) encryption algorithm, an elliptic curve cryptography (ECC) encryption algorithm, but not limited thereto.

[0043] After the first master key is generated, a first subkey may be generated for each database service user based on the generated first master key.

[0044] In some embodiments, a plurality of first sub-keys may be generated based on a derivation algorithm and the first master key.

[0045] Optionally, a derivation algorithm may be used to process the first master key to obtain a plurality of first sub-keys.

[0046] Optionally, the derivation algorithm can be a hash-based key derivation function (HMAC-based Key Derivation Function, HKDF), a password-based key derivation function 2 (Password-Based Key Derivation Function2, PBKDF2), an encryption-based key derivation function (such as a hash-based message authentication code (Hash-based Message Authentication Code, HMAC), a password-based message authentication code (Cipher-based Message Authentication Code, CMAC)), etc., but is not limited to these.

[0047] It should be noted that the generated multiple first subkeys can be distributed to multiple database service users, each database service user will be assigned a first subkey, and each database user is assigned a different first subkey.

[0048] That is, the database service provider may send the first subkey corresponding to each database user to the corresponding database service user, so that each database service user may receive the first subkey corresponding to the database service provider.

[0049] Optionally, the first subkey may be associated with first identification information, and the first identification information may be used to identify the first subkey. Different first subkeys may correspond to different first identification information.

[0050] Optionally, the first identification information may be a serial number, but is not limited thereto.

[0051] In some embodiments, the database service provider may send the first subkey and first identification information corresponding to the database service user to the database service user when the database service provider first exchanges the first subkey with the database service user. The database service user may associate and store the received first subkey and first identification information so that when the database service provider subsequently exchanges the first subkey with the database service user, it only needs to send the first identification information of the first subkey. The database service user can determine the first subkey corresponding to the received first identification information based on the stored information.

[0052] In some embodiments, the database service provider may also receive a second subkey sent by each database service user, wherein the second subkey is generated by each database service user based on its own second master key. The specific generation method will be described in Figure 3 The corresponding embodiments are described in detail and will not be repeated here.

[0053] Optionally, the second subkey may be associated with second identification information, and the second identification information may be used to identify the second subkey. Different second subkeys may correspond to different second identification information.

[0054] Optionally, the second identification information may be a serial number, but is not limited thereto.

[0055] In some embodiments, the database service user may send the second subkey and second identification information corresponding to the database service provider to the database service provider when the database service user interacts with the database service provider for the first time about the second subkey. The database service provider may store the received second subkey and second identification information in association with each other, so that when the database service user subsequently interacts with the database service provider about the second subkey, the user only needs to send the identification information of the second subkey. The database service provider may determine the second subkey corresponding to the received second identification information based on the stored information.

[0056] It should be noted that after the first subkey corresponding to each database service user (i.e., the first subkey distributed to each database service user by the database service provider) and the second subkey corresponding to each database service user (i.e., the second subkey sent to the database service provider by each database service user) are obtained through the above embodiment, a combined key corresponding to each database service user can be generated through step 201 based on the first subkey provided by the database service provider for each database service user and the second subkey provided by each database service user for the database service provider.

[0057] In some embodiments, for any database service user, a calculation may be performed based on the first subkey and the second subkey corresponding to the database service user to obtain a combined key corresponding to the database service user.

[0058] Optionally, a hash operation may be performed based on the first subkey and the second subkey corresponding to the database service user to obtain a combined key corresponding to the database service user. Alternatively, an exclusive OR (XOR) operation may be performed based on the first subkey and the second subkey corresponding to the database service user to obtain a combined key corresponding to the database service user.

[0059] Optionally, a series of calculations may be performed on the first subkey and the second subkey corresponding to the database service user based on a key derivation function to obtain a combined key corresponding to the database service user.

[0060] Optionally, the key derivation function may be HKDF, PBKDF2, an encryption-based key derivation function (such as HMAC, CMAC), etc., but is not limited thereto.

[0061] It should be noted that the above are only several exemplary implementation methods of generating a combined key and do not constitute a limitation of this specification. In more possible implementation methods, other methods can also be used to generate a combined key, and this specification does not limit this.

[0062] In addition, it should be noted that the above embodiment is described by taking the generation process of the combined key corresponding to a database service user as an example, and the generation process of the combined key corresponding to other database service users is similar and will not be repeated here.

[0063] After the combined key corresponding to each database service user is generated through the above embodiment, the combined key corresponding to each database service user can also be sent to the corresponding database user, so that each database service user can obtain the combined key corresponding to the database service provider.

[0064] It should be noted that in more possible implementations, each database service user can also generate a combined key corresponding to each database service provider based on the second subkey provided to each database service provider and the first subkey provided by each database service provider to the database service user. The generation process will be described in Figure 3 The corresponding embodiments are described in detail and will not be repeated here.

[0065] In addition, after the combined key corresponding to each database service user is generated through the above embodiment, data interaction can be performed with each database service user based on the combined key corresponding to each database service user through step 202.

[0066] In some embodiments, step 202 may be implemented in at least one of the following ways: In a possible implementation, for any database service user among multiple database service users, data reading can be implemented based on the combined key corresponding to the database service user.

[0067] That is, in response to receiving a data read request from the database service user, the data corresponding to the data read request can be encrypted based on the combined key corresponding to the database service user, so as to send the encrypted first encrypted data to the database service user.

[0068] Optionally, when there is a need to read data, the database service user may send a data acquisition request to the database service provider, and the data acquisition request may carry relevant information about the data to be acquired, so that the data corresponding to the data acquisition request can be determined based on the information carried by the data acquisition request; the database service provider can receive the data acquisition request sent by the database service user, thereby acquiring the data corresponding to the data service request from the database, and then encrypting the acquired data based on the combined key corresponding to the database service user to obtain first encrypted data, so that the first encrypted data can be sent to the database service user.

[0069] Optionally, after receiving the first encrypted data, the database service user may decrypt the first encrypted data based on the combined key to obtain unencrypted data, thereby realizing data reading.

[0070] In another possible implementation, for any database service user among multiple database service users, data writing can be implemented based on the combined key corresponding to the database service user.

[0071] That is, in response to receiving a data write request from the database service user, the second encrypted data carried in the data write request can be decrypted based on the combined key corresponding to the database service user to obtain the data to be written into the database.

[0072] Optionally, when there is a need to write data, the database service user may encrypt the data to be written based on the combined key corresponding to the database service user to obtain second encrypted data, and then send a data write request to the database service provider, and the data write request may carry the second encrypted data; the database service provider may receive the data write request sent by the database service user, and then decrypt the second encrypted data carried in the data write request based on the combined key corresponding to the database service user to obtain the data to be written into the database, and then perform corresponding data write operations in the database based on the data to be written.

[0073] The above embodiment mainly introduces the data processing flow of the database service provider. The data processing flow of the database service user is introduced below.

[0074] See also Figure 3 , Figure 3 is a flow chart of a data processing method provided by an exemplary embodiment. Figure 3 As shown, the method can be applied to a database service user, and the database service user can use services provided by multiple database service providers. The method includes: Step 301: Obtain a combined key corresponding to each database service provider. The combined key corresponding to each database service provider is generated based on a second subkey provided by a database user to each database service provider and a first subkey provided by each database service provider to a database service user.

[0075] Optionally, the database service user may provide a second subkey for each database service provider, and the second subkeys provided to different database service providers may be different. In addition, each database service provider may also provide a first subkey for the database service user, and the first subkeys provided by different database service providers may be different.

[0076] Optionally, for any database service provider among the multiple database service providers, the combined key corresponding to the database service provider can be generated based on the second subkey provided by the database service user to the database service provider and the first subkey provided by the database service provider to the database service user.

[0077] Step 302: Based on the combined key corresponding to each database service provider, data is exchanged with each database service provider respectively.

[0078] It should be noted that each database service provider will correspond to a combined key. When a database service user interacts with any database service provider, he or she can use the combined key corresponding to the database service provider to encrypt or decrypt the interactive data to ensure data security.

[0079] In introducing Figure 3 After the basic implementation of the illustrated embodiment, various optional embodiments are introduced below.

[0080] In some embodiments, the database service user may generate a second master key, and then generate a second subkey for each database service provider based on the second master key, and different database service providers may have different corresponding second subkeys.

[0081] In some embodiments, when generating the second master key, the second master key may be generated based on a second encryption algorithm and a second random number.

[0082] Optionally, a second encryption algorithm may be used to process the second random number to obtain a second master key.

[0083] Optionally, the second random number may be generated by a random number generator of the database service user, but is not limited thereto.

[0084] Optionally, the second encryption algorithm may be a symmetric encryption algorithm, such as an AES encryption algorithm, but not limited thereto; or, the second encryption algorithm may be an asymmetric encryption algorithm, such as an RSA encryption algorithm, an ECC encryption algorithm, but not limited thereto.

[0085] After the second master key is generated, a second subkey may be generated for each database service provider based on the generated second master key.

[0086] In some embodiments, a plurality of second sub-keys may be generated based on the derivation algorithm and the second master key.

[0087] Optionally, a derivation algorithm may be used to process the second master key to obtain a plurality of second sub-keys.

[0088] Optionally, the derivation algorithm may be HKDF, PBKDF2, an encryption-based key derivation function (such as HMAC, CMAC), etc., but is not limited thereto.

[0089] It should be noted that the generated multiple second subkeys can be distributed to multiple database service providers, each database service provider will be assigned a second subkey, and each database provider is assigned a different second subkey.

[0090] That is, the database service user may send the second subkey corresponding to each database provider to the corresponding database service provider, so that each database service provider may receive the second subkey corresponding to the database service user.

[0091] Optionally, the second subkey may be associated with second identification information, and the second identification information may be used to identify the second subkey. Different second subkeys may correspond to different second identification information.

[0092] Optionally, the second identification information may be a serial number, but is not limited thereto.

[0093] In some embodiments, the database service user may send the second subkey and second identification information corresponding to the database service provider to the database service provider when the database service user interacts with the database service provider for the first time about the second subkey. The database service provider may store the received second subkey and second identification information in association with each other, so that when the database service user subsequently interacts with the database service provider about the second subkey, the user only needs to send the second identification information of the second subkey. The database service provider may determine the second subkey corresponding to the received second identification information based on the stored information.

[0094] In some embodiments, the database service user may also receive the first subkey sent by each database service provider, wherein the first subkey is generated by each database service provider based on its own first master key. For specific generation methods, see Figure 2 The description in the corresponding embodiment will not be repeated here.

[0095] Optionally, the first subkey may be associated with first identification information, and the first identification information may be used to identify the first subkey. Different first subkeys may correspond to different first identification information.

[0096] Optionally, the first identification information may be a serial number, but is not limited thereto.

[0097] In some embodiments, the database service provider may send the first subkey and first identification information corresponding to the database service user to the database service user when the database service provider first exchanges the first subkey with the database service user. The database service user may associate and store the received first subkey and first identification information so that when the database service provider subsequently exchanges the first subkey with the database service user, it only needs to send the identification information of the first subkey, and the database service user can determine the first subkey corresponding to the received first identification information based on the stored information.

[0098] It should be noted that after the second subkey corresponding to each database service provider (i.e., the second subkey distributed to each database service provider by the database service user) and the first subkey corresponding to each database service provider (i.e., the first subkey sent to the database service user by each database service provider) are obtained through the above embodiment, the combined key corresponding to each database service provider can be obtained through step 301.

[0099] In some embodiments, for step 301, when obtaining the combined key corresponding to each database service provider, the combined key corresponding to each database service provider can be generated based on the second subkey provided by the database service user for each database service provider and the first subkey provided by each database service provider to the database service user.

[0100] In some embodiments, for any database service provider, a calculation may be performed based on the first subkey and the second subkey corresponding to the database service provider to obtain a combined key corresponding to the database service provider.

[0101] Optionally, a hash operation may be performed based on the first subkey and the second subkey corresponding to the database service provider to obtain the combined key corresponding to the database service provider. Alternatively, an XOR operation may be performed based on the first subkey and the second subkey corresponding to the database service provider to obtain the combined key corresponding to the database service provider.

[0102] Optionally, a series of calculations may be performed on the first subkey and the second subkey corresponding to the database service provider based on a key derivation function to obtain a combined key corresponding to the database service provider.

[0103] Optionally, the key derivation function may be HKDF, PBKDF2, an encryption-based key derivation function (such as HMAC, CMAC), etc., but is not limited thereto.

[0104] It should be noted that the above are only several exemplary implementation methods of generating a combined key and do not constitute a limitation of this specification. In more possible implementation methods, other methods can also be used to generate a combined key, and this specification does not limit this.

[0105] In addition, it should be noted that the above embodiment is described by taking the generation process of the combined key corresponding to one database service provider as an example, and the generation process of the combined key corresponding to other database service providers is similar and will not be repeated here.

[0106] In addition, it should be noted that the above embodiment is described by taking the database service user generating the combined key by itself as an example. In more possible implementations, the database service user may also receive the combined key sent by each database service provider. For any database service provider, the combined key corresponding to the database service provider is generated by the database service provider based on the second subkey provided by the database service user to the database service provider and the first subkey provided by the database service provider to the database service user. For the specific generation process, please refer to Figure 2 The corresponding embodiments will not be described in detail here.

[0107] After the combined key corresponding to each database service provider is obtained through the above embodiment, data interaction can be performed with each database service provider based on the combined key corresponding to each database service provider in step 302 .

[0108] In some embodiments, step 302 may be implemented in at least one of the following ways: In a possible implementation, for any database service provider among the multiple database service providers, data reading may be implemented based on the combined key corresponding to the database service provider.

[0109] That is, in response to receiving the first encrypted data sent by the database service provider based on the data acquisition request of the database service user, the first encrypted data can be decrypted based on the combined key corresponding to the database service provider to obtain the data requested by the database service user.

[0110] Optionally, when there is a need to read data, the database service user may send a data acquisition request to the database service provider, and the data acquisition request may carry relevant information about the data to be acquired, so that the data corresponding to the data acquisition request can be determined based on the information carried by the data acquisition request; the database service provider can receive the data acquisition request sent by the database service user, thereby acquiring the data corresponding to the data service request from the database, and then encrypting the acquired data based on the combined key corresponding to the database service provider to obtain first encrypted data, so that the first encrypted data can be sent to the database service user.

[0111] Optionally, after receiving the first encrypted data, the database service user may decrypt the first encrypted data based on the combined key to obtain unencrypted data, thereby realizing data reading.

[0112] In another possible implementation, for any database service provider among the multiple database service providers, data writing may be implemented based on the combined key corresponding to the database service provider.

[0113] That is, the data to be written into the database can be encrypted based on the combined key corresponding to the database service provider to obtain second encrypted data, and a data write request can be sent to the database service provider based on the second encrypted data.

[0114] Optionally, when there is a need to write data, the database service user may encrypt the data to be written based on the combined key corresponding to the database service provider to obtain second encrypted data, and then send a data write request to the database service provider, and the data write request may carry the second encrypted data; the database service provider may receive the data write request sent by the database service user, and then decrypt the second encrypted data carried in the data write request based on the combined key corresponding to the database service provider to obtain the data to be written into the database, and then perform corresponding data write operations in the database based on the data to be written.

[0115] See also Figure 4 , Figure 4 is a flowchart of a data processing method provided by an exemplary embodiment, such as Figure 4 As shown, the database service provider can provide services to three database service users, and the database service users can use the services provided by the three database service providers. Then, the database service provider can generate a first subkey for each database service user based on the first master key, which are respectively recorded as first subkey 1, first subkey 2, and first subkey 3; the database service user can generate a second subkey for each database service provider based on the second master key, which are respectively recorded as second subkey 1, second subkey 2, and second subkey 3. Figure 4 The database service provider and the database service user shown in FIG. 1 are a database service provider and a database service user. The first subkey generated by the database service provider for the database service user is the first subkey 1, and the second subkey generated by the database service user for the database service provider is the second subkey 1. Figure 4 The database service provider and the database service user shown in the figure can generate a combined key 1 based on the first subkey 1 and the second subkey 1, and the combined key 1 can be used for subsequent data interaction between the database service provider and the database service user.

[0116] It should be noted that by configuring different second subkeys for different database service providers and different first subkeys for different database service users, data isolation between different database service users can be ensured. Optionally, for some database service users with special needs, the same first subkey can be configured for different database service users. For example, for different departments in the same enterprise, there may be a situation where data needs to be shared. In this case, different departments in the enterprise can be used as different database service users, and the same first subkey can be configured for different database service users.

[0117] For ease of understanding, the following takes the interaction between a database service provider and a database service user as an example to further illustrate the database processing methods provided in this specification.

[0118] It should be made clear that the data processing method provided in this specification may involve the interaction between multiple database service providers and multiple database service users. For any database service user, it can form a group with each database service provider that provides services to it. The combination can correspond to one combined key, that is, the database service provider and the database service user in the combination can use the same method to generate the combined key; or, the combination can correspond to two combined keys, that is, the database service provider and the database service user in the combination can use different methods to generate the combined key. It should be noted that no matter how many combined keys the combination corresponds to, it must be ensured that the combined key is known to the database service provider and the database service user in the combination.

[0119] See also Figure 5 , Figure 5 is an interactive flow chart of a data processing method provided by an exemplary embodiment, such as Figure 5 As shown, the method includes: Step 501: The database service provider generates a first master key.

[0120] Step 502: The database service provider generates a first subkey for the database service user based on the first master key.

[0121] Step 503: The database service provider sends the generated first subkey to the database service user.

[0122] Step 504: The database service user generates a second master key.

[0123] Step 505: The database service user generates a second subkey for the database service provider based on the second master key.

[0124] Step 506: The database service user sends the generated second subkey to the database service provider.

[0125] Step 507: The database service provider and the database service user generate a combined key based on the first subkey and the second subkey respectively.

[0126] It should be noted that when the database service provider and the database service user generate a combined key based on the first subkey and the second subkey, they must use the same algorithm to ensure the consistency of the combined key generated by both parties.

[0127] It should be noted that step 507 is only explained by taking the database service provider and the database service user as examples based on the first subkey and the second subkey respectively. In more possible implementations, the database service provider can also generate a combined key based on the first subkey and the second subkey, and then send the generated combined key to the database service user. The database service user can receive the combined key sent by the database service provider without generating it by itself.

[0128] Step 508: The database service provider and the database service user exchange data based on the combined key.

[0129] It should be noted that Figure 5 The step numbers in the embodiment shown do not limit the order in which the steps are executed. Figure 5 Alternatively, steps 504 to 506 may be executed first and then steps 501 to 503. This specification does not limit the specific execution order.

[0130] In addition, it should be noted that Figure 5 The database service user described in the illustrated embodiment may be any one of a plurality of database service users, and the database service provider described may be any one of a plurality of database service providers. This embodiment only takes the interaction between a database service user and a database service provider as an example for explanation. The interaction between any database service user and any database service provider may refer to the solution provided in this embodiment, which will not be described in detail here.

[0131] In addition, it should be noted that Figure 5 This mainly describes the interaction process between the database service provider and the database service user. The specific implementation of each step can be found in Figure 2 and Figure 3 The corresponding embodiments will not be described in detail here.

[0132] The above embodiments mainly introduce optional implementation methods of generating a combined key and communicating based on the combined key. In more possible implementation methods, the key mentioned in the above embodiments may also involve an update process.

[0133] In some embodiments, each first subkey may be set with a validity period, and each first subkey may be effective within its own validity period. Optionally, the validity periods of different first subkeys may be the same or different.

[0134] In some embodiments, for any first subkey, when the validity period of the first subkey is reached, a new first subkey can be regenerated based on the first master key, and the new first subkey can be sent to the corresponding database service user.

[0135] Optionally, when sending the new first subkey to the corresponding database service user, the new first subkey and the first identification information corresponding to the original first subkey can be sent so that the database service user can associate and store the new first subkey based on the first identification information.

[0136] In some embodiments, the database service provider may also regenerate a new combined key based on the new first subkey and the second subkey provided by the corresponding database service user, so that it can subsequently interact with the corresponding database service user based on the new combined key.

[0137] In some embodiments, a buffer time may be set so that the database service provider can use the new combined key and the original combined key in parallel during the buffer time to perform data interaction with the corresponding database service user.

[0138] Optionally, when using a new combined key and the original combined key in parallel to interact with the corresponding database service user, the database service provider can choose the new combined key or the original combined key to encrypt the data, and the database service user can check whether the data is encrypted using the new combined key or the original combined key. If the new combined key is used, the database service user can use the new combined key for decryption; if the original combined key is used, the database service user can use the original combined key for decryption.

[0139] By setting the buffer time, it is ensured that different message streams can still be correctly decrypted and understood during the key switching process.

[0140] It should be noted that within the buffer time, the new combined key and the original combined key can be stored in the database service provider and the database service user at the same time. When the buffer time is exceeded, the stored original combined key can be deleted to reduce storage pressure.

[0141] In some embodiments, each second subkey may also be set with a validity period, and each second subkey may be effective within its own validity period. Optionally, the validity periods of different second subkeys may be the same or different.

[0142] In some embodiments, for any second subkey, the corresponding database service user can regenerate a new second subkey based on the second master key when the validity period of the second subkey expires, and send the new second subkey to the database service provider. Correspondingly, the database service provider can receive the second subkey resent by the corresponding database user when the validity period of the second subkey expires.

[0143] Optionally, when sending the new second subkey to the database service provider, the database service user may send the new second subkey and the second identification information corresponding to the original second subkey, so that the database service provider may associate and store the new second subkey based on the second identification information.

[0144] In some embodiments, the database service provider may also regenerate a new combined key based on the new second subkey and the first subkey provided to the corresponding database service user, so that the corresponding database service user may subsequently interact based on the new combined key.

[0145] In some embodiments, a buffer time may be set so that the database service provider can use the new combined key and the original combined key in parallel during the buffer time to perform data interaction with the corresponding database service user.

[0146] Optionally, when using a new combined key and the original combined key in parallel to interact with the corresponding database service user, the database service provider can choose the new combined key or the original combined key to encrypt the data, and the database service user can check whether the data is encrypted using the new combined key or the original combined key. If the new combined key is used, the database service user can use the new combined key for decryption; if the original combined key is used, the database service user can use the original combined key for decryption.

[0147] By setting the buffer time, it is ensured that different message streams can still be correctly decrypted and understood during the key switching process.

[0148] It should be noted that within the buffer time, the new combined key and the original combined key can be stored in the database service provider and the database service user at the same time. When the buffer time is exceeded, the stored original combined key can be deleted to reduce storage pressure.

[0149] Corresponding to the aforementioned method embodiments, this specification also provides corresponding equipment embodiments and device embodiments.

[0150] Figure 6is a schematic structural diagram of a first computing device provided by an exemplary embodiment. Figure 6 At the hardware level, the first computing device includes a processor 602, an internal bus 604, a network interface 606, a memory 608, and a non-volatile memory 610, and may also include hardware required for other tasks. One or more embodiments of this specification may be implemented based on software, such as the processor 602 reading the corresponding computer program from the non-volatile memory 610 into the memory 608 and then running it. Of course, in addition to the software implementation, one or more embodiments of this specification do not exclude other implementations, such as logic devices or a combination of software and hardware, etc., that is, the execution subject of the following processing flow is not limited to each logic unit, but can also be hardware or logic devices.

[0151] This manual also provides a data processing device, please refer to Figure 7 , Figure 7 is a block diagram of a data processing device provided by an exemplary embodiment. The data processing device can be applied to Figure 6 In the first computing device shown, the technical solution of the database service provider in this specification is implemented. The data processing device may include: A generating module 701, configured to generate a combined key corresponding to each database service user based on a first subkey provided by the database service provider for each database service user and a second subkey provided by each database service user for the database service provider; The interaction module 702 is used to interact with each database service user based on the combination key corresponding to each database service user.

[0152] In some embodiments, the interaction module 702, when used to interact with each database service user based on the combined key corresponding to each database service user, is used for at least one of the following: For any database service user among the multiple database service users, in response to receiving a data read request from the database service user, encrypting data corresponding to the data read request based on a combined key corresponding to the database service user, and sending first encrypted data obtained by encryption to the database service user; In response to receiving the data write request from the database service user, the second encrypted data carried in the data write request is decrypted based on the combined key corresponding to the database service user to obtain the data to be written into the database.

[0153] In some embodiments, the generating module 701 is further used to generate a first master key; The generating module 701 is further used to generate a first subkey for each database service user based on the first master key, and different database service users have different corresponding first subkeys.

[0154] In some embodiments, the apparatus further comprises: The sending module is used to send the first subkey corresponding to each database user to the corresponding database user.

[0155] In some embodiments, the generating module 701 is further configured to, for any first subkey, regenerate a new first subkey based on the first master key when the validity period of the first subkey reaches the end; The sending module is also used to send the new first subkey to the corresponding database user.

[0156] In some embodiments, the apparatus further comprises: The receiving module is used to receive the second subkey sent by each database service user, wherein the second subkey is generated by each database service user based on its own second master key.

[0157] In some embodiments, the receiving module is further used to receive, for any second subkey, a second subkey resent by the corresponding database user when the validity period of the second subkey expires, where the resent second subkey is newly generated based on the second master key.

[0158] In some embodiments, the generation module 701 is further configured to regenerate a new combined key when a new first subkey is generated or a new second subkey is received; The interaction module 702 is also used to use the new combined key and the original combined key in parallel during the buffer time to perform data interaction with the corresponding database service user.

[0159] In some embodiments, the sending module is further used to send the combined key corresponding to each database service user to the corresponding database user.

[0160] Figure 8 is a schematic structural diagram of a second computing device provided by an exemplary embodiment. Figure 8At the hardware level, the second computing device includes a processor 802, an internal bus 804, a network interface 806, a memory 808, and a non-volatile memory 810, and may also include hardware required for other tasks. One or more embodiments of this specification may be implemented based on software, such as the processor 802 reading the corresponding computer program from the non-volatile memory 810 into the memory 808 and then running it. Of course, in addition to the software implementation, one or more embodiments of this specification do not exclude other implementations, such as logic devices or a combination of software and hardware, etc., that is, the execution subject of the following processing flow is not limited to each logic unit, but can also be hardware or logic devices.

[0161] This manual also provides a data processing device, please refer to Fig. 9 , Fig. 9 is a block diagram of a data processing device provided by an exemplary embodiment. The data processing device can be applied to Figure 8 In the second computing device shown, the technical solution of the database service user in this specification is implemented. Among them, the data processing device may include: An acquisition module 901 is used to acquire a combined key corresponding to each database service provider, where the combined key corresponding to each database service provider is generated based on a second subkey provided by the database user for each database service provider and a first subkey provided by each database service provider for the database service user; The interaction module 902 is used to interact with each database service provider based on the combined key corresponding to each database service provider.

[0162] In some embodiments, the acquisition module 901, when used to acquire the combined key corresponding to each database service provider, is used for any of the following: Generate a combined key corresponding to each database service provider based on the second subkey provided by the database user for each database service provider and the first subkey provided by each database service provider for the database service user; Receive a combined key sent by each database service provider. For any database service provider, the combined key corresponding to the database service provider is generated by the database service provider based on the second subkey provided by the database service user to the database service provider and the first subkey provided by the database service provider to the database service user.

[0163] In some embodiments, the interaction module 902, when used to interact with each database service provider based on the combined key corresponding to each database service provider, is used for at least one of the following: For any database service provider among the multiple database service providers, in response to receiving first encrypted data sent by the database service provider based on the data acquisition request of the database service user, decrypt the first encrypted data based on the combined key corresponding to the database service provider to obtain the data requested by the database service user; The data to be written into the database is encrypted based on the combined key corresponding to the database service provider to obtain second encrypted data, and a data write request is sent to the database service provider based on the second encrypted data.

[0164] In some embodiments, the apparatus further comprises: A generating module, used for generating a second master key; The generating module is further used to generate a second subkey for each database service provider based on the second master key, and different database service providers have different corresponding second subkeys.

[0165] In some embodiments, the apparatus further comprises: The sending module is used to send the second subkey corresponding to each database provider to the corresponding database provider.

[0166] In some embodiments, the generating module is further configured to, for any second subkey, regenerate a new second subkey based on the second master key when the validity period of the second subkey is reached; The sending module is also used to send the new second subkey to the corresponding database provider.

[0167] In some embodiments, the apparatus further comprises: The receiving module is used to receive the first subkey sent by each database service provider, wherein the first subkey is generated by each database service provider based on its own first master key.

[0168] In some embodiments, the receiving module is further used to receive, for any first subkey, a first subkey resent by the corresponding database provider when the validity period of the first subkey expires, wherein the resent first subkey is newly generated based on the first master key.

[0169] In some embodiments, the generation module is further configured to regenerate a new combined key upon generating a new second subkey or receiving a new first subkey; The interaction module 902 is also used to use the new combined key and the original combined key in parallel during the buffer time to perform data interaction with the corresponding database service provider.

[0170] The systems, devices, modules or units described in the above embodiments may be implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer, which may be in the form of a personal computer, a laptop computer, a cellular phone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email transceiver, a game console, a tablet computer, a wearable device or a combination of any of these devices.

[0171] In a typical configuration, a computer includes one or more processors (Central Processing Unit, CPU), input / output interface, network interface and memory.

[0172] Memory may include non-permanent storage in a computer-readable medium, random access memory (RAM) and / or non-volatile memory such as read-only memory (ROM) or flash RAM. Memory is an example of a computer-readable medium.

[0173] Computer readable media include permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. Information can be computer readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, Phase Change Random Access Memory (PRAM), Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), other types of random access memory (RAM), Read-Only Memory (ROM), Electrically Erasable Programmable Read-Only Memory (EEPROM), Flash memory or other memory technology, Compact Disc Read-Only Memory (CD-ROM), Digital Video Disc (DVD) or other optical storage, magnetic cassettes, disk storage, quantum memory, graphene-based storage media or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. According to the definition in this article, computer-readable media does not include temporary computer-readable media (transitory media), such as modulated data signals and carrier waves.

[0174] In some embodiments, the present specification also provides a computer program product, including a computer program, which implements the data processing method provided in any embodiment of the present specification when the computer program is executed by a processor of a first computing device, or implements the data processing method provided in any embodiment of the present specification when the computer program is executed by a processor of a second computing device.

[0175] It should also be noted that the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, commodity or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, commodity or device. In the absence of more restrictions, the elements defined by the sentence "comprises a ..." do not exclude the existence of other identical elements in the process, method, commodity or device including the elements.

[0176] The above is a description of a specific embodiment of the specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recorded in the claims can be performed in an order different from that in the embodiments and still achieve the desired results. In addition, the processes depicted in the drawings do not necessarily require the specific order or continuous order shown to achieve the desired results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0177] The terms used in one or more embodiments of this specification are only for the purpose of describing specific embodiments, and are not intended to limit one or more embodiments of this specification. The singular forms of "a", "said" and "the" used in one or more embodiments of this specification and the appended claims are also intended to include plural forms, unless the context clearly indicates other meanings. It should also be understood that the term "and / or" used herein refers to and includes any or all possible combinations of one or more associated listed items.

[0178] It should be understood that although the terms first, second, third, etc. may be used to describe various information in one or more embodiments of this specification, these information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other. For example, without departing from the scope of one or more embodiments of this specification, the first information may also be referred to as the second information, and similarly, the second information may also be referred to as the first information. Depending on the context, the word "if" as used herein may be interpreted as "at the time of" or "when" or "in response to determining".

[0179] The above description is merely a preferred embodiment of one or more embodiments of the present specification and is not intended to limit one or more embodiments of the present specification. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of one or more embodiments of the present specification shall be included in the scope of protection of one or more embodiments of the present specification.

Claims

1. A data processing method, applied to a database service provider, the database service provider is used to provide services to multiple database service users, the method comprising: Generate a combined key corresponding to each database service user based on a first subkey provided by the database service provider for each database service user and a second subkey provided by each database service user for the database service provider; Based on the combined key corresponding to each database service user, data is exchanged with each database service user respectively.

2. The method according to claim 1, wherein the data interaction with each database service user based on the combined key corresponding to each database service user comprises at least one of the following: For any database service user among the multiple database service users, in response to receiving a data read request from the database service user, encrypting data corresponding to the data read request based on a combined key corresponding to the database service user, and sending first encrypted data obtained by encryption to the database service user; In response to receiving the data write request from the database service user, the second encrypted data carried in the data write request is decrypted based on the combined key corresponding to the database service user to obtain the data to be written into the database.

3. The method according to claim 1, before generating a combined key corresponding to each database service user based on the first subkey provided by the database service provider for each database service user and the second subkey provided by each database service user for the database service provider, the method further comprises: Generate a first master key; Based on the first master key, a first subkey is generated for each database service user, and different database service users have different corresponding first subkeys.

4. The method according to claim 3, after generating a first subkey for each database service user based on the first master key, the method further comprises: The first subkey corresponding to each database user is sent to the corresponding database user.

5. According to the method of claim 3, each first subkey is set with a validity period, and the method further comprises: For any first subkey, when the validity period of the first subkey reaches the end, a new first subkey is regenerated based on the first master key; The new first subkey is sent to the corresponding database user.

6. The method according to claim 1, before generating a combined key corresponding to each database service user based on a first subkey provided by the database service provider for each database service user and a second subkey provided by each database service user for the database service provider, the method further comprises: A second subkey sent by each database service user is received, wherein the second subkey is generated by each database service user based on the second master key of the respective database service user.

7. The method according to claim 6, wherein each second subkey is set with a validity period, and the method further comprises: For any second subkey, a second subkey resent by a corresponding database user when the validity period of the second subkey expires is received, wherein the resent second subkey is newly generated based on the second master key.

8. The method according to claim 5 or 6, further comprising: regenerate a new combined key when a new first subkey is generated or a new second subkey is received; During the buffer time, the new combined key and the original combined key are used in parallel to interact with the corresponding database service user.

9. The method according to claim 1, after generating a combined key corresponding to each database service user based on a first subkey provided by the database service provider for each database service user and a second subkey provided by each database service user for the database service provider, the method further comprises: The combined key corresponding to each database service consumer is sent to the corresponding database consumer.

10. A data processing method, applied to a database service user, wherein the services used by the database service user come from multiple database service providers, the method comprising: Obtaining a combined key corresponding to each database service provider, where the combined key corresponding to each database service provider is generated based on a second subkey provided by the database user for each database service provider and a first subkey provided by each database service provider for the database service user; Based on the combined key corresponding to each database service provider, data is exchanged with each database service provider respectively.

11. The method according to claim 10, wherein obtaining the combined key corresponding to each database service provider comprises any one of the following: Generate a combined key corresponding to each database service provider based on the second subkey provided by the database user for each database service provider and the first subkey provided by each database service provider for the database service user; Receive a combined key sent by each database service provider. For any database service provider, the combined key corresponding to the database service provider is generated by the database service provider based on the second subkey provided by the database service user to the database service provider and the first subkey provided by the database service provider to the database service user.

12. The method according to claim 10, wherein the data interaction with each database service provider based on the combined key corresponding to each database service provider comprises at least one of the following: For any database service provider among the multiple database service providers, in response to receiving first encrypted data sent by the database service provider based on the data acquisition request of the database service user, decrypt the first encrypted data based on the combined key corresponding to the database service provider to obtain the data requested by the database service user; The data to be written into the database is encrypted based on the combined key corresponding to the database service provider to obtain second encrypted data, and a data write request is sent to the database service provider based on the second encrypted data.

13. The method according to claim 10, before obtaining the combined key corresponding to each database service provider, the method further comprises: Generate a second master key; Based on the second master key, a second subkey is generated for each database service provider, and different database service providers have different corresponding second subkeys.

14. The method according to claim 13, after generating a second subkey for each database service provider based on the second master key, the method further comprises: The second subkey corresponding to each database provider is sent to the corresponding database provider.

15. The method according to claim 13, wherein each second subkey is set with a validity period, and the method further comprises: For any second subkey, when the validity period of the second subkey reaches the end, a new second subkey is regenerated based on the second master key; The new second subkey is sent to the corresponding database provider.

16. The method according to claim 10, before obtaining the combined key corresponding to each database service provider, the method further comprises: A first subkey sent by each database service provider is received, wherein the first subkey is generated by each database service provider based on its own first master key.

17. The method according to claim 16, wherein each first subkey is set with a validity period, and the method further comprises: For any first subkey, a first subkey resent by a corresponding database provider when the validity period of the first subkey expires is received, wherein the resent first subkey is newly generated based on the first master key.

18. The method according to claim 15 or 17, further comprising: regenerate a new combined key when a new second subkey is generated or a new first subkey is received; During the buffer time, the new combined key and the original combined key are used in parallel to exchange data with the corresponding database service provider.

19. A data processing device, applied to a database service provider, the database service provider is used to provide services to multiple database service users, the device comprising: A generating module, configured to generate a combined key corresponding to each database service user based on a first subkey provided by the database service provider for each database service user and a second subkey provided by each database service user for the database service provider; The interaction module is used to interact with each database service user based on the combined key corresponding to each database service user.

20. A data processing device, applied to a database service user, wherein the services used by the database service user come from multiple database service providers, the device comprising: an acquisition module, used to acquire a combined key corresponding to each database service provider, wherein the combined key corresponding to each database service provider is generated based on a second subkey provided by the database user for each database service provider and a first subkey provided by each database service provider for the database service user; The interaction module is used to interact with each database service provider based on the combined key corresponding to each database service provider.

21. A computing device, the computing device serving as a database service provider, comprising: processor; a memory for storing processor-executable instructions; The processor implements the method according to any one of claims 1 to 9 by running the executable instructions.

22. A second computing device, the second computing device serving as a database service user, comprising: processor; a memory for storing processor-executable instructions; The processor implements the method according to any one of claims 10-18 by running the executable instructions.

23. A computer-readable storage medium having computer instructions stored thereon, wherein when the computer instructions are executed by a processor, the steps of the method as described in any one of claims 1 to 9 are implemented, or when the computer instructions are executed by a processor, the steps of the method as described in any one of claims 10 to 18 are implemented.

Images