CN110601989A - Network traffic balancing method and device - Google Patents
Network traffic balancing method and device Download PDFInfo
- Publication number
- CN110601989A CN110601989A CN201910906022.7A CN201910906022A CN110601989A CN 110601989 A CN110601989 A CN 110601989A CN 201910906022 A CN201910906022 A CN 201910906022A CN 110601989 A CN110601989 A CN 110601989A
- Authority
- CN
- China
- Prior art keywords
- ipv6
- flow
- traffic
- ipv4
- scheduling
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Withdrawn
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/10—Flow control; Congestion control
- H04L47/12—Avoiding congestion; Recovering from congestion
- H04L47/125—Avoiding congestion; Recovering from congestion by balancing the load, e.g. traffic engineering
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/10—Flow control; Congestion control
- H04L47/29—Flow control; Congestion control using a combination of thresholds
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/10—Flow control; Congestion control
- H04L47/32—Flow control; Congestion control by discarding or delaying data units, e.g. packets or frames
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/50—Queue scheduling
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/45—Network directories; Name-to-address mapping
- H04L61/4505—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols
- H04L61/4511—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols using domain name system [DNS]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L2101/00—Indexing scheme associated with group H04L61/00
- H04L2101/60—Types of network addresses
- H04L2101/686—Types of network addresses using dual-stack hosts, e.g. in Internet protocol version 4 [IPv4]/Internet protocol version 6 [IPv6] networks
Abstract
The invention discloses a network flow balancing method and a device, wherein the method comprises the following steps: acquiring IPv6 flow bandwidth data of an outlet link of the connected switching equipment according to a preset period; judging whether the IPv6 traffic bandwidth data of the link is larger than a preset upper limit scheduling threshold, and if so, issuing a preset traffic strategy to the switching equipment to enable the switching equipment to perform traffic scheduling according to the traffic strategy; and judging whether the IPv6 traffic bandwidth data of the link is smaller than a preset lower limit scheduling threshold, and if so, issuing a traffic strategy deleting instruction to the switching equipment to enable the switching equipment to stop traffic scheduling. The network traffic balancing method and device provided by the embodiment of the invention can solve the problem of poor experience caused by IPv6 congestion access of a dual-stack terminal in the prior art.
Description
Technical Field
The present invention relates to the field of communications technologies, and in particular, to a method and an apparatus for network traffic balancing.
Background
Internet Protocol Version 6 (IPv 6) is The next generation Internet Protocol (IP) designed by The Internet Engineering Task Force (IETF) to replace IPv4, and The number of addresses can be called to code an address for each sand worldwide. Since the biggest problem of the IPv4 is that network address resources are limited, the application and development of the internet are severely restricted. The use of the IPv6 can not only solve the problem of the number of network address resources, but also solve the obstacle of connecting various access devices to the Internet, so that the interconnection of everything becomes possible.
Since IPv6 cannot immediately replace IPv4, IPv4 and IPv6 coexist in one environment for a considerable period of time. The IPv4/IPv6 dual stack technology is a solution for the transition period. The dual stack mechanism is that the network node has both an IPv4 protocol stack and an IPv6 protocol stack, and supports both IPv4 and IPv6 protocols. IPv4 and IPv6 are network layer protocols with similar functions, both of which are applied to the same physical platform and carry the same transport layer protocol, and if one host supports both IPv6 and IPv4 protocols, the host supports either IPv4 or IPv6 protocol for communication.
According to the definition of Request For Comments (RFC) 4213, a dual stack refers to a network node on which both IPv4 and IPv6 protocol stacks are installed, so as to implement information intercommunication with IPv4 or IPv6 network nodes, respectively, a node having an IPv4/IPv6 dual protocol stack is referred to as a "dual stack node", and these nodes can receive and transmit an IPv4 message and an IPv6 message, and they can use an IPv4 address to intercommunicate with an IPv4 node and can use an IPv6 address to intercommunicate with an IPv6 node.
The dual stack network architecture allows devices to receive, process and forward IPv4/IPv6 information streams, and network devices supporting both IPv4 and IPv6 stacks to allow the network to logically see both networks in parallel. And supports a smooth transition from an IPv4 network to an IPv6 network. Therefore, the dual stack mechanism is the most direct way to make the IPv4 node and the IPv6 node coexist and interwork and be compatible.
The dual stack is used as a main technology for the transition period of the IPv4 network to the IPv6 network, when a dual stack host accesses network resources, an IPv6 address is preferentially used for requesting to access the DNS server of the IPv6, and the DNS server response of the IPv6 must include an AAAA address (namely the corresponding relation between the domain name and the IPv6 address). If no AAAA address exists, the IPv4 address is reused to request access to the DNS server of IPv 4.
According to the RFC, when the dual-stack host accesses the DNS, the IPv6 address is preferentially used for requesting to access the IPv6 DNS server, and the response of the IPv6 DNS server must include the AAAA address (namely the corresponding relation between the domain name and the IPv6 address). If there is no AAAA address, IPv4 is reused to request DNS server of IPv 4. For a dual-stack host, the DNS request of IPv4 sends two DNS query messages, one is an AAAA query request, and the other is an a query request. If the DNS server of IPv4 returns AAAA inquiry response, namely IPv6 connection can be normally established, the server is accessed by preferentially using IPv6 address, and the established IPv4 connection is reset. If there is no AAAA query response, i.e. the IPv6 connection setup fails, and there is a query response received, the terminal will instead use the IPv4 address to set up a connection to access the resource.
Limited to the current seire network, the cost of the outlet of IPV6 is 5-10 times higher than that of the outlet of IPV4, and usually many colleges and enterprises deploy the outlet of IPV6 and the outlet of IPV4 at the same time, while the outlet bandwidth of IPV6 is usually smaller, so that in the successive service modification of each service provider, more and more applications and network resources supporting IPV6 are provided, and most schools directly direct the route access of IPV6 to the education network, which may cause the outlet traffic of the campus network to be directly exploded in a short period, which affects the user experience, and even affects part of important IPV6 services to be inaccessible through IPV 6.
The behavior of the dual-stack terminal client is IPv6 priority access, when all dual-stack terminals access the network by preferentially using IPv6 connection at the same time, service can be returned to IPv4 when congestion and packet loss occur, so that the return waiting time is caused, and the network access experience of the dual-stack terminals is influenced. Therefore, the problem of how to guarantee the IPv6 access user experience of the dual-stack terminal under the condition of improving the IPv6 exit bandwidth utilization rate needs to be solved urgently.
Disclosure of Invention
The embodiment of the invention provides a network flow balancing method, which is used for solving the problem of poor experience caused by IPv6 congestion access of a dual-stack terminal in the prior art.
The embodiment of the invention provides a network flow balancing method, which is applied to a Software Defined Network (SDN) controller and comprises the following steps:
acquiring IPv6 flow bandwidth data of an outlet link of the connected switching equipment according to a preset period;
judging whether the IPv6 traffic bandwidth data of the link is larger than a preset upper limit scheduling threshold, and if so, issuing a preset traffic strategy to the switching equipment to enable the switching equipment to perform traffic scheduling according to the traffic strategy;
and judging whether the IPv6 traffic bandwidth data of the link is smaller than a preset lower limit scheduling threshold, and if so, issuing a traffic strategy deleting instruction to the switching equipment to enable the switching equipment to stop traffic scheduling.
Wherein, the issuing a preset traffic policy to the switching device includes:
issuing a preset flow control table to the switching equipment so that the switching equipment forwards the message corresponding to the IPv4 network segment needing flow scheduling according to the forwarding strategy of the flow control table; the flow control table comprises a gateway ID, a forwarding strategy and an IPv4 network segment needing flow scheduling; the switching equipment is the switching equipment corresponding to the IPv4 network segment needing traffic scheduling.
Wherein the lower flow threshold is less than the upper flow threshold.
The embodiment of the invention also provides a network flow balancing method, which is applied to the switching equipment and comprises the following steps:
collecting and sending IPv6 traffic bandwidth data of an exit link for an SDN controller to issue an instruction according to the IPv6 traffic bandwidth data;
when a flow strategy issued by the SDN controller is received, chip hardware of the OpenFlow flow table is installed according to a pre-stored network segment mapping relation;
judging whether the received IPv6 message from the dual-stack terminal hits the OpenFlow flow table or not, if yes, forwarding the IPv6 message to a Central Processing Unit (CPU) of the switching equipment for discarding;
and when a flow strategy deleting instruction issued by the SDN controller is received, deleting the OpenFlow flow table installed on the chip hardware.
When receiving a flow policy issued by the SDN controller as a flow control flow table, the chip hardware installation of the OpenFlow flow table performed according to the pre-stored network segment mapping relationship includes:
determining a corresponding pre-stored network segment mapping relation according to the gateway ID in the flow control flow table;
determining an IPv6 network segment corresponding to the IPv4 network segment needing flow scheduling according to the network segment mapping relation and the IPv4 network segment needing flow scheduling in the flow control flow table;
determining an action for processing an IPv4 message and an action for processing an IPv6 message according to a forwarding strategy in the flow control table;
obtaining and storing OpenFlow flow tables comprising gateway IDs, actions of processing IPv4 messages, actions of processing IPv6 messages, IPv4 network segments and corresponding IPv6 network segments; the action of processing the IPv4 message is normal forwarding, and the action of processing the IPv6 message is forwarding to the CPU for discarding.
Wherein the determining whether the received IPv6 packet hits in the OpenFlow flow table includes:
and acquiring whether a destination IP address of the received IPv6 message belongs to an IPv6 network segment in the OpenFlow flow table, and if so, determining that the IPv6 message hits the OpenFlow flow table.
After forwarding the IPv6 packet to a central processing unit CPU of the switching device for discarding, the method further includes:
and when the discarded IPv6 message is an IPv6 domain name resolution DNS message, forging an invalid IPv6 DNS response message and sending the invalid IPv6 DNS response message to the dual-stack terminal so that the dual-stack terminal starts IPv4 connection.
The embodiment of the present invention further provides a network traffic balancing device, which is applied to a software defined network SDN controller, and includes: the device comprises an acquisition unit, a judgment unit and a sending unit; wherein the content of the first and second substances,
the acquiring unit is used for acquiring IPv6 traffic bandwidth data of an exit link of the connected switching equipment according to a preset period;
the judging unit is used for judging whether the IPv6 traffic bandwidth data of the link is greater than a preset upper limit scheduling threshold value; the method is also used for judging whether the IPv6 flow bandwidth data of the link is smaller than a preset lower limit scheduling threshold value;
the sending unit is configured to, when the IPv6 traffic of the link bandwidth data is greater than a preset upper scheduling threshold, issue a preset traffic policy to the switching device so that the switching device performs traffic scheduling according to the traffic policy; and when the IPv6 traffic of the link bandwidth data is smaller than a preset lower scheduling threshold, issuing a traffic policy deletion instruction to the switching device to cause the switching device to stop traffic scheduling.
The sending unit is specifically configured to issue a preset flow control table to the switching device, so that the switching device forwards a packet corresponding to an IPv4 network segment requiring flow scheduling according to a forwarding policy of the flow control table; the flow control table comprises a gateway ID, a forwarding strategy and an IPv4 network segment needing flow scheduling; the switching equipment is the switching equipment corresponding to the IPv4 network segment needing traffic scheduling.
Wherein the lower flow threshold is less than the upper flow threshold.
The embodiment of the present invention further provides a network traffic balancing apparatus, where the apparatus is applied to a switching device, and the apparatus includes: the system comprises an acquisition unit, a flow table unit, a matching unit and a processing unit; wherein the content of the first and second substances,
the acquisition unit is used for acquiring and sending IPv6 traffic bandwidth data of an egress link to allow an SDN controller to issue an instruction according to the IPv6 traffic bandwidth data;
the flow table unit is used for installing chip hardware of the OpenFlow flow table according to a pre-stored network segment mapping relation when receiving a flow strategy issued by the SDN controller; the flow table management module is further used for deleting the OpenFlow flow table installed on the chip hardware when a flow strategy deleting instruction issued by the SDN controller is received;
the matching unit is used for judging whether the received IPv6 message from the dual-stack terminal hits the OpenFlow flow table or not;
and the processing unit is configured to forward the IPv6 packet to a central processing unit CPU of the switch device for discarding when the IPv6 packet hits the OpenFlow flow table.
The flow table unit is specifically configured to, when receiving that a flow policy issued by an SDN controller is a flow control flow table, determine a corresponding pre-stored network segment mapping relationship according to a gateway ID in the flow control flow table; determining an IPv6 network segment corresponding to the IPv4 network segment needing flow scheduling according to the network segment mapping relation and the IPv4 network segment needing flow scheduling in the flow control flow table; determining actions for processing IPv4 messages and actions for processing IPv6 messages according to the forwarding strategy in the flow control table; obtaining and storing OpenFlow flow tables comprising gateway IDs, actions of processing IPv4 messages, actions of processing IPv6 messages, IPv4 network segments and corresponding IPv6 network segments; the action of processing the IPv4 message is normal forwarding, and the action of processing the IPv6 message is forwarding to the CPU for discarding.
The matching unit is specifically configured to obtain whether a destination IP address of the received IPv6 message belongs to an IPv6 network segment in the OpenFlow flow table, and if so, determine that the IPv6 message hits the OpenFlow table.
The processing unit is further configured to forge an invalid IPv6 DNS reply message to the dual stack terminal when the discarded IPv6 message is an IPv6 domain name resolution DNS message, so that the dual stack terminal starts IPv4 connection.
The invention has the following beneficial effects:
according to the network traffic balancing method and device provided by the embodiment of the invention, whether traffic scheduling is carried out is determined by acquiring IPv6 traffic bandwidth data of an outlet link of the switching equipment according to the relation between IPv6 traffic bandwidth and a preset scheduling threshold, so that IPv4/IPv6 access switching of the dual-stack terminal is realized. The network flow balancing method and the device provided by the embodiment of the invention can ensure that the problem of poor access experience of the terminal IPv6 caused by insufficient IPv6 bandwidth is avoided under the condition of fully utilizing the IPv6 bandwidth of the outlet; and the SDN controller schedules flow as required, so that the IPv6 service access of an important service network segment is not influenced, and the user experience is greatly improved.
Drawings
Fig. 1 is a flowchart of a network traffic balancing method according to an embodiment of the present invention;
FIG. 2 is a flow chart of another implementation of a network traffic balancing method according to an embodiment of the present invention;
fig. 3 is a schematic structural diagram of a network traffic balancing apparatus according to an embodiment of the present invention;
fig. 4 is another schematic structural diagram of a network traffic balancing apparatus according to an embodiment of the present invention.
Detailed Description
Aiming at the problem of poor experience caused by IPv6 congestion access of a dual-stack terminal in the prior art, the network traffic balancing method provided by the embodiment of the invention determines whether to perform traffic scheduling or not by acquiring the data of the exit link IPv6 traffic bandwidth of the switching equipment and comparing the IPv6 traffic bandwidth with a preset threshold value, and switches the dual-stack terminal between IPv6 and IPv4 so as to improve the bandwidth utilization rate and improve the user experience. The flow of the method of the present invention is shown in fig. 1, and is applied to an SDN controller, and the method comprises the following steps:
step 101, acquiring IPv6 traffic bandwidth data of an exit link of a connected switching device according to a preset period;
step 102, judging whether the IPv6 traffic bandwidth data of the link is greater than a preset upper limit scheduling threshold, and if so, issuing a preset traffic policy to the switching device to enable the switching device to perform traffic scheduling according to the traffic policy;
here, when the IPv6 traffic bandwidth data is greater than the preset online scheduling threshold, it indicates that the IPv6 bandwidth resource utilization rate of the current link is too high, and traffic scheduling is required, and it should be reduced that the dual stack terminal connects to the network through the IPv6 protocol.
Step 103, judging whether the IPv6 traffic bandwidth data of the link is smaller than a preset lower limit scheduling threshold, and if so, issuing a traffic policy deletion instruction to the switching device to stop traffic scheduling of the switching device.
Here, when the IPv6 traffic bandwidth data is smaller than the preset lower scheduling threshold, it indicates that the IPv6 bandwidth resource utilization of the current link is low, and traffic scheduling is required, and a dual stack terminal should be added to connect to the network through the IPv6 protocol.
Wherein, the issuing a preset traffic policy to the switching device includes:
issuing a preset flow control table to the switching equipment so that the switching equipment forwards the message corresponding to the IPv4 network segment needing flow scheduling according to the forwarding strategy of the flow control table; the flow control table comprises a gateway ID, a forwarding strategy and an IPv4 network segment needing flow scheduling; the switching equipment is the switching equipment corresponding to the IPv4 network segment needing traffic scheduling. The gateway ID refers to a gateway corresponding to the IPv4 network segment requiring traffic scheduling.
Wherein the lower flow threshold is less than the upper flow threshold.
An embodiment of the present invention further provides a network traffic balancing method, where the method is applied to a switching device, and as shown in fig. 2, the execution steps include:
step 201, collecting and sending IPv6 traffic bandwidth data of an egress link for an SDN controller to issue an instruction according to the IPv6 traffic bandwidth data;
here, the switching device may collect and transmit IPv6 traffic bandwidth data of the egress link by setting a simple network management protocol information management base (SNMP MIB) node.
Step 202, when receiving a flow strategy issued by the SDN controller, installing chip hardware of an OpenFlow flow table according to a pre-stored network segment mapping relation;
the switching equipment determines the mapping relation between the IPv4 network segment and the IPv6 network segment which need to be scheduled according to the gateway ID in the flow strategy, then determines an OpenFlow flow table according to the mapping relation, and installs chip hardware
Step 203, judging whether the received IPv6 message from the dual stack terminal hits the OpenFlow flow table, and if so, forwarding the IPv6 message to a central processing unit CPU of the switching device for discarding;
further, when the received IPv6 message misses in the OpenFlow flow table, the message is still forwarded according to the existing message forwarding protocol.
And 204, deleting the OpenFlow flow table installed on the chip hardware when a flow strategy deleting instruction issued by the SDN controller is received.
When receiving a flow policy issued by the SDN controller as a flow control flow table, the chip hardware installation of the OpenFlow flow table is performed according to a pre-stored network segment mapping relationship, including:
determining a corresponding pre-stored network segment mapping relation according to the gateway ID in the flow control flow table;
determining an IPv6 network segment corresponding to the IPv4 network segment needing flow scheduling according to the network segment mapping relation and the IPv4 network segment needing flow scheduling in the flow control flow table;
determining an action for processing an IPv4 message and an action for processing an IPv6 message according to a forwarding strategy in the flow control table;
obtaining and storing OpenFlow flow tables comprising gateway IDs, actions of processing IPv4 messages, actions of processing IPv6 messages, IPv4 network segments and corresponding IPv6 network segments; the action of processing the IPv4 message is normal forwarding, and the action of processing the IPv6 message is forwarding to the CPU for discarding.
Further, the OpenFlow flow table entry may include a number, a gateway, an IPv4 segment, an IPv6 segment, an action of processing an IPv4 message, an action of processing an IPv6 message, and the like, and the following is an OpenFlow flow table example, but is not limited to this:
wherein the determining whether the received IPv6 packet hits in the OpenFlow flow table includes:
and acquiring whether a destination IP address of the received IPv6 message belongs to an IPv6 network segment in the OpenFlow flow table, and if so, determining that the IPv6 message hits the OpenFlow flow table.
Further, after forwarding the IPv6 packet to the central processing unit CPU of the switch device for discarding, the method further includes:
when the discarded IPv6 message is a Domain name resolution (DNS) message of IPv6, sending an invalid IPv6 DNS reply message to the dual stack terminal, so that the dual stack terminal starts IPv4 connection. Here, after receiving the invalid IPv6 response message, the dual-stack terminal cannot analyze normally, and determines that the IPv6 network is unavailable, the dual-stack terminal will quickly start an IPv4 protocol stack service, and quickly establish a network connection with an external network through an IPv4 address to access the network (default behavior of a network client). Thereby completing the switch from the IPv6 connection to the IPv4 connection. Switching from IPv6 traffic access to IPv4 traffic access reduces the IPv6 bandwidth of the egress link of the switching device, such that the IPv6 bandwidth of the egress link of the switching device is no longer congested.
Based on the same inventive concept, an embodiment of the present invention provides a network traffic balancing apparatus, where the apparatus is applied to a software defined network SDN controller, and a structure of the apparatus is shown in fig. 3, where the apparatus includes: an acquisition unit 31, a judgment unit 32, and a transmission unit 33; wherein the content of the first and second substances,
the acquiring unit 31 is configured to acquire IPv6 traffic bandwidth data of an egress link of a connected switching device according to a preset period;
the determining unit 32 is configured to determine whether the IPv6 traffic bandwidth data of the link is greater than a preset upper scheduling threshold; the method is also used for judging whether the IPv6 flow bandwidth data of the link is smaller than a preset lower limit scheduling threshold value;
the sending unit 33 is configured to, when the IPv6 traffic of the link bandwidth data is greater than a preset upper scheduling threshold, issue a preset traffic policy to the switching device so that the switching device performs traffic scheduling according to the traffic policy; and when the IPv6 traffic of the link bandwidth data is smaller than a preset lower scheduling threshold, issuing a traffic policy deletion instruction to the switching device to cause the switching device to stop traffic scheduling.
The sending unit 33 is specifically configured to issue a preset flow control table to the switching device, so that the switching device forwards a packet corresponding to an IPv4 network segment requiring flow scheduling according to a forwarding policy of the flow control table; the flow control table comprises a gateway ID, a forwarding strategy and an IPv4 network segment needing flow scheduling; the switching equipment is the switching equipment corresponding to the IPv4 network segment needing traffic scheduling.
Preferably, the lower flow threshold is less than the upper flow threshold.
Based on the same inventive concept, an embodiment of the present invention further provides a network traffic balancing apparatus, where the apparatus is applied to a switching device, and a structure of the apparatus is shown in fig. 4, where the apparatus includes: an acquisition unit 41, a flow table unit 42, a matching unit 43, and a processing unit 44; wherein the content of the first and second substances,
the acquiring unit 41 is configured to acquire and send IPv6 traffic bandwidth data of an egress link to allow an SDN controller to issue an instruction according to the IPv6 traffic bandwidth data;
the flow table unit 42 is configured to, when receiving a flow policy issued by the SDN controller, perform chip hardware installation of the OpenFlow flow table according to a pre-stored network segment mapping relationship; the flow table management module is further used for deleting the OpenFlow flow table installed on the chip hardware when a flow strategy deleting instruction issued by the SDN controller is received;
the matching unit 43 is configured to determine whether the received IPv6 message from the dual stack terminal hits the OpenFlow flow table;
the processing unit 44 is configured to forward the IPv6 packet to a central processing unit CPU of the switch device for discarding when the IPv6 packet hits in the OpenFlow flow table.
The flow table unit 42 is specifically configured to, when receiving that the flow policy issued by the SDN controller is a flow control flow table, determine a corresponding pre-stored network segment mapping relationship according to a gateway ID in the flow control flow table; determining an IPv6 network segment corresponding to the IPv4 network segment needing flow scheduling according to the network segment mapping relation and the IPv4 network segment needing flow scheduling in the flow control flow table; determining actions for processing IPv4 messages and actions for processing IPv6 messages according to the forwarding strategy in the flow control table; obtaining and storing OpenFlow flow tables comprising gateway IDs, actions of processing IPv4 messages, actions of processing IPv6 messages, IPv4 network segments and corresponding IPv6 network segments; the action of processing the IPv4 message is normal forwarding, and the action of processing the IPv6 message is forwarding to the CPU for discarding.
The matching unit 43 is specifically configured to obtain whether a destination IP address of the received IPv6 message belongs to an IPv6 network segment in the OpenFlow flow table, and if so, determine that the IPv6 message hits the OpenFlow table.
Further, the processing unit 44 is further configured to, when the discarded IPv6 packet is an IPv6 domain name resolution DNS packet, forge an invalid IPv6 DNS reply packet to send to the dual stack terminal, so that the dual stack terminal starts an IPv4 connection.
It should be understood that the implementation principle and process of the network traffic balancing apparatus provided in the embodiment of the present invention are similar to those in fig. 1 and fig. 2 and the embodiment shown above, and are not described herein again.
According to the network traffic balancing method and device provided by the embodiment of the invention, whether traffic scheduling is carried out is determined by acquiring IPv6 traffic bandwidth data of an outlet link of the switching equipment according to the relation between IPv6 traffic bandwidth and a preset scheduling threshold, so that IPv4/IPv6 access switching of the dual-stack terminal is realized. The network flow balancing method and the device provided by the embodiment of the invention can ensure that the problem of poor access experience of the terminal IPv6 caused by insufficient IPv6 bandwidth is avoided under the condition of fully utilizing the IPv6 bandwidth of the outlet; and the SDN controller schedules flow as required, so that the IPv6 service access of an important service network segment is not influenced, and the user experience is greatly improved.
Those of ordinary skill in the art will understand that: the figures are merely schematic representations of one embodiment, and the blocks or flow diagrams in the figures are not necessarily required to practice the present invention.
From the above description of the embodiments, it is clear to those skilled in the art that the present invention can be implemented by software plus necessary general hardware platform. Based on such understanding, the technical solutions of the present invention may be embodied in the form of a software product, which may be stored in a storage medium, such as ROM/RAM, magnetic disk, optical disk, etc., and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to execute the method according to the embodiments or some parts of the embodiments.
The embodiments in the present specification are described in a progressive manner, and the same and similar parts among the embodiments are referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, for apparatus or system embodiments, since they are substantially similar to method embodiments, they are described in relative terms, as long as they are described in partial descriptions of method embodiments. The above-described embodiments of the apparatus and system are merely illustrative, and the units described as separate parts may or may not be physically separate, and the parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the present embodiment. One of ordinary skill in the art can understand and implement it without inventive effort.
In addition, in some of the flows described in the above embodiments and the drawings, a plurality of operations are included in a specific order, but it should be clearly understood that the operations may be executed out of the order presented herein or in parallel, and the sequence numbers of the operations, such as 201, 202, 203, etc., are merely used for distinguishing different operations, and the sequence numbers themselves do not represent any execution order. Additionally, the flows may include more or fewer operations, and the operations may be performed sequentially or in parallel. It should be noted that, the descriptions of "first", "second", etc. in this document are used for distinguishing different messages, devices, modules, etc., and do not represent a sequential order, nor limit the types of "first" and "second" to be different.
The above-described embodiments of the apparatus are merely illustrative, and the units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the present embodiment. One of ordinary skill in the art can understand and implement it without inventive effort.
The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
While alternative embodiments of the present invention have been described, additional variations and modifications in those embodiments may occur to those skilled in the art once they learn of the basic inventive concepts. It is therefore intended that the following appended claims be interpreted as including alternative embodiments and all such alterations and modifications as fall within the scope of the invention.
It will be apparent to those skilled in the art that various modifications and variations can be made in the embodiments of the present invention without departing from the spirit or scope of the embodiments of the invention. Thus, if such modifications and variations of the embodiments of the present invention fall within the scope of the claims of the present invention and their equivalents, the present invention is also intended to encompass such modifications and variations.
Claims (14)
1. A network traffic balancing method is applied to a Software Defined Network (SDN) controller and comprises the following steps:
acquiring IPv6 flow bandwidth data of an outlet link of the connected switching equipment according to a preset period;
judging whether the IPv6 traffic bandwidth data of the link is larger than a preset upper limit scheduling threshold, and if so, issuing a preset traffic strategy to the switching equipment to enable the switching equipment to perform traffic scheduling according to the traffic strategy;
and judging whether the IPv6 traffic bandwidth data of the link is smaller than a preset lower limit scheduling threshold, and if so, issuing a traffic strategy deleting instruction to the switching equipment to enable the switching equipment to stop traffic scheduling.
2. The method according to claim 1, wherein the issuing a preset traffic policy to the switching device includes:
issuing a preset flow control table to the switching equipment so that the switching equipment forwards the message corresponding to the IPv4 network segment needing flow scheduling according to the forwarding strategy of the flow control table; the flow control table comprises a gateway ID, a forwarding strategy and an IPv4 network segment needing flow scheduling; the switching equipment is the switching equipment corresponding to the IPv4 network segment needing traffic scheduling.
3. The method of claim 1, wherein the lower flow threshold is less than an upper flow threshold.
4. A network traffic balancing method is applied to a switching device, and comprises the following steps:
collecting and sending IPv6 traffic bandwidth data of an exit link for an SDN controller to issue an instruction according to the IPv6 traffic bandwidth data;
when a flow strategy issued by the SDN controller is received, chip hardware of the OpenFlow flow table is installed according to a pre-stored network segment mapping relation;
judging whether the received IPv6 message from the dual-stack terminal hits the OpenFlow flow table or not, if yes, forwarding the IPv6 message to a Central Processing Unit (CPU) of the switching equipment for discarding;
and when a flow strategy deleting instruction issued by the SDN controller is received, deleting the OpenFlow flow table installed on the chip hardware.
5. The method of claim 4, wherein when receiving that the flow policy issued by the SDN controller is a flow control flow table, the chip hardware installation of the OpenFlow flow table according to the pre-stored network segment mapping relationship comprises:
determining a corresponding pre-stored network segment mapping relation according to the gateway ID in the flow control flow table;
determining an IPv6 network segment corresponding to the IPv4 network segment needing flow scheduling according to the network segment mapping relation and the IPv4 network segment needing flow scheduling in the flow control flow table;
determining an action for processing an IPv4 message and an action for processing an IPv6 message according to a forwarding strategy in the flow control table;
obtaining and storing OpenFlow flow tables comprising gateway IDs, actions of processing IPv4 messages, actions of processing IPv6 messages, IPv4 network segments and corresponding IPv6 network segments; the action of processing the IPv4 message is normal forwarding, and the action of processing the IPv6 message is forwarding to the CPU for discarding.
6. The method according to claim 4, wherein the determining whether the received IPv6 packet hits in the OpenFlow flow table includes:
and acquiring whether a destination IP address of the received IPv6 message belongs to an IPv6 network segment in the OpenFlow flow table, and if so, determining that the IPv6 message hits the OpenFlow flow table.
7. The method according to any of claims 4 to 6, wherein after forwarding the IPv6 message to a Central Processing Unit (CPU) of the switching device for discarding, the method further comprises:
and when the discarded IPv6 message is an IPv6 domain name resolution DNS message, forging an invalid IPv6 DNS response message and sending the invalid IPv6 DNS response message to the dual-stack terminal so that the dual-stack terminal starts IPv4 connection.
8. A network traffic balancing device applied to a Software Defined Network (SDN) controller comprises the following components: the device comprises an acquisition unit, a judgment unit and a sending unit; wherein the content of the first and second substances,
the acquiring unit is used for acquiring IPv6 traffic bandwidth data of an exit link of the connected switching equipment according to a preset period;
the judging unit is used for judging whether the IPv6 traffic bandwidth data of the link is greater than a preset upper limit scheduling threshold value; the method is also used for judging whether the IPv6 flow bandwidth data of the link is smaller than a preset lower limit scheduling threshold value;
the sending unit is configured to, when the IPv6 traffic of the link bandwidth data is greater than a preset upper scheduling threshold, issue a preset traffic policy to the switching device so that the switching device performs traffic scheduling according to the traffic policy; and when the IPv6 traffic of the link bandwidth data is smaller than a preset lower scheduling threshold, issuing a traffic policy deletion instruction to the switching device to cause the switching device to stop traffic scheduling.
9. The apparatus according to claim 8, wherein the sending unit is specifically configured to issue a preset flow control table to the switching device, so that the switching device forwards a packet corresponding to an IPv4 network segment requiring flow scheduling according to a forwarding policy of the flow control table; the flow control table comprises a gateway ID, a forwarding strategy and an IPv4 network segment needing flow scheduling; the switching equipment is the switching equipment corresponding to the IPv4 network segment needing traffic scheduling.
10. The apparatus of claim 8, wherein the lower flow threshold is less than an upper flow threshold.
11. A network traffic balancing apparatus, applied to a switching device, comprising: the system comprises an acquisition unit, a flow table unit, a matching unit and a processing unit; wherein the content of the first and second substances,
the acquisition unit is used for acquiring and sending IPv6 traffic bandwidth data of an egress link to allow an SDN controller to issue an instruction according to the IPv6 traffic bandwidth data;
the flow table unit is used for installing chip hardware of the OpenFlow flow table according to a pre-stored network segment mapping relation when receiving a flow strategy issued by the SDN controller; the flow table management module is further used for deleting the OpenFlow flow table installed on the chip hardware when a flow strategy deleting instruction issued by the SDN controller is received;
the matching unit is used for judging whether the received IPv6 message from the dual-stack terminal hits the OpenFlow flow table or not;
and the processing unit is configured to forward the IPv6 packet to a central processing unit CPU of the switch device for discarding when the IPv6 packet hits the OpenFlow flow table.
12. The apparatus according to claim 11, wherein the flow table unit is specifically configured to, when receiving that the flow policy issued by the SDN controller is a flow control flow table, determine a corresponding pre-stored network segment mapping relationship according to a gateway ID in the flow control flow table; determining an IPv6 network segment corresponding to the IPv4 network segment needing flow scheduling according to the network segment mapping relation and the IPv4 network segment needing flow scheduling in the flow control flow table; determining actions for processing IPv4 messages and actions for processing IPv6 messages according to the forwarding strategy in the flow control table; obtaining and storing OpenFlow flow tables comprising gateway IDs, actions of processing IPv4 messages, actions of processing IPv6 messages, IPv4 network segments and corresponding IPv6 network segments; the action of processing the IPv4 message is normal forwarding, and the action of processing the IPv6 message is forwarding to the CPU for discarding.
13. The apparatus according to claim 11, wherein the matching unit is specifically configured to obtain whether a destination IP address of the received IPv6 packet belongs to an IPv6 segment in the OpenFlow flow table, and if so, determine that the IPv6 packet hits in the OpenFlow flow table.
14. The apparatus according to any one of claims 11 to 13, wherein the processing unit is further configured to, when the discarded IPv6 packet is an IPv6 domain name resolution DNS packet, send a fake invalid IPv6 DNS reply packet to the dual stack terminal, so that the dual stack terminal starts an IPv4 connection.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910906022.7A CN110601989A (en) | 2019-09-24 | 2019-09-24 | Network traffic balancing method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910906022.7A CN110601989A (en) | 2019-09-24 | 2019-09-24 | Network traffic balancing method and device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN110601989A true CN110601989A (en) | 2019-12-20 |
Family
ID=68862874
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910906022.7A Withdrawn CN110601989A (en) | 2019-09-24 | 2019-09-24 | Network traffic balancing method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110601989A (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111654448A (en) * | 2020-05-06 | 2020-09-11 | 杭州迪普科技股份有限公司 | Traffic scheduling method and device |
| WO2021185161A1 (en) * | 2020-03-19 | 2021-09-23 | 阿里巴巴集团控股有限公司 | Message processing device and message processing method |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103023797A (en) * | 2011-09-23 | 2013-04-03 | 百度在线网络技术（北京）有限公司 | Data center system and device and method for providing service |
| US20130308448A1 (en) * | 2012-05-16 | 2013-11-21 | The Keyw Corporation | Packet capture deep packet inspection sensor |
| CN103685281A (en) * | 2013-12-18 | 2014-03-26 | 中国联合网络通信集团有限公司 | Network address protocol switching method and device |
| CN104243317A (en) * | 2014-09-26 | 2014-12-24 | 杭州华三通信技术有限公司 | Method and device for forwarding IP (internet protocol) routes |
| CN105991456A (en) * | 2015-02-06 | 2016-10-05 | 中国电信股份有限公司 | OpenFlow switch, network system and bandwidth sharing method |
| WO2016182770A1 (en) * | 2015-05-14 | 2016-11-17 | Qualcomm Incorporated | Dynamically adjusting network services stratum parameters based on access and/or connectivity stratum utilization and/or congestion information |
| CN106685849A (en) * | 2016-12-22 | 2017-05-17 | 上海斐讯数据通信技术有限公司 | Method and system of WRED message dropping based on SDN |
-
2019
- 2019-09-24 CN CN201910906022.7A patent/CN110601989A/en not_active Withdrawn
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103023797A (en) * | 2011-09-23 | 2013-04-03 | 百度在线网络技术（北京）有限公司 | Data center system and device and method for providing service |
| US20130308448A1 (en) * | 2012-05-16 | 2013-11-21 | The Keyw Corporation | Packet capture deep packet inspection sensor |
| CN103685281A (en) * | 2013-12-18 | 2014-03-26 | 中国联合网络通信集团有限公司 | Network address protocol switching method and device |
| CN104243317A (en) * | 2014-09-26 | 2014-12-24 | 杭州华三通信技术有限公司 | Method and device for forwarding IP (internet protocol) routes |
| CN105991456A (en) * | 2015-02-06 | 2016-10-05 | 中国电信股份有限公司 | OpenFlow switch, network system and bandwidth sharing method |
| WO2016182770A1 (en) * | 2015-05-14 | 2016-11-17 | Qualcomm Incorporated | Dynamically adjusting network services stratum parameters based on access and/or connectivity stratum utilization and/or congestion information |
| CN106685849A (en) * | 2016-12-22 | 2017-05-17 | 上海斐讯数据通信技术有限公司 | Method and system of WRED message dropping based on SDN |
Non-Patent Citations (1)
| Title |
|---|
| 费怡文等: "双栈终端在IPv4-IPv6过渡期访问WAP业务的技术实现", 《数据通信》 * |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2021185161A1 (en) * | 2020-03-19 | 2021-09-23 | 阿里巴巴集团控股有限公司 | Message processing device and message processing method |
| CN113497718A (en) * | 2020-03-19 | 2021-10-12 | 阿里巴巴集团控股有限公司 | Message processing device and message processing method |
| CN113497718B (en) * | 2020-03-19 | 2023-08-15 | 阿里巴巴集团控股有限公司 | Message processing equipment and message processing method |
| CN111654448A (en) * | 2020-05-06 | 2020-09-11 | 杭州迪普科技股份有限公司 | Traffic scheduling method and device |
| CN111654448B (en) * | 2020-05-06 | 2023-07-25 | 杭州迪普科技股份有限公司 | Traffic scheduling method and device |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11522734B2 (en) | Method for controlling a remote service access path and relevant device | |
| WO2018152919A1 (en) | Path selection method and system, network acceleration node, and network acceleration system | |
| CN101443750B (en) | Techniques for load balancing over a cluster of subscriber-aware application servers | |
| CN109040243B (en) | Message processing method and device | |
| CN109379244B (en) | Network acceleration communication method and device and electronic equipment | |
| JP2011160041A (en) | Front end system and front end processing method | |
| EP2731313A1 (en) | Distributed cluster processing system and message processing method thereof | |
| JP6663082B2 (en) | Data Streaming Support Control Based on Node Type | |
| JP7313480B2 (en) | Congestion Avoidance in Slice-Based Networks | |
| CN108881018B (en) | Methods, systems, and devices for routing DIAMETER messages at DIAMETER signaling routers | |
| US10411911B2 (en) | Network as service service cross-domain orchestration method, orchestration device, and control device | |
| CN101217508A (en) | A network agent system and the corresponding realizing methods based on instant communication platform | |
| CN105991347A (en) | Redirection method of DNS request message and device | |
| CN102195882A (en) | Method and device for selecting route according to data stream application type | |
| KR20090084670A (en) | Method and system for two-phase mechanism for discovering web services based management service | |
| CN101841424B (en) | EMS network management system and method based on SOCKS proxy connection | |
| CN110601989A (en) | Network traffic balancing method and device | |
| US20060239263A1 (en) | Method for the establishing of connections in a communication system | |
| CN106790502B (en) | Load balancing system of IPv4 terminal and IPv6 service intercommunication service based on NAT64 prefix | |
| WO2020249128A1 (en) | Service routing method and apparatus | |
| CN111064825B (en) | Method and device for realizing DPI data acquisition and control based on ARP | |
| CN101686174A (en) | Method and system for realizing service flow based on MPLSs | |
| CN104735000A (en) | OpenFlow signaling control method and device | |
| CN110601993B (en) | Multi-outlet load balancing method and device | |
| US11575601B2 (en) | Network device and packet processing method using same |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| WW01 | Invention patent application withdrawn after publication | ||
| WW01 | Invention patent application withdrawn after publication |
Application publication date: 20191220 |