Blockchain-based data processing method and device, electronic device, and storage medium

Abstract

Embodiments of the present application disclose a blockchain-based data processing method and system, device, electronic equipment and storage medium. The method comprises: obtaining a data processing request initiated by a business account; obtaining a blockchain node account bound to the business account based on the data processing request, wherein different blockchain node accounts correspond to different blockchain nodes belonging to different blockchain systems, and different blockchain systems maintain different blockchains respectively; and sending the to-be-processed data contained in the data processing request to the blockchain node corresponding to the blockchain node account, so that the blockchain node initiates a processing operation on the to-be-processed data in the blockchain system to which the blockchain node belongs. The technical solution of the embodiments of the present application can enable an enterprise business to use blockchain technology and meet the needs of enterprise management in terms of authority and business isolation.

Description

Technical Field

[0001] This application relates to the field of data processing, and more specifically, to a data processing method and apparatus, electronic device, and storage medium based on blockchain. Background Technology

[0002] Blockchain is a decentralized database that features unforgeable, traceable, tamper-proof, and collectively maintained characteristics, enhancing the credibility of data and helping enterprises build trustworthy data.

[0003] However, among related technologies, blockchain-based data processing methods have low flexibility and a low degree of matching with enterprise needs. Summary of the Invention

[0004] To address the aforementioned technical problems, embodiments of this application provide a data processing method and system, apparatus, electronic device, and computationally readable storage medium based on blockchain.

[0005] According to one aspect of the embodiments of this application, a blockchain-based data processing method is provided, the method comprising:

[0006] Obtain data processing requests initiated by business accounts;

[0007] Based on the data processing request, the blockchain node account bound to the business account is obtained, wherein the blockchain nodes corresponding to different blockchain node accounts belong to different blockchain systems, and each of the different blockchain systems maintains a different blockchain.

[0008] The data to be processed contained in the data processing request is sent to the blockchain node corresponding to the blockchain node account, so that the blockchain node initiates a processing operation on the data to be processed in its own blockchain system.

[0009] According to one aspect of the embodiments of this application, a blockchain-based data processing system is provided, characterized in that the system includes: business nodes and blockchain nodes;

[0010] The business node obtains a data processing request initiated by a business account, and obtains the blockchain node account bound to the business account based on the data processing request, and sends the data to be processed contained in the data processing request to the blockchain node corresponding to the blockchain node account; wherein, the blockchain nodes corresponding to different blockchain node accounts belong to different blockchain systems, and the different blockchain systems each maintain different blockchains.

[0011] The blockchain node receives the data to be processed sent by the business node and initiates processing operations on the data to be processed in its own blockchain system.

[0012] According to one aspect of the embodiments of this application, a blockchain-based data processing apparatus is provided, comprising:

[0013] The first acquisition module is configured to acquire data processing requests initiated by business accounts;

[0014] The second acquisition module is configured to acquire the blockchain node account bound to the business account based on the data processing request, wherein the blockchain nodes corresponding to different blockchain node accounts belong to different blockchain systems, and the different blockchain systems each maintain different blockchains.

[0015] The sending module is configured to send the data to be processed contained in the data processing request to the blockchain node corresponding to the blockchain node account, so that the blockchain node initiates a processing operation on the data to be processed in its own blockchain system.

[0016] According to one aspect of the embodiments of this application, an electronic device is provided, comprising:

[0017] One or more processors;

[0018] A storage device for storing one or more programs that, when executed by one or more processors, cause the electronic device to perform the method described in any of the preceding descriptions.

[0019] According to one aspect of the embodiments of this application, a computer program product or computer program is provided, which 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 provided in the various alternative embodiments described above.

[0020] In the technical solution provided by the embodiments of this application, a data processing request initiated by a business account is obtained; based on the data processing request, the blockchain node account bound to the business account is obtained, wherein the blockchain nodes corresponding to different blockchain node accounts belong to different blockchain systems, and each blockchain system maintains a different blockchain; the data to be processed contained in the data processing request is sent to the blockchain node corresponding to the blockchain node account, so that the blockchain node initiates a processing operation on the data to be processed in its own blockchain system. On the one hand, by binding a blockchain node account to a business account, the enterprise business can use blockchain technology; on the other hand, the blockchain nodes corresponding to different blockchain node accounts belong to different blockchain systems, thereby separating the business data stored in different blockchain systems to meet the enterprise's needs for permissions and business isolation in management.

[0021] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and do not limit this application. Attached Figure Description

[0022] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application. It is obvious that the drawings described below are merely some embodiments of this application, and those skilled in the art can obtain other drawings based on these drawings without any inventive effort. In the drawings:

[0023] Figure 1 This is a schematic diagram illustrating the implementation environment of an exemplary embodiment of this application;

[0024] Figure 2 Another exemplary embodiment of this application illustrates a schematic diagram of the implementation environment;

[0025] Figure 3 This is a flowchart illustrating a blockchain-based data processing method as shown in an exemplary embodiment of this application;

[0026] Figure 4 This is a schematic diagram of an enterprise architecture illustrated in an exemplary embodiment of this application;

[0027] Figure 5 This is a flowchart illustrating a blockchain-based data processing method, as shown in another exemplary embodiment of this application;

[0028] Figure 6 This is a schematic diagram of an enterprise account and data processing system illustrated in an exemplary embodiment of this application;

[0029] Figure 7 Based on Figure 2The diagram shows the interaction flow of the implementation environment in an exemplary embodiment.

[0030] Figure 8 This is a block diagram illustrating a blockchain-based data processing apparatus as shown in an exemplary embodiment of this application;

[0031] Figure 9 This is a schematic diagram of the structure of an electronic device shown in an exemplary embodiment of this application. Detailed Implementation

[0032] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application as detailed in the appended claims.

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

[0034] The flowcharts shown in the accompanying drawings are merely illustrative and do not necessarily include all content and operations / steps, nor do they necessarily have to be performed in the described order. For example, some operations / steps can be broken down, while others can be combined or partially combined; therefore, the actual execution order may change depending on the specific circumstances.

[0035] It should also be noted that "multiple" as mentioned in this application refers to two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, or B alone. The character " / " generally indicates that the preceding and following related objects have an "or" relationship.

[0036] Before introducing the technical solutions of the embodiments of this application, the nouns and terms involved in the embodiments of this application will be explained first. The nouns and terms involved in the embodiments of this application are subject to the following interpretations.

[0037] 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 together 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 to generate the next block.

[0038] A smart contract is a computer protocol designed to disseminate, verify, or execute contracts in an informational manner. It can automatically execute the "if this happens, then execute that result" code found in traditional contracts. Developers can define contract logic using a programming language, publish it on the blockchain (contract registration), and execute it by calling keys or other events according to the contract terms to complete the contract logic. Contracts can be upgraded or cancelled.

[0039] Blockchain is a decentralized database with features such as immutability, traceability, tamper-proofness, and collective maintenance, enhancing data credibility and helping enterprises build trustworthy data. However, among related technologies, blockchain-based data processing methods have relatively low flexibility and a low degree of matching with enterprise needs. Therefore, this application proposes a blockchain-based data processing method, system, device, electronic device, and storage medium, enabling enterprises to utilize blockchain technology and meeting their needs for management permissions and business isolation.

[0040] Please see Figure 1 , Figure 1 This is a schematic diagram illustrating an implementation environment in an exemplary embodiment of this application. The implementation environment includes a business node 11 and a blockchain node 12.

[0041] Among them, business node 11 can be any electronic device that can acquire and process data processing requests, such as smartphones, tablets, laptops, computers, and servers.

[0042] Blockchain node 12 is a node in the blockchain system used to maintain the blockchain. Blockchain node 12 can be an electronic device such as a server.

[0043] In this embodiment, the business node 11 faces the user and can obtain data processing requests initiated by the business account. Based on the data processing request, it can obtain the blockchain node account bound to the business account and send the data to be processed contained in the data processing request to the blockchain node 12 corresponding to the blockchain node account. The blockchain nodes corresponding to different blockchain node accounts belong to different blockchain systems, and each blockchain system maintains a different blockchain.

[0044] After receiving the data to be processed sent by the business node 11, the corresponding blockchain node 12 initiates the processing operation of the corresponding data to be processed in its own blockchain system.

[0045] In this way, on the one hand, by binding blockchain node accounts to business accounts, enterprises can use blockchain technology. Furthermore, the relevant programs for binding blockchain node accounts to business accounts can be added to the existing enterprise business system, thereby enabling the storage of business data in the blockchain without changing the entire enterprise business system, thus reducing the cost of using blockchain for enterprises. On the other hand, the blockchain nodes corresponding to different blockchain node accounts belong to different blockchain systems, thereby separating business data stored in different blockchain systems to meet the needs of enterprises for management permissions and business isolation.

[0046] Please see Figure 2 , Figure 2 This is a schematic diagram illustrating an implementation environment in another exemplary embodiment of this application, wherein the implementation environment is... Figure 1 The implementation environment shown also includes an account management node 13. The account management node 13 can be an electronic device such as a smartphone, tablet, laptop, computer, or server.

[0047] It should be noted that the aforementioned server can be an independent physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides 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 (Content Delivery Network), and big data and artificial intelligence platforms. This document does not impose any restrictions on these aspects.

[0048] In this embodiment, the account management node 13 can create a corresponding business account based on the business account creation request initiated by the management account, and then configure the corresponding blockchain node account for the created business account based on the business account configuration request initiated by the management account, and generate an account binding relationship between the business account and the blockchain node account. The account binding relationship is then sent to the business node 11, so that after the business node 11 obtains the data processing request initiated by the business account, it can obtain the blockchain node account bound to the business account based on the account binding relationship.

[0049] It should be noted that, Figure 1 and Figure 2 The number of business nodes 11, blockchain nodes 12, and account management nodes 13 shown in this example is merely illustrative. Any number of business nodes 11, blockchain nodes 12, and account management nodes 13 can be used as needed.

[0050] Figure 3 This is a flowchart illustrating a blockchain-based data processing method according to an exemplary embodiment. This method can be applied to... Figure 1 or Figure 2 The implementation environment shown, and by Figure 1 or Figure 2 The business node 11 in the implementation environment shown is specifically executed.

[0051] like Figure 3 As shown in an exemplary embodiment, the blockchain-based data processing method may include steps S110 to S130, which are described in detail below:

[0052] Step S110: The business node obtains the data processing request initiated by the business account.

[0053] It should be noted that different companies have different business operations, and different business operations generate different business data. Even within the same company, different business operations may exist. For example, see [link to relevant documentation]. Figure 4 As shown, a company includes a production department, a purchasing department, a sales department, an accounting department, and an administration department. The production department is primarily responsible for production operations, generating mainly production-related data. The production department can include a technical department, a quality assurance department, and an equipment department. The equipment department can further include workshops, production line 1, production line 2, and production line 3. The sales department is primarily responsible for sales operations, generating mainly sales data. The sales department can further include sales division 1, sales division 2, etc. The accounting department is primarily responsible for financial recording operations, generating mainly financial data. The accounting department can include a warehouse expense management department and a financial management department. The financial management department can further include a tax department, an audit department, and a treasury department. It is evident that different departments have different business operations and generate different business data.

[0054] To differentiate between different services, this embodiment sets up service accounts, which include service identification information to determine which service a data or operation belongs to. For ease of parsing or reading by electronic devices, the service identification information can be a service ID (Identity Document).

[0055] Business nodes are used to obtain data processing requests initiated by business accounts.

[0056] Among these, business nodes can be user-facing, providing services such as business data processing. Users can operate on the platform provided by the business node (which can be a web page, mini-program, etc.) to initiate data processing requests for a specific business account. The business node then receives the data processing requests initiated based on that business account. To facilitate the business node's determination of which business the data processing request belongs to, the data processing request may include the business account's identification information.

[0057] Step S120: The business node obtains the blockchain node account bound to the business account based on the data processing request.

[0058] In this context, different blockchain node accounts correspond to blockchain nodes belonging to different blockchain systems, and each blockchain system maintains its own blockchain.

[0059] It should be noted that in this embodiment, a corresponding blockchain node account is configured for each business account, and an account binding relationship is obtained based on the business account and its corresponding blockchain node account, so that the business data corresponding to the business account can be stored in the blockchain. In the account binding relationship, the blockchain nodes corresponding to different blockchain node accounts belong to different blockchain systems, and different blockchain systems maintain different blockchains, so as to isolate the business data corresponding to different blockchain node accounts. In order to isolate the business data corresponding to different businesses and thus realize the permission control of operators in different business scenarios, the blockchain node accounts corresponding to different business accounts can be different, so that the business data of different business accounts are stored in different blockchains; of course, in one example, the blockchain node accounts corresponding to different business accounts can also be the same, that is, the business data of different business accounts can be stored in the same blockchain. For example, assuming there are 3 business accounts, denoted as y1, y2, and y3, the blockchain node account bound to y1 and y2 is q1, and the blockchain node account bound to y3 is q2, then the business data corresponding to y1 and y2 is stored in one blockchain, and the business data corresponding to y3 is stored in another blockchain, thus isolating the business data of y1 and y3.

[0060] In this embodiment, after obtaining the data processing request initiated by the business account, the blockchain node account bound to the business account is obtained based on the data processing request.

[0061] In step S130, the business node sends the data to be processed contained in the data processing request to the blockchain node corresponding to the blockchain node account, so that the blockchain node initiates the processing operation of the data to be processed in its own blockchain system.

[0062] After a business node receives a data processing request initiated by a business account and obtains the blockchain node account bound to that business account based on the data processing request, it sends the data to be processed contained in the data processing request to the blockchain node corresponding to the obtained blockchain node account. After receiving the data to be processed sent by the business node, the corresponding blockchain node initiates the processing operation for the data to be processed in its own blockchain system. For example, referring to Table 1, assume there are business accounts A1 and A2. The blockchain node account configured for business account A1 corresponds to blockchain node b1, and the blockchain node account configured for business account A2 corresponds to blockchain node c2. Blockchain node b1 belongs to blockchain system B, and blockchain node c3 belongs to blockchain system C. Blockchain system B maintains blockchain BL, and blockchain system C maintains blockchain EL. If a business node receives data processing request 1 initiated by A1, it determines that the blockchain node corresponding to the blockchain node account bound to A1 is b1. The business node sends the data to be processed contained in data processing request 1 to blockchain node b1, and blockchain node b1 initiates the corresponding processing operation for the data to be processed in blockchain system B. If a business node receives data processing request 2 initiated by A2, it determines that the blockchain node corresponding to the blockchain node account bound to A2 is c3, and the business node sends the data to be processed contained in data processing request 2 to blockchain node c3. Blockchain node c3 initiates the corresponding processing operation for the data to be processed in blockchain system C.

[0063] A1 b1 B BL A2 c3 C EL

[0064] Table 1

[0065] In this embodiment, on the one hand, by binding a blockchain node account to a business account, the enterprise can use blockchain technology. Furthermore, the relevant program for binding a blockchain node account to a business account can be added to the existing enterprise business system, thereby enabling the storage of business data in the blockchain without changing the entire enterprise business system, thus reducing the cost of using blockchain for the enterprise. On the other hand, the blockchain nodes corresponding to different blockchain node accounts belong to different blockchain systems, thereby separating the business data stored in different blockchain systems to meet the enterprise's needs for permissions and business isolation in management.

[0066] In one exemplary embodiment, in Figure 3 Before step S120 shown, the method further includes step S140, which is described in detail below:

[0067] Step S140: The business node obtains the account binding relationship from the account management node, and obtains the blockchain node account bound to the business account based on the account binding relationship.

[0068] The account binding relationship is obtained by the account management node creating the corresponding business account based on the business account creation request initiated by the management account, and then configuring the corresponding blockchain node account for the created business account based on the business account configuration request initiated by the management account.

[0069] It should be noted that the management account is used to identify different users, and the management account has the authority to create and configure business accounts. Users can initiate a business account creation request on the account management node based on the management account. After receiving the business account creation request, the account management node creates the corresponding business account based on the request. Users can also initiate a business account configuration request on the account management node based on the management account. After receiving the business account configuration request, the account management node configures the corresponding blockchain node account for the created business account based on the business account configuration request, and obtains the account binding relationship based on the business account and the corresponding blockchain node account.

[0070] The account management node can send the account binding relationship to the business node. The business node obtains the account binding relationship from the account management node and then obtains the blockchain node account bound to the business account corresponding to the data processing request based on the account binding relationship.

[0071] In this embodiment, business accounts can be created based on management accounts and corresponding blockchain node accounts can be configured for business accounts. This allows enterprise managers to flexibly allocate business accounts and blockchain node accounts for various business scenarios, thereby achieving isolation between multiple scenarios and access control for operators in different business scenarios.

[0072] See Figure 5 , Figure 5 This is a flowchart illustrating a blockchain-based data processing method according to another exemplary embodiment. Figure 5 As shown, in Figure 3 Before step S130 shown, the method further includes steps S150-S170, which are detailed below:

[0073] In step S150, the business node obtains the public key corresponding to the business account based on the data processing request.

[0074] It should be noted that in this embodiment, a corresponding public key is configured for each business account for communication authentication.

[0075] After receiving a data processing request initiated by a business account, the business node obtains the public key corresponding to that business account based on the data processing request.

[0076] Step S160: The business node verifies the signature contained in the data processing request based on the public key.

[0077] The signature contained in the data processing request is generated based on the private key corresponding to the business account.

[0078] It should be noted that when generating a data processing request, the request is signed using the private key corresponding to the business account for communication authentication. After receiving the data processing request initiated by the business account and obtaining the public key corresponding to that business account based on the data processing request, the business node verifies the signature contained in the data processing request using the obtained public key.

[0079] Step S170: If the signature passes verification, the business node will execute the step of sending the data to be processed contained in the data processing request to the blockchain node corresponding to the blockchain node account.

[0080] If the signature of the data processing request passes verification, authentication is successful. The business node then executes the step of sending the data to be processed contained in the data processing request to the blockchain node corresponding to the blockchain node account. That is, when the signature of the data processing request passes verification, the following steps are executed. Figure 3 The step S130 shown.

[0081] In this embodiment, the service node verifies the data processing request based on the public key before processing it, thereby improving security.

[0082] In another exemplary embodiment, Figure 5 Before step S150, the method further includes steps S210-S220. Details are as follows:

[0083] Step S210: Receive the key mapping relationship sent by the account management node.

[0084] The key mapping relationship includes the public key associated with the business account. The account management node creates the private key and public key for the business account based on the key creation request initiated by the management account.

[0085] It should be noted that the management account also has the authority to configure keys for business accounts. Users can initiate a key creation request through the management account on the account management node. After receiving the request, the account management node creates a private and public key pair for each business account, and establishes a key mapping relationship based on the business account and its corresponding public key. The account management node then sends this key mapping relationship to the business node, which in turn receives it. Different private and public keys can be created for different business accounts to further enhance security.

[0086] Step S220: Store the key mapping relationship locally to obtain the public key corresponding to the business account based on the key mapping relationship.

[0087] After receiving the key mapping relationship, the account management node stores it locally so that it can subsequently retrieve the public key corresponding to the business account that initiated the data processing request based on the locally stored key mapping relationship.

[0088] In this embodiment, a public key can be configured for a business account based on the management account, thereby improving management flexibility.

[0089] In another exemplary embodiment, Figure 3 Before step S130 shown, the method further includes steps S310-S320, which are described in detail below:

[0090] Step S310: The business node compares the blockchain node account contained in the data processing request with the blockchain node account bound to the business account.

[0091] In this embodiment, the data processing request contains a blockchain node account. After receiving the data processing request initiated by the business account, the business node compares the blockchain node account bound to the business account with the blockchain node account contained in the data processing request to verify whether the binding relationship between the business account and the blockchain node account in the data processing request is correct.

[0092] Step S320: If the two are the same, the business node executes the step of sending the data to be processed contained in the data processing request to the blockchain node corresponding to the blockchain node account.

[0093] If the blockchain node account contained in the data processing request is the same as the blockchain node account bound to the business account, then the step of sending the data to be processed contained in the data processing request to the blockchain node corresponding to the blockchain node account is executed. Figure 3 The step S130 shown.

[0094] In this embodiment, after receiving a data processing request initiated by a business account, the blockchain node account bound to the business account is compared with the blockchain node account contained in the data processing request. Only when the two are the same will the data to be processed contained in the data processing request be sent to the blockchain node corresponding to the blockchain node account, thereby improving the security of data processing.

[0095] In another exemplary embodiment, where the type of data processing request includes a data uploading request, and the data to be processed contained in the data processing request includes data to be uploaded to the blockchain, Figure 3The step S130 shown includes: the business node sends the data to be uploaded to the blockchain contained in the data processing request to the blockchain node corresponding to the blockchain node account, so that the blockchain node stores the data to be uploaded to the blockchain maintained by the blockchain system to which it belongs.

[0096] When the data processing request type is a data upload request, the business node sends the data to be uploaded to the blockchain node corresponding to the blockchain node account. After receiving the data to be uploaded to the blockchain node, the blockchain node stores the data to be uploaded to the blockchain maintained by its own blockchain system, thus realizing the upload of business data to the blockchain. For example, as shown in Table 1, assuming a business node receives a data upload request initiated by business account A1, the business node sends the data to be uploaded to the blockchain node b1. Blockchain node b1 stores the received data to be uploaded to its local blockchain BL and triggers a consensus mechanism in blockchain system B, so that other blockchain nodes in blockchain system B also store the data to be uploaded to their own blockchain BL, thereby ensuring that the data stored by each blockchain node in blockchain system B is consistent.

[0097] In another exemplary embodiment, where the type of data processing request includes a data query request, and the data to be processed contained in the data processing request includes identification information of the data to be queried, Figure 3 Step S130 shown includes steps S131-S132, which are described in detail below:

[0098] In step S131, the business node sends the identification information of the data to be queried contained in the data processing request to the blockchain node corresponding to the blockchain node account, so that the blockchain node can query the result data corresponding to the identification information of the data to be queried from the locally stored blockchain.

[0099] If the data processing request is a data query request, the business node sends the identification information of the data to be queried contained in the data query request to the corresponding blockchain node. After receiving the identification information of the data to be queried, the blockchain node performs a query in the locally stored blockchain based on the identification information of the data to be queried and obtains the result data.

[0100] Step S132: The business node obtains the result data returned by the blockchain node in response to the data processing request.

[0101] Business nodes obtain the result data returned by blockchain nodes in response to data query requests, thereby enabling the querying of business data on the blockchain.

[0102] For example, as shown in Table 1, assuming that a business node receives a data upload request initiated by business account A2, the business node sends the identifier information of the data to be queried contained in the data query request to blockchain node c3. Blockchain node c3 queries the result data corresponding to the identifier information of the data to be queried from the locally stored blockchain CL, and sends the result data to the business node. The business node then receives the result data sent by blockchain node c3.

[0103] It should be noted that blockchain nodes can also save this query record and initiate a consensus mechanism in their respective blockchain systems so that other blockchain nodes in their respective blockchain systems also save this query record.

[0104] Embodiments of this application also provide a blockchain-based data processing system, which includes: business nodes and blockchain nodes.

[0105] Specifically, the business node obtains the data processing request initiated by the business account, and obtains the blockchain node account bound to the business account based on the data processing request, and sends the data to be processed contained in the data processing request to the blockchain node corresponding to the blockchain node account; wherein, the blockchain nodes corresponding to different blockchain node accounts belong to different blockchain systems, and different blockchain systems maintain different blockchains.

[0106] Blockchain nodes receive pending data sent by business nodes and initiate processing operations on the pending data within their respective blockchain systems.

[0107] It should be noted that business nodes and blockchain nodes can also perform other steps in the aforementioned method, which will not be elaborated here.

[0108] In another exemplary embodiment, the system further includes an account management node. The account management node creates a corresponding business account based on a business account creation request initiated by a management account, and configures a corresponding blockchain node account for the created business account based on a business account configuration request initiated by the management account, thereby generating an account binding relationship between the business account and the blockchain node account. The account binding relationship is then sent to the business node, enabling the business node to obtain the blockchain node account bound to the business account based on the account binding relationship.

[0109] In this embodiment, the management account has the authority to create business accounts. After logging into the management account on the account management node, the user can initiate a business account creation request to the account management node based on the logged-in management account, and the account management node creates the business account based on the business account creation request.

[0110] To enable the business transactions corresponding to the business accounts to utilize blockchain technology, in this embodiment, the management account also has the authority to configure blockchain accounts for the business accounts. Users can initiate a business account configuration request to the account management node based on their logged-in management account. The account management node then generates an account binding relationship between the business account and the blockchain node account based on the business account configuration request. The business account configuration request can include the created business account and its corresponding blockchain account, allowing the account management node to generate the account binding relationship based on the business account parsed from the configuration request and its corresponding blockchain account.

[0111] In another exemplary embodiment, the account management node can also create a private key and a public key corresponding to the business account based on the key creation request initiated by the management account, generate a key mapping relationship based on the public key corresponding to the business account, and send the key mapping relationship to the corresponding business node so that the business node can obtain the public key corresponding to the business account based on the key mapping relationship.

[0112] In this embodiment, the management account also has the authority to configure public keys for business accounts. Users can initiate a key creation request for a business account to the account management node based on their logged-in management account. The account management node creates a public and private key corresponding to the business account based on the key creation request. Users can save the private key themselves. For the public key, the account management node can generate a key mapping relationship based on the business account and its corresponding public key, and send the key mapping relationship to the corresponding business node, enabling the business node to perform communication authentication based on the key mapping relationship. That is, after receiving a data processing request initiated by a business account, the business node can first look up the public key corresponding to that business account in the key mapping relationship, verify the signature of the data processing request based on the found public key, and then process the data processing request after the signature verification is successful. The signature of the data processing request is generated based on the private key corresponding to the business account.

[0113] In another exemplary embodiment, the account management node can also create a private key and a public key corresponding to the blockchain node account based on the blockchain node account creation request initiated by the management account, send the created public key to the blockchain system so that the blockchain system can create a blockchain node account based on the public key, and send the created blockchain node account to the account management node. The account management node outputs the blockchain node account for the user to select.

[0114] In this embodiment, the management account also has the authority to create blockchain node accounts, thus enabling the creation of blockchain node accounts through the management account.

[0115] In another exemplary embodiment, the management accounts logged in to the account management node include a general management account and management sub-accounts. The account management node also creates at least one management sub-account based on a sub-account creation request initiated by the general management account, and configures management permissions for at least one management sub-account.

[0116] For ease of management, in this embodiment, the management account includes a master management account and management sub-accounts. The master management account has permissions including, but not limited to, creating management sub-accounts and configuring management permissions for management sub-accounts. The management permissions configured for management sub-accounts include, but are not limited to, at least one of the following: permission to create business accounts, permission to configure blockchain accounts for business accounts, permission to configure public keys for business accounts, and permission to create blockchain node accounts.

[0117] In this embodiment, the blockchain-based data processing system can provide services to enterprise-level users. For example, see... Figure 6 As shown, to facilitate enterprise management, an enterprise management account layer, an enterprise business account layer, and an enterprise blockchain node account layer are set up. The enterprise management account layer includes a main management account and management sub-accounts (management sub-account 1, management sub-account 2, etc.). The enterprise business account layer includes business accounts (business account 1, business account 2, business account 3, etc.). The enterprise blockchain node account layer includes blockchain node accounts (blockchain node account 1, blockchain node account 2, blockchain node account 3, etc.).

[0118] Enterprises can register on the account management node. After registration, the account management node will assign a unique identifier to the enterprise as its primary management account. The account management node can also store the mapping relationship between the primary management account and the enterprise identifier to identify which enterprise the primary management account belongs to. The enterprise identifier is a unique identifier for the enterprise during its operation and includes, but is not limited to, at least one of the following: the enterprise name, taxpayer identification number, unified social credit code, and business registration number.

[0119] To manage the main account and sub-accounts, you can log in at the account management node.

[0120] The master management account can create and manage sub-accounts and configure permissions for them. For example, the master management account can cancel business accounts and configure management permissions for them. Therefore, after registering a master management account, a company can log in to it through the platform provided by the account management node (which can be a web page or an application, etc.) and, based on its internal organizational structure and needs, initiate a sub-account creation request to the account management node. The account management node then creates the sub-accounts and configures the corresponding permissions. For example, assuming Company A has three branch offices, Company A can log in to the master management account through the platform provided by the account management node and create three sub-accounts for managing the three branch offices respectively; or, see [link to relevant documentation]. Figure 4 As shown, after logging into the main management account on the platform provided by the account management node, the company can create five management sub-accounts through the account management node, which are used for the management of the production department, purchasing department, sales department, accounting department and administration department respectively.

[0121] The master account can also have the authority to create blockchain node accounts. After logging into the master account on the account management node, the master account can initiate a blockchain node account creation request to the account management node. The account management node creates the blockchain node account based on the blockchain node account creation request. For the specific creation process, please refer to the above description.

[0122] The management permissions configured for the sub-account include, but are not limited to, at least one of the following: permission to create business accounts, permission to configure blockchain accounts for business accounts, permission to configure public keys for business accounts, and permission to create blockchain node accounts. Therefore, after logging into the sub-account on the platform provided by the account management node, users can initiate requests for business account creation, business account configuration, key creation, and blockchain node account creation within the account management node based on internal business needs. The account management node creates business accounts based on business account creation requests; it creates blockchain node accounts based on blockchain node account creation requests; it configures corresponding blockchain node accounts for the created business accounts based on business account configuration requests and generates account binding relationships between business accounts and blockchain node accounts; and it creates private and public keys corresponding to business accounts based on key creation requests and generates key mapping relationships based on the public keys of business accounts. For example, see... Figure 4 As shown, after logging into its corresponding management sub-account, the sales department can initiate a business creation request based on the management sub-account to create two business accounts, and configure blockchain node accounts and public keys for these two business accounts respectively, for use in sales division 1 and sales division 2.

[0123] A business account serves as an identity identifier during interactions with business nodes. Business nodes use the business account as a communication identity for authentication, without needing to be aware of the enterprise management account layer. Therefore, upon receiving a data processing request initiated by a business account, the business node retrieves the blockchain node account bound to that business account and the corresponding public key from the account binding and key mapping relationships. It then uses the retrieved blockchain node account and public key to authenticate the data processing request. For details, please refer to the aforementioned description.

[0124] A blockchain node account serves as an identity identifier within the blockchain system, allowing the retrieval of the corresponding blockchain node. Blockchain nodes are used to authenticate data to be uploaded to the blockchain.

[0125] It should be noted that blockchain node accounts can all belong to the main management account, or they can belong to their corresponding sub-management accounts.

[0126] See Figure 7 , Figure 7 Based on Figure 2 The diagram illustrates the interaction flow of the implementation environment in an exemplary embodiment. Figure 7 As shown, the main steps include the following:

[0127] Step S701: The account management node creates at least one management sub-account based on the sub-account creation request initiated by the main management account, and configures management permissions for at least one management sub-account.

[0128] After logging into the main management account on the platform provided by the account management node, the user initiates a sub-account creation request based on the main management account. The account management node creates at least one management sub-account according to the sub-account creation request and configures management permissions for at least one management sub-account.

[0129] In step S702, the account management node creates a corresponding business account based on the business account creation request initiated by the management sub-account, and configures the corresponding blockchain node account for the created business account based on the business account configuration request initiated by the management sub-account, thereby generating an account binding relationship between the business account and the blockchain node account.

[0130] The management sub-account has the permissions to create and configure business accounts. After logging into the management sub-account on the platform provided by the account management node, the user initiates a business account creation request and a business account configuration request based on the management sub-account. The account management node creates the corresponding business account based on the business account creation request and configures the corresponding blockchain node account for the created business account based on the business account configuration request, thereby generating an account binding relationship between the business account and the blockchain node account.

[0131] In step S703, the account management node sends the account binding relationship to the business node.

[0132] In step S704, the account management node creates the private key and public key corresponding to the business account based on the key creation request initiated by the management sub-account, and generates a key mapping relationship based on the public key corresponding to the business account.

[0133] The management sub-account has the authority to configure public keys for business accounts. After logging into the management sub-account on the platform provided by the account management node, the user initiates a key creation request based on the management sub-account. The account management node creates the private and public keys corresponding to the business account based on the key creation request, and generates a key mapping relationship based on the public key corresponding to the business account.

[0134] In step S705, the account management node sends the key mapping relationship to the corresponding business node.

[0135] Step S706: The business node obtains the data processing request initiated by the business account.

[0136] Step S707: The business node obtains the blockchain node account bound to the business account and the public key corresponding to the business account based on the data processing request.

[0137] In this context, different blockchain node accounts correspond to blockchain nodes belonging to different blockchain systems, and each blockchain system maintains its own blockchain.

[0138] After a business node receives a data processing request initiated by a business account, it retrieves the blockchain node account bound to that business account from the received account binding relationship and obtains the public key corresponding to that business account from the received key mapping relationship.

[0139] Step S708: The business node verifies the signature contained in the data processing request based on the public key, and compares the blockchain node account contained in the data processing request with the blockchain node account bound to the business account.

[0140] The signature contained in the data processing request is generated based on the private key corresponding to the business account.

[0141] The business node obtains the data processing request initiated by the business account, and after obtaining the blockchain node account bound to the business account and the public key corresponding to the business account, it verifies the signature in the data processing request based on the obtained public key, and compares the blockchain node account contained in the data processing request with the blockchain node account bound to the business account.

[0142] Step S709: If the verification is successful and the two blockchain node accounts are the same, the business node will send the data to be processed contained in the data processing request to the blockchain node corresponding to the blockchain node account.

[0143] If the signature verification of the data processing request passes, and the blockchain node account contained in the data processing request is the same as the blockchain node account bound to the business account, then the business node will send the data to be processed contained in the data processing request to the blockchain node corresponding to the blockchain node account.

[0144] Step S710: The blockchain node initiates a processing operation on the data to be processed within its own blockchain system.

[0145] It should be noted that the detailed processes involved in steps S701 to S710 above have been described in the aforementioned embodiments, and therefore will not be repeated here.

[0146] In this embodiment, a master management account, sub-management accounts, business accounts, and blockchain node accounts are set up to provide a complete solution for enterprises to join the blockchain platform. Enterprises can flexibly manage account permissions and ensure the reliable on-chaining of business data based on their own management and business characteristics.

[0147] Figure 8 This is a block diagram illustrating a blockchain-based data processing apparatus according to an exemplary embodiment of this application. The apparatus includes:

[0148] The first acquisition module 801 is configured to acquire data processing requests initiated by business accounts; the second acquisition module 802 is configured to acquire the blockchain node accounts bound to the business accounts based on the data processing requests, wherein the blockchain nodes corresponding to different blockchain node accounts belong to different blockchain systems, and different blockchain systems maintain different blockchains; the sending module 803 is configured to send the data to be processed contained in the data processing request to the blockchain node corresponding to the blockchain node account, so that the blockchain node initiates processing operations on the data to be processed in its own blockchain system.

[0149] The apparatus provided in this embodiment, on the one hand, enables enterprises to use blockchain technology by binding blockchain node accounts to business accounts. Furthermore, the relevant program for binding blockchain node accounts to business accounts can be added to the existing enterprise business system, thereby enabling the storage of business data in the blockchain without changing the entire enterprise business system, thus reducing the cost of using blockchain for enterprises. On the other hand, the blockchain nodes corresponding to different blockchain node accounts belong to different blockchain systems, thereby separating business data stored in different blockchain systems to meet the needs of enterprises for management permissions and business isolation.

[0150] In another exemplary embodiment, the device further includes:

[0151] The third acquisition module is configured to acquire the account binding relationship from the account management node, so as to obtain the blockchain node account bound to the business account based on the account binding relationship; wherein, the account binding relationship is obtained by the account management node after creating the corresponding business account based on the business account creation request initiated by the management account, and configuring the corresponding blockchain node account for the created business account based on the business account configuration request initiated by the management account.

[0152] In another exemplary embodiment, the device further includes:

[0153] The fourth acquisition module is configured to obtain the public key corresponding to the business account based on the data processing request.

[0154] The verification module is configured to verify the signature contained in the data processing request based on the public key; the signature contained in the data processing request is generated based on the private key corresponding to the business account.

[0155] The first control module is configured to, if the signature passes verification, control the sending module 803 to execute the step of sending the data to be processed contained in the data processing request to the blockchain node corresponding to the blockchain node account.

[0156] In another exemplary embodiment, the device further includes:

[0157] The receiving module is configured to receive key mapping relationships sent by the account management node. The key mapping relationship includes the public key associated with the business account. The account management node creates a private key and a public key for the business account based on the key creation request initiated by the management account.

[0158] The storage module is configured to store the key mapping relationship locally in order to obtain the public key corresponding to the business account based on the key mapping relationship.

[0159] In another exemplary embodiment, the device further includes:

[0160] The comparison module is configured to compare the blockchain node account contained in the data processing request with the blockchain node account bound to the business account.

[0161] The first control module is configured such that if the two are the same, the sending module 803 will execute the step of sending the data to be processed contained in the data processing request to the blockchain node corresponding to the blockchain node account.

[0162] In another exemplary embodiment, where the type of data processing request includes a data uplink request, and the data to be processed contained in the data processing request includes data to be uplinked, the sending module 803 includes:

[0163] The first sending submodule is configured to send the data to be uploaded to the blockchain contained in the data processing request to the blockchain node corresponding to the blockchain node account, so that the blockchain node stores the data to be uploaded to the blockchain maintained by the blockchain system to which it belongs.

[0164] In another exemplary embodiment, where the type of data processing request includes a data query request, and the data to be processed contained in the data processing request includes identification information of the data to be queried, the sending module 803 includes:

[0165] The second sending submodule is configured to send the identification information of the data to be queried contained in the data processing request to the blockchain node corresponding to the blockchain node account, so that the blockchain node can query the result data corresponding to the identification information of the data to be queried from the locally stored blockchain.

[0166] The result acquisition module is configured to acquire the result data returned by the blockchain node in response to the data processing request.

[0167] Embodiments of this application also provide an electronic device, including a storage device and one or more processors; wherein the storage device is used to store one or more programs, which, when executed by one or more processors, cause the electronic device to perform the method described above.

[0168] Figure 9 This is a schematic diagram of the structure of an electronic device according to an exemplary embodiment.

[0169] It should be noted that this electronic device is merely an example adapted to this application and should not be construed as providing any limitation on the scope of use of this application. Furthermore, this electronic device should not be interpreted as requiring or depending on any specific feature. Figure 9 One or more components of the exemplary electronic device shown.

[0170] like Figure 9 As shown, in an exemplary embodiment, the electronic device includes a processing component 901, a memory 902, a power supply component 903, a multimedia component 904, an audio component 905, a sensor component 907, and a communication component 908. Not all of these components are mandatory; the electronic device may add or remove other components according to its functional requirements, and this embodiment does not impose any limitations.

[0171] Processing component 901 typically controls the overall operation of an electronic device, such as operations associated with display, data communication, and log data processing. Processing component 901 may include one or more processors 909 to execute instructions to complete all or part of the aforementioned operations. Furthermore, processing component 901 may include one or more modules to facilitate interaction between processing component 901 and other components. For example, processing component 901 may include a multimedia module to facilitate interaction between multimedia component 904 and processing component 901.

[0172] The memory 902 is configured to store various types of data to support operation of the electronic device, examples of which include instructions for any application or method operating on the electronic device. The memory 902 stores one or more modules configured to be executed by the one or more processors 909 to perform all or part of the steps in the methods described in the above embodiments.

[0173] Power supply component 903 provides power to various components of an electronic device. Power supply component 903 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power to the electronic device.

[0174] Multimedia component 904 includes a screen that provides an output interface between an electronic device and a user. In some embodiments, the screen may include a TP (Touch Panel) and an LCD (Liquid Crystal Display). If the screen includes a touch panel, the screen can be implemented as a touchscreen to receive input signals from the user. The touch panel includes one or more touch sensors to sense touches, swipes, and gestures on the touch panel. The touch sensors can sense not only the boundaries of the touch or swipe action but also the duration and pressure associated with the touch or swipe operation.

[0175] Audio component 905 is configured to output and / or input audio signals. For example, audio component 905 includes a microphone configured to receive external audio signals when the electronic device is in an operating mode, such as call mode, recording mode, and voice recognition mode. In some embodiments, audio component 905 also includes a speaker for outputting audio signals.

[0176] Sensor assembly 907 includes one or more sensors for providing state assessments of various aspects of the electronic device. For example, sensor assembly 907 can detect the on / off state of the electronic device and can also detect temperature changes in the electronic device.

[0177] Communication component 908 is configured to facilitate wired or wireless communication between electronic devices and other devices. Electronic devices can access wireless networks based on communication standards, such as Wi-Fi (Wireless-Fidelity).

[0178] Understandable. Figure 9 The structure shown is for illustrative purposes only; the electronic device may include components such as... Figure 9 The more or fewer components shown, or having the same Figure 9 The different components are shown. Figure 9 Each component shown can be implemented using hardware, software, or a combination thereof.

[0179] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this application. Each block in a flowchart or block diagram may represent a module, segment, or portion of code, which contains one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in a block diagram or flowchart, and combinations of blocks in a block diagram or flowchart, can be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0180] The units described in the embodiments of this application can be implemented in software or hardware, and the described units can also be located in a processor. The names of these units do not necessarily limit the specific unit itself.

[0181] Another aspect of this application provides a computer-readable storage medium having a computer program stored thereon that, when executed by a processor, implements the method described above. This computer-readable storage medium may be included in the electronic device described in the above embodiments, or it may exist independently and not assembled into the electronic device.

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

[0183] Another aspect of this application provides a computer program product or computer program including 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 embodiments described above.

[0184] The above description is merely a preferred exemplary embodiment of this application and is not intended to limit the implementation of this application. Those skilled in the art can easily make corresponding modifications or alterations based on the main concept and spirit of this application. Therefore, the scope of protection of this application should be determined by the scope of protection claimed in the claims.

Claims

1. A data processing method based on blockchain, characterized in that, The method includes: An account management node, independent of business nodes and blockchain nodes, responds to the enterprise's registration operation by assigning a unique identifier to the enterprise as its main management account; based on the sub-account creation request initiated by the main management account, it creates at least one management sub-account corresponding to the main management account and configures management permissions for the at least one management sub-account. The account management node creates business accounts to identify different businesses of the enterprise based on business account creation requests initiated by the main management account or the management sub-account, and configures corresponding blockchain node accounts for the created business accounts based on business account configuration requests initiated by the main management account or the management sub-account, generating an account binding relationship between the business accounts and the blockchain node accounts, and sending the account binding relationship to the business node; in response to key creation requests initiated by the main management account or the management sub-account, it creates public and private keys corresponding to the business accounts, generates a key mapping relationship based on the business accounts and the public keys corresponding to the business accounts, and sends the key mapping relationship to the business node; The business node obtains the data processing request initiated by the business account; Based on the data processing request, the business node obtains the blockchain node account bound to the business account from the received account binding relationship. Different blockchain node accounts correspond to blockchain nodes belonging to different blockchain systems. Each of the different blockchain systems maintains a different blockchain, and different business accounts correspond to different blockchain systems through the bound blockchain node accounts. Based on the data processing request, the business node obtains the public key corresponding to the business account from the key mapping relationship, and verifies the signature contained in the data processing request based on the obtained public key. The signature is generated based on the private key corresponding to the business account. If the signature passes verification, the data to be processed contained in the data processing request is sent to the blockchain node corresponding to the blockchain node account, so that the blockchain node initiates the processing operation of the data to be processed in its own blockchain system.

2. The method as described in claim 1, characterized in that, The method further includes: The business node receives the key mapping relationship sent by the account management node and stores the key mapping relationship locally in order to obtain the public key corresponding to the business account based on the key mapping relationship.

3. The method as described in claim 1, characterized in that, Before sending the data to be processed contained in the data processing request to the blockchain node corresponding to the blockchain node account, the method further includes: The business node compares the blockchain node account contained in the data processing request with the blockchain node account bound to the business account. If the two are the same, then the step of sending the data to be processed contained in the data processing request to the blockchain node corresponding to the blockchain node account is performed.

4. The method as described in claim 1, characterized in that, The data processing request type includes a data upload request, and the data to be processed contained in the data processing request includes data to be uploaded to the blockchain; the step of sending the data to be processed contained in the data processing request to the blockchain node corresponding to the blockchain node account, so that the blockchain node initiates a processing operation on the data to be processed in its own blockchain system, includes: The business node sends the data to be uploaded to the blockchain contained in the data processing request to the blockchain node corresponding to the blockchain node account, so that the blockchain node stores the data to be uploaded to the blockchain maintained by its own blockchain system.

5. The method as described in claim 1, characterized in that, The data processing request type includes a data query request, and the data to be processed contained in the data processing request includes the identification information of the data to be queried; the step of sending the data to be processed contained in the data processing request to the blockchain node corresponding to the blockchain node account, so that the blockchain node initiates a processing operation on the data to be processed in its own blockchain system, includes: The business node sends the identification information of the data to be queried contained in the data processing request to the blockchain node corresponding to the blockchain node account, so that the blockchain node can query the result data corresponding to the identification information of the data to be queried from the locally stored blockchain; Obtain the result data returned by the blockchain node in response to the data processing request.

6. A data processing system based on blockchain, characterized in that, The system includes: business nodes, blockchain nodes, and account management nodes independent of the business nodes and the blockchain nodes; In response to a company's registration operation, the account management node assigns a unique identifier to the company as its master management account; based on a sub-account creation request initiated by the master management account, it creates at least one management sub-account corresponding to the master management account and configures management permissions for the at least one management sub-account; based on a business account creation request initiated by the master management account or a management sub-account, it creates business accounts to identify different businesses of the company, and based on a business account configuration request initiated by the master management account or a management sub-account, it configures corresponding blockchain node accounts for the created business accounts, generates an account binding relationship between the business accounts and the blockchain node accounts, and sends the account binding relationship to the business node; in response to a key creation request initiated by the master management account or a management sub-account, it creates a public key and a private key corresponding to the business account, generates a key mapping relationship based on the business account and the public key corresponding to the business account, and sends the key mapping relationship to the business node; The business node receives a data processing request initiated by a business account, and based on the data processing request, retrieves the blockchain node account bound to the business account from the received account binding relationship; based on the data processing request, it retrieves the public key corresponding to the business account from the key mapping relationship, and verifies the signature contained in the data processing request based on the obtained public key, the signature being generated based on the private key corresponding to the business account; if the signature passes verification, the data to be processed contained in the data processing request is sent to the blockchain node corresponding to the blockchain node account; wherein, the blockchain nodes corresponding to different blockchain node accounts belong to different blockchain systems, each of the different blockchain systems maintains a different blockchain, and different business accounts correspond to different blockchain systems through the blockchain node accounts they are bound to; The blockchain node receives the data to be processed sent by the business node and initiates processing operations on the data to be processed in its own blockchain system.

7. A data processing device based on blockchain, characterized in that, Applied to a service node, the device includes: The first acquisition module is configured to acquire data processing requests initiated by business accounts; The second acquisition module is configured to acquire account binding relationships from the account management node, and based on the data processing request and the account binding relationships, acquire the blockchain node accounts bound to the business accounts. Different blockchain node accounts correspond to blockchain nodes belonging to different blockchain systems, each maintaining its own blockchain. Different business accounts correspond to different blockchain systems through their bound blockchain node accounts. The account binding relationships are obtained by the account management node after creating a corresponding business account based on a business account creation request initiated by the main management account or a sub-management account, and then configuring the corresponding blockchain node accounts for the created business accounts based on a business account configuration request initiated by the main management account or a sub-management account. The main management account is a unique identifier assigned to the enterprise by the account management node in response to the enterprise's registration operation. The sub-management accounts are created by the account management node for the main management account based on a sub-account creation request initiated by the main management account. The business accounts are used to identify different businesses within the enterprise. The sending module is configured to, based on the data processing request, obtain the public key corresponding to the business account from the key mapping relationship, and verify the signature contained in the data processing request based on the obtained public key. The signature is generated based on the private key corresponding to the business account. If the signature passes verification, the data to be processed contained in the data processing request is sent to the blockchain node corresponding to the blockchain node account, so that the blockchain node initiates a processing operation on the data to be processed in its own blockchain system. The account management node is independent of the business node and the blockchain node. The key mapping relationship is generated and sent to the business node based on the business account and the public key corresponding to the business account after the account management node creates the public and private keys corresponding to the business account in response to a key creation request initiated by the main management account or the sub-management account.

8. An electronic device, characterized in that, include: One or more processors; A storage device for storing one or more programs, which, when executed by the one or more processors, cause the electronic device to perform the method as described in any one of claims 1-5.

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

10. A computer program product, characterized in that, Includes computer instructions, which, when executed by a processor of a computer device, cause the computer device to perform the method described in any one of claims 1-5.

Images