A method, device and equipment for processing enterprise business based on cloud service platform

Abstract

The embodiments of this specification disclose an enterprise business processing method based on a cloud service platform, including: providing purchasable meta-service units, including consensus service units and block chain storage units, to the enterprise after it is authenticated through the cloud service platform; creating an enterprise chain node for the enterprise based on the meta-service units purchased by the enterprise, with a corresponding proxy service unit for detecting the dynamic changes in the number of consensus service units under the enterprise chain node; when a new consensus service unit is added, starting a corresponding consensus service process and mounting it to the consensus network load balancing unit deployed on the enterprise chain to which the enterprise chain node belongs; when a decrease in consensus service units is made, canceling the mounting of the corresponding consensus service process; adding the enterprise chain node to an enterprise alliance comprising multiple different enterprise chain nodes and regulatory nodes; and providing a smart contract to the enterprise alliance so that the multiple enterprise chain nodes in the enterprise alliance can trade with each other in the enterprise alliance.

Description

Technical Field

[0001] This specification relates to the field of blockchain technology, and in particular to a method, device, and equipment for processing enterprise business based on a cloud service platform. Background Art

[0002] As the industry continues to develop, the division of labor among enterprises continues to be refined, and cooperation between enterprises is becoming increasingly close. Information exchange, as the lifeblood of inter-enterprise cooperation and communication, connects all important organs of the industry like the blood, exchanging and transmitting important information, and maintaining information exchange between various cooperating enterprises.

[0003] Just like personal social networks, enterprises also need service networks for information exchange. Moreover, they have higher requirements for the security, privacy, and stability of information service networks. Blockchain, especially consortium chain technology, provides an inherent high-trust technology and environment for safe and stable information exchange between enterprises.

[0004] However, in current blockchain-based information exchange networks, enterprises often use their own computing and equipment resources to build blockchain nodes, and then communicate and negotiate with other enterprises to form alliances and corresponding alliance chains to exchange information. This approach is costly, has a high barrier to entry, and is difficult to get started. The high cost makes it unaffordable for small and micro businesses, while large enterprises find it difficult to expand. Moreover, after the alliance is established, the adjustment of alliance members is very limited, with almost no possibility of deletion and reduction, and the flexibility is extremely low. However, as businesses continue to develop and members constantly change, the limitations of adding and removing alliance members greatly restrict the development of business scenarios based on alliance chains. In the long run, this will cause the alliance chain to become disconnected from the business and its value to derail.

[0005] Based on this, in the blockchain, especially the alliance chain scenario, there is a need for inter-enterprise interaction solutions that can reduce costs and increase efficiency. Summary of the Invention

[0006] One or more embodiments of this specification provide a method, apparatus, device, and storage medium for enterprise business processing based on a cloud service platform to solve the following technical problems: In blockchain, especially consortium chain scenarios, a solution for enterprise interaction that can reduce costs and increase efficiency is needed.

[0007] To solve the above technical problems, one or more embodiments of this specification are implemented as follows:

[0008] One or more embodiments of this specification provide a method for processing enterprise business based on a cloud service platform, which is applied to a system including the cloud service platform. The method includes:

[0009] Receiving authentication information submitted by the enterprise through the cloud service platform and authenticating the enterprise;

[0010] After the authentication is passed, providing the enterprise with a purchasable meta-service unit, wherein the meta-service unit includes a consensus service unit and a block chain storage unit;

[0011] Based on the meta-service units purchased by the enterprise, an enterprise chain node containing the meta-service unit is created for the enterprise. The enterprise chain node has a corresponding proxy service unit. The proxy service unit detects the dynamic changes in the number of the consensus service units under the enterprise chain node. When the consensus service unit is newly added, the corresponding consensus service process is started and mounted to the consensus network load balancing unit deployed on the enterprise chain to which the enterprise chain node belongs for unified management. When the consensus service unit is reduced, the corresponding consensus service process is unmounted from the consensus network load balancing unit.

[0012] Joining the enterprise chain node to an enterprise alliance comprising multiple different enterprise chain nodes and supervisory nodes;

[0013] A smart contract is provided to the enterprise alliance, so that the plurality of enterprise chain nodes in the enterprise alliance can conduct mutual transactions in the enterprise alliance through the smart contract.

[0014] One or more embodiments of this specification provide an enterprise business processing device based on a cloud service platform, which is applied to a system including the cloud service platform. The device includes:

[0015] An enterprise authentication module receives authentication information submitted by an enterprise through the cloud service platform and authenticates the enterprise;

[0016] A purchasing service module, which provides the enterprise with a purchasable meta-service unit after the authentication is passed, wherein the meta-service unit includes a consensus service unit and a block chain storage unit;

[0017] A node creation module creates an enterprise chain node for the enterprise containing the meta-service unit based on the meta-service unit purchased by the enterprise. The enterprise chain node has a corresponding proxy service unit. The proxy service unit detects the dynamic changes in the number of the consensus service units under the enterprise chain node. When the consensus service unit is newly added, the corresponding consensus service process is started and mounted to the consensus network load balancing unit deployed on the enterprise chain to which the enterprise chain node belongs for unified management. When the consensus service unit is reduced, the corresponding consensus service process is unmounted from the consensus network load balancing unit.

[0018] Alliance maintenance module, adding the enterprise chain node to the enterprise alliance including multiple different enterprise chain nodes and supervision nodes;

[0019] The alliance transaction module provides a smart contract to the enterprise alliance, so that the multiple enterprise chain nodes in the enterprise alliance can conduct transactions with each other in the enterprise alliance through the smart contract.

[0020] One or more embodiments of this specification provide an enterprise business processing device based on a cloud service platform, which is applied to a system including the cloud service platform. The device includes:

[0021] at least one processor; and,

[0022] a memory communicatively connected to the at least one processor; wherein,

[0023] The memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to enable the at least one processor to:

[0024] Receiving authentication information submitted by the enterprise through the cloud service platform and authenticating the enterprise;

[0025] After the authentication is passed, providing the enterprise with a purchasable meta-service unit, wherein the meta-service unit includes a consensus service unit and a block chain storage unit;

[0026] Based on the meta-service units purchased by the enterprise, an enterprise chain node containing the meta-service unit is created for the enterprise. The enterprise chain node has a corresponding proxy service unit. The proxy service unit detects the dynamic changes in the number of the consensus service units under the enterprise chain node. When the consensus service unit is newly added, the corresponding consensus service process is started and mounted to the consensus network load balancing unit deployed on the enterprise chain to which the enterprise chain node belongs for unified management. When the consensus service unit is reduced, the corresponding consensus service process is unmounted from the consensus network load balancing unit.

[0027] Joining the enterprise chain node to an enterprise alliance comprising multiple different enterprise chain nodes and supervisory nodes;

[0028] A smart contract is provided to the enterprise alliance, so that the plurality of enterprise chain nodes in the enterprise alliance can conduct mutual transactions in the enterprise alliance through the smart contract.

[0029] At least one of the above technical solutions adopted in one or more embodiments of this specification can achieve the following beneficial effects: the enterprise chain node proposed in this solution realizes cloud-chain integration, and separates functions such as consensus services and chain block storage in the node in the form of meta-service units, which helps to fully utilize the technical dividends released by cloud technologies such as cloud native, further reduce the enterprise cost of enterprises using blockchain, and while reducing costs and increasing efficiency, it also enhances the stability and security of blockchain nodes, and can achieve one-stop upgrades, expansions, and self-healing. At the node level, the proxy service unit dynamically detects the increase and decrease of consensus service units and timely controls the start and stop of corresponding consensus service processes. At the global level, the consensus network load balancing unit uniformly manages all dynamically changing consensus service processes, thereby improving overall efficiency, reducing the management burden of the enterprise, and being able to respond to changes in enterprise needs in a timely manner. In addition, the cloud service platform provides customers with comprehensive enterprise credit management services in the form of Software as a Service (SaaS), proposes a novel and flexible alliance formation method, and uses a social network-like information exchange method to fundamentally solve the current information asymmetry in inter-enterprise cooperation, linking various nodes in the industry and opening up an information highway. BRIEF DESCRIPTION OF THE DRAWINGS

[0030] In order to more clearly illustrate the embodiments of this specification or the technical solutions in the prior art, the following briefly introduces the drawings required for use in the embodiments or the description of the prior art. Obviously, the drawings described below are only some embodiments recorded in this specification. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.

[0031] Figure 1 A flowchart of a method for processing enterprise business based on a cloud service platform provided in one or more embodiments of this specification;

[0032] Figure 2 A schematic diagram of a cloud-chain integrated chain node implementation architecture provided for one or more embodiments of this specification;

[0033] Figure 3 A schematic diagram of the internal architecture of a chain node in an enterprise chain node cloud chain integration at the service process level provided for one or more embodiments of this specification;

[0034] Figure 4 A flowchart of a consensus service elastic management for newly added services provided in one or more embodiments of this specification;

[0035] Figure 5 A flowchart of consensus service elasticity management for service reduction situations provided in one or more embodiments of this specification;

[0036] Figure 6 A flowchart of a blockchain storage service provided for one or more embodiments of this specification;

[0037] Figure 7 A schematic diagram of a system architecture including a cloud service platform and a supervisory node provided for one or more embodiments of this specification;

[0038] Figure 8 A flowchart of a transaction solution based on cross-alliance blockchain data unit reorganization provided in one or more embodiments of this specification;

[0039] Figure 9 A schematic diagram of the structure of an enterprise business processing device based on a cloud service platform provided in one or more embodiments of this specification;

[0040] Figure 10 A schematic diagram of the structure of an enterprise business processing device based on a cloud service platform provided in one or more embodiments of this specification. DETAILED DESCRIPTION

[0041] The embodiments of this specification provide a method, apparatus, device, and storage medium for enterprise business processing based on a cloud service platform.

[0042] In order to enable those skilled in the art to better understand the technical solutions in this specification, the technical solutions in the embodiments of this specification will be clearly and completely described below in conjunction with the drawings in the embodiments of this specification. Obviously, the embodiments described are only part of the embodiments of this application, not all of the embodiments. Based on the embodiments of this specification, all other embodiments obtained by ordinary technicians in this field without making creative efforts should fall within the scope of protection of this application.

[0043] In response to the problems raised by the background technology, this application proposes a cloud-chain integration solution based on cloud-native technology, which separates the chain node functions into consensus service units, block chain storage units, metadata units, etc. Consensus service units, as a microservice form based on cloud-native technology, can be purchased, used, and released at will, and customers can upgrade, expand, and self-heal without worrying about it. Block chain storage units, as basic information storage of blockchain, are the medium for basic user data information, which can achieve dynamic expansion, hot and cold backup, and flexible pluggability. Metadata units store basic metadata of user block services and are the configuration data basis for users to restore consensus services. Under this solution, customers only need to maintain the resource overhead costs of block chain storage or metadata storage during actual use. In view of the flexible alliance formation method, this solution proposes a cloud for strengthening trust between enterprises.

[0044] The service platform provides a place for information exchange and matchmaking for the formation of alliances. The cloud service platform exists in the form of SaaS. 5 Customers can enter the platform, manage chain node information, partner information, publish and subscribe to alliance cooperation intentions, search for cooperation

[0045] Partners, apply for alliance formation. The following is a detailed explanation based on this idea.

[0046] Figure 1 This is a flow chart of a method for processing business on a cloud service platform for one or more embodiments of this specification. This method can be applied to different business areas, such as electronic payment industry.

[0047] This process should be used in systems that include cloud service platforms and can be executed mainly on devices on cloud service platforms. Some input parameters in the process

[0048] The data or intermediate results allow for manual intervention and adjustment to help improve accuracy.

[0049] Figure 1 The process in may include the following steps:

[0050] S102: Receive authentication information submitted by the enterprise through the cloud service platform and authenticate the enterprise.

[0051] In one or more embodiments of this specification, an enterprise registers a cloud service platform account, logs into the platform, and submits authentication information to the Cloud Enterprise Credit 5 platform, including basic identity information, such as unified social credit code, enterprise name, legal person certificate, etc.

[0052] In addition, in order to facilitate deeper cooperation with other companies in the future, companies can also proactively provide more specific information on qualifications and operations, such as national or industry certificates obtained, government licenses for conducting specific businesses, recent financial reports, cooperation intentions, etc.

[0053] This application is committed to removing the obstacles to interaction and cooperation between enterprises, and thus attaches great importance to the reliability of enterprise credit and enterprise information. In actual applications, the cloud service platform itself may also be operated by enterprises or government departments, and the source of information may be

[0054] There may be one-sidedness. In order to avoid being at a disadvantage in this regard, the cloud service platform can cooperate with various third parties to form a platform system with a more reliable and comprehensive information source. These third parties include industrial and commercial departments, regulatory departments, audit departments, corporate associations, and companies that provide government and enterprise information inquiries.

[0055] In one or more embodiments of this specification, the above system includes a platform alliance composed of a cloud service platform and supervisory parties such as industrial and commercial departments and regulatory departments. Of course, the system can also include other third parties.

[0056] Through the cloud service platform, the authentication information submitted by the enterprise is received. Based on the authentication information, the corresponding contract transaction is submitted to the platform alliance (for example, it is called enterprise information verification transaction, and the corresponding smart contract is pre-chained to support such transaction execution).

[0057] The consensus and transaction confirmation within the platform alliance are carried out to determine whether the authentication information is authenticated. In this way,

[0058] This allows for more accurate and fair authentication of businesses, enhancing the trust of businesses that subsequently interact with them on the platform. 0S104: After the authentication is successful, the business is provided with purchasable meta-service units, which include a consensus service unit and a blockchain storage unit.

[0059] In one or more embodiments of this specification, the consensus service, block chain storage and other functions in the blockchain node are separated to construct corresponding meta-service units (the meta-services here mainly refer to relatively basic services with appropriate granularity that do not require further subdivision, so as to facilitate free assembly and take into account flexibility and efficiency) so as to be flexibly provided to enterprises for on-demand purchase. Enterprises can buy, use and release them at will without having to prepare node resources themselves. For example, a set of consensus service units and a set of block chain storage units are separated from the complete alliance chain node service resources in advance, and then divided according to specified dimensions in the set of consensus service units and the set of block chain storage units respectively to obtain and display multiple differentiated resource subsets, so that enterprises can flexibly purchase resource subsets according to specified dimensions and their actual needs. Specified dimensions include, for example, consensus algorithm dimensions, performance specification dimensions, price dimensions, business type dimensions, etc.

[0060] In one or more embodiments of this specification, the consensus service unit is the smallest meta-service unit sold by the cloud service platform. This service is stateless and focuses on network consensus, identity authentication, transaction verification, etc. It can be mounted and combined with any number of block chain storage units. The implementation of the consensus service here can be based on cloud native technology. It is essentially a container process that can be actually scheduled according to demand. The block chain storage unit provides basic cloud services for storing block chain data. The block chain storage unit can be dynamically created and freely combined with the consensus service unit. It can be used as a private business data block for users (enterprises and other system participants). The block chain storage here is also a service, similar to the consensus service, which is also a containerized process. After the block chain storage service is started, the service registration is performed, and the block chain data writing rules are synchronized to the metadata, and the block chain data is stored according to the writing rules. Similarly, more paid or free meta-service units can be provided to enterprises for use.

[0061] In one or more embodiments of this specification, after an enterprise passes authentication, the cloud service platform can create a chain account for the enterprise on the consortium chain corresponding to the platform's alliance. At this point, the enterprise does not yet have a chain node and cannot participate in consensus interactions with other enterprises. However, with the chain account, the cloud service platform can still grant the enterprise certain operational permissions, allowing the enterprise to gain a basic understanding of the relevant enterprises on the platform, which can be used as a reference for subsequent decisions on whether to join an enterprise alliance and which enterprise alliance to join.

[0062] For example, an enterprise can use its chain account to query the business information of related companies on the platform, or more specific information about authorized companies. For example, after authentication, the enterprise initiates a business information query request using its chain account. The cloud service platform responds to the request, identifies the target enterprise within the enterprise alliance served by the cloud service platform, or within an enterprise that already has a chain account but has not yet joined the alliance. The cloud service platform then submits a contract transaction to the enterprise alliance where the target enterprise resides. After the enterprise alliance executes the contract in response to the contract transaction and returns the execution result, the execution result is returned to the enterprise initiating the business information query via the chain account. The querying enterprise can then obtain the business information of the target enterprise based on the execution result. As can be seen, in this process, because the enterprise does not currently own a chain node within the enterprise alliance, it can sign the contract transaction, and the cloud service platform will then submit the signed contract transaction on its behalf. Later, if the enterprise owns a chain node, it can submit the transaction itself. In addition, if the platform alliance already has the industrial and commercial information that an enterprise wants to query, the contract transaction can also be executed within the platform alliance, which helps reduce the burden on the enterprise alliance.

[0063] S106: Based on the meta-service unit purchased by the enterprise, an enterprise chain node containing the meta-service unit is created for the enterprise. The enterprise chain node has a corresponding proxy service unit. The proxy service unit detects the dynamic changes in the number of the consensus service units under the enterprise chain node. When the consensus service unit is newly added, the corresponding consensus service process is started and mounted to the consensus network load balancing unit deployed in the enterprise chain to which the enterprise chain node belongs for unified management. When the consensus service unit is reduced, the corresponding consensus service process is unmounted to the consensus network load balancing unit.

[0064] In one or more embodiments of this specification, in the preceding process, an enterprise only possesses a blockchain account, which it uses to sign transactions, with the cloud service platform executing the transactions on its behalf to implement smart contract execution and obtain results. However, for other inter-enterprise information exchange functions provided by the cloud service platform, such as alliance creation, publishing / subscribing to cooperation intentions, and business qualification inquiries, an enterprise's blockchain account alone is insufficient. The enterprise must purchase blockchain node services (represented by corresponding meta-service units) and participate in node consensus or the post-consensus blockchain storage process.

[0065] Intuitively, see Figure 2 , Figure 2 A schematic diagram of a cloud-chain integrated chain node implementation architecture provided for one or more embodiments of this specification. Cloud-chain integration here refers to the design of a blockchain node that closely integrates chain technology with cloud services, thereby effectively improving node flexibility and reducing the cost of node creation and alliance creation. Previous blockchain nodes were not designed with cloud services in mind, and were unable to utilize cloud-native technologies. They simply relied on cross-chain protocols to form a peer-to-peer decentralized or partially decentralized network. The computing resources of each node were often unrelated and were completely prepared privately before joining the network. There was no platform to provide nodes with ready-made service resources for consensus, blockchain storage, etc.

[0066] For example, when purchasing a consensus service unit, enterprises can choose one that supports different consensus algorithms and has different performance specifications. The number of supported algorithms determines the degree of compatibility between the enterprise and other enterprises using that consensus service unit. The different performance specifications determine the throughput of consensus transactions during the enterprise's transaction consensus.

[0067] Based on their business plans, enterprises determine the specifications of the various meta-service units they wish to purchase. Upon receiving a purchase request from an enterprise, the cloud service platform, if successful, assembles the meta-service units, creates corresponding chain nodes, and registers the relevant resource identification information of the chain nodes and the enterprise's identity information within the platform's alliance. For example, if information registration is performed through a pre-defined smart contract for enterprise onboarding, the registration information chain block is stored and shared with various nodes within the alliance through transactions, thus achieving shared and credible information filing.

[0068] exist Figure 2 Figure 1 shows a cloud service platform and several cloud-connected, integrated chain nodes connected to the cloud service platform. These chain nodes can serve as the aforementioned enterprise chain nodes. The chain nodes contain the various meta-service units outlined in dashed boxes. The small icons next to the dashed boxes represent enterprise entities (i.e., the aforementioned enterprises, which typically perform preliminary operations through the client provided by the cloud service platform). Enterprise entities are abstractions of clients within the cloud service platform. Upon entry, enterprises register relevant qualification information, business qualification information, and operating status information with the cloud service platform.

[0069] The dotted box contains the consensus service unit and blockchain storage unit mentioned above. In addition, it also contains a metadata unit, which is used to store configuration data related to the consensus service unit and / or blockchain storage unit. It is the basis for realizing consensus services, free buying and selling, and blockchain storage. Similarly, more optional meta-service units can be provided. For example, the arrow icon next to the small house icon represents a proxy service unit, which is responsible for performing automated operation and maintenance operations for one or more other meta-service units. Specifically, the proxy service here, such as the control plane service belonging to the chain node, is responsible for adding, deleting, modifying and checking more basic meta-service units such as consensus services, blockchain storage, and metadata. It is also responsible for automated operation and maintenance operations such as version upgrades, monitoring and early warning, and self-healing of these meta-service units. The proxy service can implement permanent processes based on cloud native technology to continuously help enterprises with automatic management.

[0070] exist Figure 2 In the blockchain, the management information flow is the data flow related to user management information, the consensus business flow is the data flow generated during the chain node consensus process, and the proxy control flow is the control plane data flow, including operation and maintenance instructions.

[0071] After the chain node is created, the enterprise's alliance chain function is realized through the cooperation between the various units involved at the service process level. Figure 3 A schematic diagram of the internal architecture of a chain node in an enterprise chain node cloud chain integration at the service process level provided for one or more embodiments of this specification.

[0072] exist Figure 3The consensus network load balancing unit is the entry point for the entire consensus network, providing a unified IP address and capable of serving one or more chain nodes. Consensus Service A, Consensus Service B, and so on represent these consensus service units. These services, for example, operate as processes and are elastically scalable. When new or new consensus services are added or removed, their corresponding intranet IP addresses are registered or deleted with the consensus network load balancing unit. The data queue is used to store post-consensus transaction data, which has not yet been packaged into blocks. Blockchain Storage Service A, Blockchain Storage Service N, and so on represent these blockchain storage units. They retrieve data from the data queue, package it into blocks, and provide persistent storage for block transactions. Blockchain storage services can also adjust based on their own storage capacity, typically by increasing or expanding capacity. To improve overall reliability, only one process of this service can be active on a single chain node at a time. The metadata service allows for global storage and query of configurations related to the service's lifecycle management and block write rules.

[0073] Based on the explanation in the previous paragraph, the following also provides some specific processes involved in the consensus service and blockchain storage mentioned above. Figures 4 to 6 .

[0074] Figure 4 A schematic diagram of a process flow for consensus service elasticity management for new service additions provided in one or more embodiments of this specification. Figure 4 In [1], the proxy service will start the corresponding process for the newly added consensus service and confirm the availability of the process. For the convenience of unified management, the consensus service will be mounted to the consensus network load balancing unit. The consensus network load balancing unit will then register the intranet node IP and perform health checks for the consensus service. It can also dynamically schedule based on the local or global consensus service status to enable more efficient consensus across the entire network and smoother participation of chain nodes. The consensus result, that is, the transaction data that has passed the consensus, can be temporarily written to the data queue, waiting to be read by the blockchain storage service.

[0075] Figure 5 A flowchart of consensus service elasticity management for service reduction situations provided in one or more embodiments of this specification. Figure 5 Similarly, if the consensus service is reduced, the previous mount of the consensus service will be canceled. It should be noted that in actual applications, the consensus service may still involve transactions that have not been processed. Therefore, before completely stopping the consensus service to be reduced, it is necessary to check whether the transaction data involved has been written to the data queue. If not, it is necessary to wait until it is completed before stopping the service.

[0076] Figure 6A flowchart of a block chain storage service provided for one or more embodiments of this specification. When a block chain storage unit is newly added under an enterprise chain node, the corresponding block chain storage service process is started through the proxy service unit, and the block chain storage service process is registered with the metadata unit. The registration process includes recording the above-mentioned write rules. The write rules can be used to measure the current transaction storage relay situation. Since a single chain node is likely to contain multiple block chain storage units, the block chain storage units may be further increased with the expansion. Therefore, the order in which these block chain storage units are written in sequence can be pre-designed. For example, the starting transaction number of each block chain storage unit is recorded in advance. Only when the corresponding starting transaction number is reached, the corresponding block chain storage unit goes to the data queue to obtain data. In this way, each block chain storage unit can be used in relay in sequence, which helps to archive management in a more orderly manner and also helps to make full use of storage resources.

[0077] Based on this, Figure 6 In the process, the registered block chain storage service process is used to poll the transaction storage relay status recorded by the metadata unit, and the transaction data that has been agreed upon by the consensus service unit is obtained from the data queue corresponding to the enterprise chain node. According to the polling results, the transaction data is packaged into blocks in a timely manner (for example, when waiting for the corresponding starting transaction number to be reached) and the blocks are persistently stored.

[0078] S108: adding the enterprise chain node to an enterprise alliance including a plurality of different enterprise chain nodes and supervisory nodes.

[0079] In one or more embodiments of this specification, after an enterprise chain node is created and the corresponding information is registered and filed, the enterprise can then use its own node to join one or more enterprise alliances under the cloud service platform. To improve reliability, in addition to the nodes of the enterprise that is a platform customer, the enterprise alliance may also include some supervisory nodes. These supervisory nodes can come from the platform alliance or be elected by each enterprise. The same enterprise can serve as both a supervisory node and an enterprise chain node as a customer.

[0080] S110: Providing a smart contract to the enterprise alliance, so that the plurality of enterprise chain nodes in the enterprise alliance can conduct transactions with each other in the enterprise alliance through the smart contract.

[0081] In one or more embodiments of this specification, the transaction content is diverse, such as the publication / subscription of cooperation intentions, the recommendation and endorsement of transaction partners, the issuance and completion of actual business orders, pledges and permissions, etc.

[0082] Considering the enterprise alliance as part of the aforementioned system, the cloud service platform and the enterprise alliances it serves constitute a larger system. For example, for a transaction involving cooperation intentions, a certain enterprise alliance comprises multiple enterprise chain nodes, each representing a different enterprise. The transaction process involves: One of the enterprise chain nodes, referred to as the first enterprise chain node, obtains a cooperation intention-related smart contract provided by the cloud service platform and initiates a business intention transaction based on it. The enterprise alliance reaches consensus on the business intention transaction and makes it public to the other enterprise chain nodes in the alliance (nodes requiring this information can pre-subscribe). Assuming another enterprise chain node, referred to as the second enterprise chain node, also expresses cooperation intentions, the second enterprise chain node can initiate a response transaction using the cooperation intention-related smart contract, parsing and matching the business intention transaction with the response transaction. The execution results are then synchronized across the enterprise alliance. Based on the execution results, the first enterprise chain node then reaches a cooperation intention agreement with the second enterprise chain node. Key information from this process is stored on-chain on the alliance chain corresponding to the enterprise alliance.

[0083] pass Figure 1 The enterprise chain node proposed in this solution realizes cloud-chain integration, and separates the consensus service, chain block storage and other functions in the node in the form of meta-service units, which helps to make full use of the technical dividends released by cloud technologies such as cloud native, further reduce the enterprise cost of using blockchain for enterprises, and enhance the stability and security of blockchain nodes while reducing costs and increasing efficiency. It can achieve one-stop upgrade, expansion and self-healing. At the node level, the proxy service unit dynamically detects the increase and decrease of consensus service units and timely controls the start and stop of the corresponding consensus service process. At the global level, the consensus network load balancing unit uniformly manages all dynamically changing consensus service processes, which improves overall efficiency, reduces the management burden of the enterprise, and can respond to changes in enterprise needs in a timely manner. In addition, the cloud service platform provides customers with a full range of enterprise credit management services in the form of SaaS, proposes a novel and flexible alliance formation method, and fundamentally solves the current information asymmetry of cooperation between enterprises in a social network-like information exchange method, links various nodes in the industry, and opens up an information highway.

[0084] based on Figure 1 This specification also provides some specific implementation plans and extension plans of the method, which will be described below.

[0085] More intuitively, one or more embodiments of this specification also provide a schematic diagram of a system architecture including a cloud service platform and a supervisory node in an application scenario, such as Figure 7 shown.

[0086] exist Figure 7In this application scenario, the cloud service platform, along with regulatory authorities, auditing departments, business associations, industrial and commercial departments, and third-party enterprise information query companies, forms a platform alliance to provide services such as enterprise onboarding, information management, query and search, alliance matchmaking, and alliance formation. Enterprise alliance formation, a key service of the cloud service platform, uses blockchain smart contracts to perform enterprise identity identification, business qualification verification, financial auditing, and alliance metadata distribution to ensure the accuracy and financial security of each member's qualification information within the alliance.

[0087] The cloud service platform has pre-created various smart contracts for subsequent use by service companies, such as industrial and commercial information verification smart contracts, industrial and commercial information query smart contracts, business qualification audit smart contracts, enterprise entry smart contracts, operation status inspection smart contracts, cooperation intention publishing / subscription smart contracts, alliance management smart contracts, etc.

[0088] Application services are visualization services provided by the platform to SaaS users, such as the following:

[0089] Enterprise information management: Users can maintain and authenticate their own enterprise information through enterprise information management.

[0090] Cooperation intention management: Through cooperation intention management, information about cooperation and potential partners is maintained.

[0091] Alliance management. After a user and a partner reach an agreement, the service platform creates a dedicated blockchain alliance for the partner through the alliance management smart contract. The genesis block of the alliance chain is written to all parties in the alliance through the service platform. The service platform activates each node in the alliance chain through the proxy node, thereby achieving consensus networking and normal communication.

[0092] Service resource management. Manage the consensus service resources in the cloud chain integration chain node. Users can use the proxy service unit in the cloud chain integration to conveniently purchase, use and release the consensus service unit.

[0093] Data management. After users join the platform, their business data and chain metadata are unique to them. Users can perform basic management of blockchain storage units, metadata units, etc. through the proxy service unit in the cloud-chain integration; for example, they can create, mount, and unmount blockchain storage.

[0094] Basic services and corresponding smart contracts are the atomic services of the application service platform, which drive the interaction and assistance of each node in the alliance through smart contracts.

[0095] The workflow can refer to the previous description. A brief description of an implementation plan for this scenario is as follows:

[0096] Enterprises register for a cloud service platform account and log in to authenticate their identity. The platform submits the information verification contract transaction within the alliance through the industrial and commercial information verification smart contract, achieving consensus and transaction confirmation within the alliance. The platform analyzes the blockchain transaction of the industrial and commercial information verification smart contract and confirms the verification result. If the verification result is passed, the enterprise is notified to upload the public key certificate to confirm the enterprise's identity account. If the verification result is not passed, the enterprise is notified that the authentication failed and requires re-authentication. For enterprises whose identity accounts have been confirmed, the platform will create a corresponding blockchain account for them.

[0097] After having a chain account, enterprises can use the industrial and commercial information query smart contract to initiate query contract transactions to query the industrial and commercial information of other enterprises.

[0098] Enterprises purchase consensus service units, blockchain storage units, proxy service units, etc. according to their own needs. The platform creates nodes based on the purchase results and registers and files information through the enterprise’s entry into the smart contract. After that, the enterprise chain node of the enterprise can be added to the enterprise alliance.

[0099] In the enterprise alliance, inter-enterprise cooperation is carried out through publishing / subscribing smart contracts with cooperation intentions.

[0100] In one or more embodiments of this specification, in a traditional blockchain, block chain storage and consensus services are integrated into the nodes. If data transactions are to be conducted, especially some valuable private data, the data must either be recorded in a public universal ledger through consensus, or after the transaction is passed, the data must be transferred from the data seller to the data buyer through some additional channels. In either case, data privacy will be threatened and may even be leaked outside the system.

[0101] Based on this, since this solution separates the block chain storage service unit and the consensus service unit, it is considered to directly store the user's private data in the block chain storage service unit, and then directly disassemble the transaction block chain storage service unit and reorganize the corresponding chain nodes. The process of unit disassembly and reorganization is controlled by the cloud service platform, so there is no need to introduce other channels or export data from the block chain storage, which effectively protects privacy.

[0102] Furthermore, each enterprise alliance can correspond to a separate alliance chain. In traditional alliance chains, the enterprises within the chain often have a certain degree of trust and generally participate in the consensus process. Furthermore, the industry or business correlation between the enterprises is relatively high. While there may be some trust, there may also be obvious competition. In practical applications, the targets of sensitive data protection for enterprises often include such other enterprises. In this case, for data transactions, transaction fairness and competitive threats often lead to conflicts within the same alliance. Considering this, based on the direct blockchain storage unit transaction scheme mentioned in the previous paragraph, a blockchain storage unit transaction scheme for non-related enterprise alliances and cross-non-related enterprise alliances is proposed. The main idea is to proactively build enterprise alliances with low industry or business correlation to achieve consensus and ensure transaction fairness, while also reducing the threat of internal insiders within the alliance to the private data security of alliance members.

[0103] Of course, this approach also has its drawbacks. If the transaction is conducted across alliances, the buyer may be unable to participate in the consensus process and must rely primarily on the reliability of the seller's alliance. To address this issue, based on the separated consensus service units, the alliance can temporarily loan out the consensus service units within the alliance and temporarily assemble them to chain nodes outside the alliance. This allows the buyer to participate in the transaction consensus process of the seller's alliance through the loaned consensus service units. This approach effectively utilizes the loose coupling and flexibility between meta-service units, avoids major modifications to business logic, and has minimal implementation costs.

[0104] Based on the analysis in the above paragraphs, one or more embodiments of this specification also provide a flowchart of a transaction solution based on cross-alliance blockchain data unit reorganization, such as Figure 8 shown.

[0105] Figure 8 The process in includes the following steps:

[0106] S802: Determine a blockchain storage unit targeted by transactions through mutual transactions conducted within the enterprise alliance and / or mutual transactions conducted between different enterprise alliances.

[0107] For at least some enterprise-side alliances, when building them, it is possible to determine whether the industry or business correlations between multiple different enterprise chain nodes are below a set threshold. If so, these multiple different enterprise chain nodes and regulatory nodes are combined to form an enterprise-side alliance. After determining that the correlation between the newly added enterprise chain node and the existing enterprise chain nodes in the enterprise-side alliance is also below the set threshold, the newly added enterprise chain node is added to the enterprise-side alliance. Thus, a low-correlation enterprise-side alliance is achieved.

[0108] Assume that the enterprise chain node of the transaction seller and the enterprise chain node of the transaction buyer belong to different enterprise alliances.

[0109] S804: Determine another enterprise chain node having the consensus service unit in the enterprise alliance to which the enterprise chain node of the transaction seller belongs, as the unit lending node.

[0110] S806: The consensus service unit of the unit lending node is temporarily lent and assembled with the enterprise chain node of the transaction seller, so that the enterprise chain node of the transaction seller temporarily participates in the consensus process of the enterprise alliance to which the enterprise chain node of the transaction seller belongs for the corresponding transaction.

[0111] S808: After the consensus process is completed, the loaned consensus service unit is released and returned to the unit lending node.

[0112] Assuming the consensus process is passed smoothly, the transaction proceeds normally to the delivery process of the transaction items.

[0113] S810: Obtain the block chain storage unit contained in the enterprise chain node of the transaction seller.

[0114] S812: Remove the block chain storage unit from the enterprise chain node of the transaction seller as a unit to be reassembled.

[0115] S814: Reassemble the unit to be reassembled with the enterprise chain node of the transaction buyer to obtain the assembled enterprise chain node, and confirm that the corresponding transaction is completed.

[0116] Based on the same idea, one or more embodiments of this specification also provide devices and apparatuses corresponding to the above methods, such as Figure 9 、 Figure 10 shown.

[0117] Figure 9 This is a schematic diagram of the structure of an enterprise business processing device based on a cloud service platform provided in one or more embodiments of this specification. The dashed boxes represent optional modules. The device is applied to a system including the cloud service platform, and the device includes:

[0118] The enterprise authentication module 902 receives authentication information submitted by the enterprise through the cloud service platform and authenticates the enterprise;

[0119] A purchasing service module 904 provides the enterprise with a purchasable meta-service unit after the authentication is passed, wherein the meta-service unit includes a consensus service unit and a blockchain storage unit;

[0120] A node creation module 906 is configured to create an enterprise chain node including the meta-service unit for the enterprise based on the meta-service unit purchased by the enterprise;

[0121] Alliance maintenance module 908, adding the enterprise chain node to an enterprise alliance including multiple different enterprise chain nodes and supervision nodes;

[0122] The alliance transaction module 910 provides a smart contract to the enterprise alliance, so that the multiple enterprise chain nodes in the enterprise alliance can conduct transactions with each other in the enterprise alliance through the smart contract.

[0123] Optionally, the system includes a platform alliance consisting of the cloud service platform and a supervisory party;

[0124] The enterprise authentication module 902 receives authentication information submitted by the enterprise through the cloud service platform;

[0125] According to the authentication information, a corresponding contract transaction is submitted in the platform alliance, and consensus and transaction confirmation are carried out within the platform alliance to determine whether the authentication information is authenticated.

[0126] Optionally, it also includes:

[0127] The business query module 912 creates a chain account of the alliance chain corresponding to the platform alliance for the enterprise after the authentication is passed;

[0128] In response to a business information query request initiated by the enterprise through the chain account, determining a target enterprise targeted by the business information query request in the enterprise alliance served by the cloud service platform;

[0129] Submitting the corresponding contract transaction to the enterprise alliance where the target enterprise is located;

[0130] Receiving the execution result returned by the enterprise alliance after executing the contract in response to the contract transaction;

[0131] The execution result is returned to the enterprise that initiated the business information query request through the chain account, so that the enterprise can obtain the business information of the target enterprise based on the execution result.

[0132] Optionally, the industrial and commercial query module 912, before responding to the industrial and commercial information query request initiated by the enterprise through the chain account, when the enterprise does not yet own the enterprise chain node, receives the industrial and commercial information query request initiated by the enterprise through the chain account, so as to submit the corresponding contract transaction on behalf of the enterprise.

[0133] Optionally, the purchasing service module 904 determines a set of consensus service units and a set of block chain storage units that are pre-separated from the complete consortium chain node service resources;

[0134] According to the specified dimensions, the set of consensus service units and the set of block chain storage units are divided respectively to obtain and display a plurality of differentiated resource subsets so that the enterprise can purchase the resource subsets according to the specified dimensions. The specified dimensions include at least one of the consensus algorithm dimension and the performance specification dimension.

[0135] Optionally, the meta-service unit further includes a metadata unit and / or a proxy service unit;

[0136] The metadata unit is used to store configuration data related to the consensus service unit and / or the block chain storage unit;

[0137] The proxy service unit is responsible for performing automated operation and maintenance operations on one or more of the meta-service units.

[0138] Optionally, the system includes the enterprise party alliance;

[0139] The alliance transaction module 910 obtains the cooperation intention related smart contract provided by the cloud service platform through the first enterprise chain node in the enterprise alliance, and initiates a business intention transaction based on the smart contract;

[0140] The enterprise alliance reaches a consensus on the business intention transaction and makes it public to other enterprise chain nodes in the enterprise alliance;

[0141] Initiate a response transaction through the second enterprise chain node in the enterprise alliance through the smart contract related to the cooperation intention, so as to parse and match the business intention transaction with the response transaction, and synchronize the execution results in the enterprise alliance;

[0142] Through the first enterprise chain node, according to the execution result, a cooperation intention is reached with the second enterprise chain node.

[0143] Optionally, it also includes:

[0144] The unit reassembly transaction module 914 determines the blockchain storage unit targeted by the transaction through mutual transactions conducted within the enterprise alliance and / or mutual transactions conducted between different enterprise alliances;

[0145] Obtaining the block chain storage unit contained in the enterprise chain node of the transaction seller;

[0146] The block chain storage unit is removed from the enterprise chain node of the transaction seller as a unit to be reassembled;

[0147] The unit to be reassembled is reassembled with the enterprise chain node of the transaction buyer to obtain the assembled enterprise chain node, and the corresponding transaction is confirmed to be completed.

[0148] Optionally, the alliance maintenance module 908 determines whether the industry or business relevance between the multiple different enterprise chain nodes is below a set threshold before adding the enterprise chain node to the enterprise alliance comprising the multiple different enterprise chain nodes and the supervision node;

[0149] If so, the plurality of different enterprise chain nodes and supervisory nodes are formed into an enterprise alliance;

[0150] It is determined that the correlation between the enterprise chain node to be newly added and the existing enterprise chain nodes in the enterprise alliance is also lower than the set threshold.

[0151] Optionally, the enterprise chain node of the transaction seller and the enterprise chain node of the transaction buyer belong to different enterprise alliances;

[0152] The device further comprises:

[0153] The unit lending module 916 determines, before reassembling the unit to be reassembled with the enterprise chain node of the transaction buyer, another enterprise chain node having the consensus service unit in the enterprise alliance to which the enterprise chain node of the transaction seller belongs, as a unit lending node;

[0154] Temporarily lend the consensus service unit of the unit lending node and assemble it with the enterprise chain node of the transaction seller, so that the enterprise chain node of the transaction seller temporarily participates in the consensus process of the enterprise alliance to which the enterprise chain node of the transaction seller belongs for the corresponding transaction;

[0155] After the consensus process is completed, the loaned consensus service unit is released and returned to the unit lending node.

[0156] Figure 10 This is a schematic diagram of the structure of an enterprise business processing device based on a cloud service platform provided in one or more embodiments of this specification. The device is applied to a system including the cloud service platform, and the device includes:

[0157] at least one processor; and,

[0158] a memory communicatively connected to the at least one processor; wherein,

[0159] The memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to enable the at least one processor to:

[0160] Receiving authentication information submitted by the enterprise through the cloud service platform and authenticating the enterprise;

[0161] After the authentication is passed, providing the enterprise with a purchasable meta-service unit, wherein the meta-service unit includes a consensus service unit and a block chain storage unit;

[0162] Based on the meta-service units purchased by the enterprise, an enterprise chain node containing the meta-service unit is created for the enterprise. The enterprise chain node has a corresponding proxy service unit. The proxy service unit detects the dynamic changes in the number of the consensus service units under the enterprise chain node. When the consensus service unit is newly added, the corresponding consensus service process is started and mounted to the consensus network load balancing unit deployed on the enterprise chain to which the enterprise chain node belongs for unified management. When the consensus service unit is reduced, the corresponding consensus service process is unmounted from the consensus network load balancing unit.

[0163] Joining the enterprise chain node to an enterprise alliance comprising multiple different enterprise chain nodes and supervisory nodes;

[0164] A smart contract is provided to the enterprise alliance, so that the plurality of enterprise chain nodes in the enterprise alliance can conduct mutual transactions in the enterprise alliance through the smart contract.

[0165] Based on the same idea, one or more embodiments of this specification also provide corresponding Figure 1 A non-volatile computer storage medium according to the method is applied to a system including the cloud service platform, wherein the medium stores computer-executable instructions, and the computer-executable instructions are configured to:

[0166] Receiving authentication information submitted by the enterprise through the cloud service platform and authenticating the enterprise;

[0167] After the authentication is passed, providing the enterprise with a purchasable meta-service unit, wherein the meta-service unit includes a consensus service unit and a block chain storage unit;

[0168] Based on the meta-service units purchased by the enterprise, an enterprise chain node containing the meta-service unit is created for the enterprise. The enterprise chain node has a corresponding proxy service unit. The proxy service unit detects the dynamic changes in the number of the consensus service units under the enterprise chain node. When the consensus service unit is newly added, the corresponding consensus service process is started and mounted to the consensus network load balancing unit deployed on the enterprise chain to which the enterprise chain node belongs for unified management. When the consensus service unit is reduced, the corresponding consensus service process is unmounted from the consensus network load balancing unit.

[0169] Joining the enterprise chain node to an enterprise alliance comprising multiple different enterprise chain nodes and supervisory nodes;

[0170] A smart contract is provided to the enterprise alliance, so that the plurality of enterprise chain nodes in the enterprise alliance can conduct mutual transactions in the enterprise alliance through the smart contract.

[0171] The foregoing description is merely one or more embodiments of this specification and is not intended to limit this specification. It will be apparent to those skilled in the art that various modifications and variations may be made to one or more embodiments of this specification. Any modifications, equivalent substitutions, or improvements made within the spirit and principles of one or more embodiments of this specification are intended to be within the scope of the claims of this specification.

Claims

1. A method for processing enterprise business based on a cloud service platform, applied to a system including the cloud service platform, the method comprising: Receiving authentication information submitted by the enterprise through the cloud service platform and authenticating the enterprise; After the authentication is passed, providing the enterprise with a purchasable meta-service unit, wherein the meta-service unit includes a consensus service unit and a block chain storage unit; Based on the meta-service units purchased by the enterprise, an enterprise chain node containing the meta-service unit is created for the enterprise. The enterprise chain node has a corresponding proxy service unit. The proxy service unit detects the dynamic changes in the number of the consensus service units under the enterprise chain node. When the consensus service unit is newly added, the corresponding consensus service process is started and mounted to the consensus network load balancing unit deployed on the enterprise chain to which the enterprise chain node belongs for unified management. When the consensus service unit is reduced, the corresponding consensus service process is unmounted from the consensus network load balancing unit. Joining the enterprise chain node to an enterprise alliance comprising multiple different enterprise chain nodes and supervisory nodes; A smart contract is provided to the enterprise alliance, so that the plurality of enterprise chain nodes in the enterprise alliance can conduct mutual transactions in the enterprise alliance through the smart contract.

2. The method according to claim 1, wherein the enterprise chain node has a corresponding metadata unit; After creating the enterprise chain node including the meta-service unit for the enterprise, the method further includes: When the block chain storage unit is newly added under the enterprise chain node, the corresponding block chain storage service process is started through the proxy service unit, and the block chain storage service process is registered with the metadata unit; Through the registered block chain storage service process, poll the transaction storage relay status recorded by the metadata unit, obtain the transaction data that has been agreed upon by the consensus service unit from the data queue corresponding to the enterprise chain node, and according to the result of the polling, timely package the transaction data into blocks and perform persistent storage of the blocks.

3. The method according to claim 1, wherein the system comprises a platform alliance consisting of the cloud service platform and a supervisory party; The receiving of authentication information submitted by the enterprise and authenticating the enterprise specifically includes: Receiving authentication information submitted by the enterprise through the cloud service platform; According to the authentication information, a corresponding contract transaction is submitted in the platform alliance, and consensus and transaction confirmation are carried out within the platform alliance to determine whether the authentication information is authenticated.

4. The method according to claim 3, wherein after the authentication is passed, the method further comprises: Create a chain account of the alliance chain corresponding to the platform alliance for the enterprise; In response to a business information query request initiated by the enterprise through the chain account, determining a target enterprise targeted by the business information query request in the enterprise alliance served by the cloud service platform; Submitting the corresponding contract transaction to the enterprise alliance where the target enterprise is located; Receiving the execution result returned by the enterprise alliance after executing the contract in response to the contract transaction; The execution result is returned to the enterprise that initiated the business information query request through the chain account, so that the enterprise can obtain the business information of the target enterprise based on the execution result.

5. The method according to claim 4, before responding to the business information query request initiated by the enterprise through the chain account, the method further comprises: In the case that the enterprise does not yet own the enterprise chain node, receive the business information query request initiated by the enterprise through the chain account, so as to submit the corresponding contract transaction on behalf of the enterprise.

6. The method according to claim 1, wherein providing the enterprise with a purchasable meta-service unit comprises: Determine the set of consensus service units that are pre-separated from the complete consortium chain node service resources, and the set of block chain storage units; According to the specified dimensions, the set of consensus service units and the set of block chain storage units are divided respectively to obtain and display a plurality of differentiated resource subsets so that the enterprise can purchase the resource subsets according to the specified dimensions. The specified dimensions include at least one of the consensus algorithm dimension and the performance specification dimension.

7. The method of claim 1, wherein the system comprises the enterprise party alliance; The plurality of enterprise chain nodes in the enterprise alliance conduct mutual transactions in the enterprise alliance through the smart contract, specifically including: The first enterprise chain node in the enterprise alliance obtains the cooperation intention related smart contract provided by the cloud service platform and initiates a business intention transaction based on it; The enterprise alliance reaches a consensus on the business intention transaction and makes it public to other enterprise chain nodes in the enterprise alliance; The second enterprise chain node in the enterprise alliance initiates a response transaction through the smart contract related to the cooperation intention, so as to parse and match the business intention transaction with the response transaction, and synchronize the execution results in the enterprise alliance; The first enterprise chain node reaches a cooperation intention with the second enterprise chain node based on the execution result.

8. The method of claim 1 , further comprising: Determining the blockchain storage unit targeted by the transaction through mutual transactions conducted within the enterprise alliance and / or mutual transactions conducted between different enterprise alliances; Obtaining the block chain storage unit contained in the enterprise chain node of the transaction seller; The block chain storage unit is removed from the enterprise chain node of the transaction seller as a unit to be reassembled; The unit to be reassembled is reassembled with the enterprise chain node of the transaction buyer to obtain the assembled enterprise chain node, and the corresponding transaction is confirmed to be completed.

9. The method of claim 8, wherein before adding the enterprise chain node to an enterprise alliance comprising a plurality of different enterprise chain nodes and supervisory nodes, the method further comprises: Determine whether the industry or business relevance between multiple different enterprise chain nodes is below a set threshold; If so, the plurality of different enterprise chain nodes and supervisory nodes are formed into an enterprise alliance; It is determined that the correlation between the enterprise chain node to be newly added and the existing enterprise chain nodes in the enterprise alliance is also lower than the set threshold.

10. The method according to claim 8, wherein the enterprise chain node of the transaction seller and the enterprise chain node of the transaction buyer belong to different enterprise alliances; Before reassembling the unit to be reassembled with the enterprise chain node of the transaction buyer, the method further includes: In the enterprise alliance to which the enterprise chain node of the transaction seller belongs, another enterprise chain node having the consensus service unit is determined as the unit lending node; Temporarily lend the consensus service unit of the unit lending node and assemble it with the enterprise chain node of the transaction seller, so that the enterprise chain node of the transaction seller temporarily participates in the consensus process of the enterprise alliance to which the enterprise chain node of the transaction seller belongs for the corresponding transaction; After the consensus process is completed, the loaned consensus service unit is released and returned to the unit lending node.

11. An enterprise business processing device based on a cloud service platform, applied to a system including the cloud service platform, the device comprising: An enterprise authentication module receives authentication information submitted by an enterprise through the cloud service platform and authenticates the enterprise; A purchasing service module, which provides the enterprise with purchasable meta-service units after the authentication is passed, wherein the meta-service units include a consensus service unit and / or a blockchain storage unit; A node creation module creates an enterprise chain node for the enterprise containing the meta-service unit based on the meta-service unit purchased by the enterprise. The enterprise chain node has a corresponding proxy service unit. The proxy service unit detects the dynamic changes in the number of the consensus service units under the enterprise chain node. When the consensus service unit is newly added, the corresponding consensus service process is started and mounted to the consensus network load balancing unit deployed on the enterprise chain to which the enterprise chain node belongs for unified management. When the consensus service unit is reduced, the corresponding consensus service process is unmounted from the consensus network load balancing unit. Alliance maintenance module, adding the enterprise chain node to the enterprise alliance including multiple different enterprise chain nodes and supervision nodes; The alliance transaction module provides a smart contract to the enterprise alliance, so that the multiple enterprise chain nodes in the enterprise alliance can conduct transactions with each other in the enterprise alliance through the smart contract.

12. The apparatus according to claim 11, wherein the enterprise chain node has a corresponding metadata unit; The node creation module, after creating the enterprise chain node including the meta-service unit for the enterprise, starts the corresponding block chain storage service process through the proxy service unit when the block chain storage unit is newly added under the enterprise chain node, and registers the block chain storage service process with the metadata unit; Through the registered block chain storage service process, poll the transaction storage relay status recorded by the metadata unit, obtain the transaction data that has been agreed upon by the consensus service unit from the data queue corresponding to the enterprise chain node, and according to the result of the polling, timely package the transaction data into blocks and perform persistent storage of the blocks.

13. The apparatus according to claim 11, wherein the system comprises a platform alliance consisting of the cloud service platform and a supervisory party; The enterprise authentication module receives authentication information submitted by the enterprise through the cloud service platform; According to the authentication information, a corresponding contract transaction is submitted in the platform alliance, and consensus and transaction confirmation are carried out within the platform alliance to determine whether the authentication information is authenticated.

14. The apparatus of claim 13, further comprising: The industrial and commercial query module creates a chain account of the alliance chain corresponding to the platform alliance for the enterprise after the authentication is passed; In response to a business information query request initiated by the enterprise through the chain account, determining a target enterprise targeted by the business information query request in the enterprise alliance served by the cloud service platform; Submitting the corresponding contract transaction to the enterprise alliance where the target enterprise is located; Receiving the execution result returned by the enterprise alliance after executing the contract in response to the contract transaction; The execution result is returned to the enterprise that initiated the business information query request through the chain account, so that the enterprise can obtain the business information of the target enterprise based on the execution result.

15. The device as described in claim 14, wherein the industrial and commercial query module receives the industrial and commercial information query request initiated by the enterprise through the chain account before responding to the industrial and commercial information query request initiated by the enterprise through the chain account, when the enterprise does not yet own the enterprise chain node, so as to submit the corresponding contract transaction on behalf of the enterprise.

16. The apparatus of claim 11, wherein the service purchasing module determines a set of consensus service units pre-separated from the complete consortium chain node service resources and a set of block chain storage units; According to the specified dimensions, the set of consensus service units and the set of block chain storage units are divided respectively to obtain and display a plurality of differentiated resource subsets so that the enterprise can purchase the resource subsets according to the specified dimensions. The specified dimensions include at least one of the consensus algorithm dimension and the performance specification dimension.

17. The apparatus of claim 11, wherein the system comprises the enterprise party alliance; The alliance transaction module obtains the cooperation intention related smart contract provided by the cloud service platform through the first enterprise chain node in the enterprise alliance, and initiates a business intention transaction based on the smart contract; The enterprise alliance reaches a consensus on the business intention transaction and makes it public to other enterprise chain nodes in the enterprise alliance; Initiate a response transaction through the second enterprise chain node in the enterprise alliance through the smart contract related to the cooperation intention, so as to parse and match the business intention transaction with the response transaction, and synchronize the execution results in the enterprise alliance; Through the first enterprise chain node, according to the execution result, a cooperation intention is reached with the second enterprise chain node.

18. The apparatus of claim 11, further comprising: A unit reassembly transaction module determines a block chain storage unit targeted by a transaction through mutual transactions conducted within the enterprise alliance and / or mutual transactions conducted between different enterprise alliances; Obtaining the block chain storage unit contained in the enterprise chain node of the transaction seller; The block chain storage unit is removed from the enterprise chain node of the transaction seller as a unit to be reassembled; The unit to be reassembled is reassembled with the enterprise chain node of the transaction buyer to obtain the assembled enterprise chain node, and the corresponding transaction is confirmed to be completed.

19. The apparatus of claim 18, wherein the alliance maintenance module determines whether the industry or business relevance between the plurality of different enterprise chain nodes is below a set threshold before adding the enterprise chain node to an enterprise alliance comprising the plurality of different enterprise chain nodes and the supervisory node; If so, the plurality of different enterprise chain nodes and supervisory nodes are formed into an enterprise alliance; It is determined that the correlation between the enterprise chain node to be newly added and the existing enterprise chain nodes in the enterprise alliance is also lower than the set threshold.

20. The device according to claim 18, wherein the enterprise chain node of the transaction seller and the enterprise chain node of the transaction buyer belong to different enterprise alliances; The device further comprises: The unit lending module determines, before reassembling the unit to be reassembled with the enterprise chain node of the transaction buyer, another enterprise chain node having the consensus service unit in the enterprise alliance to which the enterprise chain node of the transaction seller belongs, as a unit lending node; Temporarily lend the consensus service unit of the unit lending node and assemble it with the enterprise chain node of the transaction seller, so that the enterprise chain node of the transaction seller temporarily participates in the consensus process of the enterprise alliance to which the enterprise chain node of the transaction seller belongs for the corresponding transaction; After the consensus process is completed, the loaned consensus service unit is released and returned to the unit lending node.

21. An enterprise business processing device based on a cloud service platform, applied to a system including the cloud service platform, the device comprising: at least one processor; as well as, a memory communicatively connected to the at least one processor; wherein, The memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to enable the at least one processor to: Receiving authentication information submitted by the enterprise through the cloud service platform and authenticating the enterprise; After the authentication is passed, providing the enterprise with a purchasable meta-service unit, wherein the meta-service unit includes a consensus service unit and a block chain storage unit; Based on the meta-service units purchased by the enterprise, an enterprise chain node containing the meta-service unit is created for the enterprise. The enterprise chain node has a corresponding proxy service unit. The proxy service unit detects the dynamic changes in the number of the consensus service units under the enterprise chain node. When the consensus service unit is newly added, the corresponding consensus service process is started and mounted to the consensus network load balancing unit deployed on the enterprise chain to which the enterprise chain node belongs for unified management. When the consensus service unit is reduced, the corresponding consensus service process is unmounted from the consensus network load balancing unit. Joining the enterprise chain node to an enterprise alliance comprising multiple different enterprise chain nodes and supervisory nodes; A smart contract is provided to the enterprise alliance, so that the plurality of enterprise chain nodes in the enterprise alliance can conduct mutual transactions in the enterprise alliance through the smart contract.

Images