Data access control method, equipment, device and storage medium
By using symmetric key-based proxy re-encryption technology and blockchain network in the 6G data plane, the problems of access authorization control and data privacy protection between heterogeneous databases are solved, and efficient data access authorization and privacy protection are achieved.
Patent Information
- Application Number
- CN202310620351.1
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2023-05-29
- Publication Date
- 2024-11-29
AI Technical Summary
There are technical problems with how different local databases in the 6G data plane to achieve access authorization control from heterogeneous databases, while ensuring the localization of data privacy protection.
Use re-encryption keys generated based on symmetric keys for proxy re-encryption, re-encrypt the encrypted cipher text of the target data through the proxy server, and send it to the data requester, and use the blockchain network to store the authorization table to ensure data access authorization security and privacy.
Access authorization control between different local databases is realized, which ensures the localization of data privacy protection, and significantly reduces the computing cost of encryption and re-encryption algorithms and improves computing efficiency.
Smart Images

Figure CN119052793A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of wireless communication technology, and in particular to a data access control method, device, apparatus and storage medium. Background Art
[0002] The data sources of the 6th Generation Mobile Communication Technology (6G) data plane are diversified and heterogeneous. How to control the access authorization from heterogeneous databases in different local databases while ensuring the localization of data privacy protection is a technical problem that needs to be solved in the design of the 6G data plane. Summary of the invention
[0003] The embodiments of the present application provide a data access control method, device, apparatus and storage medium to implement access authorization control of different local databases to heterogeneous databases while ensuring the localization of data privacy protection.
[0004] In a first aspect, an embodiment of the present application provides a data access control method, which is applied to a proxy server, comprising:
[0005] receiving a data access request sent by a data requester, wherein the data access request is used to request target data of a data collector;
[0006] After determining that the data requester is a user allowed to access the target data, re-encrypt the encrypted ciphertext of the target data according to the re-encryption key corresponding to the data requester in the first authorization table of the data collector to generate the re-encrypted ciphertext of the target data; wherein the first authorization table contains the re-encryption key corresponding to the authorized user, and the re-encryption keys in the first authorization table are all generated based on the symmetric key;
[0007] The re-encrypted ciphertext of the target data is sent to the data requester.
[0008] In some embodiments, determining that the data requester is a user allowed to access the target data includes:
[0009] Determining, according to the first authorization form or the second authorization form of the data collector, that the data requester is a user permitted to access the target data;
[0010] The first authorization table or the second authorization table contains identification of data that the authorized user is allowed to access.
[0011] In some embodiments, the method further comprises:
[0012] Obtain the first authorization list from the blockchain network; or obtain the first authorization list and the second authorization list from the blockchain network.
[0013] In some embodiments, in the first authorization table, different data that the same authorized user is allowed to access corresponds to different re-encryption keys.
[0014] In some embodiments, re-encrypting the encrypted ciphertext of the target data according to the re-encryption key corresponding to the data requester in the first authorization table of the data collector includes:
[0015] The encrypted ciphertext of the target data is re-encrypted according to the data requester in the first authorization table and the re-encryption key corresponding to the target data.
[0016] In some embodiments, the method further comprises:
[0017] Receive the encrypted ciphertext of the target data sent by the data collector.
[0018] In a second aspect, an embodiment of the present application further provides a data access control method, which is applied to a data collector, comprising:
[0019] Determine the symmetric key used to encrypt the data;
[0020] Based on the symmetric key and the public key of the authorized user, a re-encryption key corresponding to the authorized user is generated.
[0021] In some embodiments, the method further comprises:
[0022] Generate a first authorization table for the data collector, wherein the first authorization table includes a re-encryption key corresponding to the authorized user;
[0023] The first authorization form is encrypted using the private key of the data collector and then uploaded to the blockchain network.
[0024] In some embodiments, the first authorization table also includes an identification of data that the authorized user is allowed to access.
[0025] In some embodiments, the method further comprises:
[0026] generating a second authorization form for the data collector, wherein the second authorization form includes identification of data that the authorized user is allowed to access;
[0027] The second authorization form is encrypted using the private key of the data collector and then uploaded to the blockchain network.
[0028] In some embodiments, in the first authorization table, different data that the same authorized user is allowed to access corresponds to different re-encryption keys.
[0029] In a third aspect, an embodiment of the present application further provides a data access control method, which is applied to a data requester, comprising:
[0030] Sending a data access request to the proxy server, wherein the data access request is used to request target data of the data collector;
[0031] Receiving the re-encrypted ciphertext of the target data sent by the proxy server;
[0032] The re-encrypted ciphertext of the target data is decrypted using the private key of the data requester to obtain the target data.
[0033] In a fourth aspect, an embodiment of the present application further provides a proxy server, including a memory, a transceiver, and a processor;
[0034] A memory for storing a computer program; a transceiver for transmitting and receiving data under the control of the processor; and a processor for reading the computer program in the memory and performing the following operations:
[0035] receiving a data access request sent by a data requester, wherein the data access request is used to request target data of a data collector;
[0036] After determining that the data requester is a user allowed to access the target data, re-encrypt the encrypted ciphertext of the target data according to the re-encryption key corresponding to the data requester in the first authorization table of the data collector to generate the re-encrypted ciphertext of the target data; wherein the first authorization table contains the re-encryption key corresponding to the authorized user, and the re-encryption keys in the first authorization table are all generated based on the symmetric key;
[0037] The re-encrypted ciphertext of the target data is sent to the data requester.
[0038] In some embodiments, determining that the data requester is a user allowed to access the target data includes:
[0039] Determining, according to the first authorization form or the second authorization form of the data collector, that the data requester is a user permitted to access the target data;
[0040] The first authorization table or the second authorization table contains identification of data that the authorized user is allowed to access.
[0041] In some embodiments, the operations further include:
[0042] Obtain the first authorization list from the blockchain network; or obtain the first authorization list and the second authorization list from the blockchain network.
[0043] In some embodiments, in the first authorization table, different data that the same authorized user is allowed to access corresponds to different re-encryption keys.
[0044] In some embodiments, re-encrypting the encrypted ciphertext of the target data according to the re-encryption key corresponding to the data requester in the first authorization table of the data collector includes:
[0045] The encrypted ciphertext of the target data is re-encrypted according to the data requester in the first authorization table and the re-encryption key corresponding to the target data.
[0046] In some embodiments, the operations further include:
[0047] Receive the encrypted ciphertext of the target data sent by the data collector.
[0048] In a fifth aspect, an embodiment of the present application further provides a data collector, including a memory, a transceiver, and a processor;
[0049] A memory for storing a computer program; a transceiver for transmitting and receiving data under the control of the processor; and a processor for reading the computer program in the memory and performing the following operations:
[0050] Determine the symmetric key used to encrypt the data;
[0051] Based on the symmetric key and the public key of the authorized user, a re-encryption key corresponding to the authorized user is generated.
[0052] In some embodiments, the operations further include:
[0053] Generate a first authorization table for the data collector, wherein the first authorization table includes a re-encryption key corresponding to the authorized user;
[0054] The first authorization form is encrypted using the private key of the data collector and then uploaded to the blockchain network.
[0055] In some embodiments, the first authorization table also includes an identification of data that the authorized user is allowed to access.
[0056] In some embodiments, the operations further include:
[0057] generating a second authorization form for the data collector, wherein the second authorization form includes identification of data that the authorized user is allowed to access;
[0058] The second authorization form is encrypted using the private key of the data collector and then uploaded to the blockchain network.
[0059] In some embodiments, in the first authorization table, different data that the same authorized user is allowed to access corresponds to different re-encryption keys.
[0060] In a sixth aspect, an embodiment of the present application further provides a data requester, including a memory, a transceiver, and a processor;
[0061] A memory for storing a computer program; a transceiver for transmitting and receiving data under the control of the processor; and a processor for reading the computer program in the memory and performing the following operations:
[0062] Sending a data access request to the proxy server, wherein the data access request is used to request target data of the data collector;
[0063] Receiving the re-encrypted ciphertext of the target data sent by the proxy server;
[0064] The re-encrypted ciphertext of the target data is decrypted using the private key of the data requester to obtain the target data.
[0065] In a seventh aspect, an embodiment of the present application further provides a data access control device, including:
[0066] A first receiving unit, configured to receive a data access request sent by a data requester, wherein the data access request is used to request target data of a data collector;
[0067] a re-encryption unit, configured to re-encrypt the encrypted ciphertext of the target data according to the re-encryption key corresponding to the data requester in the first authorization table of the data collector after determining that the data requester is a user allowed to access the target data, so as to generate the re-encrypted ciphertext of the target data; wherein the first authorization table contains the re-encryption key corresponding to the authorized user, and the re-encryption keys in the first authorization table are all generated based on the symmetric key;
[0068] The first sending unit is used to send the re-encrypted ciphertext of the target data to the data requester.
[0069] In some embodiments, determining that the data requester is a user allowed to access the target data includes:
[0070] Determining, according to the first authorization form or the second authorization form of the data collector, that the data requester is a user permitted to access the target data;
[0071] The first authorization table or the second authorization table contains identification of data that the authorized user is allowed to access.
[0072] In some embodiments, the apparatus further comprises an acquisition unit, configured to:
[0073] Obtain the first authorization list from the blockchain network; or obtain the first authorization list and the second authorization list from the blockchain network.
[0074] In some embodiments, in the first authorization table, different data that the same authorized user is allowed to access corresponds to different re-encryption keys.
[0075] In some embodiments, re-encrypting the encrypted ciphertext of the target data according to the re-encryption key corresponding to the data requester in the first authorization table of the data collector includes:
[0076] The encrypted ciphertext of the target data is re-encrypted according to the data requester in the first authorization table and the re-encryption key corresponding to the target data.
[0077] In some embodiments, the first receiving unit is further configured to:
[0078] Receive the encrypted ciphertext of the target data sent by the data collector.
[0079] In an eighth aspect, an embodiment of the present application further provides a data access control device, including:
[0080] A determination unit, used to determine a symmetric key used to encrypt data;
[0081] The re-encryption key generation unit is used to generate a re-encryption key corresponding to the authorized user based on the symmetric key and the public key of the authorized user.
[0082] In some embodiments, the apparatus further comprises:
[0083] A first authorization table generating unit, used to generate a first authorization table of the data collector, wherein the first authorization table contains a re-encryption key corresponding to the authorized user;
[0084] The first uploading unit is used to encrypt the first authorization form using the private key of the data collector and then upload it to the blockchain network.
[0085] In some embodiments, the first authorization table also includes an identification of data that the authorized user is allowed to access.
[0086] In some embodiments, the apparatus further comprises:
[0087] A second authorization table generating unit, used to generate a second authorization table for the data collector, wherein the second authorization table contains identifications of data that the authorized user is allowed to access;
[0088] The second uploading unit is used to encrypt the second authorization form using the private key of the data collector and then upload it to the blockchain network.
[0089] In some embodiments, in the first authorization table, different data that the same authorized user is allowed to access corresponds to different re-encryption keys.
[0090] In a ninth aspect, an embodiment of the present application further provides a data access control device, including:
[0091] A second sending unit, used to send a data access request to the proxy server, wherein the data access request is used to request target data of the data collector;
[0092] A second receiving unit, configured to receive the re-encrypted ciphertext of the target data sent by the proxy server;
[0093] The decryption unit is used to decrypt the re-encrypted ciphertext of the target data using the private key of the data requester to obtain the target data.
[0094] In the tenth aspect, an embodiment of the present application also provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, and the computer program is used to enable a computer to execute the data access control method described in the first aspect, or execute the data access control method described in the second aspect, or execute the data access control method described in the third aspect.
[0095] In the eleventh aspect, an embodiment of the present application also provides a communication device, in which a computer program is stored, and the computer program is used to enable the communication device to execute the data access control method described in the first aspect as described above, or execute the data access control method described in the second aspect as described above, or execute the data access control method described in the third aspect as described above.
[0096] In the twelfth aspect, an embodiment of the present application also provides a processor-readable storage medium, wherein the processor-readable storage medium stores a computer program, and the computer program is used to enable the processor to execute the data access control method described in the first aspect as described above, or execute the data access control method described in the second aspect as described above, or execute the data access control method described in the third aspect as described above.
[0097] In the thirteenth aspect, an embodiment of the present application also provides a chip product, in which a computer program is stored, and the computer program is used to enable the chip product to execute the data access control method described in the first aspect as described above, or execute the data access control method described in the second aspect as described above, or execute the data access control method described in the third aspect as described above.
[0098] The data access control method, device, apparatus and storage medium provided in the embodiments of the present application can perform proxy re-encryption by using a re-encryption key generated based on a symmetric key, which can not only realize access authorization control of different local databases for heterogeneous databases and ensure the localization of data privacy protection, but also can significantly reduce the computational cost of encryption and re-encryption algorithms and improve the computational efficiency of the algorithms. BRIEF DESCRIPTION OF THE DRAWINGS
[0099] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the related technologies, the following is a brief introduction to the drawings required for use in the embodiments or the related technical descriptions. Obviously, the drawings described below are some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.
[0100] Figure 1 One of the flow charts of the data access control method provided in the embodiment of the present application;
[0101] Figure 2 The second flowchart of the data access control method provided in the embodiment of the present application;
[0102] Figure 3 The third flowchart of the data access control method provided in the embodiment of the present application;
[0103] Figure 4 An example diagram of data access control provided in an embodiment of the present application;
[0104] Figure 5 A schematic diagram of the structure of a proxy server provided in an embodiment of the present application;
[0105] Figure 6 A schematic diagram of the structure of the data collector provided in the embodiment of the present application;
[0106] Figure 7 A schematic diagram of the structure of a data requester provided in an embodiment of the present application;
[0107] Figure 8 One of the structural diagrams of the data access control device provided in the embodiment of the present application;
[0108] Fig. 9The second structural diagram of the data access control device provided in the embodiment of the present application;
[0109] Fig.10 This is a third structural diagram of the data access control device provided in an embodiment of the present application. DETAILED DESCRIPTION
[0110] In the embodiments of the present application, the term "and / or" describes the association relationship of the associated objects, indicating that three relationships may exist. For example, A and / or B may represent: A exists alone, A and B exist at the same time, and B exists alone. The character " / " generally indicates that the associated objects before and after are in an "or" relationship.
[0111] In the embodiments of the present application, the term "plurality" refers to two or more than two, and other quantifiers are similar.
[0112] In the embodiments of the present application, the terms "first", "second", etc. are used to distinguish similar objects, and are not used to describe a specific order or sequence. It should be understood that the terms used in this way can be interchangeable under appropriate circumstances, so that the embodiments of the present application can be implemented in an order other than those illustrated or described here, and the objects distinguished by "first" and "second" are generally of the same type, and the number of objects is not limited. For example, the first object can be one or more.
[0113] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.
[0114] In order to facilitate a clearer understanding of the technical solutions of the embodiments of the present application, some technical contents related to the embodiments of the present application are first introduced.
[0115] 1. 6G data plane.
[0116] The data in the 5th Generation Mobile Communication Technology (5G) network is mostly point-to-point, while the 6G network needs to integrate multiple networks and realize cross-domain and cross-system communication. The data in the network is also distributed. For example, perception data, artificial intelligence (AI) data, network behavior and status data, etc. from different devices will eventually converge to one device for calculation, so the 6G network needs to support any topology structure; and the 5G network is based on a business-centric architecture design, which creates data islands, resulting in low data quality and utilization efficiency, becoming the main bottleneck for data collection and sharing, and much of the data in 5G is one-time and is almost not stored, such as measurement information reported by the terminal, but this information can be used by endogenous AI in 6G to improve user experience and optimize network performance, etc., and there are many applications that need to access the same data, so the 6G data plane can provide a global mechanism to persist data.
[0117] However, the data sources of the 6G data plane are diversified and heterogeneous. How to control the access authorization from heterogeneous databases in different local databases while ensuring the localization of data privacy protection is a technical problem that needs to be solved in the design of the 6G data plane.
[0118] 2. Proxy re-encryption (PRE) technology.
[0119] Proxy re-encryption is considered to be a flexible data access control cryptographic system that can provide flexible data access authorization for encrypted data according to user needs. Specifically, the semi-trusted proxy in proxy re-encryption can convert the ciphertext encrypted by the data owner into the ciphertext that can be decrypted by the designated data recipient, and the proxy cannot obtain the data owner's information about the plaintext and private key.
[0120] At the same time, proxy re-encryption technology is an encryption method that can securely convert ciphertext. For example, proxy re-encryption technology can convert the ciphertext uploaded by user A using his public key into another form of ciphertext, so that user B can decrypt the converted ciphertext with his private key, and no corresponding plaintext information will be leaked during the entire conversion process.
[0121] The embodiments of the present application provide a proxy re-encryption access control mechanism based on symmetric key encryption. The intermediate access node will not know the user data, but can authorize access based on ciphertext, so that different local databases can implement access authorization control for heterogeneous databases while ensuring the localization of data privacy protection.
[0122] The technical solutions provided in the embodiments of the present application can be applicable to a variety of systems, and the present application is not limited to this. For example, it can be applicable to 5G systems or future 6G systems.
[0123] Figure 1 One of the flow diagrams of the data access control method provided in the embodiment of the present application, the method can be applied to a proxy server, such as Figure 1 As shown, the method comprises the following steps:
[0124] Step 100: Receive a data access request sent by a data requester, where the data access request is used to request target data from a data collector.
[0125] Step 101. After determining that the data requester is a user allowed to access the target data, the encrypted ciphertext of the target data is re-encrypted according to the re-encryption key corresponding to the data requester in the first authorization table of the data collector to generate a re-encrypted ciphertext of the target data; wherein the first authorization table contains the re-encryption key corresponding to the authorized user, and the re-encryption keys in the first authorization table are all generated based on the symmetric key.
[0126] Step 102: Send the re-encrypted ciphertext of the target data to the data requester.
[0127] Specifically, a proxy server (PS) is an entity or device for performing proxy re-encryption and access control functions, which can be part of the data processing function in the data plane. In some embodiments, the proxy server can also have other names, which are not limited in this application, as long as similar functions can be achieved.
[0128] A data requester (DR) is an entity or device that requests access to data, which may be a client or data consumer in the data plane. In some embodiments, the data requester may also have other titles, which are not limited in this application, as long as they are similar roles.
[0129] The data collector (DC) (or data owner) is an entity or device that plays a data collection role in the data plane, and authorizes the data access control function to the proxy server. In some embodiments, the data collector may also have other titles, which are not limited in this application, as long as they are similar roles.
[0130] When a data requester needs to access the target data of a data collector, he can send a data access request to the proxy server, and the data access request carries relevant information for requesting access to the target data, such as: identification information of the data collector, identification information of the data requester, identification information of the target data, etc. The target data can be any data that the data requester requires access to.
[0131] After the proxy server receives the data access request from the data requester, it can first determine whether the data requester is allowed to access the requested target data, for example, it can check the access rights of the data requester, the authorized users of the data collector, or the data authorized by the data collector for different users to access.
[0132] After determining that the data requester is a user allowed to access the target data, the proxy server can search the first authorization table of the data collector for the re-encryption key corresponding to the data requester, so that the proxy server can re-encrypt the encrypted ciphertext of the target data according to the re-encryption key corresponding to the data requester, and after generating the re-encrypted ciphertext of the target data, send the re-encrypted ciphertext to the data requester so that the data requester can decrypt the re-encrypted ciphertext to obtain the target data.
[0133] In this application, the re-encryption keys in the first authorization table of the data collector are all generated based on the symmetric key. In some embodiments, the public key of a certain authorized user and the symmetric key used to encrypt the plaintext data can be used to generate the re-encryption key corresponding to the authorized user. By adopting a symmetric encryption algorithm to encrypt a large amount of data, and using the public key to directly encrypt the symmetric key as the re-encryption key, the symmetric key is encrypted only once, which can reduce the computing cost and improve the computing efficiency.
[0134] The first authorization table of the data collector may include re-encryption keys corresponding to one or more authorized users. Table 1 illustrates a form of the first authorization table, as shown in Table 1, where USERID is the user's identifier, NAME represents the user, and REKEY is the user's re-encryption key.
[0135] Table 1 First Authorization Form 1
[0136] USERID NAME REKEY 1 Alice dxvsd 2 Bob csvr 3 Mary Cvt56
[0137] It should be noted that the key generation algorithm and the specific algorithm used for data encryption or re-encryption in each embodiment of the present application are not limited, and existing or future algorithms that can achieve corresponding functions known to those skilled in the art can be applied here. Correspondingly, the specific algorithm used to decrypt the re-encrypted ciphertext is not limited in the present application.
[0138] The data access control method provided in the embodiment of the present application performs proxy re-encryption through a re-encryption key generated based on a symmetric key. This can not only implement access authorization control of different local databases for heterogeneous databases and ensure the localization of data privacy protection, but also can significantly reduce the computational cost of encryption and re-encryption algorithms and improve the computational efficiency of the algorithms.
[0139] In some embodiments, determining that the data requester is a user allowed to access the target data includes:
[0140] Determining, according to the first authorization form or the second authorization form of the data collector, that the data requester is a user permitted to access the target data;
[0141] The first authorization table or the second authorization table contains identification of data that the authorized user is allowed to access.
[0142] Specifically, in some embodiments, the first authorization list of the data collector also includes identification of data that the authorized user is allowed to access, and the proxy server can determine whether the data requester is allowed to access the requested target data based on the first authorization list.
[0143] Table 2 illustrates another form of the first authorization table, as shown in Table 2, where USERID is the user's ID, NAME represents the user, REKEY is the user's re-encryption key, and TID is the data tuple name. For example, a row with USERID 1 indicates that the authorized user with user ID 1 is allowed to access data S1 and S4, and the re-encryption key corresponding to the user is dxvsd.
[0144] Form 2 First Authorization Form 2
[0145] USERID NAME TID REKEY 1 Alice S1 S4 dxvsd 2 Bob S2 Sf467 3 Mary S1 S3 FWf
[0146] In some embodiments, the proxy server may determine whether the data requester is allowed to access the requested target data based on a second authorization list of the data collector, where the second authorization list includes identifiers of data that the authorized user is allowed to access.
[0147] Table 3 illustrates a form of the second authorization table, as shown in Table 3, where USERID is the user's ID and TID is the data tuple name. For example, a row with USERID 1 indicates that the authorized user with user ID 1 is allowed to access data S1 and S4.
[0148] Table 3 Second authorization table
[0149]
[0150]
[0151] In some embodiments, in the first authorization table, different data that the same authorized user is allowed to access respectively corresponds to different re-encryption keys.
[0152] Specifically, when the data collector generates re-encryption keys for different authorized users, a re-encryption key can be generated for each authorized user, but this may lead to a problem: if the encryption key of a certain data is leaked, the data requested by the entire data requester will be leaked. To avoid this problem, different re-encryption keys can be created for different data tuples.
[0153] Table 4 illustrates another form of the first authorization table, as shown in Table 4, where USERID is the user's ID, NAME represents the user, REKEY is the user's re-encryption key, and TID is the data tuple name. For example, in a row where USERID is 1, the authorized user with user ID 1 is allowed to access data S1 and S4, and S1 and S4 correspond to different re-encryption keys, respectively.
[0154] In some embodiments, a public key of an authorized user and a symmetric key used to encrypt a certain plaintext data may be used to generate a re-encryption key corresponding to the authorized user and the plaintext data. For example, for a user with a user ID of 1 in Table 4, the re-encryption key corresponding to the data S1 that the user is allowed to access may be generated using the public key of the user and the symmetric key used to encrypt the data S1.
[0155] In some embodiments, for the case where each authorized user in Table 1 corresponds to only one re-encryption key, the same symmetric key can be used to encrypt all plaintext data, and then based on the symmetric key and the public keys of different authorized users, re-encryption keys corresponding to different authorized users are generated accordingly.
[0156] Table 4 First Authorization Form 3
[0157]
[0158]
[0159] In some embodiments, the encrypted ciphertext of the target data is re-encrypted according to the re-encryption key corresponding to the data requester in the first authorization table of the data collector, including:
[0160] The encrypted ciphertext of the target data is re-encrypted according to the re-encryption key corresponding to the data requester and the target data in the first authorization table.
[0161] For example, assuming that the data collector's first authorization list is in the form of Table 4, the data requester "Alice" requests access to the data S1 of the data collector. After confirming that the data requester "Alice" can access the data S1, the proxy server can determine the corresponding re-encryption key based on the data collector's first authorization list, that is, the re-encryption key dxvsd corresponding to the user "Alice" and data S1 in Table 4, so that the encrypted ciphertext of the data S1 can be re-encrypted using the re-encryption key, and the re-encrypted ciphertext can be sent to the data requester "Alice".
[0162] In the embodiment of the present application, the proxy server does not specifically limit the method for obtaining the first authorization list and the second authorization list of the data collector. For example, the data collector may send them to the proxy server, or the proxy server may obtain them from a trusted third party, and so on.
[0163] In some embodiments, the method further includes: obtaining a first authorization list from the blockchain network; or obtaining the first authorization list and the second authorization list from the blockchain network.
[0164] Specifically, the data collector can upload the generated first authorization form (or the first authorization form and the second authorization form) to the blockchain network. Using the blockchain network as a trusted third party to save the authorization form can avoid information loss due to single point failure. In addition, using blockchain technology to save the authorization form can ensure the non-tamperability of the authorization form and reduce the risk of privacy leakage.
[0165] In the embodiment of the present application, the proxy server does not specifically limit the method for obtaining the encrypted ciphertext of the target data. For example, the data collector may send it to the proxy server, or the proxy server may obtain it from a trusted third party, and so on.
[0166] In some embodiments, the method further includes: receiving an encrypted ciphertext of the target data sent by the data collector. That is, the data collector can directly send the target data to the proxy server after encrypting it.
[0167] In some embodiments, a key generation center can generate the keys required by the data collector and the data requester, for example, the public key, private key, and symmetric key of the data collector and the data requester.
[0168] In some embodiments, the key generation center may have other names, which is not limited in the present application, as long as it is an entity or device that can implement similar key generation and management functions.
[0169] Figure 2 The second flow chart of the data access control method provided in the embodiment of the present application is as follows. The method can be applied to data collectors, such as Figure 2 As shown, the method comprises the following steps:
[0170] Step 200: Determine the symmetric key used to encrypt data.
[0171] Step 201: Generate a re-encryption key corresponding to the authorized user based on the symmetric key and the public key of the authorized user.
[0172] Specifically, in an embodiment of the present application, the data collector may use the same symmetric key to encrypt different data (ie, plaintext data), or may use different symmetric keys to encrypt different data respectively.
[0173] When the symmetric key used for different data is the same, the data collector can use the same symmetric key and the public keys of different authorized users to generate re-encryption keys corresponding to different authorized users, as shown in Table 1.
[0174] When different data use different symmetric keys, the data collector can use the symmetric key of the corresponding data and the public keys of different authorized users to generate re-encryption keys corresponding to different authorized users and different data, as shown in Table 4.
[0175] The data access control method provided in the embodiment of the present application, by generating a re-encryption key based on a symmetric key for proxy re-encryption, can not only realize the access authorization control of different local databases for heterogeneous databases and ensure the localization of data privacy protection, but also can significantly reduce the computational cost of encryption and re-encryption algorithms and improve the computational efficiency of the algorithms.
[0176] In some embodiments, the method further comprises:
[0177] Generate a first authorization table for the data collector, where the first authorization table contains a re-encryption key corresponding to the authorized user;
[0178] The first authorization form is encrypted using the data collector’s private key and uploaded to the blockchain network.
[0179] Specifically, the data collector may generate a first authorization table based on the generated re-encryption keys corresponding to different authorized users.
[0180] In some embodiments, each authorized user in the first authorization table corresponds to a re-encryption key, as shown in Table 1.
[0181] In some embodiments, in the first authorization table, different data that the same authorized user is allowed to access corresponds to different re-encryption keys, as shown in Table 4.
[0182] In some embodiments, the first authorization table may also include identification of data that the authorized user is allowed to access.
[0183] The data collector can upload the generated first authorization form to the blockchain network. Using the blockchain network as a trusted third party to save the authorization form can avoid information loss due to single point failure. In addition, using blockchain technology to save the authorization form can ensure that the authorization form cannot be tampered with and reduce the risk of privacy leakage.
[0184] Before uploading the first authorization form to the blockchain network, the data collector may encrypt the first authorization form using his own private key.
[0185] In some embodiments, the method further comprises:
[0186] generating a second authorization form for the data collector, the second authorization form including identification of data that the authorized user is allowed to access;
[0187] The second authorization form is encrypted using the data collector’s private key and uploaded to the blockchain network.
[0188] Specifically, when the data collector generates the second authorization form, the data collector can also upload the generated second authorization form to the blockchain network, and use the blockchain network as a trusted third party to store the authorization form. Before uploading the second authorization form to the blockchain network, the data collector can encrypt the second authorization form using its own private key.
[0189] Figure 3 The third flow chart of the data access control method provided in the embodiment of the present application is as follows. The method can be applied to data requesters, such as Figure 3 As shown, the method comprises the following steps:
[0190] Step 300: Send a data access request to the proxy server, where the data access request is used to request the target data of the data collector.
[0191] Step 301: Receive the re-encrypted ciphertext of the target data sent by the proxy server.
[0192] Step 302: Use the private key of the data requester to decrypt the re-encrypted ciphertext of the target data to obtain the target data.
[0193] Specifically, when a data requester needs to access the target data of a data collector, he can send a data access request to the proxy server, and the data access request carries relevant information for requesting access to the target data, such as identification information of the data collector, identification information of the data requester, identification information of the target data, etc. The target data can be any data that the data requester requires access to.
[0194] After the proxy server receives the data access request from the data requester and determines that the data requester is a user allowed to access the target data, the proxy server can search the first authorization table of the data collector for the re-encryption key corresponding to the data requester, so that the proxy server can re-encrypt the encrypted ciphertext of the target data according to the re-encryption key corresponding to the data requester, and after generating the re-encrypted ciphertext of the target data, send the re-encrypted ciphertext to the data requester.
[0195] After receiving the re-encrypted ciphertext of the target data sent by the proxy server, the data requester can use its own private key to decrypt the re-encrypted ciphertext to obtain the required target data.
[0196] The data access control method provided in the embodiment of the present application performs proxy re-encryption through a re-encryption key generated based on a symmetric key and a user public key. This can not only achieve access authorization control of different local databases for heterogeneous databases and ensure the localization of data privacy protection, but also the data requester can use his own private key to decrypt the re-encrypted ciphertext, which can significantly reduce the computational cost of the decryption algorithm and improve the computational efficiency of the algorithm.
[0197] The methods provided in the embodiments of the present application are based on the same application concept, so the implementation of each method can refer to each other, and the repeated parts will not be repeated.
[0198] The following describes the methods provided in the above embodiments of the present application by using examples of specific application scenarios.
[0199] Example 1: This example uses symmetric key for proxy re-encryption and uses blockchain technology to save the authorization table, which ensures that the authorization table cannot be tampered with and reduces the risk of privacy leakage.
[0200] Figure 4 The data access control example diagram provided in the embodiment of the present application is as follows: Figure 4 As shown, there are four entities involved: Data Collector (DC), Proxy Server (PS), Data Requester (DR) and Key Generation Center. The blockchain network stores two authorization tables, where the first authorization table (hereinafter referred to as authorization table USER-RE-KEY) is used to store each legitimate user and the corresponding re-encryption key, and the second authorization table (hereinafter referred to as authorization table USER-COUNTER) is used to store the tuple identifier that a legitimate user can access according to the system's access control policy.
[0201] The main process of this example can be divided into three stages: initialization, re-encryption, and decryption.
[0202] 1. Initialization phase.
[0203] 1. First encryption: DC randomly selects a symmetric key e (or the key generation center randomly distributes a symmetric key e), and encrypts the plaintext data S1 into ciphertext c using the symmetric key e e , and upload it to PS. The encryption process is as follows (where E1 represents the encryption algorithm):
[0204] DC:E1(e,S1)=c e
[0205] 2. Re-encryption key generation: DC creates two authorization tables USER-RE-KEY and USER-COUNTER.
[0206] Among them, the re-encryption key rekey corresponding to DR in the authorization table USER-RE-KEY DR The generation algorithm E2 is as follows:
[0207] DC:E2(Pk DR ,e)=rekey DR
[0208] Among them, Pk DR The public key of DR. The authorization table USER-RE-KEY is composed of the re-encryption keys of each DR, and the generation of the re-encryption key is performed at the DC.
[0209] 3. Encrypt and send two authorization tables: DC uses its own private key Sk DC Encrypt the authorization tables USER-RE-KEY and USER-COUNTER and send them to the blockchain network.
[0210] 2. Re-encryption stage.
[0211] DR initiates a data access request to PS, where the data to be accessed is assumed to be S1. Among them, the visitor of the blockchain network can only be a proxy server (not specifically a proxy server).
[0212] 1. Retrieval stage: PS applies for two authorization tables from the blockchain and determines whether DR can access data S1 based on the access control policy in the USER-COUNTER authorization table.
[0213] 2. Re-encryption: If PS determines that it can be accessed, it extracts the re-encryption key rekey corresponding to DR in the USER-RE-KEY authorization table. DR , perform c e Re-encryption to generate the re-encrypted ciphertext rc e The re-encryption process is as follows (where E3 represents the re-encryption algorithm):
[0214] PS: E3 (rekey DR ,c e )P=rc e
[0215] 3. Decryption stage.
[0216] DR receives the re-encrypted ciphertext rc e , and use your own private key sk DR Decryption is performed to obtain the plaintext data S1. The decryption process is as follows (where D represents the decryption algorithm):
[0217] DR:D(sk DR ,rc e )P=S1
[0218] The methods and devices provided in the various embodiments of the present application are based on the same application concept. Since the methods and devices solve problems based on similar principles, the implementation of the devices and methods can refer to each other, and the repeated parts will not be repeated.
[0219] Figure 5 A schematic diagram of the structure of the proxy server provided in the embodiment of the present application, such as Figure 5 As shown, the proxy server includes a memory 520, a transceiver 510 and a processor 500; wherein the processor 500 and the memory 520 may also be arranged physically separately.
[0220] The memory 520 is used to store computer programs; the transceiver 510 is used to send and receive data under the control of the processor 500.
[0221] Specifically, the transceiver 510 is used to receive and send data under the control of the processor 500 .
[0222] Among them, Figure 5 In the embodiment, the bus architecture may include any number of interconnected buses and bridges, specifically linking various circuits of one or more processors represented by processor 500 and memory represented by memory 520. The bus architecture may also link various other circuits such as peripherals, voltage regulators, and power management circuits, which are well known in the art and are therefore not further described in this application. The bus interface provides an interface. The transceiver 510 may be a plurality of components, namely, a transmitter and a receiver, providing a unit for communicating with various other devices on a transmission medium, which may include a wireless channel, a wired channel, an optical cable, and other transmission media.
[0223] The processor 500 is responsible for managing the bus architecture and general processing, and the memory 520 can store data used by the processor 500 when performing operations.
[0224] The processor 500 may be a central processing unit (CPU), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or a complex programmable logic device (CPLD). The processor may also adopt a multi-core architecture.
[0225] The processor 500 calls the computer program stored in the memory 520 to execute any of the methods provided in the embodiments of the present application according to the obtained executable instructions, for example: receiving a data access request sent by a data requester, the data access request is used to request the target data of a data collector; after determining that the data requester is a user allowed to access the target data, re-encrypting the encrypted ciphertext of the target data according to the re-encryption key corresponding to the data requester in the first authorization table of the data collector to generate a re-encrypted ciphertext of the target data; wherein the first authorization table contains the re-encryption key corresponding to the authorized user, and the re-encryption keys in the first authorization table are all generated based on the symmetric key; and sending the re-encrypted ciphertext of the target data to the data requester.
[0226] In some embodiments, determining that the data requester is a user allowed to access the target data includes:
[0227] Determining, according to the first authorization form or the second authorization form of the data collector, that the data requester is a user permitted to access the target data;
[0228] The first authorization table or the second authorization table contains identification of data that the authorized user is allowed to access.
[0229] In some embodiments, the method further comprises:
[0230] Obtain a first authorization list from the blockchain network; or obtain the first authorization list and the second authorization list from the blockchain network.
[0231] In some embodiments, in the first authorization table, different data that the same authorized user is allowed to access respectively corresponds to different re-encryption keys.
[0232] In some embodiments, the encrypted ciphertext of the target data is re-encrypted according to the re-encryption key corresponding to the data requester in the first authorization table of the data collector, including:
[0233] The encrypted ciphertext of the target data is re-encrypted according to the re-encryption key corresponding to the data requester and the target data in the first authorization table.
[0234] In some embodiments, the method further comprises:
[0235] Receive the encrypted ciphertext of the target data sent by the data collector.
[0236] Figure 6 A schematic diagram of the structure of the data collector provided in the embodiment of the present application, such as Figure 6 As shown, the data collector includes a memory 620, a transceiver 610 and a processor 600; wherein the processor 600 and the memory 620 may also be arranged physically separately.
[0237] The memory 620 is used to store computer programs; the transceiver 610 is used to send and receive data under the control of the processor 600.
[0238] Specifically, the transceiver 610 is used to receive and send data under the control of the processor 600 .
[0239] Among them, Figure 6 In the embodiment, the bus architecture may include any number of interconnected buses and bridges, specifically linking together various circuits of one or more processors represented by processor 600 and memory represented by memory 620. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, and power management circuits, which are well known in the art and are therefore not further described in this application. The bus interface provides an interface. The transceiver 610 may be a plurality of components, namely, a transmitter and a receiver, providing a unit for communicating with various other devices on a transmission medium, which may include a wireless channel, a wired channel, an optical cable, and other transmission media.
[0240] The processor 600 is responsible for managing the bus architecture and general processing, and the memory 620 can store data used by the processor 600 when performing operations.
[0241] The processor 600 may be a CPU, an ASIC, an FPGA or a CPLD, and the processor may also adopt a multi-core architecture.
[0242] The processor 600 calls the computer program stored in the memory 620 to execute any of the methods provided in the embodiments of the present application according to the obtained executable instructions, for example: determining the symmetric key used to encrypt data; generating a re-encryption key corresponding to the authorized user based on the symmetric key and the public key of the authorized user.
[0243] In some embodiments, the method further comprises:
[0244] Generate a first authorization table for the data collector, where the first authorization table contains a re-encryption key corresponding to the authorized user;
[0245] The first authorization form is encrypted using the data collector’s private key and uploaded to the blockchain network.
[0246] In some embodiments, the first authorization table also includes an identification of data that the authorized user is allowed to access.
[0247] In some embodiments, the method further comprises:
[0248] generating a second authorization form for the data collector, the second authorization form including identification of data that the authorized user is allowed to access;
[0249] The second authorization form is encrypted using the data collector’s private key and uploaded to the blockchain network.
[0250] In some embodiments, in the first authorization table, different data that the same authorized user is allowed to access correspond to different re-encryption keys.
[0251] Figure 7 A schematic diagram of the structure of a data requester provided in an embodiment of the present application, such as Figure 7 As shown, the data requester includes a memory 720, a transceiver 710 and a processor 700; wherein the processor 700 and the memory 720 may also be arranged physically separately.
[0252] The memory 720 is used to store computer programs; the transceiver 710 is used to send and receive data under the control of the processor 700.
[0253] Specifically, the transceiver 710 is used to receive and send data under the control of the processor 700 .
[0254] Among them, Figure 7 In the embodiment, the bus architecture may include any number of interconnected buses and bridges, specifically linking together various circuits of one or more processors represented by processor 700 and memory represented by memory 720. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, and power management circuits, which are well known in the art and are therefore not further described in this application. The bus interface provides an interface. The transceiver 710 may be a plurality of components, namely, a transmitter and a receiver, providing a unit for communicating with various other devices on a transmission medium, which may include a wireless channel, a wired channel, an optical cable, and other transmission media.
[0255] The processor 700 is responsible for managing the bus architecture and general processing, and the memory 720 can store data used by the processor 700 when performing operations.
[0256] The processor 700 may be a CPU, an ASIC, an FPGA or a CPLD, and the processor may also adopt a multi-core architecture.
[0257] The processor 700 calls the computer program stored in the memory 720 to execute any of the methods provided in the embodiments of the present application according to the obtained executable instructions, for example: sending a data access request to the proxy server, the data access request is used to request the target data of the data collector; receiving the re-encrypted ciphertext of the target data sent by the proxy server; using the private key of the data requester to decrypt the re-encrypted ciphertext of the target data to obtain the target data.
[0258] It should be noted here that the above-mentioned proxy server, data collector and data requester provided in the embodiment of the present application can implement all the method steps implemented in the above-mentioned method embodiment, and can achieve the same technical effect. The parts and beneficial effects of this embodiment that are the same as those in the method embodiment will not be described in detail here.
[0259] Figure 8 This is one of the structural diagrams of the data access control device provided in the embodiment of the present application, such as Figure 8 As shown, the device comprises:
[0260] A first receiving unit 800 is used to receive a data access request sent by a data requester, wherein the data access request is used to request target data of a data collector;
[0261] The re-encryption unit 810 is used to re-encrypt the encrypted ciphertext of the target data according to the re-encryption key corresponding to the data requester in the first authorization table of the data collector after determining that the data requester is a user allowed to access the target data, so as to generate the re-encrypted ciphertext of the target data; wherein the first authorization table contains the re-encryption key corresponding to the authorized user, and the re-encryption keys in the first authorization table are all generated based on the symmetric key;
[0262] The first sending unit 820 is configured to send the re-encrypted ciphertext of the target data to the data requester.
[0263] In some embodiments, determining that the data requester is a user allowed to access the target data includes:
[0264] Determining, according to the first authorization form or the second authorization form of the data collector, that the data requester is a user permitted to access the target data;
[0265] The first authorization table or the second authorization table contains identification of data that the authorized user is allowed to access.
[0266] In some embodiments, the apparatus further comprises an acquisition unit, configured to:
[0267] Obtain the first authorization list from the blockchain network; or obtain the first authorization list and the second authorization list from the blockchain network.
[0268] In some embodiments, in the first authorization table, different data that the same authorized user is allowed to access corresponds to different re-encryption keys.
[0269] In some embodiments, re-encrypting the encrypted ciphertext of the target data according to the re-encryption key corresponding to the data requester in the first authorization table of the data collector includes:
[0270] The encrypted ciphertext of the target data is re-encrypted according to the data requester in the first authorization table and the re-encryption key corresponding to the target data.
[0271] In some embodiments, the first receiving unit 800 is further configured to:
[0272] Receive the encrypted ciphertext of the target data sent by the data collector.
[0273] Fig. 9 The second structural diagram of the data access control device provided in the embodiment of the present application is as follows: Fig. 9 As shown, the device comprises:
[0274] A determination unit 900, configured to determine a symmetric key used to encrypt data;
[0275] The re-encryption key generation unit 910 is used to generate a re-encryption key corresponding to the authorized user based on the symmetric key and the public key of the authorized user.
[0276] In some embodiments, the apparatus further comprises:
[0277] A first authorization table generating unit, used to generate a first authorization table of the data collector, wherein the first authorization table contains a re-encryption key corresponding to the authorized user;
[0278] The first uploading unit is used to encrypt the first authorization form using the private key of the data collector and then upload it to the blockchain network.
[0279] In some embodiments, the first authorization table also includes an identification of data that the authorized user is allowed to access.
[0280] In some embodiments, the apparatus further comprises:
[0281] A second authorization table generating unit, used to generate a second authorization table for the data collector, wherein the second authorization table contains identifications of data that the authorized user is allowed to access;
[0282] The second uploading unit is used to encrypt the second authorization form using the private key of the data collector and then upload it to the blockchain network.
[0283] In some embodiments, in the first authorization table, different data that the same authorized user is allowed to access corresponds to different re-encryption keys.
[0284] Fig.10 The third structural diagram of the data access control device provided in the embodiment of the present application is as follows: Fig.10 As shown, the device comprises:
[0285] The second sending unit 1000 is used to send a data access request to the proxy server, where the data access request is used to request the target data of the data collector;
[0286] The second receiving unit 1010 is used to receive the re-encrypted ciphertext of the target data sent by the proxy server;
[0287] The decryption unit 1020 is used to decrypt the re-encrypted ciphertext of the target data using the private key of the data requester to obtain the target data.
[0288] It should be noted that the division of units in the embodiments of the present application is schematic and is only a logical function division. There may be other division methods in actual implementation. In addition, each functional unit in each embodiment of the present application may be integrated into a processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.
[0289] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a processor-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions to enable a computer device (which can be a personal computer, server, or network device, etc.) or a processor (processor) to perform all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), disk or optical disk and other media that can store program codes.
[0290] It should be noted here that the above-mentioned device provided in the embodiment of the present application can implement all the method steps implemented in the above-mentioned method embodiment, and can achieve the same technical effect. The parts and beneficial effects of this embodiment that are the same as those in the method embodiment will not be described in detail here.
[0291] On the other hand, an embodiment of the present application further provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, and the computer program is used to enable a computer to execute the data access control method provided by the above embodiments.
[0292] It should be noted here that the computer-readable storage medium provided in the embodiment of the present application can implement all the method steps implemented in the above-mentioned method embodiment and can achieve the same technical effect. The parts and beneficial effects of this embodiment that are the same as those in the method embodiment will not be described in detail here.
[0293] The computer-readable storage medium can be any available medium or data storage device that can be accessed by a computer, including but not limited to magnetic storage (such as floppy disks, hard disks, magnetic tapes, magneto-optical disks (MO), etc.), optical storage (such as CD, DVD, BD, HVD, etc.), and semiconductor storage (such as ROM, EPROM, EEPROM, non-volatile memory (NANDFLASH), solid-state drive (SSD)), etc.
[0294] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems, or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application may adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage and optical storage, etc.) that contain computer-usable program code.
[0295] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer executable instructions. These computer executable instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.
[0296] These processor executable instructions may also be stored in a processor readable memory that can direct a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the processor readable memory produce an article of manufacture including an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.
[0297] These processor-executable instructions may also be loaded onto a computer or other programmable data processing device so that a series of operational steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for executing on the computer or other programmable device to implement the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.
[0298] Obviously, those skilled in the art can make various changes and modifications to the present application without departing from the spirit and scope of the present application. Thus, if these modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is also intended to include these modifications and variations.
Claims
1. A data access control method, characterized in that: Applicable to proxy servers, including: receiving a data access request sent by a data requester, wherein the data access request is used to request target data of a data collector; After determining that the data requester is a user allowed to access the target data, re-encrypt the encrypted ciphertext of the target data according to the re-encryption key corresponding to the data requester in the first authorization table of the data collector to generate the re-encrypted ciphertext of the target data; wherein the first authorization table contains the re-encryption key corresponding to the authorized user, and the re-encryption keys in the first authorization table are all generated based on the symmetric key; The re-encrypted ciphertext of the target data is sent to the data requester.
2. The data access control method according to claim 1, characterized in that: The determining that the data requester is a user allowed to access the target data includes: Determining, according to the first authorization form or the second authorization form of the data collector, that the data requester is a user permitted to access the target data; The first authorization table or the second authorization table contains identification of data that the authorized user is allowed to access.
3. The data access control method according to claim 2, characterized in that: The method further comprises: Obtain the first authorization list from the blockchain network; or obtain the first authorization list and the second authorization list from the blockchain network.
4. The data access control method according to claim 1 or 2, characterized in that: In the first authorization table, different data that the same authorized user is allowed to access correspond to different re-encryption keys.
5. The data access control method according to claim 4, characterized in that: The re-encrypting the encrypted ciphertext of the target data according to the re-encryption key corresponding to the data requester in the first authorization table of the data collector comprises: The encrypted ciphertext of the target data is re-encrypted according to the data requester in the first authorization table and the re-encryption key corresponding to the target data.
6. The data access control method according to claim 1, characterized in that: The method further comprises: Receive the encrypted ciphertext of the target data sent by the data collector.
7. A data access control method, characterized in that: Applies to data collectors, including: Determine the symmetric key used to encrypt the data; Based on the symmetric key and the public key of the authorized user, a re-encryption key corresponding to the authorized user is generated.
8. The data access control method according to claim 7, characterized in that: The method further comprises: Generate a first authorization table for the data collector, wherein the first authorization table includes a re-encryption key corresponding to the authorized user; The first authorization form is encrypted using the private key of the data collector and then uploaded to the blockchain network.
9. The data access control method according to claim 8, characterized in that: The first authorization table also includes identification of data that the authorized user is allowed to access.
10. The data access control method according to claim 8, characterized in that: The method further comprises: generating a second authorization form for the data collector, wherein the second authorization form includes identification of data that the authorized user is allowed to access; The second authorization form is encrypted using the private key of the data collector and then uploaded to the blockchain network.
11. The data access control method according to claim 9, characterized in that: In the first authorization table, different data that the same authorized user is allowed to access correspond to different re-encryption keys.
12. A data access control method, characterized in that: Applies to data requesters, including: Sending a data access request to the proxy server, wherein the data access request is used to request target data of the data collector; Receiving the re-encrypted ciphertext of the target data sent by the proxy server; The re-encrypted ciphertext of the target data is decrypted using the private key of the data requester to obtain the target data.
13. A proxy server, characterized in that: Including memory, transceiver, processor; Memory for storing computer programs; a transceiver, for transmitting and receiving data under the control of the processor; A processor is configured to read the computer program in the memory and perform the following operations: receiving a data access request sent by a data requester, wherein the data access request is used to request target data of a data collector; After determining that the data requester is a user allowed to access the target data, re-encrypt the encrypted ciphertext of the target data according to the re-encryption key corresponding to the data requester in the first authorization table of the data collector to generate the re-encrypted ciphertext of the target data; wherein the first authorization table contains the re-encryption key corresponding to the authorized user, and the re-encryption keys in the first authorization table are all generated based on the symmetric key; The re-encrypted ciphertext of the target data is sent to the data requester.
14. The proxy server according to claim 13, characterized in that: The determining that the data requester is a user allowed to access the target data includes: Determining, according to the first authorization form or the second authorization form of the data collector, that the data requester is a user permitted to access the target data; The first authorization table or the second authorization table contains identification of data that the authorized user is allowed to access.
15. The proxy server according to claim 14, characterized in that: The operations also include: Obtain the first authorization list from the blockchain network; or obtain the first authorization list and the second authorization list from the blockchain network.
16. The proxy server according to claim 13 or 14, characterized in that: In the first authorization table, different data that the same authorized user is allowed to access correspond to different re-encryption keys.
17. The proxy server according to claim 16, characterized in that: The re-encrypting the encrypted ciphertext of the target data according to the re-encryption key corresponding to the data requester in the first authorization table of the data collector comprises: The encrypted ciphertext of the target data is re-encrypted according to the data requester in the first authorization table and the re-encryption key corresponding to the target data.
18. The proxy server according to claim 13, characterized in that: The operations also include: Receive the encrypted ciphertext of the target data sent by the data collector.
19. A data collector, characterized in that: Including memory, transceiver, processor; Memory for storing computer programs; a transceiver, for transmitting and receiving data under the control of the processor; A processor is configured to read the computer program in the memory and perform the following operations: Determine the symmetric key used to encrypt the data; Based on the symmetric key and the public key of the authorized user, a re-encryption key corresponding to the authorized user is generated.
20. The data collector according to claim 19, characterized in that The operations also include: Generate a first authorization table for the data collector, wherein the first authorization table includes a re-encryption key corresponding to the authorized user; The first authorization form is encrypted using the private key of the data collector and then uploaded to the blockchain network.
21. The data collector according to claim 20, characterized in that The first authorization table also includes identification of data that the authorized user is allowed to access.
22. The data collector according to claim 20, characterized in that The operations also include: generating a second authorization form for the data collector, wherein the second authorization form includes identification of data that the authorized user is allowed to access; The second authorization form is encrypted using the private key of the data collector and then uploaded to the blockchain network.
23. The data collector according to claim 21, characterized in that In the first authorization table, different data that the same authorized user is allowed to access correspond to different re-encryption keys.
24. A data requester, characterized in that: Including memory, transceiver, processor; Memory for storing computer programs; a transceiver, for transmitting and receiving data under the control of the processor; A processor is configured to read the computer program in the memory and perform the following operations: Sending a data access request to the proxy server, wherein the data access request is used to request target data of the data collector; Receiving the re-encrypted ciphertext of the target data sent by the proxy server; The re-encrypted ciphertext of the target data is decrypted using the private key of the data requester to obtain the target data.
25. A data access control device, characterized in that: include: A first receiving unit, configured to receive a data access request sent by a data requester, wherein the data access request is used to request target data of a data collector; a re-encryption unit, configured to re-encrypt the encrypted ciphertext of the target data according to the re-encryption key corresponding to the data requester in the first authorization table of the data collector after determining that the data requester is a user allowed to access the target data, so as to generate the re-encrypted ciphertext of the target data; wherein the first authorization table contains the re-encryption key corresponding to the authorized user, and the re-encryption keys in the first authorization table are all generated based on the symmetric key; The first sending unit is used to send the re-encrypted ciphertext of the target data to the data requester.
26. A data access control device, characterized in that: include: A determination unit, used to determine a symmetric key used to encrypt data; The re-encryption key generation unit is used to generate a re-encryption key corresponding to the authorized user based on the symmetric key and the public key of the authorized user.
27. A data access control device, characterized in that: include: A second sending unit, used to send a data access request to the proxy server, wherein the data access request is used to request target data of the data collector; A second receiving unit, configured to receive the re-encrypted ciphertext of the target data sent by the proxy server; The decryption unit is used to decrypt the re-encrypted ciphertext of the target data using the private key of the data requester to obtain the target data.
28. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and the computer program is used to make a computer execute the method according to any one of claims 1 to 6.
29. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and the computer program is used to make a computer execute the method according to any one of claims 7 to 11.
30. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and the computer program is used to cause a computer to execute the method according to claim 12 .
