Personal data dynamic authorization method and system based on block chain

Abstract

According to the block chain-based personal data dynamic authorization method and system provided by the invention, a personal data owner dynamically authorizes a personal data demander to use personal data stored in a block chain; the method comprises the following steps of: receiving a use demand of a personal data demander for personal data of a personal data owner through a demand application interface; informing the personal data owner of the use demand; receiving agreement of the personal data owner through the authorized use interface; an authorization certificate based on the block chain non-homogeneous token is output and connected to a block chain wallet of the personal data demander; receiving a requirement of a personal data demander for accessing the personal data of the personal data owner through the personal data access interface; verifying that the block chain wallet of the personal data demander is connected with the authorization certificate created by the personal data owner; and providing the personal data of the personal data owner stored in the block chain for the personal data demander to access after the authorization certificate passes verification.

Description

Technical Field

[0001] This disclosure relates to the management of personal data, and in particular to methods and systems by which owners of personal data dynamically authorize others to use their personal data. Background Technology

[0002] In today's cloud-based internet age, our personal data is constantly being collected and used. Sometimes this collection and use is done with our consent; for example, when using certain online services, we are required to create an account and provide personal information such as our birthday, address, gender, and occupation. However, other types of personal data, such as our medical records, clinical treatments, and even health-related data like physical examinations, as well as our income, expenses, and tax-related data, are often collected, recorded, and used by relevant organizations (such as health insurance agencies and medical institutions).

[0003] With the continuous advancement of big data and artificial intelligence technologies, especially personal data involving privacy, such as the aforementioned data, is often analyzed and utilized by academic institutions. The results can then be used to develop beneficial research findings and industrial applications. For example, with the development of a precision health strategy industry as a primary goal, there is a desire to create a precision healthcare system in the future (such as early cancer detection, early treatment, and reduced mortality). Such goals require big data sharing platforms and mechanisms for a vast amount of personal health data. However, given that the personal data collected and stored by these institutions involves personal privacy, how to ensure its open access while protecting individual data privacy rights has become an urgent issue.

[0004] The burgeoning blockchain technology offers a secure and feasible data-sharing solution. Blockchain is a decentralized database technology whose core concept is packaging data into blocks. Each block contains a unique hash value calculated based on its own data, along with the hash of the previous block, thus forming a chain. These chains are then stored multiple times in a decentralized peer-to-peer network. This design makes the block content tamper-proof. Therefore, storing personal data on the blockchain can provide sharing while simultaneously ensuring the security of personal data. However, blockchain itself does not provide individuals with the right to control the privacy of their personal data—that is, the right to decide whether to disclose their personal data, and to what extent, when, how, and to whom it is disclosed. Summary of the Invention

[0005] This disclosure provides a personal data usage authorization system based on de-identification, blockchain, and credential signing technologies. It returns ownership of personal data to users while ensuring participants' right to opt out, allowing for secondary authorization and use of the de-identified data corresponding to the personal data, thus protecting the personal wishes of the data provider.

[0006] The personal data usage authorization system disclosed herein includes a dynamic consent form subsystem, a credential management subsystem, a de-identification subsystem, and a blockchain subsystem. The dynamic consent form subsystem provides a dynamic consent form authorizing the use of personal data. The credential management subsystem is coupled to the dynamic consent form subsystem and provides authorization credentials for the dynamic consent form. The de-identification subsystem is coupled to the dynamic consent form subsystem and the personal data database and performs de-identification of personal data to obtain de-identified data, and provides de-identified data according to the usage authorization. The blockchain subsystem is coupled to the dynamic consent form subsystem and the de-identification subsystem and records the hash value of the dynamic consent form, the authorization credentials, and the hash values ​​of the personal data and the de-identified data.

[0007] In one embodiment disclosed herein, the aforementioned dynamic consent form subsystem includes a human-machine interface and a dynamic consent form module. The human-machine interface is used to provide the content for filling in the dynamic consent form. The dynamic consent form module is coupled to the human-machine interface and performs tasks such as filling in the content of the dynamic consent form, calculating the hash value of the dynamic consent form, and integrating the dynamic consent form with the authorization certificate through the human-machine interface.

[0008] In one embodiment disclosed herein, the aforementioned dynamic consent form subsystem further includes an intention change module. The intention change module is coupled to the human-machine interface and the dynamic consent form module, and performs changes to the content of the dynamic consent form, calculates the hash value of the changed dynamic consent form, and integrates the changed dynamic consent form with the authorization certificate through the human-machine interface.

[0009] In one embodiment disclosed herein, the aforementioned credential management subsystem includes a human-machine interface and a credential signing module. The human-machine interface is used to provide the selection of credential sources. The credential signing module is coupled to the human-machine interface and is used to generate an authorization credential by signing an electronic signature based on the credential.

[0010] In one embodiment disclosed herein, the aforementioned credential management subsystem further includes a competent authority credential management module, a system-generated credential management module, and a personal credential management module. The competent authority credential management module is coupled to a human-machine interface and is used to manage credentials issued by the competent authority. The system-generated credential management module is coupled to a human-machine interface and is used to manage credentials issued by the personal data usage authorization system. The personal credential management module is coupled to a human-machine interface and is used to manage personal credentials.

[0011] In one embodiment of this disclosure, the de-identification subsystem includes a de-identification database. The de-identification database is used to store de-identified data.

[0012] In one embodiment disclosed herein, the aforementioned de-identification subsystem calculates a hash value based on personal data and the corresponding de-identification data.

[0013] In one embodiment disclosed herein, the aforementioned blockchain subsystem includes a blockchain on-chain module and a blockchain. The blockchain on-chain module uses the hash value of the on-chain dynamic consent form, authorization certificate, and hash values ​​of personal data and de-identified data. The blockchain is coupled to the blockchain on-chain module and is used to store the hash value of the dynamic consent form, authorization certificate, and hash values ​​of personal data and de-identified data.

[0014] This disclosure, by employing technologies such as dynamic consent forms, credential management, de-identification, and blockchain, allows for the secondary authorization and use of de-identified data corresponding to personal data, thereby protecting the personal wishes of data providers.

[0015] Another objective of this disclosure is to provide a novel method that allows individuals to dynamically and autonomously control their personal data, that is, to decide whether to disclose their personal data, and to what extent, when, how, and to whom to disclose it, and to dynamically modify the conditions of these authorizations.

[0016] Therefore, this disclosure proposes a blockchain-based dynamic authorization method for personal data, allowing a data owner to dynamically authorize a data requester to use their personal data stored on a blockchain. This method includes the following steps:

[0017] The recipient of the personal data request submits a request for use of the personal data owner's personal data through a request application interface;

[0018] Notify the data owner of this usage request;

[0019] Receive consent from the owner of the personal data through an authorization interface;

[0020] It generates an authorization certificate based on a blockchain non-fungible token and links it to a blockchain wallet of the individual data requester.

[0021] The user requesting personal data requests access to the personal data owner's personal data through a personal data access interface;

[0022] The personal data access interface verifies that the blockchain wallet of the user requesting the personal data is linked to the authorization credential created by the personal data owner; and

[0023] Once the authorization credential is verified, the personal data access interface will provide the personal data of the data owner stored in the blockchain to the data requester for access.

[0024] In some embodiments of this disclosure, the disclosure further includes the following steps:

[0025] When the personal data access interface detects that the authorization credential has expired, the personal data access interface will automatically destroy the authorization credential.

[0026] A request from the data owner to destroy the authorization certificate through the authorization interface; and

[0027] Destroy the authorization certificate.

[0028] The blockchain can be a public chain, a private chain, a hybrid chain, or a consortium chain. Furthermore, the blockchain may contain single chains or multiple chains.

[0029] Ideally, the authorization certificate is a non-tradable, soul-bound, non-fungible token.

[0030] The above and other objects and advantages of this disclosure are described in detail below with reference to the accompanying drawings, detailed description of the embodiments, and claims. It should be understood that the accompanying drawings are merely for illustrating the spirit of this disclosure and should not be construed as defining the scope of this disclosure. For a definition of the scope of this disclosure, please refer to the appended claims. Attached Figure Description

[0031] Figure 1 This is a schematic diagram of the personal data usage authorization system provided in the embodiments of this disclosure;

[0032] Figure 2 This is a schematic diagram illustrating the dynamic consent form subsystem provided in this embodiment;

[0033] Figure 3 This is a schematic diagram of the credential management subsystem provided in the embodiments disclosed herein;

[0034] Figure 4 This is a schematic diagram of the deidentification subsystem provided in the embodiments disclosed herein;

[0035] Figure 5 This is a schematic diagram of the blockchain subsystem provided in the embodiments disclosed herein.

[0036] Figure 6 This document presents a flowchart of the blockchain-based dynamic authorization method for personal data.

[0037] Figure 7 This is a schematic diagram of the blockchain-based dynamic authorization system for personal data proposed in this disclosure. Detailed Implementation

[0038] The term "personal data" as used in this disclosure, or simply "personal data," refers to data that meets the definition of personal data protection and includes information such as name, date of birth, characteristics, fingerprints, marital status, family, education, occupation, medical records, medical information, genetic information, sexual history, health examination results, criminal record, contact information, financial situation, social activities, and other data that can directly or indirectly identify an individual. That individual is the "personal data owner" as referred to in this disclosure.

[0039] Personal data of one or more data owners has been added to and stored on a blockchain by a "personal data custodian" using a blockchain-based block-building method. The relevant block-building method is existing technology and will not be described in detail here. The term "personal data custodian" in this disclosure refers to an organization responsible for collecting, managing, or maintaining personal data (e.g., healthcare organizations, medical institutions, financial institutions, operators of biometric databases, etc.).

[0040] The blockchain can be a public blockchain (which is permissionless and can be used by the general public), a private blockchain (which is privately controlled and not publicly disclosed), a consortium blockchain (which is accessible only to a predetermined number of organizations or institutions), or a hybrid blockchain (a combination of public and private blockchains). The blockchain can contain a single blockchain or multiple blockchains.

[0041] Individuals or organizations intending to use the aforementioned personal data stored on this blockchain are referred to in this disclosure as "personal data requesters." Personal data requesters need permission to use the blockchain and will therefore have their own dedicated "wallet" on that blockchain. A blockchain wallet is a unique address, functioning similarly to an account for online services; it is a digital asset and management mechanism on the blockchain. The main functions of a blockchain wallet include generating and managing cryptographic key pairs (public and private keys) and signing transactions. Through this unique address, the blockchain wallet can be used to send and receive cryptocurrencies (such as Ethereum) and dynamic authorizations from the personal data owners as described in this disclosure. The methods for building blockchain wallets are existing technology and will not be elaborated upon here.

[0042] Please see Figure 1The diagram illustrates a personal data usage authorization system provided in this embodiment. The personal data usage authorization system 1 provided in this embodiment can be hardware, software, or a combination of hardware and software for executing, calculating, and storing information and data, including at least one cloud server, computer, or other similar device. The personal data usage authorization system 1 provided in this embodiment includes a dynamic consent form subsystem 2, a credential management subsystem 3, a de-identification subsystem 4, and a blockchain subsystem 5. The credential management subsystem 3 is coupled to the dynamic consent form subsystem 2, the de-identification subsystem 4 is coupled to the dynamic consent form subsystem 2 and a personal data database 6, and the blockchain subsystem 5 is coupled to the dynamic consent form subsystem 2 and the de-identification subsystem 4. Furthermore, the functions of each subsystem in the personal data usage authorization system 1 are detailed below. The Dynamic Consent Subsystem 2 provides a dynamic consent form authorizing the use of personal data; the Credential Management Subsystem 3 provides authorization credentials for the dynamic consent form; the De-identification Subsystem 4 performs de-identification of personal data to obtain de-identified data and provides de-identified data according to the usage authorization; and the Blockchain Subsystem 5 records the hash value of the dynamic consent form, the authorization credentials, and the hash values ​​of the personal data and the de-identified data. It is important to note that the dynamic consent form is provided to personal data providers to sign and modify the content of their authorization for the use of their personal data, ensuring that the personal data of the personal data provider complies with the legal use within the scope of the personal data provider's consent.

[0043] Please see Figure 2 The diagram shown is a schematic of the dynamic consent form subsystem provided in this embodiment. The dynamic consent form subsystem 2 provided in this embodiment includes a human-machine interface 21, a dynamic consent form module 22, and an intention change module 23. The dynamic consent form module 22 is coupled to the human-machine interface 21, and the intention change module 23 is coupled to both the human-machine interface 21 and the dynamic consent form module 22. Specifically, the functions of each interface and module in the dynamic consent form subsystem 2 are as follows: The human-machine interface 21 is used to provide the content for filling in the dynamic consent form; the dynamic consent form module 22 is used to fill in the content of the dynamic consent form through the human-machine interface 21, calculate the hash value of the dynamic consent form, and integrate the dynamic consent form with the authorization certificate; and the intention change module 23 is used to change the content of the dynamic consent form through the human-machine interface 21, calculate the hash value of the changed dynamic consent form, and integrate the changed dynamic consent form with the authorization certificate.

[0044] Please see Figure 3The diagram shown is a schematic of the credential management subsystem provided in this embodiment. The credential management subsystem 3 provided in this embodiment includes a human-machine interface 31, a credential signing module 32, a competent authority credential management module 33, a system-generated credential management module 34, and a private credential management module 35. The credential signing module 32 is coupled to the human-machine interface 31, the competent authority credential management module 33 is coupled to the human-machine interface 31, the system-generated credential management module 34 is coupled to the human-machine interface 31, and the private credential management module 35 is coupled to the human-machine interface 31. Specifically, the functions of each interface and module in the credential management subsystem 3 are as follows: The human-machine interface 31 is used to provide credential source selection; the credential signing module 32 is used to generate authorization credentials by signing an electronic signature based on the credential; the competent authority credential management module 33 is used to manage credentials issued by the competent authority 7; the system-generated credential management module 34 is used to manage credentials issued by the personal data usage authorization system; and the private credential management module 35 is used to manage personal private credentials.

[0045] Please see Figure 4 The diagram shown is a schematic of the de-identification subsystem provided in this embodiment. The de-identification subsystem 4 provided in this embodiment includes a de-identification database 41, wherein the de-identification subsystem 4 calculates hash values ​​based on personal data and corresponding de-identification data, and the de-identification database 41 is used to store de-identification data.

[0046] Please see Figure 5 The diagram shown is a schematic of the blockchain subsystem provided in this embodiment. The blockchain subsystem 5 provided in this embodiment includes a blockchain on-chain module 51 and a blockchain 52, wherein the blockchain 52 is coupled to the blockchain on-chain module 51. Specifically, the functions of each module in the blockchain subsystem 5 are as follows: The blockchain on-chain module 51 is used to store the hash value of the dynamic consent form, authorization certificate, and hash values ​​of personal data and de-identified data; and the blockchain 52 is used to store the hash value of the dynamic consent form, authorization certificate, and hash values ​​of personal data and de-identified data.

[0047] In one example, a personal data provider participates in a health and medical big data program. This program can protect the personal data provider's rights to use their personal data through the Personal Data Use Authorization System 1 of this invention. After registering in the Personal Data Use Authorization System 1, the system-generated certificate management module 34 of the certificate management subsystem 3 of this invention automatically generates a certificate for the personal data provider's use. When the personal data provider logs into the Personal Data Use Authorization System 1, the dynamic consent module 22 of the dynamic consent module 2 provides a dynamic consent form for personal data to the personal data provider through the human-computer interface 21, allowing them to fill in the content of the dynamic consent form. Furthermore, after the dynamic consent form is completed, the personal data provider can select a certificate from the competent authority certificate management module 33, the system-generated certificate management module 34, and the personal certificate management module 35 through the human-computer interface 31 of the certificate management subsystem 3. The certificate signing module 32 then signs an electronic signature based on the certificate to generate an authorization certificate, thereby completing a signed document. The dynamic consent module 22 in the dynamic consent subsystem 2 of this invention then calculates the hash value of the dynamic consent form and integrates the dynamic consent form and authorization certificate, so that the hash value of the dynamic consent form and the authorization certificate are uploaded to the blockchain 52 via the blockchain upload module 51 in the blockchain subsystem 5 of this invention. After the personal data provider completes the signing of the dynamic consent form, a personal physical examination is conducted through a hospital. The plan analyzes the personal physical examination and generates analyzed personal health data, which is stored in a personal data database 6. When the personal data provider agrees to authorize the use of personal data, the de-identification subsystem 4 of this invention de-identifies the personal data of the personal data provider to generate de-identified data. At the same time, a hash value is calculated based on the personal data and the corresponding de-identified data. For example, medical record numbers in the personal data are replaced with meaningless unique codes. The personal data and the replaced information can be separately recorded in the personal data use authorization system 1 of this invention. In addition, the de-identification database 41 in the de-identification subsystem 4 of this invention stores the de-identified data. Next, the hash values ​​of the dynamic personal data and de-identified data are uploaded to blockchain 52 via blockchain-on-chain module 51 in the blockchain subsystem 5 of this invention. If, in the future, this health big data project makes unexpected discoveries while analyzing data from personal data providers, such as potential significant disease risks, the de-identified data can be re-linked to the personal data provider's data through the personal data usage authorization system 1 of this invention. Simultaneously, the data processed by the personal data usage authorization system 1 of this invention can be stored in other databases to facilitate the reuse of the health data from this project.

[0048] In another example, when a personal data provider wants to modify part of the dynamic consent form already filled out for this project, the personal data provider logs into the Personal Data Use Authorization System 1 of this project and selects the signed dynamic consent form through the human-machine interface 21 via the intention change module 23. After adjusting the intended changes to the dynamic consent form, the modified dynamic consent form is sent to the dynamic consent form module 22. After the modified dynamic consent form is filled out, the personal data provider can select a certificate from the competent authority certificate management module 33, the system-generated certificate management module 34, and the private certificate management module 35 through the human-machine interface 31 in the certificate management subsystem 3 of this project. The certificate signing module 32 then signs an electronic seal based on the certificate to generate an authorization certificate, thereby completing a signed document. The dynamic consent form module 22 in the dynamic consent form subsystem 2 of this project then calculates the hash value of the modified dynamic consent form and integrates the modified dynamic consent form and the authorization certificate, so that the hash value of the modified dynamic consent form and the authorization certificate are uploaded to the blockchain 52 via the blockchain uploading module 51 in the blockchain subsystem 5 of this project.

[0049] In another example, when a personal data provider wishes to withdraw from this program due to personal reasons, the personal data provider logs into the Personal Data Use Authorization System 1 of this invention and selects the signed dynamic consent form through the human-computer operation interface 21 via the intention change module 23. After adjusting the intention change content (i.e., selecting to withdraw) in the dynamic consent form, the modified dynamic consent form will be sent to the dynamic consent form module 22, and dynamic consent form withdrawal record information will be generated. Then, the dynamic consent form withdrawal record information will be uploaded to the blockchain 52 via the blockchain on-chain module 51 in the blockchain subsystem 5 of this invention, so that the personal data provider can check it in the future.

[0050] In summary, the personal data usage authorization system provided in this work employs technologies such as dynamic consent forms, credential management, de-identification, and blockchain, thus allowing for the secondary authorization and use of de-identified data corresponding to personal data, thereby protecting the personal wishes of personal data providers.

[0051] Please see Figure 6 As shown below, the steps of the blockchain-based dynamic authorization method for personal data disclosed herein will be described in detail.

[0052] First, this disclosure provides a request interface for a data requester to submit a "use request" for the personal data of a data owner. The "use request" referred to in this disclosure includes, but is not limited to, the data requester's identity data, the scope of the personal data to be used (a specific portion or all), the purpose of use, the date and time range of use, and the number of times of use. This disclosure also includes an authorization interface for a data owner to agree to or refuse a use request for their personal data, or to modify the use request (e.g., change the scope of personal data, the date and time range of use, or the number of times of use) before agreeing to it.

[0053] The request interface and the authorization interface are preferably (but not limited to) provided by a decentralized application (DApp). A DApp is an application built on blockchain technology. Unlike traditional centralized applications, DApps distribute data storage and processing across multiple nodes in the blockchain network during operation, rather than centralizing it on a single centralized server. Because data storage and processing are distributed across multiple nodes and utilize encryption technology, DApps typically offer extremely high security.

[0054] The architecture of this decentralized application is divided into a front-end (i.e., the aforementioned request application interface, authorization interface, etc.) and a back-end (the smart contracts, which will be discussed later). The front-end interface is not stored on the blockchain, but is (but not limited to) a conventional web application using technologies such as HTML, CSS, and JavaScript (providing one or more web pages), running on a traditional or decentralized web server. The back-end smart contracts, which handle business logic, data storage, and transaction processing, are stored on the blockchain, with a copy existing on each node.

[0055] Decentralized applications (Decentralized Applications) and smart contracts, which will be used later in this disclosure, are both important mechanisms of blockchain. In this disclosure, the decentralized application provides a request interface and an authorization interface, allowing personal data requesters and owners to interact with smart contracts on the blockchain and use their functions. Specifically, personal data requesters or owners access the front-end request interface or authorization interface through a web browser on a mobile phone, computer, or other device, and then interact with the back-end smart contracts through these interfaces. The back-end smart contracts receive requests, execute the corresponding business logic, and return the results to the front-end interface. Simultaneously, all transactions and state changes are recorded on the blockchain and broadcast to all nodes.

[0056] Next, as Figure 6 As shown, this disclosure allows a data requester to submit a request for use of a data owner's personal data through this request application interface. After the request is submitted, it will be reviewed by the personal data administrator. This disclosure may also provide a similar request application interface or authorization interface, or a management and review interface based on a decentralized application. Further details will not be repeated here.

[0057] After the personal data administrator approves the request, this disclosure will then notify the relevant personal data owner of the usage requirement. This notification may be delivered to the personal data owner via email, SMS, or other mechanisms. In addition to the aforementioned usage requirement, the notification will also include a link to access the authorized usage interface.

[0058] The data owner agrees to, refuses, or modifies the usage request through the authorization interface. If the data owner agrees to the usage request (or the modified usage request), the smart contract corresponding to the authorization interface generates an authorization credential based on a blockchain token and "stores" it in the data requester's blockchain wallet. This authorization credential records the content of the aforementioned usage request (or modified usage request) (such as the scope of personal data used, the date and time range of use, the number of times used, etc.). The term "stores" is a colloquial expression; more precisely, it means linking the authorization credential to the unique address of the blockchain wallet.

[0059] Tokens are mechanisms for issuing, managing, transferring, and trading on a blockchain, representing various assets or values. Tokens include currencies (such as Ethereum), physical assets (such as gold, real estate, and artwork), and specific rights or functions (such as voting rights and access rights). Tokens use blockchain technology to ensure security and transparency, and can be tracked and recorded on the blockchain, thereby ensuring the authenticity and immutability of the token's issuance, management, transfer, and trading.

[0060] This authorization certificate is a type of non-fungible token (NFT). Unlike cryptocurrency tokens (such as Ethereum), NFTs are not fungible, and each NFT has a unique identity. Therefore, the authorization certificate based on NFT, generated by the consent of each data owner for each user's use of the data, is unique and non-fungible.

[0061] Preferably, this authorization certificate is a special type of non-tradable, non-transferable so-called soul-bound non-fungible token (NFT). The term "soul-bound" implies a close connection between this NFT and its holder, who possesses special rights to the corresponding asset.

[0062] As previously stated, the creation and management of this authorization credential are accomplished through a smart contract provided in this disclosure. A smart contract is an automated computer program that executes on a blockchain. It contains pre-written code that automatically performs calculations when specific conditions are met to implement pre-planned business logic and tracks related transactions and decisions. Smart contracts are commonly used to manage digital assets (such as the aforementioned tokens), execute transactions, and implement decentralized services.

[0063] The code for a smart contract is typically stored on every node of the blockchain (each node has an identical copy of the smart contract). When a smart contract is deployed to the blockchain, its code and initial state are recorded in a block and broadcast across the entire blockchain network. Each participating node receives and stores the smart contract's code and state locally. Therefore, all nodes have an identical copy of the smart contract. When the smart contract is triggered for execution, each node executes the same contract code and updates its state based on the execution result. These results are also broadcast across the entire blockchain network and verified and recorded by each node. In this way, the state and operational results of the smart contract can be verified and recorded on all nodes of the blockchain network, thus ensuring its transparency, security, and immutability.

[0064] If the data owner agrees to the usage request, the authorization interface initiates the corresponding smart contract, creates a non-fungible token representing the authorization credential, and links it to the data user's blockchain wallet. In other words, the decentralized application (DApplication) of the authorization interface serves as the interface for the data owner to interact with the blockchain, while the smart contract is the program code that implements the business logic and functionality behind the DApplication. Note that smart contracts can be shared by multiple DApplications, and are not limited to a single DApplication.

[0065] The creation, transfer, and destruction of the aforementioned authorization credentials based on blockchain tokens, as well as transaction records, are stored on the blockchain as part of the smart contract state of each node. Therefore, there is a copy of this information on each node of the blockchain.

[0066] A data requester's blockchain wallet contains an authorization credential created by the data owner, signifying that the data requester has obtained authorization from the data owner to use the latter's personal data. The data requester accesses the data owner's personal data through the data access interface provided in this disclosure. Like the request interface and the authorization interface, this data access interface is preferably also the front end of a decentralized application, and its operation will invoke a corresponding smart contract. This smart contract can be the same as or a different smart contract from the data request interface and the authorization interface.

[0067] Therefore, when a data requester requests access to a data owner's personal data through this personal data access interface, the interface invokes its corresponding smart contract. This smart contract verifies that the data requester's blockchain wallet is linked to the authorization certificate created by the data owner, and that the access complies with the usage requirements stated in the authorization certificate (such as the scope of personal data used, the date and time range of use, and the number of uses). Then, after the access is verified by the smart contract, the smart contract decrypts and reassembles the relevant personal data stored on the blockchain and provides it to the data requester through the personal data access interface.

[0068] When the smart contract detects that a user's blockchain wallet's authorization certificate has expired (e.g., it has exceeded its recorded usage date and time range, or it has reached the required number of uses), the smart contract will automatically burn the tokens associated with that authorization certificate. Burning tokens on the blockchain means permanently removing them from the supply, typically by sending them to a special address (called a burn address or zero address). Once the tokens are sent to this address, they can no longer be used because their private keys are no longer available, thus the tokens are permanently lost. Burning tokens is an irreversible operation; once a token is burned, it cannot be recovered.

[0069] In addition to automatically destroying expired authorization tokens through the smart contract of the aforementioned personal data access interface, a personal data owner can also request the cancellation of previously created, still-valid usage authorizations at any time through the aforementioned authorization usage interface. This is also achieved by destroying the tokens of the already created usage authorizations through the smart contract of the authorization usage interface.

[0070] Furthermore, an individual data owner can modify an existing, valid usage authorization at any time through the aforementioned authorization interface (e.g., changing the scope of personal data, the date and time range of use, or the number of uses). This is achieved by first destroying the existing usage authorization token through a smart contract within the authorization interface, and then creating a new, blockchain-based authorization credential and linking it to the individual data requester's blockchain wallet. This new authorization credential records the modified usage requirements (such as the scope of personal data used, the date and time range of use, and the number of uses).

[0071] This disclosure also provides a system for implementing the aforementioned dynamic authorization of personal data. For example... Figure 7 As shown, this system comprises the following components:

[0072] A blockchain 10 comprises multiple decentralized nodes 102 connected via a network. This blockchain can be a public, private, hybrid, or consortium blockchain. It can also consist of a single blockchain or multiple blockchains. A data owner's personal data has been added to and stored on node 102 of this blockchain by a data custodian according to the blockchain's block-building method.

[0073] A first decentralized application 20 includes a front-end request interface 202 and a back-end first smart contract 204. The request interface 202 runs on a first server 104, allowing a data requester to submit a request to use the personal data of the data owner. The first server 104 is one of the nodes 102, which may be a web server, and the request interface is a web application running on that web server. The data requester accesses the web application and uses the authorization request interface 202 through a web browser on a mobile phone, computer, or other device.

[0074] A second decentralized application 30 includes a front-end authorization interface 302 and a back-end second smart contract 304. The authorization interface 302 runs on a second server 106, allowing the personal data owner to agree to, refuse, or modify a request to use their personal data. The second server 106 is one of the nodes 102, and may be a web server; the authorization interface is a web application running on that web server. The personal data owner accesses the web application and uses the authorization interface 302 through a web browser on a mobile phone, computer, or other device.

[0075] The first server 104 and the second server 106 can be the same server. The first smart contract 204 and the second smart contract 304 can be the same smart contract. The first and second smart contracts 204 and 304 are stored on the blockchain and a copy exists on each node 102.

[0076] After the first smart contract 204 is initiated via the request application interface 202, it transmits the usage request to a personal data custodian. Upon approval by the personal data custodian, the first smart contract 204 notifies the personal data owner of the usage request. The personal data owner, upon receiving the notification, accesses the authorization interface 302 to agree, refuse, or modify and agree to the usage request. If the personal data owner agrees to the usage request, or agrees after modification, the authorization interface 302 initiates the second smart contract 304. The second smart contract 304 generates an authorization certificate based on a blockchain token and links this authorization certificate to the personal data requester's blockchain wallet 50.

[0077] A third decentralized application 40 includes a front-end personal data access interface 402 and a back-end third smart contract 404. The personal data access interface 402 runs on a third server 108, allowing the personal data requester to access the personal data of the data owner. The third server 108 is one of the nodes 102, and the personal data access interface 402 can provide data access, for example, via an API, to the application running on the third server 108. The personal data requester uses the personal data access interface 402 through a query program on a computer or other device.

[0078] When a user requests access to the personal data of the data owner via the personal data access interface 402, the interface calls its corresponding third smart contract 404. The third smart contract 404 verifies whether the user's blockchain wallet 50 is connected to the authorization certificate created by the data owner and whether it meets the usage requirements stated in the authorization certificate. After verification, the third smart contract 404 decrypts and reassembles the relevant personal data stored on the blockchain and provides it to the user via the personal data access interface 402. If the third smart contract 404 discovers that the authorization certificate linked to the user's blockchain wallet 50 has expired, it will automatically destroy the tokens associated with that authorization certificate.

[0079] The data owner can also request the cancellation of previously created, yet-to-expire usage authorizations at any time through the aforementioned authorization interface 302. This is achieved by destroying the tokens associated with the created usage authorizations through the second smart contract 304 of the authorization interface 302.

[0080] The personal data owner can also modify an existing, valid usage authorization at any time through the aforementioned authorization interface 302. This is achieved by first destroying the token of the existing usage authorization through the second smart contract 302 of the authorization interface 302, and then creating a new, blockchain-based authorization certificate and linking it to the personal data requester's blockchain wallet 50. This new authorization certificate records the modified usage request details.

[0081] The third server 108 may be the same server as the first server 104 or the second server 106. The third smart contract 404 may be the same smart contract as the first smart contract 204 or the second smart contract 304. The third smart contract 404 is stored on the blockchain and a copy exists on each node 102.

[0082] The detailed description of the specific embodiments above is intended to more clearly describe the features and spirit of this disclosure, and is not intended to limit the scope of this disclosure to the specific embodiments disclosed above. Rather, the aim is to cover various modifications and equivalent arrangements within the scope of the claims to which this disclosure is intended.

Claims

1. A blockchain-based method for dynamic authorization of personal data, enabling a data owner to dynamically authorize a data requester to use their personal data stored on a blockchain, comprising the following steps: The recipient of the personal data request submits a request for use of the personal data owner's personal data through a request application interface; Notify the data owner of this usage request; Receive consent from the owner of the personal data through an authorized use interface, or consent from the owner of the personal data after modifying the usage requirements through the authorized use interface; Produce a pair of authorization credentials based on blockchain non-fungible tokens that should be used to meet the needs of the individual data user and link them to the user's blockchain wallet. The request of the person requesting the personal data to access the personal data owner's personal data through a personal data access interface; The blockchain wallet of the person requesting the personal data verifies that it contains the authorization credential created by the owner of the personal data. as well as Once the authorization credential is verified, the personal data of the data owner stored on the blockchain will be made available to the data requester for access.

2. The blockchain-based dynamic authorization method for personal data as described in claim 1 further comprises the following steps: When the personal data access interface detects that the authorization credential has expired, it will automatically destroy the authorization credential.

3. The blockchain-based dynamic authorization method for personal data as described in claim 1 further comprises the following steps: A request from the data owner to destroy the authorization certificate through the authorization interface; and Destroy the authorization certificate.

4. The blockchain-based dynamic authorization method for personal data as described in claim 1 further comprises the following steps: The recipient of the personal data owner has a request to modify the usage requirements through the authorized usage interface; Destroy the authorization certificate; and The system generates a corresponding modified usage requirement, another authorization certificate based on a blockchain non-fungible token, and links it to the blockchain wallet of the individual data user.

5. The blockchain-based dynamic authorization method for personal data as described in claim 1, wherein the blockchain is a public chain, a private chain, a hybrid chain, or a consortium chain.

6. The blockchain-based dynamic authorization method for personal data as described in claim 1, wherein the blockchain comprises a single chain or multiple chains.

7. The blockchain-based dynamic authorization method for personal data as described in claim 1, wherein the usage requirement includes part or all of the personal data to be used, the purpose of use, the date and time range of use, and the number of times it will be used.

8. The blockchain-based dynamic authorization method for personal data as described in claim 1, wherein the authorization certificate is a non-tradable, soul-bound, non-fungible token.

9. The blockchain-based dynamic authorization method for personal data as described in claim 1, wherein the request application interface, the authorization usage interface, and the personal data access interface are provided by a decentralized application or by a single decentralized application, respectively.

10. The blockchain-based dynamic authorization method for personal data as described in claim 9, wherein each decentralized application implements the functions of the request application interface, the authorization usage interface, and the personal data access interface through a corresponding smart contract.

11. A blockchain-based dynamic authorization system for personal data, enabling a data owner to dynamically authorize a data requester to use their personal data, the system comprising: A blockchain contains multiple nodes, and the personal data of the data owner has been added to and stored on the nodes of the blockchain according to the blockchain's block construction method. The first decentralized application includes a front-end request interface and a back-end smart contract, wherein... The request interface allows the user to submit a request to use the personal data of the data owner. The first smart contract notifies the data owner of the usage request. The first smart contract is stored on each of these nodes. The first server is one of the multiple nodes that runs the request interface. A second decentralized application includes a front-end authorization interface and a back-end second smart contract. The authorization interface allows the personal data owner to agree to or refuse the use request for their personal data, or to agree to the use request after modification. After the personal data owner agrees to the use request or agrees to the use request after modification, the second smart contract generates an authorization certificate based on a blockchain non-fungible token and links the authorization certificate to the personal data requester's blockchain wallet. The second smart contract is stored on each of these nodes. A second server, which is one of the plurality of nodes, runs the authorized user interface; A third decentralized application includes a front-end personal data access interface and a back-end third smart contract. The personal data access interface allows a user to request access to the personal data of the data owner. The third smart contract verifies whether the user's blockchain wallet is connected to the authorization certificate created by the data owner, and whether the request conforms to the usage requirements recorded in the authorization certificate. After verification, the third smart contract provides the data owner's personal data stored on the blockchain to the user via the personal data access interface. The third smart contract is stored on each of the plurality of nodes. A third server, one of the multiple nodes, runs the personal data access interface.

12. The blockchain-based dynamic authorization system for personal data as described in claim 11, wherein when a third smart contract discovers that the authorization credential has expired, the third smart contract automatically destroys the authorization credential.

13. The blockchain-based dynamic authorization system for personal data as described in claim 11, wherein after receiving a request from the personal data owner to destroy the authorization certificate, the second smart contract destroys the authorization certificate.

14. The blockchain-based dynamic authorization system for personal data as described in claim 11, wherein after the authorization user interface receives a request from the personal data owner to modify the usage requirements, the second smart contract destroys the authorization certificate; and The second smart contract generates another authorization credential based on a blockchain-based non-fungible token for the modified usage request and links it to the blockchain wallet of the individual data requester.

15. The blockchain-based dynamic authorization system for personal data as described in claim 11, wherein the blockchain is a public chain, a private chain, a hybrid chain, or a consortium chain.

16. The blockchain-based dynamic authorization system for personal data as described in claim 11, wherein the blockchain comprises a single chain or multiple chains.

17. The blockchain-based dynamic authorization system for personal data as described in claim 11, wherein the usage requirement includes part or all of the personal data to be used, the purpose of use, the date and time range of use, and the number of times it will be used.

18. The blockchain-based dynamic authorization system for personal data as described in claim 11, wherein the authorization certificate is a non-tradable, soul-bound, non-fungible token.

19. The blockchain-based dynamic authorization system for personal data as described in claim 11, wherein the first server, the second server, and the third server are the same server.

20. The blockchain-based dynamic authorization system for personal data as described in claim 11, wherein the first smart contract, the second smart contract, and the third smart contract are the same smart contract.

Images