CN103401800B - A kind of balancing link load method and apparatus - Google Patents
A kind of balancing link load method and apparatus Download PDFInfo
- Publication number
- CN103401800B CN103401800B CN201310331543.7A CN201310331543A CN103401800B CN 103401800 B CN103401800 B CN 103401800B CN 201310331543 A CN201310331543 A CN 201310331543A CN 103401800 B CN103401800 B CN 103401800B
- Authority
- CN
- China
- Prior art keywords
- address
- load balancing
- type
- class
- external network
- 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.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 38
- 230000004044 response Effects 0.000 claims description 75
- 238000001514 detection method Methods 0.000 claims description 22
- 238000004891 communication Methods 0.000 claims description 10
- 238000006243 chemical reaction Methods 0.000 description 10
- 230000008569 process Effects 0.000 description 9
- 238000010586 diagram Methods 0.000 description 7
- 238000005516 engineering process Methods 0.000 description 7
- 230000002085 persistent effect Effects 0.000 description 6
- 101100443945 Mus musculus Dpysl3 gene Proteins 0.000 description 1
- 230000036541 health Effects 0.000 description 1
Landscapes
- Data Exchanges In Wide-Area Networks (AREA)
- Computer And Data Communications (AREA)
Abstract
The invention discloses a kind of balancing link load method and apparatus, the method includes: load-balancing device receives DNS request message, to the first IP like address of dns server request external network server, and to the second IP like address of dns server request external network server；Load-balancing device records the corresponding relation between the first IP like address of external network server and the second IP like address of external network server in equivalent service table；Load-balancing device receives service request message, and its purpose IP address is the first IP like address of external network server；When the second IP like address that the first IP like address having external network server in equivalent service table is corresponding, load-balancing device selects ISP link from ISP link based on the first IP like address and ISP link based on the second IP like address.In the embodiment of the present invention, between ISP link based on IPv4 address and ISP link based on IPv6 address, realize load balancing, and make full use of the bandwidth of ISP link.
Description
Technical Field
The present invention relates to the field of communications technologies, and in particular, to a link load balancing method and device.
Background
As shown in fig. 1, an application scenario diagram of a link load balancing technology is shown, where a load balancing device (i.e., an LB device) is deployed to guide an intranet client to access a path of an external resource through the load balancing device, and a suitable physical link is searched according to a destination IP address of a packet and a link load balancing policy, so as to complete load balancing of the packet among multiple links. The load balancing device can realize the following functions: intelligent link selection, flow control and management, link health state detection, link fault handling, and the like.
When selecting a link, the load balancing device may select a link with the closest arrival destination address or the smallest delay, which is proximity detection. Specifically, after receiving the message, the load balancing device sends detection messages from all physical links by taking the destination IP address of the message as a target, generates proximity table entries for each physical link based on the detection result of each physical link, and selects the optimal link for the subsequent message according to the proximity table entries.
As shown in fig. 2, in the IPv4 link load balancing technology, a load balancing device receives a message from an intranet client, where a source IP address of the message is an IP address of a terminal device, and a destination IP address is a public network IP address of an extranet server; the load balancing device selects an ISP (Internet service provider) link according to the destination IP address of the message and a link load balancing strategy; the load balancing equipment sends the message to the ISP link so as to send the message to the external network server through the ISP link, wherein the source IP address of the message is the public network address of the ISP link (the public network address of the ISP link is used for replacing the source IP address of the message through network address conversion), and the destination IP address is the public network IP address of the external network server; the load balancing equipment receives a message returned by the external network server, wherein the source IP address of the message is the public network IP address of the external network server, and the destination IP address is the public network address of the ISP link; the load balancing device sends the message to the intranet client, the source IP address of the message is the public network IP address of the extranet server, and the destination IP address is the IP address of the terminal device (the destination IP address of the message is replaced by the IP address of the terminal device through network address conversion).
In the IPv6 link load balancing technology, the principle of implementing link load balancing is similar to that of implementing IPv4 link load balancing, except that the source IP address and the destination IP address of the packet are both IPv6 addresses, whereas in the IPv4 link load balancing technology, the source IP address and the destination IP address of the packet are both IPv4 addresses.
In the prior art, the load balancing technology is only implemented separately for the IPv4 address or the IPv6 address, but the load balancing technology cannot be implemented when the IPv4 address and the IPv6 address coexist. Specifically, when the plurality of ISP links include an ISP link based on an IPv4 address and an ISP link based on an IPv6 address, the load balancing apparatus cannot implement a load balancing technique between the ISP link based on the IPv4 address and the ISP link based on the IPv6 address, and thus cannot fully utilize the bandwidth of the ISP link.
Disclosure of Invention
The embodiment of the invention provides a link load balancing method and equipment, which realize load balancing between an ISP link based on an IPv4 address and an ISP link based on an IPv6 address and fully utilize the bandwidth of the ISP link.
In order to achieve the above object, an embodiment of the present invention provides a link load balancing method, which is applied to a network including an intranet client, a load balancing device, a domain name system DNS server, and an extranet server, where an internet service provider ISP link based on a first type of IP address and an ISP link based on a second type of IP address exist between the load balancing device and the extranet server, and the method includes:
the load balancing equipment receives a DNS request message carrying domain name information from an intranet client, and requests a DNS server for a first-class IP address of an extranet server corresponding to the domain name information and a second-class IP address of the extranet server corresponding to the domain name information;
the load balancing equipment receives a first class of IP address of an external network server from the DNS server and a second class of IP address of the external network server, and records the corresponding relation between the first class of IP address of the external network server and the second class of IP address of the external network server in an equivalent service table;
the load balancing equipment receives a service request message from an intranet client, wherein the destination IP address of the service request message is a first-class IP address of an extranet server;
when the equivalent service table has a second type of IP address of the external network server corresponding to the first type of IP address of the external network server, the load balancing equipment selects an ISP link from ISP links based on the first type of IP address and ISP links based on the second type of IP address by using a link load balancing strategy;
when the selected ISP link is based on the second type of IP address, the load balancing equipment modifies the source IP address of the service request message into the second type of IP address of the load balancing equipment, modifies the destination IP address of the service request message into the second type of IP address of the external network server corresponding to the first type of IP address of the external network server, and transmits the modified service request message through the selected ISP link.
The method further comprises the following steps:
the load balancing equipment modifies a source IP address of a service request message into a second type IP address of the load balancing equipment, modifies a destination IP address of the service request message into a second type IP address of an external network server, and records the corresponding relation among the IP address of the internal network client carried in the service request message, the first type IP address of the external network server carried in the service request message, the second type IP address of the load balancing equipment and the second type IP address of the external network server;
the load balancing equipment receives a service response message from the external network server, the source IP address of the service response message is the second-class IP address of the external network server, and the destination IP address of the service response message is the second-class IP address of the load balancing equipment;
the load balancing equipment queries the corresponding relation through a second type IP address of the external network server and the second type IP address of the load balancing equipment to obtain the IP address of the internal network client and the first type IP address of the external network server which are recorded in the corresponding relation;
and the load balancing equipment modifies the source IP address of the service response message into the first class IP address of the external network server, modifies the destination IP address of the service response message into the IP address of the internal network client, and sends the modified service response message to the internal network client.
After the load balancing device selects an ISP link from the ISP links based on the first type of IP address and the ISP links based on the second type of IP address by using the link load balancing policy, the method further includes:
when the selected ISP link is based on a first-class IP address, the load balancing equipment modifies the source IP address of the service request message into the first-class IP address of the load balancing equipment, sends the modified service request message through the selected ISP link, and records the corresponding relation among the IP address of the intranet client carried in the service request message, the first-class IP address of the extranet server carried in the service request message and the first-class IP address of the load balancing equipment;
the load balancing equipment receives a service response message from the external network server, wherein the source IP address of the service response message is the first-class IP address of the external network server, and the destination IP address of the service response message is the first-class IP address of the load balancing equipment;
the load balancing equipment queries the corresponding relation through the first-class IP address of the external network server and the first-class IP address of the load balancing equipment to obtain the IP address of the internal network client recorded in the corresponding relation, modifies the target IP address of the service response message into the IP address of the internal network client, and sends the modified service response message to the internal network client.
When the link load balancing policy requires selection of an ISP link from among ISP links based on a first type of IP address and ISP links based on a second type of IP address based on a proximity table, the method further comprises:
the load balancing equipment carries out proximity detection on the first class IP address of the external network server through the ISP link based on the first class IP address, carries out proximity detection on the second class IP address of the external network server through the ISP link based on the second class IP address, and maintains a proximity table by using a result of detecting the first class IP address of the external network server and a result of detecting the second class IP address of the external network server.
The first type of IP address is an IPv4 address, and the second type of IP address is an IPv6 address; or,
the first type of IP address is an IPv6 address, and the second type of IP address is an IPv4 address.
The embodiment of the invention provides a load balancing device, which is applied to a network comprising an intranet client, the load balancing device, a Domain Name System (DNS) server and an extranet server, wherein an Internet Service Provider (ISP) link based on a first type of IP address and an ISP link based on a second type of IP address exist between the load balancing device and the extranet server, and the load balancing device specifically comprises:
the communication module is used for receiving a DNS request message carrying domain name information from an intranet client, and requesting a first-class IP address of an extranet server corresponding to the domain name information and a second-class IP address of the extranet server corresponding to the domain name information from the DNS server; receiving a first class IP address of an external network server from the DNS server and a second class IP address of the external network server, and recording a corresponding relation between the first class IP address of the external network server and the second class IP address of the external network server in an equivalent service table; receiving a service request message from an intranet client, wherein the destination IP address of the service request message is a first-class IP address of an extranet server;
a selecting module, configured to select, when there is a second type IP address of the external network server corresponding to the first type IP address of the external network server in the equivalent service table, an ISP link from ISP links based on the first type IP address and ISP links based on the second type IP address by using a link load balancing policy;
and the processing module is used for modifying the source IP address of the service request message into the second type IP address of the load balancing equipment when the selected ISP link is the ISP link based on the second type IP address, modifying the destination IP address of the service request message into the second type IP address of the external network server corresponding to the first type IP address of the external network server, and sending the modified service request message through the selected ISP link.
The processing module is further configured to record a corresponding relationship between an IP address of the intranet client carried in the service request packet, a first-class IP address of the extranet server carried in the service request packet, a second-class IP address of the load balancing device, and a second-class IP address of the extranet server after modifying a source IP address of the service request packet into the second-class IP address of the load balancing device and modifying a destination IP address of the service request packet into the second-class IP address of the extranet server;
the communication module is further configured to receive a service response packet from the external network server, where a source IP address of the service response packet is a second-class IP address of the external network server, and a destination IP address of the service response packet is a second-class IP address of the load balancing device;
the processing module is further configured to query the corresponding relationship through a second type of IP address of the external network server and a second type of IP address of the load balancing device, so as to obtain an IP address of the internal network client and a first type of IP address of the external network server, which are recorded in the corresponding relationship; and modifying the source IP address of the service response message into a first class IP address of the extranet server, modifying the destination IP address of the service response message into the IP address of the intranet client, and sending the modified service response message to the intranet client.
The processing module is further configured to, after an ISP link is selected from an ISP link based on a first type of IP address and an ISP link based on a second type of IP address by using a link load balancing policy, modify a source IP address of the service request packet into the first type of IP address of the load balancing device when the selected ISP link is the ISP link based on the first type of IP address, send the modified service request packet through the selected ISP link, and record a correspondence relationship between an IP address of an intranet client carried in the service request packet, the first type of IP address of an extranet server carried in the service request packet, and the first type of IP address of the load balancing device;
the communication module is further configured to receive a service response packet from the external network server, where a source IP address of the service response packet is a first-class IP address of the external network server, and a destination IP address of the service response packet is a first-class IP address of the load balancing device;
the processing module is further configured to query the corresponding relationship through the first-class IP address of the extranet server and the first-class IP address of the load balancing device to obtain the IP address of the intranet client recorded in the corresponding relationship, modify the destination IP address of the service response packet into the IP address of the intranet client, and send the modified service response packet to the intranet client.
The processing module is further configured to, when the link load balancing policy needs to select an ISP link from ISP links based on the first type IP addresses and ISP links based on the second type IP addresses based on the proximity table, perform proximity detection on the first type IP addresses of the extranet servers through the ISP links based on the first type IP addresses, perform proximity detection on the second type IP addresses of the extranet servers through the ISP links based on the second type IP addresses, and maintain the proximity table by using a result of detecting the first type IP addresses of the extranet servers and a result of detecting the second type IP addresses of the extranet servers.
The first type of IP address is an IPv4 address, and the second type of IP address is an IPv6 address; or,
the first type of IP address is an IPv6 address, and the second type of IP address is an IPv4 address.
Compared with the prior art, the embodiment of the invention at least has the following advantages: in the embodiment of the invention, in a network in which an ISP link based on an IPv4 address and an ISP link based on an IPv6 address exist between load balancing equipment and an external network server, the load balancing equipment records the corresponding relation between the IPv4 address and the IPv6 address of the external network server in an equivalent service table so as to realize load balancing between the ISP link based on the IPv4 address and the ISP link based on the IPv6 address and fully utilize the bandwidth of the ISP link.
Drawings
Fig. 1 is a schematic view of an application scenario of a link load balancing technique in the prior art;
FIG. 2 is a schematic diagram of an application scenario of an IPv4 link load balancing technique in the prior art;
fig. 3 is a schematic flowchart of a link load balancing method according to an embodiment of the present invention;
FIGS. 4 and 5 are diagrams illustrating specific application scenarios of embodiments of the present invention;
fig. 6is a schematic structural diagram of a load balancing device according to an embodiment of the present invention.
Detailed Description
In order to solve the problems in the prior art, an embodiment of the present invention provides a link load balancing method, which may be applied to a network including at least an intranet client, a load balancing device, a DNS (domain name system) server, and an extranet server, where an ISP link based on a first type of IP address and an ISP link based on a second type of IP address exist between the load balancing device and the extranet server. The first type of IP address is an IPv4 address, and the second type of IP address is an IPv6 address; or the first type of IP address is an IPv6 address, and the second type of IP address is an IPv4 address.
The load balancing equipment needs to be configured with a first class IP address and a second class IP address, the first class IP address of the load balancing equipment is used for communicating with an intranet client using the first class IP address, and the second class IP address of the load balancing equipment is used for communicating with the intranet client using the second class IP address.
As shown in fig. 3, the link load balancing method includes the following steps:
step 301, a load balancing device receives a DNS request packet carrying domain name information from an intranet client, and requests a DNS server for a first-class IP address of an extranet server corresponding to the domain name information and a second-class IP address of the extranet server corresponding to the domain name information.
In the embodiment of the present invention, the process that the load balancing device requests the DNS server for the first type of IP address of the external network server corresponding to the domain name information and requests the DNS server for the second type of IP address of the external network server corresponding to the domain name information specifically includes, but is not limited to, the following manners:
when a DNS request message carrying domain name information from an intranet client carries a first-class IP address of a DNS server, load balancing equipment requests the DNS server for the first-class IP address of an outer network server corresponding to the domain name information and a second-class IP address of the outer network server corresponding to the requested domain name information through the first-class IP address of the load balancing equipment; when a DNS request message carrying domain name information from an intranet client carries a second-class IP address of a DNS server, the load balancing equipment requests the DNS server for a first-class IP address of an outer network server corresponding to the domain name information and a second-class IP address of the outer network server corresponding to the domain name information through the second-class IP address of the load balancing equipment.
In a second mode, no matter a DNS request message carrying domain name information from an intranet client carries a first-class IP address of a DNS server or a second-class IP address of the DNS server, the load balancing equipment requests the DNS server for the first-class IP address of the outer network server corresponding to the domain name information and the second-class IP address of the outer network server corresponding to the request domain name information through the first-class IP address of the load balancing equipment; or the load balancing devices all request the DNS server for the first class IP address of the external network server corresponding to the domain name information and the second class IP address of the external network server corresponding to the domain name information through the second class IP address of the load balancing device.
In the first and second modes, the load balancing device requests the DNS server for the first class IP address of the external network server corresponding to the domain name information and the second class IP address of the external network server corresponding to the request domain name information through the first class IP address of the load balancing device, or the load balancing device requests the DNS server for the first class IP address of the external network server corresponding to the domain name information and the second class IP address of the external network server corresponding to the request domain name information through the second class IP address of the load balancing device, which may be the first class IP address of the external network server and the second class IP address of the external network server requested based on the same address request process, or the first class IP address of the external network server and the second class IP address of the external network server requested based on two different address request processes.
Step 302, the load balancing device receives the first type IP address of the external network server and the second type IP address of the external network server from the DNS server, and records a corresponding relationship between the first type IP address of the external network server and the second type IP address of the external network server in the equivalent service table.
In the embodiment of the invention, the first-class IP address of the external network server from the DNS server can be a plurality of first-class IP addresses of the external network server; further, the second type of IP address of the foreign network server from the DNS server may be a plurality of second type IP addresses of the foreign network server.
Step 303, the load balancing device receives a service request packet (i.e. a packet related to a request service) from the intranet client, where a source IP address of the service request packet is a first-class IP address of the intranet client, and a destination IP address of the service request packet is a first-class IP address of the extranet server.
Step 304, when there is the second type IP address of the external network server corresponding to the first type IP address of the external network server in the equivalent service table, the load balancing device selects an ISP link from the ISP link based on the first type IP address and the ISP link based on the second type IP address by using a link load balancing policy.
After receiving a service request message from an intranet client, if a second-class IP address of an extranet server corresponding to a first-class IP address of an extranet server carried in the service request message exists in an equivalent service table, the load balancing equipment selects an ISP link from ISP links based on the first-class IP address and ISP links based on the second-class IP address by using a link load balancing strategy. If the second type of IP address of the external network server corresponding to the first type of IP address of the external network server carried in the service request message is not present in the equivalent service table, the load balancing device selects an ISP link from ISP links based on the first type of IP address by using a link load balancing policy, which is not described again in this process.
The link load balancing policy (i.e., load balancing algorithm) includes, but is not limited to: a polling selection strategy, a random selection strategy, an address-based Hash selection strategy, a nearby selection strategy (i.e. selecting a link which is the closest to a destination address or has the smallest time delay), a weighted selection strategy, a persistent table item selection strategy, etc.
When the link load balancing policy is the proximity selection policy, the load balancing device needs to select an ISP link from ISP links based on the first type IP addresses and ISP links based on the second type IP addresses based on the proximity table, and when the load balancing device needs to select an ISP link from the ISP links based on the first type IP addresses and the ISP links based on the second type IP addresses based on the proximity table, the load balancing device needs to perform proximity detection on the first type IP addresses of the external network servers through the ISP links based on the first type IP addresses, perform proximity detection on the second type IP addresses of the external network servers through the ISP links based on the second type IP addresses, and maintain the proximity table using a result of the detection on the first type IP addresses of the external network servers and a result of the detection on the second type IP addresses of the external network servers.
When the link load balancing policy is a persistent entry selection policy, the load balancing device needs to continuously redirect multiple related connections to the same physical link, and to achieve this purpose, the load balancing device creates a persistent entry and stores an ISP link based on the first type of IP address and an ISP link based on the second type of IP address in the persistent entry. The continuous table item searching needs to search according to the addresses in the equivalent service table, and the continuous table items of the addresses in the equivalent service table are mutually exclusive, that is, only one continuous table item can be generated by the addresses in the equivalent service table at the same time. Based on the persistent entry, the process of the load balancing device selecting the ISP link using the persistent entry is not described in detail.
When the link load balancing strategy is an address-based Hash selection strategy, the load balancing equipment uses the address as a Hash Hash value to search a physical link, and the specific implementation mode comprises the following steps:
(1) distinguishing a Hash algorithm for the IPv4 address and the IPv6 address; such as:
the following Hash algorithm is adopted for the IPv4 address:
key=((IP>>22)+(IP>>11)+ulIP)；
the following Hash algorithm is adopted for the IPv6 address:
while (cycle fetch IPv6 address byte)
{
key = key max + (current address byte value);
}
(2) the same Hash algorithm is adopted for the IPv4 address and the IPv6 address; such as:
the following Hash algorithm is adopted for the IPv4 address and the IPv6 address:
while (byte address cycle)
{
key = key max + (current address byte value);
}
step 305, when the selected ISP link is an ISP link based on the second type IP address, the load balancing device modifies the source IP address of the service request packet into the second type IP address of the load balancing device, and modifies the destination IP address of the service request packet into the second type IP address of the extranet server corresponding to the first type IP address of the extranet server (which is the destination IP address of the service request packet).
In the embodiment of the present invention, after the load balancing device modifies the source IP address of the service request packet into the second type IP address of the load balancing device and modifies the destination IP address of the service request packet into the second type IP address of the extranet server, the load balancing device needs to record the corresponding relationship between the IP address of the intranet client carried in the service request packet, the first type IP address of the extranet server carried in the service request packet, the second type IP address of the load balancing device, and the second type IP address of the extranet server.
Step 306, the load balancing device sends the modified service request message through the selected ISP link, that is, the load balancing device sends the service request message to the extranet server through the selected ISP link.
Step 307, the load balancing device receives a service response packet (i.e. a response packet of the service request packet) from the external network server, where a source IP address of the service response packet is the second type IP address of the external network server, and a destination IP address of the service response packet is the second type IP address of the load balancing device.
In step 308, the load balancing device queries a corresponding relationship (which is maintained in step 305) through the second type IP address of the extranet server and the second type IP address of the load balancing device, so as to obtain the IP address of the intranet client and the first type IP address of the extranet server recorded in the corresponding relationship.
Step 309, the load balancing device modifies the source IP address of the service response packet into the first type IP address of the extranet server, modifies the destination IP address of the service response packet into the IP address of the intranet client, and sends the modified service response packet to the intranet client.
In the embodiment of the invention, after selecting an ISP link from an ISP link based on a first type of IP address and an ISP link based on a second type of IP address by using a link load balancing policy, when the selected ISP link is the ISP link based on the first type of IP address, the load balancing device modifies a source IP address of a service request message into the first type of IP address of the load balancing device, sends the modified service request message through the selected ISP link (that is, sends the service request message to an external network server through the selected ISP link), and records a corresponding relationship between an IP address of an internal network client carried in the service request message, the first type of IP address of the external network server carried in the service request message, and the first type of IP address of the load balancing device. The load balancing equipment receives a service response message from the external network server, the source IP address of the service response message is the first class IP address of the external network server, and the destination IP address of the service response message is the first class IP address of the load balancing equipment; then, the load balancing device queries the corresponding relationship through the first class IP address of the external network server and the first class IP address of the load balancing device to obtain the IP address of the internal network client recorded in the corresponding relationship, modifies the target IP address of the service response message into the IP address of the internal network client, and sends the modified service response message to the internal network client.
In the embodiment of the present invention, the load balancing device may further adjust information such as the source port number during the process of modifying the source IP address and the destination IP address of the service request packet, the adjustment process is similar to the prior art, and details are not repeated in the embodiment of the present invention.
In the embodiment of the present invention, the load balancing device may further enable a link virtual service to configure an IPv4 network segment or an IPv6 network segment, and after receiving a service request message from an intranet client, if a destination IPv4 address carried in the service request message is located in the IPv4 network segment or a destination IPv6 address carried in the service request message is located in the IPv6 network segment, the technical solution provided by the embodiment of the present invention is used for processing. In a general case, the IPv4 segment or the IPv6 segment may be a full segment.
In summary, in the embodiment of the present invention, in a network in which an ISP link based on an IP address of a first type (e.g., an IPv4 address) and an ISP link based on an IP address of a second type (e.g., an IPv6 address) exist between a load balancing device and an external network server, the load balancing device records a correspondence relationship between the IPv4 address and the IPv6 address of the external network server in an equivalent service table, so as to achieve load balancing between the ISP link based on the IPv4 address and the ISP link based on the IPv6 address, and fully utilize the bandwidth of the ISP link.
The technical solution of the embodiments of the present invention is described in detail below with reference to specific application scenarios.
As shown in the application scenario diagram shown in fig. 4, taking an intranet client as an IPv4 user as an example, in this application scenario, the link load balancing method includes the following steps:
step 1, an intranet client sends a DNS request message to load balancing equipment, wherein the DNS request message is a type A query of DNS, and domain name information carried in the DNS request message is a.com.
Step 2, after receiving the DNS request message, the load balancing device records a correspondence between a DNS query record (e.g., a.com) of the intranet client and a source IP address (e.g., 192.168.20.96) of the intranet client, as shown in table 1, which is a DNS request table for recording the correspondence.
TABLE 1
| IP address of intranet client | Requesting a domain name |
| 192.168.20.96 | a.com |
| 100::96 | b.com |
| …… | ...../ |
And 3, the load balancing equipment sends a class A query request of the DNS to request the IPv4 public network address of the external network server corresponding to the domain name (a.com), and sends an AAAA query request of the DNS to request the IPv6 public network address of the external network server corresponding to the domain name (a.com).
In the embodiment of the present invention, since the DNS request message is a class a query of the DNS, the DNS request message carrying domain name information from the intranet client carries an IPv4 address of the DNS server, and the load balancing device sends the class a query request of the DNS server to the DNS server through the IPv4 public network address of the load balancing device, requests the IPv4 public network address of the external network server corresponding to the domain name (a.com), and sends the AAAA query request of the DNS server through the IPv4 public network address of the load balancing device, and requests the IPv6 public network address of the external network server corresponding to the domain name (a.com).
And 4, the DNS server sends the IPv4 public network address of the external network server corresponding to the domain name (a.com) to the load balancing equipment through the class A response of the DNS, and sends the IPv6 public network address of the external network server corresponding to the domain name (a.com) to the load balancing equipment through the AAAA response of the DNS.
The IPv4 public network address of the external network server sent by the DNS server to the load balancing device may be a plurality of IPv4 public network addresses of the external network server; the IPv6 public network address of the external network server sent by the DNS server to the load balancing device may be a plurality of IPv6 public network addresses of the external network server.
Step 5, the load balancing device records the corresponding relation between the IPv4 public network address (such as 100.1.1.1) of the outer network server and the IPv6 public network address (such as 88:: 8) of the outer network server in the equivalent service table; these IPv4 public network addresses and IPv6 public network addresses correspond to the same extranet server (with a.com domain name) and are recorded in the load balancing device as different protocol family addresses that can provide the same service.
As shown in Table 2, is an example of an equivalent service table that records the correspondence between the IPv4 public network address of the extranet server (e.g., 100.1.1.1) and the IPv6 public network address of the extranet server (e.g., 88:: 8). The number of the IPv4 public network addresses of the extranet servers and the number of the IPv6 public network addresses of the extranet servers can be multiple.
TABLE 2
| IPv4 public network address | IPv6 public network address |
| 100.1.1.1 | 88::8 |
| 200.1.1.1 | 99::9 |
| …… | ...../ |
And 6, the load balancing equipment queries a DNS request table (records a DNS query record of the intranet client and a source IP address of the intranet client), obtains the source IP address of the intranet client, constructs a type A response of the DNS and returns the IPv4 public network address (such as 100.1.1.1) of the external network server to the intranet client.
In addition, the load balancing equipment can also carry out proximity detection on the IPv4 public network address (such as 100.1.1.1) and the IPv6 public network address (such as 88:: 8) of the extranet server; if a plurality of groups of ISP links based on IPv4 addresses or a plurality of groups of ISP links based on IPv6 addresses exist, the proximity detection detects the IPv4 public network address of the external network server in the ISP links based on the IPv4 addresses, and detects the IPv6 public network address of the external network server in the ISP links based on the IPv6 addresses, and the best exit link is obtained and recorded in the proximity table entry.
And 7, the intranet client sends a service request message to the load balancing equipment, wherein the source IP address of the service request message is the IPv4 address (such as 192.168.20.96) of the intranet client, and the destination IP address of the service request message is the public network IPv4 address (such as 100.1.1.1) of the extranet server.
And 8, after receiving the service request message from the intranet client, the load balancing equipment queries whether the equivalent service table has a public network IPv6 address corresponding to the public network IPv4 address of the extranet server. If not, the load balancing equipment selects the ISP link from the ISP links based on the IPv4 address by using a link load balancing strategy, and the process is not repeated herein. If so, the load balancing device selects an ISP link from the ISP link based on the IPv4 address and the ISP link based on the IPv6 address. Further, when the selected ISP link is an ISP link based on the IPv4 address, the relevant processing is not described herein again.
And 9, when the selected ISP link is the ISP link based on the IPv6 address, the load balancing equipment executes NAT (network address translation) translation related processing.
Specifically, the load balancing device modifies the destination IP address of the service request packet into the corresponding IPv6 public network address recorded in the equivalent service table, modifies the source IP address of the service request packet into the IPv6 public network address of the load balancing device (i.e., the IPv6ISP egress public network address), records a correspondence relationship between the source IP address of the service request packet before conversion (i.e., the IP address of the intranet client carried in the service request packet), the destination IP address of the service request packet before conversion (i.e., the IPv4 public network address of the extranet server carried in the service request packet), the source IP address of the service request packet after conversion (i.e., the IPv6 public network address of the load balancing device), and the destination IP address of the service request packet after conversion (i.e., the IPv6 public network address of the extranet server), so as to ensure that the service response packet can be returned to the intranet client.
Step 10, the load balancing device sends the modified service request message through the selected ISP link, that is, the load balancing device sends the service request message to the extranet server through the selected ISP link.
As shown in the application scenario diagram shown in fig. 5, taking an intranet client as an IPv6 user as an example, in this application scenario, the link load balancing method includes the following steps:
step 1, an intranet client sends a DNS request message to load balancing equipment, wherein the DNS request message is an AAAA type query of DNS, and domain name information carried in the DNS request message is a.com.
And 2, after receiving the DNS request message, the load balancing equipment records the corresponding relation between a DNS query record (such as a.com) of the intranet client and the source IP address of the intranet client through a DNS request table.
And 3, the load balancing equipment sends a class A query request of the DNS to request the IPv4 public network address of the external network server corresponding to the domain name (a.com), and sends an AAAA query request of the DNS to request the IPv6 public network address of the external network server corresponding to the domain name (a.com).
In the embodiment of the present invention, since the DNS request message is an AAAA-type query of the DNS, the DNS request message carrying domain name information from the intranet client carries an IPv6 address of the DNS server, and the load balancing device sends the a-type query request of the DNS server to the DNS server through the IPv6 public network address of the load balancing device, requests the IPv4 public network address of the external network server corresponding to the domain name (a.com), and sends the AAAA-type query request of the DNS server to the DNS server through the IPv6 public network address of the load balancing device, and requests the IPv6 public network address of the external network server corresponding to the domain name (a.com).
And 4, the DNS server sends the IPv4 public network address of the external network server corresponding to the domain name (a.com) to the load balancing equipment through the class A response of the DNS, and sends the IPv6 public network address of the external network server corresponding to the domain name (a.com) to the load balancing equipment through the AAAA response of the DNS.
The IPv4 public network address of the external network server sent by the DNS server to the load balancing device may be a plurality of IPv4 public network addresses of the external network server; the IPv6 public network address of the external network server sent by the DNS server to the load balancing device may be a plurality of IPv6 public network addresses of the external network server.
Step 5, the load balancing device records the corresponding relation between the IPv4 public network address (such as 100.1.1.1) of the outer network server and the IPv6 public network address (such as 88:: 8) of the outer network server in the equivalent service table; these IPv4 public network addresses and IPv6 public network addresses correspond to the same extranet server (with a.com domain name) and are recorded in the load balancing device as different protocol family addresses that can provide the same service.
And step 6, the load balancing equipment queries a DNS request table (records a DNS query record of the intranet client and a source IP address of the intranet client), obtains the source IP address of the intranet client, constructs an AAAA type response of the DNS and returns the IPv6 public network address (such as 88:: 8) of the external network server to the intranet client.
In addition, the load balancing equipment can also carry out proximity detection on the IPv4 public network address (such as 100.1.1.1) and the IPv6 public network address (such as 88:: 8) of the extranet server; if a plurality of groups of ISP links based on IPv4 addresses or a plurality of groups of ISP links based on IPv6 addresses exist, the proximity detection detects the IPv4 public network address of the external network server in the ISP links based on the IPv4 addresses, and detects the IPv6 public network address of the external network server in the ISP links based on the IPv6 addresses, and the best exit link is obtained and recorded in the proximity table entry.
And 7, the intranet client sends a service request message to the load balancing equipment, wherein the source IP address of the service request message is the IPv6 address of the intranet client, and the destination IP address of the service request message is the public network IPv6 address of the extranet server (such as 88:: 8).
And 8, after receiving the service request message from the intranet client, the load balancing equipment queries whether the equivalent service table has a public network IPv4 address corresponding to the public network IPv6 address of the extranet server. If not, the load balancing equipment selects the ISP link from the ISP links based on the IPv6 address by using a link load balancing strategy, and the process is not repeated herein. If so, the load balancing device selects an ISP link from the ISP link based on the IPv4 address and the ISP link based on the IPv6 address. Further, when the selected ISP link is an ISP link based on the IPv6 address, the relevant processing is not described herein again.
And 9, when the selected ISP link is the ISP link based on the IPv4 address, the load balancing equipment executes NAT (network address translation) translation related processing.
Specifically, the load balancing device modifies the destination IP address of the service request packet into the corresponding IPv4 public network address recorded in the equivalent service table, modifies the source IP address of the service request packet into the IPv4 public network address of the load balancing device (i.e., the IPv4ISP egress public network address), records a correspondence relationship between the source IP address of the service request packet before conversion (i.e., the IP address of the intranet client carried in the service request packet), the destination IP address of the service request packet before conversion (i.e., the IPv6 public network address of the extranet server carried in the service request packet), the source IP address of the service request packet after conversion (i.e., the IPv4 public network address of the load balancing device), and the destination IP address of the service request packet after conversion (i.e., the IPv4 public network address of the extranet server), so as to ensure that the service response packet can be returned to the intranet client.
Step 10, the load balancing device sends the modified service request message through the selected ISP link, that is, the load balancing device sends the service request message to the extranet server through the selected ISP link.
Based on the same inventive concept as the above method, an embodiment of the present invention further provides a load balancing device, which is applied to a network including an intranet client, the load balancing device, a domain name system DNS server, and an extranet server, where an internet service provider ISP link based on a first type of IP address and an ISP link based on a second type of IP address exist between the load balancing device and the extranet server, and as shown in fig. 6, the load balancing device specifically includes:
the communication module 11 is configured to receive a DNS request packet carrying domain name information from an intranet client, and request the DNS server for a first type of IP address of an extranet server corresponding to the domain name information and a second type of IP address of the extranet server corresponding to the domain name information; receiving a first class IP address of an external network server from the DNS server and a second class IP address of the external network server, and recording a corresponding relation between the first class IP address of the external network server and the second class IP address of the external network server in an equivalent service table; receiving a service request message from an intranet client, wherein the destination IP address of the service request message is a first-class IP address of an extranet server;
a selecting module 12, configured to select, when there is a second type IP address of the external network server corresponding to the first type IP address of the external network server in the equivalent service table, an ISP link from ISP links based on the first type IP address and ISP links based on the second type IP address by using a link load balancing policy;
and the processing module 13 is configured to modify a source IP address of the service request packet into a second type IP address of the load balancing device when the selected ISP link is an ISP link based on the second type IP address, modify a destination IP address of the service request packet into the second type IP address of the external network server corresponding to the first type IP address of the external network server, and send the modified service request packet through the selected ISP link.
The processing module 13 is further configured to record a corresponding relationship between an IP address of the intranet client carried in the service request packet, a first class IP address of the extranet server carried in the service request packet, a second class IP address of the load balancing device, and a second class IP address of the extranet server after modifying a source IP address of the service request packet into the second class IP address of the load balancing device and modifying a destination IP address of the service request packet into the second class IP address of the extranet server;
the communication module 11 is further configured to receive a service response packet from the external network server, where a source IP address of the service response packet is a second-class IP address of the external network server, and a destination IP address of the service response packet is a second-class IP address of the load balancing device;
the processing module 13 is further configured to query the corresponding relationship through a second type IP address of the extranet server and a second type IP address of the load balancing device, so as to obtain an IP address of the intranet client and a first type IP address of the extranet server, which are recorded in the corresponding relationship; and modifying the source IP address of the service response message into a first class IP address of the extranet server, modifying the destination IP address of the service response message into the IP address of the intranet client, and sending the modified service response message to the intranet client.
The processing module 13 is further configured to, after an ISP link is selected from an ISP link based on a first type of IP address and an ISP link based on a second type of IP address by using a link load balancing policy, modify a source IP address of the service request packet into the first type of IP address of the load balancing device when the selected ISP link is the ISP link based on the first type of IP address, send the modified service request packet through the selected ISP link, and record a correspondence relationship between an IP address of an intranet client carried in the service request packet, the first type of IP address of an extranet server carried in the service request packet, and the first type of IP address of the load balancing device;
the communication module 11 is further configured to receive a service response packet from the external network server, where a source IP address of the service response packet is a first-class IP address of the external network server, and a destination IP address of the service response packet is a first-class IP address of the load balancing device;
the processing module 13 is further configured to query the corresponding relationship through the first type IP address of the extranet server and the first type IP address of the load balancing device to obtain the IP address of the intranet client recorded in the corresponding relationship, modify the destination IP address of the service response packet into the IP address of the intranet client, and send the modified service response packet to the intranet client.
The processing module 13 is further configured to, when the link load balancing policy needs to select an ISP link from ISP links based on the first type IP addresses and ISP links based on the second type IP addresses based on a proximity table, perform proximity detection on the first type IP addresses of the extranet servers through the ISP links based on the first type IP addresses, perform proximity detection on the second type IP addresses of the extranet servers through the ISP links based on the second type IP addresses, and maintain the proximity table by using a result of detecting the first type IP addresses of the extranet servers and a result of detecting the second type IP addresses of the extranet servers.
The first type of IP address is an IPv4 address, and the second type of IP address is an IPv6 address; or,
the first type of IP address is an IPv6 address, and the second type of IP address is an IPv4 address.
The modules of the device can be integrated into a whole or can be separately deployed. The modules can be combined into one module, and can also be further split into a plurality of sub-modules.
Through the above description of the embodiments, those skilled in the art will clearly understand that the present invention may be implemented by software plus a necessary general hardware platform, and certainly may also be implemented by hardware, but in many cases, the former is a better embodiment. Based on such understanding, the technical solutions of the present invention may be embodied in the form of a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute the methods according to the embodiments of the present invention.
Those skilled in the art will appreciate that the drawings are merely schematic representations of one preferred embodiment and that the blocks or flow diagrams in the drawings are not necessarily required to practice the present invention.
Those skilled in the art will appreciate that the modules in the devices in the embodiments may be distributed in the devices in the embodiments according to the description of the embodiments, and may be correspondingly changed in one or more devices different from the embodiments. The modules of the above embodiments may be combined into one module, or further split into multiple sub-modules.
The above-mentioned serial numbers of the embodiments of the present invention are merely for description and do not represent the merits of the embodiments.
The above disclosure is only for a few specific embodiments of the present invention, but the present invention is not limited thereto, and any variations that can be made by those skilled in the art are intended to fall within the scope of the present invention.
Claims (8)
1. A link load balancing method is applied to a network comprising an internal network client, load balancing equipment, a Domain Name System (DNS) server and an external network server, wherein an Internet Service Provider (ISP) link based on a first type of IP address and an ISP link based on a second type of IP address exist between the load balancing equipment and the external network server, and the method is characterized by comprising the following steps of:
the load balancing equipment receives a DNS request message carrying domain name information from an intranet client, and requests a DNS server for a first-class IP address of an extranet server corresponding to the domain name information and a second-class IP address of the extranet server corresponding to the domain name information;
the load balancing equipment receives a first class of IP address of an external network server from the DNS server and a second class of IP address of the external network server, and records the corresponding relation between the first class of IP address of the external network server and the second class of IP address of the external network server in an equivalent service table;
the load balancing equipment receives a service request message from an intranet client, wherein the destination IP address of the service request message is a first-class IP address of an extranet server;
when the equivalent service table has a second type of IP address of the external network server corresponding to the first type of IP address of the external network server, the load balancing equipment selects an ISP link from ISP links based on the first type of IP address and ISP links based on the second type of IP address by using a link load balancing strategy;
when the selected ISP link is based on a second-class IP address, the load balancing equipment modifies a source IP address of the service request message into the second-class IP address of the load balancing equipment, modifies a target IP address of the service request message into the second-class IP address of the external network server corresponding to the first-class IP address of the external network server, and transmits the modified service request message through the selected ISP link;
wherein the method further comprises:
the load balancing equipment modifies a source IP address of a service request message into a second type IP address of the load balancing equipment, modifies a destination IP address of the service request message into a second type IP address of an external network server, and records the corresponding relation among the IP address of the internal network client carried in the service request message, the first type IP address of the external network server carried in the service request message, the second type IP address of the load balancing equipment and the second type IP address of the external network server;
the load balancing equipment receives a service response message from the external network server, the source IP address of the service response message is the second-class IP address of the external network server, and the destination IP address of the service response message is the second-class IP address of the load balancing equipment;
the load balancing equipment queries the corresponding relation through a second type IP address of the external network server and the second type IP address of the load balancing equipment to obtain the IP address of the internal network client and the first type IP address of the external network server which are recorded in the corresponding relation;
and the load balancing equipment modifies the source IP address of the service response message into the first class IP address of the external network server, modifies the destination IP address of the service response message into the IP address of the internal network client, and sends the modified service response message to the internal network client.
2. The method of claim 1, wherein after the load balancing device selects an ISP link from among ISP links based on a first type of IP address and ISP links based on a second type of IP address using a link load balancing policy, the method further comprises:
when the selected ISP link is based on a first-class IP address, the load balancing equipment modifies the source IP address of the service request message into the first-class IP address of the load balancing equipment, sends the modified service request message through the selected ISP link, and records the corresponding relation among the IP address of the intranet client carried in the service request message, the first-class IP address of the extranet server carried in the service request message and the first-class IP address of the load balancing equipment;
the load balancing equipment receives a service response message from the external network server, wherein the source IP address of the service response message is the first-class IP address of the external network server, and the destination IP address of the service response message is the first-class IP address of the load balancing equipment;
the load balancing equipment queries the corresponding relation through the first-class IP address of the external network server and the first-class IP address of the load balancing equipment to obtain the IP address of the internal network client recorded in the corresponding relation, modifies the target IP address of the service response message into the IP address of the internal network client, and sends the modified service response message to the internal network client.
3. The method of claim 1, wherein when the link load balancing policy requires selection of an ISP link from among ISP links based on a first type of IP address and ISP links based on a second type of IP address based on a proximity table, the method further comprises:
the load balancing equipment carries out proximity detection on the first class IP address of the external network server through the ISP link based on the first class IP address, carries out proximity detection on the second class IP address of the external network server through the ISP link based on the second class IP address, and maintains a proximity table by using a result of detecting the first class IP address of the external network server and a result of detecting the second class IP address of the external network server.
4. The method according to any one of claims 1 to 3,
the first type of IP address is an IPv4 address, and the second type of IP address is an IPv6 address; or,
the first type of IP address is an IPv6 address, and the second type of IP address is an IPv4 address.
5. A load balancing device is applied to a network comprising an internal network client, the load balancing device, a Domain Name System (DNS) server and an external network server, wherein an Internet Service Provider (ISP) link based on a first type of IP address and an ISP link based on a second type of IP address exist between the load balancing device and the external network server, and the load balancing device is characterized by specifically comprising:
the communication module is used for receiving a DNS request message carrying domain name information from an intranet client, and requesting a first-class IP address of an extranet server corresponding to the domain name information and a second-class IP address of the extranet server corresponding to the domain name information from the DNS server; receiving a first class IP address of an external network server from the DNS server and a second class IP address of the external network server, and recording a corresponding relation between the first class IP address of the external network server and the second class IP address of the external network server in an equivalent service table; receiving a service request message from an intranet client, wherein the destination IP address of the service request message is a first-class IP address of an extranet server;
a selecting module, configured to select, when there is a second type IP address of the external network server corresponding to the first type IP address of the external network server in the equivalent service table, an ISP link from ISP links based on the first type IP address and ISP links based on the second type IP address by using a link load balancing policy;
the processing module is used for modifying the source IP address of the service request message into the second type IP address of the load balancing equipment when the selected ISP link is the ISP link based on the second type IP address, modifying the target IP address of the service request message into the second type IP address of the outer network server corresponding to the first type IP address of the outer network server, and sending the modified service request message through the selected ISP link;
the processing module is further configured to record a corresponding relationship between an IP address of an intranet client carried in a service request packet, a first class IP address of an extranet server carried in the service request packet, a second class IP address of the load balancing device, and a second class IP address of an extranet server after modifying a source IP address of the service request packet into the second class IP address of the load balancing device and modifying a destination IP address of the service request packet into the second class IP address of the extranet server;
the communication module is further configured to receive a service response packet from the external network server, where a source IP address of the service response packet is a second-class IP address of the external network server, and a destination IP address of the service response packet is a second-class IP address of the load balancing device;
the processing module is further configured to query the corresponding relationship through a second type of IP address of the external network server and a second type of IP address of the load balancing device, so as to obtain an IP address of the internal network client and a first type of IP address of the external network server, which are recorded in the corresponding relationship; and modifying the source IP address of the service response message into a first class IP address of the extranet server, modifying the destination IP address of the service response message into the IP address of the intranet client, and sending the modified service response message to the intranet client.
6. The load balancing apparatus of claim 5,
the processing module is further configured to, after an ISP link is selected from an ISP link based on a first type of IP address and an ISP link based on a second type of IP address by using a link load balancing policy, modify a source IP address of the service request packet into the first type of IP address of the load balancing device when the selected ISP link is the ISP link based on the first type of IP address, send the modified service request packet through the selected ISP link, and record a correspondence relationship between an IP address of an intranet client carried in the service request packet, the first type of IP address of an extranet server carried in the service request packet, and the first type of IP address of the load balancing device;
the communication module is further configured to receive a service response packet from the external network server, where a source IP address of the service response packet is a first-class IP address of the external network server, and a destination IP address of the service response packet is a first-class IP address of the load balancing device;
the processing module is further configured to query the corresponding relationship through the first-class IP address of the extranet server and the first-class IP address of the load balancing device to obtain the IP address of the intranet client recorded in the corresponding relationship, modify the destination IP address of the service response packet into the IP address of the intranet client, and send the modified service response packet to the intranet client.
7. The load balancing apparatus of claim 5,
the processing module is further configured to, when the link load balancing policy needs to select an ISP link from ISP links based on the first type IP addresses and ISP links based on the second type IP addresses based on the proximity table, perform proximity detection on the first type IP addresses of the extranet servers through the ISP links based on the first type IP addresses, perform proximity detection on the second type IP addresses of the extranet servers through the ISP links based on the second type IP addresses, and maintain the proximity table by using a result of detecting the first type IP addresses of the extranet servers and a result of detecting the second type IP addresses of the extranet servers.
8. Load balancing device according to any one of claims 5 to 7,
the first type of IP address is an IPv4 address, and the second type of IP address is an IPv6 address; or,
the first type of IP address is an IPv6 address, and the second type of IP address is an IPv4 address.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201310331543.7A CN103401800B (en) | 2013-07-31 | 2013-07-31 | A kind of balancing link load method and apparatus |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201310331543.7A CN103401800B (en) | 2013-07-31 | 2013-07-31 | A kind of balancing link load method and apparatus |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN103401800A CN103401800A (en) | 2013-11-20 |
| CN103401800B true CN103401800B (en) | 2016-08-03 |
Family
ID=49565329
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201310331543.7A Active CN103401800B (en) | 2013-07-31 | 2013-07-31 | A kind of balancing link load method and apparatus |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN103401800B (en) |
Families Citing this family (14)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104767690B (en) * | 2014-01-08 | 2018-11-27 | 杭州迪普科技股份有限公司 | A kind of flow scheduling device and method |
| CN104935521B (en) * | 2014-03-18 | 2018-11-16 | 中国电信股份有限公司 | For realizing the Whole load equalizing method and server of mixed scheduling |
| CN104144222B (en) * | 2014-08-20 | 2015-08-19 | 北京阅联信息技术有限公司 | Based on the load-balancing method of canonical name and system in DNS authoring system |
| CN105376168B (en) | 2014-08-25 | 2019-06-11 | 深圳市中兴微电子技术有限公司 | A kind of method and apparatus of load balancing |
| CN106209411B (en) * | 2015-05-08 | 2019-06-07 | 阿里巴巴集团控股有限公司 | Distributed network system (DNS) fault-tolerance approach, device and fault tolerant type distributed network system (DNS) |
| CN105591962B (en) * | 2015-08-03 | 2019-09-17 | 新华三技术有限公司 | A kind of detection method and device of balancing link load |
| CN107086966B (en) * | 2016-02-16 | 2021-07-27 | 阿里巴巴集团控股有限公司 | Network load balancing, control and network interaction method and device |
| CN106100926A (en) * | 2016-06-17 | 2016-11-09 | 山东超越数控电子有限公司 | A kind of Network Load Balance link physical examination method |
| CN106534398A (en) * | 2016-11-14 | 2017-03-22 | 赛尔网络有限公司 | Device and method used for IPv6 network |
| CN108173979B (en) * | 2017-12-25 | 2021-03-12 | 新华三信息安全技术有限公司 | Message processing method, device, equipment and storage medium |
| US10536380B2 (en) | 2018-01-26 | 2020-01-14 | Wipro Limited | Method and system for intelligent link load balancing |
| CN109120745B (en) * | 2018-09-25 | 2021-09-21 | 京信网络系统股份有限公司 | Shunting gateway link switching method and device, computer storage medium and equipment |
| CN114363288B (en) * | 2021-12-16 | 2024-08-06 | 北京华耀科技有限公司 | Message processing method, device, link load balancing equipment and storage medium |
| CN115766588A (en) * | 2022-12-20 | 2023-03-07 | 北京天融信网络安全技术有限公司 | A load balancing method, device, electronic equipment and storage medium |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1585376A (en) * | 2003-08-20 | 2005-02-23 | 华为技术有限公司 | Addressing converting method and mixed addressing converting router for realizing it |
| CN101197858A (en) * | 2008-01-07 | 2008-06-11 | 杭州华三通信技术有限公司 | Address translation method, device and router with the same |
| CN102075445A (en) * | 2011-02-28 | 2011-05-25 | 杭州华三通信技术有限公司 | Load balancing method and device |
| CN102739810A (en) * | 2011-04-07 | 2012-10-17 | 中国电信股份有限公司 | IPv4CP/SP and IPv6 network interworking method and device |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| KR100901790B1 (en) * | 2006-12-04 | 2009-06-11 | 한국전자통신연구원 | CONTROL TUNNEL AND DIRECT TUNNEL CONFIGURATION METHOD IN IPv6 SERVICE PROVIDE SYSTEM BASED IPv4 NETWORK |
-
2013
- 2013-07-31 CN CN201310331543.7A patent/CN103401800B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1585376A (en) * | 2003-08-20 | 2005-02-23 | 华为技术有限公司 | Addressing converting method and mixed addressing converting router for realizing it |
| CN101197858A (en) * | 2008-01-07 | 2008-06-11 | 杭州华三通信技术有限公司 | Address translation method, device and router with the same |
| CN102075445A (en) * | 2011-02-28 | 2011-05-25 | 杭州华三通信技术有限公司 | Load balancing method and device |
| CN102739810A (en) * | 2011-04-07 | 2012-10-17 | 中国电信股份有限公司 | IPv4CP/SP and IPv6 network interworking method and device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN103401800A (en) | 2013-11-20 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN103401800B (en) | A kind of balancing link load method and apparatus | |
| US10097566B1 (en) | Identifying targets of network attacks | |
| US10200402B2 (en) | Mitigating network attacks | |
| US11743230B2 (en) | Network address translation (NAT) traversal and proxy between user plane function (UPF) and session management function (SMF) | |
| KR102138619B1 (en) | Message clustering method and load balancer based on server cluster | |
| US9742795B1 (en) | Mitigating network attacks | |
| US11799821B2 (en) | Service chains for inter-cloud traffic | |
| US9843554B2 (en) | Methods for dynamic DNS implementation and systems thereof | |
| US8984112B2 (en) | Internet address information processing method, apparatus, and internet system | |
| CN105323173B (en) | Method and device for setting network rule entry | |
| US8578468B1 (en) | Multi-factor client authentication | |
| CN107528862B (en) | Domain name resolution method and device | |
| JP2014511089A (en) | Private address and public address mapping | |
| EP4002796A1 (en) | Resource acquisition method and edge computing scheduling server | |
| CN103618801B (en) | Method, equipment and the system of a kind of P2P resource-sharing | |
| CN107094110B (en) | DHCP message forwarding method and device | |
| AU2015264883A1 (en) | Access control method and system, and access point | |
| CN107547339B (en) | Method and device for feeding back MAC address of gateway media access control | |
| CN105681249B (en) | A network access method and network conversion device | |
| CN106027354B (en) | The reflow method and device of VPN client | |
| US9697173B2 (en) | DNS proxy service for multi-core platforms | |
| CN104092751B (en) | A kind of Operational Visit method and apparatus | |
| CN109246024B (en) | Method, device, terminal equipment and storage medium for load sharing in networking | |
| CN103051544B (en) | Realize method and the access device of IPv4 private network access IPv6 network | |
| CN113645326B (en) | Quasi-stateless adaptive mapping method for IPv4/IPv6 access |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| CP03 | Change of name, title or address | ||
| CP03 | Change of name, title or address |
Address after: 310052 Binjiang District Changhe Road, Zhejiang, China, No. 466, No. Patentee after: Xinhua three Technology Co., Ltd. Address before: 310053 Hangzhou hi tech Industrial Development Zone, Zhejiang province science and Technology Industrial Park, No. 310 and No. six road, HUAWEI, Hangzhou production base Patentee before: Huasan Communication Technology Co., Ltd. |