Gateway changing method, device, electronic device and computer storage medium

Abstract

The present application provides a gateway change method, device, electronic device and computer storage medium, the method comprising: receiving a gateway change strategy; wherein the gateway change strategy includes the cluster that needs to be changed this time and the gateway that needs to be changed within the cluster that needs to be changed, the upgrade strategy corresponding to the gateway that needs to be changed, and the target cluster change invariant; then, for each gateway that needs to be changed in the same cluster, the gateway that needs to be changed is changed in turn according to the upgrade strategy corresponding to the gateway that needs to be changed; before, during and after the cluster is changed, the current cluster invariant is calculated respectively; wherein the invariant refers to a judgment that any stable state before, during and after the change remains true; when the current cluster change invariant does not match the target cluster change invariant, a first alarm message is generated. The present application provides a standardized change process, and at the same time, improves the correctness verification between clusters.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a gateway change method, device, electronic device and computer storage medium. Background Art

[0002] Since 24 / 7 uninterrupted application services require that gateway services cannot be interrupted, gateway upgrades need to be performed in a polling manner to ensure that at least one gateway in the cluster survives if network capacity permits. At the same time, the correctness of gateway upgrades is extremely high. If a gateway is uncontrollable or the correctness of the gateway cannot be determined, production incidents may occur.

[0003] Currently, the common methods for gateway changes and change verification include manually checking the correctness of gateway operation status, upgrading gateways one by one, taking into account the service status of other gateways in the same cluster during changes, and defining and verifying post-upgrade verification indicators.

[0004] However, the correctness of gateway upgrades based on manual judgment often relies on personal experience, there are individual differences in verification methods, there is a lack of unified standards, and the change process cannot form a standard; at the same time, in order to view the overall status of the gateway cluster, it is necessary to check the status of other gateways in the cluster from time to time when making changes. Switching operations on different gateways is risky and can easily cause operational errors, thereby causing production incidents caused by operational errors. Summary of the invention

[0005] In view of this, the present application provides a gateway change method, device, electronic device and computer storage medium. The present application provides a standardized change process to ensure correctness. At the same time, it improves the correctness verification between clusters. Only a single operation is required during the change, shortening the gateway change cycle, reducing the risk of implementing the change operation, and improving the speed of determining the correctness of the change.

[0006] The first aspect of the present application provides a gateway change method, comprising:

[0007] Receive a gateway change strategy; wherein the gateway change strategy includes the cluster to be changed this time, the gateway to be changed in the cluster to be changed, the upgrade strategy corresponding to the gateway to be changed, and the target cluster change invariant; the target cluster change invariant is generated according to the planning information of the cloud network;

[0008] For each gateway that needs to be changed in the same cluster, the gateway that needs to be changed is changed in turn according to the upgrade strategy corresponding to the gateway that needs to be changed;

[0009] Before, during, and after the cluster is changed, respectively, a current inter-cluster invariant is calculated; wherein the invariant refers to a determination that any stable state before, during, and after the change is maintained to be true;

[0010] When the current inter-cluster invariant does not match the target inter-cluster change invariant, a first alarm message is generated.

[0011] Optionally, different clusters can make changes in parallel.

[0012] Optionally, if before the cluster is changed, the current inter-cluster invariant is calculated before, during, and after the cluster is changed, respectively, including:

[0013] Before the cluster is changed, current first target comparison data is obtained; wherein the data source of the first target comparison data includes at least: a cloud management and control database and gateway operation status information;

[0014] A current inter-cluster invariant is generated according to the current first target comparison data.

[0015] Optionally, for each gateway that needs to be changed in the same cluster, changing the gateway that needs to be changed in turn according to the upgrade strategy corresponding to the gateway that needs to be changed includes:

[0016] The gateway that needs to be changed receives gateway neighbor information through a data stream;

[0017] Before, during and after the gateway that needs to be changed is changed, respectively calculating a current single gateway invariant;

[0018] When the current single gateway invariant does not match the target gateway invariant, second alarm information is generated.

[0019] Optionally, if before the gateway that needs to be changed is changed, the current single gateway invariant is calculated before, during, and after the gateway that needs to be changed is changed, including:

[0020] Before the gateway to be changed is changed, the current second target comparison data is obtained; wherein the data source of the second target comparison data includes at least: a cloud management and control database and gateway operation status information;

[0021] A current single gateway invariant is generated according to the current second target comparison data.

[0022] A second aspect of the present application provides a gateway change device, including:

[0023] A first receiving unit is used to receive a gateway change strategy; wherein the gateway change strategy includes the cluster that needs to be changed this time and the gateway that needs to be changed in the cluster that needs to be changed, the upgrade strategy corresponding to the gateway that needs to be changed, and the target cluster change invariant; the target cluster change invariant is generated according to the planning information of the cloud network;

[0024] A changing unit, configured to change each gateway that needs to be changed in the same cluster in turn according to an upgrade strategy corresponding to the gateway that needs to be changed;

[0025] A first calculation unit is used to calculate the current inter-cluster invariant before, during, and after the cluster is changed; wherein the invariant refers to a determination that any stable state before, during, and after the change is maintained to be true;

[0026] The first generating unit is configured to generate first alarm information when the current inter-cluster invariant does not match the target inter-cluster change invariant.

[0027] Optionally, different clusters can make changes in parallel.

[0028] Optionally, before the cluster is changed, the first computing unit includes:

[0029] A first acquisition unit is used to acquire current first target comparison data before the cluster is changed; wherein the data source of the first target comparison data includes at least: a cloud management and control database and gateway operation status information;

[0030] The second generating unit is used to generate a current inter-cluster invariant according to the current first target comparison data.

[0031] Optionally, the changing unit includes:

[0032] A second receiving unit, configured for the gateway to be changed to receive gateway neighbor information through a data stream;

[0033] A second calculation unit is used to calculate the current single gateway invariant before, during and after the gateway that needs to be changed is changed;

[0034] The third generating unit is configured to generate second alarm information when the current single gateway invariant does not match the target gateway invariant.

[0035] Optionally, before the gateway to be changed is changed, the second computing unit includes:

[0036] A second acquisition unit is used to acquire the current second target comparison data before the gateway to be changed is changed; wherein the data source of the second target comparison data includes at least: a cloud management and control database and gateway operation status information;

[0037] The fourth generating unit is used to generate a current single gateway invariant according to the current second target comparison data.

[0038] A third aspect of the present application provides an electronic device, including:

[0039] one or more processors;

[0040] a storage device having one or more programs stored thereon;

[0041] When the one or more programs are executed by the one or more processors, the one or more processors implement the gateway change method as described in any one of the first aspects.

[0042] A fourth aspect of the present application provides a computer storage medium having a computer program stored thereon, wherein when the computer program is executed by a processor, the gateway change method as described in any one of the first aspects is implemented.

[0043] It can be seen from the above scheme that the present application provides a gateway change method, device, electronic device and computer storage medium, wherein the gateway change method includes: receiving a gateway change strategy; wherein the gateway change strategy includes the cluster to be changed this time and the gateway to be changed in the cluster to be changed, the upgrade strategy corresponding to the gateway to be changed and the target cluster change invariant; the target cluster change invariant is generated according to the planning information of the cloud network; then, for each of the gateways to be changed in the same cluster, the gateways to be changed are changed in turn according to the upgrade strategy corresponding to the gateway to be changed; thereafter, before, during and after the cluster is changed, the current cluster change invariant is calculated respectively; wherein the invariant refers to the judgment that any stable state before, during and after the change is maintained as true; when the current cluster change invariant does not match the target cluster change invariant, a first alarm message is generated. The present application provides a standardized change process, and the correctness is guaranteed. At the same time, the correctness verification between clusters is improved. Only a single operation is required during the change, which shortens the gateway change cycle, reduces the risk of implementing the change operation, and improves the speed of correctness judgment of the change. BRIEF DESCRIPTION OF THE DRAWINGS

[0044] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on the provided drawings without paying any creative work.

[0045] Figure 1 A specific flow chart of a gateway change method provided in an embodiment of the present application;

[0046] Figure 2 A flowchart of a gateway change method provided in another embodiment of the present application;

[0047] Figure 3 A flowchart of a gateway change method provided in another embodiment of the present application;

[0048] Figure 4 A flowchart of a gateway change method provided in another embodiment of the present application;

[0049] Figure 5 A schematic diagram of the structure of a gateway change method provided in another embodiment of the present application;

[0050] Figure 6 A schematic diagram of a gateway changing device provided in another embodiment of the present application;

[0051] Figure 7 A schematic diagram of an electronic device for implementing a gateway change method provided in another embodiment of the present application. DETAILED DESCRIPTION

[0052] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0053] It should be noted that the concepts of "first", "second", etc. mentioned in this application are only used to distinguish different devices, modules or units, and are not used to limit the order or interdependence of the functions performed by these devices, modules or units, and the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "including one..." do not exclude the existence of other identical elements in the process, method, article or device including the elements.

[0054] The present application embodiment provides a method for changing a gateway, such as Figure 1 As shown, the specific steps include:

[0055] S101, receiving gateway change strategy.

[0056] Among them, the gateway change strategy includes the cluster that needs to be changed this time, the gateway that needs to be changed in the cluster that needs to be changed, the upgrade strategy corresponding to the gateway that needs to be changed, and the target cluster change invariant; the target cluster change invariant is generated according to the planning information of the cloud network.

[0057] It should be noted that changes include but are not limited to the upgrade or modification of the supporting software of the gateway, such as the operating system, the upgrade or replacement of the gateway application, the modification of the configuration information, etc., which are not limited here. Invariants refer to judgments that remain true in any stable state before, during, and after the change. The judgments in the invariants can be dynamically adjusted according to the actual application situation. The network gateway is a network infrastructure that provides interconnection between different network protocols or different network areas.

[0058] In the specific implementation process of this application, users can write gateway change policies through browsers, etc., which is not limited here. It also supports online writing of adjustment invariants, and the invariant ID, gateway, and invariant calculation time are unified into an invariant calculation result key.

[0059] S102: For each gateway that needs to be changed in the same cluster, the gateway that needs to be changed is changed in turn according to the upgrade strategy corresponding to the gateway that needs to be changed.

[0060] It should be noted that different clusters can make changes in parallel.

[0061] In the specific implementation process of this application, each gateway that needs to be changed in each cluster will be issued a change script to achieve the change of the gateway that needs to be changed according to the upgrade strategy corresponding to the gateway that needs to be changed, and it is easy to control the unified management of the center.

[0062] Optionally, in another embodiment of the present application, an implementation of step S102 is as follows: Figure 2 As shown, including:

[0063] S201. The gateway to be changed receives gateway neighbor information via a data stream.

[0064] S202: Before, during, and after the gateway that needs to be changed is changed, respectively calculate and obtain the current single gateway invariant.

[0065] Optionally, in another embodiment of the present application, taking the gateway to be changed before the change as an example, an implementation of step S202 is as follows: Figure 3 As shown, including:

[0066] S301. Before changing the gateway that needs to be changed, obtain current second target comparison data.

[0067] The data sources of the second target comparison data include at least: cloud control database and gateway operation status information. The cloud control database is generally stored in a relational database such as Mysql, or information stored in the distributed application coordination service zookeeper; the gateway operation status information includes the status of the local station, cluster neighbors, neighbor session synchronization status, etc., which are not limited here.

[0068] S302: Generate a current single gateway invariant according to the current second target comparison data.

[0069] The pseudo code for calculating the invariant of a single gateway is as follows:

[0070]

[0071]

[0072] S203: When the current single gateway invariant does not match the target gateway invariant, generate second alarm information.

[0073] Among them, the target gateway invariant is generated according to the planning information of the cloud network.

[0074] S103: Before, during, and after the cluster is changed, respectively calculate and obtain the current inter-cluster invariant.

[0075] Among them, the invariant refers to a judgment that remains true in any stable state before, during, and after the change.

[0076] It should be noted that the calculation method of the inter-cluster invariant can refer to the gateway invariant in the above steps, which will not be repeated here.

[0077] Optionally, in another embodiment of the present application, taking the cluster to be changed before the change as an example, an implementation method of step S103 is as follows: Figure 4 As shown, including:

[0078] S401. Before the cluster is changed, obtain current first target comparison data.

[0079] Among them, the data source of the first target comparison data includes at least: a cloud management and control database and gateway operation status information.

[0080] S402: Generate a current inter-cluster invariant according to the current first target comparison data.

[0081] It should be noted that the calculation method of the inter-cluster invariant can refer to the gateway invariant in the above steps, which will not be repeated here.

[0082] S104: When the current inter-cluster invariant does not match the target inter-cluster change invariant, generate first alarm information.

[0083] like Figure 5 As shown, users can write gateway change policies (upgrade policies, inter-cluster change invariants, etc.) through the browser. The gateway control center can control the gateway to be changed to initiate changes based on the gateway cluster change policy file; at the same time, it calculates the invariants between clusters; it is the control center for automated batch changes. The configuration center is used to store network planning and design files, such as gateway location information and IP planning information; it stores gateway configuration information, such as gateway application thread planning information. It is the basis for invariant calculation and verification. The gateway cluster is used for online changes of network devices. It obtains configuration planning information and neighbor gateway information in the same cluster through data streams (such as OSPF neighbor status, real-time session synchronization status of stateful gateways, full session synchronization status before and after stateful gateway service status changes, and success or failure calculation), and calculates invariants before, during, and after the change.

[0084] It can be seen from the above scheme that the present application provides a gateway change method: receiving a gateway change strategy; wherein the gateway change strategy includes the cluster that needs to be changed this time and the gateway that needs to be changed in the cluster that needs to be changed, the upgrade strategy corresponding to the gateway that needs to be changed, and the target cluster change invariant; the target cluster change invariant is generated according to the planning information of the cloud network; then, for each gateway that needs to be changed in the same cluster, the gateway that needs to be changed is changed in turn according to the upgrade strategy corresponding to the gateway that needs to be changed; then, before the cluster is changed, during the change, and after the change, the current cluster invariant is calculated respectively; wherein the invariant refers to the judgment that any stable state before, during, and after the change remains true; when the current cluster invariant does not match the target cluster change invariant, a first alarm message is generated. The present application provides a standardized change process, and the correctness is guaranteed. At the same time, the correctness verification between clusters is improved. Only a single operation is required during the change, which shortens the gateway change cycle, reduces the risk of implementing the change operation, and improves the speed of correctness judgment of the change.

[0085] Another embodiment of the present application provides a gateway modification device, such as Figure 6 As shown, specifically including:

[0086] The first receiving unit 601 is configured to receive a gateway change strategy.

[0087] Among them, the gateway change strategy includes the cluster that needs to be changed this time, the gateway that needs to be changed in the cluster that needs to be changed, the upgrade strategy corresponding to the gateway that needs to be changed, and the target cluster change invariant; the target cluster change invariant is generated according to the planning information of the cloud network.

[0088] The changing unit 602 is used to change each gateway that needs to be changed in the same cluster in turn according to the upgrade strategy corresponding to the gateway that needs to be changed.

[0089] Optionally, different clusters can make changes in parallel.

[0090] Optionally, in another embodiment of the present application, an implementation of the changing unit 602 includes:

[0091] The second receiving unit is used for the gateway to be changed to receive gateway neighbor information through a data stream.

[0092] The second calculation unit is used to calculate the current single gateway invariant before, during and after the gateway that needs to be changed is changed.

[0093] The third generating unit is configured to generate second alarm information when the current single gateway invariant does not match the target gateway invariant.

[0094] For the specific working process of the units disclosed in the above embodiments of the present application, please refer to the corresponding method embodiments, such as Figure 2 As shown, no further description is given here.

[0095] Optionally, in another embodiment of the present application, before the gateway to be changed is changed, an implementation of the second computing unit includes:

[0096] The second acquisition unit is used to acquire the current second target comparison data before the gateway that needs to be changed is changed.

[0097] Among them, the data source of the second target comparison data at least includes: a cloud management and control database and gateway operation status information.

[0098] The fourth generating unit is used to generate a current single gateway invariant according to the current second target comparison data.

[0099] For the specific working process of the units disclosed in the above embodiments of the present application, please refer to the corresponding method embodiments, such as Figure 3 As shown, no further description is given here.

[0100] The first calculation unit 603 is used to calculate and obtain the current inter-cluster invariant before, during, and after the cluster is changed.

[0101] Among them, the invariant refers to a judgment that remains true in any stable state before, during, and after the change.

[0102] Optionally, in another embodiment of the present application, before the cluster is changed, an implementation of the first computing unit 603 includes:

[0103] The first acquisition unit is used to acquire the current first target comparison data before the cluster is changed.

[0104] Among them, the data source of the first target comparison data includes at least: a cloud management and control database and gateway operation status information.

[0105] The second generating unit is used to generate a current inter-cluster invariant according to the current first target comparison data.

[0106] For the specific working process of the units disclosed in the above embodiments of the present application, please refer to the corresponding method embodiments, such as Figure 4 As shown, no further description is given here.

[0107] The first generating unit 604 is configured to generate first warning information when the current inter-cluster invariant does not match the target inter-cluster change invariant.

[0108] For the specific working process of the units disclosed in the above embodiments of the present application, please refer to the corresponding method embodiments, such as Figure 1 As shown, no further description is given here.

[0109] As can be seen from the above scheme, the present application provides a gateway change device: the first receiving unit 601 receives the gateway change strategy; wherein the gateway change strategy includes the cluster that needs to be changed this time and the gateway that needs to be changed in the cluster that needs to be changed, the upgrade strategy corresponding to the gateway that needs to be changed, and the target cluster change invariant; the target cluster change invariant is generated according to the planning information of the cloud network; then, the change unit 602 changes the gateway that needs to be changed in the same cluster according to the upgrade strategy corresponding to the gateway that needs to be changed; then, the first calculation unit 603 calculates the current cluster change invariant before, during, and after the cluster is changed; wherein the invariant refers to the judgment that any stable state before, during, and after the change is maintained as true; the first generation unit 604 generates a first alarm message when the current cluster change invariant does not match the target cluster change invariant. The present application provides a standardized change process, and the correctness is guaranteed. At the same time, the correctness verification between clusters is improved. Only a single operation is required during the change, which shortens the gateway change cycle, reduces the risk of implementing the change operation, and improves the speed of correctness judgment of the change.

[0110] Another embodiment of the present application provides an electronic device, such as Figure 7 As shown, including:

[0111] One or more processors 701.

[0112] The storage device 702 stores one or more programs.

[0113] When the one or more programs are executed by the one or more processors 701, the one or more processors 701 implement the gateway changing method as described in any one of the above embodiments.

[0114] Another embodiment of the present application provides a computer storage medium on which a computer program is stored, wherein when the computer program is executed by a processor, the gateway changing method as described in any one of the above embodiments is implemented.

[0115] In the above embodiments disclosed in the present application, it should be understood that the disclosed apparatus and method can also be implemented in other ways. The apparatus and method embodiments described above are merely schematic. For example, the flowcharts and block diagrams in the accompanying drawings show the possible architecture, functions and operations of the apparatus, method and computer program product according to multiple embodiments of the present disclosure. In this regard, each box in the flowchart or block diagram can represent a module, a program segment or a part of a code, and the module, program segment or a part of the code contains one or more executable instructions for implementing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in a different order from the order marked in the accompanying drawings. For example, two consecutive boxes can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram and / or flowchart, and the combination of boxes in the block diagram and / or flowchart can be implemented with a dedicated hardware-based system that performs a specified function or action, or can be implemented with a combination of dedicated hardware and computer instructions.

[0116] In addition, each functional module in each embodiment of the present disclosure can be integrated together to form an independent part, or each module can exist separately, or two or more modules can be integrated to form an independent part. If the function is implemented in the form of a software functional module and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present disclosure is essentially or the part that contributes to the prior art or the part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including several instructions to enable a computer device (which can be a personal computer, a live broadcast device, or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present disclosure. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), disk or optical disk and other media that can store program code.

[0117] The present application can be implemented or used by professionals and technicians. Various modifications to these embodiments will be apparent to professionals and technicians in the field, and the general principles defined herein can be implemented in other embodiments without departing from the spirit or scope of the present application. Therefore, the present application will not be limited to the embodiments shown herein, but will conform to the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A gateway change method, characterized in that: include: Receive a gateway change strategy; wherein the gateway change strategy includes the cluster to be changed this time, the gateway to be changed in the cluster to be changed, the upgrade strategy corresponding to the gateway to be changed, and the target cluster change invariant; the target cluster change invariant is an inter-cluster invariant generated according to the planning information of the cloud network; For each gateway that needs to be changed in the same cluster, the gateway that needs to be changed is changed in turn according to the upgrade strategy corresponding to the gateway that needs to be changed; Before, during and after the cluster is changed, the current inter-cluster invariant is calculated respectively; wherein the inter-cluster invariant is the basis for determining the stable state between clusters, and if the state between clusters is in a stable state at any time before, during and after the cluster is changed, the determination result of the inter-cluster invariant remains true; When the current inter-cluster invariant does not match the target inter-cluster change invariant, a first alarm message is generated.

2. The method for changing according to claim 1, characterized in that: Different clusters can make changes in parallel.

3. The method for changing according to claim 1, characterized in that: If before the cluster is changed, the current inter-cluster invariant is calculated before, during, and after the cluster is changed, including: Before the cluster is changed, current first target comparison data is obtained; wherein the data source of the first target comparison data includes at least: a cloud management and control database and gateway operation status information; A current inter-cluster invariant is generated according to the current first target comparison data.

4. The method for changing according to claim 1, characterized in that: For each gateway that needs to be changed in the same cluster, the gateway that needs to be changed is changed in turn according to the upgrade strategy corresponding to the gateway that needs to be changed, including: The gateway that needs to be changed receives gateway neighbor information through a data stream; Before, during and after the gateway that needs to be changed is changed, the current single gateway invariant is calculated respectively; the single gateway invariant is the basis for determining the stable state of the single gateway, and if the state of the gateway is in a stable state at any time before, during and after the gateway is changed, the determination result of the single gateway invariant remains true; When the current single gateway invariant does not match the target gateway invariant, second alarm information is generated.

5. The method for changing according to claim 4, characterized in that: If the gateway that needs to be changed is changed before, during, and after the gateway that needs to be changed is changed, the current single gateway invariant is calculated respectively, including: Before the gateway to be changed is changed, the current second target comparison data is obtained; wherein the data source of the second target comparison data includes at least: a cloud management and control database and gateway operation status information; A current single gateway invariant is generated according to the current second target comparison data.

6. A gateway changing device, characterized in that: include: A first receiving unit is used to receive a gateway change strategy; wherein the gateway change strategy includes the cluster that needs to be changed this time and the gateway that needs to be changed in the cluster that needs to be changed, the upgrade strategy corresponding to the gateway that needs to be changed, and the target cluster change invariant; the target cluster change invariant is an inter-cluster invariant generated according to the planning information of the cloud network; A changing unit, configured to change each gateway that needs to be changed in the same cluster in turn according to an upgrade strategy corresponding to the gateway that needs to be changed; A first calculation unit is used to calculate the current inter-cluster invariant before, during, and after the cluster is changed, respectively; wherein the inter-cluster invariant is a basis for determining the stable state between clusters, and if the state between clusters is in a stable state at any time before, during, and after the cluster is changed, the determination result of the inter-cluster invariant remains true; The first generating unit is configured to generate first alarm information when the current inter-cluster invariant does not match the target inter-cluster change invariant.

7. The changing device according to claim 6, characterized in that: Different clusters can make changes in parallel.

8. The changing device according to claim 6, characterized in that: Before the cluster is changed, the first computing unit includes: A first acquisition unit is used to acquire current first target comparison data before the cluster is changed; wherein the data source of the first target comparison data includes at least: a cloud management and control database and gateway operation status information; The second generating unit is used to generate a current inter-cluster invariant according to the current first target comparison data.

9. An electronic device, characterized in that: include: one or more processors; a storage device having one or more programs stored thereon; When the one or more programs are executed by the one or more processors, the one or more processors implement the gateway changing method as claimed in any one of claims 1 to 5.

10. A computer storage medium, characterized in that: A computer program is stored thereon, wherein when the computer program is executed by a processor, the gateway changing method as claimed in any one of claims 1 to 5 is implemented.

Images