TWI746506B - Method and device for network load balancing, control and network interaction - Google Patents

Abstract

The invention provides a method and device for network load balancing, control and network interaction. The method includes: receiving preset traffic scheduling rules sent by the control device and the unique path indication information of the back-end server in the second type of network; Information about the unique path instruction of the similar network; send the back-end server access request to the back-end server selected according to the preset traffic scheduling rules; receive the request response information returned by the back-end server, and follow the client's unique path instruction The information returns the request response information to the client. The unique path indicates that the information uniquely exists in the first type of network where the client is located and the second type of network where each back-end server is located. The first type of network and the second type of network At least one of the similar networks is a virtual private network VPC, and the solution of the present invention can eliminate the need for the gateway to perform address translation processing on the client and the back-end server.

Description

Method and device for network load balancing, control and network interaction

The present invention relates to the field of Internet technology, in particular to a network load balancing method and a network load balancing device, as well as a network load balancing control method and a network load balancing control device, and a network An interactive method and a network interactive device.

With the development of Internet technology, the access traffic from the client to the server is becoming larger and more frequent, and the scalability of the server is becoming more and more important. In order to facilitate client access, multiple extended back-end servers are usually virtualized as a virtual server to unify the interface for providing services to the outside world. Between the client and the back-end server, the Load Balancer (LB) usually dispatches the access traffic to the back-end server (Real Server, RS) that actually provides the service according to a certain algorithm to balance Access traffic from multiple back-end servers.

For some clients in the VPC (Virtual Private Cloud) domain established based on VXLAN (Virtual eXtensible Local Area Network), their address is only unique within the domain and cannot directly access devices outside the domain. So need to go through Address translation processing of the gateway. When accessing a device outside the domain, the address needs to be converted to a non-VPC address through the gateway, so that the back-end server can be accessed smoothly through the scheduling of the load balancer.

In addition, when the load balancer schedules access traffic to the back-end server in the VPC domain, because its address is only unique in its domain, the load balancer cannot directly perform traffic scheduling processing, and it also needs to pass the gateway to the server. Only when the address is converted from a non-VPC address can the scheduling process be realized.

In the process of the client's access to the back-end server, the original VPC addresses of the client and the server need to be converted by the gateway. The problem of low access efficiency. In addition, after the gateway conversion process, the load balancer cannot know the real network address of the client, and cannot precisely access and control the client. Furthermore, address translation will consume traditional IP addresses.

In view of the above problems, embodiments of the present invention are proposed to provide a network load balancing method and a corresponding network load balancing device that overcome the above problems or at least partially solve the above problems, and a network load balance A control method and a corresponding network load balancing control device, as well as a network interaction method and a network interaction device.

In order to solve the above problems, the present invention discloses a network load balancing method, including: Receive the preset traffic scheduling rules sent by the control device and the unique path indication information of the back-end server in the second type of network; from the back-end server access request sent by the client, obtain that the client is in the first type The unique path indication information of the network; according to the unique path indication information of the back-end server, the back-end server access request is sent to at least one back-end server selected according to the preset traffic scheduling rule ; Receive the request response information returned by the back-end server, and return the request response information to the client according to the unique path indication information of the client, where the unique path indication information is in the client The first type of network where the end is located and the second type of network where each back-end server is located, and at least one of the first type of network and the second type of network is a virtual private network VPC .

Optionally, the unique path indication information is generated from the network identification information of the virtual private network VPC where it is located and the address identification information in the virtual private network VPC.

Optionally, it also includes: correspondingly accessing multiple back-end servers according to the unique path indication information of multiple back-end application servers; checking the running status of the accessed back-end servers, and targeting the back-end servers with abnormal status , Marking an abnormality identifier on the corresponding unique path indication information; the abnormality identifier is used to instruct to suspend sending the back-end server access request to the back-end server.

Optionally, in the back-end server access request sent from the client In the step of obtaining the unique path indication information of the client in the first type of network, the method further includes: identifying the network type of the first type of network where the client is located.

Optionally, in the back-end server access request sent from the client, the step of obtaining the unique path indication information of the client in the first type of network includes: a network for the first type of network Type, unblock the network identification information of the first type of network and the address identification information of the client from the back-end server access request, and generate unique path indication information of the client.

Optionally, the step of returning the request response information to the client includes: encapsulating the request response information for the network type of the first type of network and sending it to the client.

Optionally, in the back-end server access request sent from the client, before the step of obtaining the unique path indication information of the client in the first type of network, the method further includes: receiving and saving multiple The network identification information of the first type of network in which the client is located is submitted when a client registers with the control device; in the back-end server access request sent from the client, the client is acquired After the step of indicating information for the unique path of the terminal, the method further includes: determining whether the network identification information of the first type of network obtained from the back-end server access request is in the stored network of the first type of network Logo Information If not, return access denied information to the client.

In order to solve the above problem, the present invention also discloses a network load balancing control method, which includes: obtaining the unique path indication information of the back-end server in the second type of network from each back-end server; The scheduling rules and the unique path indication information of the back-end server are sent to the load balancing device, so that the load balancing device can access the back-end server of the client according to the unique path indication information of the back-end server The request is sent to at least one back-end server selected in accordance with the preset traffic scheduling rule, and the request returned by the back-end server according to the unique path indication information of the client in the first type of network The response information is returned to the client, where the unique path indication information uniquely exists in the first type of network where the client is located and the second type of network where each back-end server is located, the first type At least one of the network and the second type of network is a virtual private network VPC.

Optionally, the unique path indication information is generated from the network identification information of the virtual private network VPC where it is located and the address identification information in the virtual private network VPC.

Optionally, the method further includes: instructing the load balancing device to send the unique path indication information of the load balancing device to the back-end server, so that the back-end server can follow the unique path of the load balancing device Indicating information, returning request response information to the load balancing device.

Optionally, it also includes: Receiving the network identification information of the first type of network where the client is located, submitted by the client during registration; sending the network identification information of the first type of network to the load balancing device for The load balancing device saves and, when receiving the back-end server access request of the client, determines whether the network identification information of the first type of network obtained from the back-end server access request is in the saved first Within the range of the network identification information of a type of network, if not, return the access denied information to the client.

In order to solve the above problems, the present invention also discloses a network interaction method, which includes: according to the unique path indication information of the back-end server in the second type of network, sending the client's access request to the back-end server to the At least one back-end server selected by the preset traffic scheduling rule, the second type of network is a virtual private network VPC; and/or, according to the unique path instruction of the client in the first type of network Information, the request response information returned by the back-end server for the client's access request is returned to the client. The first type of network is a virtual private network VPC; wherein the unique path indication information is in the client The only existence in the first type of network where the end is located and the second type of network where each back-end server is located.

In order to solve the above problems, the present invention also discloses a network load balancing device, including: a preset flow scheduling rule receiving module, configured to receive the preset flow scheduling rule sent by the control device, and the back-end server in the second Network-like A path indication information; an information acquisition module for obtaining the unique path indication information of the client in the first type of network from the back-end server access request sent by the client; the back-end server access request sending module Group, used to send the back-end server access request to at least one back-end server selected according to the preset traffic scheduling rule according to the unique path indication information of the back-end server; request response information The return module is used to receive the request response information returned by the back-end server, and return the request response information to the client according to the unique path indication information of the client, wherein the unique path indication Information only exists in the first type of network where the client is located and the second type of network where each back-end server is located, and at least one of the first type of network and the second type of network is virtual private Network VPC.

Optionally, the unique path indication information is generated from the network identification information of the virtual private network VPC where it is located and the address identification information in the virtual private network VPC.

Optionally, it further includes: a back-end server access module for correspondingly accessing multiple back-end servers according to the unique path indication information of the multiple back-end application servers.

The running status check module is used to check the running status of the accessed back-end server. For the back-end server with abnormal status, mark the abnormal identifier on the corresponding unique path indication information; the abnormal identifier is used to indicate the suspension of sending The back-end server access request to the back-end server.

Optionally, it further includes: a network type identification module for identifying the network type of the first type of network where the client is located.

Optionally, the information acquisition module includes: a back-end server access request unblocking sub-module for unblocking the back-end server access request for the network type of the first type of network The network identification information of the first type of network and the address identification information of the client are sealed, and unique path indication information of the client is generated.

Optionally, the request response information return module includes: a request response information encapsulation sub-module for encapsulating the request response information for the network type of the first type of network and sending it to the client .

Optionally, it further includes: a network identification information receiving module, configured to receive and save the network identification information of the first type of network where the client is located, submitted when multiple clients register with the control device The device also includes: a network identification information determination module, used to determine whether the network identification information of the first type of network obtained from the back-end server access request is in the stored first type of network Within the range of the network identification information, if not, return the access denied information to the client.

In order to solve the above-mentioned problems, the present invention also discloses a network load balancing control device, including: a back-end server unique path indication information acquisition module, which is used to obtain information from each back-end server The end server obtains the unique path indication information of the back-end server in the second type of network; the preset traffic scheduling rule sending module is used to indicate the preset traffic scheduling rule and the unique path of the back-end server The information is sent to the load balancing device, so that the load balancing device sends the back-end server access request of the client to the selection according to the preset traffic scheduling rule according to the unique path indication information of the back-end server And return the request response information returned by the back-end server to the client according to the unique path indication information of the client in the first type of network. The unique path indication information uniquely exists in the first type of network where the client is located and the second type of network where each back-end server is located, at least one of the first type of network and the second type of network It is a virtual private network VPC.

Optionally, the unique path indication information is generated from the network identification information of the virtual private network VPC where it is located and the address identification information in the virtual private network VPC.

Optionally, it further includes: a sending instruction module for instructing the load balancing device to send the unique path instruction information of the load balancing device to the back-end server, so that the back-end server can follow The unique path indication information of the load balancing device returns request response information to the load balancing device.

Optionally, it further includes: a network identification information receiving module, configured to receive the network identification information of the first type of network where the client is located, submitted by the client during registration; The network identification information sending module is used to send the network identification information of the first type of network to the load balancing device for the load balancing device to save and receive the back-end server of the client In the case of a server access request, it is determined whether the network identification information of the first type of network obtained from the back-end server access request is within the range of the saved network identification information of the first type of network, if not, then Return the access denied information to the client.

In order to solve the above-mentioned problems, the present invention also discloses a network interaction device, including: an access request sending module, which is used to connect the client to the back-end server according to the unique path indication information of the back-end server in the second type of network The access request of the server is sent to at least one back-end server selected according to the preset traffic scheduling rule, the second type of network is a virtual private network VPC; and/or the request response information return module, It is used to return the request response information returned by the back-end server for the client's access request to the client according to the unique path indication information of the client in the first type of network, and the first type of network is a virtual Private network VPC; wherein the unique path indication information uniquely exists in the first type of network where the client is located and the second type of network where each back-end server is located.

According to the embodiment of the present invention, the load balancer sends the access request to the back-end server by using the unique path indication information of the back-end server issued by the control device, and the load balancer accesses the back-end server by using the back-end server sent by the client. Request to obtain the unique path indication information of the client, and forward the request response information returned by the back-end server to the client. Since the unique path between the client and the back-end server indicates that the information is in the first type of network where the client is located and Each back-end server only exists in the second type of network. Therefore, when at least one of the first type of network and the second type of network is a virtual private network VPC, there is no need for a gateway to connect the client and The address translation processing of the back-end server avoids the access delay caused by the gateway's address translation processing, and improves the client's access efficiency to the back-end server and the return efficiency of the back-end server's request response information. Save the processing resources of the gateway. Moreover, since there is no need to convert the addresses of the client and the back-end server, the consumption of non-VPC IP addresses by the client and the back-end server is saved.

In addition, the embodiment of the present invention does not need to go through the gateway for conversion processing, and the load balancer can obtain the real network address of the client, so that the client can be accurately controlled.

501‧‧‧Receiving module for preset traffic scheduling rules

502‧‧‧Information Acquisition Module

503‧‧‧Back-end server access request sending module

504‧‧‧Request response information return module

601‧‧‧Network identification information receiving module

602‧‧‧Receiving module for preset traffic scheduling rules

603‧‧‧Back-end server access module

604‧‧‧Operation status check module

605‧‧‧Network Type Identification Module

606‧‧‧Information Acquisition Module

607‧‧‧Network Identification Information Judgment Module

608‧‧‧Back-end server access request sending module

609‧‧‧Request response information return module

701‧‧‧Back-end server unique path indication information acquisition module

702‧‧‧Pre-set flow scheduling rule sending module

801‧‧‧Access request sending module

802‧‧‧Request response information return module

Client‧‧‧Client

LB‧‧‧Load Balancer

RS1‧‧‧Backend server

RS2‧‧‧Back-end server

RS3‧‧‧Back-end server

RS4‧‧‧Back-end server

Figure 1 is a flow chart of the steps of Embodiment 1 of a network load balancing method of the present invention; Figure 2 is a flow chart of the steps of Embodiment 2 of a network load balancing method of the present invention; Figure 3 is a network of the present invention Fig. 4 is a step flowchart of an embodiment of a network interaction method of the present invention; Fig. 5 is a structural frame of embodiment 1 of a network load balancing device of the present invention picture; Fig. 6 is a structural block diagram of Embodiment 2 of a network load balancing device of the present invention; Fig. 7 is a structural block diagram of an embodiment of a network load balancing control device of the present invention; Fig. 8 is a network of the present invention Fig. 9 is a schematic diagram of the working principle of a current load balancer; Fig. 10 is a schematic diagram of a current working principle of load balancing using a gateway; Fig. 11 is a load balancing method of the present invention Figure 12 is a schematic diagram of application scenario two of a load balancing method of the present invention; Figure 13 is a schematic diagram of application scenario three of a load balancing method of the present invention; Figure 14 is a schematic diagram of application scenario three of a load balancing method of the present invention; Balance processing flow chart; FIG. 15 is a structural diagram of a load balancing system according to an embodiment of the present invention; FIG. 16 is a schematic diagram of a process of assisting a health check by using a VSOCK module according to an embodiment of the present invention;

In order to make the above objectives, features and advantages of the present invention more obvious and understandable, the present invention will be further described in detail below in conjunction with the accompanying drawings and specific embodiments.

Referring to Fig. 1, there is shown a step flow chart of Embodiment 1 of a network load balancing method of the present invention, which may specifically include the following steps:

Step 101: Receive preset traffic scheduling rules sent by the control device and unique path indication information of the back-end server in the second type of network.

It should be noted that there can be many types of networks, such as common IP network wide area network and virtual private network VPC. IP network is a network that uses IP (Internet Protocol) communication protocol to interconnect multiple computer terminals, clients, and servers. It can be understood as a public network. Among them, each terminal in the IP network has a dedicated IP address, and different terminals are identified and distinguished based on the IP address to facilitate the accurate transmission of information. Compared with the public IP network, the virtual private network VPC uses encryption protocols, tunneling protocols and other security procedures to form a private and independent virtual network environment in the public IP network. VPC users can access the virtual private network. Customize the IP address range of each terminal in the VPC.

In the embodiment of the present invention, the above-mentioned second type of network may be a wide area network or a virtual private network VPC. That is, the back-end server may be in a wide area network, or it may be in a virtual private network VPC.

The above-mentioned unique path indication information of the back-end server can uniquely correspond to a certain back-end server, and communication with the corresponding back-end server can be carried out according to the unique path indication information.

In a specific implementation, the control device can send preset traffic scheduling rules and unique path indication information of multiple back-end servers to the load balancer. The load balancer receives preset traffic scheduling rules and unique path indication information of the back-end server to facilitate subsequent traffic scheduling processing. also, The control device can also send the unique path indication information of the load balancer to the client.

There are multiple traffic scheduling rules, such as WRR (Weighted Round Robin), RR (Round-Robin, round-robin scheduling algorithm), WLC (Weighted Least-Connection Scheduling, weighted least connection scheduling algorithm), etc. Technical personnel can adopt various traffic scheduling rules as needed, which is not limited in the embodiment of the present invention.

Step 102: Obtain the unique path indication information of the client in the first type of network from the back-end server access request sent by the client.

In the embodiment of the present invention, the above-mentioned first type of network may be a wide area network or a virtual private network VPC. That is, the client may be in the wide area network or in the virtual private network VPC. The above-mentioned unique path indication information of the client can uniquely correspond to a certain client, and it can communicate with the corresponding client according to the unique path indication information.

In a specific implementation, the client can obtain the corresponding service by sending a back-end server access request to the back-end server. Before sending the back-end server access request to the actual processed back-end server, the load balancer may receive the access request, so as to further dispatch the access request to a suitable back-end server. From the back-end server access request sent by the client, the unique path indication information of the client can be obtained, and the unique path indication information can be recorded and learned to indicate the address of the client when the request response information is returned to the client.

It should be noted that the step 102 can also be performed in the step 101 Executed before. That is, the unique path indication information of the client can be obtained from the back-end server access request first, and then the preset traffic scheduling rules and the unique path indication information of multiple back-end servers can be received. In actual applications, when the load balancer receives the back-end server access request sent by the client, it indicates that it has initially established a connection with the client. At this time, the client's unique path indication information can be recorded and learned so that it can be received After the request response information is returned by the back-end server, the unique path indication information is used to return the request response information to the client.

Step 103: According to the unique path indication information of the back-end server, send the back-end server access request to at least one back-end server selected according to the preset traffic scheduling rule.

The preset traffic scheduling rules can be used to calculate the load conditions of each back-end server, and the back-end servers available for scheduling can be selected accordingly. According to the unique path indication information of the selected back-end servers, the back-end servers can be selected accordingly. The server access request is forwarded to the back-end server, and the back-end server processes and responds to the access request from the client, and returns the request response information to the load balancer accordingly.

Step 104: Receive the request response information returned by the back-end server, and return the request response information to the client according to the unique path indication information of the client, where the unique path indication information is in the client The first type of network where the end is located and the second type of network where each back-end server is located, and at least one of the first type of network and the second type of network is a virtual private network VPC .

When receiving the request response data from the back-end server in response to the access request Information, the request response information can be returned to the client according to the previously recorded unique path indication information of the client.

Since the unique path indication information only exists in the first type of network and the second type of network, in step 103, according to the indication of the unique path indication information of the back-end server, the request response information can be sent to the only corresponding post The end server, in step 104, can send the request response information to the only corresponding client according to the instructions of the client's unique path indication information.

Therefore, when at least one of the first type of network and the second type of network is a virtual private network VPC, there is no need for the gateway to perform address translation processing on the client and back-end server, thereby avoiding the gateway from performing address translation processing The resulting access delay improves the client's access efficiency to the back-end server and the return efficiency of the back-end server's request and response information, and at the same time saves the processing resources of the gateway. Moreover, since there is no need to convert the addresses of the client and the back-end server, the consumption of non-VPC IP addresses by the client and the back-end server is saved.

In addition, the embodiment of the present invention does not need to go through the gateway for conversion processing, and the load balancer can obtain the real network address of the client, so that the client can be accurately controlled.

The embodiment of the present invention can be applied to the application scenario where at least one network is a virtual private network VPC in the first type of network where the client is located and the second type of network where the back-end server is located. Specifically, There can be the following situations:

When the first type of network where the client is located is a wide area network, if the There is only one end server, and the second type of network where the back-end server is located is a virtual private network VPC. If there are multiple back-end servers scheduled, the multiple back-end servers can be all in a virtual private network VPC, or at least one back-end server is in a virtual private network VPC and the rest of the back-end servers are in a WAN . For multiple back-end servers in a virtual private network VPC, they can all be in the same virtual private network VPC, or all are in different virtual private network VPCs, or some of them are in the same virtual private network VPC.

When the first type of network where the client is located is a virtual private network VPC, if only one back-end server is scheduled, the second type of network where the back-end server is located is a virtual private network VPC or Wan. If there are multiple back-end servers scheduled, the multiple back-end servers can be all in a virtual private network VPC, or all in a wide area network, or part in a wide area network, and part in a virtual private network VPC. For multiple back-end servers in a virtual private network VPC, they can all be in the same virtual private network VPC, or all are in different virtual private network VPCs, or some of them are in the same virtual private network VPC.

It can be seen from the above that in the application scenario to which the embodiments of the present invention are applicable, when the first type of network is a virtual private network VPC, the second type of network can be a wide area network or a virtual private network VPC, that is, the first type The network and the second type of network can be homogeneous or heterogeneous; when the first type of network is a wide area network, the second type of network can be a virtual private network VPC, that is, the first type of network and the second type of network The class network is heterogeneous.

As a preferred example of the embodiment of the present invention, the unique path indication resource The information can be generated from the network identification information of the virtual private network VPC where it is located and the address identification information in the virtual private network VPC.

In a specific implementation, the network identification information of the first type of network where the client is located, and the address identification information of the client in the first type of network where the client is located can be obtained from the back-end server access request. Generate unique path indication information for the client.

In actual application, for the client in the VPC based on the VXLAN virtual private network, the access request sent can be an encapsulated VXLAN message. After receiving the VXLAN message, the VXLAN message can be decapsulated Process, obtain the network identification information VNI of the virtual private network VPC where the client is located, and the IP address information of the client as the VTEP destination address in the virtual private network VPC, thereby generating a unique path indication for the client Information.

It should be noted that VXLAN is a commonly used technology to construct a virtual private network VPC. It uses the MAC in UDP method to access the server through VXLAN packets and uses VTEP (VXLAN Tunnel End Point, VXLAN tunnel terminal node) encapsulation Reconcile and unseal the VXLAN packet. The VXLAN message contains VNI (VXLAN Network Identifier, VXLAN network identifier) information, the IP address information used as the VTEP destination address in the virtual private network VPC, and the inner layer information of the message. The VNI information is the network identification information of the virtual private network VPC where the client is located. The inner layer information of the message includes the IP address and port information of the client in the virtual private network VPC where the client is located. Therefore, in the back-end server access request sent, the network where the client is located can be included The network identification information and the address identification information in the first type of network, the load balancer can obtain the network identification information and address identification information, and generate a unique path indication information for the client. For example, the back-end server access request generated by the VXLAN message contains the network identification information VNI79 of the virtual private network VPC where the client is located, and the address identification information 192.168.0.1 of the virtual private network VPC. The unique path indication information VNI79/192.168.0.1 of the client can be generated accordingly.

It should be further explained that, in addition to VXLAN constructing a virtual private network VPC, the technical solution of the embodiment of the present invention can also be applied to a virtual private network VPC constructed based on GRE (Generic Routing Encapsulation, Generic Routing Encapsulation). GRE uses the Tunnel (tunnel) technology, which can encapsulate the datagrams of certain network layer protocols, so that these encapsulated datagrams can be transmitted in the IPv4 network.

For the back-end server in the virtual private network VPC constructed based on VXLAN, the VXLAN message containing the network identification information VNI and address information can be sent to the control device, and the control device generates the unique path indication information of the back-end server And send it to the load balancer, and the load balancer sends it to the back-end server according to the unique path indication information of the back-end server. Or, the back-end server generates unique path indication information based on its own network identification information VNI and address information, encapsulates it in a VXLAN message, and sends it to the load balancer through the control device.

Referring to Fig. 2, there is shown a step flow chart of Embodiment 2 of a network load balancing method of the present invention, which may specifically include the following steps:

Step 201: Receive and save the network identification information of the first type of network where the client is located, which is submitted when a plurality of clients register with the control device.

In actual applications, the client can register with the control device, and the network identification information of the first type of network where the client is located can be submitted during registration. The control device can send the network identification information of the first type of network received during registration to the load balancer.

Step 202: Receive the preset traffic scheduling rule sent by the control device and the unique path indication information of the back-end server in the second type of network, wherein the unique path indication information is in the first type of the client. The network and each back-end server are uniquely located in the second type of network, and at least one of the first type of network and the second type of network is a virtual private network VPC.

Step 203: According to the unique path instruction information of the multiple back-end application servers, correspondingly access the multiple back-end servers.

Step 204: Check the running status of the accessed back-end server, and mark the abnormal identifier on the corresponding unique path indication information for the back-end server with abnormal status; the abnormal identifier is used to indicate the suspension of sending the back-end server Server access request to the back-end server.

It should be noted that the load balancer usually checks the running status of the back-end server before performing traffic scheduling processing, and does not schedule traffic to servers with abnormal running status. There can be many kinds of abnormal operation status, such as slow response of the server, failure of the application on the server, and error in the association of the application on the server.

In the prior art prior to the present invention, when checking the back-end server in the virtual private network VPC, since the address of the back-end server is only unique within its domain, the load balancer cannot directly access the virtual private network The back-end server in the VPC also needs to interact with the back-end server through the gateway.

In a specific implementation, the load balancer can access each back-end server and check its running status according to the unique path indication information of the back-end application server before performing traffic scheduling processing. For servers with abnormal status, an abnormal identifier can be marked on the corresponding unique path indication information. During traffic scheduling, for servers with abnormal identifiers, the access request will be suspended to ensure normal operation. The server of which assumes the access is to provide services. Therefore, the load balancer accesses the back-end server by using the unique path indication information of the back-end server issued by the control device, because the unique path indication information of the back-end server is in the first type of network where the client is located and The only existence in the second type of network where each back-end server is located, therefore, the operation status of the back-end server can be checked and processed without the participation of the gateway.

In actual applications, you can set up a running status check auxiliary module in the load balancer. This module can be set at the bottom of the system. When the load balancer creates a connection with the back-end server through the running status check program, pass The system calls the stored unique path indication information of the back-end server, and the module encapsulates a VXLAN message based on the unique path indication information of the back-end server and sends it to the corresponding back-end server.

Step 205: Identify the network type of the first type of network where the client is located type.

Because in actual applications, the client may be in a virtual private network VPC or a traditional wide area network based on VXLAN. Different networks use different network protocols. The load balancer can use different network protocols according to the characteristics of different network protocols. Data packet structure suitable for this type of network.

Step 206: For the network type of the first type of network, unblock the network identification information of the first type of network and the address identification information of the client from the back-end server access request. And generate unique path indication information of the client.

For the back-end server access request initiated by the client in the first type of network, the network of the first type of network can be unblocked from the access request according to the characteristics of the network type of the first type of network The identification information and the client's address identification information, and correspondingly generate the client's unique path indication information.

In actual applications, when the load balancer receives the back-end server access request sent by the client, it indicates that it has initially established a connection with the client. At this time, the client's unique path indication information can be recorded and learned. The subsequent processing can be Use the unique path indication information to return the original path of the request response information to the client.

Step 207: Determine whether the network identification information of the first type of network obtained from the back-end server access request is within the range of the stored network identification information of the first type of network, if not, return a rejection Access information to the client; if yes, go to step 208.

In a specific implementation, you can also find out whether there is a corresponding network logo unblocked from the access request in the pre-stored network identification information. Cognition information. If the network identification information cannot be found, it indicates that the client or the network where the client is located has not been registered on the control device, and the access denied information can be returned to the client accordingly. If you find the network identification information, you can continue to perform the next step of traffic scheduling processing.

Step 208: According to the unique path indication information of the back-end server, send the back-end server access request to at least one back-end server selected according to the preset traffic scheduling rule.

The preset traffic scheduling rules can be used to calculate the load conditions of each back-end server, and the back-end servers available for scheduling can be selected accordingly. According to the unique path indication information of the selected back-end servers, the back-end servers can be selected accordingly. The server access request is forwarded to the back-end server, and the back-end server processes and responds to the access request from the client, and returns the request response information to the load balancer accordingly.

Step 209: Receive the request response information returned by the back-end server, and according to the unique path indication information of the client, encapsulate the request response information for the network type of the first type of network and send it to all The client.

After receiving the request response information from the back-end server in response to the access request, the request response information can be encapsulated according to the previously determined network type of the first type of network, and according to the recorded unique path indication information of the client, corresponding Return to the client.

In practical applications, in order to enable the back-end server to accurately return request response information to the load balancer, a VTEP automatic learning module can be deployed on the back-end server to learn and record the VTEP of the load balancer Address information. Of course, the back-end server may also obtain a preset return request response information rule from the control device, so as to accurately return the request response information to the load balancer.

According to the embodiment of the present invention, the load balancer sends the access request to the back-end server by using the unique path indication information of the back-end server issued by the control device, and the load balancer accesses the back-end server by using the back-end server sent by the client. Request to obtain the unique path indication information of the client, and forward the request response information returned by the back-end server to the client. Since the unique path indication information between the client and the back-end server only exists in the first type of network where the client is located and the second type of network where each back-end server is located, so in the first type of network When at least one of the second and second types of networks is a virtual private network VPC, the address translation processing of the client and the back-end server by the gateway is not required, thereby avoiding the access delay caused by the address translation processing of the gateway and increasing The client's access efficiency to the back-end server and the return efficiency of the back-end server's request response information also save the processing resources of the gateway. Moreover, since there is no need to convert the addresses of the client and the back-end server, the consumption of non-VPC IP addresses by the client and the back-end server is saved.

In addition, the embodiment of the present invention does not need to go through the gateway for conversion processing, and the load balancer can obtain the real network address of the client, so that the client can be accurately controlled.

Finally, according to the embodiment of the present invention, the load balancer accesses the back-end server by using the unique path indicating information of the back-end server issued by the control device, because the unique path indicating information of the back-end server is in the location where the client is located. The first type of network and the second type of network where each back-end server is located is the only one. Therefore, the VPC address of the back-end server can be converted without the gateway, and the unique path indication of the back-end server can be used. Information checks the running status of the back-end server, avoiding the delay caused by the gateway's address translation processing, and improving the efficiency of running status checking.

Referring to FIG. 3, there is shown a step flow chart of an embodiment of a network load balancing control method of the present invention, which may specifically include the following steps:

Step 301: Obtain unique path indication information of the back-end server in the second type of network from each back-end server.

The control device can obtain the unique path indication information of the back-end server from each back-end server, so as to indicate that the information is accurately sent to the back-end server.

As a preferred example of the embodiment of the present invention, the unique path indication information can be generated from the network identification information of the virtual private network VPC where it is located and the address identification information in the virtual private network VPC. Specifically, the control device may obtain from multiple back-end servers the network identification information of each second-type network where the back-end servers are located, and the network identification information of the back-end servers in the second-type network where the back-end servers are located. Address identification information, correspondingly generate unique path instruction information for each back-end server.

Step 302: Send the preset traffic scheduling rule and the unique path indication information of the back-end server to the load balancing device, so that the load balancing device can send the information according to the unique path indication information of the back-end server The client's back-end server access request is sent to at least one back-end server selected according to the preset traffic scheduling rule, and according to the client The unique path indicating information of the client in the first type of network returns the request response information returned by the back-end server to the client, wherein the unique path indicating information is in the first type of the client The network and each back-end server are uniquely located in the second type of network, and at least one of the first type of network and the second type of network is a virtual private network VPC.

The control device sends the preset traffic scheduling rules and unique path indication information of multiple back-end servers to the load balancing device. When the load balancing device receives the client's request for access to the back-end server, it can obtain the unique path indication information of the first type of network where the client is located from the access request, and use the preset traffic scheduling rules to calculate each post According to the load situation of the end server, the back-end server that can be dispatched is selected accordingly, and the back-end server access request is forwarded to the back-end server according to the unique path indication information of the selected back-end server. The back-end server processes and responds to the access request from the client, and returns the request response information to the load balancing device accordingly.

After the load balancing device receives the request response information from the back-end server in response to the access request, it can return the request response information to the client according to the unique path indication information of the client.

It should be noted that the load balancing device may be a load balancer, or any device responsible for scheduling the access request sent by the client to at least one back-end server.

According to the embodiment of the present invention, the load balancer sends the access request to the back-end server by using the unique path indication information of the back-end server issued by the control device. Because the unique path indication information of the back-end server is in the client The only existence in the first type of network where the end is located and the second type of network where each back-end server is located. Therefore, at least one of the first type of network and the second type of network is a virtual private network VPC At this time, the address translation processing of the gateway to the back-end server is not required, thereby avoiding the access delay caused by the address translation processing of the gateway, improving the access efficiency of the client to the back-end server, and also saving the processing of the gateway. resource. Moreover, because there is no need to convert the address of the back-end server, it saves the back-end server's consumption of non-VPC IP addresses.

In addition, the embodiment of the present invention does not need to go through the gateway for conversion processing, and the load balancer can obtain the real network address of the client, so that the client can be accurately controlled.

As a preferred example of the embodiment of the present invention, the method may further include: instructing the load balancing device to send the unique path indication information of the load balancing device to the back-end server for the back-end server The device returns request response information to the load balancing device according to the unique path indication information of the load balancing device.

The control device may also instruct the load balancing device to send its unique path indication information to multiple back-end servers, so that the back-end server can accurately return request response information to the load balancing device.

As a preferred example of the embodiment of the present invention, the method may further include: receiving the network identification information of the first type of network where the client is located, submitted by the client during registration; The network identification information of the network is sent to the load balancing device for the load balancing device to save and determine when the client's back-end server access request is received Whether the network identification information of the first type of network obtained from the back-end server access request is within the range of the saved network identification information of the first type of network, if not, return the access denied information to all The client.

The client can register with the control device, and can submit the network identification information of the first type of network where the client is located during registration. The control device can send the collected network identification information of the first type of network to the load balancing device.

The load balancing device can save the received network identification information of the first type of network, and when receiving the back-end server access request initiated by the client, it can obtain the first type of network where the client is located from the access request In the pre-stored network identification information, find out whether there is the network identification information of the first type of network where the client is located. If the network identification information is not found, it indicates that the client or the network where the client is located has not been registered on the control device, and the access denied information can be returned to the client accordingly. If you find the network identification information, you can continue to perform the next step of traffic scheduling processing.

Referring to Fig. 4, a flowchart of the steps of an embodiment of a network interaction method of the present invention is shown, which may specifically include the following steps:

Step 401: According to the unique path indication information of the back-end server in the second type of network, send the client's access request to the back-end server to at least one selected according to the preset traffic scheduling rule End server, the second type of network is a virtual private network VPC.

When the first type of network where the back-end server is located is a virtual private network VPC, the load balancer can use the preset traffic scheduling rules to calculate each back-end The load situation of the server, and correspondingly select the back-end server available for scheduling, and forward the back-end server access request to the back-end server according to the unique path indication information of the selected back-end server. The back-end server processes and responds to the access request from the client, and returns the request response information to the load balancer accordingly.

Step 402: Return the request response information returned by the back-end server for the client's access request to the client according to the unique path indication information of the client in the first type of network. The first type of network is Virtual private network VPC.

Wherein, the unique path indication information uniquely exists in the first type of network where the client is located and the second type of network where each back-end server is located.

The load balancer receives the request response information from the back-end server in response to the access request, and can return the request response information to the client accordingly. When the second type of network where the client is located is a virtual private network VPC, the request response information can be returned to the client according to the unique path indication information of the client.

It should be noted that in actual applications, one or more of the above-mentioned steps may be executed. For example, only step 401 may be executed, or both steps 401 and 402 may be executed.

According to the embodiment of the present invention, the load balancer sends the access request to the back-end server by using the unique path indication information of the back-end server issued by the control device, and the load balancer obtains the client's information by using the access request sent by the client. The unique path indication information forwards the request response information returned by the back-end server to the client. Due to the uniqueness of the client and back-end server The path indication information only exists in the first type of network where the client is located and the second type of network where each back-end server is located. Therefore, at least one of the first type of network and the second type of network is In the case of virtual private network VPC, the address translation processing of the client and the back-end server by the gateway is not required, thereby avoiding the access delay caused by the address translation processing of the gateway, and improving the access efficiency of the client to the back-end server And the return efficiency of the request response information of the back-end server, while also saving the processing resources of the gateway. Moreover, since there is no need to convert the addresses of the client and the back-end server, the consumption of non-VPC IP addresses by the client and the back-end server is saved.

In addition, the embodiment of the present invention does not need to go through the gateway for conversion processing, and the load balancer can obtain the real network address of the client, so that the client can be accurately controlled.

In order to enable those skilled in the art to better understand the embodiments of the present invention, the load balancing and control method of the present invention will be described below through specific examples.

Figure 9 shows a schematic diagram of the working principle of a current load balancer. It can be seen from the figure that the client Client accesses a certain server to obtain services, and after domain name resolution, it will correspondingly access the VIP: VPORT port of the load balancer LB. After the visit reaches the load balancer, the visit will be distributed to the multiple back-end servers RS1, RS2, RS3, or RS4 that actually provide services in the back-end according to certain traffic scheduling rules. The back-end servers RS1, RS2, RS3, or RS4 respectively receive access from the client through their respective RIP1: RPORT1, RIP2: RPORT2, RIP3: RPORT3, and RIP4: RPORT4 ports, and return the processing results from the original path after corresponding processing. To the load balancer. The load balancer returns the processing result to the client by accessing the CIP: CPORT port of the client. The load balancer scheduling is based on TCP/UDP scheduling as four-layer load balancing (L4 LB), and according to the application layer (http, ftp, etc.), it is seven-layer load balancing (L7 LB). In addition, the load balancer also has the function of checking the health of the back-end servers, ignoring the back-end servers that have failed the health check when distributing traffic.

Figure 10 shows a schematic diagram of the current working principle of using a gateway for load balancing. It can be seen from the figure that the client is in a VXLAN-type virtual private network VPC with the network identification VNI79. In this virtual private network VPC, its IP address is 192.168.0.1, and the IP address is only in the virtual private network of VNI79. It is the only one in the VPC, the VPC address needs to be converted into a non-VPC address through the gateway VXLAN Gateway, which is converted into a unique IP address 10.18.0.1 in the entire network, before it can pass through the load balancer with an IP address of 10.1.2.3. LB is scheduled to access the back-end servers RS1 and RS2 in the virtual private network VPC of VNI79, and the back-end servers RS1 and RS2 in the virtual private network VPC of VNI1234.

The back-end servers RS1 and RS2 in the virtual private network VPC with the network ID of VNI79 have unique address identification information 192.168.1.11 and 192.168.2.12 in the network where they are located. The back-end server in the virtual private network VPC of VNI1234 The end servers RS1 and RS2 have unique address identification information 172.16.100.11 and 172.16.200.12 in the network where they are located. However, the address identification information of each back-end server is only unique in the virtual private network VPC where it is located, and it also needs to be converted into an IP address through the gateway. 10.16.1.11, 10.16.2.12, 10.16.3.13, and 10.16.4.14 can interact with the load balancer.

In order to facilitate those skilled in the art to understand the implementation of the load balancing method of the present invention in different application scenarios, the following will describe with reference to FIG. 11, FIG. 12 and FIG. 13.

It should be noted that the illustration is simplified into an application scenario of 2 to 4 back-end servers for the sake of simplicity. In actual applications, it can be applied to any number of back-end servers. Among them, Figure 11 and Figure 12 respectively show the application scenarios where the client is in a virtual private network VPC, multiple back-end servers are in the virtual private network VPC, and multiple back-end servers are all in the WAN. . In practical applications, it may also include the situation where some of the multiple back-end servers are in the wide area network and some are in the virtual private network VPC.

Figure 13 shows a schematic diagram of an application scenario where multiple back-end servers are in a virtual private network VPC when the client is in the WAN. In actual applications, it may also include a situation where at least one back-end server is in a virtual private network VPC and the remaining back-end servers are in a wide area network.

Those skilled in the art can apply the load balancing method of the present invention to various applicable application scenarios according to actual needs.

FIG. 11 shows a schematic diagram of application scenario 1 of a load balancing method of the present invention. It can be seen from the figure that the client Client is in the virtual private network VPC with the network identification VNI79, and the address in the virtual private network VPC of VNI79 is 192.168.0.1. The client can obtain the unique path indication information of the load balancer LB when registering with the control device VNI79/192.168.10.1, and access the load balancer LB according to the unique path indication information to initiate an access request to the back-end server via the load balancer. The load balancer uses the network identifier VNI79 of the virtual private network VPC where the client is located and the IP address 192.168.0.1 in the virtual private network VPC to generate the unique path indication information VNI79/192.168.0.1 of the client and record the learning.

In this application scenario, in addition to the virtual private network VPC with VNI79, there is also a virtual private network VPC with VNI1234. Two back-end servers RS1 and RS2 are respectively deployed under the two virtual private network VPCs. The back-end server has unique address identification information 192.168.1.11, 192.168.2.12, 172.16.100.11 and 172.16.200.12 in the virtual private network VPC to which it belongs.

The load balancer can obtain the unique path indication information of multiple back-end servers from the control device. As you can see in the figure, the load balancer can obtain the unique path indication information VNI79/192.168.1.11 and VNI79/192.168.2.12, and VNI1234 of the back-end servers RS1 and RS2 in the virtual private network VPC with the network identifier VNI79. The unique path indication information VNI1234/172.16.100.11 and VNI1234/172.16.200.12 of the back-end servers RS1 and RS2 in the virtual private network VPC.

Using the unique path indication information of the back-end server, the access request initiated by the client can be accurately dispatched to the back-end server. When the back-end server returns the response information, it can also accurately return the response information to the client according to the unique path indication information of the client that records the learning. Therefore, there is no need to go through the gateway to convert the VPC addresses of the client and back-end servers to non- With VPC address, the load balancer can accurately schedule the client's access to the back-end server, and can accurately return the response information of the back-end server to the client.

In actual applications, in addition to VXLAN, clients and back-end servers can also be in a virtual private network VPC based on GRE, or some clients and back-end servers can be in a virtual private network VPC based on VXLAN. Part of it is in a virtual private network VPC created based on GRE. Those skilled in the art can apply the embodiments of the present invention to a virtual private network VPC constructed in various ways.

Fig. 12 shows a schematic diagram of application scenario 2 of a load balancing method of the present invention. It can be seen from the figure that the client Client is in the virtual private network VPC, while the back-end servers RS1 and RS2 are in the traditional wide area network. The load balancer uses the network identifier VNI79 of the virtual private network VPC where the client is located and the IP address 192.168.0.1 in the virtual private network VPC to generate the unique path indication information of the client and record the learning. The load balancing server dispatches the access request initiated by the client to the back-end servers RS1 and RS2 with IP addresses of 100.12.1.11 and 100.12.1.12 respectively, and uses the back-end server's response information according to the uniqueness of the client learned by the record Path indication information, return to the client. Therefore, without the need for a gateway to convert the VPC address to a non-VPC address, the load balancer can accurately schedule the client's access to the back-end server and return response information to the client.

FIG. 13 shows a schematic diagram of application scenario 3 of a load balancing method of the present invention. It can be seen from the figure that the client is in a traditional WAN, The IP address is 10.18.0.1; and the back-end servers RS1 and RS2 are in the virtual private network VPC with the network identification VNI79, and their IP addresses in the virtual private network VPC are 192.168.1.11 and 192.168.2.12, respectively. When the load balancer dispatches the client-initiated access request to the back-end server, it can generate each based on the back-end server's network identifier VNI79 and its IP addresses 192.168.1.11 and 192.168.2.12 in the virtual private network VPC. The unique path to indicate information. According to their unique path indication information, the load balancer can accurately dispatch the access request to the back-end server without going through the gateway to convert the VPC address of the back-end server into a non-VPC address.

Fig. 14 shows a flow chart of load balancing processing according to an embodiment of the present invention. It can be seen from the figure that the VXLAN message is first unpacked from the access request initiated by the client, and the VNI information and the inner layer information of the message are obtained. Then the scheduling module selects the back-end server according to the obtained VNI information and the inner layer information of the message containing the client IP address, as well as the preset scheduling rules. If the client successfully establishes a connection initially, it will learn and record the acquired VNI information and message inner information through the VTEP automatic learning module. Construct a VXLAN message based on the VNI information and address information of the back-end server and send it to the corresponding back-end server. After the back-end server receives the request processing, it returns the response information to the load balancer LB.

Fig. 15 shows a structural diagram of a load balancing system according to an embodiment of the present invention. As can be seen from the figure, the system includes the following key modules:

The control center is used to issue scheduling rules to the load balancer. If it is a back-end server in a virtual private network VPC, the back-end server needs to be issued The VNI information and IP address information of the server are given to the load balancer.

The VXLAN processing module is used to identify and unseal the received VXLAN message according to the characteristics of the VXLAN protocol when the access request sent by the client is received. When the request response is returned, a VXLAN packet is encapsulated accordingly.

The VTEP automatic learning module is used to learn and record the address information of the client when the client initially establishes a connection or when the VTEP changes, for direct use when returning a request response.

The scheduling module is used to configure the load balancing of the back-end server according to the early scheduling rules.

The VSOCK module is used to assist in the health check of the back-end server in the virtual private network VPC.

Figure 16 shows a schematic diagram of the process of using the VSOCK module to assist the health check. It can be seen from the figure that the VSOCK module works at the bottom of the system. The health check program first calls the VNI information and address information of the back-end server through the system before establishing a connection. Subsequent VSOCK modules will encapsulate or unseal the VXLAN report according to the called information. The text is sent to the back-end server, and the information interaction with the back-end server can be completed without the participation of the gateway.

It should be noted that for the method embodiments, for the sake of simple description, they are all expressed as a series of action combinations, but those skilled in the art should know that the embodiments of the present invention are not limited by the described sequence of actions, because According to the embodiments of the present invention, certain steps may be performed in other order or simultaneously. Secondly, those skilled in the art should also be aware that the embodiments described in the specification are all preferred embodiments, and the actions involved are not necessarily It is necessary for the embodiment of the present invention.

Referring to Figure 5, there is shown a structural block diagram of Embodiment 1 of a network load balancing device of the present invention, which may specifically include the following modules:

The preset traffic scheduling rule receiving module 501 is configured to receive the preset traffic scheduling rule sent by the control device and the unique path indication information of the back-end server in the second type of network.

The information obtaining module 502 is used to obtain the unique path indication information of the client in the first type of network from the back-end server access request sent by the client.

The back-end server access request sending module 503 is configured to send the back-end server access request to at least one selected according to the preset traffic scheduling rule according to the unique path indication information of the back-end server A back-end server.

The request response information return module 504 is configured to receive the request response information returned by the back-end server, and return the request response information to the client according to the unique path indication information of the client. The unique path indication information uniquely exists in the first type of network where the client is located and the second type of network where each back-end server is located, at least in the first type of network and the second type of network One is a virtual private network VPC.

According to the embodiment of the present invention, the load balancer sends the access request to the back-end server by using the unique path indication information of the back-end server issued by the control device, and the load balancer accesses the back-end server by using the back-end server sent by the client. Request to obtain the unique path indication information of the client, and forward the request response information returned by the back-end server to the client. Since the client and back-end server The server’s unique path indication information uniquely exists in the first type of network where the client is located and the second type of network where each back-end server is located. Therefore, in the first type of network and the second type of network When at least one of them is a virtual private network VPC, the address translation processing of the client and the back-end server by the gateway may not be required, thereby avoiding the access delay caused by the address translation processing of the gateway, and improving the client's response to the back-end server. The access efficiency of the server and the return efficiency of the request response information of the back-end server, while also saving the processing resources of the gateway. Moreover, since there is no need to convert the addresses of the client and the back-end server, the consumption of non-VPC IP addresses by the client and the back-end server is saved.

In addition, the embodiment of the present invention does not need to go through the gateway for conversion processing, and the load balancer can obtain the real network address of the client, so that the client can be accurately controlled. As a preferred example of the embodiment of the present invention, the unique path indication information is generated from the network identification information of the virtual private network VPC where it is located and the address identification information in the virtual private network VPC.

Referring to FIG. 6, there is shown a structural block diagram of Embodiment 2 of a network load balancing device of the present invention, which may specifically include the following modules:

The network identification information receiving module 601 is used to receive and save the network identification information of the first type of network where the client is located, which is submitted when multiple clients register with the control device.

The preset traffic scheduling rule receiving module 602 is configured to receive the preset traffic scheduling rule sent by the control device and the unique path indication information of the back-end server in the second type of network.

The back-end server access module 603 is used for correspondingly accessing multiple back-end servers according to the unique path instruction information of the multiple back-end application servers.

The running status checking module 604 is used to check the running status of the accessed back-end server, and for the back-end server with abnormal status, mark the abnormal identifier on the corresponding unique path indication information; the abnormal identifier is used to indicate the suspension Send the back-end server access request to the back-end server.

The network type identification module 605 is used to identify the network type of the first type of network where the client is located.

The information acquisition module 606 is used for acquiring the unique path indication information of the client in the first type of network from the back-end server access request sent by the client.

The network identification information determining module 607 is used to determine whether the network identification information of the first type of network obtained from the back-end server access request is within the range of the stored network identification information of the first type of network If not, then return access denied information to the client.

The back-end server access request sending module 608 is configured to send the back-end server access request to at least one selected according to the preset traffic scheduling rule according to the unique path indication information of the back-end server A back-end server.

The request response information return module 609 is used to receive the request response information returned by the back-end server, and return the request response information to the client according to the unique path indication information of the client. The unique path indication information uniquely exists in the first type of network where the client is located and the second type of network where each back-end server is located. The first type of network At least one of the second type of networks is a virtual private network VPC.

According to the embodiment of the present invention, the load balancer sends the access request to the back-end server by using the unique path indication information of the back-end server issued by the control device, and the load balancer accesses the back-end server by using the back-end server sent by the client. Request to obtain the unique path indication information of the client, and forward the request response information returned by the back-end server to the client. Since the unique path indication information between the client and the back-end server only exists in the first type of network where the client is located and the second type of network where each back-end server is located, so in the first type of network When at least one of the second and second types of networks is a virtual private network VPC, the address translation processing of the client and the back-end server by the gateway is not required, thereby avoiding the access delay caused by the address translation processing of the gateway and increasing The client's access efficiency to the back-end server and the return efficiency of the back-end server's request response information also save the processing resources of the gateway. Moreover, since there is no need to convert the addresses of the client and the back-end server, the consumption of non-VPC IP addresses by the client and the back-end server is saved.

In addition, the embodiment of the present invention does not need to go through the gateway for conversion processing, and the load balancer can obtain the real network address of the client, so that the client can be accurately controlled.

Finally, according to the embodiment of the present invention, the load balancer accesses the back-end server by using the unique path indication information of the back-end server issued by the control device, because the unique path indication information of the back-end server is in the first position where the client is located. The first type of network and the second type of network where each back-end server is located is the only one. Therefore, it is possible to communicate the VPC address of the back-end server without going through the gateway. Perform conversion, and use the unique path indication information of the back-end server to check the running status of the back-end server, avoiding the delay caused by the gateway's address translation processing, and improving the efficiency of running status checking.

As a preferred example of the embodiment of the present invention, the information acquisition module 606 may include: a back-end server access request unblocking sub-module, which is used for the network type of the first type of network, from the The back-end server access request unblocks the network identification information of the first type of network and the address identification information of the client, and generates unique path indication information of the client.

As a preferred example of the embodiment of the present invention, the request response information return module 609 may include the following submodules: a request response information encapsulation submodule for encapsulating the network type of the first type of network The request response information is sent to the client.

Referring to FIG. 7, there is shown a structural block diagram of an embodiment of a network load balancing control device of the present invention, which may specifically include the following modules: a back-end server unique path indication information acquisition module 701, which is used to obtain information from each back-end server The end server obtains the unique path indication information of the back end server in the second type of network.

The preset traffic scheduling rule sending module 702 is configured to send the preset traffic scheduling rule and the unique path indication information of the back-end server to the load balancing device, so that the load balancing device can use the back-end server according to The unique path indication information of the client sends the client’s back-end server access request to at least one selected according to the preset traffic scheduling rule The back-end server, and according to the unique path indication information of the client in the first type of network, returns the request response information returned by the back-end server to the client, wherein the unique path indication information Only exists in the first type of network where the client is located and the second type of network where each back-end server is located, and at least one of the first type of network and the second type of network is a virtual private network Road VPC.

According to the embodiment of the present invention, the load balancer sends the access request to the back-end server by using the unique path indication information of the back-end server issued by the control device. Because the unique path indication information of the back-end server is in the client The first type of network at the location and the second type of network where each back-end server is located. Therefore, when at least one of the first type of network and the second type of network is a virtual private network VPC, The address translation processing of the gateway to the back-end server may not be required, thereby avoiding the access delay caused by the address translation processing of the gateway, improving the access efficiency of the client to the back-end server, and also saving the processing resources of the gateway. Moreover, because there is no need to convert the address of the back-end server, it saves the back-end server's consumption of non-VPC IP addresses.

In addition, the embodiment of the present invention does not need to go through the gateway for conversion processing, and the load balancer can obtain the real network address of the client, so that the client can be accurately controlled.

As a preferred example of the embodiment of the present invention, the unique path indication information is generated from the network identification information of the virtual private network VPC where it is located and the address identification information in the virtual private network VPC.

As a preferred example of the embodiment of the present invention, the device may further include The following modules: a sending instruction module for instructing the load balancing device to send the unique path instruction information of the load balancing device to the back-end server, so that the back-end server can balance the load according to the load The unique path indication information of the device, and the request response information is returned to the load balancing device.

As a preferred example of the embodiment of the present invention, the device may further include the following module: a network identification information receiving module for receiving the first type of network where the client is located, submitted by the client during registration. Network identification information of the road.

The network identification information sending module is used to send the network identification information of the first type of network to the load balancing device for the load balancing device to save and receive the back-end server of the client In the case of a server access request, it is determined whether the network identification information of the first type of network obtained from the back-end server access request is within the range of the saved network identification information of the first type of network, if not, then Return the access denied information to the client.

Referring to FIG. 8, there is shown a structural block diagram of an embodiment of a network interaction device of the present invention, which may specifically include the following modules: an access request sending module 801, which is used to send a request according to the back-end server in the second type of network The unique path indication information sends the client's access request to the back-end server to at least one back-end server selected according to the preset traffic scheduling rule, and the second type of network is a virtual private network VPC And/or, the request response information return module 802, which is used to return the request response information returned by the back-end server to the client's access request according to the unique path indication information of the client in the first type of network Describe the customer At the end, the first type of network is a virtual private network VPC; wherein, the unique path indication information is in the first type of network where the client is located and the second type of network where each back-end server is located The only one exists in.

According to the embodiment of the present invention, the load balancer sends the access request to the back-end server by using the unique path indication information of the back-end server issued by the control device, and the load balancer accesses the back-end server by using the back-end server sent by the client. Request to obtain the unique path indication information of the client, and forward the request response information returned by the back-end server to the client. Since the unique path indication information between the client and the back-end server only exists in the first type of network where the client is located and the second type of network where each back-end server is located, so in the first type of network When at least one of the second and second types of networks is a virtual private network VPC, the address translation processing of the client and the back-end server by the gateway is not required, thereby avoiding the access delay caused by the address translation processing of the gateway and increasing The client's access efficiency to the back-end server and the return efficiency of the back-end server's request response information also save the processing resources of the gateway. Moreover, since there is no need to convert the addresses of the client and the back-end server, the consumption of non-VPC IP addresses by the client and the back-end server is saved.

In addition, the embodiment of the present invention does not need to go through the gateway for conversion processing, and the load balancer can obtain the real network address of the client, so that the client can be accurately controlled.

As for the device embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and for related parts, please refer to the part of the description of the method embodiment.

The various embodiments in this specification are described in a progressive manner, and each embodiment focuses on the differences from other embodiments, and the same or similar parts between the various embodiments can be referred to each other.

Those skilled in the art should understand that the embodiments of the embodiments of the present invention may be provided as methods, devices, or computer program products. Therefore, the embodiments of the present invention may adopt the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware. Moreover, the embodiments of the present invention may adopt computer program products implemented on one or more computer-usable storage media (including but not limited to disk memory, CD-ROM, optical memory, etc.) containing computer-usable program codes. form.

In a typical configuration, the computer device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory. The memory may include non-permanent memory in computer-readable media, random access memory (RAM) and/or non-volatile memory, such as read-only memory (ROM) or flash memory (flash RAM). Memory is an example of computer-readable media. Computer-readable media include permanent and non-permanent, removable and non-removable media, and information storage can be realized by any method or technology. Information can be computer-readable instructions, data structures, program modules, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), and other types of random access memory (RAM) , Read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, CD-ROM, digital multi-function disc (DVD) or other light Electronic storage, magnetic cassette tape, magnetic tape magnetic disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by computing devices. According to the definition in this article, computer-readable media does not include non-persistent computer-readable media (transitory media), such as modulated data signals and carrier waves.

The embodiments of the present invention are described with reference to the flowcharts and/or block diagrams of the methods, terminal devices (systems), and computer program products according to the embodiments of the present invention. It should be understood that each process and/or block in the flowchart and/or block diagram, and the combination of processes and/or blocks in the flowchart and/or block diagram can be implemented by computer program instructions. These computer program instructions can be provided to the processors of general-purpose computers, special-purpose computers, embedded processors, or other programmable data processing terminal equipment to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing terminal equipment A device for realizing the functions specified in one process or multiple processes in the flowchart and/or one block or multiple blocks in the block diagram is generated.

These computer program instructions can also be stored in a computer-readable memory that can guide a computer or other programmable data processing terminal equipment to work in a specific manner, so that the instructions stored in the computer-readable memory produce a manufactured product including the instruction device , The instruction device realizes the functions specified in one process or multiple processes in the flowchart and/or one block or multiple blocks in the block diagram.

These computer program instructions can also be loaded on a computer or other programmable data processing terminal equipment, so that a series of operation steps are executed on the computer or other programmable terminal equipment to produce computer-implemented processing, thereby Instructions executed on a computer or other programmable terminal device provide steps for implementing functions specified in a flow or multiple flows in the flowchart and/or a block or multiple blocks in the block diagram.

Although the preferred embodiments of the embodiments of the present invention have been described, those skilled in the art can make additional changes and modifications to these embodiments once they learn the basic creative concept. Therefore, the scope of the attached patent application is intended to be interpreted as including the preferred embodiments and all changes and modifications falling within the scope of the embodiments of the present invention.

Finally, it should be noted that in this article, relational terms such as first and second are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply these entities. Or there is any such actual relationship or sequence between operations. Moreover, the terms "include", "include" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or terminal device including a series of elements not only includes those elements, but also includes those elements that are not explicitly listed. Other elements listed, or also include elements inherent to this process, method, article, or terminal device. Without more restrictions, the element defined by the sentence "including a..." does not exclude the existence of other same elements in the process, method, article, or terminal device that includes the element.

The above is a network load balancing method and a network load balancing device provided by the present invention, a network load balancing control method and a network load balancing control device, a network interaction method and a network interaction The device is introduced in detail, and specific examples are used in this article The principle and implementation of the present invention are explained. The description of the above embodiments is only used to help understand the method and core idea of the present invention; at the same time, for those of ordinary skill in the art, according to the idea of the present invention, in the specific implementation mode There will be changes in the scope of application and the scope of application. In summary, the content of this specification should not be construed as a limitation of the present invention.

Claims (20)

A network load balancing method, characterized in that it includes: receiving preset traffic scheduling rules sent by a control device, and unique path indication information of a back-end server in the second type of network; and a back-end server sent from a client In the server access request, obtain the unique path indication information of the client in the first type of network; according to the indication of the unique path indication information of the back-end server, send the back-end server access request to the At least one back-end server selected by the preset traffic scheduling rule; receiving request response information returned by the back-end server, and returning the request response information according to the instructions of the client's unique path indication information To the client, wherein the unique path indication information of the back-end server exists only in the first type of network where the client is located and the second type of network where each back-end server is located, so The unique path indication information of the client only exists in the first type of network where the client is located and the second type of network where each back-end server is located. The first type of network and the second type of network At least one of the networks is a virtual private network VPC; wherein the unique path indication information is generated from the network identification information of the virtual private network VPC where it is located and the address identification information in the virtual private network VPC. The method according to claim 1, which further includes: correspondingly accessing multiple back-end servers according to the unique path indication information of the multiple back-end application servers; checking the running status of the accessed back-end servers, aiming at State different The normal back-end server marks an abnormality identifier on the corresponding unique path indication information; the abnormality identifier is used to instruct to suspend sending the back-end server access request to the back-end server. The method according to claim 1, wherein, in the back-end server access request sent from the client, before the step of obtaining the unique path indication information of the client in the first type of network, the method It also includes: identifying the network type of the first type of network where the client is located. The method according to claim 3, wherein, in the back-end server access request sent from the client, the step of obtaining the unique path indication information of the client in the first type of network includes: The network type of a type of network, the network identification information of the first type of network and the address identification information of the client are unsealed from the back-end server access request, and the unique of the client is generated Path indication information. The method according to claim 3, wherein the step of returning the request response information to the client includes: encapsulating the request response information for the network type of the first type of network and sending it to The client. The method according to claim 1, wherein, in the back-end server access request sent from the client, before the step of obtaining the unique path indication information of the client in the first type of network, the method It also includes: receiving and saving the network identification information of the first type of network where the client is located when a plurality of clients register with the control device; accessing the back-end server sent from the client Request, get After the step of indicating information about the unique path of the client, the method further includes: determining whether the network identification information of the first type of network obtained from the back-end server access request is in the stored first type of network Within the range of the network identification information of, if not, return the access denied information to the client. A network load balancing control method, which is characterized in that it comprises: obtaining the unique path indication information of the back-end server in the second type of network from each back-end server; The unique path indication information of the end server is sent to the load balancing device, so that the load balancing device sends the back-end server access request of the client to the load balancing device according to the indication of the unique path indication information of the back-end server. The at least one back-end server selected by the preset traffic scheduling rule, and the request response information returned by the back-end server is returned to The client, wherein the unique path indication information of the back-end server uniquely exists in the first type of network where the client is located and the second type of network where each back-end server is located, and the client's The unique path indication information uniquely exists in the first type of network where the client is located and the second type of network where each back-end server is located, in the first type of network and the second type of network At least one is a virtual private network VPC; wherein the unique path indication information is generated from the network identification information of the virtual private network VPC where it is located and the address identification information in the virtual private network VPC. The method according to claim 7, further comprising: instructing the load balancing device to send the unique path indication information of the load balancing device to the back-end server, so that the back-end server can follow The unique path indication information of the load balancing device returns request response information to the load balancing device. The method according to claim 7, further comprising: receiving the network identification information of the first type of network where the client is located, submitted by the client during registration; The network identification information is sent to the load balancing device for storage by the load balancing device, and when receiving the client's back-end server access request, it determines the first obtained from the back-end server access request Whether the network identification information of the class network is within the range of the saved network identification information of the first class network, if not, return the access denied information to the client. A network interaction method, which is characterized in that it includes: according to the indication of the unique path indication information of the back-end server in the second type of network, sending the client's access request to the back-end server to the scheduling according to the preset flow At least one back-end server selected by the rule, the second type of network is a virtual private network VPC; and/or, according to the instructions of the client's unique path indication information in the first type of network, the The request response information returned by the end server in response to the client's access request is returned to the client. The first type of network is a virtual private network VPC; wherein the unique path indication information of the back-end server is in the guest The first type of network where the client is located and the second type of network where each back-end server is located uniquely exist, and the unique path indication information of the client is in the type 1 network where the client is located and each The back-end server is uniquely present in the second type of network; wherein, the unique path indication information is generated from the network identification information of the virtual private network VPC where it is located and the address identification information in the virtual private network VPC . A network load balancing device, which is characterized by comprising: a preset flow scheduling rule receiving module for receiving preset flow scheduling rules sent by a control device, and a unique path of a back-end server in the second type of network Instruction information; an information acquisition module for acquiring the unique path instruction information of the client in the first type of network from the back-end server access request sent by the client; the back-end server access request sending module, It is used to send the back-end server access request to at least one back-end server selected according to the preset traffic scheduling rule according to the instruction of the unique path indication information of the back-end server; request response information The return module is used to receive the request response information returned by the back-end server, and return the request response information to the client according to the instructions of the unique path indication information of the client, where the back The unique path indication information of the end server uniquely exists in the first type of network where the client is located and the second type of network where each back-end server is located, and the unique path indication information of the client is located at the client. At The first type of network and the second type of network where each back-end server is located only exists, and at least one of the first type of network and the second type of network is a virtual private network VPC; The unique path indication information is generated from the network identification information of the virtual private network VPC where it is located and the address identification information in the virtual private network VPC. The device according to claim 11, which further includes: a back-end server access module for correspondingly accessing multiple back-end servers according to the unique path indication information of the multiple back-end application servers; operation status check The module is used to check the running status of the accessed back-end server, and mark the abnormal identifier on the corresponding unique path indication information for the back-end server with abnormal status; the abnormal identifier is used to indicate the suspension of sending the back-end server The end server access request to the back end server. The device according to claim 11, further comprising: a network type identification module for identifying the network type of the first type of network where the client is located. The device according to claim 13, wherein the information acquisition module includes: a back-end server access request unblocking sub-module, which is used for the network type of the first type of network, from the back The end server access request unblocks the network identification information of the first type of network and the address identification information of the client, and generates unique path indication information of the client. The device according to claim 13, wherein the request response information return module includes: The request response information encapsulation sub-module is used to encapsulate the request response information for the network type of the first type of network and send it to the client. The device according to claim 11, further comprising: a network identification information receiving module, configured to receive and save the first type of the client submitted when the multiple clients register with the control device Network identification information of the network; the device further includes: a network identification information judgment module for judging whether the network identification information of the first type of network obtained from the back-end server access request is being stored If not, return access denied information to the client. A network load balancing control device, characterized in that, the device includes: a back-end server unique path indication information acquisition module, which is used to obtain from each back-end server that the back-end server is in the second type of network The unique path indication information of the road; the preset traffic scheduling rule sending module is used to send the preset traffic scheduling rule and the unique path indication information of the back-end server to the load balancing device for the load balancing device according to According to the indication of the unique path indication information of the back-end server, the client's back-end server access request is sent to at least one back-end server selected according to the preset traffic scheduling rule, and according to the client In the direction of the unique path indication information of the first type of network, return the request response information returned by the back-end server Back to the client, where the unique path indication information of the back-end server uniquely exists in the first type of network where the client is located and the second type of network where each back-end server is located, the The unique path indication information of the client only exists in the first type of network where the client is located and the second type of network where each back-end server is located. The first type of network and the second type of network At least one of the paths is a virtual private network VPC; wherein the unique path indication information is generated from the network identification information of the virtual private network VPC where it is located and the address identification information in the virtual private network VPC. The device according to claim 17, further comprising: a sending instruction module for instructing the load balancing device to send the unique path instruction information of the load balancing device to the back-end server for all The back-end server returns request response information to the load balancing device according to the unique path indication information of the load balancing device. The device according to claim 17, further comprising: a network identification information receiving module, configured to receive the network identification information of the first type of network where the client is located, submitted by the client during registration ; The network identification information sending module is used to send the network identification information of the first type of network to the load balancing device for the load balancing device to save and receive the backend of the client In the server access request, it is determined whether the network identification information of the first type of network obtained from the back-end server access request is within the range of the stored network identification information of the first type of network, if not, Then return the access denied information to the client. A network interactive device, characterized in that it comprises: The access request sending module is used to send the client's access request to the back-end server to the one selected according to the preset traffic scheduling rules according to the indication of the unique path indication information of the back-end server in the second type of network At least one back-end server, the second type of network is a virtual private network VPC; and/or a request response information return module for indicating information according to the unique path of the client in the first type of network To return the request response information returned by the back-end server in response to the client's access request to the client. The first type of network is a virtual private network VPC; wherein, the only path of the back-end server The indication information uniquely exists in the first type of network where the client is located and the second type of network where each back-end server is located, and the unique path indication information of the client is in the first type of network where the client is located A type network and the second type of network where each back-end server is located; wherein, the unique path indication information consists of the network identification information of the virtual private network VPC where it is located and in the virtual private network VPC The address identification information is generated.

Images