WO2020177548A1 - Procédé et dispositif de commande d'autorité de chaîne de blocs - Google Patents

Procédé et dispositif de commande d'autorité de chaîne de blocs Download PDF

Info

Publication number
WO2020177548A1
WO2020177548A1 PCT/CN2020/076086 CN2020076086W WO2020177548A1 WO 2020177548 A1 WO2020177548 A1 WO 2020177548A1 CN 2020076086 W CN2020076086 W CN 2020076086W WO 2020177548 A1 WO2020177548 A1 WO 2020177548A1
Authority
WO
WIPO (PCT)
Prior art keywords
operated
account
blockchain
permission
authority
Prior art date
Application number
PCT/CN2020/076086
Other languages
English (en)
Chinese (zh)
Inventor
莫楠
廖飞强
白兴强
李辉忠
张开翔
范瑞彬
Original Assignee
深圳前海微众银行股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 深圳前海微众银行股份有限公司 filed Critical 深圳前海微众银行股份有限公司
Publication of WO2020177548A1 publication Critical patent/WO2020177548A1/fr

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/30—Authentication, i.e. establishing the identity or authorisation of security principals
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F2221/00—Indexing scheme relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F2221/21—Indexing scheme relating to G06F21/00 and subgroups addressing additional information or applications relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F2221/2141—Access rights, e.g. capability lists, access control lists, access tables, access matrices

Definitions

  • the embodiments of the present invention relate to the field of technology and finance technology, and in particular to a method and device for controlling permissions of a blockchain.
  • Blockchain is the use of block chain data structure to verify and store data, the use of distributed node consensus algorithms to generate and update data, the use of cryptography to ensure the security of data transmission and access, and the use of smart contracts composed of automated script codes.
  • a new distributed infrastructure and calculation method for programming and manipulating data For the public chain in the blockchain, there is no restriction on node joining, and the data on the chain is completely open, suitable for some publicization, and does not involve privacy information storage. But for private chains and consortium chains, because some private data storage is involved, it is necessary to control the permissions of the blockchain.
  • the role corresponding to the account is determined through the preset first association relationship, and then the authority of the account is determined according to the preset authority of the role, and then based on the authority of the account, the corresponding interface is called to the blockchain.
  • the Merkle tree of the main body of the block is operated to complete the transaction.
  • the corresponding relationship between roles and permissions needs to be saved in advance, and at the same time, the account permissions are limited to the preset permissions of the role, resulting in insufficient fine-grained control of the account permissions.
  • the embodiments of the present invention provide a blockchain permission control method and device.
  • an embodiment of the present invention provides a method for controlling permissions on a blockchain.
  • Each block in the blockchain stores a ledger in the form of a table.
  • the method includes:
  • the transaction request including transaction information and a transaction account
  • the operation content is executed in the table to be operated.
  • the authority table is preset and the authority of each account on the table in the blockchain is stored in the authority table, when the transaction account initiates a transaction and needs to operate the table in the blockchain, you can query the authority table to determine the operation authority and execute the table Operation to realize the authority control of the blockchain. Since the specific permissions of the account can be set freely in the permission table, and the account permissions can be added or deleted based on actual needs, compared with the role-based permission control, the control of the account permissions is more fine-grained and it is convenient to manage the account permissions.
  • the table to be operated is a system table or a user table
  • the system table is used to control the system functions of the blockchain
  • the user table is used to control the business functions of the blockchain.
  • the method before the determining the authority account corresponding to the table to be operated from the preset authority table, the method includes:
  • the method further includes:
  • the operation record of the table to be operated is sent to other network nodes in the blockchain network, so that the other network node determines from the permission table the corresponding table to be operated according to the identifier of the table to be operated
  • the authority account when it is determined that the transaction account matches the authority account corresponding to the table to be operated, execute the operation content in the table to be operated.
  • the other network nodes can verify the validity of the operation record of the table to be operated and execute the operation content, thereby realizing the synchronization of the table content in the blockchain network and ensuring Consistency and security of tables in the blockchain.
  • it also includes:
  • the permission table is located in a block of the blockchain
  • the updated permission table takes effect in the next block of the current block.
  • an embodiment of the present invention provides a permission control device for a blockchain.
  • Each block in the blockchain stores a ledger in the form of a table.
  • the device includes:
  • the obtaining module is used to obtain a transaction request, the transaction request including transaction information and a transaction account;
  • the analysis module is used to determine the table to be operated and the content of the operation in the table to be operated according to the transaction information, the table to be operated is located in a block of the blockchain;
  • the screening module is used to determine the authority account corresponding to the table to be operated from the preset authority table;
  • the control module is configured to execute the operation content in the table to be operated when it is determined that the transaction account matches the authority account corresponding to the table to be operated.
  • the table to be operated is a system table or a user table
  • the system table is used to control the system functions of the blockchain
  • the user table is used to control the business functions of the blockchain.
  • the screening module is also used to:
  • the operation content is a write operation.
  • control module is also used to:
  • the operation record of the table to be operated is sent to other network nodes in the blockchain network, so that the other network node determines from the permission table the corresponding table to be operated according to the identifier of the table to be operated
  • the authority account when it is determined that the transaction account matches the authority account corresponding to the table to be operated, execute the operation content in the table to be operated.
  • the screening module is also used to:
  • the updated permission table takes effect in the next block of the current block, and the permission table is located in a block of the blockchain.
  • an embodiment of the present invention provides a computer device, including at least one processing unit and at least one storage unit, wherein the storage unit stores a computer program, and when the program is executed by the processing unit, The processing unit executes the steps of the permission control method of the blockchain.
  • an embodiment of the present invention provides a computer-readable medium that stores a computer program executable by a computer device.
  • the program runs on the computer device, the computer device executes the authority control of the blockchain.
  • an embodiment of the present invention provides a computer program product, the computer program product includes a calculation program stored on a computer-readable medium, the computer program includes program instructions, when the program instructions are executed by a computer device , So that the computer equipment executes the steps of the blockchain permission control method.
  • the authority table is preset and the authority of each account to the table in the blockchain is stored in the authority table
  • the transaction account initiates a transaction and needs to operate the table in the blockchain, it can be determined by querying the authority table Operate permissions and perform operations on tables to achieve permission control on the blockchain. Since the specific permissions of the account can be set freely in the permission table, and the account permissions can be added or deleted based on actual needs, compared with the role-based permission control, the control of the account permissions is more fine-grained and it is convenient to manage the account permissions.
  • FIG. 1 is a schematic diagram of an application scenario provided by an embodiment of the present invention.
  • FIG. 2 is a schematic flowchart of a method for controlling permissions on a blockchain according to an embodiment of the present invention
  • FIG. 3 is a schematic flowchart of a method for controlling permissions on a blockchain according to an embodiment of the present invention
  • FIG. 4 is a schematic flowchart of a method for controlling permissions on a blockchain according to an embodiment of the present invention
  • FIG. 5 is a schematic structural diagram of a permission control device for a blockchain provided by an embodiment of the present invention.
  • Fig. 6 is a schematic structural diagram of a computer device provided by an embodiment of the present invention.
  • Blockchain uses block-chain data structure to verify and store data, uses distributed node consensus algorithm to generate and update data, uses cryptography to ensure the security of data transmission and access, and is composed of automated script codes A new distributed infrastructure and calculation method for programming and manipulating data with smart contracts.
  • consortium chain The consortium chain is between a public chain and a private chain. Several organizations jointly maintain a block chain with an access mechanism. The generation of each block is determined by a preselected node.
  • Smart contract is a service program written in solidity language that implements specific logic, and is published on the alliance chain in a binary manner for contract participants to execute and call on the alliance chain.
  • a control mechanism for accessing blockchain functions is achieved by controlling access to the blockchain. For example, based on the distributed storage of the FISCO BCOS alliance chain platform, by controlling the access to tables in the blockchain To achieve access to blockchain functions.
  • the consortium chain network includes multiple network nodes 101.
  • the node 101 includes a block chain authority control device.
  • the network node 101 may be a server or a server cluster composed of several servers, and the network nodes 101 are connected through a wireless network.
  • each organization corresponds to one or more network nodes 101, and the tables in each network node 101 in the alliance chain are synchronized in real time.
  • the institution initiates a transaction request through the transaction account in the network node 101.
  • the network node 101 After receiving the transaction request, the network node 101 determines the table to be operated and the operation content in the table to be operated according to the transaction information. Then, the authority account corresponding to the table to be operated is determined from the preset authority table, and when it is determined that the transaction account matches the authority account corresponding to the table to be operated, the operation content is executed in the table to be operated. The network node 101 then generates the operation record of the table to be operated and sends the operation record of the table to be operated to other network nodes 101 in the blockchain network.
  • the operation record includes the identifier of the table to be operated, operation content and transaction account.
  • the other network nodes 101 determine the permission account corresponding to the table to be operated from the permission table according to the identifier of the table to be operated, and when it is determined that the transaction account matches the permission account corresponding to the table to be operated, the operation content is executed in the table to be operated.
  • an embodiment of the present invention provides a flow of a blockchain permission control method, which can be executed by a blockchain permission control device, as shown in Figure 2, including The following steps:
  • Step S201 Obtain a transaction request.
  • the transaction request is initiated by the transaction account, and the transaction request includes transaction information and the transaction account.
  • Different transactions correspond to different transaction information.
  • the transaction information is the name of the table involved in deploying the contract, contract-related data, etc.
  • Step S202 Determine the table to be operated and the operation content in the table to be operated according to the transaction information.
  • the table to be operated is located in a block of the blockchain, and different transaction information corresponds to different tables to be operated.
  • the table to be operated can be a system table or a user table.
  • the system table is used to control the system functions of the blockchain
  • the user table is used to control the business functions of the blockchain.
  • the transaction account is based on the permissions in the permission table. Operate the system table of the blockchain to control the system functions of the blockchain.
  • the transaction account operates the user table of the blockchain according to the permissions in the permission table to control the business functions of the blockchain.
  • system tables include _sys_tables_ table, _sys_cns_ table, _sys_miners_ table, _sys_config_ table, _sys_table_access_ table, etc.
  • the sys_tables_ table stores the table field information of all tables in the blockchain system, and all table field information needs to be stored in the _sys_tables_ table before table creation can be performed. Deploying the contract needs to establish the contract table, and the contract operation user table needs to create the user table first. Therefore, permission control acts on the _sys_tables_ table to control the deployment of the contract and the creation of the user table.
  • the _sys_cns_ table saves CNS information for deploying contracts in the blockchain using Contract Name Service (Contract Name Service, CNS for short).
  • CNS information includes the contract name, contract version number, contract deployment address, and contract application binary interface (Application Binary Interfac, ABI for short).
  • Using CNS to deploy contracts requires CNS information to be written into the _sys_cns_ table. Therefore, permission control acts on the _sys_cns_ table to control whether an account has the permission to deploy contracts using CNS.
  • the _sys_miners_ table stores the information of all node types in the blockchain. There are three types of nodes in the blockchain network, namely, accounting nodes, observation nodes, and free nodes. The conversion of these three types of node types can be realized by operating the _sys_miners_ table. Therefore, permission control acts on the _sys_miners_ table to control the type conversion of blockchain nodes.
  • the _sys_config_ table saves system configuration information in the blockchain, such as setting tx_count_limit (the upper limit of the number of transactions in the block) and tx_gas_limit (the upper limit of gas for transactions). Therefore, permission control acts on the _sys_config_ table to control the setting permissions of system configuration information.
  • the user table is a table related to the business, and the authority control acting on each user table will finely control the related business functions.
  • the user table 1 is an operating user table of contract A, which includes a list of users who can operate contract A.
  • the user table 2 is a user table of loan services, which includes a list of users who can loan services.
  • Step S203 Determine the authority account corresponding to the table to be operated from the preset authority table.
  • the permission table is used to store permission setting information, and the permission table also belongs to a system table.
  • the permission control usage rules are determined. For example, a management node can be selected from the blockchain network, and then the account corresponding to the management node can be an administrator account. Only the administrator account can use the permission setting function, and the non-administrator account has no permission setting function.
  • the permission table is located in a block of the blockchain. When the permission table is updated, the updated permission table takes effect in the next block of the current block.
  • a new block is generated after the current block, and the new permission record is stored in the block body of the new block.
  • the permission record A is modified in the permission table, a new block is generated after the current block, and the modified permission record A is stored in the block body of the new block.
  • the embodiment of the present invention provides an example of a permission table, as shown in Table 1:
  • a permission record in the permission table, includes table name, account name, effective block height, and status fields.
  • the effective block height is the position and status of the effective block of the permission record in the blockchain.
  • a preset permission contract interface can be used to operate the permission table.
  • Permission contract interfaces include insert interface, remove interface, queryByName interface, etc.
  • the insert interface sets permission records through the table name and account address, and returns the number of records set. The set record will be saved in the permission table, and the same permission record is refused to be set repeatedly, that is, 0 is directly returned.
  • the remove interface removes the set permission records through the table name and account address, and returns the number of removed records.
  • the _status_ field of the record to be removed is set from "0" to "1", and the repeated removal of the same permission record is refused, that is, 0 is directly returned.
  • the queryByName interface queries the set permission records through the table name, and the records are returned in the form of json strings. This interface is used to query the permission records.
  • Java SDK side API and command line tool commands are as follows:
  • String add This API calls the insert interface of the permission contract to set permission information.
  • the corresponding command is addAuthority (abbreviated command is aa), and the parameters are the table name and account address.
  • This API calls the queryByName interface of the permission contract to query permission information.
  • the corresponding command is queryAuthority (the abbreviated command is qa), and the parameter is the table name.
  • Step S204 when it is determined that the transaction account matches the authority account corresponding to the table to be operated, the operation content is executed in the table to be operated.
  • the operation content is a write operation
  • the authority account corresponding to the table to be operated is determined from the preset authority table, and when it is determined that the transaction account matches the authority account corresponding to the table to be operated, The write operation is performed in the table to be operated.
  • the operation content is a read operation
  • the read operation is performed in the table to be operated.
  • setting transaction account 1 needs to deploy a HelloWorld contract, and the network node receives a transaction request, and the transaction request includes the content of transaction account 1 and HelloWorld contract.
  • the network node determines that the transaction account 1 needs to write the contents of the HelloWorld contract into the _sys_tables_ table based on the transaction information, it queries the permission record of the _sys_tables_ table from the permission table to determine the permission account of the _sys_tables_ table. If trading account 1 is included in the authority account, write the content of the HelloWorld contract to the _sys_tables_ table, otherwise refuse to write the content of the HelloWorld contract to the _sys_tables_ table. When the network node determines that the transaction account 1 needs to read the content of the sys_tables_ table according to the transaction information, it directly reads the content of the sys_tables_ table.
  • the authority account corresponding to the table to be operated is determined from the preset authority table, and when it is determined that the transaction account matches the authority account corresponding to the table to be operated, Perform a write operation or a read operation in the table to be operated.
  • the permission table corresponding to the read operation and the permission table corresponding to the write operation can be preset.
  • the operation content is a write operation
  • the authorization account corresponding to the table to be operated is determined from the authorization table corresponding to the write operation, and when it is determined that the transaction account matches the authorization account corresponding to the table to be operated, the write operation is performed in the table to be operated.
  • the authorization account corresponding to the table to be operated is determined from the authorization table corresponding to the read operation, and when it is determined that the transaction account matches the authorization account corresponding to the table to be operated, the read operation is performed in the table to be operated.
  • the authority table is preset and the authority of each account on the table in the blockchain is stored in the authority table, when the transaction account initiates a transaction and needs to operate the table in the blockchain, you can query the authority table to determine the operation authority and execute the table Operation to realize the authority control of the blockchain. Since the specific permissions of the account can be set freely in the permission table, and the account permissions can be added or deleted based on actual needs, compared with the role-based permission control, the control of the account permissions is more fine-grained and it is convenient to manage the account permissions.
  • an operation record of the table to be operated is generated, the operation record includes the identifier of the table to be operated, the operation content and the transaction account, and the operation record of the table to be operated is sent to the blockchain network
  • Other network nodes other network nodes determine the permission account corresponding to the table to be operated from the permission table according to the identifier of the table to be operated, and when it is determined that the transaction account matches the permission account corresponding to the table to be operated, the operation content is executed in the table to be operated .
  • the tables of each network node in the blockchain network are synchronized in real time.
  • a network node performs a write operation in the table to be operated and changes the content in the table to be operated, it needs to synchronize the changed content in the table to be operated to other network nodes in the blockchain network.
  • other network nodes receive the operation record of the operation table, they first need to verify the legitimacy of the operation record of the operation table. Specifically, according to the identifier of the table to be operated in the operation record, determine the permission corresponding to the table to be operated from the permission table.
  • the operation record is determined to be legal, and then the operation content is executed in the table to be operated, so as to synchronize the content of the table in the blockchain network and ensure that the blockchain is Consistency and safety of the table.
  • the following describes a block chain permission control method provided by the embodiments of the present invention in combination with specific implementation scenarios.
  • the method is executed by a network node. As shown in FIG. 4, the method includes the following step:
  • Step S401 Obtain a transaction request of the transaction account.
  • Step S402 Determine the list to be operated and the content of the operation according to the transaction request.
  • the table to be operated can be a system table or a user table.
  • Step S403 It is judged whether the operation content is a write operation, if not, step S404 is executed, otherwise, step S405 is executed.
  • Step S404 obtain the query result.
  • step S405 it is judged whether there is a permission record cache, if yes, step S406 is executed, otherwise, step S409 is executed.
  • the permission record when a certain permission record has been queried in the permission table before, the permission record can be cached, so when a request for querying permission records is received, the cache can be directly queried instead of querying the permission table every time , Thereby improving query efficiency.
  • step S406 it is judged whether the transaction account has authority, if so, step S407 is executed, otherwise, step S408 is executed.
  • Step S407 perform a write operation.
  • Step S408 Reject the write operation.
  • Step S409 query the permission table.
  • the network node receives the transaction request.
  • the transaction request deploys the HelloWorld contract for transaction account 1.
  • the transaction to deploy the contract needs to write to the _sys_tables_ table.
  • the network node queries the permission record of the _sys_tables_ table in the permission table, and determines the permission account of the _sys_tables_ table from the permission record. Then compare trading account 1 with the authority account of the _sys_tables_ table.
  • the transaction account 1 is the authority account of the _sys_tables_ table
  • write the relevant content of the HelloWorld contract into the _sys_tables_ table to deploy The contract is successful.
  • the network node receives a transaction request, the transaction request deploys the HelloWorld contract for transaction account 2.
  • the transaction to deploy the contract needs to write to the _sys_tables_ table.
  • the network node queries the permission record of the _sys_tables_ table in the permission table, and determines the permission account of the _sys_tables_ table from the permission record. Then compare trading account 2 with the authority account of the _sys_tables_ table.
  • the network node receives the transaction request.
  • the transaction request adds the operating user mm of the HelloWorld contract to the transaction account 2 and needs to write to the user table A.
  • the network node queries the permission record of user table A in the permission table, and determines the permission account of user table A from the permission record. Then the transaction account 2 is compared with the authority account of the user table A, and when the comparison result is that the transaction account 2 is the authority account of the user table A, the relevant information of the user mm is written into the user table A.
  • the transaction request adds the operating user nn of the HelloWorld contract to the transaction account 3, and the user table A needs to be written.
  • the network node queries the permission record of user table A in the permission table, and determines the permission account of user table A from the permission record. Then compare the transaction account 3 with the authority account of the user table A. When the comparison result is that the transaction account 3 is not the authority account of the user table A, the addition fails.
  • the authority table is preset and the authority of each account to the table in the blockchain is stored in the authority table
  • the transaction account initiates a transaction and needs to operate the table in the blockchain, it can be determined by querying the authority table Operate permissions and perform operations on tables to achieve permission control on the blockchain. Since the specific permissions of the account can be set freely in the permission table, and the account permissions can be added or deleted based on actual needs, compared with the role-based permission control, the control of the account permissions is more fine-grained and it is convenient to manage the account permissions.
  • an embodiment of the present invention provides a block chain permission control device. As shown in FIG. 5, the device 500 includes:
  • the obtaining module 501 is configured to obtain a transaction request, the transaction request including transaction information and a transaction account;
  • the analysis module 502 is configured to determine the table to be operated and the operation content in the table to be operated according to the transaction information, the table to be operated is located in a block of the blockchain;
  • the screening module 503 is configured to determine the authority account corresponding to the table to be operated from the preset authority table;
  • the control module 504 is configured to execute the operation content in the table to be operated when it is determined that the transaction account matches the authority account corresponding to the table to be operated.
  • the table to be operated is a system table or a user table
  • the system table is used to control the system functions of the blockchain
  • the user table is used to control the business functions of the blockchain.
  • the screening module 503 is further configured to:
  • the operation content is a write operation.
  • control module 504 is further configured to:
  • the operation record of the table to be operated is sent to other network nodes in the blockchain network, so that the other network node determines from the permission table the corresponding table to be operated according to the identifier of the table to be operated
  • the authority account when it is determined that the transaction account matches the authority account corresponding to the table to be operated, execute the operation content in the table to be operated.
  • the screening module 503 is further configured to:
  • the updated permission table takes effect in the next block of the current block, and the permission table is located in a block of the blockchain.
  • an embodiment of the present invention provides a computer device. As shown in FIG. 6, it includes at least one processor 601 and a memory 602 connected to the at least one processor.
  • the embodiment of the present invention does not limit the processor.
  • the connection between the processor 601 and the memory 602 in FIG. 6 is taken as an example.
  • the bus can be divided into address bus, data bus, control bus, etc.
  • the memory 602 stores instructions that can be executed by at least one processor 601. By executing the instructions stored in the memory 602, the at least one processor 601 can execute the aforementioned blockchain permission control method. step.
  • the processor 601 is the control center of the computer equipment, which can use various interfaces and lines to connect to various parts of the computer equipment, and control the authority by running or executing instructions stored in the memory 602 and calling data stored in the memory 602 .
  • the processor 601 may include one or more processing units, and the processor 601 may integrate an application processor and a modem processor.
  • the application processor mainly processes the operating system, user interface, and application programs, etc.
  • the adjustment processor mainly deals with wireless communication. It can be understood that the foregoing modem processor may not be integrated into the processor 601.
  • the processor 601 and the memory 602 may be implemented on the same chip, and in some embodiments, they may also be implemented on separate chips.
  • the processor 601 may be a general-purpose processor, such as a central processing unit (CPU), a digital signal processor, an application specific integrated circuit (ASIC), a field programmable gate array or other programmable logic devices, discrete gates or transistors Logic devices and discrete hardware components can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of the present invention.
  • the general-purpose processor may be a microprocessor or any conventional processor. The steps of the method disclosed in the embodiments of the present invention may be directly embodied as being executed and completed by a hardware processor, or executed and completed by a combination of hardware and software modules in the processor.
  • the memory 602 as a non-volatile computer-readable storage medium, can be used to store non-volatile software programs, non-volatile computer-executable programs and modules.
  • the memory 602 may include at least one type of storage medium, for example, it may include flash memory, hard disk, multimedia card, card-type memory, random access memory (Random Access Memory, RAM), static random access memory (Static Random Access Memory, SRAM), Programmable Read Only Memory (PROM), Read Only Memory (ROM), Electrically Erasable Programmable Read-Only Memory (EEPROM), magnetic memory, disk , CD, etc.
  • the memory 602 is any other medium that can be used to carry or store desired program codes in the form of instructions or data structures and that can be accessed by a computer, but is not limited thereto.
  • the memory 602 in the embodiment of the present invention may also be a circuit or any other device capable of realizing a storage function, for storing program instructions and/or data.
  • the embodiments of the present invention provide a computer-readable medium that stores a computer program executable by a computer device.
  • the computer device executes the blockchain Steps of the permission control method.
  • the embodiments of the present invention provide a computer program product.
  • the computer program product includes a calculation program stored on a computer-readable medium.
  • the computer program includes program instructions. When executed, the computer equipment is made to execute the steps of the permission control method of the blockchain.
  • the embodiments of the present invention may be provided as methods or computer program products. Therefore, the present invention may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, the present invention 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, CD-ROM, optical storage, etc.) containing computer-usable program codes.
  • a computer-usable storage media including but not limited to disk storage, CD-ROM, optical storage, etc.
  • These computer program instructions can also be stored in a computer-readable memory that can guide a computer or other programmable data processing equipment to work in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture including the instruction device.
  • the device implements the functions specified in one process or multiple processes in the flowchart and/or one block or multiple blocks in the block diagram.
  • These computer program instructions can also be loaded on a computer or other programmable data processing equipment, so that a series of operation steps are executed on the computer or other programmable equipment to produce computer-implemented processing, so as to execute on the computer or other programmable equipment.
  • the instructions provide steps for implementing functions specified in a flow or multiple flows in the flowchart and/or a block or multiple blocks in the block diagram.

Abstract

Selon la présente invention, des modes de réalisation concernent le domaine technique de la technologie scientifique et de la finance, et concernent un procédé et un dispositif de commande d'autorité de chaîne de blocs. Le procédé consiste : à obtenir une requête de transaction, la requête de transaction comprenant des informations de transaction et un compte de transaction, puis à déterminer une table à exploiter et un contenu d'exploitation en fonction des informations de transaction ; à déterminer, à partir d'une table d'autorité prédéfinie, un compte autorisé correspondant à ladite table, et à exécuter le contenu d'exploitation dans ladite table s'il est déterminé que le compte de transaction correspond au compte autorisé correspondant à ladite table. Étant donné que l'autorité de chaque compte pour des tables dans la chaîne de blocs est mémorisée dans une table d'autorité à l'avance, lorsqu'un compte de transaction lance une transaction et doit exploiter une table dans la chaîne de blocs, la commande d'autorité de la chaîne de blocs peut être obtenue par interrogation de la table d'autorité pour déterminer l'autorité d'exploitation et réaliser ensuite l'opération sur la table. Dans la table d'autorité, l'autorité d'un compte peut être établie librement et peut être ajoutée ou supprimée selon les besoins, de sorte qu'une commande plus nuancée de l'autorité de compte peut être obtenue, par comparaison avec la commande d'autorité dépendant d'un rôle, ce qui facilite la gestion de l'autorité de compte.
PCT/CN2020/076086 2019-03-05 2020-02-20 Procédé et dispositif de commande d'autorité de chaîne de blocs WO2020177548A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910163011.4 2019-03-05
CN201910163011.4A CN110008665B (zh) 2019-03-05 2019-03-05 一种区块链的权限控制方法及装置

Publications (1)

Publication Number Publication Date
WO2020177548A1 true WO2020177548A1 (fr) 2020-09-10

Family

ID=67166331

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/076086 WO2020177548A1 (fr) 2019-03-05 2020-02-20 Procédé et dispositif de commande d'autorité de chaîne de blocs

Country Status (2)

Country Link
CN (1) CN110008665B (fr)
WO (1) WO2020177548A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN117709947A (zh) * 2024-02-05 2024-03-15 广东通莞科技股份有限公司 基于区块链的pos机结算权限管理方法

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110008665B (zh) * 2019-03-05 2024-02-06 深圳前海微众银行股份有限公司 一种区块链的权限控制方法及装置
CN112468525B (zh) * 2019-09-06 2022-06-28 傲为有限公司 一种基于区块链的域名管理系统
CN113761581A (zh) * 2021-09-24 2021-12-07 支付宝(杭州)信息技术有限公司 区块链中的权限管控方法、装置和电子设备
CN115001718B (zh) * 2022-08-04 2023-01-20 树根格致科技(湖南)有限公司 数据处理方法、装置、计算机设备及可读存储介质

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107911373A (zh) * 2017-11-24 2018-04-13 中钞信用卡产业发展有限公司杭州区块链技术研究院 一种区块链权限管理方法及系统
CN108012582A (zh) * 2017-08-18 2018-05-08 达闼科技成都有限公司 区块链系统及其权限管理方法
CN109087214A (zh) * 2018-07-23 2018-12-25 江苏恒宝智能系统技术有限公司 一种基于区块链的天然气生活缴费管理系统
CN109344631A (zh) * 2018-09-18 2019-02-15 百度在线网络技术（北京）有限公司 区块链的数据修改及区块验证方法、装置、设备和介质
CN110008665A (zh) * 2019-03-05 2019-07-12 深圳前海微众银行股份有限公司 一种区块链的权限控制方法及装置

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106796685A (zh) * 2016-12-30 2017-05-31 深圳前海达闼云端智能科技有限公司 区块链权限控制方法、装置及节点设备
CN109241365B (zh) * 2018-08-23 2020-11-20 泰链（厦门）科技有限公司 区块链系统的构造方法、介质、计算机设备及区块链系统

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108012582A (zh) * 2017-08-18 2018-05-08 达闼科技成都有限公司 区块链系统及其权限管理方法
CN107911373A (zh) * 2017-11-24 2018-04-13 中钞信用卡产业发展有限公司杭州区块链技术研究院 一种区块链权限管理方法及系统
CN109087214A (zh) * 2018-07-23 2018-12-25 江苏恒宝智能系统技术有限公司 一种基于区块链的天然气生活缴费管理系统
CN109344631A (zh) * 2018-09-18 2019-02-15 百度在线网络技术（北京）有限公司 区块链的数据修改及区块验证方法、装置、设备和介质
CN110008665A (zh) * 2019-03-05 2019-07-12 深圳前海微众银行股份有限公司 一种区块链的权限控制方法及装置

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN117709947A (zh) * 2024-02-05 2024-03-15 广东通莞科技股份有限公司 基于区块链的pos机结算权限管理方法
CN117709947B (zh) * 2024-02-05 2024-04-19 广东通莞科技股份有限公司 基于区块链的pos机结算权限管理方法

Also Published As

Publication number Publication date
CN110008665B (zh) 2024-02-06
CN110008665A (zh) 2019-07-12

Similar Documents

Publication Publication Date Title
WO2020177548A1 (fr) Procédé et dispositif de commande d'autorité de chaîne de blocs
CN110636492B (zh) 使用区块链切换移动服务提供商
US11190525B2 (en) Blockchain system and permission management method thereof
JP2021525931A (ja) ブロックチェーンのための効率的な検証
KR20190111037A (ko) 컨소시엄 블록체인에 의한 스마트 계약 업그레이드 방법 및 시스템
CN112003858B (zh) 基于区块链的平台对接的方法、电子装置和存储介质
CN110855777B (zh) 一种基于区块链的节点管理方法及装置
TW202024953A (zh) 資料結構的讀取及更新方法、裝置、電子設備
CN112862490B (zh) 一种异步网络下的输出共识方法
US11070563B2 (en) Trace-based transaction validation and commitment
WO2021027532A1 (fr) Procédé et dispositif de vérification d'autorité pour contrat intelligent
CN111177701B (zh) 基于可信执行环境和安全芯片的密码功能服务实现方法和设备
CN104639650A (zh) 一种细粒度分布式接口访问控制方法及装置
WO2022134797A1 (fr) Procédé et appareil de stockage de fragmentation de données, dispositif informatique et support de stockage
CN114357498A (zh) 一种数据脱敏方法及装置
CN109802832A (zh) 一种数据文件的处理方法、系统、大数据处理服务器和计算机存储介质
CN111127206A (zh) 一种基于智能合约的区块链数据访问控制方法及装置
US20150156193A1 (en) Creating and managing certificates in a role-based certificate store
KR20050063669A (ko) 다수의 키 캐시 매니저가 보안 칩의 암호화 키 저장부리소스를 공유하는 방법 및 컴퓨터 판독가능 기록 매체
CN108713200A (zh) 用于将订阅加载到移动终端设备的嵌入式安全元件中的方法
CN117014175A (zh) 云系统的权限处理方法、装置、电子设备及存储介质
CN116015929B (zh) 一种联盟链准入管理方法及装置
CN111159752B (zh) 一种机构间信息共享方法和装置
CN110610069A (zh) 一种在web系统中调用REST接口的方法与装置
CN110602690A (zh) 一种应用于ZigBee系统的加密方法及装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 20766601

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 19.01.2022)

122 Ep: pct application non-entry in european phase

Ref document number: 20766601

Country of ref document: EP

Kind code of ref document: A1