|
CP-ABE category | Description |
|
Revocable CP-ABE constructions [3, 4] | It can achieve fine-grained revocable access control. According to the fine-grained difference, the revocation mechanism is divided into user revocation and attribute revocation; according to nonrevoked users, it is divided into indirect revocation and direct revocation. |
Traceable CP-ABE constructions [5] | It can realize fine-grained and traceable access control mechanism, responsible for user traceability and attribute authority responsibility, which can be divided into white-box traceability and black-box traceability. |
Policy-hiding CP-ABE constructions [6] | Hide related attributes and have a fine-grained access control mechanism for attribute privacy protection. It can be divided into fully hidden and partially hidden. Currently, there is no specific and completely hidden CP-ABE scheme. |
Policy-updating CP-ABE constructions [7] | Involving proxy re-encryption, it is impossible to change the secret access policy. In an emergency, the policy update policy can be adopted. Used to implement fine-grained access control for policy updates. |
Multiauthority CP-ABE constructions [8] | It can realize fine-grained distributed access authority and can be divided into centralized CP-ABE and distributed CP-ABE according to whether there is a central organization. |
Hierarchical CP-ABE constructions [9ā13] | It can achieve hierarchical fine-grained access control. The delegation of access privilege is organized in a hierarchical manner. |
Online/offline CP-ABE constructions [14] | In order to reduce the amount of calculation of the data owner and attribute authority, offline encryption or offline key generation can be used. |
Outsourced CP-ABE constructions [15, 16] | In order to support resource constrained users (data users, data owners, and central authority), laborious calculations are outsourced to third-party servers in the encryption and decryption process. |
|