A network upgrading method, device, equipment, medium and program product

Abstract

The present disclosure relates to the technical field of computer networks, and particularly relates to a network upgrading method, device, equipment, medium and program product; the method comprises the following steps: in response to a first operation of a user, introducing a new version of a NAT gateway into a target network; establishing a first route between the new version of the NAT gateway and an edge gateway, and establishing a second route between a to-be-eliminated NAT gateway and the edge gateway, the priority of the first route being lower than the priority of the second route; publishing a first public network segment of the to-be-eliminated NAT gateway to the edge gateway, changing a traffic inlet and outlet corresponding to the first public network segment from the to-be-eliminated NAT gateway to the edge gateway, and sequentially deleting the second route and the to-be-eliminated NAT gateway from the target network; based on this, seamless replacement between the to-be-eliminated NAT gateway and the new version of the NAT gateway is realized, service interruption problems caused by service suspension are avoided, and the effects of network smooth upgrading and improved user experience are achieved.

Description

Technical Field

[0001] This disclosure relates to the field of computer network technology, and in particular to a network upgrade method, apparatus, device, medium, and program product. Background Technology

[0002] Network upgrades are an indispensable part of network technology. They must not only meet ever-changing business needs but also optimize network resources and save costs.

[0003] In related technologies, network upgrades are primarily achieved by halting service. However, this upgrade method can impact user services, resulting in a poor user experience. Summary of the Invention

[0004] To address the aforementioned technical problems, this disclosure provides a network upgrade method, apparatus, device, medium, and program product.

[0005] Firstly, this disclosure provides a network upgrade method, including:

[0006] In response to the user's first action, a new version of the NAT gateway is introduced into the target network, which includes an edge gateway and a NAT gateway to be phased out. The edge gateway has the function of pooling elastic IPs and NAT IPs. A first route is established between the new NAT gateway and the edge gateway, and a second route is established between the NAT gateway to be phased out and the edge gateway. The first route has a lower priority than the second route. The first public network segment of the NAT gateway to be phased out is advertised to the edge gateway, and the traffic entry and exit points corresponding to the first public network segment are changed from the NAT gateway to be phased out to the edge gateway. The second route and the NAT gateway to be phased out are then removed from the target network.

[0007] In some alternative implementations, the target network is deployed as follows:

[0008] In response to the user's second action, an edge gateway is deployed in the initial network, which includes an elastic public IP gateway; a route is established between the edge gateway and the elastic public IP gateway; the second public network segment of the elastic public IP gateway is published to the edge gateway, and the traffic entry and exit points corresponding to the second public network segment are changed from the elastic public IP gateway to the edge gateway, thus obtaining the target network.

[0009] In some alternative implementations, after deploying the edge gateway in the initial network in response to a second user action, the method further includes:

[0010] Perform gray-scale testing on the edge gateway.

[0011] In some optional implementations, gray-scale testing of the edge gateway includes:

[0012] Publish a new public network segment on the edge gateway and set the traffic entry and exit points of the new public network segment as the edge gateway. The new public network segment is used as an elastic public IP. In response to business requests, conduct gray-scale testing on the edge gateway.

[0013] In some optional implementations, the second public network segment of the elastic public IP gateway is advertised to the edge gateway, and the traffic ingress / egress point corresponding to the second public network segment is changed from the elastic public IP gateway to the edge gateway, including:

[0014] A portion of the second public network segment is published to the edge gateway, and the traffic ingress / egress point corresponding to the portion of the segment is changed from the Elastic Public IP Gateway to the edge gateway. In response to a service request, a gray-scale test is conducted on the edge gateway based on the portion of the segment, and the test results are obtained. When the test results are qualified, the remaining segments of the second public network segment, excluding the portion of the segment, are published to the edge gateway, and the traffic ingress / egress point corresponding to the remaining segments is changed from the Elastic Public IP Gateway to the edge gateway.

[0015] In some alternative implementations, the NAT gateway to be phased out is a gateway that has undergone a preliminary upgrade of the old NAT gateway, and the first public network segment includes non-shared pool network segments and shared pool network segments.

[0016] Secondly, this disclosure provides a network upgrade device, comprising:

[0017] The module introduces a new NAT gateway in response to the user's first action. The target network includes an edge gateway and a NAT gateway to be phased out. The edge gateway has the function of pooling elastic IPs and NAT IPs. The module establishes a first route between the new NAT gateway and the edge gateway, and a second route between the NAT gateway to be phased out and the edge gateway. The first route has a lower priority than the second route. The module upgrades the first public network segment of the NAT gateway to be phased out to the edge gateway, changes the traffic entry and exit points corresponding to the first public network segment from the NAT gateway to be phased out to the edge gateway, and then removes the second route and the NAT gateway to be phased out from the target network.

[0018] Thirdly, this disclosure provides a computer device, including:

[0019] The memory and processor are interconnected and communicate with each other. The memory stores computer instructions, and the processor executes the computer instructions to perform the network upgrade method described in the first aspect and any of its embodiments.

[0020] Fourthly, this disclosure provides a computer-readable storage medium storing computer instructions for causing a computer to perform the network upgrade method described in the first aspect and any embodiment thereof.

[0021] Fifthly, this disclosure provides a computer program product, including a computer program that, when executed by a processor, implements the steps of the network upgrade method described in the first aspect and any embodiment thereof.

[0022] The technical solution provided in this disclosure has the following advantages compared with the prior art:

[0023] The network upgrade method provided in this embodiment, in response to the user's first operation, introduces a new version of the NAT gateway into the target network. The target network includes an edge gateway and a NAT gateway to be phased out. The edge gateway has the function of pooling elastic IPs and NAT IPs. A first route is established between the new version of the NAT gateway and the edge gateway, and a second route is established between the NAT gateway to be phased out and the edge gateway. The first route has a lower priority than the second route. The first public network segment of the NAT gateway to be phased out is published to the edge gateway, and the traffic entry and exit points corresponding to the first public network segment are changed from the NAT gateway to be phased out to the edge gateway. The second route and the NAT gateway to be phased out are then deleted from the target network. After establishing the low-priority first route and the high-priority second route, the above scheme automatically forwards traffic to the new version of the NAT gateway through the first route by deleting the high-priority second route. This achieves a seamless replacement between the NAT gateway to be phased out and the new version of the NAT gateway, avoiding service interruption caused by service downtime, and achieving the effect of smooth network upgrade and improved user experience. Attached Figure Description

[0024] The accompanying drawings, which are incorporated in and form a part of this specification, illustrate embodiments consistent with this disclosure and, together with the description, serve to explain the principles of this disclosure.

[0025] To more clearly illustrate the technical solutions in the embodiments of this disclosure or the prior art, the accompanying drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, for those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0026] Figure 1 A flowchart illustrating the network upgrade method provided in this embodiment of the disclosure;

[0027] Figure 2 An initial network diagram provided for embodiments of this disclosure;

[0028] Figure 3This is a schematic diagram of the target network provided in an embodiment of the present disclosure;

[0029] Figure 4 A schematic diagram illustrating the deployment process of the target network provided in this embodiment of the disclosure;

[0030] Figure 5 A schematic diagram of the grayscale testing process provided in the embodiments of this disclosure;

[0031] Figure 6 A schematic diagram of the upgraded target network provided in an embodiment of this disclosure;

[0032] Figure 7 A structural connection diagram of the network upgrade device provided in the embodiments of this disclosure;

[0033] Figure 8 This is a structural connection diagram of a computer device provided in an embodiment of the present disclosure. Detailed Implementation

[0034] To better understand the above-mentioned objectives, features, and advantages of this disclosure, the solutions disclosed herein will be further described below. It should be noted that, unless otherwise specified, the embodiments and features described herein can be combined with each other.

[0035] Numerous specific details are set forth in the following description to provide a thorough understanding of this disclosure, but this disclosure may also be implemented in other ways different from those described herein; obviously, the embodiments in the specification are only a part of the embodiments of this disclosure, and not all of them. All other embodiments obtained by those skilled in the art based on the embodiments of this disclosure without inventive effort are within the scope of protection of this disclosure.

[0036] It should be noted that, in this document, relational terms such as "first" and "second" are used merely to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes the element.

[0037] Before providing a detailed description of the embodiments disclosed herein, a brief introduction to the relevant terms and background of this case is given below.

[0038] (I) Related Terminology

[0039] Underlay network: also known as physical network, is the current basic forwarding architecture of data center network. Interconnected devices ensure the connectivity between IPs through the routing protocol of the traditional OSI (Open System Interconnect) seven-layer model. Due to the fixed nature of the hardware devices, the data forwarding path is not easy to change and is not flexible enough. During business changes, the underlying network connection needs to be manually modified.

[0040] Overlay network: also known as virtual network, is a logical network built on top of a physical network. It does not require large-scale modifications to the underlying network and builds and expands the network by managing and controlling network devices.

[0041] (II) Background of this case

[0042] Network upgrades are an indispensable part of network technology. They primarily involve upgrading or modifying network equipment to improve network performance and reduce costs.

[0043] In related technologies, network upgrades are primarily completed by stopping services (referred to as service downtime). Generally, downtime lasts for several hours. However, downtime disrupts customer services and creates a poor user experience. In addition, operations personnel need to complete the cabling and routing deployment of the underlay data plane, as well as the upgrade operations of the overlay control plane, within the downtime window. This process is time-sensitive, technically challenging, has low fault tolerance, and is not conducive to rollback; any problem in any stage can have serious consequences.

[0044] Therefore, the network upgrade method provided in this disclosure, after establishing a low-priority first route between the new NAT gateway and the edge gateway, and a high-priority second route between the NAT gateway to be phased out and the edge gateway, automatically forwards traffic to the new NAT gateway through the first route by deleting the high-priority second route. This achieves seamless replacement between the NAT gateway to be phased out and the new NAT gateway, avoids service interruption caused by service outages, and achieves the effect of smooth network upgrade and improved user experience.

[0045] According to an embodiment of this disclosure, a network upgrade method embodiment is provided. It should be noted that the steps shown in the flowchart in the accompanying drawings can be executed in a computer system such as a set of computer-executable instructions. Furthermore, although a logical order is shown in the flowchart, in some cases, the steps shown or described may be executed in a different order than that shown here.

[0046] This embodiment provides a network upgrade method applied to a network upgrade scenario, specifically a network upgrade scenario in a shared-pool environment. This method is applicable to network upgrade devices. Figure 1 This is a flowchart of a network upgrade method according to an embodiment of the present disclosure, such as... Figure 1 As shown, the process includes the following steps:

[0047] S101, in response to the user's first action, introduces a new version of the NAT gateway in the target network, which includes an edge gateway and a NAT gateway to be phased out. The edge gateway has the function of pooling elastic IP and NAT IP.

[0048] The first operation involves user actions based on the new NAT gateway, including cabling in the underlay network and upgrade operations in the overlay network. The target network is the network to be upgraded. The target network includes at least an edge gateway and a NAT gateway to be phased out. The edge gateway and the NAT gateway to be phased out each act as independent traffic entry and exit points, handling traffic from their respective public network segments. The edge gateway has the capability to pool elastic IPs and NAT IPs. In this embodiment, implementing a pooled elastic IP and NAT IP in the edge gateway of the target network can reduce development and maintenance costs, effectively reduce tenant usage costs, improve IP address utilization, and achieve cost reduction and efficiency improvement.

[0049] Specifically, in response to user cabling operations, the NAT gateway is deployed to the target network at the physical layer; in response to user upgrade operations, the NAT gateway is upgraded at the virtual layer to obtain a new version of the NAT gateway, thus realizing the introduction of the new version of the NAT gateway into the pre-deployed target network. The aforementioned cabling and upgrade operations are the first operations performed by the user with the new version of the NAT gateway. Compared to the NAT gateway to be phased out, in addition to performance upgrades, the new version of the NAT gateway also has its corresponding NAT IP network segment divided into non-shared-pool network segments and shared-pool network segments. IPs in the shared-pool network segment can be used as NATIPs or as Elastic IPs bound to cloud resources.

[0050] In some alternative embodiments, the target network is a Figure 2 The network shown is an upgraded version of the Elastic Public IP Gateway Xgw in the initial network. The upgraded Elastic Public IP Gateway Xgw has the function of sharing Elastic IP and NAT IP pools. The upgraded Elastic Public IP Gateway is also known as the edge gateway. Figure 2 The initial network shown also includes the NAT gateway Natα, which is to be phased out, while for Figure 2 Other gateways such as pgw and vgw do not need to be considered.

[0051] In some alternative embodiments, the target network is as follows: Figure 3The network shown, Figure 3 The target network shown is, in Figure 2 This illustrates the introduction of an ESGW gateway into the initial network, and the establishment of a network with routing between the ESGW gateway and the Elastic Public IP Gateway (XGW). The ESGW gateway is also known as the edge gateway.

[0052] S102, establish the first route between the new NAT gateway and the edge gateway, and establish the second route between the NAT gateway to be phased out and the edge gateway. The priority of the first route is lower than that of the second route.

[0053] Specifically, after introducing the new NAT gateway into the target network, a first route is established between the new NAT gateway and the edge gateway, and a second route is established between the NAT gateway to be phased out and the edge gateway. The first route is configured as a low-priority route, and the second route is configured as a high-priority route. This embodiment establishes the first and second routes before phasing out the NAT gateway to be phased out, providing an important prerequisite for a smooth network upgrade.

[0054] It is important to emphasize that, during the upgrade process in this embodiment, although the first and second routes are established, the entry and exit points for NAT IP traffic are still the NAT gateway to be phased out. Therefore, the new NAT gateway has not yet started processing traffic during this process, and the NAT IP traffic is still processed by the NAT gateway to be phased out.

[0055] In some alternative embodiments, the NAT gateway to be phased out is an older version of the NAT gateway, and the public network segment corresponding to the NAT gateway to be phased out is a non-shared pool network segment.

[0056] In some alternative embodiments, due to the user's urgent need for the basic functions of the new NAT gateway, the old NAT gateway in the target network can be initially upgraded before S101. That is, the NAT gateway to be phased out is the gateway after the initial upgrade of the old NAT gateway. Although the initially upgraded NAT gateway to be phased out has the basic functions of the new NAT gateway, its upgrade is not thorough and its performance is unstable. Therefore, the NAT gateway to be phased out can replace the new NAT gateway for traffic processing in a short period of time, but it still needs to be replaced by the new NAT gateway in the future. It should also be noted that in this embodiment, the public network segment corresponding to the NAT gateway to be phased out includes both non-shared pool network segments and shared pool network segments.

[0057] S103, publish the first public network segment of the NAT gateway to be phased out to the edge gateway, change the traffic entry and exit points corresponding to the first public network segment from the NAT gateway to be phased out to the edge gateway, and delete the second route and the NAT gateway to be phased out from the target network in sequence.

[0058] The first public network segment is the non-shared-pool segment within the public network segment corresponding to the NAT gateway to be phased out. When the NAT gateway to be phased out is an older version NAT gateway, the first public network segment is the public network segment corresponding to the older version NAT gateway, i.e., the non-shared-pool segment. When the NAT gateway to be phased out is a gateway that has undergone a preliminary upgrade of an older version NAT gateway, the first public network segment is the non-shared-pool segment within the public network segment corresponding to the NAT gateway to be phased out.

[0059] Specifically, the first public network segment of the NAT gateway to be phased out is advertised to the edge gateway, and the traffic ingress / egress point corresponding to the first public network segment is changed from the NAT gateway to be phased out to the edge gateway. At this point, only one traffic ingress / egress point exists in the target network: the edge gateway. Since the first route between the new NAT gateway and the edge gateway, and the second route between the NAT gateway to be phased out and the edge gateway have been established, and the second route has a higher priority than the first route, when NAT IP traffic enters the edge gateway, the edge gateway will prioritize forwarding the traffic to the NAT gateway to be phased out. Then, the second route is removed from the target network, and the edge gateway will automatically forward the corresponding traffic to the new NAT gateway, which will then forward the traffic to the internal network devices. Once it is confirmed that the edge gateway can securely and stably forward traffic to the new NAT gateway, the NAT gateway to be phased out is then removed from the target network.

[0060] The network upgrade method provided in this embodiment, in response to the user's first operation, introduces a new version of the NAT gateway into the target network. The target network includes an edge gateway and a NAT gateway to be phased out. The edge gateway has the function of pooling elastic IPs and NAT IPs. A first route is established between the new version of the NAT gateway and the edge gateway, and a second route is established between the NAT gateway to be phased out and the edge gateway. The first route has a lower priority than the second route. The first public network segment of the NAT gateway to be phased out is published to the edge gateway, and the traffic entry and exit points corresponding to the first public network segment are changed from the NAT gateway to be phased out to the edge gateway. The second route and the NAT gateway to be phased out are then deleted from the target network. After establishing the low-priority first route and the high-priority second route, the above scheme automatically forwards traffic to the new version of the NAT gateway through the first route by deleting the high-priority second route. This achieves a seamless replacement between the NAT gateway to be phased out and the new version of the NAT gateway, avoiding service interruption caused by service downtime, and achieving the effect of smooth network upgrade and improved user experience.

[0061] This embodiment also provides a network upgrade method, which adds... Figure 3 The deployment process of the target network shown is as follows: Figure 4 As shown, it includes the following steps:

[0062] S401, in response to a second user action, deploys an edge gateway in the initial network, which includes an elastic public IP gateway.

[0063] The initial network is as follows: Figure 2 As shown. The second operation is the user's operation based on the edge gateway ESGW. The second operation includes operations based on... Figure 2 This illustrates the cabling operations for the underlay network. An Elastic Public IP Gateway is a gateway that provides Elastic Public IP services, i.e. Figure 2 The gateway Xgw in the system.

[0064] Specifically, in response to user cabling operations in the initial network, the edge gateway ESGW is deployed into the initial network at the physical layer.

[0065] S402 establishes a route between the edge gateway and the elastic public IP gateway.

[0066] Specifically, after introducing the ESGW into the initial network, a route is established between the ESGW and the Elastic Public IP Gateway (Xgw). It should be noted that at this stage, only the route is established; therefore, the ESGW does not yet perform traffic processing.

[0067] In some optional embodiments, to ensure the security, stability, and other performance of the edge gateway (ESGW), a gray-scale test is required after step S401. Subsequent operations are only performed if the gray-scale test results are satisfactory. In this embodiment, performing a gray-scale test on the edge gateway after step S401 reduces the risk of errors during the upgrade process and improves upgrade efficiency.

[0068] In some alternative embodiments, by means of, Figure 5 The steps shown involve performing gray-scale testing on the edge gateway, specifically including:

[0069] S501 publishes a new public network segment on the edge gateway and sets the traffic entry and exit points of the new public network segment to the edge gateway.

[0070] The new public network segment is determined by the cloud service provider. This new public network segment will be used as an elastic public IP address.

[0071] Specifically, the new public network segment determined by the cloud service provider is published on the edge gateway, and the traffic entry and exit points corresponding to the new public network segment are set as the edge gateway, so that the traffic of the elastic IP belonging to the new public network segment can be processed by the edge gateway in the future.

[0072] S502, in response to a service request, performs a gray-scale test on the edge gateway.

[0073] Among them, business requests can be elastic IP application requests or traffic processing requests, such as traffic forwarding.

[0074] Specifically, when an elastic IP request is received, the edge gateway randomly assigns an IP address to the user from multiple IP addresses corresponding to the new public network segment. Here, the user refers to the cloud resource tenant. When a traffic processing request is received, the edge gateway forwards the traffic to the corresponding device. The process of the edge gateway undertaking services is the process of canary deployment testing. After the edge gateway receives a preset number of service requests, or undertakes service requests within a preset time period, the test result of the canary deployment test is determined based on the response to the requests. For example, the test result can be determined based on whether the response time reaches a preset time threshold. The specific method for determining whether the canary deployment test is successful is not limited here.

[0075] S403 publishes the second public network segment of the Elastic Public IP Gateway to the edge gateway, and changes the traffic entry and exit points corresponding to the second public network segment from the Elastic Public IP Gateway to the edge gateway to obtain the target network.

[0076] The second public network segment is the public network segment corresponding to the Elastic Public IP Gateway.

[0077] In some optional embodiments, the gray-scale test of the edge gateway can be completed in process S403, and the handover to the second public network segment can be completed after the gray-scale test is passed. In this scenario, S403 includes the following steps:

[0078] S4031 publishes a portion of the second public network segment to the edge gateway and changes the traffic entry and exit points corresponding to the portion of the network segment from the elastic public IP gateway to the edge gateway.

[0079] Among them, some network segments in the second public network segment can be understood as the network segments to which currently unused elastic IP addresses belong in the second public network segment, and some network segments can be one or more.

[0080] Specifically, when it is determined that there are unused elastic IP addresses in the second public network segment, the network segment to which at least one unused elastic IP address belongs (i.e., a partial network segment) is published to the edge gateway, and the traffic entry point corresponding to the partial network segment is changed from the elastic public IP gateway to the edge gateway.

[0081] S4032, in response to a service request, combines a portion of the network segment to conduct a gray-scale test on the edge gateway and obtain the test results.

[0082] For a description of the business request, please refer to S502, which will not be repeated here.

[0083] Specifically, when an elastic IP request is received, the edge gateway selects an IP address from the network segments corresponding to it and binds it to the user. When a processing request is received for traffic corresponding to an IP address belonging to a network segment, the edge gateway forwards the traffic to the corresponding device. The process of the edge gateway undertaking services is the process of canary deployment testing.

[0084] S4033: When the test result is qualified, the remaining network segments in the second public network segment, except for some segments, will be published to the edge gateway, and the traffic entry and exit points corresponding to the remaining network segments will be changed from the elastic public IP gateway to the edge gateway.

[0085] Specifically, when the gray-scale test result is qualified, it indicates that the edge gateway performs well and is stable during traffic processing. At this time, all remaining network segments in the second public network segment, excluding the aforementioned segments, can be advertised to the edge gateway. Simultaneously, the traffic ingress / egress point for these remaining segments should be changed from the elastic public IP gateway to the edge gateway. It is important to note that... Figure 2 The initial network shown has two independent traffic entry and exit points: one corresponding to the Elastic Public IP Gateway (Xgw), and the other to the NAT Gateway (Natα) to be phased out. After S4033, the deployment is completed as follows... Figure 3 The target network shown still has two independent traffic entry and exit points: the traffic entry and exit point corresponding to the edge gateway ESGW and the traffic entry and exit point corresponding to the NAT gateway Natα to be phased out.

[0086] S404, in response to the user's first action, introduces a new version of the NAT gateway into the target network. The target network includes an edge gateway and a NAT gateway to be phased out. The edge gateway has the ability to pool Elastic IPs and NAT IPs. For details, please refer to [link to details]. Figure 1 S101 of the illustrated embodiment will not be described again here.

[0087] S405 establishes a first route between the new NAT gateway and the edge gateway, and a second route between the NAT gateway to be phased out and the edge gateway. The first route has a lower priority than the second route. For details, please refer to [link to documentation]. Figure 1 S102 of the illustrated embodiment will not be described again here.

[0088] S406: Publish the first public network segment of the NAT gateway to be phased out to the edge gateway, change the traffic ingress / egress point corresponding to the first public network segment from the NAT gateway to be phased out to the edge gateway, and then remove the second route and the NAT gateway to be phased out from the target network in sequence. For details, please refer to [link to details]. Figure 1 S103 of the illustrated embodiment will not be described again here.

[0089] The network upgrade method provided in this embodiment, through processing steps S401 to S406, will... Figure 2 The initial network deployment shown is Figure 3 The target network shown will... Figure 3 The target network shown is upgraded to Figure 6 The upgraded target network is shown. It's clear that the upgraded target network only contains traffic ingress and egress points corresponding to the Edge Gateway (ESGW). Traffic entering the ESGW is either forwarded to the new NAT gateway (Natβ) or the Elastic Public IP Gateway (Xgw). During the network upgrade process, a multi-window, staggered, progressive upgrade approach was adopted, combining underlay (e.g., introducing the Edge Gateway and the new NAT gateway through cabling) and overlay (e.g., establishing routes and changing traffic ingress and egress points). This approach solved problems such as short downtime, high operational difficulty, low fault tolerance, and difficulty in rollback during upgrades, thus improving upgrade efficiency.

[0090] This embodiment also provides a network upgrade device for implementing the above embodiments and preferred embodiments; details already described will not be repeated. As used below, the term "module" can refer to a combination of software and / or hardware that performs a predetermined function. Although the device described in the following embodiments is preferably implemented in software, hardware implementation, or a combination of software and hardware, is also possible and contemplated.

[0091] This embodiment provides a network upgrade device, such as... Figure 7 As shown, it includes:

[0092] Module 701 is introduced to introduce a new version of the NAT gateway in response to the user's first operation. The target network includes an edge gateway and a NAT gateway to be phased out. The edge gateway has the function of pooling elastic IP and NAT IP.

[0093] Module 702 is used to establish a first route between the new NAT gateway and the edge gateway, and to establish a second route between the NAT gateway to be phased out and the edge gateway. The first route has a lower priority than the second route.

[0094] Upgrade module 703 is used to publish the first public network segment of the NAT gateway to be phased out to the edge gateway, change the traffic entry and exit points corresponding to the first public network segment from the NAT gateway to be phased out to the edge gateway, and delete the second route and the NAT gateway to be phased out from the target network in sequence.

[0095] In some optional implementations, the network upgrade apparatus further includes a deployment module for deploying the target network in the following manner:

[0096] The deployment submodule is used to respond to the user's second operation by deploying the edge gateway in the initial network, which includes the Elastic Public IP Gateway; the establishment submodule is used to establish the route between the edge gateway and the Elastic Public IP Gateway; the modification submodule is used to publish the second public network segment of the Elastic Public IP Gateway to the edge gateway, and change the traffic ingress and egress corresponding to the second public network segment from the Elastic Public IP Gateway to the edge gateway to obtain the target network.

[0097] In some alternative implementations, the deployment module further includes:

[0098] The testing submodule is used to perform gray-scale testing of the edge gateway after it has been deployed in the initial network in response to a second user action.

[0099] In some alternative implementations, the test submodule includes:

[0100] The configuration unit is used to publish a new public network segment on the edge gateway and set the traffic entry and exit points of the new public network segment to the edge gateway. The new public network segment is used as an elastic public IP. The first testing unit is used to perform gray-scale testing on the edge gateway in response to business requests.

[0101] In some alternative implementations, the submodules are modified, including:

[0102] The first modification unit is used to publish a portion of the network segments in the second public network segment to the edge gateway, and change the traffic ingress and egress points corresponding to the portion of the network segments from the elastic public IP gateway to the edge gateway; the second testing unit is used to respond to service requests, and in conjunction with the portion of the network segments, to conduct gray-scale testing on the edge gateway and obtain test results; the second modification unit, when the test results are qualified, publishes the remaining network segments in the second public network segment, excluding the portion of the network segments, to the edge gateway, and changes the traffic ingress and egress points corresponding to the remaining segments from the elastic public IP gateway to the edge gateway.

[0103] In some alternative implementations, the NAT gateway to be phased out is a gateway that has undergone a preliminary upgrade of the old NAT gateway, and the first public network segment includes non-shared pool network segments and shared pool network segments.

[0104] Further functional descriptions of the above modules and units are the same as those in the corresponding embodiments described above, and will not be repeated here.

[0105] In this embodiment, the network upgrade device is presented in the form of a functional unit. Here, a unit refers to an ASIC (Application Specific Integrated Circuit) circuit, a processor and memory that execute one or more software or fixed programs, and / or other devices that can provide the above functions.

[0106] This disclosure also provides a computer device having the above-described features. Figure 7 The network upgrade device shown.

[0107] Please see Figure 8 , Figure 8 This is a schematic diagram of the structure of a computer device provided in an optional embodiment of this disclosure, such as... Figure 8 As shown, the computer device includes one or more processors 10, memory 20, and interfaces for connecting the components, including high-speed interfaces and low-speed interfaces. The components communicate with each other via different buses and can be mounted on a common motherboard or otherwise installed as needed. The processors can process instructions executed within the computer device, including instructions stored in or on memory to display graphical information of a GUI on external input / output devices (such as display devices coupled to the interfaces). In some alternative implementations, multiple processors and / or multiple buses can be used with multiple memories and multiple memory modules, if desired. Similarly, multiple computer devices can be connected, each providing some of the necessary operations (e.g., as a server array, a group of blade servers, or a multiprocessor system). Figure 8 Take a processor 10 as an example.

[0108] Processor 10 may be a central processing unit, a network processor, or a combination thereof. Processor 10 may further include a hardware chip. The hardware chip may be an application-specific integrated circuit (ASIC), a programmable logic device (PLD), or a combination thereof. The programmable logic device may be a complex programmable logic device (CAMP), a field-programmable gate array (FPGA), a general-purpose array logic (GDA), or any combination thereof.

[0109] The memory 20 stores instructions executable by at least one processor 10 to cause at least one processor 10 to perform the method shown in the above embodiments.

[0110] The memory 20 may include a program storage area and a data storage area. The program storage area may store the operating system and applications required for at least one function; the data storage area may store data created based on the use of the computer device. Furthermore, the memory 20 may include high-speed random access memory and may also include non-transitory memory, such as at least one disk storage device, flash memory device, or other non-transitory solid-state storage device. In some alternative embodiments, the memory 20 may optionally include memory remotely located relative to the processor 10, and these remote memories may be connected to the computer device via a network. Examples of such networks include, but are not limited to, the Internet, intranets, local area networks, mobile communication networks, and combinations thereof.

[0111] The memory 20 may include volatile memory, such as random access memory; the memory may also include non-volatile memory, such as flash memory, hard disk or solid-state drive; the memory 20 may also include a combination of the above types of memory.

[0112] The computer device also includes a communication interface 30 for communicating with other devices or communication networks.

[0113] This disclosure also provides a computer-readable storage medium in which the methods described in this disclosure can be implemented in hardware or firmware, or implemented as recordable on a storage medium, or implemented as computer code originally stored on a remote storage medium or a non-transitory machine-readable storage medium and subsequently stored on a local storage medium after being downloaded over a network. Thus, the methods described herein can be processed by software stored on a storage medium using a general-purpose computer, a dedicated processor, or programmable or dedicated hardware. The storage medium may be a magnetic disk, optical disk, read-only memory, random access memory, flash memory, hard disk, or solid-state drive, etc.; further, the storage medium may also include combinations of the above types of memory. It is understood that computers, processors, microprocessor controllers, or programmable hardware include storage components capable of storing or receiving software or computer code that, when accessed and executed by the computer, processor, or hardware, implements the methods shown in the above embodiments.

[0114] In addition to the computer devices and computer-readable storage media described above, embodiments of this application may also be computer program products, which include computer program instructions that, when executed by a processor, cause the processor to perform the steps of the sound source localization method provided in any embodiment of this application.

[0115] Computer program products can be written in any combination of one or more programming languages ​​to perform the operations of the embodiments of this application. The programming languages ​​include object-oriented programming languages ​​such as Java and C++, as well as conventional procedural programming languages ​​such as C or similar languages. The program code can be executed entirely on the user's computing device, partially on the user's computing device, as a standalone software package, partially on the user's computing device and partially on a remote computing device, or entirely on a remote computing device or server.

[0116] The above are merely specific embodiments of this disclosure, enabling those skilled in the art to understand or implement this disclosure. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of this disclosure. Therefore, this disclosure is not to be limited to these embodiments, but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A network upgrade method, characterized in that, include: In response to the user's first action, a new version of the NAT gateway is introduced into the target network, which includes an edge gateway and a NAT gateway to be phased out. The edge gateway has the function of pooling elastic IP and NAT IP. Establish a first route between the new NAT gateway and the edge gateway, and establish a second route between the NAT gateway to be phased out and the edge gateway, wherein the priority of the first route is lower than the priority of the second route; The first public network segment of the NAT gateway to be phased out is published to the edge gateway, and the traffic entry and exit points corresponding to the first public network segment are changed from the NAT gateway to be phased out to the edge gateway. The second route and the NAT gateway to be phased out are then deleted from the target network in sequence.

2. The method according to claim 1, characterized in that, The target network is deployed in the following manner: In response to a second user action, an edge gateway is deployed in the initial network, which includes a resilient public IP gateway; Establish a route between the edge gateway and the elastic public IP gateway; The second public network segment of the elastic public IP gateway is published to the edge gateway, and the traffic entry and exit point corresponding to the second public network segment is changed from the elastic public IP gateway to the edge gateway to obtain the target network.

3. The method according to claim 2, characterized in that, After deploying the edge gateway in the initial network in response to the user's second action, the method further includes: Perform grayscale testing on the edge gateway.

4. The method according to claim 3, characterized in that, The gray-scale test of the edge gateway includes: A new public network segment is published on the edge gateway, and the traffic ingress and egress of the new public network segment is set to the edge gateway. The new public network segment is used as an elastic public IP. In response to a business request, a gray-scale test is performed on the edge gateway.

5. The method according to claim 2, characterized in that, The step of publishing the second public network segment of the elastic public IP gateway to the edge gateway, and changing the traffic ingress / egress point corresponding to the second public network segment from the elastic public IP gateway to the edge gateway, includes: A portion of the second public network segment is published to the edge gateway, and the traffic entry and exit points corresponding to the portion of the network segment are changed from the elastic public IP gateway to the edge gateway; In response to a service request, and in conjunction with the aforementioned network segments, a gray-scale test is conducted on the edge gateway to obtain the test results; When the test result is qualified, the remaining network segments in the second public network segment, excluding the aforementioned network segments, are published to the edge gateway, and the traffic entry and exit points corresponding to the remaining network segments are changed from the elastic public IP gateway to the edge gateway.

6. The method according to claim 1, characterized in that, The NAT gateway to be phased out is a gateway that has undergone a preliminary upgrade of the old NAT gateway, and the first public network segment includes non-shared pool network segment and shared pool network segment.

7. A network upgrade device, characterized in that, include: An introduction module is used to introduce a new version of the NAT gateway into the target network in response to the user's first operation. The target network includes an edge gateway and a NAT gateway to be phased out. The edge gateway has the function of pooling elastic IP and NAT IP. The module is used to establish a first route between the new NAT gateway and the edge gateway, and to establish a second route between the NAT gateway to be phased out and the edge gateway, wherein the priority of the first route is lower than the priority of the second route; The upgrade module is used to publish the first public network segment of the NAT gateway to be phased out to the edge gateway, change the traffic entry and exit point corresponding to the first public network segment from the NAT gateway to be phased out to the edge gateway, and sequentially delete the second route and the NAT gateway to be phased out from the target network.

8. A computer device, characterized in that, include: A memory and a processor are communicatively connected, the memory stores computer instructions, and the processor executes the computer instructions to perform the network upgrade method according to any one of claims 1 to 6.

9. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer instructions for causing the computer to perform the network upgrade method according to any one of claims 1 to 6.

10. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the steps of the network upgrade method according to any one of claims 1 to 6.

Images