Blockchain-based data processing method and apparatus, computer device, and medium

Abstract

The application discloses a blockchain-based data processing method and device, computer equipment and a medium. The method comprises the following steps: displaying a first service interface of a blockchain system; the blockchain system comprises N system nodes which have been accessed; N is a positive integer; selecting M system nodes from the N system nodes on the first service interface, and obtaining node configuration information of the M system nodes; M is a positive integer which is less than or equal to N; and constructing a business blockchain to which the M system nodes belong according to the node configuration information. The application can improve the efficiency of constructing the business blockchain.

Description

Technical Field

[0001] This application relates to the field of computer technology, and in particular to a data processing method, apparatus, computer equipment, and medium based on blockchain. Background Technology

[0002] With the continuous development of computer networks, blockchain technology has become increasingly mature. Blockchain is a novel application model of computer technologies such as distributed data storage, peer-to-peer transmission, consensus mechanisms, and encryption algorithms.

[0003] In existing technologies, blockchains are typically built using open-source blockchain platforms. Specifically, users can obtain basic blockchain building code from these platforms and then modify it to construct the blockchain. However, existing technologies require modifying the code within the open-source blockchain platform, which is extremely difficult and results in low efficiency in blockchain construction. Summary of the Invention

[0004] This application provides a blockchain-based data processing method, apparatus, computer equipment, and medium that can improve the efficiency of building business blockchains.

[0005] This application provides a blockchain-based data processing method, which includes:

[0006] Displays the first service interface of the blockchain system; the blockchain system includes N system nodes that have been connected; N is a positive integer;

[0007] On the first service interface, select M system nodes from N system nodes and obtain the node configuration information for the M system nodes; M is a positive integer less than or equal to N;

[0008] Construct a business blockchain comprising M system nodes based on node configuration information.

[0009] This application provides a blockchain-based data processing method, which includes:

[0010] Send service information of the blockchain system to the terminal device so that the terminal device can display the first service interface of the blockchain system based on the service information; the blockchain system includes N system nodes that have been connected; N is a positive integer;

[0011] The terminal device receives M system nodes and their configuration information; the M system nodes are selected by the terminal device from N system nodes on the first service interface; M is a positive integer less than or equal to N.

[0012] Based on the node configuration information, construct a business blockchain belonging to M system nodes and run the constructed business blockchain.

[0013] This application provides a blockchain-based data processing device, which includes:

[0014] The page display module is used to display the first service interface of the blockchain system; the blockchain system includes N system nodes that have been connected; N is a positive integer;

[0015] The node selection module is used to select M system nodes from N system nodes on the first service interface and obtain node configuration information for the M system nodes; M is a positive integer less than or equal to N.

[0016] The blockchain building module is used to construct a business blockchain belonging to M system nodes according to the node configuration information.

[0017] Optionally, the blockchain system includes the constructed business consortium blockchain;

[0018] The page display module displays the primary service interface of the blockchain system in the following ways:

[0019] Display the second service interface of the blockchain system and obtain the consortium blockchain identification information of the business consortium blockchain entered in the second service interface;

[0020] The system nodes included in the business consortium chain among N system nodes are determined based on the consortium chain identification information;

[0021] The first service interface is displayed based on the node identification information of the system nodes included in the business consortium chain;

[0022] The constructed business blockchain is a sub-chain of the business consortium blockchain.

[0023] Optionally, the node selection module may obtain node configuration information for M system nodes in the following ways:

[0024] Obtain the shared data type for sharing data with the business blockchain on the first service interface;

[0025] Retrieves Z data fields from a shared data type; Z is a positive integer.

[0026] Retrieve node configuration information based on Z data fields.

[0027] Optionally, the node selection module may obtain node configuration information based on Z data fields in the following ways:

[0028] On the first service interface, obtain the data uplink format of each of the Z data fields and obtain the field combination strategy corresponding to the Z data fields;

[0029] The data uplink format and field combination strategy for each data field are defined as node configuration information.

[0030] Optionally, the above-mentioned device further includes:

[0031] The query field acquisition module is used to display the third service interface of the blockchain system and acquire the business query fields for the business blockchain from the third service interface.

[0032] The data query module is used to query business data associated with business query fields in the business blockchain;

[0033] The data display module is used to display the business data associated with the business query fields on the third service interface.

[0034] Optionally, the above-mentioned device further includes:

[0035] The on-chain data acquisition module is used to display the fourth service interface of the blockchain system, acquire target business data in the fourth service interface, and import the target business data into the business blockchain.

[0036] The data export module is used to export the abnormal import data of the target business data from the business blockchain if the target business data is detected to be in an abnormal import state in the business blockchain.

[0037] The re-import module is used to re-import target business data into the business blockchain based on abnormal import data.

[0038] This application provides a blockchain-based data processing device, which includes:

[0039] The service information sending module is used to send service information of the blockchain system to the terminal device, so that the terminal device can display the first service interface of the blockchain system according to the service information; the blockchain system includes N system nodes that have been connected; N is a positive integer;

[0040] The configuration information receiving module is used to receive the M system nodes and their configuration information returned by the terminal device; the M system nodes are selected by the terminal device from N system nodes on the first service interface; M is a positive integer less than or equal to N;

[0041] The blockchain operation module is used to construct a business blockchain belonging to M system nodes based on node configuration information, and to run the constructed business blockchain.

[0042] Optionally, the blockchain system includes the constructed business consortium blockchain;

[0043] The service information sending module sends service information of the blockchain system to terminal devices in the following ways:

[0044] Obtain the consortium blockchain identifier information of the business consortium blockchain sent by the terminal device; the consortium blockchain identifier information is obtained by the terminal device on the second service interface of the blockchain system;

[0045] Based on the consortium blockchain identification information, determine the system nodes included in the business consortium blockchain among N system nodes, and obtain the node identification information of the system nodes included in the business consortium blockchain;

[0046] Service information is generated based on node identification information and sent to terminal devices.

[0047] Optionally, the node configuration information includes the data on-chain format of each of the Z data fields and the field combination strategy of the Z data fields; the Z data fields are the data fields contained in the data of the target data type; the target data type is a shared data type for data sharing with the business blockchain; Z is a positive integer;

[0048] The blockchain runtime module constructs a business blockchain comprising M system nodes based on node configuration information in the following ways:

[0049] Based on the data on-chain format of each data field in the node configuration information and the field combination strategy of the Z data fields, a data on-chain contract is generated;

[0050] Deploy a data on-chain contract on each of the M system nodes to obtain the constructed business blockchain.

[0051] Optionally, the blockchain runtime module can deploy data-on-chain contracts on each of the M system nodes to obtain the constructed business blockchain in the following ways:

[0052] Deploy a data on-chain contract on each system node to obtain the initial business blockchain;

[0053] Create a business access channel for the initial business blockchain, and define the initial business blockchain with the business access channel as the business blockchain.

[0054] Among them, M system nodes are used to call the data on-chain contract in the business blockchain through the business access channel.

[0055] Optionally, the above device is applied to a target system node among N system nodes; the target system node belongs to M system nodes; and each of the M system nodes has an associated business system.

[0056] The above-mentioned device also includes:

[0057] The first system determination module is used to determine the business systems associated with the target system node as the target business systems;

[0058] The first data acquisition module is used to acquire L pieces of data to be uploaded to the blockchain from the target business system based on the contract interface between the target business system and the business sub-chain; the L pieces of data to be uploaded to the blockchain have the same data format type, and L is a positive integer;

[0059] The template-on-chain module is used to obtain data on-chain templates for L data items to be uploaded to the blockchain, and to call the data on-chain contract through the contract interface to import the L data items to be uploaded to the business blockchain in batches using the data on-chain templates.

[0060] Optionally, the above device is applied to a target system node among N system nodes; the target system node belongs to M system nodes; and each of the M system nodes has an associated business system.

[0061] The above-mentioned device also includes:

[0062] The second system determination module is used to determine the business systems associated with the target system node as the target business systems;

[0063] The second data acquisition module is used to acquire incremental data from the target business system based on the contract interface between the target business system and the business blockchain.

[0064] The interface on-chain module is used to obtain the data import interface for incremental data, and to call the data on-chain contract through the contract interface to import the incremental data into the business blockchain using the data import interface.

[0065] This application provides a computer device, including a memory and a processor. The memory stores a computer program, and when the computer program is executed by the processor, the processor performs the method of this application.

[0066] This application provides a computer-readable storage medium storing a computer program, the computer program including program instructions that, when executed by a processor, cause the processor to perform the method described above.

[0067] According to one aspect of this application, a computer program product or computer program is provided, comprising computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the methods provided in the various alternative embodiments described above.

[0068] This application can display a first service interface of a blockchain system; the blockchain system includes N system nodes that have been connected; N is a positive integer; on the first service interface, M system nodes are selected from the N system nodes, and node configuration information for the M system nodes is obtained; M is a positive integer less than or equal to N; the business blockchain to which the M system nodes belong is constructed according to the node configuration information. Therefore, the method proposed in this application can obtain M system nodes and their node configuration information on the first service interface, and then directly and quickly construct the business blockchain to which the M system nodes belong using this node configuration information, thereby reducing the difficulty of constructing the business blockchain and improving its construction efficiency. Attached Figure Description

[0069] To more clearly illustrate the technical solutions in this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0070] Figure 1 is a network architecture diagram of a blockchain system provided in an embodiment of this application;

[0071] Figure 2 is a schematic diagram of the structure of a blockchain system provided in this application;

[0072] Figure 3 is a flowchart illustrating a blockchain-based data processing method provided in this application;

[0073] Figures 4a-4d are schematic diagrams of a service interface for creating a blockchain provided in this application;

[0074] Figure 5 is a schematic diagram of a data query service interface provided in this application;

[0075] Figure 6 is a schematic diagram of the interface of a contract query service provided in this application;

[0076] Figure 7 is a flowchart illustrating a blockchain-based data processing method provided in this application;

[0077] Figure 8 is a schematic diagram of the service interface of a contract publishing interface provided in this application;

[0078] Figure 9 is a schematic diagram of the service interface for contract interface authorization provided in this application;

[0079] Figure 10 is a schematic diagram of the interface of a data template import service provided in this application;

[0080] Figure 11 is a schematic diagram of the interface of a data template import service provided in this application;

[0081] Figure 12 is a flowchart illustrating a method for creating a consortium blockchain provided in this application;

[0082] Figure 13 is a flowchart illustrating a data uploading method provided in this application;

[0083] Figure 14 is a flowchart illustrating a data usage method provided in this application;

[0084] Figure 15 is a schematic diagram of the structure of a blockchain-based data processing device provided in this application;

[0085] Figure 16 is a schematic diagram of the structure of a blockchain-based data processing device provided in this application;

[0086] Figure 17 is a schematic diagram of the structure of a computer device provided in this application. Detailed Implementation

[0087] The technical solutions of this application will now be clearly and completely described with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0088] This application relates to blockchain-related technologies. Blockchain is a novel application model of computer technologies such as distributed data storage, peer-to-peer transmission, consensus mechanisms, and cryptographic algorithms. Essentially, a blockchain is a decentralized database, a chain of data blocks linked using cryptographic methods. Each data block contains information about a batch of network transactions, used to verify the validity of the information (anti-counterfeiting) and generate the next block. A blockchain can include a blockchain underlying platform, a platform product service layer, and an application service layer. A blockchain consists of a series of blocks sequentially generated in chronological order. Once a new block is added to the blockchain, it cannot be removed. Each block records the data submitted by nodes in the blockchain system. This application enables the rapid construction of a business blockchain on a blockchain platform, and allows for convenient operation of business-related transactions within the blockchain through the blockchain platform.

[0089] Furthermore, this application also relates to smart contracts in blockchain. A smart contract is contract code that executes automatically on the blockchain's central hub, typically including the contract owner, contract objects, contract terms, contract algorithm, and contract triggering conditions. In blockchain applications for electronic certificates, after data sharing rules are converted into smart contracts and deployed on the blockchain, regular sharing terms and breach of contract handling terms can be automatically fulfilled. The execution process is fully recorded by the blockchain, and its execution status can be viewed and audited at any time, thus providing a fair, just, and transparent contract execution environment. In this application, various smart contracts can be created on the business blockchain according to business needs to implement corresponding business operations.

[0090] This application also relates to cloud technology. Cloud technology refers to a managed technology that unifies a series of resources such as hardware, software, and networks within a wide area network or local area network to realize the computing, storage, processing, and sharing of data.

[0091] Cloud technology is a collective term for network technology, information technology, integration technology, management platform technology, and application technology applied to the cloud computing business model. It can form resource pools, providing flexible and convenient on-demand access. Cloud computing technology will become a crucial support. Backend services of technical network systems require substantial computing and storage resources, such as video websites, image websites, and many portal websites. With the rapid development and application of the internet industry, every item may have its own identification mark in the future, requiring transmission to backend systems for logical processing. Data at different levels will be processed separately, and various industry data will all require robust system support, which can only be achieved through cloud computing.

[0092] The cloud technology involved in this application mainly refers to the data interaction between terminal devices and blockchain nodes through the "cloud". Furthermore, the blockchain nodes in this application can be composed of cloud devices (such as cloud servers).

[0093] Please refer to Figure 1, which is a network architecture diagram of a blockchain system provided in an embodiment of this application. As shown in Figure 1, the business systems may include the Public Security Bureau system of the Public Security Bureau, the Human Resources and Social Security Bureau system of the Human Resources and Social Security Bureau, the Market Supervision Bureau system of the Market Supervision Bureau, and the Finance Bureau system of the Finance Bureau, etc., in box 100a. These business systems are the original systems of their respective bureaus (such as the Human Resources and Social Security Bureau and the Public Security Bureau), and are not part of the blockchain. Therefore, the business systems in box 100a have business interactions, and thus, a business blockchain corresponding to the business systems in box 100a can be constructed. Please refer to the following description.

[0094] First, corresponding blockchain nodes can be configured for each business system within the blockchain system. These blockchain nodes corresponding to each business system can be referred to as system nodes for that business system. As shown in Figure 1, the blockchain system can be configured with system nodes such as 101a for the Public Security Bureau system, 102a for the Human Resources and Social Security Bureau system, 103a for the Market Supervision Bureau system, and 104a for the Finance Bureau system. These system nodes 101a, 102a, 103a, and 104a can constitute a business consortium chain within the blockchain system.

[0095] In a blockchain system, each system node can be an independent physical server, a server cluster composed of multiple physical servers, or a distributed system. It can also be a cloud server providing basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, CDN, and big data and artificial intelligence platforms. Terminal devices can be smart terminals such as smartphones, tablets, laptops, desktop computers, and smart TVs.

[0096] Furthermore, one or more sub-chains (which can be called business sub-chains) can be created within the aforementioned business consortium blockchain. For example, a business sub-chain can be created between system nodes 101a of the Public Security Bureau, 102a of the Human Resources and Social Security Bureau, and 103a of the Market Supervision Bureau. This business sub-chain, including system nodes 101a, 102a, and 103a, can be called business sub-chain y1. Similarly, a business sub-chain can be created between system nodes 102a of the Human Resources and Social Security Bureau, 103a of the Market Supervision Bureau, and 104a of the Finance Bureau. This business sub-chain, including system nodes 102a, 103a, and 104a, can be called business sub-chain y2. The aforementioned business consortium blockchain can be understood as the largest business sub-chain.

[0097] Furthermore, business access channels can be created separately for each blockchain (including business consortium chains and business sub-chains). As shown in Figure 1, the business access channel of the business consortium chain can be a general channel, which is joined by all system nodes in the business consortium chain; the business access channel of business sub-chain y1 can be an ID card channel, which is joined by system nodes 101a, 102a, and 103a; the business access channel of business sub-chain y2 can be a social security card channel, which is joined by system nodes 102a, 103a, and 104a.

[0098] Each blockchain can also deploy smart contracts. For example, smart contracts deployed on the business consortium blockchain may include a certificate catalog contract (for generating a catalog of uploaded certificates) and a batch on-chain contract (for batch on-chaining of data); smart contracts deployed on the business sub-chain y1 may include an ID card contract (for executing ID card-related business); and smart contracts deployed on the business sub-chain y1 may include a social security card contract (for executing social security card-related business). Each system node can call the corresponding smart contracts on the blockchain through the business access channel it joins.

[0099] Furthermore, the business system and the blockchain system can communicate encryptedly, for example, through an encrypted interface, enabling the import of data from the business system onto the blockchain. In addition, the blockchain system of this application includes a blockchain platform that can be hosted on a terminal device, thus supporting users to perform relevant business operations on the blockchain within the blockchain system on the terminal device's blockchain platform, such as creating smart contracts, uploading data to the blockchain, and querying on-chain data. The blockchain platform and the blockchain in the blockchain system's backend can interact via an API (Application Programming Interface).

[0100] Please also refer to Figure 2, which is a schematic diagram of the structure of a blockchain system provided in this application. As shown in Figure 2, the blockchain system 100b may include a blockchain platform 101b and a blockchain backend 102b. The blockchain platform 101b can be understood as the front end of the blockchain system. This blockchain platform can be hosted in a terminal device, supporting users to issue relevant business instructions to the blockchain backend on the blockchain platform of the terminal device. The blockchain backend can then provide technical support to the blockchain platform, enabling business operations related to the business instructions issued by the user through the blockchain platform.

[0101] The method provided in this application allows for the construction of a business consortium blockchain for multiple (at least two) business entities (organizations to which business systems belong, such as human resources and social security bureaus, public security bureaus, and government data bureaus) with business dealings. This enables data from the business systems of these multiple entities to be imported into the consortium blockchain (including into the business sub-chains within the consortium blockchain). Therefore, these multiple business entities can quickly access data from each other's business systems within the consortium blockchain, without needing to access other entities' data separately, thus improving the efficiency of data exchange between multiple business systems. Furthermore, using a blockchain platform to construct the blockchain (including the business consortium blockchain and its business sub-chains) and apply the constructed blockchain reduces the complexity of these business operations, thereby improving business processing efficiency.

[0102] Please refer to Figure 3, which is a flowchart illustrating a blockchain-based data processing method provided in this application. The executing entity in this embodiment can be a single computer device or a cluster of multiple computer devices. The computer device can be a server or a terminal device. Therefore, the executing entity in this embodiment can be a server, a terminal device, or a combination of both. Here, we will use a terminal device as an example to illustrate the method. As shown in Figure 3, the method may include:

[0103] Step S101: Display the first service interface of the blockchain system; the blockchain system includes N system nodes that have been connected; N is a positive integer;

[0104] In this application, the blockchain system may include a blockchain platform, which can be understood as the front-end client of the blockchain system. The blockchain platform can run on a terminal device. Therefore, users can quickly perform operations such as blockchain construction, data upload, and data query through the blockchain platform running on the terminal device. Please refer to the following description.

[0105] The service interface of the blockchain system is the interface on the blockchain platform in the terminal device. The operations that the terminal device responds to and executes in the following process can all be implemented through the blockchain platform. Therefore, some processes in the following description can omit the blockchain platform and be directly described by the corresponding operations performed by the terminal device. However, it is understood that the operations performed by the terminal device can be implemented through the blockchain platform.

[0106] A blockchain system can pre-create N blockchain nodes, referred to as system nodes, where N is a positive integer, and its specific value depends on the actual application scenario. A business blockchain can be constructed using these N blockchain nodes. It's important to note that the constructed business blockchain can be a business consortium blockchain (or simply a consortium blockchain) built within the blockchain system, or, if a business consortium blockchain already exists, the constructed business blockchain can be a sub-chain within that consortium blockchain. The number of system nodes in this sub-chain is less than or equal to the number of system nodes in the consortium blockchain; the consortium blockchain can be considered the largest sub-chain.

[0107] In this context, it's understandable that when multiple (at least two) business systems interact with each other, a business blockchain can be built for these systems, but these systems themselves are not part of the constructed business blockchain. In this scenario, system nodes can be pre-created within the blockchain system for these multiple business systems; these system nodes can be the aforementioned N system nodes. A system node can consist of one or more computer devices.

[0108] For example, if there are business dealings between the Human Resources and Social Security Bureau, the Public Security Bureau, the Finance Bureau, and the Government Data Bureau, and it is necessary to build a business blockchain between them, then the above-mentioned N system nodes can include the system nodes corresponding to the Human Resources and Social Security Bureau, the Public Security Bureau, the Finance Bureau, and the Government Data Bureau.

[0109] The blockchain system described in this application can create three levels of administrator accounts, all of which can log in to the blockchain platform. These three levels of administrator accounts include a consortium administrator account, a chain administrator account, and a node administrator account. The consortium administrator account has the authority to build a business consortium blockchain, the chain administrator account has the authority to manage business sub-chains within the business consortium blockchain, and the node administrator account has the authority to manage its assigned system nodes. Each system node can have its own node administrator account, and the number of node administrator accounts can be one or multiple.

[0110] Each administrator account can create more administrator accounts, and the administrator account that created the administrator accounts can manage the administrator accounts it created. For example, the initial node administrator account created in the blockchain system can create more node administrator accounts, and the initial node administrator account can manage the node administrator accounts it created.

[0111] It's important to note that business subchains within a consortium blockchain are typically created by the node administrator account of a system node. The node administrator account that creates the business subchain becomes the chain administrator account for that subchain. Alternatively, business subchains can also be created by a consortium administrator account; in this case, the consortium administrator account also becomes the chain administrator account for the created business subchain. The consortium administrator account is the highest-level administrator account, and its permissions can be configured according to the specific application scenario. For example, the consortium administrator account can also have permissions to manage business subchains and system nodes. The consortium administrator account can also belong to the administrator account of a system node within the blockchain system.

[0112] If the business blockchain to be created is a business consortium blockchain, the administrator account logged in on the terminal device can be a consortium administrator account. The business consortium blockchain can be created through the logged-in consortium administrator account. In this case, the first service interface can be the service interface in the blockchain platform where the consortium administrator account is logged in.

[0113] If the business blockchain to be created is a sub-chain of a business consortium blockchain that has already been created, the administrator account logged in on the terminal device can be the node administrator account of the system node or the consortium administrator account. The business sub-chain can be created through the logged-in node administrator account or consortium administrator account. At this time, the first service interface can be the service interface of the blockchain platform where the node administrator account or consortium administrator account is logged in.

[0114] Optionally, the blockchain platform may also include a trigger control for creating a business blockchain. The terminal device can respond to the user's trigger operation on the trigger control (such as a click operation or a swipe operation) and display a first service interface, which is the interface that guides the user to create a business blockchain.

[0115] Step S102: Select M system nodes from N system nodes on the first service interface and obtain node configuration information for the M system nodes; M is a positive integer less than or equal to N.

[0116] In this application, the terminal device can select M system nodes from N system nodes on the first service interface in the following ways: each system node has node identification information, which may include the node name or node identifier (node ​​ID) of the system node. Therefore, if the business blockchain to be created is a business consortium blockchain, the terminal device can obtain the node identification information entered by the user on the first service interface and use the system node to which the node identification information entered by the user on the first service interface belongs as the M system nodes selected from the N system nodes. Alternatively, the first service interface may also include the node identification information of the N system nodes. The node identification information of the N system nodes on the first service interface may have a control function. Therefore, the terminal device can respond to the user's selection operation of the N node identification information on the first service interface and use the system node to which the node identification information selected by the user belongs as the selected M system nodes.

[0117] Similarly, if the business blockchain to be created is a business sub-chain in a business consortium chain, the terminal device can obtain the node identification information of the system nodes included in the business consortium chain entered by the user on the first service interface, and use the system node to which the node identification information entered by the user on the first service interface belongs as the M system nodes selected from N system nodes.

[0118] Alternatively, the first service interface may also display node identifier information of the system nodes included in the business consortium blockchain. The node identifier information displayed in the first service interface can be obtained by the terminal device displaying a second service interface before displaying the first service interface. This second service interface is used to obtain N system nodes. The aforementioned business consortium blockchain also has consortium blockchain identifier information, which can be the node name or node identifier (node ​​ID) of the business consortium blockchain. Therefore, the terminal device can obtain the consortium blockchain identifier entered by the user in the second service interface and obtain the corresponding business consortium blockchain through this identifier, thereby determining the system nodes included in the business consortium blockchain from the N system nodes. Therefore, the terminal device can also obtain the node identifier information of the system nodes included in the business consortium blockchain. The terminal device can display the first service interface based on the node identifier information of the system nodes included in the business consortium blockchain, and this first service interface includes the node identifier information of the system nodes included in the business consortium blockchain. The node identification information of the system nodes included in the business consortium chain can have a control function in the node identification information in the first service interface. Therefore, the terminal device can respond to the user's selection operation on the node identification information in the first service interface and take the system node to which the node identification information selected by the user belongs as the selected M system nodes. In this case, the M system nodes belong to the business consortium chain.

[0119] Since the administrator account logged into the blockchain platform of the terminal device can belong to the administrator account of a certain system node in the blockchain system, the data obtained by the terminal device (such as) can all be obtained through the system node to which the logged-in administrator account belongs.

[0120] The M system nodes selected above are the system nodes used to build the business blockchain, where M is a positive integer less than or equal to N.

[0121] Furthermore, the terminal device can not only obtain the M system nodes from the first service interface, but also the name of the business blockchain to be created, its application scenario, and related descriptive information entered by the user on the first service interface. This information, including the business blockchain name, application scenario, and descriptive information entered by the user on the first service interface, can be used as configuration information for the business blockchain to be created. For the M system nodes of the business blockchain, this configuration information constitutes the node configuration information for those M system nodes.

[0122] Furthermore, since all business transactions within the constructed business blockchain can be executed via smart contracts, the node configuration information for the M system nodes can also include information related to creating smart contracts. Please see the following description:

[0123] The terminal device can also obtain the data type (which can be called the shared data type) that can be shared with the business blockchain to be created on the first service interface. This shared data type is the type of data to be imported into the business blockchain, and there can be one or more (at least two) shared data types. For example, if the business blockchain being constructed is a blockchain for storing electronic certificates, which may include ID cards, student ID cards, and passports, then the shared data types could include the types of ID cards, student ID cards, and passports, etc.

[0124] The terminal device can also obtain Z data fields included in the shared data type. The value of Z may be different for different shared data types. Z is a positive integer, and its value is determined according to the actual application scenario. For example, if the shared data type is an ID card, then the Z data fields may include a name field, a gender field, a date of birth field, and an address field, etc.

[0125] The terminal device can obtain node configuration information for M system nodes through these Z data fields. The first service interface also supports users setting the on-chain format (referred to as the data on-chain format) for each data field of the data to be uploaded to the blockchain. For example, the data on-chain format can include plaintext on-chain format, ciphertext on-chain format, and hash value on-chain format. Specifically, the first service interface can include options for setting the data on-chain format for each data field. The terminal device can determine the data on-chain format for each data field by selecting the options for each data field in the first service interface. Therefore, the terminal device can obtain the data on-chain format of each of the aforementioned Z data fields on the first service interface.

[0126] Furthermore, the terminal device can also obtain a field combination strategy for the Z data fields on the first service interface. This field combination strategy can include the combination order of the Z data fields and the layout information between the Z data fields (such as the layout position of each data field). It is understood that this field combination strategy can be set by the user on the first service interface.

[0127] Therefore, the terminal device can also use the field combination strategy for the Z data fields and the data uplink format of each of the Z data fields as node configuration information for the M system nodes.

[0128] Step S103: Construct the business blockchain to which M system nodes belong according to the node configuration information;

[0129] In this application, the terminal device can construct a business blockchain belonging to M system nodes according to the node configuration information. This business blockchain can be a newly established business consortium blockchain, or it can be a business sub-chain of an existing business consortium blockchain in the blockchain system. The blockchain name, application scenario, and related description information of this business blockchain are the same as the name, application scenario, and related description information obtained through the first service interface mentioned above in the node configuration information.

[0130] Furthermore, by using the field combination strategy for the aforementioned Z data fields in the node configuration information, as well as the data on-chain format for each of the Z data fields, a smart contract for on-chaining data of shared data types can be created. This smart contract can be called a data on-chain contract. Therefore, this data on-chain contract can be configured (i.e., deployed) on each of the M system nodes to obtain the aforementioned business blockchain.

[0131] It is understandable that the data on-chain contract mentioned here is just one example. In reality, the node configuration information may not necessarily include the field combination strategy for the Z data fields and the data on-chain format for each of the Z data fields. The node configuration information may also include information related to creating smart contracts for any type of business. Therefore, by using the information related to creating smart contracts for any type of business in the node configuration information, smart contracts of any type of business can be configured for M system nodes. The type and number of these smart contracts are determined based on the actual application scenario and are not limited thereto.

[0132] Furthermore, not only can smart contracts be configured for each system node in the business blockchain when it is created, but after the business blockchain is created, terminal devices can also configure new smart contracts for each system node in the business blockchain based on some configuration operations performed by the user on the blockchain platform.

[0133] Within a business consortium blockchain, multiple business sub-chains can be created based on business needs. Different sub-chains may or may not share the same system nodes. Data within a sub-chain can typically only be uploaded, accessed, or viewed by the system nodes within that sub-chain, and data between different sub-chains can be isolated. The business consortium blockchain can be understood as a large group, within which multiple subgroups can be created; a sub-group can be considered a business sub-chain. Different sub-chains may handle different types of business. Therefore, when multiple system nodes have business interactions, a business consortium blockchain belonging to those system nodes can be established first. Subsequently, when some of these system nodes have other business needs, business sub-chains can be built for those specific system nodes within the business consortium blockchain.

[0134] For example, the system nodes in a business consortium blockchain can also be the system nodes corresponding to the various departments of an enterprise. Based on the different business needs of each department, business sub-chains can be established between the departments.

[0135] Please refer to Figures 4a-4d, which are schematic diagrams of a service interface for creating a blockchain provided in this application. As shown in Figure 4a, interface 100c can be the first service interface mentioned above, and the business blockchain created through interface 100c is a business consortium blockchain. Specifically, on interface 100c, the basic node configuration information for creating a business consortium blockchain (hereinafter referred to as consortium blockchain) can be obtained through step ①. This node configuration information may include the consortium type, consortium name, and consortium description, etc.

[0136] On interface 100c, step ② allows you to add members to the alliance. Adding members to the alliance here means selecting M system nodes from the N system nodes of the blockchain system to build a business alliance chain. These M system nodes are the members joining the alliance.

[0137] As shown in Figure 4b, interface 101c can also be the first service interface mentioned above. The business blockchain created through interface 101c is a business sub-chain in the business consortium blockchain. Specifically, on interface 101c, the basic node configuration information for creating the business sub-chain can be obtained through step ①. This node configuration information can include the blockchain network to which the business sub-chain belongs (such as which business consortium blockchain it belongs to), the business type, the sub-chain name, and the sub-chain description.

[0138] On interface 101c, node configuration can be performed through step ②, which specifies which system nodes (such as the M system nodes mentioned above) in the business consortium chain need to be added to the business sub-chain. It can be understood that the business sub-chain can contain some or all of the system nodes in the business consortium chain. If it includes all the system nodes in the business consortium chain, then the business sub-chain is the business consortium chain.

[0139] As shown in Figure 4c, interface 102c also belongs to the first service interface mentioned above. Interface 102c is actually the interface for step ③ of interface 101c. In interface 102c, the type of data to be shared in the business sub-chain (i.e., the shared data type mentioned above) can be obtained. Here, the shared data type is the construction permit type. Interface 102c can obtain multiple data fields of the construction permit (corresponding to the Z data fields mentioned above). These multiple data fields can include the document name, number, and construction unit data fields. Since the remark data field is not selected by "√", it is not included in these multiple data fields. As shown in interface 102c, the data uplink format can be set for these multiple data fields. Here, the data uplink format for the document name field is set to plaintext, the data uplink format for the number field is set to plaintext, and the data uplink format for the construction unit field is also set to plaintext. Plaintext means uplinking the data field using plaintext, i.e., uplinking the original data corresponding to the data field without encryption.

[0140] Furthermore, a key value can be defined in interface 102c. This key value contains the field combination order set by the user for the multiple data fields selected above. Here, the field combination order is as follows: the data field with the number, the data field with the certificate name, and the data field with the construction unit. This field combination order can serve as the aforementioned field combination strategy. Therefore, the data uplink format and field combination strategy of the multiple data fields obtained in interface 102c can also be used as node configuration information for system nodes.

[0141] Smart contracts (such as the data-on-chain contract mentioned above) can be created using the data on-chain format of these multiple data fields and the field combination strategy. The contract name of the smart contract can also be set in interface 102c.

[0142] As shown in Figure 4d, interface 103c is actually the interface for step ④ of interface 102c mentioned above. This interface displays the smart contracts created (such as those created in interface 102c). Interface 103c includes a "Install and Instantiate Contract" button, allowing users to select the smart contract to be installed and instantiated (i.e., the smart contract to be deployed and used) from among the created smart contracts. The terminal device can respond to the user's trigger operation on the "Install and Instantiate Contract" button, creating a business sub-chain (if this business sub-chain is a business consortium chain, it does not need to be created again here), and deploying the selected smart contract to be installed and instantiated on this business sub-chain, thus obtaining the final created business sub-chain.

[0143] After constructing the aforementioned business blockchain, each system node within the blockchain can import the data to be uploaded to the blockchain through the data upload contract, and manage the uploaded data through the created smart contracts. Subsequently, the blockchain platform can query the data uploaded to the business blockchain, and also query the contract execution status of business operations executed through smart contracts (such as data upload operations) within the business blockchain.

[0144] For example, the terminal device can also display a third service interface of the blockchain system. This third service interface can be used for data queries or contract execution status inquiries. The terminal device can obtain the business query fields entered by the user in this third service interface, which are the relevant fields of the data the user wants to query.

[0145] The business query field can be a field for querying data uploaded to the business blockchain, or it can be a field for querying the execution status of a contract. Smart contracts in the business blockchain can have custom or automatically set names; for example, the contract used to upload data to the blockchain can be named "Data Upload Contract." Furthermore, the ledger to which the uploaded data belongs can also have a corresponding ledger name; for example, the ledger to which an ID card belongs can be named "Resident ID Card." Therefore, users can use ledger name, smart contract name, time period, and participating parties (such as system nodes participating in data uploading) as business query fields on the blockchain platform to query the data indicated by the specified business query field uploaded to the business blockchain.

[0146] Furthermore, it also supports users to use relevant fields such as smart contract name, smart contract call status, system that called the smart contract (such as the business system corresponding to a certain system node), and data source as business query fields on the blockchain platform to query the execution status of smart contracts related to the business query field, such as the name of the executed smart contract, the time of execution of the smart contract, and the execution result of the smart contract (such as the result of execution failure or execution success).

[0147] Data retrieved from the business blockchain based on a business query field can be considered business data associated with that query field. This business data can be displayed on the third-party service interface for users to browse and view.

[0148] Please refer to Figure 5, which is a schematic diagram of a data query service interface provided in this application. As shown in Figure 5, interface 104c can be the aforementioned third service interface. Interface 104c is an interface that supports users in querying data on the business blockchain. Furthermore, the queried data can be from the production environment or the test environment, and users can choose which type of data to view (such as the type of production environment or the category of test environment).

[0149] Users can enter the ledger name (which can be understood as the name of data of a shared data type, such as an ID card), business system name, consortium name (i.e., the name of the consortium blockchain), and / or business sub-chain name as the business query fields in this interface 104c. Alternatively, the region selected by the user in interface 104c (such as Guangzhou, Shenzhen, and / or Tianhe District) can also be used as the business query field. Therefore, there can be one or more business query fields. The business query fields entered by the user in interface 104c can be used to filter the business data queried by the user. For example, the two business data items displayed in interface 104c include the business data of the ID card and the business license on the business blockchain.

[0150] Please refer to Figure 6, which is a schematic diagram of a contract query service interface provided in this application. As shown in Figure 6, interface 105c can be the aforementioned third service interface. Interface 105c is an interface that supports users in querying the execution status of smart contracts on the business blockchain. Furthermore, the smart contracts queried can be from the production environment or the test environment, and users can choose which type of smart contract (such as the type of production environment or the category of test environment) to view.

[0151] Users can enter information such as the contract name (i.e., the name of the smart contract), the calling organization (i.e., which business organization is calling the smart contract, such as the Human Resources and Social Security Bureau), the alliance name, and / or the business sub-chain name as the business query fields in interface 105c. By using the business query fields entered by the user in interface 105c, the execution status of the smart contract queried by the user can be filtered (such as the call status shown here). For example, the two smart contract call statuses displayed in interface 105c include the call status of the smart contract for ID cards (e.g., successful) and the call status of the smart contract for professional licenses (e.g., failed).

[0152] Furthermore, the terminal device can also display a fourth service interface of the blockchain system, which can be a service interface for uploading data to the blockchain. The terminal device can obtain the target business data entered by the user in this fourth service interface, which is the data that the user needs to import into the business blockchain. This target business data can be obtained by the user from the data stored on the terminal device, or it can be obtained from a certain business system.

[0153] Terminal devices can import target business data into the business blockchain within the blockchain platform. For example, the blockchain platform may include a data import control, allowing the terminal device to import the target business data based on user actions triggered by this control (such as clicks, voice control, or swipes). It can be understood that system nodes can be considered backend devices of the blockchain platform; therefore, the aforementioned business blockchain also belongs to the backend of the blockchain platform, and the administrator account logged into the blockchain platform can belong to a specific system node. Thus, when a terminal device imports target business data into the business blockchain through the blockchain platform, it is essentially requesting the corresponding system node in the backend to import the target business data into the business blockchain.

[0154] When importing target business data onto the business blockchain, the terminal device can also display the import status of the target business data onto the business blockchain on the fourth service interface. This import status can include an abnormal import status and a normal import status. An abnormal import status indicates that the target business data has not been successfully imported onto the business blockchain, possibly because only part of the target business data was imported or incorrect data was imported. Only a normal import status indicates that the target business data has been successfully imported onto the business blockchain.

[0155] Therefore, when a terminal device detects that the target business data is in an abnormal import state on the business blockchain, the terminal device can automatically export the abnormal import data of the target business data from the business blockchain, or the terminal device can respond to the user's abnormal data export operation and export the abnormal import data of the target business data from the business blockchain. This abnormal import data is the data imported into the business blockchain when the target business data was imported, but because the target business data is in an abnormal import state, it indicates that this abnormal import data is not the same as the target business data. This abnormal import data may be partial data of the target business data or erroneous data of the target business data (such as garbled data), etc.

[0156] After the terminal device exports the abnormally imported data from the business blockchain, it can retry importing the target business data into the business blockchain until the target business data is successfully imported into the business blockchain.

[0157] The aforementioned blockchain platform and node devices can interact via API (Application Programming Interface) services. The blockchain platform provided in this application can exist as an app (software) on the terminal device, or it can exist as a webpage on the terminal device. Therefore, it supports simple user operations (such as triggering controls) on the blockchain platform, enabling operations such as building a business blockchain, uploading data to the business blockchain, querying uploaded data, creating smart contracts, and querying the execution status of smart contracts. This reduces the difficulty for users to perform related operations on the business blockchain, eliminating the need for users to possess in-depth knowledge of the underlying blockchain technology or manipulate the blockchain's source code. Therefore, it improves the convenience of the business blockchain and the efficiency of performing related business operations on it. Furthermore, by constructing business blockchains corresponding to multiple business systems, it can also solve the compatibility issues between the terminal's operating system and the business systems. The business blockchain enables access to data from multiple business systems, improving the universality of data access.

[0158] This application can display a first service interface of a blockchain system; the blockchain system includes N system nodes that have been connected; N is a positive integer; on the first service interface, M system nodes are selected from the N system nodes, and node configuration information for the M system nodes is obtained; M is a positive integer less than or equal to N; the business blockchain to which the M system nodes belong is constructed according to the node configuration information. Therefore, the method proposed in this application can obtain M system nodes and their node configuration information on the first service interface, and then directly and quickly construct the business blockchain to which the M system nodes belong using this node configuration information, thereby reducing the difficulty of constructing the business blockchain and improving its construction efficiency.

[0159] Please refer to Figure 7, which is a flowchart illustrating a blockchain-based data processing method provided in this application. Here, we will use a server as the execution entity in this embodiment as an example for explanation. As shown in Figure 7, the method may include:

[0160] Step S201: Send service information of the blockchain system to the terminal device so that the terminal device displays the first service interface of the blockchain system according to the service information; the blockchain system includes N system nodes that have been connected; N is a positive integer;

[0161] The method described in this application embodiment is actually the same as the method described in the embodiment corresponding to FIG3 above, except that the embodiment corresponding to FIG3 above describes the front-end operation of the method, while this application embodiment describes the back-end implementation of the method. Therefore, it can be understood that the content described in the embodiment corresponding to FIG3 can be combined with the content described in this embodiment. Accordingly, the execution subject in this embodiment can be the system node to which the administrator account logged in in the blockchain platform of the embodiment corresponding to FIG3 belongs. Here, the execution subject in this embodiment can be referred to as a node device, which is the device that constitutes the system node to which the administrator account logged in in the blockchain platform belongs, such as one or more computer devices.

[0162] It is understood that when the terminal device in the embodiment corresponding to Figure 3 needs to display the first service interface (for example, when the terminal device obtains a display operation performed by the user on the first service interface), the terminal device can send a page display request for the first service interface to the node device. The node device can then send service information of the blockchain system to the terminal device based on this page display request. This service information may include the information to be displayed in the first service interface, such as text, icons, and controls, and may also include the layout information between these elements. Therefore, after obtaining this service information, the terminal device can render and display the first service interface based on it. This first service interface is used to select system nodes from the N system nodes of the blockchain system for constructing the business blockchain.

[0163] For example, if the business blockchain to be constructed is a business sub-chain in a business consortium blockchain, the node device can obtain the consortium blockchain identification information sent by the terminal device. This consortium blockchain identification information can be obtained by the terminal device on the aforementioned second service interface.

[0164] Therefore, the node device can determine the corresponding business consortium chain based on the consortium chain identifier, thereby identifying which of the aforementioned N system nodes are included in the business consortium chain. The node device can generate the aforementioned service information based on the node identifier information of the system nodes included in the business consortium chain, and this service information can include the node identifier information of the system nodes included in the business consortium chain. The node device can then send the generated service information to the terminal device, enabling the terminal device to display the first service interface based on the received service information.

[0165] Step S202: Receive the M system nodes and their configuration information returned by the terminal device; the M system nodes are selected by the terminal device from N system nodes on the first service interface; M is a positive integer less than or equal to N.

[0166] In this application, the node device can receive M system nodes returned by the terminal device. These M system nodes are the system nodes selected by the terminal device from the aforementioned N system nodes on the first service interface for building the business blockchain. The specific process by which the terminal device obtains these M system nodes on the first service interface can be found in the description of the embodiment corresponding to Figure 3 above. When the node device obtains the M system nodes sent by the terminal device, it can also obtain a blockchain construction request sent by the terminal device. This blockchain construction request is the terminal device's request to the node device to build the business blockchain to which the M system nodes belong. This blockchain construction request can be generated by the terminal device in response to a user's blockchain building operation on the blockchain platform.

[0167] In addition, the node device can also obtain the node configuration information of the M system nodes returned by the terminal device. This node configuration information can also be obtained by the terminal device on the first service interface. The specific process of how the terminal device obtains the node configuration information on the first service interface can also be referred to the description in the embodiment corresponding to Figure 3 above.

[0168] Step S203: Construct a business blockchain for M system nodes based on node configuration information, and run the constructed business blockchain;

[0169] In this application, the node device can construct the business blockchain to which the aforementioned M system nodes belong based on the obtained blockchain construction request and using node configuration information, and can run the constructed business blockchain. Specifically, the node device can add the M system nodes in the blockchain system to a business blockchain, and can configure each system node on the blockchain according to the node configuration information to obtain the final constructed business blockchain.

[0170] Optionally, the node configuration information may include the data on-chain format of each of the above Z data fields and the field combination strategy of the Z data fields. The Z data fields may be data fields contained in the target data type, which is the type of data that can be shared with the business blockchain (which can be called a shared data type).

[0171] Therefore, the node device can generate a data-on-chain contract based on the data-on-chain format of each data field in the node configuration information and the field combination strategy corresponding to the Z data fields. This data-on-chain contract is a smart contract that adds data of the target data type to the business blockchain. Thus, the node device can deploy this data-on-chain contract on each of the M system nodes to obtain the constructed business blockchain, where each system node can deploy this data-on-chain contract.

[0172] Furthermore, after constructing the aforementioned data on-chain contract for each of the M system nodes, the resulting blockchain belonging to these M system nodes can be referred to as the initial business blockchain. The node devices can also create a business access channel for this initial business blockchain, on which smart contracts in the initial business blockchain can be instantiated, ultimately resulting in a business blockchain with a business access channel.

[0173] This involves adding M system nodes to the business access channel, allowing these M system nodes in the business blockchain to access the business blockchain through the created access channel. This access includes operations such as calling smart contracts (e.g., data upload contracts) within the business blockchain. It's important to note that each blockchain can correspond to only one business access channel, and system nodes not joined by this channel typically cannot access the corresponding blockchain. For example, a business consortium blockchain can have one business access channel; if the consortium blockchain includes multiple business sub-chains, each sub-chain can also have its own access channel. By establishing business access channels for each blockchain, data sharing permissions between different system nodes can be quickly implemented, achieving minimal data isolation.

[0174] In this business blockchain, smart contracts of any type can be deployed on each system node. These smart contracts can be generated based on user configuration operations on the blockchain platform. For example, the smart contract can also include a smart contract for resource transfer between two system nodes. For instance, when system node A provides information to system node B, and system node B confirms the information, system node B can transfer a specified amount of resources (such as a specified amount of money) to system node A.

[0175] Furthermore, the aforementioned node devices can belong to the target system node, which can be any one of the M system nodes. Since each system node corresponds to its original business system, this application, while ensuring minimal modification to the original business systems of each system node, can achieve data interaction between each system node and its corresponding business system through encrypted interfaces. However, it is important to understand that the business system is independent of the blockchain system. For example, if a system node is the blockchain node corresponding to the Human Resources and Social Security Bureau, then the business system corresponding to that system node is the original system of the Human Resources and Social Security Bureau. Similarly, if a system node is the blockchain node corresponding to the Public Security Bureau, then the business system corresponding to that system node is the original system of the Public Security Bureau.

[0176] The business system associated with (i.e., corresponding to) the aforementioned target system node can be referred to as the target business system. The encrypted interface between the system node and the corresponding business system can be a contract interface. The business system can call the smart contract on the corresponding system node through this contract system. This business system can be referred to as a third-party system. The node device can also set access permissions for this contract interface. For example, the access permissions can include access time periods, the number of times per day, and access IP (Internet Protocol) addresses, etc.

[0177] It should be noted that all smart contracts deployed on the business blockchain can have contract interfaces set. These interfaces are used by other business systems or other system nodes to call the smart contracts. By setting interface permissions for these interfaces, the permissions of other business systems or other system nodes to call the smart contracts can be restricted, such as restrictions on the access time period and the number of times they can be accessed.

[0178] Please refer to Figure 8, which is a schematic diagram of the service interface for publishing a contract interface provided in this application. After creating a smart contract on the business blockchain, the contract interface of the smart contract can be published, allowing other system nodes or third-party systems (such as a business system) to call the corresponding smart contract through the contract interface. As shown in Figure 8, the smart contracts created on the business blockchain can be displayed and queried in interface 106c, and contract interfaces can be published for the displayed or queried smart contracts. It is understood that the publication of contract interfaces for smart contracts in the business blockchain can be done in a production environment or a test environment, depending on the needs of the business scenario. For example, the smart contract named "111" with the ledger name "ID Card" has published a contract interface, while the smart contract named "222" with the ledger name "Construction Permit" has not published a contract interface. Therefore, the operation of publishing a contract interface can be performed on these smart contracts.

[0179] Please refer to Figure 9, which is a schematic diagram of the service interface for contract interface authorization provided in this application. In interface 107c, the contract interface published as shown in Figure 8 above can be authorized. For example, the contract interface can be "modified," which means configuring the permissions of the contract interface, including the access time period and the number of accesses. As shown in interface 107c, the smart contract interface can include its network (such as the business blockchain), PASS ID (i.e., the identifier of the contract interface), PASS TOKEN (i.e., the token of the contract interface, which can be understood as permission verification information), and data decryption private key (such as the private key for decrypting the PASS TOKEN). Therefore, it can be understood that the contract interface is an encrypted interface. The contract interface can be encrypted using the PASS TOKEN and decrypted using the data decryption private key, thereby enabling the invocation of the smart contract through this contract interface.

[0180] Therefore, node devices can obtain L pieces of data to be uploaded to the blockchain from the target business system through this contract interface, where L is a positive integer. These L pieces of data have the same data format type (e.g., ID card type), such as the L user ID cards. The node device can also obtain a data upload template for these L pieces of data, which can include methods for uploading the data to the blockchain. The node device can call the data upload contract through the contract interface and use the data upload template to import the L pieces of data into the business blockchain in batches. When there is a large amount of data to be uploaded, the data upload template can be used to quickly import a large amount of data into the business blockchain in batches.

[0181] Please refer to Figure 10, which is a schematic diagram of the service interface for importing data templates provided in this application. As shown in Figure 10, users can import data through templates in interface 108c, such as quickly batch-uploading multiple data to be uploaded to the blockchain (e.g., L data to be uploaded to the blockchain as mentioned above) using the aforementioned data upload template. If the imported data is abnormal, the abnormal data can be exported and then the original data can be re-imported. For example, interface 108c shows imported data including data named "abc" and data named "efg". It can be understood that the node device can obtain the data entered by the user in interface 108c, therefore, data import on the business blockchain is actually achieved through the node device.

[0182] For a business system with relatively little incremental data, a data import interface can be used to quickly import the incremental data into the business blockchain. Typically, the data import interface can import one incremental data entry at a time. For example, this incremental data could be a user's ID card information added to the public security bureau's business system, with only one incremental data entry per day.

[0183] Specifically, node devices can also obtain incremental data from the target business system through the contract interface between the target business system and the business blockchain, and can obtain a data import interface for this incremental data. This data import interface can be a URL (link) interface. Therefore, node devices can call the data on-chain contract through the contract interface and use the data import interface to import the incremental data into the business blockchain.

[0184] Please refer to Figure 11, which is a schematic diagram of the service interface for importing data templates provided in this application. As shown in Figure 11, users can import data through the data import interface in interface 109c. This data import interface can be a URL link, allowing users to copy the URL link and then upload the data to the blockchain through the copied URL link. As shown in interface 108c, the imported data includes data with the field name "aaa" and data with the field name "bbb". It can be understood that the node device can obtain the data entered by the user through the data import interface; therefore, importing data on the business blockchain is actually achieved through the node device.

[0185] As shown above, in interface 108c, data is imported via the data upload template on a per-file basis. Therefore, the data upload template allows for rapid batch upload of multiple files to the blockchain. In interface 109c, data is imported via the data import interface, which imports data based on multiple fields contained in a file. Therefore, for small amounts of newly added data, the data import interface can be used for rapid upload. Different methods can be selected for data upload based on the actual application scenario.

[0186] After constructing the aforementioned business blockchain, a production environment and a testing environment can be provided. The production environment involves normal use of the business blockchain, including data upload, data querying, and smart contract calls. The testing environment is used to test these operations. Data generated in the testing environment is not actually added to the business blockchain; it exists only within the testing environment. Data generated in the production environment, however, is actually added to the business blockchain.

[0187] By providing both formal and testing environments, developers can apply the business blockchain in the formal environment and easily test it in the testing environment. Once the business blockchain is successfully tested, it can be officially deployed into application.

[0188] Optionally, if the business blockchain is a blockchain used in electronic certificate scenarios (such as ID cards, social security cards, and licenses), then the smart contracts deployed on the business blockchain may include, but are not limited to, the following smart contracts:

[0189] 1. Electronic certificate information on-chain storage contract:

[0190] This service utilizes a smart contract for on-chain storage of electronic certificate information. The electronic certificate information includes both structured and unstructured data. The contract logic connects to the municipal electronic certificate database to upload basic electronic certificate information to the blockchain. It also defines the interface and permissions for the smart contract, enabling data retrieval by upper-layer application platforms (such as blockchain platforms).

[0191] 2. Electronic Certificate Information Verification Contract:

[0192] The smart contract service for verifying electronic certificate information connects to the municipal electronic certificate database to verify the basic information of electronic certificates. It implements electronic certificate information authentication and verification contract services, ensuring the credibility of electronic certificate information for government business processing based on the electronic certificate blockchain. The service also defines the interface (contract interface) and permissions (such as authorized access periods and access counts) for the smart contract for verifying electronic certificate information, enabling data verification through upper-layer application platforms.

[0193] 3. Electronic Certificate Authorization Agreement:

[0194] Access to on-chain data on the electronic certificate blockchain application platform requires on-chain authorization. The authorization information definition contract service provides the logic for defining permissions to access on-chain data of electronic certificates, stores authorization information on the electronic certificate chain, and has the functions of adding and revoking authorizations. The smart contract is deployed to run in the electronic certificate chain channel, providing relevant smart contract interfaces to connect with application platforms and realize the logic for querying authorized data on the chain. It also completes the interface definition and interface permission definition for smart contracts of third-party application systems (such as business systems), enabling upper-layer application platforms to access and authorize data use.

[0195] 4. Electronic Certificate Information Inquiry Contract:

[0196] This is a smart contract service for querying electronic certificate information. Electronic certificate information includes both structured and unstructured data. It connects to the municipal electronic certificate database and implements the contract logic for querying electronic certificate information, including queries based on primary keys and indexes. The interface and permission definitions for the smart contract for querying electronic certificate information are completed, enabling upper-layer application platforms to connect and query data on the blockchain.

[0197] 5. Contract for Historical Inquiry of Electronic Certificate Information:

[0198] For querying historical data of electronic certificate information, the blockchain service on the blockchain platform can be called to access and view the historical operation records of the data on the chain.

[0199] 6. Electronic certificates use on-chain contracts (such as the data on-chain contract mentioned above):

[0200] Electronic certificates utilize on-chain smart contract services to record information about the use of electronic certificates on the blockchain. The smart contracts are deployed and run within the electronic certificate blockchain channel, providing relevant smart contract interfaces to connect with application platforms. This includes defining the interfaces and permissions for third-party application systems to call the smart contracts, enabling upper-layer application platforms to connect to the on-chain data contract.

[0201] In this application, when a smart contract is called for the first time, consensus needs to be reached on the business blockchain. If the consensus is reached, subsequent calls to the smart contract will not require consensus and can be made directly.

[0202] This application can display a first service interface of a blockchain system; the blockchain system includes N system nodes that have been connected; N is a positive integer; on the first service interface, M system nodes are selected from the N system nodes, and node configuration information for the M system nodes is obtained; M is a positive integer less than or equal to N; the business blockchain to which the M system nodes belong is constructed according to the node configuration information. Therefore, the method proposed in this application can obtain M system nodes and their node configuration information on the first service interface, and then directly and quickly construct the business blockchain to which the M system nodes belong using this node configuration information, thereby reducing the difficulty of constructing the business blockchain and improving its construction efficiency.

[0203] Please refer to Figure 12, which is a flowchart illustrating a consortium blockchain creation method provided in this application. As shown in Figure 12, the method may include:

[0204] Step S301: Deploy the blockchain consortium;

[0205] Optionally, system nodes of the business entities that need to be added to the business consortium chain can be deployed in the blockchain system, such as the M system nodes mentioned above.

[0206] Step S302: Deploy the consortium blockchain network;

[0207] Optionally, the deployed system nodes can then be added to a business consortium blockchain (i.e., a consortium blockchain network).

[0208] Step S303: Establish the basic channel;

[0209] Optionally, after adding a system node to a business consortium blockchain, this initial consortium blockchain is still considered an initial one. A business access channel for this consortium blockchain, such as the general channel shown in Figure 1, still needs to be established. All system nodes in the business consortium blockchain can join this business access channel.

[0210] Step S304: Deploy the regulatory contract;

[0211] Optionally, smart contracts (i.e. regulatory contracts) can be deployed on the business consortium chain obtained through step S303.

[0212] Step S305: Call the standard contract to perform predefined settings;

[0213] Optionally, the smart contract deployed on the business consortium chain in step S304 can be predefined. The predefined settings can be to set specific execution parameters of the smart contract. For example, if it is a smart contract for data resource transfer, the predefined settings for the smart contract can be to set the amount of data resources to be transferred.

[0214] Users can quickly create the aforementioned business consortium blockchain by issuing corresponding commands on the blockchain platform.

[0215] Please refer to Figure 13, which is a flowchart illustrating a data upload method provided in this application. As shown in Figure 13, the method may include:

[0216] Step S401: Enable the data sharing network;

[0217] Optionally, a business sub-chain within a business consortium blockchain belongs to a data sharing network, and the business consortium blockchain itself also belongs to a data sharing network. Data providers (which can be any business entity) can choose which system nodes to share their provided data (such as ID cards), thereby enabling the construction of business sub-chains through these system nodes.

[0218] Step S402: Select the data sharing type;

[0219] Optionally, the data provider (through their administrator account on the blockchain platform) can select the data sharing type (such as the type of ID card) for the data shared on the data sharing network. This data sharing type is equivalent to the data types mentioned above. Here, a list of data types can be provided on the blockchain platform, allowing users to select the data sharing type from this list.

[0220] Step S403: Add a new data sharing type;

[0221] Optionally, if the list of data types mentioned above does not include the type of data that the data provider wants to share, the data provider can add new data sharing types on their own.

[0222] Step S404: Determine the data upload metadata information;

[0223] Optionally, the data on-chain metadata information is the metadata of the data that needs to be uploaded to the blockchain. For example, the data that needs to be uploaded to the blockchain may include the above Z data fields, and the data on-chain metadata information may include the metadata information of each of the Z data fields.

[0224] Step S405: Select a ledger template;

[0225] Optionally, the ledger template is the on-chain template for the data that needs to be uploaded to the blockchain. For example, if the data to be uploaded to the blockchain is an ID card, then the ledger template can be the on-chain template corresponding to the ID card. The on-chain template can include the method of uploading the data fields contained in the ID card to the blockchain and the layout information, etc.

[0226] Step S406: Select a contract template;

[0227] Optionally, after selecting the above ledger template, you can also select a contract template for the ledger template. The contract template can be a smart contract that uses the ledger template to upload data to the blockchain.

[0228] Step S407: Submit a request for on-chain service;

[0229] Optionally, after selecting the ledger template and contract template corresponding to the above data on-chain metadata information, you can submit a request for on-chain service for the data on-chain metadata information based on the ledger template and contract template.

[0230] Step S408: Data upload to the blockchain;

[0231] Optionally, by requesting the above-mentioned on-chain service, the data to which the metadata information belongs (such as an ID card) can be uploaded to the blockchain using the above-mentioned ledger template and contract template, that is, added to the above-mentioned data sharing network.

[0232] Users can quickly upload the aforementioned data to the blockchain by issuing corresponding commands on the blockchain platform.

[0233] Please refer to Figure 14, which is a flowchart illustrating a data usage method provided in this application. As shown in Figure 14, the method may include:

[0234] Step S501: Join the data sharing network;

[0235] Optionally, the system nodes of the data user (which can be any business entity, or a business entity that needs to use the data provided by the data provider in the corresponding embodiment of Figure 13 above) can join the data sharing network created by the data provider.

[0236] Step S502: Analyze the certificate requirements based on business needs;

[0237] Optionally, the authentication requirement can be the access method, such as access requirements for business access channels and contract interfaces of the data sharing network.

[0238] Step S503: Join the data sharing channel;

[0239] Optionally, data users can first join the business access channel of the data sharing network.

[0240] Step S504: Obtain data authorization;

[0241] Optionally, the data user can then obtain a data authorization, which is a contract interface authorized by the data provider for the data user. The data user can also verify the validity period of the contract interface.

[0242] Step S506: Retrieve data information;

[0243] Optionally, if the contract interface is within its validity period, the required data (such as ID card) can be retrieved through the contract interface.

[0244] Step S507, Business Progress;

[0245] Optionally, after obtaining the required data, the data user can then use the obtained data in a specific way.

[0246] Users can quickly obtain on-chain data by issuing corresponding commands in the blockchain platform.

[0247] Please refer to Figure 15, which is a schematic diagram of the structure of a blockchain-based data processing device provided in this application. This blockchain-based data processing device can be a computer program (including program code) running on a computer device. For example, the blockchain-based data processing device is an application software, and it can be used to execute the corresponding steps in the methods provided in the embodiments of this application. As shown in Figure 15, the blockchain-based data processing device 1 may include: a page display module 101, a node selection module 102, and a blockchain construction module 103.

[0248] Page display module 101 is used to display the first service interface of the blockchain system; the blockchain system includes N system nodes that have been connected; N is a positive integer;

[0249] The node selection module 102 is used to select M system nodes from N system nodes on the first service interface and obtain node configuration information for the M system nodes; M is a positive integer less than or equal to N.

[0250] Blockchain building module 103 is used to build a business blockchain belonging to M system nodes according to node configuration information.

[0251] Optionally, the blockchain system includes the constructed business consortium blockchain;

[0252] The methods by which page display module 101 displays the first service interface of the blockchain system include:

[0253] Display the second service interface of the blockchain system and obtain the consortium blockchain identification information of the business consortium blockchain entered in the second service interface;

[0254] The system nodes included in the business consortium chain among N system nodes are determined based on the consortium chain identification information;

[0255] The first service interface is displayed based on the node identification information of the system nodes included in the business consortium chain;

[0256] The constructed business blockchain is a sub-chain of the business consortium blockchain.

[0257] Optionally, the node selection module 102 may obtain node configuration information for M system nodes in the following ways:

[0258] Obtain the shared data type for sharing data with the business blockchain on the first service interface;

[0259] Retrieves Z data fields from a shared data type; Z is a positive integer.

[0260] Retrieve node configuration information based on Z data fields.

[0261] Optionally, the node selection module 102 may obtain node configuration information based on Z data fields in the following ways:

[0262] On the first service interface, obtain the data uplink format of each of the Z data fields and obtain the field combination strategy corresponding to the Z data fields;

[0263] The data uplink format and field combination strategy for each data field are defined as node configuration information.

[0264] Optionally, the above-mentioned device 1 further includes: a query field acquisition block 104, a data query module 105, and a data display module 106.

[0265] The query field is obtained from block 104, which is used to display the third service interface of the blockchain system and obtain the business query field for the business blockchain on the third service interface.

[0266] The data query module 105 is used to query business data associated with business query fields in the business blockchain;

[0267] The data display module 106 is used to display the business data associated with the business query field on the third service interface.

[0268] Optionally, the above-mentioned device 1 further includes: an on-chain data acquisition module 107, a data export module 108, and a re-import module 109.

[0269] The on-chain data acquisition module 107 is used to display the fourth service interface of the blockchain system, acquire target business data in the fourth service interface, and import the target business data into the business blockchain.

[0270] The data export module 108 is used to export the abnormal import data of the target business data from the business blockchain if the target business data is detected to be in an abnormal import state in the business blockchain.

[0271] The re-import module 109 is used to re-import the target business data into the business blockchain based on the abnormal import data.

[0272] According to one embodiment of this application, the steps involved in the blockchain-based data processing method shown in FIG3 can be executed by various modules in the blockchain-based data processing device 1 shown in FIG15. For example, step S101 shown in FIG3 can be executed by the page display module 101 in FIG15; step S102 shown in FIG3 can be executed by the node selection module 102 in FIG15; and step S103 shown in FIG3 can be executed by the blockchain construction module 103 in FIG15.

[0273] This application can display a first service interface of a blockchain system; the blockchain system includes N system nodes that have been connected; N is a positive integer; on the first service interface, M system nodes are selected from the N system nodes, and node configuration information for the M system nodes is obtained; M is a positive integer less than or equal to N; the business blockchain to which the M system nodes belong is constructed according to the node configuration information. Therefore, the device proposed in this application can obtain M system nodes and their node configuration information on the first service interface, and then directly and quickly construct the business blockchain to which the M system nodes belong using this node configuration information, thereby reducing the difficulty of constructing the business blockchain and improving its construction efficiency.

[0274] According to one embodiment of this application, the modules in the blockchain-based data processing device 1 shown in FIG15 can be individually or entirely merged into one or more units, or one or more of the units can be further divided into multiple functionally smaller sub-units to achieve the same operation without affecting the technical effect of the embodiment of this application. The above modules are based on logical function division. In practical applications, the function of one module can also be implemented by multiple units, or the function of multiple modules can be implemented by one unit. In other embodiments of this application, the blockchain-based data processing device 1 may also include other units. In practical applications, these functions can also be implemented with the assistance of other units, and can be implemented collaboratively by multiple units.

[0275] According to one embodiment of this application, a blockchain-based data processing apparatus 1 as shown in FIG15, and the blockchain-based data processing method of this application embodiment, can be constructed and implemented by running a computer program (including program code) capable of performing the steps involved in the corresponding method shown in FIG3 on a general-purpose computer device, such as a computer, which includes processing elements and storage elements such as a central processing unit (CPU), random access storage medium (RAM), and read-only storage medium (ROM). The aforementioned computer program can be recorded on, for example, a computer-readable recording medium, loaded onto the aforementioned computing device via the computer-readable recording medium, and run therein.

[0276] Please refer to Figure 16, which is a schematic diagram of the structure of a blockchain-based data processing device provided in this application. This blockchain-based data processing device can be a computer program (including program code) running on a computer device. For example, the blockchain-based data processing device is an application software, and it can be used to execute the corresponding steps in the methods provided in the embodiments of this application. As shown in Figure 16, the blockchain-based data processing device 2 may include: a service information sending module 201, a configuration information receiving module 202, and a blockchain running module 203.

[0277] The service information sending module 201 is used to send service information of the blockchain system to the terminal device so that the terminal device can display the first service interface of the blockchain system according to the service information; the blockchain system includes N system nodes that have been connected; N is a positive integer;

[0278] The configuration information receiving module 202 is used to receive the M system nodes and the node configuration information of the M system nodes returned by the terminal device; the M system nodes are the system nodes selected by the terminal device from N system nodes on the first service interface; M is a positive integer less than or equal to N;

[0279] The blockchain operation module 203 is used to construct a business blockchain belonging to M system nodes based on node configuration information, and to run the constructed business blockchain.

[0280] Optionally, the blockchain system includes the constructed business consortium blockchain;

[0281] The service information sending module 201 sends service information of the blockchain system to the terminal device in the following ways:

[0282] Obtain the consortium blockchain identifier information of the business consortium blockchain sent by the terminal device; the consortium blockchain identifier information is obtained by the terminal device on the second service interface of the blockchain system;

[0283] Based on the consortium blockchain identification information, determine the system nodes included in the business consortium blockchain among N system nodes, and obtain the node identification information of the system nodes included in the business consortium blockchain;

[0284] Service information is generated based on node identification information and sent to terminal devices.

[0285] Optionally, the node configuration information includes the data on-chain format of each of the Z data fields and the field combination strategy of the Z data fields; the Z data fields are the data fields contained in the data of the target data type; the target data type is a shared data type for data sharing with the business blockchain; Z is a positive integer;

[0286] The blockchain operation module 203 constructs a business blockchain belonging to M system nodes based on node configuration information in the following ways:

[0287] Based on the data on-chain format of each data field in the node configuration information and the field combination strategy of the Z data fields, a data on-chain contract is generated;

[0288] Deploy a data on-chain contract on each of the M system nodes to obtain the constructed business blockchain.

[0289] Optionally, the blockchain execution module 203 can deploy data-on-chain contracts on each of the M system nodes to obtain the constructed business blockchain in the following ways:

[0290] Deploy a data on-chain contract on each system node to obtain the initial business blockchain;

[0291] Create a business access channel for the initial business blockchain, and define the initial business blockchain with the business access channel as the business blockchain.

[0292] Among them, M system nodes are used to call the data on-chain contract in the business blockchain through the business access channel.

[0293] Optionally, the above-mentioned device 2 is applied to a target system node among N system nodes; the target system node belongs to M system nodes; and each of the M system nodes has an associated business system.

[0294] The aforementioned device 2 further includes: a first system determination module 204, a first data acquisition module 205, and a template uplink module 206.

[0295] The first system determination module 204 is used to determine the business system associated with the target system node as the target business system;

[0296] The first data acquisition module 205 is used to acquire L pieces of data to be uploaded to the blockchain from the target business system according to the contract interface between the target business system and the business sub-chain; the L pieces of data to be uploaded to the blockchain have the same data format type, and L is a positive integer;

[0297] The template-on-chain module 206 is used to obtain a data-on-chain template for L data items to be uploaded to the blockchain, and to use the data-on-chain template to batch import the L data items to be uploaded to the business blockchain by calling the data-on-chain contract through the contract interface.

[0298] Optionally, the above-mentioned device 2 is applied to a target system node among N system nodes; the target system node belongs to M system nodes; and each of the M system nodes has an associated business system.

[0299] The aforementioned device 2 further includes: a second system determination module 207, a second data acquisition module 208, and an interface uplink module 209.

[0300] The second system determination module 207 is used to determine the business system associated with the target system node as the target business system;

[0301] The second data acquisition module 208 is used to acquire incremental data in the target business system based on the contract interface between the target business system and the business blockchain.

[0302] The interface on-chain module 209 is used to obtain the data import interface for incremental data, and to call the data on-chain contract through the contract interface to import the incremental data into the business blockchain using the data import interface.

[0303] According to one embodiment of this application, the steps involved in the blockchain-based data processing method shown in FIG7 can be executed by various modules in the blockchain-based data processing device 2 shown in FIG16. For example, step S201 shown in FIG7 can be executed by the service information sending module 201 in FIG16; step S202 shown in FIG7 can be executed by the configuration information receiving module 202 in FIG16; and step S203 shown in FIG7 can be executed by the blockchain running module 203 in FIG16.

[0304] This application can display a first service interface of a blockchain system; the blockchain system includes N system nodes that have been connected; N is a positive integer; on the first service interface, M system nodes are selected from the N system nodes, and node configuration information for the M system nodes is obtained; M is a positive integer less than or equal to N; the business blockchain to which the M system nodes belong is constructed according to the node configuration information. Therefore, the device proposed in this application can obtain M system nodes and their node configuration information on the first service interface, and then directly and quickly construct the business blockchain to which the M system nodes belong using this node configuration information, thereby reducing the difficulty of constructing the business blockchain and improving its construction efficiency.

[0305] According to one embodiment of this application, the modules in the blockchain-based data processing device 2 shown in FIG16 can be individually or entirely merged into one or more units, or one or more of the units can be further divided into multiple functionally smaller sub-units to achieve the same operation without affecting the technical effect of the embodiment of this application. The above modules are based on logical function division. In practical applications, the function of one module can also be implemented by multiple units, or the function of multiple modules can be implemented by one unit. In other embodiments of this application, the blockchain-based data processing device 2 may also include other units. In practical applications, these functions can also be implemented with the assistance of other units, and can be implemented collaboratively by multiple units.

[0306] According to one embodiment of this application, a blockchain-based data processing apparatus 2 as shown in FIG16, and the blockchain-based data processing method of this application embodiment, can be constructed and implemented by running a computer program (including program code) capable of performing the steps involved in the corresponding method shown in FIG7 on a general-purpose computer device including processing elements and storage elements such as a central processing unit (CPU), random access storage medium (RAM), and read-only storage medium (ROM). The aforementioned computer program can be recorded on, for example, a computer-readable recording medium, loaded onto the aforementioned computing device via the computer-readable recording medium, and run therein.

[0307] Please refer to Figure 17, which is a schematic diagram of the structure of a computer device provided in this application. As shown in Figure 17, the computer device 1000 may include: a processor 1001, a network interface 1004, and a memory 1005. Furthermore, the computer device 1000 may also include: a user interface 1003, and at least one communication bus 1002. The communication bus 1002 is used to realize communication between these components. The user interface 1003 may include a display screen and a keyboard; optionally, the user interface 1003 may also include a standard wired interface or a wireless interface. The network interface 1004 may optionally include a standard wired interface or a wireless interface (such as a Wi-Fi interface). The memory 1005 may be a high-speed RAM memory or a non-volatile memory, such as at least one disk storage device. Optionally, the memory 1005 may also be at least one storage device located remotely from the aforementioned processor 1001. As shown in Figure 17, the memory 1005, as a computer storage medium, may include an operating system, a network communication module, a user interface module, and a device control application program.

[0308] In the computer device 1000 shown in Figure 17, the network interface 1004 provides network communication functions; the user interface 1003 is mainly used to provide an input interface for the user; and the processor 1001 can be used to call the device control application stored in the memory 1005 to achieve:

[0309] Displays the first service interface of the blockchain system; the blockchain system includes N system nodes that have been connected; N is a positive integer;

[0310] On the first service interface, select M system nodes from N system nodes and obtain the node configuration information for the M system nodes; M is a positive integer less than or equal to N;

[0311] Construct a business blockchain comprising M system nodes based on node configuration information.

[0312] Optionally, the processor 1001 can be used to call device control applications stored in the memory 1005, and can also achieve:

[0313] Send service information of the blockchain system to the terminal device so that the terminal device can display the first service interface of the blockchain system based on the service information; the blockchain system includes N system nodes that have been connected; N is a positive integer;

[0314] The terminal device receives M system nodes and their configuration information; the M system nodes are selected by the terminal device from N system nodes on the first service interface; M is a positive integer less than or equal to N.

[0315] Based on the node configuration information, construct a business blockchain belonging to M system nodes and run the constructed business blockchain.

[0316] It should be understood that the computer device 1000 described in the embodiments of this application can execute the description of the blockchain-based data processing method in the embodiments corresponding to any one of Figures 3 or 7 above, and can also execute the description of the blockchain-based data processing device 1 in the embodiments corresponding to Figure 15 above, and the description of the blockchain-based data processing device 2 in the embodiments corresponding to Figure 16 above, which will not be repeated here. In addition, the beneficial effects of using the same method will not be repeated here.

[0317] Furthermore, it should be noted that this application also provides a computer-readable storage medium storing a computer program executed by the aforementioned blockchain-based data processing device 1 and blockchain-based data processing device 2. The computer program includes program instructions, which, when executed by a processor, enable the execution of the blockchain-based data processing method described in the embodiments corresponding to either Figure 3 or Figure 7. Therefore, these descriptions will not be repeated here. Additionally, the beneficial effects of using the same method will also not be repeated. For technical details not disclosed in the embodiments of the computer storage medium involved in this application, please refer to the description of the method embodiments of this application.

[0318] As an example, the above program instructions can be deployed and executed on a single computer device, or deployed and executed on multiple computer devices located in one location, or executed on multiple computer devices distributed across multiple locations and interconnected via a communication network. Multiple computer devices distributed across multiple locations and interconnected via a communication network can form a blockchain network.

[0319] The aforementioned computer-readable storage medium can be the internal storage unit of the blockchain-based data processing device provided in any of the foregoing embodiments, or the computer device itself, such as the hard drive or memory of the computer device. The computer-readable storage medium can also be an external storage device of the computer device, such as a plug-in hard drive, smart media card (SMC), secure digital (SD) card, flash card, etc., provided on the computer device. Furthermore, the computer-readable storage medium can include both internal and external storage units of the computer device. The computer-readable storage medium is used to store the computer program and other programs and data required by the computer device. The computer-readable storage medium can also be used to temporarily store data that has been output or will be output.

[0320] This application provides a computer program product or computer program that includes computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the blockchain-based data processing method described in the embodiments corresponding to Figures 3 or 7 above; therefore, it will not be repeated here. Furthermore, the beneficial effects of using the same method will also not be repeated. For technical details not disclosed in the computer-readable storage medium embodiments involved in this application, please refer to the description of the method embodiments of this application.

[0321] The terms "first," "second," etc., in the specification, claims, and drawings of this application are used to distinguish different objects, not to describe a specific order. Furthermore, the term "comprising," and any variations thereof, are intended to cover non-exclusive inclusion. For example, a process, method, apparatus, product, or device that includes a series of steps or units is not limited to the listed steps or modules, but may optionally include steps or modules not listed, or may optionally include other step units inherent to these processes, methods, apparatuses, products, or devices.

[0322] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of both. To clearly illustrate the interchangeability of hardware and software, the components and steps of the various examples have been generally described in terms of functionality in the foregoing description. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementations should not be considered beyond the scope of this application.

[0323] The methods and related apparatus provided in this application are described with reference to the method flowcharts and / or structural diagrams provided in this application. Specifically, each block of the method flowcharts and / or structural diagrams, as well as combinations of blocks in the flowcharts and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing device to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing device, create means for implementing the functions specified in one or more blocks of the flowcharts and / or one or more blocks of the structural diagrams. These computer program instructions can also be stored in a computer-readable storage medium capable of directing a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means that implement the functions specified in one or more blocks of the flowcharts and / or one or more blocks of the structural diagrams. These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer-implemented process, such that the instructions, which execute on the computer or other programmable apparatus, provide steps for implementing the functions specified in one or more flowcharts and / or one or more blocks in the structural diagram.

[0324] The above-disclosed embodiments are merely preferred embodiments of this application and should not be construed as limiting the scope of this application. Therefore, any equivalent variations made in accordance with the claims of this application shall still fall within the scope of this application.

Claims

1. A data processing method based on blockchain, characterized in that, The method includes: Displays the first service interface of the blockchain system; the blockchain system includes N system nodes that have been connected; N is a positive integer; On the first service interface, select M system nodes from the N system nodes and obtain node configuration information for the M system nodes; M is a positive integer less than or equal to N; wherein, the M system nodes are selected based on the node identification information of the M system nodes entered in the first service interface, or based on the selection operation of the node identification information of the M system nodes among the N system nodes in the first service interface; the node configuration information includes the field combination strategy of each of the Z data fields of at least one shared data type set in the first service interface, and the data uplink format of each of the Z data fields, where Z is a positive integer; The business blockchain to which the M system nodes belong is constructed according to the node configuration information; wherein, each of the M system nodes in the business blockchain is equipped with a data on-chain contract, and the data on-chain contract is used to share data of at least one shared data type among the selected M system nodes according to the field combination strategy corresponding to each shared data type and the data on-chain format of each data field.

2. The method according to claim 1, characterized in that, The blockchain system includes a constructed business consortium blockchain; The first service interface of the blockchain system includes: Display the second service interface of the blockchain system and obtain the consortium blockchain identifier information of the business consortium blockchain entered in the second service interface; The system nodes included in the business consortium chain among the N system nodes are determined based on the consortium chain identification information; The first service interface is displayed based on the node identification information of the system nodes included in the business consortium chain; The constructed business blockchain is a sub-chain of the business consortium blockchain.

3. The method according to claim 1, characterized in that, The step of obtaining the node configuration information for the M system nodes includes: On the first service interface, obtain the shared data type for sharing data with the business blockchain; Obtain the Z data fields included in the data of the shared data type; Z is a positive integer; The node configuration information is obtained based on the Z data fields.

4. The method according to claim 3, characterized in that, The step of obtaining the node configuration information based on the Z data fields includes: On the first service interface, obtain the data uplink format of each of the Z data fields, and obtain the field combination strategy corresponding to the Z data fields; The data uplink format of each data field and the field combination strategy are determined as the node configuration information.

5. The method according to claim 1, characterized in that, The method further includes: Display the third service interface of the blockchain system, and obtain the business query field for the business blockchain on the third service interface; Query the business data associated with the business query field in the business blockchain; The third service interface displays the business data associated with the business query field.

6. The method according to claim 1, characterized in that, The method further includes: The fourth service interface of the blockchain system is displayed, the target business data is obtained in the fourth service interface, and the target business data is imported into the business blockchain; If the target business data is detected to be in an abnormal import state in the business blockchain, then the abnormal import data of the target business data is exported from the business blockchain; The target business data is re-imported into the business blockchain based on the abnormal import data.

7. A data processing method based on blockchain, characterized in that, The method includes: The service information of the blockchain system is sent to the terminal device so that the terminal device displays the first service interface of the blockchain system according to the service information; the blockchain system includes N system nodes that have been connected; N is a positive integer; The system receives M system nodes and their configuration information returned by the terminal device. The M system nodes are selected by the terminal device from N system nodes on the first service interface; M is a positive integer less than or equal to N. The selection of the M system nodes is based on the node identifier information entered in the first service interface, or on a selection operation of the node identifier information of the M system nodes among the N system nodes in the first service interface. The node configuration information includes a field combination strategy for each of the Z data fields of at least one shared data type set in the first service interface, and the data uplink format of each of the Z data fields, where Z is a positive integer. The business blockchain to which the M system nodes belong is constructed based on the node configuration information, and the constructed business blockchain is run; wherein, each of the M system nodes in the business blockchain has a data on-chain contract deployed on it, and the data on-chain contract is used to share data of at least one shared data type among the selected M system nodes according to the field combination strategy corresponding to each shared data type and the data on-chain format of each data field.

8. The method according to claim 7, characterized in that, The blockchain system includes a constructed business consortium blockchain; Sending service information of the blockchain system to the terminal device includes: The terminal device obtains the consortium blockchain identification information of the business consortium blockchain sent by the terminal device; the consortium blockchain identification information is obtained by the terminal device from the second service interface of the blockchain system. Based on the consortium blockchain identification information, determine the system nodes included in the business consortium blockchain among the N system nodes, and obtain the node identification information of the system nodes included in the business consortium blockchain; The service information is generated based on the node identification information and then sent to the terminal device.

9. The method according to claim 7, characterized in that, The Z data fields are the data fields contained in the target data type; the target data type is a shared data type for data sharing in the business blockchain; The step of constructing the business blockchain to which the M system nodes belong based on the node configuration information includes: The data on-chain contract is generated based on the data on-chain format of each data field in the node configuration information and the field combination strategy of the Z data fields; The data on-chain contract is deployed on each of the M system nodes to obtain the constructed business blockchain.

10. The method according to claim 9, characterized in that, The process of deploying the data-on-chain contract on each of the M system nodes to obtain the constructed business blockchain includes: Deploy the data on-chain contract on each system node to obtain the initial business blockchain; Create a business access channel for the initial business blockchain, and identify the initial business blockchain with the business access channel as the business blockchain. The M system nodes are used to invoke the data on-chain contract in the business blockchain through the business access channel.

11. The method according to claim 9, characterized in that, The method is executed by the target system node among the N system nodes; The target system node belongs to the M system nodes; each of the M system nodes has an associated business system. The method further includes: The business systems associated with the target system node are identified as the target business systems; Based on the contract interface between the target business system and the business sub-chain, obtain L pieces of data to be uploaded to the chain from the target business system; the L pieces of data to be uploaded to the chain have the same data format type, and L is a positive integer. Obtain the data upload template for the L data items to be uploaded to the blockchain, and use the contract interface to call the data upload contract to import the L data items to be uploaded to the business blockchain in batches using the data upload template.

12. The method according to claim 9, characterized in that, The method is executed by the target system node among the N system nodes; The target system node belongs to the M system nodes; each of the M system nodes has an associated business system. The method further includes: The business systems associated with the target system node are identified as the target business systems; Based on the contract interface between the target business system and the business blockchain, incremental data is obtained from the target business system. Obtain the data import interface for the incremental data, and use the contract interface to call the data on-chain contract to import the incremental data into the business blockchain using the data import interface.

13. A data processing device based on blockchain, characterized in that, The device includes: The page display module is used to display the first service interface of the blockchain system; the blockchain system includes N system nodes that have been connected; N is a positive integer; The node selection module is used to select M system nodes from the N system nodes on the first service interface and obtain node configuration information for the M system nodes; M is a positive integer less than or equal to N; wherein, the M system nodes are selected based on the node identification information of the M system nodes entered in the first service interface, or based on the selection operation of the node identification information of the M system nodes among the N system nodes in the first service interface; the node configuration information includes the field combination strategy of each of the Z data fields of at least one shared data type set in the first service interface, and the data uplink format of each of the Z data fields, where Z is a positive integer; A blockchain construction module is used to construct a business blockchain to which the M system nodes belong, according to the node configuration information; wherein, each of the M system nodes in the business blockchain has a data on-chain contract deployed on it, and the data on-chain contract is used to share data of at least one shared data type among the selected M system nodes according to the field combination strategy corresponding to each shared data type and the data on-chain format of each data field.

14. A computer device, characterized in that, It includes a memory and a processor, the memory storing a computer program that, when executed by the processor, causes the processor to perform the steps of the method according to any one of claims 1-12.

15. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program adapted to be loaded by a processor and executed as described in any one of claims 1-12.

Images