Block chain access management engine and management method
Through the multi -review and contract translation module of the management engine into the management engine, the problem of lack of audit and cross -chain scenarios in the existing technology in the existing technologies, and realized higher information security and cross -chain applications Flexibility.
Patent Information
- Application Number
- CN202411309163.8
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-09-19
- Publication Date
- 2025-01-21
AI Technical Summary
The existing blockchain business linking method lacks a comprehensive review process, and cannot confirm the integrity, legality and compliance of business chain information. The cross-chain scenarios lack support for different digital asset smart contracts, and there are privacy and security issues. .
Provides a blockchain access management engine, including application layer and service layer. The application layer includes contract translation module, channel building module and message distribution module. The service layer provides communication protocol, service registration center, service monitoring, distributed database and distribution storage module. The engine confirms the integrity and compliance of business chain information through multiple audits, supports transaction transfers between different smart contracts through the contract translation module, and establishes encrypted information channels to improve the security of data transactions.
Multi -review ensure the integrity and compliance of business chain information, support transaction transfer between different smart contracts, improve the diversity and flexibility of cross -chain application scenarios, and improve the security of data transactions through encrypted information channels.
Smart Images

Figure CN119337397A_ABST
Abstract
Description
Technical Field
[0001] This invention belongs to the field of computer technology, specifically relating to a blockchain access management engine and management method. Background Technology
[0002] Blockchain is a decentralized distributed ledger that is block-based, immutable, secure, and reliable. It combines technologies such as distributed storage, peer-to-peer transmission, consensus mechanisms, and cryptography to record transactions and information through a continuously growing chain of data blocks, ensuring data security and transparency.
[0003] As blockchain technology matures, the ability to facilitate the transfer of digital assets between different blockchains has become a significant constraint on its development. Faced with diverse transaction needs across various blockchain-based businesses, effectively managing the access and transfer of data from different blockchain platforms has become a pressing issue.
[0004] Currently, most cross-chain operations between business blockchains rely on notary mechanisms, sidechains, relay chains, and hash locking. This process primarily enables the transfer of underlying chain data, but it suffers from the following problems: 1. The existing business link entry method lacks a comprehensive review process, which cannot fully confirm the completeness, legality and compliance of business chain information.
[0005] 2. Existing cross-chain scenarios cannot effectively support smart contracts for different types of digital assets. The lack of matching of business attributes for contracts with different fields of the same type and adaptation to heterogeneous smart contract frameworks limits the diversity and flexibility of cross-chain application scenarios.
[0006] 3. The two parties failed to establish an independent information channel for data transactions, which raises certain privacy and security concerns. Summary of the Invention
[0007] To address the problems mentioned in the background, this invention provides a blockchain access management engine and management method to solve the problems of existing business link access methods lacking a comprehensive review process, cross-chain scenarios not effectively supporting smart contracts for different digital asset classes, and the lack of an independent information channel for data transactions between the two parties, which poses certain privacy risks.
[0008] To achieve the above objectives, the present invention provides the following technical solution: A blockchain access management engine, comprising: Application layer; The application layer includes a contract translation module, a channel construction module, and a message distribution module. The contract translation module is used to translate smart contracts using a preset translation table. The channel construction module is used to build a communication channel between two business chains. The message distribution module is used to broadcast information to the business chains. Service layer: The service layer provides functional services to the application layer. The service layer includes a communication protocol module, a service registration center module, a service monitoring module, a distributed database, and a distributed storage module.
[0009] Preferably, the contract translation module consists of the meta-attributes and meta-methods of the digital asset. The meta-attributes include the digital asset name, digital asset ID, digital asset owner's address, and digital asset status. Metamethods include add, update, and delete operations.
[0010] Preferably, the communication protocol module uses the message broker software RabbitMQ, the service registry module uses the service discovery framework Eureka, and the service monitoring module consists of the Mertics tool and the distributed tracing system ZipKin.
[0011] A blockchain access management method includes the following steps: S1: Create and verify a cross-chain identity; use the blockchain access management engine to register the cross-chain identity of business chain A and verify the chain type and business. If the verification fails, return to the cross-chain identity registration step. If the verification is successful, the blockchain access management engine will send the address and public key of business chain A to business chain A. S2: Initiate a blockchain cross-chain transaction; Business chain A initiates a blockchain cross-chain transaction. The blockchain access management engine verifies and confirms the transaction application between business chain A and the target business chain. If the verification and confirmation are successful, proceed to the next step; otherwise, the execution of this blockchain cross-chain transaction is rejected. S3: Execute cross-chain blockchain business; if business chain A and the target business chain are of the same type of smart contract and have the same feature value, the blockchain access management engine calls the smart contract of the target business chain to directly complete the transaction application. If business chain A and the target business chain are not of the same type of smart contract or the feature values of the smart contracts of business chain A and the target business chain are inconsistent, the smart contract is translated by the contract translation module, and business chain A and the target business chain complete the transaction application through the translated smart contract. S4: Execute the audit process; The blockchain access management engine compiles statistics on the communication records, cross-chain data records, and node data between business chain A and the target business chain, audits the operation of cross-chain business, and completes the cross-chain business.
[0012] Preferably, S1 is as follows: S1.1: Business chain A sends an access application to the blockchain access management engine; S1.2: Use the blockchain access management engine to register the cross-chain identity of business chain A and verify whether the chain type of business chain A is consistent with the information in its access application. If they are inconsistent, return to the identity registration step; if they are consistent, broadcast the registered cross-chain identity. S1.3: After receiving the broadcast, the other business links in the blockchain confirm whether the real-name address of the registered cross-chain identity matches the target business. If it is confirmed that it does not match, the identity registration step is returned. If it is confirmed that it matches, the address and public key of business chain A are generated. The blockchain access management engine sends the address and public key of business chain A back to business chain A after encryption, thus completing the cross-chain identity registration.
[0013] Preferably, S2 is as follows: When business chain A initiates a cross-chain business, business chain A sends a cross-chain business transaction request to the target business chain to the blockchain access management engine. The blockchain access management engine verifies the identity of the address of the cross-chain business and obtains the business attributes of the target business chain. The blockchain access management engine verifies the validity of the transaction request and confirms that business chain A has data corresponding to the business attributes of the target business chain. If identity verification is successful, the transaction request is valid, and business chain A has data corresponding to the business attributes of the target business chain, then proceed to S3; otherwise, the execution of this blockchain cross-chain transaction will be rejected.
[0014] Preferably, the business attributes include the network identifier of the target business chain, the receiving address, and the verification data.
[0015] Preferably, S3 is as follows: S3.1: Prepare to execute the smart contracts of business chain A and the target business chain; S3.2: If business chain A and the target business chain are of the same type of smart contract and have the same characteristic value, the blockchain access management engine will call the smart contract of the target business chain to directly complete the transaction application, and then execute the asset destruction operation on the smart contract of business chain A, broadcast the execution result and update the corresponding account status. If business chain A and the target business chain are not of the same type of smart contract, or if the feature values of the smart contracts of business chain A and the target business chain are inconsistent, a translation request is sent to the blockchain access management engine. After the translation request is successfully matched, the blockchain access management engine calls the contract translation module to translate the smart contract. Digital asset operations are performed through the translated smart contract. After the transaction is completed, the asset destruction operation is performed on the smart contract of business chain A, and the execution result is broadcast and the corresponding account status is updated.
[0016] The preferred translation steps are as follows: S3.11: The blockchain access management engine calls the contract translation module; S3.12: The contract translation module performs entity parsing on the smart contracts of business chain A and the target business chain, extracts the asset name, serial number, owner, and status attributes of the smart contracts, and completes the correspondence through the meta-attributes of the contract translation module; S3.13: Extract the methods mint and burn of business chain A, extract the methods creat and delete of the target business chain, and complete the corresponding tasks through the meta-methods of the contract translation module; S3.14: After a translation request is successfully matched, the blockchain access management engine establishes a communication channel between business chain A and the target business chain. The channel communicates based on the negotiated key between the two parties, executes the smart contract of business chain A, and initiates a call to the smart contract of the target business chain based on the correspondence between meta-attributes and meta-methods recorded in the contract translation module.
[0017] Preferably, in S4, the business chain communication record includes inter-chain transaction records, inter-chain communication protocol, and inter-chain transaction confirmation time; Cross-chain data records include cross-chain transaction type, cross-chain data synchronization, and cross-chain data time. The node data involved includes node type, number of nodes, and node distribution; Operational audits include audits of transaction volume, transaction speed statistics, and transaction fee statistics.
[0018] Compared with the prior art, the beneficial effects of the present invention are: 1. This application uses a blockchain access management engine to conduct multiple audits of the business chain, confirming the integrity, legality, and compliance of the business chain information, and preventing information tampering and forgery.
[0019] 2. This application relies on the call and translation of the contract translation module to solve the problem of transaction transfer between different types and methods of digital asset smart contracts, promote cooperation and connection between blockchain networks, and realize a more open and inclusive blockchain ecosystem.
[0020] 3. This application enables multiple parties to establish encrypted information channels through a blockchain access management engine when communication is needed, thereby improving the security and reliability of business processes. Attached Figure Description
[0021] Figure 1 This is a schematic diagram of the blockchain access management engine. Figure 2 A flowchart illustrating the process of creating and verifying a cross-chain identity; Figure 3 A flowchart illustrating the process of initiating cross-chain blockchain business; Figure 4 A flowchart illustrating the process of executing cross-chain blockchain transactions; Figure 5 A flowchart illustrating the audit process. Detailed Implementation
[0022] To facilitate understanding of the technical content of this invention by those skilled in the art, the invention will be further described in detail below with reference to the accompanying drawings and specific examples. It should be understood that the specific examples described herein are merely illustrative and not intended to limit the scope of the invention.
[0023] like Figure 1 As shown, a blockchain access management engine includes: Application Layer; The application layer includes a contract translation module, a channel construction module, a message distribution module, an identity service module, a pre-access service module, and a smart contract integration management service module. The contract translation module is used to translate smart contracts using a preset translation table. The channel construction module is used to build a communication channel between two business chains. The message distribution module is used to broadcast information to the business chains. The identity service module is used to manage and verify user identities. The contract translation module consists of the meta-attributes and meta-methods of digital assets. The meta-attributes include the digital asset name, digital asset ID, digital asset owner's address, and digital asset status. Metamethods include add, update, and delete operations.
[0024] Service Layer: The service layer provides functional services to the application layer. It includes a communication protocol module, a service registry module, a service monitoring module, a MySQL distributed database, and a Redis distributed storage module. The communication protocol module uses the message broker software RabbitMQ, the service registry module uses the service discovery framework Eureka, and the service monitoring module consists of the Mertics tool and the distributed tracing system ZipKin.
[0025] A blockchain access management method includes the following steps: S1: Create and verify a cross-chain identity; Using decentralized identities via business chains enables the establishment of portable identities across different blockchain networks. Each business chain possesses unique identity information, including chain ID, public / private keys, smart contract type, smart contract characteristics, access control, verification records, and transaction records. Furthermore, this identity information can be verified across different blockchain networks, thus achieving cross-chain identity verification. like Figure 2 As shown, the blockchain access management engine is used to register the cross-chain identity of business chain A and to verify the chain type and business. If the verification fails, the cross-chain identity registration step is returned. If the verification is successful, the blockchain access management engine sends the address and public key of business chain A to business chain A. The specific steps for S1 are as follows: S1.1: Business chain A sends an access application to the blockchain access management engine; S1.2: Use the blockchain access management engine to register the cross-chain identity of business chain A and verify whether the chain type of business chain A is consistent with the information in its access application. If they are inconsistent, return to the identity registration step; if they are consistent, broadcast the registered cross-chain identity. S1.3: After receiving the broadcast, the other business links in the blockchain confirm whether the real-name address of the registered cross-chain identity matches the target business. If it is confirmed that it does not match, the identity registration step is returned. If it is confirmed that it matches, the address and public key of business chain A are generated. The blockchain access management engine sends the address and public key of business chain A back to business chain A after encryption, thus completing the cross-chain identity registration.
[0026] S2: Initiate cross-chain blockchain business; such as... Figure 3 As shown, business chain A initiates a blockchain cross-chain business. The blockchain access management engine verifies and confirms the transaction application between business chain A and the target business chain. If the verification and confirmation are successful, the process proceeds to the next step; otherwise, the execution of this blockchain cross-chain business is rejected. The specific steps for S2 are as follows: When business chain A initiates a cross-chain business transaction, it sends a cross-chain business transaction request to the blockchain access management engine. The blockchain access management engine verifies the identity of the cross-chain business address and obtains the business attributes of the target business chain. The blockchain access management engine verifies the validity of the transaction request and confirms that business chain A has data corresponding to the business attributes of the target business chain. The business attributes include the network identifier of the target business chain, the receiving address, and the verification data. At the same time, the transaction also includes relevant information about the cross-chain transaction for subsequent blockchain management to display transaction records. If identity verification is successful, the transaction request is valid, and business chain A has data corresponding to the business attributes of the target business chain, then proceed to S3; otherwise, the execution of this blockchain cross-chain transaction will be rejected.
[0027] S3: Execute cross-chain blockchain transactions; such as... Figure 4 As shown, if business chain A and the target business chain have the same type of smart contract and the same feature value, the blockchain access management engine will call the smart contract of the target business chain to directly complete the transaction application. In this case, the efficiency of cross-chain communication is high because no additional conversion, translation or matching is required. If business chain A and the target business chain do not belong to the same type of smart contract or the feature values of the smart contracts of business chain A and the target business chain are inconsistent, the smart contract will be translated by the contract translation module, and business chain A and the target business chain will complete the transaction application through the translated smart contract. S3 specifically refers to: S3.1: Prepare to execute the smart contracts of business chain A and the target business chain; S3.2: If business chain A and the target business chain are of the same type of smart contract and have the same characteristic value, the blockchain access management engine will call the smart contract of the target business chain to directly complete the transaction application, and then execute the asset destruction operation on the smart contract of business chain A, broadcast the execution result and update the corresponding account status. If business chain A and the target business chain are not of the same type of smart contract, or if the feature values of the smart contracts of business chain A and the target business chain are inconsistent, a translation request is sent to the blockchain access management engine. After the translation request is successfully matched, the blockchain access management engine calls the contract translation module to translate the smart contract. Digital asset operations are performed through the translated smart contract. After the transaction is completed, the asset destruction operation is performed on the smart contract of business chain A, and the execution result is broadcast and the corresponding account status is updated.
[0028] If business chain A is built using an Ethereum ERC721 smart contract, its main asset-related fields include NFT (Non-Fungible Asset), tokenID (Asset ID), and owner (Asset Address). The target business chain uses a custom Go contract, primarily containing asset-related fields such as evd (Evidence Asset Name), evdID (Evidence ID), and operator (Evidence Holder). The specific translation steps are as follows: S3.11: Business chain A initiates a digital asset translation request to the blockchain access management engine. The blockchain access management engine calls the translation module, which consists of digital asset meta-attributes and meta-methods. The meta-attributes include DAN (digital asset name), DANID (digital asset ID), owner (owner's address), and status. The meta-methods include add, update, and delete operations. S3.12: It first performs entity parsing on the smart contracts of business chain A and target business chain, extracts the asset name, serial number, owner, and status attributes of the original contract, and completes the correspondence through the meta-attributes of the translation module. For example, the NFT of business chain A is equivalent to the meta-attribute DAN, and is also equivalent to the evd of the target business chain.
[0029] S3.13: Extract the methods mint (forging) and burn (destroying) of business chain A, extract the methods creat (creating) and delete (deleting) of the target business chain, and complete the corresponding transformation through the meta-methods of the translation module. For example, mint of chain A is equivalent to the meta-method add, and is also equivalent to creat of chain B.
[0030] S3.14: S3.12 and S3.13 achieve this through the built-in standard contract pre-extraction function, supporting contracts such as ERC721 and ERC1155. Other contracts need to be configured by the administrator and recorded in the translation table when the business is linked into the management engine or when the contract is installed and deployed. If the contract is already in the translation table, the next step can be directly performed.
[0031] After a successful translation request match, the blockchain access management engine will re-establish a communication channel between business chain A and the target business chain. This channel communicates using a key negotiated between the two parties. At this point, the smart contract of business chain A will be executed, and the translation module will translate the attribute and method mappings recorded in the translation table, initiating a call to the smart contract module of the target business chain. The operation result will also be broadcast to the blockchain access management engine, updating the relevant account status.
[0032] This focuses on translating smart contracts for different digital asset types using different programming languages or fields. For example, ERC721 and 1155 can have their methods and attributes identified in advance. Other contracts can be identified and configured by the administrator when the business chain connects to the blockchain access management engine. This enables fast cross-chain transactions and transfers of digital assets across different chains.
[0033] S4: Perform the audit process; such as Figure 5 As shown, the blockchain access management engine performs statistics on the communication records, cross-chain data records, and node data between business chain A and the target business chain, audits the operation of cross-chain business, and completes the cross-chain business.
[0034] Business chain communication records include inter-chain transaction records, inter-chain communication protocols, and inter-chain transaction confirmation times; Cross-chain data records include cross-chain transaction type, cross-chain data synchronization, and cross-chain data time. The node data involved includes node type, number of nodes, and node distribution; Operational audits include audits of transaction volume, transaction speed statistics, and transaction fee statistics.
[0035] In this embodiment, the application uses a blockchain access management engine to conduct multiple audits of the business chain, confirming the integrity, legality, and compliance of the business chain information, and preventing information tampering and forgery. This application relies on the call and translation of the contract translation module to solve the problem of transaction transfer between different types and methods of digital asset smart contracts, promoting cooperation and connection between blockchain networks, and realizing a more open and inclusive blockchain ecosystem. This application enables multiple parties to establish encrypted information channels through the blockchain access management engine when communication is needed, improving the security and reliability of business flow.
Claims
1. A blockchain access management engine, characterized in that: include: Application layer; The application layer includes a contract translation module, a channel construction module, and a message distribution module. The contract translation module is used to translate the smart contract through a preset translation table, the channel construction module is used to build a communication channel between two business chains, and the message distribution module is used to broadcast information to the business chain; Service layer: The service layer provides functional services for the application layer. The service layer includes a communication protocol module, a service registration center module, a service monitoring module, a distributed database, and a distributed storage module.
2. A blockchain access management engine according to claim 1, characterized in that: The contract translation module consists of meta-attributes and meta-methods of digital assets. Meta-attributes include digital asset name, digital asset ID, digital asset owner address, and digital asset status. Metamethods include add operations, update operations, and delete operations.
3. A blockchain access management engine according to claim 1, characterized in that: The communication protocol module uses the message broker software RabbitMQ, the service registration center module uses the service discovery framework Eureka, and the service monitoring module consists of the Mertics tool and the distributed tracking system ZipKin.
4. A blockchain access management method, applied to a blockchain access management engine as described in claims 1-3, characterized in that: The following steps are involved: S1: Create a cross-chain identity and verify it; use the blockchain access management engine to register the cross-chain identity of business chain A and perform chain type verification and business verification. If the verification fails, return to the cross-chain identity registration step. If the verification succeeds, the blockchain access management engine sends the address and public key of business chain A to business chain A; S2: Initiate cross-chain blockchain business; Business chain A initiates cross-chain blockchain business, and the blockchain access management engine verifies and confirms the transaction application of business chain A and the target business chain. If the verification and confirmation succeeds, it will proceed to the next step. If it fails, the execution of this cross-chain blockchain business will be rejected; S3: Execute cross-chain blockchain business; if business chain A and the target business chain belong to the same type of smart contract and have the same characteristic values, the blockchain access management engine calls the smart contract of the target business chain to directly complete the transaction application; if business chain A and the target business chain do not belong to the same type of smart contract or the characteristic values of the smart contract of business chain A and the target business chain are inconsistent, the smart contract is translated by the contract translation module, and business chain A and the target business chain complete the transaction application through the translated smart contract; S4: Execute the audit process; The blockchain access management engine collects statistics on the communication records, cross-chain data records, and node data between business chain A and the target business chain, audits the operation of the cross-chain business, and completes the cross-chain business.
5. A blockchain access management method according to claim 4, characterized in that: S1 is specifically: S1.1: Business chain A sends an access application to the blockchain access management engine; S1.2: Use the blockchain access management engine to register the cross-chain identity of business chain A and verify whether the chain type of business chain A is consistent with the information in its own access application. If they are inconsistent, return to the identity registration step. If they are consistent, broadcast the registered cross-chain identity; S1.3: After receiving the broadcast, the other business links in the blockchain confirm whether the real-name address of the registered cross-chain identity complies with the target business. If it is confirmed that it does not comply, it returns to the identity registration step. After confirming that it complies, the address and public key of business chain A are generated. The blockchain access management engine encrypts the address and public key of business chain A and returns them to business chain A to complete the cross-chain identity registration.
6. A blockchain access management method according to claim 4, characterized in that: S2 is specifically: When business chain A initiates a cross-chain blockchain service, business chain A initiates a cross-chain service transaction request for the target business chain to the blockchain access management engine. The blockchain access management engine verifies the identity of the address of the cross-chain blockchain service and obtains the business attributes of the target business chain. The blockchain access management engine verifies the validity of the transaction request and confirms that business chain A has data corresponding to the business attributes of the target business chain. If the identity verification is successful, the transaction request is valid, and business chain A has data corresponding to the business attributes of the target business chain, then enter S3, otherwise the execution of this blockchain cross-chain business is rejected.
7. A blockchain access management method according to claim 4, characterized in that: The service attributes include the network identifier of the target service chain, the receiving address, and the verification data.
8. A blockchain access management method according to claim 4, characterized in that: S3 is specifically: S3.1: Prepare to execute the smart contracts of business chain A and target business chain; S3.2: If business chain A and the target business chain belong to the same type of smart contract and have the same characteristic values, the blockchain access management engine calls the smart contract of the target business chain to directly complete the transaction application, and then executes the asset destruction operation on the smart contract of business chain A, broadcasts the execution result and updates the corresponding account status; If business chain A and the target business chain do not belong to the same type of smart contract or the feature values of the smart contracts of business chain A and the target business chain are inconsistent, a translation request is sent to the blockchain access management engine. After the translation request is successfully matched, the blockchain access management engine calls the contract translation module to translate the smart contract, and performs digital asset operations through the translated smart contract. After the transaction is completed, the asset destruction operation is executed on the smart contract of business chain A, and the execution result is broadcast and the corresponding account status is updated.
9. A blockchain access management method according to claim 8, characterized in that: The specific steps of translation are as follows: S3.11: Blockchain access management engine calls the contract translation module; S3.12: The contract translation module performs entity parsing on the smart contracts of business chain A and the target business chain, extracts the asset name, serial number, owner, and status attributes of the smart contract, and completes the correspondence through the meta-attributes of the contract translation module; S3.13: Extract the mint and burn methods of business chain A, extract the creat and delete methods of the target business chain, and complete the correspondence through the contract translation module meta method; S3.14: After the translation request is successfully matched, the blockchain access management engine establishes a communication channel between business chain A and the target business chain. The channel communicates based on the key agreed upon by both parties, executes the smart contract of business chain A, and initiates a call to the smart contract of the target business chain based on the correspondence between the meta-attributes and meta-methods recorded in the contract translation module.
10. A blockchain access management method according to claim 4, characterized in that: In S4, the business chain communication records include inter-chain transaction records, inter-chain communication protocols, and inter-chain transaction confirmation time; Data cross-chain records include cross-chain transaction type, cross-chain data synchronization, and data cross-chain time; The node data involved include node type, node quantity, and node distribution; Operational audits include transaction volume audits, transaction speed statistics, and transaction fee statistics.
Citation Information
Patent Citations
Cross-link interface calling validity verification method
CN111666325A
Blockchain multi-chain cross-chain system and implementation mechanism thereof
CN112287029A
Cross-chain contract analysis method of block chain, relay chain and cross-chain system
CN112488679A
Cross-chain transaction credibility verification method and device and computer equipment
CN112508563A
Blockchain cross-chain regulation method for governance of chain by chain
WO2023201927A1