License authorization management device and method based on block chain

Abstract

The invention discloses a license authorization management device based on a block chain, and the device comprises an on-chain intelligent contract service layer which is disposed on a block chain platform, and is used for converting the issuing, transferring, revoking, renewing and authorization verification services of license into contracts; the on-chain and off-chain interaction protocol layer is used for carrying out data and business logic interaction between the on-chain intelligent contract service layer and the off-chain calculation and storage layer by utilizing an interaction protocol; and the under-chain calculation and storage layer is used for processing license authorization requests, data storage, calculation and compliance services. The invention further discloses a license authorization management method based on the block chain. According to the method, decentralized authorization, verification, management and tracing of the license can be realized, meanwhile, the complexity of block chain limitation is reduced to the greatest extent, and the security, transparency and efficiency are improved.

Description

Technical Field

[0001] The present invention belongs to the field of communication technologies, and particularly relates to a license authorization management device and method based on a blockchain. Background Art

[0002] With the rapid development of global informatization and the popularization of digital content, the authorization management of intellectual property rights (such as metaverse works, etc.) has become an important link among various creators, enterprises, and users. Most traditional license authorization management models are based on centralized licensing systems, including the following three licensing systems: 1. Traditional license management system: Usually relies on a single authentication center to issue, track, and manage licenses, mainly manages authorizations through a registry and an authentication server. The authorization information between users and suppliers is often centrally stored on the server, and intermediary agencies are required to handle operations such as distribution, modification, and update; 2. Cloud-based license management system: The rise of cloud computing has promoted the development of cloud-based license management platforms. These platforms provide authorization services across devices and platforms through a unified management interface, and perform verification and authorization management through cloud services; 3. System based on digital rights management (DRM): DRM (Digital Rights Management) technology controls the replication and distribution of digital products through encryption, authentication, and licensing agreements. Although such technology has a certain effect in protecting copyrights, most systems still rely on centralized management agencies for authorization verification.

[0003] Although the above-mentioned existing technologies have solved the problem of license management to a certain extent, they generally face the following problems: 1. Single point of failure: Usually, a single organization or authority owns the license database, manages the distribution, and enforces the terms and conditions of the license agreement; Since all data and transactions are stored in a centralized server or database, the system is vulnerable to attacks, server failures, and unauthorized access; Violations or failures may lead to the loss of licenses or unauthorized distribution; 2. Low efficiency and high cost: Centralized systems usually involve cumbersome administrative processes and require intermediaries to verify and enforce licenses, resulting in increased operating costs, delayed transaction processing, and low efficiency; 3. Lack of transparency and trust: Users and third-party organizations usually have limited visibility into the licensing process; Trust in the central authority is crucial, but any mismanagement or lack of transparency can erode confidence in the system; In addition, it is very difficult to independently audit or verify the license distribution and usage history; 4. Geographical and regulatory barriers: Centralized systems may be subject to local laws and regulations, and managing cross-border license agreements can be complex and time-consuming; Data privacy laws, regional restrictions, and the lack of common standards often cause friction in global license management; 5. Limited cooperation: Centralized license management usually limits cooperation between multiple entities or stakeholders; Licenses issued by one organization are usually not easily transferable or shared with other organizations, and cooperation between different systems requires complex agreements and infrastructure.

[0004] Blockchain is a technical solution for collectively maintaining a reliable database in a decentralized and trustless manner, that is, a way for all people to participate in bookkeeping. It is a distributed ledger technology that is anti-tampering, shared, and traceable, with the advantages of decentralization, openness and transparency, immutability, consensus among all, smart contractization, authenticity, auditability, and traceability. Blockchain can provide an authorized record for the whole process traceability of digital assets, ensure the fairness and security of the authorization process, and does not rely on a single intermediary or management agency, and is widely used in the fields of finance, securities, insurance, commerce, logistics, etc. Summary of the Invention

[0005] In order to solve the problems existing in the license authorization management solution in the prior art in terms of reliability, security, efficiency, and transparency, the purpose of the present invention is to provide a blockchain-based license authorization management device and method, which can achieve decentralized authorization, verification, management, and traceability of licenses, while minimizing the complexity of blockchain limitations, and improving security, transparency, and efficiency.

[0006] To achieve the above-mentioned invention purpose, the present invention adopts the following technical solutions: A blockchain-based license authorization management device, which includes: The on-chain smart contract service layer is deployed on the blockchain platform and is used to contractually manage the issuance, transfer, revocation, renewal, and authorization verification of licenses. The on-chain and off-chain interaction protocol layer is used to perform data and business logic interactions between the on-chain smart contract service layer and the off-chain computing and storage layer using an interaction protocol. The format of the interaction protocol adopts the TLV format, including the operation type, data length, and operation data. The operation type includes license authorization verification, issuance, transfer, renewal, and revocation. The data length is the length of the entire protocol message. The operation data is the license information carried by the message. The checksum field is the integrity check value of the message. The off-chain computing and storage layer is used to process license authorization requests, data storage, computing, and compliance operations.

[0007] Furthermore, the above on-chain smart contract service layer is used to perform the following operations: (1) License issuance: The off-chain system processes the application, verification, and payment. After approval, the blockchain triggers the smart contract to issue a unique license token, which is recorded on the blockchain. (2) License authorization verification: The blockchain ensures the authenticity and status of the license by referencing the unique license token. (3) License transfer: The blockchain smart contract manages the transfer of licenses between entities. (4) License renewal: The off-chain system manages the renewal request, payment processing, and eligibility check. (5) License revocation and expiration: The smart contract automatically manages license expiration or revocation. (6) Access control and permissions: Use on-chain and off-chain components to perform access control.

[0008] Furthermore, for the above on-chain and off-chain interaction protocol layer, the information of each interaction field is as follows: (1) Operation type The operation type is a total of 4 bits and determines the processing action of the on-chain smart contract service layer or the off-chain computing and storage layer after receiving the license authorization management interaction protocol message. The definition of the operation type field is as follows: 0000: Indicates that the operation is successful; 1111: Indicates that the operation fails; 0001: Indicates license authorization verification; 0010: Indicates license issuance; 0011: Indicates license transfer; 0100: Indicates license renewal; 0101: Indicates license revocation (2), Data length The data length is a total of 12 bits, representing the length of the protocol message, with the unit being bytes; the length of the protocol message includes 4 bits for the operation type and 2 bytes occupied by the 12 bits of the data length; (3), Operation data The operation data is the data information carried when the on-chain smart contract service layer unloads computing power and storage to the off-chain computing and storage layer when processing license authorization verification, issuance, transfer, renewal, and revocation services; (4), Checksum The checksum is used to ensure the integrity of the protocol message. The checksum adopts CRC check technology and is calculated through the Hash algorithm. The length of the checksum field is 4 bytes, 8 bytes, or 16 bytes.

[0009] Further, the above off-chain computing and storage layer includes: The centralized database is used to store user data, metadata, and operation data; The authorization database: adopts a relational database or distributed storage and is used to store user authorization information, license terms, and usage history data; The API layer is used to provide interfaces for the front-end client to interact with external systems and process user requests, authorization verification, and system update information; The identity authentication and permission management module: adopts a centralized identity authentication system and is used to ensure user identity verification and permission control; The compliance service module: is used for compliance checking and compliance report generation.

[0010] A blockchain-based license authorization management method includes the following steps: S1, The on-chain smart contract service layer receives a user's license authorization verification, issuance, transfer, revocation, or renewal request and calls the corresponding processing contract of the license; S2, The corresponding processing contract of the license determines whether it is necessary to unload the computing power and storage services to the off-chain computing and storage layer according to the pre-setting of the service provider; S3, If it is necessary to unload for off-chain verification, it is transferred to the off-chain computing and storage layer through the on-chain and off-chain interaction protocol layer for license authorization verification, issuance, transfer, revocation, or renewal processing; S4, If it is not necessary to unload for off-chain processing, it is directly processed on the chain; S5, Return the verification result to the user.

[0011] Due to the above - described technical solution, the present invention has the following advantages: The license authorization management device and method based on blockchain of the present invention utilize the transparency, security, decentralization and trust characteristics of blockchain, as well as the efficiency and data processing capabilities of traditional centralized systems, seamlessly transitioning from a centralized structure to a blockchain - based model, ensuring scalability, transparency, enhanced security and efficiency, while minimizing blockchain storage and computing overheads to guarantee the high efficiency and scalability of the system; service providers can set whether to offload the license authorization management service to off - chain according to the computing power and storage capacity of the blockchain system, thereby achieving a reduction in operating costs; the on - chain and off - chain interaction protocol is used to realize the collaboration of license authorization management on - chain and off - chain, effectively solving the limitations of blockchain storage costs and computing power. BRIEF DESCRIPTION OF THE DRAWINGS

[0012] Figure 1 is a block diagram of the license authorization management device based on blockchain of the present invention; Figure 2 is a flowchart of one embodiment of the license authorization management method based on blockchain of the present invention; Figure 3 is a flowchart of a second embodiment of the license authorization management method based on blockchain of the present invention; Figure 4 is a flowchart of a third embodiment of the license authorization management method based on blockchain of the present invention; Figure 5 is a flowchart of a fourth embodiment of the license authorization management method based on blockchain of the present invention; Figure 6 is a flowchart of a fifth embodiment of the license authorization management method based on blockchain of the present invention. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0013] The technical solution of the present invention will be further described in detail below with reference to the drawings and embodiments.

[0014] As Figure 1 shown, a license authorization management device based on blockchain includes: The on-chain smart contract service layer is deployed on the blockchain platform and is used to automatically execute authorization management operations, contract the license issuance, transfer, revocation, renewal, and authorization verification business, realize the on-chain decentralized management of the license, and ensure the transparency and immutability of the authorization process; the blockchain platform is based on a public chain or a consortium chain to record and manage authorization data, and the blockchain is used to store immutable authorization information and record key operations such as authorization changes, transfers, and activations; the on-chain smart contract service layer performs the following operations: (1) License Issuance: The off-chain system processes application processing, verification, and payment. After approval, the blockchain triggers the smart contract to issue a unique license token, which is recorded on the blockchain; (2) License Authorization Verification: The blockchain ensures the authenticity and status of the license by referencing the unique License token, and users or third parties can conveniently verify the validity of the license through the blockchain; (3) License Transfer: The blockchain smart contract manages the transfer of licenses between entities, ensuring that ownership changes are securely and transparently tracked and verified; (4) License Renewal: The off-chain system manages renewal requests, payment processing, and eligibility checks; when the conditions are met, the blockchain smart contract updates the license status to reflect the renewal situation; (5) License Revocation and Expiration: The smart contract automatically manages license expiration or revocation to ensure compliance with predefined rules; the revoked license is recorded on the blockchain, providing an auditable history; (6) Access Control and Permissions: Use on-chain and off-chain components to perform access control; the blockchain manages the validity of the license; The on-chain and off-chain interaction protocol layer is used to utilize the interaction protocol to perform data and business logic interactions between the on-chain smart contract service layer and the off-chain computing and storage layer, improve the efficiency of license authorization management, and ensure that during the transition process, both the high efficiency of traditional systems can be utilized and the decentralized characteristics of the blockchain can be gradually introduced, minimizing the storage and computing overhead of the blockchain; the protocol format is the TLV format (T represents Type, L represents Length, and V represents Value), including the operation type, data length, and operation data. The operation type includes license authorization verification, issuance, transfer, renewal, and revocation; the data length is the length of the entire protocol message; the operation data is the license information carried by the message; the checksum field is the integrity check value of the message; through protocol field control, the license authorization management computing power and storage are unloaded from the on-chain to the off-chain; The information of each field of the interaction protocol is as follows: (1) Operation Type The operation type is 4 bits in total, which determines the processing actions of the on-chain smart contract service layer or the off-chain computing and storage layer after receiving the license authorization management interaction protocol message. The specific definition of the operation type field is as follows: 0000: Indicates successful operation; 1111: Indicates operation failure; 0001: Indicates license authorization verification; 0010: Indicates license issuance; 0011: Indicates license transfer; 0100: Indicates license renewal; 0101: Indicates license revocation; (2) Data Length The data length is 12 bits in total, indicating the length of the protocol message, with the unit being bytes. The length of the protocol message includes the 2 bytes occupied by the 4 bits of the operation type and the 12 bits of the data length. (3) Operation Data The operation data is the data information carried when the on-chain smart contract service layer unloads computing power and storage to the off-chain computing and storage layer during the processing of license authorization verification, issuance, transfer, renewal, and revocation services. The operation data is license certificate information or user identity information. (4) Checksum The checksum is used to ensure the integrity of the protocol message and prevent the protocol from being tampered with during transmission. The checksum adopts CRC check (Cyclic Redundancy Check) technology and is calculated through the Hash algorithm. The length of the checksum field is 4 bytes, 8 bytes, or 16 bytes. The off-chain computing and storage layer is used to process license authorization requests, data storage, computing, and compliance services, which can improve the efficiency of license authorization management and make up for the low efficiency of the blockchain in computing and compliance service processing. The off-chain computing and storage layer includes: The centralized database is used to store user data, metadata, and operation data; The authorization database: adopts a relational database or distributed storage, and is used to store user authorization information, license terms, and usage history data, providing efficient query and update operations; The API layer is used to provide interfaces for front-end clients to interact with external systems, and processes user requests, authorization verification, and system update information; The identity authentication and permission management module: adopts a centralized identity authentication system and is used to ensure user identity verification and permission control; The compliance service module: used for compliance checking and compliance report generation to ensure that off-chain services comply with regulations and jurisdiction verification; The specific functions are as follows: (1) Audit and compliance reports: The blockchain ensures transparent record-keeping, making it compliant with regulatory requirements and providing an immutable audit trail for all licensed operations; (2) Data storage and analysis: The off-chain system stores large datasets (e.g., user profiles, license usage statistics) and performs complex data analysis to achieve effective reporting and trend analysis while reducing the blockchain load; (3) Notifications and alerts: The system automatically sends license expiration notifications, renewal reminders, and compliance alerts; (4) Access control and permissions: The system uses on-chain and off-chain components to enforce access control, and the off-chain computing and storage layer system authenticates users and manages permission levels.

[0015] As Figure 2 shown, a blockchain-based license authorization management method that performs license authorization verification includes the following steps: S1. The on-chain intelligent contract service layer receives the user's license verification request and calls the license authorization verification contract; S2. The license authorization verification contract determines whether it is necessary to offload the computing power and storage services to the off-chain computing and storage layer according to the pre-setting of the service provider; S3. If it is necessary to offload for off-chain verification, it is transferred to the off-chain computing and storage layer through the on-chain and off-chain interaction protocol layer for license validity verification; The specific operation is as follows: S3.1. First, the license authorization verification contract fills the operation type field with 0001 and fills the operation data with license information, including the license authorization date and license authorization code information; then calculates the message length and the checksum of the protocol message; finally, encapsulates the protocol message; S3.2. The protocol message is sent to the off-chain computing and storage layer through an oracle or cross-chain technology. The off-chain computing and storage layer receives the protocol message, calculates the checksum to ensure the integrity of the protocol message; then parses the protocol message, obtains the operation data information, and performs validity verification according to the license information provided by the user; The off-chain computing and storage layer returns the verification result to the on-chain license authorization verification contract through the protocol message; if the verification passes, the operation type field is filled with 0000, indicating that the verification passes; if the verification fails, the operation type field is filled with 1111, indicating that the verification fails; the data length and operation data remain unchanged, and the checksum needs to be recalculated each time for encapsulation; S4. If there is no need to unload for off-chain verification, directly conduct verification on-chain; S5. Return the verification result to the user.

[0016] As Figure 3 shown, a license authorization management method based on blockchain for issuing License includes the following steps: S1. The on-chain smart contract service layer receives the user's license issuance request and calls the license issuance contract; S2. The license issuance contract determines whether it is necessary to unload the computing power and storage services to the off-chain computing and storage layer according to the pre-setting of the service provider; S3. If it is necessary to unload for off-chain verification, transfer it to the off-chain computing and storage layer through the on-chain and off-chain interaction protocol layer for license issuance application verification; The specific operation is as follows: S3.1. First, the license issuance contract fills the operation type field with 0010 and fills the operation data with the user's application information, including the user identity information and the payment voucher information; then calculates the message length and the checksum of the protocol message; finally, encapsulates the protocol message; S3.2. Send the protocol message to the off-chain computing and storage layer through an oracle or cross-chain technology. The off-chain computing and storage layer receives the protocol message, calculates the checksum to ensure the integrity of the protocol message, then parses the protocol message, obtains the operation data information, and conducts the issuance application verification according to the application information provided by the user; The off-chain computing and storage layer returns the verification result to the on-chain license issuance contract through the protocol message; If the verification fails, fill the operation type field with 1111 to indicate verification failure; The data length and operation data remain unchanged, and the checksum is recalculated; If the verification passes, fill the operation type field with 0000 to indicate verification passed, fill the operation data with the issued license information, and recalculate the message length and checksum; S4. If there is no need to unload for off-chain verification, directly conduct verification on-chain; S5. If the verification passes, generate a license and issue the license to the user, otherwise return failure.

[0017] As Figure 4 shown, a license authorization management method based on blockchain for transferring License includes the following steps: S1. The on-chain smart contract service layer receives the user's license transfer request and calls the license transfer contract; S2. The license transfer contract determines whether it is necessary to offload the computing power and storage services to the off-chain computing and storage layer according to the pre-setting of the service provider; S3. If offloading to off-chain processing is required, it is transferred to the off-chain computing and storage layer through the on-chain and off-chain interaction protocol layer for license transfer processing; The specific operation is as follows: S3.1. First, the license transfer contract fills the operation type field with 0011 and fills the operation data with user information and license information, including user identity information, license authorization code, and license authorization date information; Then calculate the message length and the checksum of the protocol message; Finally, encapsulate the protocol message; S3.2. The protocol message is sent to the off-chain computing and storage layer through an oracle or cross-chain technology. The off-chain computing and storage layer receives the protocol message, calculates the checksum to ensure the integrity of the protocol message, then parses the protocol message to obtain the operation data information, performs transfer and change processing according to the user information and license information, and updates the license information; The off-chain computing and storage layer then returns the processing result to the on-chain license transfer contract through a protocol message; If the transfer and change processing fails, the operation type field is filled with 1111, indicating processing failure; The data length and operation data remain unchanged, and the checksum is recalculated; If the transfer and change processing is successful, the operation type field is filled with 0000, indicating that the processing is passed, the operation data is filled with user information and the updated license information, and the message length and checksum are recalculated; S4. If offloading to off-chain verification is not required, the transfer and change processing is directly performed on the chain; S5. If the transfer and change processing is successful, notify the user that the license authorization transfer is successful, otherwise return that the license authorization transfer fails to the user.

[0018] As Figure 5 shown, a blockchain-based license authorization management method for renewing a License includes the following steps: S1. The on-chain smart contract service layer receives the user's license renewal request and calls the license renewal contract; S2. The license renewal contract determines whether it is necessary to offload the computing power and storage services to the off-chain computing and storage layer according to the pre-setting of the service provider; S3. If offloading to off-chain processing is required, it is transferred to the off-chain computing and storage layer through the on-chain and off-chain interaction protocol layer for license renewal processing; The specific operation is as follows: S3.1. First, the license renewal contract fills the operation type field with 0100, and fills the operation data with user information and license information, including user identity information, license authorization code, and license authorization date information. Then, calculate the message length and the checksum of the protocol message. Finally, encapsulate the protocol message. S3.2. Send the protocol message to the off-chain computing and storage layer through an oracle or cross-chain technology. The off-chain computing and storage layer receives the protocol message, calculates the checksum to ensure the integrity of the protocol message, then parses the protocol message to obtain the operation data information, performs renewal processing based on the user information and license information, and updates the license authorization code and license authorization date information. The off-chain computing and storage layer returns the processing result to the on-chain license renewal contract through a protocol message. If the renewal processing fails, fill the operation type field with 1111 to indicate failure; the data length and operation data remain unchanged, and recalculate the checksum. If the renewal processing is successful, fill the operation type field with 0000 to indicate passing, fill the operation data with user information and the updated license information, and recalculate the message length and checksum. S4. If it is not necessary to unload for off-chain verification, directly perform the renewal processing on the chain. S5. If the renewal processing passes, extend the license authorization and refresh the license authorization code; otherwise, return renewal failure.

[0019] As Figure 6 shown, a blockchain-based license authorization management method for revoking a License includes the following steps: S1. The on-chain smart contract service layer regularly checks the validity period of the License revocation contract for the License and notifies the user in advance at a set time before expiration. S2. The License revocation contract determines whether it is necessary to unload the computing and storage services to the off-chain computing and storage layer according to the pre-setting of the service provider. S3. If it is necessary to unload for off-chain processing, transfer it to the off-chain computing and storage layer through the on-chain and off-chain interaction protocol layer for license revocation verification processing. The specific operation is as follows: S3.1. First, the license revocation contract fills the operation type field with 0101 and fills the operation data with license information, including license authorization code and license authorization date information. Then, calculate the message length and the checksum of the protocol message. Finally, encapsulate the protocol message. S3.2. Send the protocol message to the off-chain computing and storage layer through an oracle or cross-chain technology. After receiving the protocol message, the off-chain computing and storage layer calculates the checksum to ensure the integrity of the protocol message, then parses the protocol message to obtain the operation data information, and determines whether the license authorization date has expired; the off-chain computing and storage layer returns the judgment result to the on-chain license revocation contract through the protocol message; fill the operation type field with 0000, fill the operation data with the license information and the expiration judgment information, and recalculate the message length and checksum; S4. If it is not necessary to unload for off-chain processing, directly perform the check on the chain; S5. Within the specified time, if the user does not renew the fee, revoke the license issued to the user, otherwise repeat steps S1 to S3.

[0020] The license authorization management device and method based on blockchain of the present invention effectively realize the efficiency, transparency, security and traceability of license authorization management.

[0021] The above are only the preferred embodiments of the present invention, and are not intended to limit the present invention. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principle of the present invention shall be included in the protection scope of the present invention.

Claims

1. A license authorization management device based on blockchain, characterized in that: include: The on-chain smart contract service layer is deployed on the blockchain platform to contract the issuance, transfer, revocation, renewal and authorization verification of licenses; The on-chain and off-chain interaction protocol layer is used to use the interaction protocol to perform data and business logic interaction between the on-chain smart contract service layer and the off-chain computing and storage layer; the format of the interaction protocol adopts the TLV format, including the operation type, data length and operation data, and the operation type includes the authorization verification, issuance, transfer, renewal and revocation of the license; The data length is the length of the entire protocol message; the operation data is the license information carried by the message; the checksum field is the integrity check value of the message; The off-chain computing and storage layer is used to process license authorization requests, data storage, computing, and compliance services.

2. The blockchain-based license authorization management device according to claim 1 is characterized in that: The on-chain smart contract service layer is used to perform the following operations: (1) License issuance: The off-chain system handles application processing, verification, and payment. After approval, the blockchain triggers the smart contract to issue a unique license token, which is recorded on the blockchain; (2) License authorization verification: The blockchain ensures the authenticity and status of the license by referencing a unique license token; (3) License transfer: Blockchain smart contracts manage license transfers between entities; (4) License renewal: The off-chain system manages renewal requests, payment processing, and eligibility checks; (5) License revocation and expiration: Smart contracts automatically manage license expiration or revocation; (6) Access control and permissions: Use on-chain and off-chain components to enforce access control.

3. The blockchain-based license authorization management device according to claim 1 is characterized in that: The on-chain and off-chain interaction protocol layer, the information of each field of the interaction is as follows: (1) Operation type The operation type is 4 bits in total, which determines the processing action of the on-chain smart contract service layer or the off-chain computing and storage layer after receiving the license authorization management interaction protocol message; the operation type field is defined as follows: 0000: indicates successful operation; 1111: indicates operation failure; 0001: indicates license authorization verification; 0010: indicates license issuance; 0011: indicates license transfer; 0100: indicates license renewal; 0101: indicates license revocation (2) Data length The data length is 12 bits in total, indicating the length of the protocol message in bytes. The length of the protocol message includes 4 bits of the operation type and 2 bytes occupied by the 12 bits of the data length. (3) Operational data Operational data refers to the data information carried by the on-chain smart contract service layer when it offloads computing power and storage to the off-chain computing and storage layer when processing the authorization verification, issuance, transfer, renewal and revocation of licenses; (4) Checksum The checksum is used to ensure the integrity of the protocol message. The checksum uses the CRC checksum technology and is calculated through the Hash algorithm. The checksum field length is 4 bytes, 8 bytes, or 16 bytes.

4. The blockchain-based license authorization management device according to claim 1 is characterized in that: The off-chain computing and storage layer includes: The centralized database is used to store user data, metadata and operation data; The authorization database: adopts a relational database or distributed storage to store user authorization information, license terms, and usage history data; The API layer is used to provide an interface for front-end clients to interact with external systems and process user requests, authorization verification, and system update information; The identity authentication and authority management module: adopts a centralized identity authentication system to ensure user identity verification and authority control; The compliance service module is used for compliance checking and compliance report generation.

5. A blockchain-based license authorization management method, implemented by using the blockchain-based license authorization management device described in any one of claims 1 to 4, characterized in that: It includes the following steps: S1. The on-chain smart contract service layer receives the user's license authorization verification, issuance, transfer, revocation or renewal request and calls the corresponding processing contract of the license; S2. The corresponding processing contract of the license determines whether it is necessary to offload the computing power and storage business to the off-chain computing and storage layer according to the pre-set settings of the service provider; S3. If it is necessary to offload to off-chain verification, it is transferred to the off-chain computing and storage layer through the on-chain off-chain interaction protocol layer to perform authorization verification, issuance, transfer, revocation or renewal of the license; S4. If it is not necessary to offload to off-chain processing, process it directly on the chain; S5. Return the verification result to the user.

Images