# US 2021/0344496 A1 · Blockchain-based data authorization method and apparatus > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 2021/0344496 A1 - Document ID: US20210344496A1 - Status: Published application - Kind: A1 - Application number: 17/378,424 - Filed: 2021-07-16 - Published: 2021-11-04 - Earliest claimed: 2019-07-31 - Assignees: Advanced New Technologies Co., Ltd. - Applicants: Advanced New Technologies Co., Ltd. - Inventors: Changzheng Wei; Ying Yan; Hui Zhang; Yujun Peng - Web page: https://patentgrep.com/patent/US20210344496A1 ## CPC - H04L 9/3234: {involving additional secure or trusted devices, e.g. TPM, smartcard, USB or software token (network architectures or network communication protocols for supporting authentication of entities using an additional device in a packet data network H04L63/0853)} - H04L 63/10: {for controlling access to devices or network resources} - G06F 21/31: User authentication - G06F 21/57: Certifying or maintaining trusted computer platforms, e.g. secure boots or power-downs, version controls, system software checks, secure updates or assessing vulnerabilities - G06F 21/602: {Providing cryptographic facilities or services} - G06F 21/6272: {by registering files or documents with a third party} - G06F 21/64: Protecting data integrity, e.g. using checksums, certificates or signatures - H04L 9/0637: {Modes of operation, e.g. cipher block chaining [CBC], electronic codebook [ECB] or Galois/counter mode [GCM]} - H04L 9/0643: {Hash functions, e.g. MD5, SHA, HMAC or f9 MAC} - H04L 9/30: Public key, i.e. encryption algorithm being computationally infeasible to invert or user's encryption keys not requiring secrecy - H04L 9/3213: {using tickets or tokens, e.g. Kerberos (network architectures or network communication protocols for entities authentication using tickets in a packet data network H04L63/0807)} - H04L 9/3239: {involving non-keyed hash functions, e.g. modification detection codes [MDCs], MD5, SHA or RIPEMD} - H04L 63/0442: {wherein the sending and receiving network entities apply asymmetric encryption, i.e. different keys for encryption and decryption (cryptographic mechanisms or cryptographic arrangements for public-key encryption H04L9/30)} - H04L 63/08: {for authentication of entities (cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32)} - H04L 63/101: {Access control lists [ACL]} - G06F 2221/2115: Third party - H04L 9/50: {using hash chains, e.g. blockchains or hash trees} - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) ## Abstract One or more implementations of the present specification provide a blockchain-based data authorization method and apparatus. The method can include receiving, by a blockchain node, an authentication transaction submitted by a privacy computing platform, where the authentication transaction queries whether a data user has obtained authorization of target data possessed by a data owner, and in response to determining that the data user has obtained authorization of the target data, executing, by the blockchain node, a smart contract invoked by the authentication transaction to provide an authorization token to the privacy computing platform that instructs the privacy computing platform to obtain the target data, and send a computational result of one or more predetermined computational operations based on the target data to the data user. ## Claims ### Claim at position 1 1-20. (canceled) ### Claim 21 A computer-implemented method comprising: receiving, by one or more computers that are associated with an off-chain platform, a request that is initiated by a data user and that requests to obtain target data whose access is controlled by a different device and that is stored on the off-chain platform; transmitting, by the one or more computers that are associated with the off-chain platform and to a blockchain, an authentication request transaction that queries whether the data user has obtained authorization for the target data; obtaining, by the one or more computers that are associated with the off-chain platform, a transaction execution result event indicating that the different device has authorized the data user to obtain the target data in response to (i) the blockchain invoking a data authorization smart contract using information included in the authentication request transaction, (ii) the blockchain generating an authorization request event in response to invoking the data authorization smart contract, and (iii) the different device transmitting an authorization confirmation transaction to the blockchain to indicate that the data user has obtained authorization for the target data in response to the authorization request event; obtaining, by the one or more computers that are associated with the off-chain platform, an authorization token from the transaction execution result event; decrypting, by the one or more computers that are associated with the off-chain platform, encrypted target data using the authorization token to generate the target data; and providing, by the one or more computers that are associated with the off-chain platform. the target data to the data user. ### Claim 22 (depends on 21) The method of claim 21, wherein the data authorization smart contract is associated with an authorizer list. ### Claim 23 (depends on 21) The method of claim 21, wherein obtaining the transaction execution result event comprises: obtaining the transaction execution result event from a transaction log of the blockchain using an event listening mechanism. ### Claim 24 (depends on 21) The method of claim 21, comprising providing the authorization token to the data user. ### Claim 25 (depends on 21) The method of claim 21, comprising providing the authorization token to the data user based on a user ID associated with the data user. ### Claim 26 (depends on 21) The method of claim 21, comprising providing, by the one or more computers, the target data based on a privacy level associated with the target data. ### Claim 27 (depends on 21) The method of claim 21, wherein the authorization token comprises a temporary session key. ### Claim 28 A non-transitory, computer-readable medium storing one or more instructions executable by a computer system to perform operations comprising: receiving, by one or more computers that are associated with an off-chain platform, a request that is initiated by a data user and that requests to obtain target data whose access is controlled by a different device and that is stored on the off-chain platform; transmitting, by the one or more computers that are associated with the off-chain platform and to a blockchain, an authentication request transaction that queries whether the data user has obtained authorization for the target data; obtaining, by the one or more computers that are associated with the off-chain platform, a transaction execution result event indicating that the different device has authorized the data user to obtain the target data in response to (i) the blockchain invoking a data authorization smart contract using information included in the authentication request transaction, (ii) the blockchain generating an authorization request event in response to invoking the data authorization smart contract, and (iii) the different device transmitting an authorization confirmation transaction to the blockchain to indicate that the data user has obtained authorization for the target data in response to the authorization request event; obtaining, by the one or more computers that are associated with the off-chain platform, an authorization token from the transaction execution result event; decrypting, by the one or more computers that are associated with the off-chain platform, encrypted target data using the authorization token to generate the target data; and providing, by the one or more computers that are associated with the off-chain platform. the target data to the data user. ### Claim 29 (depends on 28) The medium of claim 28, wherein the data authorization smart contract is associated with an authorizer list. ### Claim 30 (depends on 28) The medium of claim 28, wherein obtaining the transaction execution result event comprises: obtaining the transaction execution result event from a transaction log of the blockchain using an event listening mechanism. ### Claim 31 (depends on 28) The medium of claim 28, wherein the operations comprise providing the authorization token to the data user. ### Claim 32 (depends on 28) The medium of claim 28, wherein the operations comprise providing the authorization token to the data user based on a user ID associated with the data user. ### Claim 33 (depends on 28) The medium of claim 28, wherein the operations comprise providing, by the one or more computers, the target data based on a privacy level associated with the target data. ### Claim 34 (depends on 28) The medium of claim 28, wherein the authorization token comprises a temporary session key. ### Claim 35 A computer-implemented system comprising: one or more processors; and one or more computer-readable memories coupled to the one or more processors and having instructions stored thereon that are executable by the one or more processors to perform one or more operations comprising: receiving, by one or more computers that are associated with an off-chain platform, a request that is initiated by a data user and that requests to obtain target data whose access is controlled by a different device and that is stored on the off-chain platform; transmitting, by the one or more computers that are associated with the off-chain platform and to a blockchain, an authentication request transaction that queries whether the data user has obtained authorization for the target data; obtaining, by the one or more computers that are associated with the off-chain platform, a transaction execution result event indicating that the different device has authorized the data user to obtain the target data in response to (i) the blockchain invoking a data authorization smart contract using information included in the authentication request transaction, (ii) the blockchain generating an authorization request event in response to invoking the data authorization smart contract, and (iii) the different device transmitting an authorization confirmation transaction to the blockchain to indicate that the data user has obtained authorization for the target data in response to the authorization request event; obtaining, by the one or more computers that are associated with the off-chain platform, an authorization token from the transaction execution result event; decrypting, by the one or more computers that are associated with the off-chain platform, encrypted target data using the authorization token to generate the target data; and providing, by the one or more computers that are associated with the off-chain platform. the target data to the data user. ### Claim 36 (depends on 35) The system of claim 35, wherein the data authorization smart contract is associated with an authorizer list. ### Claim 37 (depends on 35) The system of claim 35, wherein obtaining the transaction execution result event comprises: obtaining the transaction execution result event from a transaction log of the blockchain using an event listening mechanism. ### Claim 38 (depends on 35) The system of claim 35, wherein the operations comprise providing the authorization token to the data user. ### Claim 39 (depends on 35) The system of claim 35, wherein the operations comprise providing the authorization token to the data user based on a user ID associated with the data user. ### Claim 40 (depends on 35) The system of claim 35, wherein the operations comprise providing, by the one or more computers, the target data based on a privacy level associated with the target data.