Deployment method, operation method and alliance chain network of alliance chain network

Abstract

The present disclosure relates to a method for deploying a consortium chain network, comprising: establishing a cloud-native container cluster, deploying one or more first consortium chain nodes of the consortium chain network in one or more containers of the cloud-native container cluster; establishing an edge computing node, the edge computing node joining the cloud-native container cluster through a container cluster API of the cloud-native container cluster; and deploying one or more second consortium chain nodes of the consortium chain network in one or more containers of the edge computing node. The present disclosure also relates to a method for running a consortium chain network and a consortium chain network.

Description

TECHNICAL FIELD

[0001] One or more embodiments of the present disclosure relate to a deployment method of a consortium chain network, a running method of the consortium chain network, and the consortium chain network. BACKGROUND

[0002] With the development of blockchain technology, a business processing mode based on a consortium chain network is relatively common. A plurality of service institutions can form a consortium, and a server (or a server cluster) of each service institution can be regarded as a node in the consortium chain network. For any service institution, the node managed by the service institution is usually responsible for receiving a business-related transaction initiated by a customer of the service institution, and then broadcasting the business-related transaction to the entire network, so that each node executes the business-related transaction and writes the business-related transaction into a blockchain for distributed storage. SUMMARY

[0003] One or more embodiments of the present disclosure relate to a deployment method of a consortium chain network, a running method of the consortium chain network, and the consortium chain network.

[0004] According to an aspect of one or more embodiments of the present disclosure, a deployment method of a consortium chain network is provided, including: establishing a cloud-native container cluster, deploying one or more first consortium chain nodes of the consortium chain network in one or more containers of the cloud-native container cluster; establishing an edge computing node, the edge computing node joining the cloud-native container cluster through a container cluster API of the cloud-native container cluster; and deploying one or more second consortium chain nodes of the consortium chain network in one or more containers of the edge computing node.

[0005] According to another aspect of one or more embodiments of the present disclosure, a deployment method of a consortium chain network is provided, including: establishing a cloud-native container cluster located in a first region, deploying one or more first consortium chain nodes of the consortium chain network in the cloud-native container cluster; establishing an edge computing node located in a second region, the edge computing node accessing a container cluster API of the cloud-native container cluster, and deploying one or more second consortium chain nodes of the consortium chain network in the edge computing node; and establishing a cloud-native management plane associated with the cloud-native container cluster and a consortium chain management platform, the cloud-native management plane managing the cloud-native container cluster and the edge computing node, and the consortium chain management platform managing the consortium chain network.

[0006] According to still another aspect of one or more embodiments of the present disclosure, there is provided a method for operating a consortium chain network, the consortium chain network comprising: one or more first consortium chain nodes deployed in a cloud-native container cluster; and one or more second consortium chain nodes deployed in an edge computing node, wherein the edge computing node joins the cloud-native container cluster through a container cluster API of the cloud-native container cluster, and wherein the method comprises: generating, by a consortium chain management platform, a resource description file for the consortium chain nodes and submitting the resource description file to a cloud-native management plane; submitting, by the cloud-native management plane, the resource description file to the cloud-native container cluster, and updating, by the cloud-native container cluster, the one or more first consortium chain nodes according to the resource description file; and receiving, by the edge computing node, the resource description file via the container cluster API, and updating the one or more second consortium chain nodes according to the resource description file.

[0007] According to still another aspect of one or more embodiments of the present disclosure, there is provided a consortium chain network, comprising: one or more first consortium chain nodes deployed in a container cluster of a cloud-native container cluster located in a first region; and one or more second consortium chain nodes deployed in an edge computing node located in a second region, wherein the edge computing node joins the cloud-native container cluster through a container cluster API of the cloud-native container cluster, and wherein the cloud-native container cluster and the edge computing node are managed by a cloud-native management plane established in association with the cloud-native container cluster.

[0008] Other features and advantages of the present disclosure will become apparent from the following detailed description of exemplary embodiments of the present disclosure with reference to the drawings. BRIEF DESCRIPTION OF DRAWINGS

[0009] The accompanying drawings, which constitute a part of this specification, illustrate one or more embodiments of the present disclosure and together with the description, explain the principles of one or more embodiments of the present disclosure.

[0010] Reference will now be made to the drawings, in which embodiments of the present disclosure will be described. The goal of the detailed description is to explain one or more embodiments of the present disclosure, and not necessarily to mention all features of the present disclosure.

[0011] Figure 1 is a schematic diagram of an example consortium chain network;

[0012] Figure 2 is a flowchart of a deployment method of a consortium chain network according to one or more exemplary embodiments of the present disclosure;

[0013] Figures 3 to 5 is a schematic diagram of a deployment method of a consortium chain network according to one or more exemplary embodiments of the present disclosure;

[0014] Figure 6 is a flowchart of a method of operating a consortium chain network according to one or more example embodiments of the present disclosure. DETAILED DESCRIPTION

[0015] In order to better understand the technical solutions in the specification, the technical solutions in the specification will be clearly and completely described below in combination with the drawings in the specification. Obviously, the described embodiments are only some of the embodiments of the specification, not all the embodiments. It should be understood that one or more embodiments of the present disclosure can be presented in many different ways, and are not limited to the embodiments described below. It should also be understood that one or more embodiments of the present disclosure can be combined in various ways to provide more additional embodiments. Based on the embodiments in the specification, all other embodiments obtained by those of ordinary skill in the art without creative labor should fall within the scope of protection of the specification.

[0016] It should be understood that in all the drawings, the same reference signs represent the same elements. In the drawings, the size of some features can be distorted for the sake of clarity.

[0017] It should be understood that the language used herein is only used to describe specific embodiments and is not intended to be limiting. Unless otherwise defined, all terms (including technical and scientific terms) used herein have meanings commonly understood by those of ordinary skill in the art. Well-known functions or constructions can not be described in detail for the sake of brevity and / or clarity.

[0018] In this document, the term "connected" is intended to include a physical, electrical, and / or communicational connection between one feature and another, and that the one feature and another can or can not exist between the one feature and another. When the connection is a communicational connection, even if it is mentioned that A and B are "directly connected", it is only intended to emphasize that there is no one or more features emphasized by one or more embodiments of the present disclosure between the connection of A and B, but it does not mean that A and B are connected without any element, and those skilled in the art should understand that A and B can be connected through a cable, router, gateway, channel, link, network, etc. It should be noted that in the drawings of one or more embodiments of the present disclosure, whether A and B are directly connected or indirectly connected is represented by a straight line or other graphical elements connected between A and B.

[0019] In this document, the term "A or B" includes "A and B" and "A or B", but not exclusively only "A" or only "B", unless otherwise specified.

[0020] In this document, the terms "example" and "exemplary" mean "serving as an example, instance, or illustration," and not "preferred" over other implementations. In this context, any implementation described in the specification as an "example" or "exemplary" is not necessarily to be construed as preferred over other implementations. Likewise, the terms "for example" or "e.g." do not mean "for the purpose of example" or "for the purpose of exemplification." Rather, these terms mean "by way of example."

[0021] In this document, the term "substantially" is used to account for any imperfections in design, manufacturing, workmanship, environmental influences, and / or other factors. The term "substantially" also allows for differences between a perfect or ideal situation and a real-world implementation.

[0022] In addition, "first," "second," and other similar terms can also be used herein, simply for purposes of reference and thus do not necessarily infer or require a sequence or order to them. For example, unless the context clearly indicates otherwise, words describing the structure or elements "first," "second," and other such numerical terms do not imply a sequence or order to the elements bound by these terms.

[0023] It is also to be understood that the term "comprising" or "including" when used in this specification, specifies the presence of stated features, integers, steps, operations, elements, or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof.

[0024] Figure 1 is a schematic diagram of an example consortium chain network. The example consortium chain network has multiple participants, such as multiple enterprises, and each participant can have one or more consortium chain nodes. Cloud-native container clusters are increasingly being applied in enterprises, and in order to fully obtain the various advantages provided by cloud-native container cluster technology, it has become increasingly popular to deploy consortium chains in container clusters. However, general cloud-native clusters are usually centrally deployed in a geographically proximate network, and consortium participants distributed in different regions all hope to deploy consortium chain nodes in a physical location close to their own enterprise business. In this way, how to deploy and operate consortium chains using cloud-native container cluster technology between enterprises distributed in different geographic locations will face various challenges in terms of cost and technology.

[0025] Currently, in order to fully utilize cloud-native container technology, the following two methods are usually used to deploy consortium chain. Method one: the main network of the consortium chain is deployed in a container cluster, and the lightweight node is deployed using non-container technology. In this deployment method, since the main network and the lightweight node use different technical architectures, not only the difficulty and complexity of deployment, management and maintenance are increased, but also the lightweight node cannot fully utilize the technical advantages of the cloud-native container cluster. Method two: the main network is deployed in a container cluster, and the lightweight node is deployed in another container cluster. For this deployment method, for the lightweight node, the additional management resource consumption of the container cluster increases the cost, and the management and maintenance of multiple clusters also increase the management and maintenance cost of the consortium chain. For example, when the consortium chain node needs to be upgraded, coordination and communication must be carried out between different nodes to complete the overall upgrade of all consortium chain nodes.

[0026] One or more embodiments of the present disclosure provide a deployment method of a consortium chain network using cloud-native container technology, using a cloud-native container cluster such as a Kubernetes cluster to manage the main network of the management center, and adding the lightweight consortium chain nodes distributed in various places as edge nodes to the container cluster, and centrally and uniformly managing the cloud-native container cluster and the edge nodes, thereby realizing centralized and uniform management of each node of the consortium chain using cloud-native container technology.

[0027] Figure 2 is a flowchart of a deployment method 100 of a consortium chain network according to one or more example embodiments of the present disclosure. The method 100 includes: establishing a cloud-native container cluster, deploying one or more first consortium chain nodes of a consortium chain network in one or more containers of the cloud-native container cluster (operation 110); establishing an edge computing node, the edge computing node joining the cloud-native container cluster through a container cluster API of the cloud-native container cluster (operation 120); and deploying one or more second consortium chain nodes of the consortium chain network in one or more containers of the edge computing node (operation 130).

[0028] The cloud-native container cluster can be established in the first region. The cloud-native container cluster established can be, for example, a Kubernetes cluster. Those skilled in the art should understand that the cloud-native container cluster in the embodiments of the present disclosure is not limited to a Kubernetes cluster, and can also be applied to, for example, an openshift cluster, a swarm cluster, and the like. One or more first alliance chain nodes deployed in one or more containers of the cloud-native container cluster can be full-level nodes of the alliance chain network, that is, the main network of the alliance chain is deployed in the cloud-native container cluster. In addition, a cloud-native management plane and an alliance chain management platform can also be established in association with the cloud-native container cluster, for example, can be set in the Master resource of the Kubernetes cluster. In terms of geographical location, the cloud-native management plane and the alliance chain management platform can be located in the first region where the cloud-native container cluster is located. The cloud-native management plane can be provided by a cloud platform provider, for example, which manages the cloud-native container cluster and the edge computing nodes that join the cloud-native container cluster. Specifically, the cloud-native management plane manages the resources of the computing nodes, for example, the interaction between the computing nodes of the container cluster, the joining of the computing nodes to the container cluster, the leaving of the computing nodes from the container cluster, and the like. The alliance chain management platform can be operated by a provider of the alliance chain network, for example, which manages the alliance chain network, for example, creates and deletes alliance chain nodes, and the like.

[0029] The edge computing node can be established in a second region different from the first region. One or more second alliance chain nodes deployed in one or more containers of the edge computing node can be light-level nodes of the alliance chain network, that is, the light-level nodes are deployed in the edge computing node. The edge computing node can access the container cluster API of the cloud-native container cluster via a public network, a private line network, a proxy network, an internal network, an IDC machine room, or the like, so as to join the cloud-native container cluster. In this way, the cloud-native management plane for managing the container cluster can centrally and uniformly manage, that is, the cloud-native management plane manages the cloud-native container cluster located in the first region and the edge computing node located in the second region. Therefore, the alliance chain management platform can centrally and uniformly manage the first alliance chain nodes deployed in the cloud-native container cluster located in the first region and the second alliance chain nodes deployed in the edge computing node located in the second region. In this way, some nodes (second alliance chain nodes) of the alliance chain can be arranged in a geographical region far away from the main network (first alliance chain nodes) of the alliance chain, so as to facilitate the participants of the alliance chain to deploy alliance chain nodes according to their own production needs, for example, to arrange nodes related to their own enterprises in a geographical region close to their own enterprises but far away from the main network, while being able to apply the cloud-native container cluster technology of centralized and uniform management in the entire alliance chain.

[0030] Although the native container clusters and edge computing nodes described in the above embodiments are located in different regions, those skilled in the art should understand that the embodiments of this disclosure do not limit the geographical location of the native container clusters and edge computing nodes. In other embodiments, the native container clusters and edge computing nodes may be located in the same region, for example, due to network limitations or compliance requirements, the native container clusters and edge computing nodes may be established in the same region (e.g., within the same data center).

[0031] The following reference Figures 3 to 5 This document describes a method for deploying a consortium blockchain network according to exemplary embodiments of the present disclosure, using a specific example. Figure 3 As shown, a cloud-native container cluster is created in region A, and a cloud-native management plane and a consortium blockchain management platform are deployed to manage the container cluster and the consortium blockchain respectively. Figure 4 As shown, an edge node is established in region B. The edge node accesses the container cluster API from the intranet or IDC data center of region B via public network / wired connection or proxy, thereby joining the container cluster. Figure 5 As shown, consortium blockchain nodes are deployed in edge nodes. Specifically, the cloud-native management plane submits the resource description file for the new consortium blockchain node to the cloud-native container cluster (as shown by reference numeral #1 in the attached figure). The edge computing node receives the resource description file via the container cluster API (as shown by reference numeral #2 in the attached figure). The edge computing node allocates resources for the consortium blockchain node deployed within it according to the resource description file to start the consortium blockchain node, and joins the consortium blockchain network according to the corresponding configuration parameters. The resource description file can be generated by the consortium blockchain management platform based on parameters configured by the user (e.g., the consortium blockchain provider) and submitted to the cloud-native management plane.

[0032] It should be understood that the term "new" node in a consortium blockchain as used in this article refers to a node that will join the consortium blockchain, but the node may already be a node in another consortium blockchain, such as in the Fabric consortium blockchain network where a node joins multiple channels (or subnets).

[0033] Figure 6 This is a flowchart of a method 200 for operating a consortium blockchain network according to one or more exemplary embodiments of this disclosure. Method 200 includes: generating resource description files for consortium blockchain nodes by a consortium blockchain management platform and submitting them to a cloud-native management plane (operation 210); submitting the resource description files to a cloud-native container cluster by the cloud-native management plane, and updating one or more first consortium blockchain nodes according to the resource description files by the cloud-native container cluster (operation 220); and receiving the resource description files by an edge computing node via a container cluster API and updating one or more second consortium blockchain nodes according to the resource description files (operation 230).

[0034] The method 200 can be used for upgrading the consortium chain nodes, such as updating the version of the application, upgrading the specification of the computing instance (such as expanding the computing resources and / or storage resources), service expansion of the nodes (increasing the number of computing instances for each node), and the like. The consortium chain management platform can generate a resource description file to describe the parameters that need to be upgraded according to the capabilities of the container cluster provided by the cloud native management plane, and then submit the resource description file to the cloud native management plane. The cloud native management plane updates each node according to the resource description file to meet the requirements of the description file.

[0035] The resource description file for the consortium chain nodes (including new nodes) mentioned in the description of the embodiments of the present disclosure can include establishing several consortium chain nodes, deploying each consortium chain node on which edge computing unit, deploying several computing instances for each consortium chain node, how many computing and storage resources each instance has, and the like. The user, such as the consortium chain provider, can input these parameters to the consortium chain management platform, and the consortium chain management platform will generate a resource description file according to these parameters in the background and then submit it to the cloud native management plane.

[0036] Through the scheme provided by one or more embodiments of the present disclosure, the advantages of the cloud native container cluster can be fully utilized, the deployment, management and maintenance of the consortium chain can be simplified through the centralized container cluster control center, and the management, operation and maintenance cost of the lightweight nodes can be reduced by using the characteristics of the edge container cluster nodes.

[0037] The above describes one or more exemplary embodiments of the present disclosure. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims can be performed in a different order than the order in which they are recited and still achieve the desired results. In addition, the processes depicted in the figures do not necessarily require the particular order shown, or sequential order, to achieve the desired results. In certain implementations, multitasking and parallel processing can be advantageous or necessary.

[0038] In the 1990s, it was quite obvious to distinguish whether an improvement in a technology was in hardware (e.g., improvement in circuit structures of diodes, transistors, switches, etc.) or in software (improvement in method flow). However, as technology has evolved, many improvements in method flow today can be considered as direct improvements in hardware circuit structures. Designers almost always obtain the corresponding hardware circuit structures by programming the improved method flow into hardware circuits. Therefore, it cannot be said that an improvement in a method flow cannot be implemented by hardware entity modules. For example, a programmable logic device (PLD) (e.g., a field programmable gate array (FPGA)) is an integrated circuit whose logic function is determined by user programming of the device. A digital system is "integrated" on a PLD by the designer programming it, rather than by asking a chip manufacturer to design and fabricate a custom integrated circuit chip. Moreover, instead of manually fabricating integrated circuit chips, this programming is now mostly implemented by "logic compiler" software, which is similar to software compilers used in program development, and the original code to be compiled is written in a specific programming language, which is called a hardware description language (HDL), and there are many such languages, such as ABEL (Advanced Boolean Expression Language), AHDL (Altera Hardware Description Language), Confluence, CUPL (Cornell University Programming Language), HDCal, JHDL (Java Hardware Description Language), Lava, Lola, MyHDL, PALASM, RHDL (Ruby Hardware Description Language), etc., and the most commonly used are VHDL (Very-High-Speed Integrated Circuit Hardware Description Language) and Verilog. Those skilled in the art should be aware that, as long as the method flow is logically programmed in the above-mentioned hardware description languages and programmed into an integrated circuit, a hardware circuit implementing the logical method flow can be easily obtained.

[0039] The controller can be implemented in any suitable way, for example, the controller can take the form of, for example, a microprocessor or processor and a computer readable medium storing computer readable program code, such as software or firmware, executable by the (micro)processor, logic gates, switches, an application specific integrated circuit (ASIC), a programmable logic controller and an embedded microcontroller, examples of which include but are not limited to the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20 and Silicone Labs C8051F320, the memory controller can also be implemented as part of the control logic of the memory. The skilled person will also appreciate that, in addition to implementing the controller in pure computer readable program code, it is possible to implement the controller in the form of logic gates, switches, an application specific integrated circuit, a programmable logic controller and an embedded microcontroller, etc. to perform the same functions by logically programming the method steps. Such a controller can therefore be considered to be a hardware component, and the means included therein to perform the various functions can also be considered to be structures within the hardware component. Alternatively, or even additionally, the means to perform the various functions can be considered to be both a software module implementing the method and a structure within a hardware component.

[0040] The systems, apparatuses, modules or units illustrated by the above embodiments can be specifically implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a server system. Of course, the present application does not rule out that with the development of future computer technologies, computers implementing the functions of the above embodiments can be personal computers, laptop computers, vehicle human-computer interaction devices, cellular phones, camera phones, smart phones, personal digital assistants, media players, navigation devices, email devices, game consoles, tablet computers, wearable devices, or combinations of any of these devices.

[0041] Although the method operations of the embodiments of the present disclosure are described in a particular, sequential order, one or more of the method operations can be omitted, or the method operations can be performed in an order other than the described order. Additionally, one or more of the method operations can be performed concurrently, or with partial concurrence. Furthermore, one or more of the method operations can be performed by different entities, or over different time periods. The term "including" as used herein is intended to mean "comprising," such that the process, method, article, or apparatus that includes elements in addition to those specified. As used in this description, the term "coupled" means a direct or indirect connection, which can be physical or logical. The term "coupled" does not relate to a direct connection or wiring.

[0042] For the sake of description, the above-described apparatus is described as various modules to describe the functions of the apparatus. Of course, when implementing one or more embodiments of the present disclosure, the functions of the modules can be implemented in one or more software and / or hardware, or the modules implementing the same functions can be combined into a plurality of sub-modules or sub-units. The apparatus embodiments described above are merely illustrative, for example, the division of the units is merely a logical function division, and actual implementation can have another division manner, for example, a plurality of units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the coupling or direct coupling or communication connection between the units or components shown or discussed can be indirect coupling or communication connection through some interfaces, devices or units, and can be electrical, mechanical or other forms.

[0043] The present disclosure is described with reference to the flowcharts and / or block diagrams of the methods, apparatus (systems) and computer program products according to embodiments of the present disclosure. It should be understood that each flow and / or block in the flowcharts and / or block diagrams can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing apparatus to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing apparatus generate a means for implementing the functions specified in the flowcharts and / or block diagrams. Figure 1 The functions of one or more flows and / or blocks Figure 1 The apparatus that implements the functions specified in one or more flows and / or blocks.

[0044] These computer program instructions can also be stored in a computer- readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instructions which implement the Figure 1 function specified in the flow or flows and / or blocks Figure 1 of the block or blocks.

[0045] These computer program instructions can also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the Figure 1 function specified in the flow or flows and / or blocks Figure 1 of the block or blocks.

[0046] In a typical configuration, a computing device includes one or more processors (CPUs), input / output interfaces, network interfaces, and memory.

[0047] The memory can include non-persistent memory and / or volatile memory, such as random access memory (RAM) and / or cache memory, non-volatile memory, such as read-only memory (ROM), EPROM, and / or flash memory. The memory is an example of computer-readable media.

[0048] Computer-readable media includes permanent and non-permanent, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disc read-only memory (CD-ROM), digital versatile disc (DVD), or other optical storage, magnetic cassettes, magnetic tapes, magnetic disk storage, graphene storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information accessible to computing devices. According to the definition herein, computer-readable media does not include transitory media, such as modulated data signals and carrier waves.

[0049] Those skilled in the art will appreciate that the one or more embodiments described herein can be provided as a method, a system or a computer program product. Accordingly, the one or more embodiments described herein can take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the one or more embodiments described herein can take the form of a computer program product on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROMs, optical storage devices, etc.) embodying computer readable code.

[0050] The one or more embodiments described herein can be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc., that perform particular tasks or implement particular abstract data types. The one or more embodiments described herein can also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules can be located in both local and remote computer storage media including memory storage devices.

[0051] The various embodiments described in this specification can be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc., that perform particular tasks or implement particular abstract data types. The various embodiments described in this specification can also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules can be located in both local and remote computer storage media including memory storage devices.

[0052] The above description is only some embodiments of the one or more embodiments described in this specification and is not intended to limit the one or more embodiments described in this specification. Those skilled in the art can make various modifications and changes to the one or more embodiments described in this specification. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principle of the one or more embodiments described in this specification shall be included in the scope of the claims.

Claims

1. A method for deploying a consortium blockchain network, comprising: Establish a cloud-native container cluster, and deploy one or more first consortium blockchain nodes of the consortium blockchain network in one or more containers of the cloud-native container cluster; Establish edge computing nodes, which join the cloud-native container cluster via the container cluster API of the cloud-native container cluster; A cloud-native management plane is established in association with the cloud-native container cluster, which manages the cloud-native container cluster and the added edge computing nodes; Deploying one or more second consortium blockchain nodes of the consortium blockchain network in one or more containers of the edge computing node includes: submitting a resource description file for the new consortium blockchain node to the cloud-native container cluster by the cloud-native management plane; receiving the resource description file by the edge computing node via the container cluster API; allocating resources for the one or more second consortium blockchain nodes according to the resource description file; and starting the one or more second consortium blockchain nodes, so that the one or more second consortium blockchain nodes join the consortium blockchain network.

2. The method according to claim 1, further comprising: A consortium blockchain management platform is established in association with the cloud-native container cluster, and the consortium blockchain management platform manages the consortium blockchain network.

3. The method according to claim 1, wherein, At least one of the one or more first consortium chain nodes is a full-scale node, and at least one of the one or more second consortium chain nodes is a lightweight node.

4. The method according to claim 1, wherein, The cloud-native container cluster is located in a first region, and the edge computing node is located in a second region, which is different from the first region.

5. The method according to claim 1, wherein, The edge computing nodes access the container cluster API via one or more of the following: public network, leased network, proxy network, internal network, or IDC data center.

6. The method according to claim 2, further comprising: The resource description file is generated by the consortium blockchain management platform and submitted to the cloud-native management plane.

7. The method according to claim 1, wherein, The cloud-native container cluster includes a Kubernetes cluster.

8. A method for deploying a consortium blockchain network, comprising: Establish a cloud-native container cluster located in the first region, and deploy one or more first consortium blockchain nodes of the consortium blockchain network in the cloud-native container cluster; Establish an edge computing node located in a second region, the edge computing node accessing the container cluster API of the cloud-native container cluster, and deploy one or more second consortium blockchain nodes of the consortium blockchain network in the edge computing node; as well as Establish a cloud-native management plane and a consortium blockchain management platform associated with the cloud-native container cluster. The cloud-native management plane manages the cloud-native container cluster and the edge computing nodes, and the consortium blockchain management platform manages the consortium blockchain network. Deploying one or more second consortium blockchain nodes in the edge computing nodes includes: The cloud-native management plane submits the resource description file for the new node of the consortium blockchain to the cloud-native container cluster. The edge computing node receives the resource description file via the container cluster API, allocates resources for the one or more second consortium chain nodes according to the resource description file, and starts the one or more second consortium chain nodes so that the one or more second consortium chain nodes join the consortium chain network.

9. The method according to claim 8, wherein, The cloud-native management plane and the consortium blockchain management platform are located in the first region.

10. The method according to claim 8, wherein, At least one of the one or more first consortium chain nodes is a full-scale node, and at least one of the one or more second consortium chain nodes is a lightweight node.

11. The method according to claim 8, wherein, The edge computing nodes access the container cluster API of the cloud-native container cluster via one or more of the following: public network, leased line network, proxy network, internal network, or IDC data center.

12. The method according to claim 8, further comprising: The resource description file is generated by the consortium blockchain management platform and submitted to the cloud-native management plane.

13. The method according to claim 8, wherein, The cloud-native container cluster includes a Kubernetes cluster.

14. A method for operating a consortium blockchain network, the consortium blockchain network comprising: One or more first-level consortium blockchain nodes are deployed in a cloud-native container cluster; as well as One or more second consortium blockchain nodes are deployed in edge computing nodes, wherein the edge computing nodes join the cloud-native container cluster via the container cluster API of the cloud-native container cluster. The method includes: The consortium blockchain management platform generates resource description files for consortium blockchain nodes and submits them to the cloud-native management plane; The cloud-native management plane submits the resource description file to the cloud-native container cluster, and the cloud-native container cluster updates the one or more first consortium blockchain nodes according to the resource description file; and The edge computing node receives the resource description file via the container cluster API and updates the one or more second consortium chain nodes according to the resource description file.

15. The method according to claim 14, wherein, The cloud-native container cluster is located in a first region, and the edge computing node is located in a second region, which is different from the first region.

16. The method according to claim 15, wherein, The cloud-native management plane and the consortium blockchain management platform are located in the first region.

17. The method of claim 14, wherein, At least one of the one or more first consortium chain nodes is a full-scale node, and at least one of the one or more second consortium chain nodes is a lightweight node.

18. The method according to claim 14, wherein, The edge computing nodes access the container cluster API of the cloud-native container cluster via one or more of the following: public network, leased line network, proxy network, internal network, or IDC data center.

19. The method of claim 14, wherein, The cloud-native container cluster includes a Kubernetes cluster.

20. A consortium blockchain network, comprising: One or more first consortium blockchain nodes are deployed in a container cluster of cloud-native container clusters located in the first region; as well as One or more second consortium blockchain nodes are deployed in edge computing nodes located in a second geographic region, wherein, The edge computing node joins the cloud-native container cluster via the container cluster API of the cloud-native container cluster. The cloud-native container cluster and the edge computing node are managed by a cloud-native management plane established in association with the cloud-native container cluster. The cloud-native container cluster is configured to update one or more first consortium blockchain nodes according to resource description files for consortium blockchain nodes submitted by the cloud-native management plane. The edge computing node is configured to receive the resource description files via the container cluster API and update one or more second consortium blockchain nodes according to the resource description files.

21. The consortium blockchain network according to claim 20, wherein, The consortium blockchain network is managed by a consortium blockchain management platform established in association with the cloud-native container cluster; and The resource description file is generated and submitted to the cloud-native management plane by the consortium blockchain management platform.

22. The consortium blockchain network according to claim 20, wherein, The cloud-native management plane is located in the first region.

23. The consortium blockchain network according to claim 20, wherein, At least one of the one or more first consortium chain nodes is a full-scale node, and at least one of the one or more second consortium chain nodes is a lightweight node.

24. The consortium blockchain network according to claim 20, wherein, The edge computing nodes access the container cluster API of the cloud-native container cluster via one or more of the following: public network, leased line network, proxy network, internal network, or IDC data center.

25. The consortium blockchain network according to claim 20, wherein, The cloud-native container cluster includes a Kubernetes cluster.

Images