Method and device for realizing multi-operator exit network in cloud network

Abstract

The invention provides a method and a device for realizing a multi-operator exit network in a cloud network. The method comprises the steps that a virtual network controlled by a software defined network (SDN) controller is established, and software comprises a three-layer structure including a traffic control (TC) area, a network element service area and a resource access layer; establishing an address pool of a multi-line elastic public network EIP of a preset operator, and realizing a multi-exit deployment mode; a preset operator elastic public network EIP is bound for a preset network card to realize a scheme that a single cloud host provides multi-operator bandwidth externally, and an operator link is selected by configuring a static routing mode in the cloud host; based on a preset flow control strategy, network element and multi-operator exit background control is realized; based on a preset virtual machine in an operator network, obtaining a time delay condition of a network of a plurality of EIPs bound on a single virtual machine of each client, and realizing detection of an operator link; and according to the link delay or interruption condition, switching control of an operator link or an operator exit is realized.

Description

Technical Field

[0001] The present application relates to the field of cloud computing network technology, and in particular to a method and apparatus for implementing a multi-operator egress network in a cloud network. Background Art

[0002] CloudOS 4.0, the next-generation IaaS cloud platform, supports multi-AZ resource layout, ultra-large cluster scale (a single AZ supports over 10,000 devices), and software and hardware collaboration. Its core resource pool capabilities meet the requirements for ultra-large-scale, high-performance, secure, and reliable cloud services.

[0003] Improves the IaaS platform's ultra-large-scale resource pool management and scheduling capabilities, supports ultra-large-scale data center networking and multi-AZ architectures, and boasts network management capabilities for resource pools up to 5,000 nodes. A single AZ supports 5,000 servers, increasing region size by more than 10 times, reaching industry-leading standards. This meets enterprise application needs for dual-site, three-center active-active deployment and disaster recovery.

[0004] CloudOS4.0, a new generation cloud platform developed based on the National Cloud, has been fully commercialized and deployed on the live network. As an independent and controllable cloud base with "one cloud, multiple forms, one cloud, multiple cores", and as one of the core components of CloudOS4.0, it provides a high-performance, high-availability, and highly reliable basic cloud network base.

[0005] Problems with existing technologies:

[0006] 1. Currently, cloud platforms, whether public or private, can only bind virtual machines to an EIP address with a fixed external network plane attribute, typically an EIP address with the China Telecom 163 plane attribute. In the networks of large ISPs, such as China Mobile and China Unicom, there are external network planes with multiple service attributes.

[0007] 2. As telecom service platforms move towards cloud computing, EIPs must connect not only to the public network but also to the telecom's internal DCN, CN2, and bearer networks, including the VPNs carried by these networks. For example, cloud tenant A's multiple virtual machines, VM1, VM2, and VMn, require access to multiple networks. Scenario 1: VM1 requires access to CN2, and VM2 to the DCN. Scenario 2: VM1 requires access to both CN2 and the DCN.

[0008] 3. In gaming scenarios, customer terminals may be hosted by different carriers, potentially seven or eight, such as China Railway Communications Corporation (CRCC). This requires a virtual machine with multiple external EIP addresses. The virtual machine can select the optimal EIP based on the customer's service latency. If one carrier link fails, the service can automatically switch to another carrier link. Currently, the cloud platform does not provide this feature. Summary of the Invention

[0009] This application shows a method and apparatus for implementing a multi-operator egress network in a cloud network.

[0010] In a first aspect, the present application provides a method for implementing a multi-operator egress network in a cloud network, the method comprising:

[0011] Establishing a virtual network controlled by a software-defined network (SDN) controller, wherein the software includes a three-layer structure of a traffic control TC area, a network element service area, and a resource access layer;

[0012] Establish a multi-line elastic public network EIP address pool with a preset operator to achieve a multi-egress deployment mode;

[0013] Bind the preset network card to the preset carrier's elastic public network EIP to enable a single cloud host to provide bandwidth from multiple carriers. Configure static routing within the cloud host to select the carrier link, or enable the cloud host to bind a network card to an EIP in the BGP multi-line address pool.

[0014] Based on preset traffic control strategies, it can realize background control of network elements and multi-operator egress;

[0015] Based on the pre-set virtual machines in the carrier network, the network latency of multiple EIPs bound to each customer's single virtual machine is obtained to detect the carrier link.

[0016] Based on link delay or interruption, operator link or operator export switching control is implemented.

[0017] In an exemplary embodiment of the present disclosure, the method further includes:

[0018] The first layer is the TC zone, which is responsible for accessing external networks, including extranet traffic, NAS traffic, dedicated point-of-presence (POPs), inter-cloud high-speed devices, and VPN devices. The network elements deployed in this zone include the AGW and SGW. The AGW is responsible for publishing the public network CIDR, and the SGW is responsible for rate limiting.

[0019] The second layer is the network element service area. The deployed service areas in this area provide tenants with network services from Layer 3 to Layer 7, including dedicated lines, IGW, NAT, VPN access, and LB.

[0020] The third layer is the resource access layer, which is responsible for providing virtual network access services for VMs, containers, and bare metal machines. The network element types are DVRs and SmartNICs.

[0021] In an exemplary embodiment of the present disclosure, the method further includes:

[0022] Multiple carriers are connected to the egress switch, and the link health detection function is enabled on each carrier egress and the egress switch.

[0023] On the cloud platform, an EIP address pool is provided for each operator, and a multi-line EIP address pool is also provided. The EIPs in the address pool automatically select the operator with the optimal route.

[0024] The EIP in the carrier's single-line address pool and the EIP in the BGP multi-line address pool are selected by the customer.

[0025] In an exemplary embodiment of the present disclosure, the method further includes:

[0026] Bind a pre-set network interface card (NIC) to a pre-set carrier's elastic public network EIP to enable a single cloud host to provide bandwidth from multiple carriers. Alternatively, configure static routing within the cloud host to select a carrier link, or enable binding a NIC to an EIP in a BGP multi-line address pool. Customers can choose which binding method to use based on network latency requirements and configuration flexibility.

[0027] In an exemplary embodiment of the present disclosure, the method further includes:

[0028] When traffic is diverted, the preset operator's bandwidth establishes a BGP neighbor relationship with the egress switch. The network element AGW and the egress switch establish a BGP neighbor relationship, publish EIP routes, and use routing policies to control the weight of the EIP to achieve route priority selection of the operator link;

[0029] When the traffic goes out, the SDN controller controls the traffic to perform corresponding NAT mapping on the IGW to the EIP address of the public network. Then, after the traffic rate is limited on the SGW, different VLAN headers are added to the preset operator traffic. The VLAN ID in the VLAN header is used to control the operator network selection of the traffic. Then, the traffic enters the egress switch through the default route within each VLAN. On the egress switch, the traffic is forwarded to the operator egress corresponding to the VLAN header according to the different VLAN headers of the traffic.

[0030] In an exemplary embodiment of the present disclosure, the method further includes:

[0031] The link latency information is provided to the customer, who then selects the carrier with the highest traffic priority based on the link quality.

[0032] For multi-line BGP, the link with the lowest latency is preferentially selected to forward traffic.

[0033] In an exemplary embodiment of the present disclosure, the method further includes:

[0034] If a ping test finds a carrier link outage, the controller will prioritize forwarding traffic to the carrier link with the second lowest latency for multi-line BGP EIPs.

[0035] For EIP traffic of a single operator, an alarm is issued to the customer, who then operates to switch the operator link egress.

[0036] In a second aspect, the present application provides a device for implementing a multi-operator egress network in a cloud network, the device comprising:

[0037] A virtual network construction module is used to establish a virtual network controlled by a software-defined network (SDN) controller. The software includes a three-layer structure consisting of a traffic control TC area, a network element service area, and a resource access layer.

[0038] The multi-egress deployment module is used to establish a multi-line elastic public network EIP address pool of a preset operator to implement a multi-egress deployment mode;

[0039] The EIP binding module is used to bind a preset network card to a preset carrier's elastic public network EIP to enable a single cloud host to provide bandwidth from multiple carriers. The cloud host can configure static routing internally to select the carrier link, or the cloud host can enable a network card to bind to an EIP in the BGP multi-line address pool.

[0040] Default operator determination module, used to implement background control of network elements and multi-operator egress based on preset traffic control strategies;

[0041] The carrier link detection module is used to obtain the network latency of multiple EIPs bound to each customer's single VM based on the preset VMs in the carrier network, thereby detecting the carrier link.

[0042] The operator egress switching module is used to implement operator link or operator egress switching control based on link delay or interruption.

[0043] In a third aspect, the present application shows an electronic device, which includes: a processor; a memory for storing processor-executable instructions; wherein the processor is configured to execute the method described in any of the above aspects.

[0044] In a fourth aspect, the present application shows a non-temporary computer-readable storage medium, which, when the instructions in the storage medium are executed by a processor of an electronic device, enables the electronic device to execute the method described in any of the above aspects.

[0045] In a fifth aspect, the present application illustrates a computer program product. When instructions in the computer program product are executed by a processor of an electronic device, the electronic device is enabled to execute the method as described in any one of the above aspects.

[0046] The present application provides a method and apparatus for implementing a multi-operator egress network in a cloud network. The method comprises: establishing a virtual network controlled by a software-defined network (SDN) controller, wherein the software comprises a three-layer structure of a traffic control TC zone, a network element service zone, and a resource access layer; establishing an address pool of a preset operator's multi-line elastic public network EIP to implement a multi-egress deployment mode; binding a preset operator's elastic public network EIP to a preset network card to implement a solution where a single cloud host provides multi-operator bandwidth externally, configuring static routing within the cloud host to select the operator link, or enabling the cloud host to bind a network card to an EIP in a BGP multi-line address pool; implementing backend control of network elements and multi-operator egress based on a preset traffic control policy; obtaining network latency of multiple EIPs bound to a single virtual machine for each customer based on preset virtual machines in the operator network to implement operator link detection; and implementing operator link or operator egress switching control based on link delay or interruption. This disclosure can provide cloud hosts with an export network solution that allows flexible control of multiple operator exports. It can also provide customers with recommendations for selecting the optimal operator bandwidth by detecting link quality. When a certain operator network fails, it can automatically switch to the optimal backup line, achieving high reliability of the multi-operator network. BRIEF DESCRIPTION OF THE DRAWINGS

[0047] Figure 1 This is a flowchart of the steps of a method for implementing a multi-operator egress network in a cloud network in the present application.

[0048] Figure 2 This is a schematic diagram of a virtual network controlled by an SDN controller in a method of implementing a multi-operator egress network in a cloud network according to the present application.

[0049] Figure 3 This is a schematic diagram of an operator multi-egress deployment mode for a method of implementing a multi-operator egress network in a cloud network in the present application.

[0050] Figure 4 This is a schematic diagram of addresses in an EIP address pool of a method for implementing a multi-operator egress network in a cloud network according to the present application.

[0051] Figure 5AThis is a schematic diagram of a scenario in which the cloud host operator links of the present application are respectively selected from China Telecom, China Unicom and China Mobile for realizing a method of multi-operator egress network in a cloud network.

[0052] Figure 5B This is a schematic diagram of a scenario in which a cloud host operator link selects BGP multiple lines in a method for implementing a multi-operator egress network in a cloud network according to the present application.

[0053] Figure 6 This is a schematic diagram of network elements and multi-operator egress backgrounds for a method of implementing a multi-operator egress network in a cloud network according to the present application.

[0054] Figure 7 This is a structural block diagram of a device for implementing a multi-operator egress network in a cloud network according to the present application.

[0055] Figure 8 This is a block diagram of an electronic device of the present application.

[0056] Figure 9 It is a block diagram of a computer-readable storage medium of the present application. DETAILED DESCRIPTION

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

[0058] The method for implementing a multi-operator egress network in a cloud network disclosed herein includes:

[0059] Step S110, establishing a virtual network controlled by a software-defined network (SDN) controller, wherein the software includes a three-layer structure of a traffic control TC area, a network element service area, and a resource access layer;

[0060] Step S120: Establish a multi-line elastic public network EIP address pool of a preset operator to implement a multi-egress deployment mode;

[0061] Step S130: Bind the preset network card to the preset operator's elastic public network EIP to implement a solution where a single cloud host provides bandwidth from multiple operators. The cloud host configures static routing internally to select the operator link, or the cloud host starts binding a network card to an EIP in the BGP multi-line address pool.

[0062] Step S140, based on the preset traffic control strategy, realize the network element and multi-operator egress background control;

[0063] Step S150: Based on the preset virtual machines in the operator network, the network latency of multiple EIPs bound to each customer's single virtual machine is obtained to detect the operator link.

[0064] Step S160: Implement operator link or operator export switching control according to link delay or interruption.

[0065] The present application provides a method and apparatus for implementing a multi-operator egress network in a cloud network. The method comprises: establishing a virtual network controlled by a software-defined network (SDN) controller, wherein the software comprises a three-layer structure of a traffic control TC zone, a network element service zone, and a resource access layer; establishing an address pool of a preset operator's multi-line elastic public network EIP to implement a multi-egress deployment mode; binding a preset operator's elastic public network EIP to a preset network card to implement a solution where a single cloud host provides multi-operator bandwidth externally, configuring static routing within the cloud host to select the operator link, or enabling the cloud host to bind a network card to an EIP in a BGP multi-line address pool; implementing backend control of network elements and multi-operator egress based on a preset traffic control policy; obtaining network latency of multiple EIPs bound to a single virtual machine for each customer based on preset virtual machines in the operator network to implement operator link detection; and implementing operator link or operator egress switching control based on link delay or interruption. This disclosure can provide cloud hosts with an export network solution that allows flexible control of multiple operator exports. It can also provide customers with recommendations for selecting the optimal operator bandwidth by detecting link quality. When a certain operator network fails, it can automatically switch to the optimal backup line, achieving high reliability of the multi-operator network.

[0066] Example 1:

[0067] Reference Figure 1 , shows a flowchart of the steps of a method for implementing a multi-operator egress network in a cloud network of the present application, which can be applied to an electronic device, wherein the method specifically may include the following steps:

[0068] In step S110, a virtual network controlled by a software-defined network (SDN) controller may be established, wherein the software includes a three-layer structure of a traffic control TC area, a network element service area, and a resource access layer.

[0069] In the embodiment of this example, the method further includes:

[0070] The first layer is the TC zone, which is responsible for accessing external networks, including extranet traffic, NAS traffic, dedicated point-of-presence (POPs), inter-cloud high-speed devices, and VPN devices. The network elements deployed in this zone include the AGW and SGW. The AGW is responsible for publishing the public network CIDR, and the SGW is responsible for rate limiting.

[0071] The second layer is the network element service area, which provides tenants with network services from layer 3 to layer 7, including dedicated lines, IGW, NAT, VPN access, LB

[0072] The third layer is the resource access layer, which is responsible for providing virtual network access services for VMs, containers, and bare metal machines. The network element types are DVRs and SmartNICs.

[0073] In step S120, an address pool of a preset operator's multi-line elastic public network EIP can be established to implement a multi-egress deployment mode.

[0074] In this exemplary embodiment, the method further includes:

[0075] Multiple carriers are connected to the egress switch, and the link health detection function is enabled on each carrier egress and the egress switch.

[0076] On the cloud platform, an EIP address pool is provided for each operator, and a multi-line EIP address pool is also provided. The EIPs in the address pool automatically select the operator with the optimal route;

[0077] The EIP in the carrier's single-line address pool and the EIP in the BGP multi-line address pool are selected by the customer.

[0078] In step S130, the preset network card can be bound to the preset operator's elastic public network EIP to enable a single cloud host to provide multi-operator bandwidth to the outside world. The cloud host can select the operator link by configuring static routing internally, or the cloud host can start a network card to bind an EIP in the BGP multi-line address pool.

[0079] In this exemplary embodiment, the method further includes:

[0080] Bind a pre-set network interface card (NIC) to a pre-set carrier's elastic public network EIP to enable a single cloud host to provide bandwidth from multiple carriers. Alternatively, configure static routing within the cloud host to select a carrier link, or enable binding a NIC to an EIP in a BGP multi-line address pool. Customers can choose which binding method to use based on network latency requirements and configuration flexibility.

[0081] In step S140, network element and multi-operator egress background control may be implemented based on a preset traffic control strategy.

[0082] In this exemplary embodiment, the method further includes:

[0083] When traffic is diverted, the preset operator's bandwidth establishes a BGP neighbor relationship with the egress switch. The network element AGW and the egress switch establish a BGP neighbor relationship, publish EIP routes, and use routing policies to control the weight of the EIP to achieve route priority selection of the operator link;

[0084] When the traffic goes out, the SDN controller controls the traffic to perform corresponding NAT mapping on the IGW to the EIP address of the public network. Then, after the traffic rate is limited on the SGW, different VLAN headers are added to the preset operator traffic. The VLAN ID in the VLAN header is used to control the operator network selection of the traffic. Then, the traffic enters the egress switch through the default route within each VLAN. On the egress switch, the traffic is forwarded to the operator egress corresponding to the VLAN header according to the different VLAN headers of the traffic.

[0085] In step S150, based on the preset virtual machines in the operator network, the network latency of multiple EIPs bound to a single virtual machine of each customer can be obtained to implement the detection of the operator link.

[0086] In step S160, operator link or operator export switching control can be implemented according to link delay or interruption.

[0087] In this exemplary embodiment, the method further includes:

[0088] The link latency information is provided to the customer, who then selects the carrier with the highest traffic priority based on the link quality.

[0089] For multi-line BGP, the link with the lowest latency is preferentially selected to forward traffic.

[0090] In this exemplary embodiment, the method further includes:

[0091] If a ping test finds a carrier link outage, the controller will prioritize forwarding traffic to the carrier link with the second lowest latency for multi-line BGP EIPs.

[0092] For EIP traffic of a single operator, an alarm is issued to the customer, who then operates to switch the operator link egress.

[0093] Example 2:

[0094] In the embodiment of this example, the proper nouns are described as follows:

[0095] SDN (Software Defined Network)

[0096] OVS (Open Vswitch, virtual switch)

[0097] VXLAN (Virtual eXtensible LAN)

[0098] EIP (Elastic Public IP function, achieving 1:1 NAT)

[0099] Subnet (subnet function, can create subnets within VPC)

[0100] VNI range VNI segment management.

[0101] In this exemplary embodiment, Figure 2 As shown in the figure, the virtual network controlled by the SDN controller is divided into three layers:

[0102] The first layer is the TC area, which is responsible for accessing the external network, including external network traffic, NAS traffic, dedicated line POP, cloud high-speed equipment, VPN equipment, etc. These devices are all multi-active access. The network elements deployed in this area are AGW and SGW. AGW is responsible for publishing public network CIDR, and SGW is responsible for speed limiting.

[0103] The second layer is the network element service area. The service area deployed in this area provides tenants with network services from layer 3 to layer 7, including dedicated lines, IGW, NAT, VPN access, LB, etc.

[0104] The third layer is the resource access layer, which is responsible for providing virtual network access services for VMs, containers, and bare metal machines. The network element types are DVRs and SmartNICs.

[0105] In this exemplary embodiment, Figure 3 As shown, the operator's multi-egress deployment mode is as follows:

[0106] Multiple operators are connected to the egress switch, and the link health detection function is enabled on each operator's egress and egress switch. An EIP address pool is provided for each operator on the cloud platform, and a multi-line EIP address pool is also provided. The EIP in this address pool will automatically select the operator with the best route. Figure 4 As shown, customers can bind specific addresses in the EIP address pool according to their needs.

[0107] Provide EIPs in the operator's single-line address pool and EIPs in the BGP multi-line address pool for customers to choose from.

[0108] In this example, at the cloud host level, multiple network cards are started by the cloud host, and each network card is bound to a different operator's EIP to implement a single cloud host to provide multiple operator bandwidth solutions. Static routing can be configured within the cloud host to select which operator link the traffic should take, such as Figure 5A shown.

[0109] You can also let the cloud host start a network card to bind the EIP in the BGP multi-line address pool, such as Figure 5B shown.

[0110] In this example, the two binding scenarios differ. A single cloud host activates multiple network interfaces (NICs) and binds them to different carriers. Customers can segment traffic to specific carriers, reducing network latency for their services and saving costs. However, this requires high deployment requirements, requiring customers to configure traffic routing and select the carrier's NIC. Alternatively, a single NIC in a cloud host is bound to an EIP from a BGP multi-line address pool. The SDN controller detects and selects the optimal carrier link, eliminating the need for customers to configure routing. This facilitates usage, but prevents tailoring to the carrier with the lowest latency for each customer, and results in higher costs.

[0111] In this example embodiment, the network element and the multi-operator export background are specifically implemented as follows Figure 6 As shown:

[0112] When routing traffic, each carrier's bandwidth establishes a BGP peer relationship with the egress switch. The AGW (Advanced Gateway) establishes a BGP peer relationship with the egress switch and advertises EIP routes. For example, an EIP in the telecom resource pool is advertised only to the telecom egress using BGP routing policies. An EIP in the BGP multi-line address pool advertises EIP routes to all carrier egresses. Routing policies weight these EIPs to prioritize routes from carrier links. When traffic is routed out, the SDN controller performs NAT on the IGW to the public network's EIP address. After rate limiting on the SGW, traffic from different carriers is added with different VLAN headers. VLAN IDs are used to control which carrier network the traffic enters. Within each VLAN, traffic enters the egress switch using the default route. The egress switch then forwards the traffic to different carrier egresses based on the VLAN headers.

[0113] In this example embodiment, carrier link detection is implemented as follows: For customer-purchased EIPs, a detection function is enabled. A virtual machine is started in the same carrier network, simulating a client in Beijing, for example, and pinging this EIP. This provides network latency for multiple EIPs bound to each customer's single virtual machine, as shown in the following table.

[0114] EIP(type) Link delay 10.1.1.1 (Telecommunications) 30ms 20.1.1.1 (Mobile) 50ms 30.1.1.1 (China Unicom) 100ms 40.1.1.1 (China Railway Communications Corporation) 300ms 50.1.1.1 (multi-line BGP) 30ms

[0115] In this example embodiment, the link latency is provided to the customer, allowing the customer to select which operator's bandwidth to prioritize traffic based on link quality. For multi-line BGP, the link with the lowest latency is prioritized for forwarding traffic.

[0116] In this example embodiment, when a ping test detects a link outage with a specific carrier, the controller prioritizes forwarding traffic for multi-line BGP EIPs to the carrier link with the second lowest latency. For traffic from a single carrier's EIP, an alert is immediately issued to the customer, who then switches traffic to the appropriate carrier link egress.

[0117] In the embodiment of this example, through the above steps, it is possible to provide the cloud host with an export network solution that flexibly controls the exports of multiple operators. At the same time, by detecting the quality of the link, it can help customers provide recommendations for selecting the optimal operator bandwidth. At the same time, when a certain operator network fails, it can automatically switch to the optimal backup line, thereby achieving the goal of high reliability of the multi-operator network.

[0118] In the embodiment of this example, the present disclosure proposes an export network solution that provides cloud hosts with flexible control of multi-operator exports; by detecting the quality of the link, it can help customers provide recommendations for selecting the optimal operator bandwidth. At the same time, when a certain operator network fails, it can automatically switch to the optimal backup line, thereby achieving the goal of high reliability of multi-operator networks.

[0119] It should be noted that for the method embodiments, for simplicity of description, they are all expressed as a series of action combinations, but those skilled in the art should be aware that this application is not limited by the order of the actions described, because according to this application, certain steps can be performed in other orders or simultaneously. Secondly, those skilled in the art should also be aware that the embodiments described in this specification are all optional embodiments, and the actions involved are not necessarily required by this application.

[0120] Reference Figure 7 , shows a structural block diagram of a device for implementing a multi-operator egress network in a cloud network of the present application, the device comprising:

[0121] A virtual network construction module 210 is used to establish a virtual network controlled by a software-defined network (SDN) controller. The software includes a three-layer structure of a traffic control TC area, a network element service area, and a resource access layer.

[0122] The multi-egress deployment module 220 is used to establish an address pool of multiple elastic public network EIPs of a preset operator to implement a multi-egress deployment mode;

[0123] The EIP binding module 230 is used to bind a preset network card to a preset operator's elastic public network EIP to enable a single cloud host to provide multiple operator bandwidth externally. The cloud host configures static routing internally to select the operator link, or the cloud host starts a network card to bind an EIP in the BGP multi-line address pool;

[0124] The default operator determination module 240 is used to implement network element and multi-operator egress background control based on a preset traffic control strategy;

[0125] The operator link detection module 250 is used to obtain the network latency of multiple EIPs bound to a single virtual machine of each customer based on the preset virtual machines in the operator network, thereby realizing the detection of the operator link;

[0126] The operator egress switching module 260 is used to implement operator link or operator egress switching control according to link delay or interruption.

[0127] As for the device embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment.

[0128] Optionally, an embodiment of the present application also provides an electronic device, comprising: a processor, a memory, and a computer program stored in the memory and runnable on the processor. When the computer program is executed by the processor, the various processes of the above-mentioned method embodiment are implemented and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

[0129] The present application also provides a computer-readable storage medium having a computer program stored thereon. When the computer program is executed by a processor, the various processes of the above-described method embodiments are implemented and the same technical effects are achieved. To avoid repetition, the details are not described here. The computer-readable storage medium may be, for example, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0130] Figure 88 is a block diagram of an electronic device 800 shown in the present application. For example, the electronic device 800 may be a mobile phone, a computer, a digital broadcast terminal, a messaging device, a game console, a tablet device, a medical device, a fitness device, a personal digital assistant, etc.

[0131] Reference Figure 8 , the electronic device 800 may include one or more of the following components: a processing component 802 , a memory 804 , a power component 806 , a multimedia component 808 , an audio component 810 , an input / output (I / O) interface 812 , a sensor component 814 , and a communication component 816 .

[0132] The processing component 802 generally controls the overall operation of the electronic device 800, such as operations associated with display, phone calls, data communications, camera operation, and recording operations. The processing component 802 may include one or more processors 820 to execute instructions to perform all or part of the steps of the above-described method. In addition, the processing component 802 may include one or more modules to facilitate interaction between the processing component 802 and other components. For example, the processing component 802 may include a multimedia module to facilitate interaction between the multimedia component 808 and the processing component 802.

[0133] The memory 804 is configured to store various types of data to support operations on the device 800. Examples of such data include instructions for any application or method operating on the electronic device 800, contact data, phone book data, messages, images, videos, etc. The memory 804 can be implemented by any type of volatile or non-volatile storage device, or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic disk, or optical disk.

[0134] The power supply component 806 provides power to the various components of the electronic device 800. The power supply component 806 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power to the electronic device 800.

[0135] The multimedia component 808 includes a screen that provides an output interface between the electronic device 800 and the user. In some embodiments, the screen may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen can be implemented as a touch screen to receive input signals from the user. The touch panel includes one or more touch sensors to sense touches, slides, and gestures on the touch panel. The touch sensor can not only sense the boundaries of the touch or slide action, but also detect the duration and pressure associated with the touch or slide operation. In some embodiments, the multimedia component 808 includes a front camera and / or a rear camera. When the device 800 is in an operating mode, such as a shooting mode or a video mode, the front camera and / or the rear camera can receive external multimedia data. Each front camera and rear camera can be a fixed optical lens system or have a focal length and optical zoom capability.

[0136] The audio component 810 is configured to output and / or input audio signals. For example, the audio component 810 includes a microphone (MIC), which is configured to receive external audio signals when the electronic device 800 is in an operating mode, such as a call mode, a recording mode, and a voice recognition mode. The received audio signal can be further stored in the memory 804 or transmitted via the communication component 816. In some embodiments, the audio component 810 also includes a speaker for outputting audio signals.

[0137] I / O interface 812 provides an interface between processing component 802 and peripheral interface modules, such as a keyboard, click wheel, buttons, etc. These buttons may include but are not limited to: a home button, volume buttons, a start button, and a lock button.

[0138] The sensor assembly 814 includes one or more sensors for providing various aspects of status assessment for the electronic device 800. For example, the sensor assembly 814 can detect the open / closed state of the device 800, the relative positioning of components, such as the display and keypad of the electronic device 800. The sensor assembly 814 can also detect changes in the position of the electronic device 800 or a component of the electronic device 800, the presence or absence of user contact with the electronic device 800, the orientation or acceleration / deceleration of the electronic device 800, and temperature changes of the electronic device 800. The sensor assembly 814 may include a proximity sensor configured to detect the presence of nearby objects without any physical contact. The sensor assembly 814 may also include a light sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In some embodiments, the sensor assembly 814 may also include an accelerometer, a gyroscope sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.

[0139] The communication component 816 is configured to facilitate wired or wireless communication between the electronic device 800 and other devices. The electronic device 800 can access a wireless network based on a communication standard, such as WiFi, an operator network (such as 2G, 3G, 4G or 5G), or a combination thereof. In an exemplary embodiment, the communication component 816 receives a broadcast signal or broadcast operation information from an external broadcast management system via a broadcast channel. In an exemplary embodiment, the communication component 816 also includes a near field communication (NFC) module to facilitate short-range communication. For example, the NFC module can be implemented based on radio frequency identification (RFID) technology, infrared data association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology and other technologies.

[0140] In an exemplary embodiment, the electronic device 800 may be implemented by one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), controllers, microcontrollers, microprocessors, or other electronic components to perform the above methods.

[0141] In an exemplary embodiment, a non-transitory computer-readable storage medium including instructions is also provided, such as a memory 804 including instructions, and the instructions can be executed by the processor 820 of the electronic device 800 to perform the above method. For example, the non-transitory computer-readable storage medium can be a ROM, a random access memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, etc.

[0142] Figure 9 19 is a block diagram of a computer-readable storage medium 1900 shown in the present application. For example, the computer-readable storage medium 1900 may be provided as a server.

[0143] Reference Figure 9 Computer-readable storage medium 1900 includes a processing component 1922, which further includes one or more processors, and memory resources represented by memory 1932 for storing instructions, such as applications, that can be executed by processing component 1922. The application stored in memory 1932 may include one or more modules, each corresponding to a set of instructions. In addition, processing component 1922 is configured to execute instructions to perform the above-described method.

[0144] The computer-readable storage medium 1900 may further include a power supply component 1926 configured to perform power management of the computer-readable storage medium 1900, a wired or wireless network interface 1950 configured to connect the computer-readable storage medium 1900 to a network, and an input / output (I / O) interface 1958. The computer-readable storage medium 1900 may operate based on an operating system stored in the memory 1932, such as Windows Server™, Mac OS X™, Unix™, Linux™, FreeBSD™, or the like.

[0145] It should be noted that, in this document, the terms "comprises," "includes," or any other variations thereof are intended to encompass non-exclusive inclusion, such that a process, method, article, or apparatus comprising a series of elements includes not only those elements but also other elements not explicitly listed, or elements inherent to such process, method, article, or apparatus. In the absence of further limitations, an element defined by the phrase "comprising a ..." does not exclude the presence of other identical elements in the process, method, article, or apparatus comprising the element.

[0146] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus the necessary general hardware platform, and of course can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk), and includes a number of instructions for enabling a terminal (which can be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in each embodiment of the present application.

[0147] The embodiments of the present application are described above in conjunction with the accompanying drawings, but the present application is not limited to the above-mentioned specific implementation methods. The above-mentioned specific implementation methods are merely illustrative and not restrictive. Under the guidance of this application, ordinary technicians in this field can also make many forms without departing from the purpose of this application and the scope of protection of the claims, all of which are within the protection of this application.

[0148] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed in the embodiments of this application can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0149] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0150] In the embodiments provided in this application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of the units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0151] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of these units may be selected to achieve the purpose of this embodiment according to actual needs.

[0152] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0153] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, 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. The computer software product is stored in a storage medium and includes several instructions for enabling a computer device (which can be a personal computer, server, or network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes various media that can store program codes, such as a USB flash drive, a mobile hard disk, a ROM, a RAM, a magnetic disk, or an optical disk.

[0154] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this application should be included in the scope of protection of the present application. Therefore, the scope of protection of the present application should be based on the scope of protection of the claims.

Claims

1. A method for implementing a multi-operator egress network in a cloud network, characterized in that: The method comprises: Establish a virtual network controlled by a software-defined network SDN controller, wherein the software includes a three-layer structure of a flow control TC area, a network element service area, and a resource access layer; the software includes a three-layer structure of a flow control TC area, a network element service area, and a resource access layer; Establish a preset operator multi-line elastic public network EIP address pool to achieve multi-egress deployment mode; Bind the preset operator's elastic public network EIP to the preset network card to enable a single cloud host to provide multi-operator bandwidth externally: the cloud host selects the operator link by configuring static routing internally, or the cloud host starts a network card to bind an EIP in the BGP multi-line address pool; Based on the preset traffic control strategy, the background control of network elements and multi-operator exports is realized; Based on the preset virtual machines in the operator network, the network latency of multiple EIPs bound to each customer's single virtual machine is obtained to detect the operator link. According to the link delay or interruption situation, the operator link or operator's export switching control is realized.

2. The method according to claim 1, characterized in that The method further includes: The first layer is the TC area, which is responsible for accessing external networks including external network traffic, NAS traffic, dedicated line POP, inter-cloud high-speed devices, and VPN devices. The network elements deployed in this area are AGW and SGW. AGW is responsible for publishing public network CIDR, and SGW is responsible for speed limit. The second layer is the network element service area. The deployed service areas in this area provide tenants with network services from layer 3 to layer 7, including dedicated lines, IGW, NAT, VPN access, and LB. The third layer is the resource access layer, which is responsible for providing virtual network access services for VMs, containers, and bare metal machines. The network element types are DVR and SmartNIC.

3. The method according to claim 1, characterized in that The method further comprises: Multiple operators are connected to the egress switch, and the link health detection function is enabled on each operator egress and egress switch; An EIP address pool is provided for each operator on the cloud platform, and a multi-line EIP address pool is provided at the same time. The EIP in the address pool automatically selects the operator with the best route; The EIPs in the carrier's single-line address pool and the EIPs in the BGP multi-line address pool are selected by the customer.

4. The method according to claim 1, characterized in that The method further comprises: Bind the preset network card to the preset operator's elastic public network EIP to enable a single cloud host to provide multi-operator bandwidth to the outside world. The cloud host configures static routing internally to select the operator link, or the cloud host starts a network card to bind the EIP in the BGP multi-line address pool. Customers can choose to use it according to network latency requirements and configuration freedom.

5. The method according to claim 1, characterized in that The method further comprises: When traffic is diverted, the bandwidth of the preset operator is established with the egress switch as a BGP neighbor, the network element AGW and the egress switch establish a BGP neighbor, publish EIP routes to the outside, and control the weight of the EIP through the routing policy to achieve the routing priority selection of the operator link; When the traffic goes out, the SDN controller controls the traffic to do the corresponding NAT mapping on the IGW to the EIP address of the public network, and then adds different VLAN headers to the preset operator traffic after limiting the traffic speed on the SGW. The operator network selection of the traffic is controlled by the VLAN ID in the VLAN header, and then enters the egress switch through the default route in each VLAN. On the egress switch, according to the different VLAN headers of the traffic, it is forwarded to the operator exit corresponding to the VLAN header.

6. The method according to claim 1, characterized in that The method further comprises: The link latency information is provided to the customer, who then selects the operator with the highest traffic priority based on the link quality. For multi-line BGP, the link with the lowest latency is preferentially selected to forward traffic.

7. The method according to claim 1, characterized in that The method further comprises: When the ping test finds that the carrier link is disconnected, for multi-line BGP EIP, the controller controls the traffic to be forwarded to the carrier link with the second lowest latency first; For EIP traffic of a single operator, an alarm is issued to the customer, who then operates to switch the operator's link egress.

8. A device for implementing a multi-operator egress network in a cloud network, characterized in that: The device comprises: A virtual network construction module is used to establish a virtual network controlled by a software-defined network SDN controller, wherein the software includes a three-layer structure of a traffic control TC area, a network element service area, and a resource access layer; The multi-egress deployment module is used to establish an address pool of multi-line elastic public network EIPs of a preset operator to implement a multi-egress deployment mode; The EIP binding module is used to bind the preset operator's elastic public network EIP to the preset network card so that a single cloud host can provide multiple operator bandwidths to the outside world. The cloud host can select the operator link by configuring static routing inside, or the cloud host can start a network card to bind an EIP in the BGP multi-line address pool. The default operator determination module is used to implement background control of network elements and multi-operator egress based on preset traffic control strategies; The operator link detection module is used to obtain the network latency of multiple EIPs bound to a single virtual machine of each customer based on the preset virtual machine in the operator network, so as to realize the detection of the operator link; The operator export switching module is used to implement operator link or operator export switching control according to link delay or interruption.

9. An electronic device, characterized in that: include: A processor, a memory, and a computer program stored in the memory and executable on the processor, wherein the computer program implements the method according to any one of claims 1 to 7 when executed by the processor.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the method according to any one of claims 1 to 7 is implemented.

Images