Dynamic bandwidth sharing management method based on OpenFlow

Abstract

The invention particularly relates to a dynamic bandwidth sharing management method based on OpenFlow. According to the dynamic bandwidth sharing management method based on the OpenFlow, an intranet switch guides out-of-network traffic of a virtual machine to an OpenFlow node, and it is ensured that all out-of-station traffic passes through a control platform subjected to centralized management; the OpenFlow controller monitors and analyzes the flow in real time, and limits the flow through IP matching by using a set flow table; the OpenFlow node carries out mutual conversion on the flow of the intranet and the flow of the extranet and applies a corresponding QoS strategy; and the internal network core switch sends the processed flow to the target virtual machine to realize flow control of QoS (Quality of Service). According to the dynamic bandwidth sharing management method based on OpenFlow, it can be ensured that key services obtain necessary bandwidth support, meanwhile, the operation cost of a user is reduced, the network management process is simplified, efficient sharing and cooperation of resources are promoted, the bandwidth management capacity in a cloud computing environment is improved, the elasticity and expandability of a system are enhanced, and the dynamic bandwidth sharing management method based on OpenFlow can be applied to the cloud computing environment. And ever-increasing business requirements can be met.

Description

Technical Field

[0001] The present invention relates to the field of information technology, and in particular to a dynamic bandwidth sharing management method based on OpenFlow. Background Art

[0002] With the rapid development of network technology, Internet services are becoming more and more diversified. In addition to traditional WWW, E-mail, and FTP applications, users are also trying to expand new services on the Internet, such as IP telephone, e-commerce, multimedia games, distance learning, telemedicine, videophone, video conferencing, video on demand, and online movies. Emerging corporate users also have similar demands. In addition to basic web browsing, they also need to ensure the identity authentication of internal employees and external visitors, remote video conferencing, a large number of work emails, video playback, FTP file upload and download, Telnet special equipment and other services during a relatively concentrated working period. These new services have a common feature, that is, they have special requirements for transmission performance such as bandwidth, delay, and delay jitter. For example, services such as video conferencing and video on demand require high bandwidth, low delay, and low delay jitter. Although key tasks such as transaction processing and Telnet do not necessarily require high bandwidth, they require low delay and priority processing when congestion occurs. The popularization of the network and the diversification of services have caused a surge in Internet traffic, resulting in network congestion, increased forwarding delay, and in severe cases, packet loss, resulting in reduced service quality or even unavailability. Therefore, in order to carry out these real-time services on IP networks, network congestion must be resolved. The best way to resolve network congestion is to increase network bandwidth. However, this is unrealistic in terms of operation and maintenance costs. In addition, increasing bandwidth cannot fundamentally resolve the problem and is only a temporary solution. Therefore, the most effective solution is to apply a "guaranteed" strategy to manage network congestion.

[0003] In today's rapidly developing cloud computing environment, more and more enterprises and individual users rely on virtual machines (VMs) and other computing resources provided by cloud service providers. Users usually deploy multiple virtual machines according to different business needs to handle various application scenarios. However, in actual use, the bandwidth requirements of these virtual machines often show dynamic characteristics. Traditional bandwidth allocation strategies usually allocate a fixed bandwidth limit to each virtual machine, which may lead to insufficient bandwidth during peak traffic periods, thereby affecting transmission quality, causing packet loss and retransmission, and affecting user experience.

[0004] For example, a user may run three virtual machines at the same time, each with 200M bandwidth, which seems sufficient under normal circumstances. However, during peak hours, the traffic of these three virtual machines may surge at the same time, causing the actual bandwidth demand to exceed 600M, resulting in a performance bottleneck. This fixed bandwidth limit not only leads to inefficient resource utilization, but may also cause users to face additional cost expenditures.

[0005] Based on the above situation, the present invention proposes a dynamic bandwidth sharing management method based on OpenFlow. Summary of the invention

[0006] In order to overcome the defects of the prior art, the present invention provides a simple and efficient OpenFlow-based dynamic bandwidth sharing management method.

[0007] The present invention is achieved through the following technical solutions:

[0008] A dynamic bandwidth sharing management method based on OpenFlow, comprising the following steps:

[0009] Step S1: Intranet switch directs traffic

[0010] Direct the outbound traffic of the virtual machine (VM) to the OpenFlow node through the intranet switch, ensuring that all outbound traffic passes through the centrally managed control platform, thereby enabling traffic monitoring and management;

[0011] Step S2: Traffic enters the OpenFlow controller

[0012] Traffic enters the OpenFlow controller through the Ingress port. During this process, the OpenFlow controller monitors and analyzes the traffic in real time for subsequent traffic control and QoS policy application.

[0013] Step S3: Use flow table to limit current

[0014] The OpenFlow controller uses the set flow table to limit the traffic through IP matching;

[0015] Step S4: Traffic conversion

[0016] OpenFlow nodes convert traffic between the intranet and the extranet to ensure smooth transmission of traffic in different network environments and apply corresponding QoS policies;

[0017] Step S5: The intranet core switch sends traffic

[0018] The intranet core switch sends the processed traffic to the target virtual machine to implement QoS traffic control.

[0019] In step S3, the flow table matches a specific IP address and port according to the QoS policy predefined by the user, and controls the traffic within the set bandwidth range to ensure that the allocated resources are not exceeded.

[0020] In step S3, the OpenFlow controller creates a corresponding flow table according to user needs, defines the forwarding path and rules of the traffic, creates a meter table for traffic rate limiting, modifies the flow table to use the custom specified meter table, and ensures that the traffic is first processed by rate limiting before forwarding.

[0021] A dynamic bandwidth sharing management system based on OpenFlow, comprising:

[0022] The northbound interface is responsible for providing a series of RESTful interfaces to the cloud computing management platform or third-party platform, supporting users to create, modify, delete and view custom policy routes; these interfaces provide the basis for the flexibility and scalability of the system, allowing users to easily manage QoS policies.

[0023] The database is used to record the shared QoS information created by users based on virtual machine multi-ports, including the configuration and status of all QoS policies, to ensure that the system can maintain consistency and traceability in a dynamically changing network environment;

[0024] The shared QoS management module is responsible for the creation, modification, and deletion of shared QoS policies and the specific operations of binding QoS to virtual machines;

[0025] The virtual network L2 management module is responsible for sending QoS policies to the underlying flow table to implement rate limiting based on the OpenFlow flow table.

[0026] The shared QoS management module calls the relevant interface of the virtual network L2 management module to implement the flow rate limit of the data plane, thereby ensuring the stability and security of the virtual machine when sharing the bandwidth.

[0027] The virtual network L2 management module is also responsible for monitoring changes in bound QoS policies and the increase or decrease of multiple ports of virtual machines, ensuring the flexibility of the system in a dynamic environment.

[0028] A dynamic bandwidth sharing management device based on OpenFlow, characterized in that it comprises a memory and a processor; the memory is used to store a computer program, and the processor is used to implement the above method steps when executing the computer program.

[0029] A readable storage medium, characterized in that: a computer program is stored on the readable storage medium, and the computer program implements the above method steps when executed by a processor.

[0030] The beneficial effects of the present invention are as follows: the dynamic bandwidth sharing management method based on OpenFlow can ensure that key businesses obtain the necessary bandwidth support, while reducing the user's operating costs, simplifying the network management process, and promoting efficient sharing and collaboration of resources. It not only improves the bandwidth management capability in the cloud computing environment, but also enhances the elasticity and scalability of the system, and can meet the growing business needs. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0032] Attached Figure 1 It is a schematic diagram of the dynamic bandwidth sharing management method based on OpenFlow of the present invention. DETAILED DESCRIPTION

[0033] In order to enable those skilled in the art to better understand the technical solutions in the present invention, the technical solutions in the embodiments of the present invention will be clearly and completely described below in conjunction with the embodiments of the present invention. Obviously, the described embodiments are only a part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of the present invention.

[0034] As an emerging network control protocol, OpenFlow provides the ability to achieve flexible traffic management through software-defined networks (SDN), and can monitor and control traffic through meter tables, thus providing a technical basis for dynamic bandwidth sharing. Therefore, developing a bandwidth sharing management method for cloud computing environments based on OpenFlow's meter table can effectively improve bandwidth utilization, improve network transmission quality, and reduce users' operating costs, which is an important direction of current technological development.

[0035] QoS technology was developed in this context. QoS is the abbreviation of Quality of Service, and its purpose is to provide end-to-end service quality assurance for various services according to their different needs. QoS technology is increasingly used in today's Internet, and its role is becoming more and more important. Without QoS technology, the service quality of the service cannot be guaranteed. Shared network Qos means that multiple network cards of the same virtual machine or multiple network cards of multiple virtual machines share the same bandwidth limit.

[0036] The OpenFlow-based dynamic bandwidth sharing management method comprises the following steps:

[0037] Step S1: Intranet switch directs traffic

[0038] Direct the outbound traffic of the virtual machine (VM) to the OpenFlow node through the intranet switch, ensuring that all outbound traffic passes through the centrally managed control platform, thereby enabling traffic monitoring and management;

[0039] Step S2: Traffic enters the OpenFlow controller

[0040] Traffic enters the OpenFlow controller through the Ingress port. During this process, the OpenFlow controller monitors and analyzes the traffic in real time for subsequent traffic control and QoS policy application.

[0041] Step S3: Use flow table to limit current

[0042] The OpenFlow controller uses the set flow table to limit the traffic through IP matching;

[0043] Step S4: Traffic conversion

[0044] OpenFlow nodes convert traffic between the intranet and the extranet to ensure smooth transmission of traffic in different network environments and apply corresponding QoS policies;

[0045] Step S5: The intranet core switch sends traffic

[0046] The intranet core switch sends the processed traffic to the target virtual machine to implement QoS traffic control.

[0047] This process ensures reasonable traffic scheduling between virtual machines and avoids performance degradation due to insufficient bandwidth.

[0048] In step S3, the flow table matches a specific IP address and port according to the QoS policy predefined by the user, and controls the traffic within the set bandwidth range to ensure that the allocated resources are not exceeded.

[0049] In step S3, the OpenFlow controller creates a corresponding flow table according to user needs, defines the forwarding path and rules of the traffic, creates a meter table for traffic rate limiting, modifies the flow table to use the custom specified meter table, and ensures that the traffic is first processed by rate limiting before forwarding.

[0050] For example, when the flow table on the switch is set to forward the traffic coming from port 1 to port 2, the configuration is in_port = 1, actions = output: 2.

[0051] For example, traffic exceeding 10M will be dropped. The meter table configuration is meter=1, type=drop, rate=10000.

[0052] Modify the flow table and configure it as in_port = 1, actions = meter: 1, output: 2 to ensure that the traffic is rate-limited before it is forwarded.

[0053] When traffic enters the switch from port 1, the traffic will be directed to the corresponding processing path based on the settings of the flow table.

[0054] Before the traffic is forwarded to port 2, it will be processed by the meter table, and the traffic exceeding the set rate will be discarded. This mechanism effectively prevents network congestion and excessive consumption of resources.

[0055] The processed traffic is finally forwarded to the target port to achieve traffic control and QoS guarantee.

[0056] The OpenFlow-based dynamic bandwidth sharing management system includes:

[0057] The northbound interface is responsible for providing a series of RESTful interfaces to the cloud computing management platform or third-party platform, supporting users to create, modify, delete and view custom policy routes; these interfaces provide the basis for the flexibility and scalability of the system, allowing users to easily manage QoS policies.

[0058] The database is used to record the shared QoS information created by users based on virtual machine multi-ports, including the configuration and status of all QoS policies, to ensure that the system can maintain consistency and traceability in a dynamically changing network environment;

[0059] The shared QoS management module is responsible for the creation, modification, and deletion of shared QoS policies and the specific operations of binding QoS to virtual machines;

[0060] The virtual network L2 management module is responsible for sending QoS policies to the underlying flow table to implement rate limiting based on the OpenFlow flow table.

[0061] The shared QoS management module calls the relevant interface of the virtual network L2 management module to implement the flow rate limit of the data plane, thereby ensuring the stability and security of the virtual machine when sharing the bandwidth.

[0062] The virtual network L2 management module is also responsible for monitoring changes in bound QoS policies and the increase or decrease of multiple ports of virtual machines, ensuring the flexibility of the system in a dynamic environment.

[0063] The OpenFlow-based dynamic bandwidth sharing management device includes a memory and a processor; the memory is used to store a computer program, and the processor is used to implement the above method steps when executing the computer program.

[0064] The readable storage medium stores a computer program, and when the computer program is executed by a processor, the above method steps are implemented.

[0065] This OpenFlow-based dynamic bandwidth sharing management method, combined with the flexibility and programmability of OpenFlow, provides an effective QoS management method that can adapt to the bandwidth requirements and resource management challenges in modern cloud computing environments. Through refined traffic control and dynamic bandwidth sharing mechanisms, users can ensure the stability and reliability of their services while making efficient use of resources, thereby promoting the efficient deployment and operation of private clouds.

[0066] Compared with the existing technology, it has the following characteristics:

[0067] 1) Optimize bandwidth utilization

[0068] Through the dynamic bandwidth sharing mechanism, the bandwidth between multiple virtual machines is effectively allocated, the overall bandwidth utilization efficiency is improved, and resource idleness is avoided.

[0069] 2) Improve network transmission quality

[0070] The system significantly reduces network congestion, packet loss and retransmission through real-time traffic monitoring and the application of QoS strategies, thereby ensuring the stability and reliability of data transmission.

[0071] 3) Reduce operating costs

[0072] Users do not need to rely on expensive third-party hardware firewalls for QoS management, which reduces infrastructure investment and maintenance costs. At the same time, shared bandwidth reduces the need to purchase additional bandwidth.

[0073] 4) Flexibly respond to traffic fluctuations

[0074] The system can monitor traffic changes in real time and dynamically adjust bandwidth allocation to ensure that business needs can be met even during peak traffic periods, thereby ensuring service continuity.

[0075] 5) Refined management capabilities

[0076] Tenants can flexibly configure QoS policies according to specific needs, achieve refined management of bandwidth, and support specific traffic control in different application scenarios.

[0077] 6) Simplified network management

[0078] Through centralized management and automated QoS policy configuration, the management process of network resources is simplified, operation and maintenance efficiency is improved, and the need for manual intervention is reduced.

[0079] 7) Enhanced system flexibility

[0080] When faced with burst traffic, the system can respond quickly and adjust bandwidth resource allocation, enhancing the overall network's resilience and stress resistance.

[0081] 8) Support multiple application scenarios

[0082] This system is applicable to a variety of cloud computing environments and application scenarios, such as containerized deployment, large-scale data processing, and online services, providing a wider range of application support.

[0083] 9) Improve user satisfaction

[0084] By ensuring traffic stability and reducing packet loss rates, the system improves user experience and satisfaction, and enhances user trust and reliance on the service.

[0085] 10) Promote resource sharing and collaboration

[0086] It encourages users to make rational use of shared resources, promotes resource sharing and collaboration among different tenants in the cloud environment, and achieves more efficient resource utilization.

[0087] 11) Traffic policing, traffic shaping and interface speed limiting

[0088] Traffic policing and traffic shaping can limit service traffic to a specific bandwidth. When the service traffic exceeds the rated bandwidth, the excess traffic will be discarded or cached. The technology of discarding the excess traffic is called traffic policing, and the technology of caching the excess traffic is called traffic shaping. Interface rate limiting is divided into interface-based traffic policing and interface-based traffic shaping.

[0089] 12) Congestion management and congestion avoidance

[0090] Congestion management puts packets into a queue for buffering when network congestion occurs, and uses a scheduling algorithm to arrange the forwarding order of packets. Congestion avoidance can monitor the use of network resources, and when congestion is found to be increasing, it will actively discard packets and relieve network overload by adjusting traffic.

[0091] 13) Multiple network cards share QoS to make more efficient use of bandwidth. In most cases, the traffic of multiple network cards is not always at its peak at the same time. Sharing bandwidth by multiple network cards means that a single network card can achieve the same bandwidth as that which could be purchased at the same price during peak traffic periods.

[0092] The embodiment described above is only one specific implementation of the present invention. Common changes and substitutions made by those skilled in the art within the scope of the technical solution of the present invention should be included in the protection scope of the present invention.

Claims

1. A dynamic bandwidth sharing management method based on OpenFlow, characterized in that: The following steps are involved: Step S1: Intranet switch directs traffic The outbound traffic of the virtual machine is directed to the OpenFlow node through the intranet switch to ensure that all outbound traffic passes through the centrally managed control platform, thereby realizing traffic monitoring and management; Step S2: Traffic enters the OpenFlow controller Traffic enters the OpenFlow controller through the Ingress port; During this process, the OpenFlow controller monitors and analyzes traffic in real time for subsequent traffic control and QoS policy application; Step S3: Use flow table to limit current The OpenFlow controller uses the set flow table to limit the traffic through IP matching; Step S4: Traffic conversion OpenFlow nodes convert traffic between the intranet and the extranet to ensure smooth transmission of traffic in different network environments and apply corresponding QoS policies; Step S5: Intranet core switch sends traffic The intranet core switch sends the processed traffic to the target virtual machine to implement QoS traffic control.

2. The OpenFlow-based dynamic bandwidth sharing management method according to claim 1, characterized in that: In step S3, the flow table matches a specific IP address and port according to the QoS policy predefined by the user, and controls the traffic within the set bandwidth range to ensure that the allocated resources are not exceeded.

3. The OpenFlow-based dynamic bandwidth sharing management method according to claim 2, characterized in that: In step S3, the OpenFlow controller creates a corresponding flow table according to user needs, defines the forwarding path and rules of the traffic, creates a meter table for traffic rate limiting, modifies the flow table to use the custom specified meter table, and ensures that the traffic is first processed by rate limiting before forwarding.

4. A system based on the OpenFlow-based dynamic bandwidth sharing management method according to any one of claims 1 to 7, characterized in that: include: The northbound interface is responsible for providing a series of RESTful interfaces to the cloud computing management platform or third-party platform, supporting users to create, modify, delete and view custom policy routes so that users can manage QoS policies. The database is used to record the shared QoS information created by users based on virtual machine multi-ports, including the configuration and status of all QoS policies, to ensure that the system can maintain consistency and traceability in a dynamically changing network environment; The shared QoS management module is responsible for the creation, modification, and deletion of shared QoS policies and the specific operations of binding QoS to virtual machines; The virtual network L2 management module is responsible for sending QoS policies to the underlying flow table to implement rate limiting based on the OpenFlow flow table.

5. The OpenFlow-based dynamic bandwidth sharing management system according to claim 4, characterized in that: The shared QoS management module calls the relevant interface of the virtual network L2 management module to implement the flow rate limit of the data plane, thereby ensuring the stability and security of the virtual machine when sharing the bandwidth.

6. The OpenFlow-based dynamic bandwidth sharing management system according to claim 4, characterized in that: The virtual network L2 management module is also responsible for monitoring changes in bound QoS policies and the increase or decrease of multiple ports of virtual machines, ensuring the flexibility of the system in a dynamic environment.

7. A dynamic bandwidth sharing management device based on OpenFlow, characterized in that: The method comprises a memory and a processor; the memory is used to store a computer program, and the processor is used to implement the method according to any one of claims 1 to 3 when executing the computer program.

8. A readable storage medium, characterized in that: The 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 3 is implemented.

Images