A method and system for traffic pinning based on SDWAN

Abstract

The application discloses a traffic collection method and system based on SDWAN, wherein the method comprises the following steps: S1, establishing an independent forwarding logic plane from a branch CPE to a collection CPE for each collection center; S2, when a main collection center fails, the internet traffic on the branch CPE can be automatically switched to a standby collection center; S3, when the outlet of the collection center is congested, the internet traffic on the outlet can be intelligently scheduled to a non-congested collection center. The application has low deployment cost, and enterprise users can independently construct multiple internet collections within the enterprise geographical coverage range based on SDWAN. The multiple collections can simultaneously collect the internet traffic of branches, and when a collection center fails, the traffic can be automatically switched to the outlet of other collection centers. When the outlet of a collection center is congested, the traffic on the congested outlet can be automatically scheduled to the outlet of other collection centers, so that the network resource utilization rate can be improved, and the global optimization of the traffic is ensured.

Description

Technical Field

[0001] This invention relates to the field of network communication technology, and in particular to a traffic convergence method and system based on SDWAN. Background Technology

[0002] With the rapid development of information technology and the deepening of enterprise informatization, central state-owned enterprises and large enterprise groups have placed higher demands on network traffic management for their branches across the country. To strengthen network security supervision, improve network usage efficiency, and meet the guiding principles of relevant national policies, existing network traffic control solutions urgently need optimization and improvement.

[0003] Currently, enterprises mainly adopt two approaches when deploying traffic aggregation solutions:

[0004] 1. Leased Line Solution: This solution includes mainstream leased lines such as fiber optic, MSTP, MPLS, and IP RAN. Each branch site and the receiving site transmit the host's Internet traffic through a leased line. However, this solution has extremely high leased line costs, which prevents many enterprises from adopting it due to budget constraints.

[0005] 2. Internet-based SD-WAN or VPN solutions: This solution utilizes SD-WAN or VPN technology to build an overlay tunnel over the internet to transmit internet traffic. Because it's built over the internet, the cost is relatively low, making it widely accepted. However, this solution typically only supports a single gateway center site or a primary / backup gateway center site, and cannot effectively support multiple gateway center load balancing deployments, or it can only achieve load balancing by deploying multiple networks. Furthermore, due to network differences between northern and southern China, gateway congestion can easily occur during different business periods, making global optimization impossible. Summary of the Invention

[0006] The purpose of this section is to outline some aspects of embodiments of the present invention and to briefly describe some preferred embodiments. Simplifications or omissions may be made in this section, as well as in the abstract and title of this application, to avoid obscuring the purpose of these documents; however, such simplifications or omissions should not be construed as limiting the scope of the invention.

[0007] To address the aforementioned technical problems, this invention provides the following technical solution: a traffic convergence method based on SDWAN, comprising the following steps:

[0008] S1: Establish an independent forwarding logical plane from the branch CPE to the receiving CPE for each receiving center;

[0009] S2: In the event of a failure of the primary receiving center, internet traffic on the branch CPE can be automatically switched to the backup receiving center;

[0010] S3: When the exit point of a receiving center is congested, it can intelligently dispatch Internet traffic on that exit point to a non-congested receiving center.

[0011] As a preferred embodiment of the SDWAN-based traffic convergence method of the present invention, the specific implementation process of S1 is as follows:

[0012] S11: Create an Internet gateway strategy. The strategy parameters mainly include a primary gateway site, a backup gateway site, and several branch sites.

[0013] S12: After the policy parameters are configured, the SDWAN controller will automatically orchestrate the data plane network elements CPE and POP that are bound to the receiving policy on the SDWAN network to establish a logical overlay plane;

[0014] S13: If there are multiple receiving centers, multiple forwarding planes need to be built. Each forwarding plane is isolated by the router's VRF to ensure the independence and security of each plane and prevent traffic interference and leakage between different planes.

[0015] As a preferred embodiment of the SDWAN-based traffic convergence method described in this invention, the overlay plane is used to realize traffic forwarding from the branch CPE to the convergence CPE.

[0016] As a preferred embodiment of the SDWAN-based traffic convergence method of the present invention, the specific implementation process of step S2 is as follows:

[0017] S21: For a branch site, when the primary receiving center site corresponding to its own site fails, the fault detection mechanism will trigger the default route published by the primary receiving center to become invalid.

[0018] S22: The branch CPF automatically selects the low-priority default route published by the backup receiving center, and the Internet traffic of the branch site is automatically forwarded to the CPE of the backup receiving center through the sdwan overlay tunnel;

[0019] S23: When the primary receiving center recovers from a failure, it republishes the high-priority default route. Once the branch CPE detects that the high-priority default route is available, it automatically switches the internet traffic of the branch site back to the primary receiving center's exit route.

[0020] As a preferred embodiment of the SDWAN-based traffic convergence method described in this invention, seamless switching technology can be used when automatically switching the Internet traffic of branch sites back to the main convergence center exit.

[0021] As a preferred embodiment of the SDWAN-based traffic convergence method described in this invention, the seamless switching technology includes MPLS or GRE tunnels.

[0022] As a preferred embodiment of the SDWAN-based traffic convergence method described in this invention, a fault detection mechanism is configured on the SDWAN controller and the branch CPE.

[0023] As a preferred embodiment of the SDWAN-based traffic convergence method of the present invention, the specific implementation process of S3 is as follows:

[0024] S31: Each branch site's CPE device is configured with a bandwidth monitoring module to continuously monitor the real-time internet bandwidth load between the site and the SDWAN network, and periodically and proactively upload the data to the SDWAN controller.

[0025] S32: Deploy a traffic monitor on the CPE of traffic receiving center A to monitor the real-time bandwidth load from the center to the Internet and periodically send the data to the SDWAN controller.

[0026] S33: Deploy a traffic monitor and a traffic scheduler on the SDWAN controller. The traffic monitor collects the internet bandwidth usage load of all branch and receiving center CPE network elements in real time.

[0027] S34: The traffic scheduler sets a line bandwidth usage threshold based on the Internet egress bandwidth of the CPE network element in the receiving center. When the real-time bandwidth exceeds the threshold, it indicates that the egress line is congested. When the real-time bandwidth exceeds the threshold value, intelligent traffic scheduling is triggered.

[0028] S35: When the congestion state of receiving center A is relieved and the real-time bandwidth utilization of the receiving center is less than 80%, the SDWAN traffic scheduler can switch the Internet traffic of the branch sites that were switched away in step S34 back from receiving center B to receiving center A. In order to avoid the back-switching causing congestion in receiving center A again, the back-switching action is performed once every 5 minutes. The total real-time bandwidth of the branch sites switched back each time does not exceed the set of branch sites that are 5% of the receiving center's congestion threshold.

[0029] As a preferred embodiment of the SDWAN-based traffic convergence method described in this invention, the intelligent traffic scheduling step is as follows:

[0030] S341: When receiving center A is congested, the traffic scheduler first selects an available receiving center B as the receiver for traffic scheduling. The current real-time bandwidth utilization of receiving center B is the lowest and does not exceed 80% of its own congestion threshold.

[0031] S342: The traffic scheduler then calculates the total amount of overloaded bandwidth usage at the current congested receiving center A, collects the current forwarded Internet traffic to the branch sites of the overloaded receiving center, selects N sites from the collected branch sites, and ensures that the Internet bandwidth usage of these N sites does not exceed 10% of the congestion threshold bandwidth. Then, it switches the Internet traffic of these N sites to the backup receiving center selected in step S341.

[0032] S343: Execute steps S341 and S342 every M minutes until the congestion at the closing center A is relieved.

[0033] The present invention also provides a system for a traffic convergence method based on SDWAN, including an SDWAN controller, a branch CPE device, and a convergence CPE device;

[0034] The SDWAN controller is responsible for policy configuration, network orchestration, traffic monitoring, and scheduling.

[0035] The branch CPE device is used to monitor and report bandwidth load and perform traffic switching;

[0036] The CPE device monitors internet bandwidth load and assists in traffic scheduling.

[0037] The beneficial effects of this invention are:

[0038] 1. This invention significantly reduces deployment costs by building an SDWAN overlay tunnel on the Internet.

[0039] 2. By setting up primary and backup receiving centers, this invention can achieve automatic switching, ensuring high network reliability.

[0040] 3. When congestion occurs at the receiving center, this invention can intelligently dispatch traffic to a non-congested receiving center, thereby improving network resource utilization and ensuring global traffic optimization.

[0041] 4. This invention supports load balancing deployment of multiple receiving centers, adapting to changes in enterprise network needs and offering high flexibility.

[0042] 5. This invention can optimize traffic allocation across the entire network through real-time monitoring and intelligent scheduling, avoid local network congestion, and thus improve overall network performance. Attached Figure Description

[0043] To more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings used in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort. Wherein:

[0044] Figure 1 This is a flowchart of a traffic convergence method based on SDWAN according to the present invention.

[0045] Figure 2 This is a technical illustration of a traffic convergence scheme based on an SDWAN-based traffic convergence method according to the present invention.

[0046] Figure 3 This is a diagram illustrating the multi-traffic interface master / slave switching of a traffic interface based on SDWAN according to the present invention.

[0047] Figure 4 This is a load balancing scheduling diagram for a multi-traffic gateway center based on an SDWAN-based traffic gateway method according to the present invention. Detailed Implementation

[0048] To make the above-mentioned objects, features and advantages of the present invention more apparent and understandable, the specific embodiments of the present invention will be described in detail below with reference to the accompanying drawings.

[0049] Many specific details are set forth in the following description in order to provide a full understanding of the invention. However, the invention may also be practiced in other ways different from those described herein, and those skilled in the art can make similar extensions without departing from the spirit of the invention. Therefore, the invention is not limited to the specific embodiments disclosed below.

[0050] Secondly, the term "one embodiment" or "embodiment" as used herein refers to a specific feature, structure, or characteristic that may be included in at least one implementation of the present invention. The phrase "in one embodiment" appearing in different places in this specification does not necessarily refer to the same embodiment, nor is it a single or selective embodiment that is mutually exclusive with other embodiments.

[0051] Secondly, the present invention is described in detail with reference to the schematic diagrams. When detailing the embodiments of the present invention, for ease of explanation, the cross-sectional views illustrating the device structure may be partially enlarged, not according to the usual scale. Furthermore, the schematic diagrams are merely examples and should not limit the scope of protection of the present invention. In addition, actual fabrication should include three-dimensional spatial dimensions of length, width, and depth.

[0052] Example 1

[0053] Reference Figure 1-4This is the first embodiment of the present invention, providing a traffic convergence method and system based on SDWAN, including the following steps (such as...). Figure 1 ):

[0054] S1: Establish an independent forwarding logical plane from the branch CPE to the receiving CPE for each receiving center;

[0055] S2: In the event of a failure of the primary receiving center, internet traffic on the branch CPE can be automatically switched to the backup receiving center;

[0056] S3: When the exit point of a receiving center is congested, it can intelligently dispatch Internet traffic on that exit point to a non-congested receiving center.

[0057] Specifically, the implementation process of S1 is as follows:

[0058] S11: Create an Internet gateway strategy. The strategy parameters mainly include a primary gateway site, (optional) a backup gateway site, and several branch sites.

[0059] S12: After the policy parameters are configured, the SDWAN controller will automatically orchestrate the data plane network elements CPE and POP that are bound to the receiving policy on the SDWAN network, and establish a logical overlay plane to realize traffic forwarding from branch CPE to receiving CPE.

[0060] S13: If there are multiple receiving centers, multiple forwarding planes need to be built. Each forwarding plane is isolated by a router VRF (Virtual Routing Forwarding Table) to ensure the independence and security of each plane and prevent traffic interference and leakage between different planes.

[0061] like Figure 2 Each network element is interconnected through an independent overlay tunnel in each forwarding plane. The CPE publishes detailed routes within its site to the POP via the BGP protocol, while the receiving center CPE publishes default routes to the POP via BGP. The default route of the primary receiving center must have a higher priority than the default route of the backup receiving center. When a branch site forwards Internet traffic to the receiving center, the Internet traffic can be directed to the forwarding plane and corresponding tunnel of receiving center A by matching the default route.

[0062] Specifically, the implementation process of S2 is as follows (e.g. Figure 3 ):

[0063] S21: For a branch site, when the primary receiving center site corresponding to its own site fails, the fault detection mechanism will trigger the default route published by the primary receiving center to become invalid.

[0064] S22: The branch CPF automatically selects the low-priority default route published by the backup receiving center, and the Internet traffic of the branch site is automatically forwarded to the CPE of the backup receiving center through the sdwan overlay tunnel;

[0065] S23: When the primary receiving center recovers from a failure, it republishes the high-priority default route. When the branch CPE detects that the high-priority default route is available, it automatically switches the Internet traffic of the branch site back to the primary receiving center exit. Seamless switching technology (such as MPLS or GRE tunnel) can be used.

[0066] In the above, the SDWAN controller and branch CPE are configured with fault detection mechanisms, such as heartbeat packet detection or path monitoring, and fault detection thresholds are set.

[0067] Specifically, the implementation process of S3 is as follows (e.g. Figure 4 ):

[0068] S31: The CPE devices of branch sites 1-5 (in actual deployment, the number of branch sites will reach tens of thousands) are configured with bandwidth monitoring modules to continuously monitor the real-time bandwidth load of the Internet between this site and the SDWAN network, and periodically and proactively send it to the SDWAN controller.

[0069] S32: Deploy a traffic monitor on the CPE of traffic receiving center A to monitor the real-time bandwidth load from the center to the Internet and periodically send the data to the SDWAN controller.

[0070] S33: Deploy a traffic monitor and a traffic scheduler on the SDWAN controller. The traffic monitor collects the internet bandwidth usage load of all branch and receiving center CPE network elements in real time.

[0071] S34: The traffic scheduler sets a line bandwidth usage threshold based on the Internet egress bandwidth of the CPE network element in the receiving center. When the real-time bandwidth exceeds the threshold, it indicates that the egress line is congested. When the real-time bandwidth exceeds the threshold value, intelligent traffic scheduling is triggered.

[0072] The steps for intelligent traffic scheduling are as follows:

[0073] S341: When receiving center A is congested, the traffic scheduler needs to first select an available receiving center as the receiver for traffic scheduling, as shown in the figure for receiving center B. The current real-time bandwidth utilization of this receiving center is the lowest and does not exceed 80% of its own congestion threshold.

[0074] S342: The traffic scheduler then calculates the total overload of the current congested receiving center A's outbound bandwidth (current receiving center real-time bandwidth - congestion threshold), collects the current forwarded Internet traffic to the branch sites of the overloaded receiving center, selects N sites from the collected branch sites, and ensures that the Internet bandwidth used by these N sites does not exceed 10% of the congestion threshold bandwidth. Then, it switches the Internet traffic of these N sites to the backup receiving center selected in step S341.

[0075] S343: Execute steps S341 and S342 every M minutes until the congestion at the closing center A is relieved;

[0076] S35: When the congestion state of receiving center A is relieved and the real-time bandwidth utilization of the receiving center is less than 80%, the SDWAN traffic scheduler can switch the Internet traffic of the branch sites that were switched away in step S34 back from receiving center B to receiving center A. In order to avoid the back-switching causing congestion in receiving center A again, the back-switching action is performed once every 5 minutes. The total real-time bandwidth of the branch sites switched back each time does not exceed the set of branch sites that are 5% of the receiving center's congestion threshold.

[0077] As a preferred embodiment of the SDWAN-based traffic convergence method described in this invention, the intelligent traffic scheduling step is as follows:

[0078] S341: When receiving center A is congested, the traffic scheduler first selects an available receiving center B as the receiver for traffic scheduling. The current real-time bandwidth utilization of receiving center B is the lowest and does not exceed 80% of its own congestion threshold.

[0079] S342: The traffic scheduler then calculates the total amount of overloaded bandwidth usage at the current congested receiving center A, collects the current forwarded Internet traffic to the branch sites of the overloaded receiving center, selects N sites from the collected branch sites, and ensures that the Internet bandwidth usage of these N sites does not exceed 10% of the congestion threshold bandwidth. Then, it switches the Internet traffic of these N sites to the backup receiving center selected in step S341.

[0080] S343: Execute steps S341 and S342 every M minutes until the congestion at the closing center A is relieved.

[0081] In summary, the traffic aggregation method provided by this invention significantly reduces deployment costs by constructing an SDWAN overlay tunnel on the Internet. Enterprise users can independently build multiple Internet aggregation points within their geographical coverage area based on SDWAN. These multiple aggregation points can simultaneously aggregate Internet traffic from branches in various locations. When one aggregation point fails, traffic can be automatically switched to other aggregation point exits. When one aggregation point exit becomes congested, traffic on the congested exit can be automatically scheduled to other aggregation point exits, thereby improving network resource utilization, ensuring global traffic optimization, and ultimately providing load balancing for multiple cross-regional Internet aggregation point exits.

[0082] The present invention also provides a system for a traffic convergence method based on SDWAN, including an SDWAN controller, a branch CPE device, and a convergence CPE device;

[0083] The SDWAN controller is responsible for policy configuration, network orchestration, traffic monitoring, and scheduling.

[0084] The branch CPE device is used to monitor and report bandwidth load and perform traffic switching;

[0085] The CPE device monitors internet bandwidth load and assists in traffic scheduling.

[0086] It should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention and are not intended to limit it. Although the present invention has been described in detail with reference to preferred embodiments, those skilled in the art should understand that modifications or equivalent substitutions can be made to the technical solutions of the present invention without departing from the spirit and scope of the technical solutions of the present invention, and all such modifications or substitutions should be covered within the scope of the claims of the present invention.

Claims

1. A traffic convergence method based on SDWAN, characterized in that, Includes the following steps: S1: Establish an independent forwarding logical plane from the branch CPE to the receiving CPE for each receiving center; The specific implementation process of S1 is as follows: S11: Create an Internet gateway strategy. The strategy parameters mainly include a primary gateway site, a backup gateway site, and several branch sites. S12: After the policy parameters are configured, the SDWAN controller will automatically orchestrate the data plane network elements CPE and POP that are bound to the receiving policy on the SDWAN network to establish a logical overlay plane; S13: If there are multiple receiving centers, multiple forwarding planes need to be built, and each forwarding plane is isolated through the router's VRF; S2: In the event of a failure of the primary receiving center, internet traffic on the branch CPE can be automatically switched to the backup receiving center; The specific implementation process of S2 is as follows: S21: For a branch site, when the primary receiving center site corresponding to its own site fails, the fault detection mechanism will trigger the default route published by the primary receiving center to become invalid. S22: The branch CPF automatically selects the low-priority default route published by the backup receiving center, and the Internet traffic of the branch site is automatically forwarded to the CPE of the backup receiving center through the sdwan overlay tunnel; S23: When the primary receiving center recovers from the failure, it republishes the high-priority default route. When the branch CPE detects that the high-priority default route is available, it automatically switches the Internet traffic of the branch site back to the primary receiving center exit. S3: When the exit point of the receiving center is congested, it can intelligently dispatch Internet traffic on that exit point to a non-congested receiving center. The specific implementation process of S3 is as follows: S31: Each branch site's CPE device is configured with a bandwidth monitoring module to continuously monitor the real-time internet bandwidth load between the site and the SDWAN network, and periodically and proactively upload the data to the SDWAN controller. S32: Deploy a traffic monitor on the CPE of traffic receiving center A to monitor the real-time bandwidth load from the center to the Internet and periodically send the data to the SDWAN controller. S33: Deploy a traffic monitor and a traffic scheduler on the SDWAN controller. The traffic monitor collects the internet bandwidth usage load of all branch and receiving center CPE network elements in real time. S34: The traffic scheduler sets a line bandwidth usage threshold based on the Internet egress bandwidth of the CPE network element in the receiving center. When the real-time bandwidth exceeds the threshold, it indicates that the egress line is congested. When the real-time bandwidth exceeds the threshold value, intelligent traffic scheduling is triggered. S35: When the congestion state of receiving center A is relieved and the real-time bandwidth load utilization of the receiving center is less than 80%, the SDWAN traffic scheduler will switch the Internet traffic of the branch sites that were switched away in step S34 back from receiving center B to receiving center A. In order to avoid the back-switching causing congestion in receiving center A again, the back-switching action is performed once every 5 minutes. The total real-time bandwidth of the branch sites switched back each time does not exceed the set of branch sites that are 5% of the receiving center congestion threshold. The intelligent traffic scheduling steps are as follows: S341: When receiving center A is congested, the traffic scheduler first selects an available receiving center B as the receiver for traffic scheduling. The current real-time bandwidth utilization of receiving center B is the lowest and does not exceed 80% of its own congestion threshold. S342: The traffic scheduler then calculates the total amount of overloaded outbound bandwidth of the current congested receiving center A, collects the current forwarded Internet traffic to the branch sites of the overloaded receiving center A, selects N sites from the collected branch sites, and the Internet bandwidth used by these N sites does not exceed 10% of the congestion threshold bandwidth. Then, the Internet traffic of these N sites is switched to the backup receiving center selected in step S341. S343: Execute steps S341 and S342 every M minutes until the congestion at the closing center A is relieved.

2. The traffic convergence method based on SDWAN as described in claim 1, characterized in that: The overlay plane is used to implement traffic forwarding from the branch CPE to the receiving CPE.

3. The traffic convergence method based on SDWAN as described in claim 1, characterized in that: When automatically switching internet traffic from branch sites back to the main receiving center exit, seamless switching technology is used.

4. The traffic convergence method based on SDWAN as described in claim 3, characterized in that: The seamless switching technology includes MPLS or GRE tunneling.

5. The traffic convergence method based on SDWAN as described in claim 1, characterized in that: Fault detection mechanisms are configured on the SDWAN controller and branch CPE.

6. The caching system of the SDWAN-based traffic caching method as described in any one of claims 1-5, characterized in that, This includes SDWAN controllers, branch CPE devices, and back-end CPE devices; The SDWAN controller is responsible for policy configuration, network orchestration, traffic monitoring, and scheduling. The branch CPE device is used to monitor and report bandwidth load and perform traffic switching; The CPE device monitors internet bandwidth load and assists in traffic scheduling.

Images