Data processing method, device and equipment based on block chain and readable storage medium

By acquiring and customizing the target blockchain files in the blockchain database, the problem of low efficiency in generating blockchain delivery files is solved, achieving more efficient generation and management of blockchain delivery files.

CN120973764APending Publication Date: 2025-11-18TENCENT TECHNOLOGY (SHENZHEN) CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202410612856.8
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-05-16
Publication Date
2025-11-18

AI Technical Summary

Technical Problem

In existing technologies, the generation efficiency is low when different entities generate blockchain delivery documents due to the large amount of customized information.

Method used

By obtaining the request to generate blockchain delivery documents, the target underlying blockchain file in the underlying blockchain database is extracted and customized to generate the blockchain delivery documents.

Benefits of technology

It improves the efficiency of generating blockchain delivery documents and managing the underlying blockchain documents, ensuring the timely generation of blockchain delivery documents.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN120973764A_ABST
    Figure CN120973764A_ABST
Patent Text Reader

Abstract

The embodiment of the invention discloses a data processing method and device based on a block chain, equipment and a readable storage medium. The method comprises the steps that a generation request for a block chain delivery file used for building a block chain is acquired, the generation request is used for indicating attribute information corresponding to a target bottom chain file needed to be used for generating the block chain delivery file, and the generation request comprises customization demand information for building the block chain; extracting a target bottom chain file matched with the attribute information from a plurality of bottom chain files contained in a bottom chain database; and based on the customization demand information, performing customization modification on the target bottom chain file, and generating a block chain delivery file. Through the method, the generation efficiency of the block chain delivery file can be improved.
Need to check novelty before this filing date? Find Prior Art

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of blockchains, in particular to a data processing method and device based on a blockchain, equipment and a readable storage medium. BACKGROUND

[0002] A blockchain is a new application mode of computer technologies such as distributed data storage, peer-to-peer transmission, consensus mechanism and encryption algorithm. Some entities often deploy a blockchain within the entity in order to facilitate data management.

[0003] In related technologies, different entities usually have different blockchain deployment requirements. In the case of generating a blockchain delivery file corresponding to each entity to build a blockchain, a base chain file is first generated, and then a blockchain delivery file is generated based on the base chain file, which greatly reduces the generation efficiency of the blockchain delivery file.

[0004] Therefore, how to improve the generation efficiency of the blockchain delivery file is a problem to be solved. SUMMARY

[0005] To solve the above technical problems, embodiments of the present application provide a data processing method and device based on a blockchain, equipment and a readable storage medium.

[0006] The technical scheme adopted by the present application is as follows:

[0007] A data processing method based on a blockchain comprises:

[0008] Obtaining a generation request for a blockchain delivery file used to build a blockchain, the generation request being used to indicate attribute information of a target base chain file required to be used to generate the blockchain delivery file, and the generation request comprising customization requirement information for building a blockchain;

[0009] Extracting a target base chain file matching the attribute information from a plurality of base chain files contained in a base chain database;

[0010] Customizing and modifying the target base chain file based on the customization requirement information to generate the blockchain delivery file.

[0011] A data processing device based on a blockchain comprises:

[0012] An obtaining unit configured to obtain a generation request for a blockchain delivery file used to build a blockchain, the generation request being used to indicate attribute information of a target base chain file required to be used to generate the blockchain delivery file, and the generation request comprising customization requirement information for building a blockchain;

[0013] an extraction unit configured to extract a target bottom chain file matching the attribute information from a plurality of bottom chain files contained in a bottom chain database;

[0014] a processing unit configured to perform customized modification on the target bottom chain file based on the customized requirement information, and generate the blockchain delivery file.

[0015] In an embodiment of the present application, based on the foregoing scheme, after the generation request for the blockchain delivery file for building a blockchain is acquired, the processing unit is further configured to generate blockchain function information corresponding to the blockchain delivery file based on the generation request, determine target type information and target version information of a bottom chain file required for constructing the blockchain function information, and combine the target type information and the target version information to obtain attribute information corresponding to the target bottom chain file.

[0016] In an embodiment of the present application, based on the foregoing scheme, the attribute information includes target type information and target version information; and the processing unit is further configured to, if a target database table matching the target type information is acquired from the bottom chain database, detect version information of each bottom chain file included in the target database table; and if a bottom chain file having version information matching the target version information is detected in the target database table, determine the detected bottom chain file as the target bottom chain file.

[0017] In an embodiment of the present application, based on the foregoing scheme, the attribute information includes target type information and target version information; after the generation request for the blockchain delivery file for building a blockchain is acquired, the processing unit is further configured to, if a target bottom chain file matching the attribute information is not extracted from a plurality of bottom chain files contained in a bottom chain database, generate the target bottom chain file based on the target type information and the target version information; and a storage unit configured to store the target bottom chain file into the bottom chain database.

[0018] In an embodiment of the present application, based on the foregoing scheme, the processing unit is further configured to perform filling processing on a preset bottom chain template based on the target type information and the target version information to obtain a filled bottom chain template; and if the filled bottom chain template is verified successfully, encapsulate the filled bottom chain template to obtain the target bottom chain file.

[0019] In an embodiment of the present application, based on the foregoing scheme, the processing unit is further configured to set a release state of the target bottom chain file as a released state, determine a target database table matching the target type information from a bottom chain database, and import the target bottom chain file into the target database table.

[0020] In an embodiment of the present application, based on the foregoing scheme, the processing unit is further configured to modify the target base chain file based on the customization requirement information to obtain a customized base chain file, and package the customized base chain file to obtain the blockchain delivery file.

[0021] In an embodiment of the present application, based on the foregoing scheme, the processing unit is further configured to, if it is detected that the target base chain file includes customized content matching the customization requirement information of other blockchains, delete the customized content from the target base chain file to obtain an updated base chain file, and modify the updated base chain file based on the customization requirement information to obtain a customized base chain file.

[0022] In an embodiment of the present application, based on the foregoing scheme, the processing unit is further configured to, if the number of customized base chain files is one, package the customized base chain file to obtain the blockchain delivery file, and if the number of customized base chain files is more than one, merge the plurality of customized base chain files to obtain a merged base chain file, and package the merged base chain file to obtain the blockchain delivery file.

[0023] A blockchain-based data processing device includes a processor and a memory, and the memory stores computer readable instructions. When the computer readable instructions are executed by the processor, the blockchain-based data processing method is implemented.

[0024] A computer readable storage medium stores computer readable instructions. When the computer readable instructions are executed by a processor of a computer, the computer performs the blockchain-based data processing method.

[0025] A computer program product includes computer readable instructions. When the computer readable instructions are executed by a processor, the blockchain-based data processing method is implemented.

[0026] In the above technical solution:

[0027] The generation request for the blockchain delivery file for building a blockchain can be obtained, and the attribute information of the target base chain file required for generating the blockchain delivery file is included in the generation request. In this way, it can be known which base chain files need to be obtained to construct the blockchain delivery file. Next, the target base chain file matching the attribute information can be extracted from the plurality of base chain files contained in the base chain database, and the target base chain file can be modified based on the customization requirement information to generate the blockchain delivery file.

[0028] In one aspect, after receiving a generation request of a blockchain delivery file, if the target bottom chain file is obtained from the bottom chain database, only customized modification is needed, without the need to generate a new bottom chain file, thereby improving the generation efficiency of the blockchain delivery file.

[0029] In another aspect, the bottom chain database is used to manage the bottom chain files, so that the data management is more orderly, the acquisition efficiency of the bottom chain file is improved, and the generation efficiency of the blockchain delivery file is improved.

[0030] It should be understood that the foregoing general description and the following detailed description are only exemplary and explanatory, and cannot limit the present application. BRIEF DESCRIPTION OF DRAWINGS

[0031] The drawings incorporated into the specification and forming a part thereof, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the application. It is clear that the drawings in the following description are only some embodiments of the present application, and for those skilled in the art, other drawings can be obtained from these drawings without creative labor. In the drawings:

[0032] Figure 1 is a structural schematic diagram of a blockchain network related to the present application;

[0033] Figure 2 is a schematic diagram of an implementation environment related to the present application;

[0034] Figure 3 is a web page corresponding to a product end related to the present application;

[0035] Figure 4 is an internal architecture schematic diagram of a blockchain operation management system related to the present application;

[0036] Figure 5 is a flowchart of a blockchain-based data processing method according to an exemplary embodiment;

[0037] Figure 6 is a flowchart of a blockchain-based data processing method according to another exemplary embodiment;

[0038] Figure 7 is a flowchart of a blockchain-based data processing method according to another exemplary embodiment;

[0039] Figure 8 is a flowchart of a blockchain-based data processing method according to another exemplary embodiment;

[0040] Figure 9is a flowchart of a blockchain-based data processing method according to another exemplary embodiment;

[0041] Figure 10 is a flowchart of a blockchain-based data processing method according to another exemplary embodiment;

[0042] Figure 11 is a block diagram of a blockchain-based data processing apparatus according to an exemplary embodiment;

[0043] Figure 12 is a structural schematic diagram of a computer system of a blockchain-based data processing device according to an exemplary embodiment. DETAILED DESCRIPTION

[0044] The exemplary embodiments will be described in detail with reference to the accompanying drawings. In the following description, the same drawing reference numerals are used to denote elements in the various figures. The following exemplary embodiments are not representative of all embodiments that are identical to the present application. Rather, they are merely examples of apparatuses and methods identical to some aspects of the present application as detailed in the appended claims.

[0045] The block diagrams shown in the accompanying drawings are merely functional entities, and do not necessarily have to correspond to physically independent entities. That is, the functional entities can be implemented in software, or in one or more hardware modules or integrated circuits, or in different network and / or processor apparatuses and / or microcontroller apparatuses.

[0046] The flowcharts shown in the accompanying drawings are merely exemplary illustrations, and do not necessarily include all contents and operations / steps, nor do they have to be executed in the order described. For example, some operations / steps can be further divided, and some operations / steps can be integrated or partially integrated, so the actual execution order can be changed depending on the actual situation.

[0047] It should be noted that "a plurality of" as mentioned in the present application means two or more. The association relationship of "and / or" described in the associated objects means that there can be three relationships, for example, A and / or B can mean that A exists alone, A and B exist together, and B exists alone, the three cases. The character " / " generally means that the associated objects before and after are in an "or" relationship.

[0048] It should be noted that in the specific embodiments of the present application, data related to the user is involved, when the embodiments of the present application are applied to specific products or technologies, the user's permission or consent needs to be obtained, and the collection, use and processing of related data needs to comply with relevant laws, regulations and standards of the country and region. At the same time, the formula involved in the embodiments of the present application can be flexibly adjusted, for example, increasing or reducing corresponding parameters.

[0049] Before introducing the technical solutions of the embodiments of the present application, the technical terms involved in the embodiments of the present application are introduced here.

[0050] The block chain (Block Chain) technology is a new distributed infrastructure and computing method, which 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 uses automatic script code to program and operate data. The block chain refers to a decentralized, distributed storage-based infrastructure, which is a data structure composed of data blocks in time sequence in the form of linked list, which can safely store data with chronological relationship and can be verified in the system, and can be guaranteed by cryptography. In short, the block chain is a decentralized distributed account book, and each chain is equivalent to an independent account book.

[0051] The block chain underlying platform can include user management, basic service, smart contract and operation monitoring processing modules. Among them, the user management module is responsible for the identity information management of all block chain participants, including maintaining public and private key generation (account management), key management, and user real identity and block chain address correspondence maintenance (permission management), etc., and under authorization, supervising and auditing the transaction of some real identity, providing risk control rule configuration (risk audit); The basic service module is deployed on all block chain node devices to verify the validity of business requests, and record to the storage after completing the consensus for valid requests. For a new business request, the basic service first parses and authenticates the interface (interface adaptation), then encrypts the business information through the consensus algorithm (consensus management), and then transmits it to the shared account book (network communication) after the encryption is complete. Consistent and complete record storage; the smart contract module is responsible for contract registration and issuance, contract triggering and contract execution. Developers can define contract logic through a certain programming language, publish it to the block chain (contract registration), call keys or other event triggers to execute according to the logic of contract terms, complete contract logic, and also provide contract upgrade and cancellation functions; The operation monitoring module is mainly responsible for the deployment, configuration modification, contract setting, cloud adaptation in the product release process, and the real-time state visualization output in the product running.

[0052] A consortium chain is a form of blockchain network that is managed and controlled by a group of known entities, usually organizations, enterprises or institutions. Unlike public chains, participants in a consortium chain need to be licensed to join the network, and the control of the network is usually managed by the participants together, rather than in a completely decentralized way. Participants in a consortium chain network are licensed and usually controlled and managed by a group of known entities or organizations. These participants may be enterprises, financial institutions, government departments, etc. Because the participants are licensed, consortium chains usually have higher privacy and security, and can limit data access and transaction visibility. Consortium chains usually have higher customization, and can customize the rules, consensus mechanisms, data storage methods, etc. of the blockchain network according to the needs of participants. Consortium chains can be used for cooperation between enterprises or organizations to build private and secure blockchain networks for solving specific business problems, such as supply chain management, cross-border payment, digital asset management, etc. It can provide more efficient, secure and transparent transaction and cooperation methods for participants, while protecting the privacy and business interests of participants.

[0053] The blockchain base chain is the infrastructure of the blockchain system, similar to the kernel of the operating system. It mainly includes consensus mechanisms, data storage, transaction verification and block generation, etc. The consensus mechanism ensures the consistent recognition of transactions among all nodes in the network, ensuring the accuracy and security of data; data storage is responsible for saving all transaction information and state data, usually in the form of distributed database or distributed ledger, ensuring the data's non-tamperability and transparency; transaction verification is to verify and confirm transactions to ensure their validity and legality; and block generation is to package verified transactions into blocks and add them to the blockchain, forming a chain structure. These underlying functions together form the core of the blockchain system, providing a solid foundation for the operation and development of blockchain applications. In the embodiments of the present application, the blockchain base chain can include multiple types, such as Bcos, Fabric and Chainmaker, etc.

[0054] MySQL has a wide range of applications in web applications. Relational Database Management System (RDBMS) is a database system based on the relational model, which uses tables to store data and organizes and manages data by establishing relationships between different tables. MySQL has high performance, reliability and ease of use, and provides rich features and powerful performance optimization tools, making it one of the preferred database management systems for many WEB applications.

[0055] In the related art, different entities can have different blockchain deployment requirements. When customizing the blockchain delivery files required by different entities, a large amount of customization information is generated, thereby creating a large number of base chain files for constructing the blockchain delivery files. However, the large amount of customization information can cause the generation of the blockchain delivery files and the generation efficiency to be reduced.

[0056] Based on this, the embodiments of the present application respectively propose a blockchain-based data processing method, a blockchain-based data processing device, a blockchain-based data processing equipment, a computer readable storage medium, and a computer program product. In these embodiments, a generation request for a blockchain delivery file used to build a blockchain can be obtained, and the generation request includes attribute information of a target base chain file required to generate the blockchain delivery file. In this way, it can be known which base chain files need to be obtained to construct the blockchain delivery file. Next, the target base chain file matching the attribute information can be extracted from a plurality of base chain files contained in a base chain database, and the target base chain file can be customized and modified based on customization requirement information, thereby generating the blockchain delivery file. In this method, on the one hand, after receiving the generation request of the blockchain delivery file, if the target base chain file is obtained from the base chain database, it only needs to be customized and modified, without the need to generate a new base chain file, thereby improving the generation efficiency of the blockchain delivery file. On the other hand, the base chain database is used to manage each base chain file, so that the management of data is more orderly, the acquisition efficiency of the base chain file is improved, and the generation efficiency of the blockchain delivery file is improved.

[0057] Figure 1 FIG. 1 is a structural schematic diagram of a blockchain network according to an example embodiment. Figure 1 The blockchain network 100 shown can include a node device 10a, a node device 10b, a node device 10c, and a node device 10d. The node device 10a, the node device 10b, the node device 10c, and the node device 10d are all blockchain nodes (referred to as nodes for short) in the blockchain network 100. Figure 1 The nodes in the blockchain network 100 shown can be any form of computing devices accessing the blockchain network 100, such as servers, user terminals, etc. Figure 1 The node device 10a, the node device 10b, the node device 10c, and the node device 10d shown can also be connected to form the blockchain network 100 in the form of network communication.

[0058] Figure 1The type of blockchain involved in the architecture of the blockchain network 100 shown can specifically include a public blockchain, a private blockchain and a consortium blockchain. The type of blockchain used in different blockchain application scenarios can be different, which is not limited here. The public blockchain refers to a blockchain that can be publicly disclosed and joined and accessed by anyone. Blocks on the public blockchain can be viewed by anyone, anyone can initiate a transaction on the public blockchain, and anyone can participate in the consensus process of the public blockchain at any time. The private blockchain refers to a blockchain that can be used within a private organization. The read-write permission and the permission to participate in accounting on the blockchain can be formulated according to the rules of the private organization. It is usually used for data management, auditing, etc. within an enterprise. The consortium blockchain refers to a blockchain in which the read-write permission and the permission to participate in accounting of the consortium members participating in the consortium blockchain can be formulated according to the rules of the consortium. It is usually used for scenarios such as inter-institutional transactions, settlement or clearing.

[0059] Please refer to Figure 2 , Figure 2 is a schematic diagram of an implementation environment involved in the present application.

[0060] Figure 2 The implementation environment shown includes a request end 210 and a blockchain operation and management system 220, wherein the blockchain operation and management system 220 further includes a product end 230, an operation and maintenance end 240, a development end 250, a test end 260 and a database 270. The product end 230, the operation and maintenance end 240, the development end 250 and the test end 260 are all ports in the blockchain operation and management system 220, and each port can interact.

[0061] The product end 230 can receive a generation request for a blockchain delivery file for building a blockchain sent by the request end 210. The generation request can include dimensions such as functions and characteristics required by the request end for building a blockchain. After receiving the generation request, the product end 230 can analyze it to analyze attribute information corresponding to a target base chain file required for generating the blockchain delivery file.

[0062] In the embodiment of the present application, the product end 230 is a front end in the blockchain operation and management system 220. The front end can be displayed in the form of a WEB (web) page, such as Figure 3A product end corresponding to a webpage schematic diagram involved in an embodiment of the present application. In the webpage schematic diagram, the content of the project management column is presented, and the project management can include business projects, public services and base platforms. Among them, the business projects include projects requested by different request ends, and these projects can be based on different platforms, for example, BaaS is based on the tbaas platform, DID is based on the tdid platform, BIS is a cross-chain project, BCC business is a number chain pass, etc. The public services are services that can be used by the requested projects of each request end, for example, the account center (Account Center) and the operation and maintenance management platform (OMC). The base platform is the infrastructure, which provides a series of basic functions and services to support the upper-layer application and business, for example, it can be a blockchain private platform (Pedestal).

[0063] The product end 230 can respond to the generation request to obtain a target bottom chain file from the bottom chain database included in the database 270, and the target bottom chain file can be used to build the blockchain requested by the request end 210 to build. If the product end 230 obtains the target bottom chain file, it can directly customize and modify it to obtain a customized bottom chain file. If the product end 230 does not obtain the target bottom chain file in the database 270, it needs to send a generation request for the target bottom chain file to the development end 250, so that the development end 250 generates the target bottom chain file. The test end 260 tests and verifies the target bottom chain file generated by the development end 250, and if the test and verification are passed, the target bottom chain file can be stored in the database 270, so that the product end 230 can obtain the target bottom chain file and customize and modify it to obtain a customized bottom chain file.

[0064] The operation and maintenance end 240 encapsulates the customized bottom chain file to generate a blockchain delivery file. Next, the operation and maintenance end 240 can send the blockchain delivery file to the request end 210 and deploy the blockchain delivery file according to the customer running environment of the request end 210 to complete the building of the blockchain. In this way, the request end 210 can have its own private customized blockchain. Among them, the private customized blockchain in the embodiment of the present application can refer to a private customized alliance chain.

[0065] It should be noted that the blockchain operation and management system 220 contains a database 270, and the database 270 contains a plurality of MySQL databases, such as a bottom chain database, a license database and a user data statistics database.

[0066] The bottom chain database can store various types of bottom chain files, such as Bcos, Fabric, Chainmaker, etc. Bottom chain files of the same type can be stored in the same database table, and different versions of bottom chain files can be stored in one database table. For example, the Bcos type database table can store Bcos1.0, Bcos2.0, and Bcos3.0 version Bcos bottom chain files.

[0067] The certificate database can store certificates corresponding to different users. These certificates can be generated by the blockchain operation management system 220. After receiving the generation request sent by the product end 230, the blockchain operation management system 220 can generate blockchain function information corresponding to the blockchain delivery file based on the generation request, and based on the blockchain function information, a plurality of certificates corresponding to the request end can be generated. These certificates can be used to analyze whether each bottom chain file in the current bottom chain database can meet the implementation of the blockchain function information. These certificates will be stored in the certificate database, and the certificates corresponding to each request end will be stored together, so that the management of data is more orderly.

[0068] The user data statistics database can statistically analyze the total number of networks, the total number of nodes, and the number of inventory users in the formal network of the blockchain built by each request end through the received blockchain delivery file, and the number of inventory users and the cumulative number of users in the experience network. These data can reflect the usage information of the blockchain built by the request end, facilitating the maintenance and management of the blockchain by the blockchain operation management system 220 and the request end.

[0069] As shown in the figure, Figure 4 The internal architecture of a blockchain operation management system according to an embodiment of the present application. In the internal architecture of the blockchain operation management system, the front-end system, the back-end service, and the running environment are included.

[0070] In the front-end page of the front-end system, a plurality of options are included, such as Figure 3 The project management, license management, user data statistics, forensic tool operation, and operation audit option modules shown in the figure. The skilled person in the art clicks different option modules in the front-end page, and the system will be linked with the back-end service and the running environment to trigger the execution of corresponding tasks. When the option module in the front-end page is selected, the front-end will generate a request, which will be sent to the back-end service. The request includes the task to be executed. The request can be an Ajax request. The Ajax request can call the back-end service to perform corresponding addition and modification operations on the database tables in the back-end service.

[0071] The backend service is a service for processing various task requests sent by the front-end system in the embodiments of the present application. In the backend service, there are intelligent gateways, resource services, permission management, routing distribution, operation platform services, cloud databases, and exception alarm services.

[0072] The intelligent gateway can first link the functions corresponding to each option, so that when a certain option module is clicked, the backend service only knows which data flow processing should be performed. The intelligent gateway can use the Taihu service.

[0073] The resource service can be used to store resource request logs, which can record the selection records of different options by those skilled in the art.

[0074] The permission management service can determine whether the request sent by the front-end has permission. When managing permissions, the Disku service can be used.

[0075] Routing distribution can route the database required for the request and provide the identification information of the corresponding MySQL database for the request. For example, for the certificate service, the identification information of the MySQL database corresponding to the certificate service can be provided; for the user data statistics service, the identification information of the MySQL database corresponding to the user data statistics service can be provided; for the evidence tool operation service, the identification information of the MySQL database corresponding to the evidence tool operation service can be provided, and so on.

[0076] In the backend service, the number of databases can be set by those skilled in the art, so that the information in multiple dimensions such as blockchain function characteristics, version characteristics, and menu configuration can be stored, facilitating the use when similar function blockchain delivery files are configured afterwards. In the embodiments of the present application, the databases of the backend service can follow the following principles when designed:

[0077] 1. Standardization: follow the standardization principle to decompose data into smaller and more concise tables to reduce data redundancy and maintain data consistency. Use appropriate primary and foreign key relationships to establish associations between tables.

[0078] 2. Index optimization: create indexes reasonably to improve query performance. According to frequently used query conditions and access patterns, select appropriate columns to create indexes to avoid excessive or unnecessary indexes.

[0079] 3. Data type selection: select appropriate data types to save storage space and ensure data accuracy. Avoid using excessively large or small data types, and select appropriate types such as integers, strings, dates, etc. according to the characteristics of the data.

[0080] 4. Avoid overdesign: Avoid overly normalized or overly complex table designs. Balance the degree of normalization and redundancy based on actual requirements and performance needs.

[0081] 5. Scalability considerations: When designing database tables, consider future scalability needs. Reserve enough room for additional data fields or functionality.

[0082] The operation service platform can record the running log of the current system.

[0083] The cloud database can be used to save the running log recorded by the operation service platform.

[0084] The exception alarm service can analyze the running log in the cloud database to detect whether an exception has occurred in the current system. If an exception has occurred, an alarm information can be output.

[0085] Optionally, the intelligent gateway, the permission management, the routing distribution and the exception alarm service can all access the third-party extension service, that is, the implementation of these functions can be realized by the third-party extension service. For example, Figure 4 The Taihu service, the Pangu service, the certificate service, the user data statistics service, the evidence tool operation service and the exception alarm service in the above table are all third-party extension services.

[0086] The backend service part in the embodiment of the present application can be realized by Node.js. Through Node.js, the system can communicate with the MySQL database and support the extension of multiple services.

[0087] The blockchain operation management system further includes a running environment part, in which two Pods (container groups) are contained. One Pod is a minimum deployment unit composed of one or more containers. These containers share network and storage resources and usually work together to realize the function of an application. The two Pods are both subjected to load balancing processing, so that the system can more evenly allocate tasks when processing tasks, avoiding the situation that one Pod processes a large number of tasks and the other Pod processes a small number of tasks. Each Pod is connected to a packaging file (docker), so that each Pod can generate a blockchain delivery file through packaging by using the packaging file.

[0088] It should be noted that the request end 210 in the embodiments of the present application can be a terminal device, which can be a mobile phone, a tablet computer, a notebook computer, a palm computer, a mobile internet device (MID), a vehicle-mounted device, a flying device, a wearable device (such as a smart device of a smart watch, a smart bracelet, a pedometer, etc.), a virtual reality device (such as a VR (Virtual Reality) device, an AR (Augmented Reality) device), and the like.

[0089] Optionally, the blockchain operation management system 220 in the embodiments of the present application can be a server, which can be a stand-alone physical server, a server cluster or a distributed system composed of multiple physical servers, or a cloud server providing cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, CDN (Content Delivery Network), and basic cloud computing services such as big data and artificial intelligence platforms.

[0090] Please refer to Figure 5 , Figure 5 is a flowchart of a blockchain-based data processing method according to an exemplary embodiment. The method can be applicable to Figure 2 the implementation environment shown in the figure, and is specifically executed by the blockchain operation management system 220 (referred to as the system). Of course, the method can also be applicable to other implementation environments, and the execution subject of the method is not limited herein.

[0091] The blockchain-based data processing method will be described in detail below with the blockchain operation management system 220 as an exemplary execution subject. As shown in Figure 5 in an exemplary embodiment, the method includes at least the following steps:

[0092] S510, obtaining a generation request for a blockchain delivery file for building a blockchain, the generation request being used to indicate attribute information of a target base chain file required to generate the blockchain delivery file, and the generation request including customization requirement information for building the blockchain.

[0093] In an embodiment of the present application, after the system obtains the generation request for the blockchain delivery file for building the blockchain, the system generates the blockchain function information corresponding to the blockchain delivery file based on the generation request, and determines the target type information and the target version information of the base chain file required to construct the blockchain function information. Finally, the target type information and the target version information are merged to obtain the attribute information of the target base chain file.

[0094] Optionally, after obtaining the generation request for the blockchain delivery file for building the blockchain, the system can generate the blockchain function information corresponding to the blockchain delivery file based on the generation request. Based on the blockchain function information, the system can generate a plurality of certificates corresponding to the request end, and the certificates can be used to analyze whether the plurality of base chain files in the current base chain database can meet the implementation of the blockchain function information.

[0095] In an embodiment of the present application, the number of target base chain files can be multiple, and the generation request can indicate target type information and target version information corresponding to each target base chain file.

[0096] S520, extracting a target base chain file matching the attribute information from the plurality of base chain files contained in the base chain database.

[0097] The attribute information includes target type information and target version information. The target type information is used to indicate the type of the target base chain file, such as Bcos type, Fabric type, Chainmaker type, etc. The target version information is used to indicate the version information of the base chain file corresponding to the target type information, such as 1.0 version, 2.0 version and 3.0 version, etc.

[0098] The system will first search the target database table matching the target type information in the base chain database according to the target type information, and then search the base chain file matching the target version information in the target database table as the target base chain file.

[0099] Specifically, if the target database table matching the target type information is obtained from the base chain database, the version information of each base chain file included in the target database table is detected. If it is detected that there is a base chain file in the target database table whose version information matches the target version information, the detected base chain file is determined as the target base chain file.

[0100] If the target base chain file matching the attribute information is not extracted from the plurality of base chain files contained in the base chain database, the target base chain file is generated based on the target type information and the target version information. Moreover, the generated target base chain file needs to be stored in the base chain database.

[0101] When generating the target base chain file, the system fills the preset base chain template based on the target type information and the target version information to obtain a filled base chain template. If the filled base chain template is verified successfully, the filled base chain template is encapsulated to obtain the target base chain file.

[0102] Wherein, when the generated target bottom chain file is stored in the bottom chain database, the system needs to set the publishing state of the target bottom chain file as published, then determine the target database table matched with the target type information from the bottom chain database, and finally import the target bottom chain file into the target database table.

[0103] S530, customizing and modifying the target bottom chain file based on the customization requirement information to generate the blockchain delivery file.

[0104] Specifically, the system customizes and modifies the target bottom chain file based on the customization requirement information to obtain a customized bottom chain file. The customized bottom chain file can also be called a configuration file, which can be a js format file, and its name can be set by those skilled in the art, for example, it can be a file named "System.js". Wherein, the customized bottom chain file is generated by the product end in the system, and the product end sends the customized bottom chain file to the operation and maintenance end in the system. The operation and maintenance end can put the customized bottom chain file into the corresponding packaging pipeline, and use the preset packaging file (docker) to package the customized bottom chain file to obtain the blockchain delivery file.

[0105] In an embodiment of the present application, if it is detected that the target bottom chain file includes customized content matched with the customization requirement information of other blockchains, the customized content is deleted from the target bottom chain file to obtain an updated bottom chain file. The updated bottom chain file is customized and modified based on the customization requirement information to obtain a customized bottom chain file.

[0106] In an embodiment of the present application, if the number of customized bottom chain files is one, the customized bottom chain file is packaged to obtain the blockchain delivery file; if the number of customized bottom chain files is multiple, the multiple customized bottom chain files are merged to obtain a merged bottom chain file, and the merged bottom chain file is packaged to obtain the blockchain delivery file.

[0107] Through the method, on the one hand, after the blockchain operation and management system receives the generation request of the blockchain delivery file, if the target bottom chain file is obtained from the bottom chain database, it only needs to be customized and modified, without the need to generate a new bottom chain file, which improves the generation efficiency of the blockchain delivery file. If the target bottom chain file is not obtained, the target bottom chain file can also be generated in time for customized and modified modification, which ensures the timely generation of the blockchain delivery file. On the other hand, the bottom chain database is used to manage each bottom chain file, which makes the management of data more orderly, improves the acquisition efficiency of the bottom chain file, and thus improves the generation efficiency of the blockchain delivery file.

[0108] In an embodiment of the present application, another blockchain-based data processing method is provided, which can be executed by a blockchain operation management system. As shown in Figure 6 The blockchain-based data processing method can include S510, S610-S630 and S520-S530. That is, S610-S630 is the method needed to be implemented after S510 as shown. Figure 5

[0109] S610-S630 are described as follows:

[0110] S610, based on a generation request, generates blockchain function information corresponding to a blockchain delivery file.

[0111] The generation request contains some functional requirements of the requestor for building a blockchain, and the system detects these functional requirements to determine which functional information in the system corresponds to these functional requirements for building a blockchain.

[0112] For example, the functional requirement in the generation request is: to implement a multi-level permission management mechanism to ensure that different role users have different permissions, including reading data, submitting transactions, managing smart contracts, etc. The system detects this functional requirement and determines the corresponding functional information in the blockchain system. The functional requirement corresponds to the permission management function, the smart contract writing function, and the transaction verification function in building a blockchain. Among them, the permission management module is used to manage user identity authentication and permission allocation; the smart contract writing function is used to define the permissions of different role users and execute permission verification logic on the blockchain to ensure that users comply with permission rules when executing transactions; the transaction verification function can ensure that the transaction contains permission verification logic and verifies the user's permission before transaction execution to ensure that only users with corresponding permissions can perform corresponding operations.

[0113] S620, determines the target type information and target version information of the underlying chain file needed to build the blockchain function information.

[0114] Specifically, the system can generate a plurality of certificates corresponding to the requestor based on the blockchain function information, and these certificates can be used to represent the target type information and target version information of the underlying chain file needed to build the blockchain function information.

[0115] In an embodiment of the present application, when building a blockchain, the number of underlying chain files needed can be multiple, and each underlying chain file also needs to specify version information.

[0116] ​For example, the target bottom chain file required by the blockchain requested to be built by the request end includes a Bcos type bottom chain file with version information of 2.0 version, and a Fabric type bottom chain file with version information of 4.0 version. Then the target type information of the bottom chain file required by the blockchain function information of the blockchain to be built is Bocs and Fabric, and the target version information is 2.0 version and 4.0 version in turn.

[0117] S630, merging the target type information and the target version information to obtain attribute information corresponding to the target bottom chain file.

[0118] The system can generate attribute information corresponding to the target bottom chain file based on the determined target type information and target version information through merging.

[0119] Through the method, the system can identify the target type information and target version information of the target bottom chain file required for generating the blockchain delivery file based on the generation request of the blockchain delivery file sent by the request end for building the blockchain, so that the blockchain delivery file can be generated more accurately, and the accuracy of the blockchain delivery is improved.

[0120] In an embodiment of the present application, another blockchain-based data processing method is provided, which can be executed by a blockchain operation and management system. As shown in Figure 7 The blockchain-based data processing method can include S510, S710 to S720 and S530. That is, S710 to S720 are Figure 5 the specific implementation method of S520.

[0121] S710 to S720 are described below:

[0122] S710, if the target database table matching the target type information is obtained from the bottom chain database, the version information of each bottom chain file included in the target database table is detected.

[0123] Wherein, when the system searches for the target bottom chain file in the bottom chain database, it can first find the target database table corresponding to the target type information from the plurality of bottom chain database tables included in the bottom chain database, and then query the bottom chain file with the version matching the target version information in the target database table.

[0124] Since the number of target bottom chain files can be multiple, the system will obtain multiple target database tables from the bottom chain database according to the target type information of each target bottom chain file.

[0125] S720, if it is detected that there is a bottom chain file in the target database table whose version information matches the target version information, the detected bottom chain file is determined as the target bottom chain file.

[0126] Each target database table can contain a bottom chain file, and if a bottom chain file whose version information matches the target version information is detected, it can be determined that the target bottom chain file is obtained.

[0127] For example, a Bcos bottom chain file of version 2.0 and a Fabric bottom chain file of version 4.0 are generated to represent the request. If the system finds a database table of the Bcos type in the bottom chain database, and finds a bottom chain file of version 2.0 in the database table of the Bcos type, the system can determine the bottom chain file as the target bottom chain file. Similarly, if the system finds a database table of the Fabric type in the bottom chain database, and finds a bottom chain file of version 4.0 in the database table of the Fabric type, the system can also determine the bottom chain file as the target bottom chain file.

[0128] It should be noted that only when all the target bottom chain files indicated by the generation request are obtained in the bottom chain database, the system will perform subsequent operations of customizing and modifying the target bottom chain file.

[0129] Through the method, the bottom chain database is used to manage each bottom chain file, so that the management of data is more orderly, the acquisition efficiency of the bottom chain file is improved, and the system can timely customize and modify the target bottom chain file, thereby improving the generation efficiency of the block chain delivery file.

[0130] In an embodiment of the present application, another blockchain-based data processing method is provided, which can be executed by a blockchain operation and management system. As shown in Figure 8 The blockchain-based data processing method can include S510, S810 to S820, and S520 to S530. That is, S810 to S820 are Figure 5 The method to be implemented after S510 as shown.

[0131] S810 to S820 are described as follows:

[0132] S810, if a target bottom chain file matching the attribute information is not extracted from the plurality of bottom chain files contained in the bottom chain database, a target bottom chain file is generated based on the target type information and the target version information.

[0133] Among them, not extracting a target bottom chain file matching the attribute information from the plurality of bottom chain files contained in the bottom chain database includes two cases:

[0134] Firstly, no target database table matching the target type information was found in the bottom chain database.

[0135] Secondly, the target database table matching the target type information was found in the bottom link database, but no bottom link file matching the target version information was found in the target database table.

[0136] If the system detects either of the above two situations, it needs to generate the target bottom link file based on the target type information and target version information.

[0137] Since there can be multiple target bottom-chain files, the system records the target type and version information of any missing target bottom-chain files and fills this information into a document, which can be an agile collaboration platform (TAPD) document or an application programming interface (API) document, etc. Furthermore, the development team in the system can receive this document and generate the target bottom-chain files.

[0138] Specifically, the process of generating the target bottom chain file based on the target type information and the target version information may include S811 to S812.

[0139] The following describes S811 to S812:

[0140] S811, fill the preset bottom chain template based on the target type information and target version information to obtain the filled bottom chain template.

[0141] The preset bottom-chain target includes multiple components, such as custom data, Chinese and English menus, feature switches, and resource routes. The development team can populate the preset bottom-chain template based on target type and target version information to obtain a populated bottom-chain template. This populated bottom-chain template can then be used as the bottom-chain file associated with the target type and target version information.

[0142] S812, if the filled bottom chain template is successfully verified, the filled bottom chain template is encapsulated to obtain the target bottom chain file.

[0143] The system's testing end can test and verify the filled bottom chain template. If the verification is successful, the filled bottom chain file can be encapsulated using a bottom chain encapsulation file (docker) to obtain the target bottom chain file.

[0144] S820 stores the target bottom chain file in the bottom chain database.

[0145] Specifically, S820 may include S821 to S823.

[0146] The following describes S821 to S823:

[0147] S821, set the publishing state of the target base chain file to the published state.

[0148] When the target base chain file is in the published state, the next step of customized modification can be performed.

[0149] S822, determine the target database table matching the target type information from the base chain database.

[0150] The system needs to find the target database table matching the target type information in the agent database, so that it can be determined that the target base chain file should be stored in which target database table.

[0151] S823, import the target base chain file into the target database table.

[0152] The system needs to import and store the target base chain file into the target database table.

[0153] Through this method, if the system does not extract the target base chain file matching the attribute information from the plurality of base chain files contained in the base chain database, the development end will be called to generate the target base chain file and store it in the agent database, so that if the generation request of the blockchain delivery file of other blockchains needs to use the target base chain file, it can be directly obtained from the base chain database without generating the same type and version of the base chain file again, improving the generation efficiency of the blockchain delivery file.

[0154] In an embodiment of the present application, another blockchain-based data processing method is provided, which can be executed by a blockchain operation management system. As shown in Figure 9 The blockchain-based data processing method can include S510 to S520 and S910 to S920. That is, S910 to S920 are Figure 5 the specific implementation method of S530.

[0155] S910 to S920 are described below:

[0156] S910, based on the customized demand information, customizing and modifying the target base chain file to obtain a customized base chain file.

[0157] Specifically, the system needs to first detect whether there is customized content in the target base chain file that matches the customized demand information of other blockchains. This part of the customized content is not universal content, so it is an interfering content when performing customized modification.

[0158] Specifically, S910 can include S911 to S912.

[0159] The following describes S911-S912:

[0160] S911, if it is detected that the target base chain file includes customized content matching the customization requirement information of other blockchains, the customized content is deleted from the target base chain file to obtain an updated base chain file.

[0161] In an embodiment of the present application, in the target base chain file, the custom data, Chinese and English menus, and feature switches are customized content, and the system can detect whether these contents include customized content matching the customization requirement information of other blockchains. If it is detected, the customized content needs to be deleted from the target base chain file to obtain an updated base chain file. The updated base chain file is a template base chain file without content of the customization requirement information of other blockchains.

[0162] S912, the updated base chain file is customized and modified based on the customization requirement information to obtain a customized base chain file.

[0163] Specifically, the system can customize and modify the custom data, Chinese and English menus, and feature switches included in the updated base chain file based on the customization requirement information, so that the final customized base chain file can meet the blockchain function information.

[0164] S920, the customized base chain file is packaged to obtain a blockchain delivery file.

[0165] The system can use a preset packaging file to package the customized base chain file to obtain a blockchain delivery file.

[0166] Specifically, S920 can include S921-S922.

[0167] The following describes S921-S922:

[0168] S921, if the number of customized base chain files is one, the customized base chain file is packaged to obtain a blockchain delivery file.

[0169] When the number of customized base chain files is one, it indicates that the target base chain file required for generating the blockchain delivery file indicated by the generation request is one. At this time, the system only needs to package the customized base chain file corresponding to the target base chain file to obtain the blockchain delivery file.

[0170] S922, if the number of customized base chain files is multiple, the multiple customized base chain files are merged to obtain a merged base chain file, and the merged base chain file is packaged to obtain a blockchain delivery file.

[0171] When the number of the customized base chain files is multiple, it indicates that multiple target base chain files are required to be used to generate the blockchain delivery file indicated by the generation request. The system respectively modifies each target base chain file to obtain multiple customized base chain files. Before generating the blockchain delivery file, the system needs to merge the multiple customized base chain files to obtain a merged base chain file, and then encapsulates the merged base chain file to obtain the blockchain delivery file.

[0172] In an embodiment of the present application, the system can send the blockchain delivery file to the request end, and deploy the blockchain delivery file according to the customer running environment of the request end to complete the construction of the blockchain.

[0173] Through the method, the system can modify the target base chain file based on the customization requirement information, so that the finally generated blockchain delivery file can be used to meet the customization requirement of the request end and complete the functional customization of the blockchain. Moreover, the method can directly obtain the target base chain file from the base chain database and modify the target base chain file, without the need to re-create the target base chain file in the case that the base chain file of the existing type and version is matched, thereby improving the generation efficiency of the blockchain delivery file.

[0174] In an embodiment of the present application, another blockchain-based data processing method is provided, which can be executed by the request end, the ticket of the blockchain operation and management system, the operation and maintenance end, the development end and the test end. As shown in Figure 10 The blockchain-based data processing method can include S1001 to S1019.

[0175] S1001 to S1019 are described as follows:

[0176] S1001, the product end receives a generation request of a blockchain delivery file for constructing a blockchain sent by a request end.

[0177] S1002, the product end generates attribute information corresponding to a target base chain file.

[0178] The generation request is used to indicate the attribute information corresponding to the target base chain file required to generate the blockchain delivery file, and the generation request includes customization requirement information for constructing the blockchain.

[0179] S1003, the product end obtains the target base chain file based on the attribute information.

[0180] S1004, the product end judges whether the target database table matched with the target type information is obtained from the base chain database.

[0181] If yes, S1005 is executed; if no, S1008 is executed.

[0182] S1005, the product end detects whether there is a bottom chain file with version information matching the target version information in the target database table.

[0183] If yes, S1006 is executed; if no, S1008 is executed.

[0184] S1006, the product end detects whether the bottom chain file with version information matching the target version information is in a released state.

[0185] If yes, S1016 is executed; if no, S1007 is executed.

[0186] S1007, the product end sets the release state of the bottom chain file with version information matching the target version information to a released state.

[0187] After S1007 is executed, S1006 can be executed.

[0188] S1008, the product end generates an information document with target type information and target version information of the target bottom chain file that has not been obtained.

[0189] S1009, the product end sends the information document to the development end.

[0190] S1010, the development end generates a filled bottom chain template based on the target type information, the target version information, and a preset bottom chain target.

[0191] S1011, the development end sends the filled bottom chain template to the testing end.

[0192] S1012, the testing end tests and verifies the filled bottom chain template.

[0193] S1013, the development end judges whether the testing end tests and verifies the filled bottom chain template successfully.

[0194] If yes, S1014 is executed; if no, S1010 is executed.

[0195] S1014, the development end encapsulates the filled bottom chain template to obtain a target bottom chain file.

[0196] S1015, the development end imports the target bottom chain file into the bottom chain database.

[0197] After S1015 is executed, S1004 can be executed.

[0198] S1016, the development end customizes and modifies the target bottom chain file based on customization requirement information to obtain a customized bottom chain file.

[0199] The customization requirement information is contained in the generation request.

[0200] If the target base chain file includes customization content matching the customization requirement information of other blockchains, the customization content needs to be deleted to obtain an updated base chain file. At this time, the development end customizes and modifies the updated base chain file based on the customization requirement information to obtain a customized base chain file. The customized base chain file can be a system.js file.

[0201] S1017, the development end sends the customized base chain file to the operation and maintenance end.

[0202] S1018, the operation and maintenance end encapsulates the customized base chain file to obtain a blockchain delivery file.

[0203] S1019, the operation and maintenance end sends the blockchain delivery file to the request end.

[0204] Through the method, on the one hand, after the blockchain operation and management system receives the generation request of the blockchain delivery file, if the target base chain file is obtained from the base chain database, only the customization modification is needed, and a new base chain file does not need to be generated, thereby improving the generation efficiency of the blockchain delivery file. If the target base chain file is not obtained, the target base chain file can be generated in time, and then the customization modification is performed, thereby ensuring the timely generation of the blockchain delivery file. On the other hand, the base chain database is used to manage various base chain files, so that the data management is more orderly, the acquisition efficiency of the base chain file is improved, and the generation efficiency of the blockchain delivery file is improved.

[0205] Figure 11 is a block diagram of a blockchain-based data processing apparatus shown in an embodiment of the present application. As shown in the figure, the blockchain-based data processing apparatus can be applied to a computer, and the apparatus includes: Figure 11

[0206] A blockchain-based data processing device includes:

[0207] 1110, configured to obtain a generation request for a blockchain delivery file for building a blockchain, the generation request being used to indicate attribute information of a target base chain file required to be used for generating the blockchain delivery file, and the generation request including customization requirement information for building the blockchain;

[0208] The extraction unit 1120 is configured to extract a target base chain file matching the attribute information from a plurality of base chain files contained in the base chain database;

[0209] The processing unit 1130 is configured to customize and modify the target base chain file based on the customization requirement information to generate the blockchain delivery file.

[0210] ​In an embodiment of the present application, based on the foregoing scheme, after obtaining the generation request for the blockchain delivery file for building the blockchain, the processing unit 1130 is further configured to generate the blockchain function information corresponding to the blockchain delivery file based on the generation request; determine the target type information and the target version information of the underlying chain file required for constructing the blockchain function information; and combine the target type information and the target version information to obtain the attribute information of the target underlying chain file.

[0211] In an embodiment of the present application, based on the foregoing scheme, the attribute information includes the target type information and the target version information; and the processing unit 1130 is further configured to, if the target database table matching the target type information is obtained from the underlying chain database, detect the version information of each underlying chain file included in the target database table; and if the underlying chain file with the version information matching the target version information is detected in the target database table, determine the detected underlying chain file as the target underlying chain file.

[0212] In an embodiment of the present application, based on the foregoing scheme, the attribute information includes the target type information and the target version information; and after obtaining the generation request for the blockchain delivery file for building the blockchain, the processing unit 1130 is further configured to, if the target underlying chain file matching the attribute information is not extracted from the plurality of underlying chain files contained in the underlying chain database, generate the target underlying chain file based on the target type information and the target version information; and the storage unit 1140 is configured to store the target underlying chain file in the underlying chain database.

[0213] In an embodiment of the present application, based on the foregoing scheme, the processing unit 1130 is further configured to perform filling processing on the preset underlying chain template based on the target type information and the target version information to obtain the filled underlying chain template; and if the filled underlying chain template is verified successfully, encapsulate the filled underlying chain template to obtain the target underlying chain file.

[0214] In an embodiment of the present application, based on the foregoing scheme, the processing unit 1130 is further configured to set the publishing state of the target underlying chain file to the published state; determine the target database table matching the target type information from the underlying chain database; and import the target underlying chain file into the target database table.

[0215] In an embodiment of the present application, based on the foregoing scheme, the processing unit 1130 is further configured to customize and modify the target underlying chain file based on the customization requirement information to obtain a customized underlying chain file; and encapsulate the customized underlying chain file to obtain the blockchain delivery file.

[0216] In an embodiment of the present application, based on the foregoing scheme, the processing unit 1130 is further configured to, if it is detected that the target base chain file includes customization content matching the customization requirement information of other blockchains, delete the customization content from the target base chain file to obtain an updated base chain file; and customize and modify the updated base chain file based on the customization requirement information to obtain a customized base chain file.

[0217] In an embodiment of the present application, based on the foregoing scheme, the processing unit 1130 is further configured to, if the number of customized base chain files is one, package the customized base chain file to obtain a blockchain delivery file; and if the number of customized base chain files is more than one, perform merging processing on the plurality of customized base chain files to obtain a merged base chain file, and package the merged base chain file to obtain a blockchain delivery file.

[0218] It should be noted that the apparatus provided in the foregoing embodiments and the method provided in the foregoing embodiments belong to the same concept, and the specific manner in which each module and unit performs operations has been described in detail in the method embodiments.

[0219] Embodiments of the present application also provide a blockchain-based data processing device, including: one or more processors; a memory for storing one or more programs, when the one or more programs are executed by the one or more processors, the electronic device implements the foregoing blockchain-based data processing method.

[0220] Figure 12 FIG. 1 is a structural schematic diagram of a computer system suitable for implementing the blockchain-based data processing device according to an embodiment of the present application.

[0221] It should be noted that, Figure 12 The computer system 1200 of the electronic device shown is only an example and should not impose any limitations on the functions and use range of the embodiments of the present application.

[0222] As Figure 12As shown, the computer system 1200 includes a central processing unit (CPU) 1201 which can execute various appropriate actions and processes in accordance with programs stored in a read-only memory (ROM) 1202 or loaded from the storage section 1208 into a random access memory (RAM) 1203, such as executing the methods in the above-described embodiments. Various programs and data required for system operation are also stored in the RAM 1203. The CPU 1201, the ROM 1202, and the RAM 1203 are connected to each other through a bus 1204. An input / output (I / O) interface 1205 is also connected to the bus 1204.

[0223] Connected to the I / O interface 1205 are an input section 1206 including a keyboard, a mouse, etc.; an output section 1207 including a display such as a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and a speaker, etc.; a storage section 1208 including a hard disk, etc.; and a communication section 1209 including a network interface card such as a LAN (Local Area Network) card, a modem, etc. The communication section 1209 performs communication processing via a network such as the Internet. A drive 1210 is also connected to the I / O interface 1205 as necessary. A removable recording medium 1211 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc. is attached to the drive 1210 as necessary, so that a computer program read therefrom is installed into the storage section 1208 as necessary.

[0224] In particular, according to embodiments of the present application, the processes described above with reference to the flowcharts can be implemented as a computer software program. For example, embodiments of the present application include a computer program product comprising a computer program carried on a computer readable medium, the computer program containing a computer program for executing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via the communication section 1209, and / or installed from the removable recording medium 1211. When the computer program is executed by the central processing unit (CPU) 1201, various functions defined in the systems of the present application are executed.

[0225] It should be noted that the computer-readable medium in the embodiments of the present application can be a computer-readable signal medium or a computer-readable storage medium or any combination thereof. The computer-readable medium may, for example, be an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or apparatus, or any combination thereof. More specific examples of the computer-readable medium can include, but are not limited to, an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM), a flash memory, an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination thereof. In this application, the computer-readable medium can be any tangible medium that contains or stores a program that can be used by or in connection with an instruction execution system, apparatus or device. In this application, the computer-readable signal medium can include a data signal that propagates in a baseband or as part of a carrier wave, in which the computer-readable computer program is carried. Such a propagated data signal can take many forms, including but not limited to an electromagnetic signal, an optical signal, or any suitable combination thereof. The computer-readable signal medium can also be any computer-readable medium other than the computer-readable storage medium that can transmit, propagate or transport a program for use by or in connection with an instruction execution system, apparatus or device. The computer program contained in the computer-readable medium can be transmitted in any suitable medium, including but not limited to wireless, wired, optical, etc., or any suitable combination thereof.

[0226] The flowcharts and block diagrams in the drawings illustrate the possible implementation architectures, functions and operations of the systems, methods and computer program products according to various embodiments of the present application. In the flowcharts or block diagrams, each block can represent a module, a program segment or a part of code containing one or more executable instructions for implementing the specified logical functions. It should also be noted that in some alternative implementations, the functions noted in the blocks can occur in a different order than that noted in the drawings. For example, two blocks that are shown in succession can actually be executed substantially in parallel, and they can also be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams or flowcharts, and the combination of blocks in the block diagrams or flowcharts, can be implemented by a dedicated hardware-based system that performs the specified functions or operations, or can be implemented by a combination of special-purpose hardware and computer instructions.

[0227] The units described in the embodiments of the present application can be implemented in the form of software, or can be implemented in the form of hardware, and the described units can also be arranged in a processor. In some cases, the names of the units do not constitute a limitation on the units themselves.

[0228] Another aspect of the present application also provides a computer readable medium having a computer program stored thereon, the computer program being executed by a processor to implement the foregoing blockchain-based data processing method. The computer readable medium can be included in the electronic device described in the foregoing embodiments, or can exist separately and not be assembled into the electronic device.

[0229] Another aspect of the present application also provides a computer program product or computer program, the computer program product or computer program comprising computer instructions stored in a computer readable medium. The processor of the computer device reads the computer instructions from the computer readable medium, and the processor executes the computer instructions to enable the computer device to execute the blockchain-based data processing method provided in the foregoing embodiments.

[0230] The above is only a preferred exemplary embodiment of the present application, and is not intended to limit the implementation of the present application. Those skilled in the art can easily make corresponding modifications or changes according to the main concept and spirit of the present application, and the protection scope of the present application should be subject to the protection scope required by the claims.

Claims

1. A data processing method based on blockchain, characterized in that, include: Obtain a generation request for a blockchain delivery file used to build a blockchain. The generation request is used to indicate the attribute information of the target underlying chain file required to generate the blockchain delivery file, and the generation request includes customized requirement information for building the blockchain. Extract the target bottom chain file that matches the attribute information from multiple bottom chain files contained in the bottom chain database; Based on the customized requirements information, the target underlying chain file is customized and modified to generate the blockchain delivery file.

2. The method according to claim 1, characterized in that, After obtaining the request to generate the blockchain delivery file used to build the blockchain, the method further includes: Based on the generation request, generate the blockchain functional information corresponding to the blockchain delivery document; Determine the target type and target version information of the underlying chain file required to construct the blockchain functional information; The target type information and target version information are merged to obtain the attribute information corresponding to the target bottom link file.

3. The method according to claim 1, characterized in that, The attribute information includes target type information and target version information; the step of extracting the target bottom chain file that matches the attribute information from multiple bottom chain files contained in the bottom chain database includes: If a target database table matching the target type information is obtained from the bottom chain database, then the version information of each bottom chain file included in the target database table is detected; If a bottom link file whose version information matches the target version information is detected in the target database table, then the detected bottom link file is identified as the target bottom link file.

4. The method according to claim 1, characterized in that, The attribute information includes target type information and target version information; after obtaining the generation request for the blockchain delivery file used to build the blockchain, the method further includes: If no target bottom chain file matching the attribute information is extracted from the multiple bottom chain files contained in the bottom chain database, the target bottom chain file is generated based on the target type information and the target version information. The target bottom chain file is stored in the bottom chain database.

5. The method according to claim 4, characterized in that, The process of generating the target base link file based on the target type information and the target version information includes: Based on the target type information and the target version information, the preset bottom chain template is filled to obtain the filled bottom chain template. If the filled bottom chain template is successfully verified, the filled bottom chain template is then encapsulated to obtain the target bottom chain file.

6. The method according to claim 4, characterized in that, The step of storing the target bottom chain file into the bottom chain database includes: Set the publication status of the target bottom chain file to published; Determine the target database table that matches the target type information from the bottom chain database; Import the target bottom chain file into the target database table.

7. The method according to any one of claims 1 to 6, characterized in that, The process of customizing the target bottom-chain file based on the customized requirements information to generate the blockchain delivery file includes: Based on the customized requirements information, the target bottom chain file is modified to obtain a customized bottom chain file; The customized bottom chain file is encapsulated to obtain the blockchain delivery file.

8. The method according to claim 7, characterized in that, The process of customizing the target bottom chain file based on the customized requirements information to obtain a customized bottom chain file includes: If the target bottom chain file is detected to contain customized content that matches the customized requirements of other blockchains, then the customized content is deleted from the target bottom chain file to obtain an updated bottom chain file; Based on the customized requirements information, the updated bottom link file is modified to obtain a customized bottom link file.

9. The method according to claim 7, characterized in that, The process of encapsulating the customized base chain file to obtain the blockchain delivery file includes: If the number of the customized bottom chain files is one, then the customized bottom chain files are encapsulated to obtain the blockchain delivery file; If there are multiple customized bottom chain files, the multiple customized bottom chain files are merged to obtain a merged bottom chain file, and the merged bottom chain file is encapsulated to obtain the blockchain delivery file.

10. A data processing device based on blockchain, characterized in that, include: The acquisition unit is used to acquire a generation request for a blockchain delivery file used to build a blockchain. The generation request is used to indicate the attribute information of the target bottom chain file required to generate the blockchain delivery file, and the generation request includes customized requirement information for building the blockchain. An extraction unit is used to extract a target bottom chain file that matches the attribute information from multiple bottom chain files contained in the bottom chain database; The processing unit is used to customize the target bottom chain file based on the customized requirement information and generate the blockchain delivery file.

11. A data processing device based on blockchain, characterized in that, include: Memory, which stores computer-readable instructions; A processor reads computer-readable instructions stored in memory to perform the method of any one of claims 1 to 9.

12. A computer-readable storage medium, characterized in that, It stores computer-readable instructions that, when executed by the computer's processor, cause the computer to perform the method of any one of claims 1 to 9.