WO2017140216A1 - 一种网络的负载均衡、控制及网络交互方法和装置 - Google Patents

一种网络的负载均衡、控制及网络交互方法和装置 Download PDF

Info

Publication number
WO2017140216A1
WO2017140216A1 PCT/CN2017/072881 CN2017072881W WO2017140216A1 WO 2017140216 A1 WO2017140216 A1 WO 2017140216A1 CN 2017072881 W CN2017072881 W CN 2017072881W WO 2017140216 A1 WO2017140216 A1 WO 2017140216A1
Authority
WO
WIPO (PCT)
Prior art keywords
network
client
type
backend server
information
Prior art date
Application number
PCT/CN2017/072881
Other languages
English (en)
French (fr)
Inventor
陈家军
吴佳明
薛蹦蹦
杨玉玺
Original Assignee
阿里巴巴集团控股有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 阿里巴巴集团控股有限公司 filed Critical 阿里巴巴集团控股有限公司
Publication of WO2017140216A1 publication Critical patent/WO2017140216A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/12—Avoiding congestion; Recovering from congestion
    • H04L47/125—Avoiding congestion; Recovering from congestion by balancing the load, e.g. traffic engineering
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/13—Flow control; Congestion control in a LAN segment, e.g. ring or bus

Definitions

  • the present invention relates to the field of Internet technologies, and in particular, to a network load balancing method and a network load balancing device, and a network load balancing control method and a network load balancing control device, and a network An interaction method and a network interaction device.
  • the extended multiple back-end servers are usually virtualized as one virtual server to unify the external service interface.
  • the load balancer is usually used to schedule the access traffic to the actual back-end server (Real Server, RS) according to a certain algorithm to balance multiple Access traffic to the backend server.
  • VPC Virtual Private Cloud
  • VXLAN virtual eXtensible Local Area Network
  • the address is only in its domain uniquely, so that the load balancer cannot directly perform traffic scheduling processing, and the gateway needs to perform non-VPC on the server address.
  • the conversion of the address can be used for scheduling processing.
  • the original VPC address of the client and the server needs to be converted by the gateway, and the processing process increases the delay of the entire access, thereby causing the access efficiency to the back-end server. Low problem.
  • the load balancer cannot know the real network address of the client, and the access control client cannot be accurately accessed. Further, address translation also consumes traditional IP addresses.
  • embodiments of the present application have been made in order to provide a network load balancing method and a corresponding network load balancing apparatus that overcome the above problems or at least partially solve the above problems, and a network load.
  • a network load balancing method including:
  • the first type of network and the second type of network where each backend server is located are uniquely present, and at least one of the first type of network and the second type of network is a virtual private network (VPC).
  • VPC virtual private network
  • the unique path indication information is generated by network identification information of the virtual private network VPC and the address identification information in the virtual private network VPC.
  • it also includes:
  • the abnormality identifier is used to indicate that the backend server access request is suspended from being sent to the backend server.
  • the method further includes: before the step of acquiring the unique path indication information of the client in the first type of network, in the backend server access request sent by the client, the method further includes:
  • the step of obtaining the unique path indication information of the client in the first type of network in the backend server access request sent by the client includes:
  • the step of returning the request response information to the client includes:
  • the request response information is encapsulated and sent to the client for the network type of the first type of network.
  • the method further includes: before the step of acquiring the unique path indication information of the client in the first type of network, in the backend server access request sent by the client, the method further includes:
  • the method further includes:
  • the present application also discloses a network load balancing control method, including:
  • the load balancing device sends the back-end server of the client according to the unique path indication information of the back-end server
  • the access request is sent to at least one backend server selected according to the preset traffic scheduling rule, and the request response information returned by the backend server according to the unique path indication information of the client in the first type of network
  • the unique path indication information uniquely exists in a first type of network where the client is located and a second type of network in which each backend server is located, the first type of network and the first At least one of the second type networks is a virtual private network VPC.
  • the unique path indication information is generated by network identification information of the virtual private network VPC and the address identification information in the virtual private network VPC.
  • it also includes:
  • it also includes:
  • the present application also discloses a network interaction method, including:
  • the network is a virtual private network VPC;
  • the request response information returned by the backend server for the client's access request according to the unique path indication information of the client in the first type of network, where the first type of network is a virtual private Network VPC;
  • the unique path indication information uniquely exists in the first type of network where the client is located and the second type of network in which each backend server is located.
  • a load balancing device for a network including:
  • the preset traffic scheduling rule receiving module is configured to receive a preset traffic scheduling rule sent by the control device, and a unique path indication information of the backend server in the second type network;
  • An information obtaining module configured to obtain, by the backend server access request sent by the client, the unique path indication information of the client in the first type of network;
  • a backend server access request sending module configured to send the backend server access request to at least one backend server selected according to the preset traffic scheduling rule according to the unique path indication information of the backend server;
  • a request response information returning module configured to receive request response information returned by the backend server, and return the request response information to the client according to the unique path indication information of the client, where the unique path
  • the indication information is uniquely present in the first type of network in which the client is located and in the second type of network in which the backend servers are located.
  • At least one of the first type of network and the second type of network is a virtual private network (VPC).
  • VPC virtual private network
  • the unique path indication information is generated by network identification information of the virtual private network VPC and the address identification information in the virtual private network VPC.
  • it also includes:
  • the back-end server access module is configured to access multiple back-end servers according to unique path indication information of multiple back-end application servers.
  • the running status check module is configured 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 pause Sending the backend server access request to the backend server.
  • it also includes:
  • a network type identification module is configured to identify a network type of the first type of network in which the client is located.
  • the information acquiring module includes:
  • a backend server access request decapsulation submodule configured to, for the network type of the first type of network, unpack the network identification information of the first type of network and the client from the backend server access request The address identifies the information and generates unique path indication information of the client.
  • the request response information returning module includes:
  • a request response information encapsulating submodule configured to encapsulate the request response information for the network type of the first type of network and send the request response information to the client.
  • it also includes:
  • a network identifier information receiving module configured to receive and save network identifier information of a first type of network where the client is located when the plurality of clients register with the control device;
  • the device also includes:
  • the network identifier information determining module is configured to determine whether the network identifier information of the first type network acquired by the backend server access request is within the range of the saved network identifier information of the first type network, and if not, returning the rejection Access information to the client.
  • a load balancing control device for a network including:
  • the back-end server unique path indication information obtaining module is configured to obtain, from each back-end server, unique path indication information of the back-end server in the second type of network;
  • a preset traffic scheduling rule sending module configured to send the preset traffic scheduling rule and the unique path indication information of the backend server to the load balancing device, where the load balancing device indicates according to the unique path of the backend server And sending, to the client, the backend server access request of the client to the at least one backend server selected according to the preset traffic scheduling rule, and according to the unique path indication information of the client in the first type of network, Returning the request response information returned by the backend server 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 in which each backend server is located. 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 by network identification information of the virtual private network VPC and the address identification information in the virtual private network VPC.
  • it also includes:
  • a sending indication module configured to send, by the load balancing device, the unique path indication information of the load balancing device to the backend server, where the backend server follows the unique path indication information of the load balancing device, Returning request response information to the load balancing device.
  • it also includes:
  • a network identifier information receiving module configured to receive network identifier information of a first type network of the client that is submitted by the client when registering;
  • a network identifier information sending module configured to send network identifier information of the first type of network to the load balancing device, where the load balancing device saves and receives a backend server access request of the client, Determining whether the network identification information of the first type of network acquired from the backend server access request is within the range of the saved network identification information of the first type of network, and if not, returning the denied access information to the client.
  • a network interaction device including:
  • the access request sending module is configured to send, according to the unique path indication information of the back-end server in the second type network, the client-side access request to the back-end server to the at least one backend selected according to the preset traffic scheduling rule.
  • a server, the second type of network is a virtual private network VPC;
  • the request response information returning module is configured to return the request response information returned by the backend server to 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 a virtual private network VPC;
  • the unique path indication information uniquely exists in the first type of network where the client is located and the second type of network in which each backend server is located.
  • the load balancer sends the access request to the backend server by using the unique path indication information of the backend server delivered by the control device, and the load balancer obtains the client by using the backend server access request sent by the client.
  • the unique path indication information of the end forwards the backend server return request response information to the client.
  • the unique path indication information of the client and the back-end server is unique in the first type of network where the client is located and the second type of network in which each back-end server is located, in the first type network and the second type network
  • at least one of the virtual private network VPCs does not need the address translation processing of the gateway to the client and the backend server, thereby avoiding the access delay caused by the gateway performing address translation processing and improving the client's access to the backend server.
  • the efficiency and return efficiency of the request response information of the backend server also saves the processing resources of the gateway. Moreover, since there is no need to convert the addresses of the client and the backend server, the consumption of the IP address of the non-VPC by the client and the backend server is saved.
  • the embodiment of the present application does not need to perform conversion processing through the gateway, and the load balancer can obtain the client.
  • the real network address allows for precise access control to the client.
  • Embodiment 1 is a flow chart showing the steps of Embodiment 1 of a network load balancing method according to the present application;
  • Embodiment 2 is a flow chart showing the steps of Embodiment 2 of a network load balancing method according to the present application;
  • FIG. 3 is a flow chart showing the steps of an embodiment of a load balancing control method for a network according to the present application
  • Embodiment 1 of a network load balancing apparatus according to the present application.
  • Embodiment 6 is a structural block diagram of Embodiment 2 of a network load balancing device of the present application.
  • FIG. 7 is a structural block diagram of an embodiment of a load balancing control apparatus for a network according to the present application.
  • FIG. 8 is a structural block diagram of an embodiment of a network interaction apparatus according to the present application.
  • FIG. 9 is a schematic diagram of the working principle of a current load balancer
  • FIG. 10 is a schematic diagram of a working principle of using a gateway for load balancing
  • FIG. 11 is a schematic diagram of an application scenario 1 of a load balancing method of the present application.
  • FIG. 12 is a schematic diagram of an application scenario 2 of a load balancing method of the present application.
  • FIG. 13 is a schematic diagram of an application scenario 3 of a load balancing method of the present application.
  • FIG. 15 is a structural diagram of a load balancing system according to an embodiment of the present application.
  • FIG. 16 is a schematic flowchart of the VSOCK module assisting health check according to an embodiment of the present application.
  • Embodiment 1 of a network load balancing method of the present application is shown, which may specifically include the following steps:
  • Step 101 Receive a preset traffic scheduling rule sent by the control device, and a unique path indication information of the backend server in the second type of network.
  • the network can be of various types, such as a wide area network of a common IP network and a virtual private network VPC.
  • IP network uses IP (Internet Protocol) communication protocol to interconnect multiple computer terminals, clients, and services.
  • a network of services can be understood as a public network.
  • Each terminal in the IP network has a proprietary IP address, and identifies and distinguishes different terminals based on the IP address, so as to facilitate accurate transmission of information.
  • virtual private network VPCs use encryption protocols, tunneling protocols, and other security procedures to form a private and independent virtual network environment in a public IP network.
  • VPC users can customize in virtual private network VPCs. The IP address range of each terminal.
  • the foregoing second type of network may be a wide area network, or may be a virtual private network VPC. That is, the backend server may be in the WAN or in the virtual private network VPC.
  • the unique path indication information of the back-end server described above may uniquely correspond to a certain back-end server, and the unique path indication information may communicate with its corresponding back-end server.
  • control device may send the preset traffic scheduling rule and the unique path indication information of the multiple backend servers to the load balancer.
  • the load balancer receives the preset traffic scheduling rule and the unique path indication information of the backend server to facilitate subsequent traffic scheduling processing.
  • control device can also send the unique path indication information of the load balancer to the client.
  • Traffic scheduling rules can be various, such as WRR (Weighted Round Robin), RR (Round-Robin, Polling Scheduling Algorithm), WLC (Weighted Least-Connection Scheduling), etc.
  • WRR Weighted Round Robin
  • RR Raund-Robin, Polling Scheduling Algorithm
  • WLC Weighted Least-Connection Scheduling
  • Step 102 Obtain unique path indication information of the client in the first type of network from the backend server access request sent by the client.
  • the foregoing first type of network may be a wide area network, or may be a virtual private network VPC. That is, the client may be in the WAN or in the virtual private network VPC.
  • the unique path indication information of the above client may uniquely correspond to a certain client, and the unique path indication information may communicate with the corresponding client.
  • the client can obtain a corresponding service by sending a backend server access request to the backend server.
  • the access request may be received by the load balancer before the backend server access request is sent to the actually processed backend server to further dispatch the access request to the appropriate backend server.
  • the unique path indication information of the client may be obtained, and the unique path indication information is learned and used to indicate the address of the client when the request response information is returned to the client.
  • the step 102 may also be performed before the step 101. That is, the first path indication information of the client may be obtained from the backend server access request, and the preset traffic scheduling rule and multiple The unique path indication information for the backend server.
  • the load balancer when the load balancer receives the backend server access request sent by the client, it indicates that the client has initially established a connection, and the unique path indication information of the client may be recorded and learned, so that after receiving the After the end server correspondingly returns the request response information, the unique path indication information is used to return the request response information to the client.
  • Step 103 Send, according to the unique path indication information of the backend server, the backend server access request to at least one backend server selected according to the preset traffic scheduling rule.
  • the preset traffic scheduling rule can be used to calculate the load status of each back-end server, and the back-end server that can be scheduled is selected accordingly, and the back-end server access request is forwarded according to the unique path indication information of the selected back-end server.
  • the backend 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 request response information returned by the backend 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 at the client end.
  • the first type of network and the second type of network in which each backend server is located are uniquely present, and at least one of the first type of network and the second type of network is a virtual private network (VPC).
  • VPC virtual private network
  • the request response information may be returned to the client according to the previously recorded unique path indication information of the client.
  • the request response information may be sent to the unique corresponding backend server.
  • the request response information may be sent to the unique corresponding client according to the indication of the unique path indication information of the client.
  • the address translation processing of the gateway to the client and the backend server may not be required, thereby avoiding the access caused by the gateway performing address translation processing.
  • the delay improves the access efficiency of the client to the backend server and the return efficiency of the request response information of the backend server, and also saves the processing resources of the gateway.
  • the consumption of the IP address of the non-VPC by the client and the backend server is saved.
  • the embodiment of the present application does not need to perform conversion processing through the gateway, and the load balancer can obtain the real network address of the client, so that the access control can be accurately performed on the client.
  • the embodiment of the present application can be applied to the second type of network where the first type network and the back end server are located, and at least one network is an application scenario of the virtual private network VPC. Specifically, the following may be used.
  • the back end service When the first type of network where the client is located is a wide area network, if there is only one backed server scheduled, the back end service
  • the second type of network in which the server is located is a virtual private network VPC. If there are multiple backend servers scheduled, the multiple backend servers may all be in the virtual private network VPC, or at least one backend server in the virtual private network VPC and the remaining backend servers in the wide area network. In the case that multiple back-end servers are in the virtual private network VPC, they may all be in the same virtual private network VPC, or all in different virtual private network VPCs, or partially in the same virtual private network VPC.
  • the first type of network in which the client is located is a virtual private network VPC
  • the second type of network in which the backend server is located is a virtual private network VPC or a wide area network.
  • the multiple back-end servers may all be in the virtual private network VPC, or all in the wide area network, or partially in the wide area network, and partially in the virtual private network VPC.
  • they may all be in the same virtual private network VPC, or all in different virtual private network VPCs, or partially in the same virtual private network VPC.
  • the second type of network when the first type of network is a virtual private network VPC, the second type of network may be a wide area network, or may be a virtual private network VPC, that is, a first type network and a second type.
  • the class network may be isomorphic or heterogeneous; when the first type of network is a wide area network, the second type of network may be a virtual private network VPC, that is, the first type of network and the second type of network are heterogeneous.
  • the unique path indication information may be generated by network identification information of a virtual private network VPC and an address identification information in the virtual private network VPC.
  • the network identifier information of the first type of network where the client is located and the address identification information of the first type of network where the client is located may be obtained from the backend server access request, and the unique identifier of the client is generated accordingly.
  • Path indication information may be obtained from the backend server access request, and the unique identifier of the client is generated accordingly.
  • the client in the virtual private network VPC based on the VXLAN can send the access request to the encapsulated VXLAN packet.
  • the VXLAN packet can be decapsulated.
  • the network identification information VNI of the virtual private network VPC where the client is located is obtained, and the IP address information of the client as the VTEP destination address in the virtual private network VPC is obtained, thereby generating unique path indication information of the client.
  • VXLAN is a commonly used technology for constructing a virtual private network VPC. It uses the MAC in UDP method to access the server through VXLAN packets and encapsulates and resolves with VTEP (VXLAN Tunnel End Point). Seal the VXLAN message.
  • the VXLAN packet contains VNI (VXLAN Network Identifier) information, and the IP address information and the packet inner layer information of the VTEP destination address in the virtual private network VPC.
  • VNI information is the virtual private network VPC of the client.
  • Network identification information, the inner layer information of the message includes the IP address of the virtual private network VPC where the client is located, and the port information.
  • the sent backend server access request may include network identification information of the network where the client is located, and address identification information in the first type of network, and the load balancer may obtain the network identification information and the address identification information. And generate a unique path indication information for the client.
  • the backend server access request generated by using the VXLAN message includes 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, and the client can be generated accordingly.
  • the only path indication on the end is VNI79/192.168.0.1.
  • GRE Generic Routing Encapsulation
  • the VXLAN packet containing the network identifier information VNI and the address information may be sent to the control device, and the control device generates the unique path indication information of the back-end server and sends the information to the control device.
  • a load balancer that directs information to the backend server based on the unique path of the backend server.
  • the back-end server generates the unique path indication information according to the network identifier information VNI and the address information, and the encapsulation is sent to the load balancer via the control device in the VXLAN message.
  • Embodiment 2 of the network load balancing method of the present application may specifically include the following steps:
  • Step 201 Receive and save network identification information of a first type of network where the client is submitted when the multiple clients register with the control device.
  • 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 when registering.
  • the control device may send the network identification information of the first type of network received at the time of registration to the load balancer.
  • Step 202 Receive a preset traffic scheduling rule sent by the control device, and unique path indication information of the back-end server in the second type network, where the unique path indication information is in the first type of network where the client is located, and Each back-end server is 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).
  • VPC virtual private network
  • Step 203 Access multiple back-end servers correspondingly according to the unique path indication information of the multiple back-end application servers.
  • Step 204 Perform a running status check on 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 that the back-end server access request is suspended. To the backend server.
  • the load balancer usually checks the running status of the back-end server before performing the traffic scheduling process, and does not schedule traffic to the server whose operating state is abnormal. There are various operational exceptions, such as slow server response, application failure on the server, and application association errors on the server.
  • the load balancer can access each back-end server and check the running status according to the unique path indication information of the back-end application server before performing the traffic scheduling process. For a server with abnormal status, an abnormal identifier can be marked on the corresponding unique path indication information. When the traffic is scheduled, the server carrying the abnormal identifier is suspended from sending an access request to ensure that the server is operating normally. Providing the service as a result of the visit. Therefore, the load balancer accesses the back-end server by using the unique path indication information of the back-end server delivered by the control device, because the unique path indication information of the back-end server is in the first-type network and each back-end server where the client is located. The only type of network that exists is the only one, so the check processing of the back-end server running status can be realized without the participation of the gateway.
  • a running status check auxiliary module can be set in the load balancer.
  • the module can be set at the bottom of the system.
  • the load balancer creates a connection with the backend server through the running status check program, it is saved by the system call.
  • the unique path indication information of some back-end servers the module encapsulates a VXLAN message according to the unique path indication information of the back-end server, and sends it to the corresponding back-end server.
  • Step 205 Identify a network type of the first type of network where the client is located.
  • the client may be in a virtual private network VPC based on VXLAN or a traditional wide area network
  • different networks adopt different network protocols
  • the load balancer may adopt a suitable type according to different network protocols.
  • Step 206 Decapsulate the network identification information of the first type network and the address identification information of the client from the backend server access request for the network type of the first type of network, and generate the client The only path indication information for the end.
  • the backend server access request initiated by the client in the first type of network may be based on the first type of network
  • the characteristics of the network type of the network, the network identification information of the first type of network and the address identification information of the client are decapsulated from the access request, and the unique path indication information of the client is generated accordingly.
  • the load balancer when the load balancer receives the backend server access request sent by the client, it indicates that the client has initially established a connection with the client. In this case, the unique path indication information of the client can be recorded and learned, and can be used in subsequent processing. The unique path indication information returns the request response information to the client.
  • Step 207 determining whether the network identification information of the first type network acquired from the backend server access request is within the range of the saved network identification information of the first type network, and if not, returning the denied access information to the Client; if yes, step 208 is performed.
  • the network identifier information pre-stored may be used to find whether there is a corresponding network identifier information that is decapsulated from the access request. If the network identification information is not found, indicating that the client or the network where the client is located has not been registered on the control device, the access denied information may be returned to the client. If the network identification information is found, the next step of the traffic scheduling process can be continued.
  • Step 208 Send, according to the unique path indication information of the backend server, the backend server access request to at least one backend server selected according to the preset traffic scheduling rule.
  • the preset traffic scheduling rule can be used to calculate the load status of each back-end server, and the back-end server that can be scheduled is selected accordingly, and the back-end server access request is forwarded according to the unique path indication information of the selected back-end server.
  • the backend 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 request response information returned by the backend server, and encapsulate the request response information for the network type of the first type network according to the unique path indication information of the client, and send the request response information to the client. .
  • the request response information may be encapsulated according to the previously determined network type of the first type network, and the information is returned to the client according to the unique path indication information of the recorded client. end.
  • a VTEP automatic learning module may be deployed on the backend server to learn to record the VTEP address information of the load balancer.
  • the backend server can 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.
  • the load balancer sends the access request to the backend server by using the unique path indication information of the backend server delivered by the control device, and the load balancer uses the backend server sent by the client.
  • the access request acquires the unique path indication information of the client, and forwards the backend server return request response information to the client.
  • the unique path indication information of the client and the back-end server is unique in the first type of network where the client is located and the second type of network in which each back-end server is located, in the first type network and the second type network
  • at least one of the virtual private network VPCs does not need the address translation processing of the gateway to the client and the backend server, thereby avoiding the access delay caused by the gateway performing address translation processing and improving the client's access to the backend server.
  • the efficiency and return efficiency of the request response information of the backend server also saves the processing resources of the gateway. Moreover, since there is no need to convert the addresses of the client and the backend server, the consumption of the IP address of the non-VPC by the client and the backend server is saved.
  • the embodiment of the present application does not need to perform conversion processing through the gateway, and the load balancer can obtain the real network address of the client, so that the access control can be accurately performed on the client.
  • the load balancer accesses the back-end server by using the unique path indication information of the back-end server delivered by the control device, because the unique path indication information of the back-end server is in the first-type network where the client is located. And the only type of network in which the back-end servers are located. Therefore, the VPC address of the back-end server can be converted without using a gateway, and the back-end server can be checked for running status by using the unique path indication information of the back-end server. The delay caused by the address translation process of the gateway is avoided, and the efficiency of the running state check is improved.
  • the method may include the following steps:
  • Step 301 Obtain unique path indication information of the backend server in the second type of network from each backend server.
  • the control device may obtain unique path indication information of the backend server from each backend server for indicating that the information is accurately transmitted to the backend server.
  • the unique path indication information may be generated by network identification information of a virtual private network VPC and an address identification information in the virtual private network VPC.
  • the control device may obtain, from the plurality of back-end servers, network identification information of each second-type network where the back-end servers are respectively located, and address identification information of the second-type network of the back-end server, and generate correspondingly Unique path indication information for each backend server.
  • Step 302 Send the preset traffic scheduling rule and the unique path indication information of the backend server to the load balancing device, so that the load balancing device sends the client according to the unique path indication information of the backend server.
  • the backend server access request is sent to at least one backend selected according to the preset traffic scheduling rule And returning, by the server, the request response information returned by the backend server to the client according to the unique path indication information of the client in the first type of network, where the unique path indication information is at the client end
  • the first type of network and the second type of network in which each backend server is located are uniquely present, and at least one of the first type of network and the second type of network is a virtual private network (VPC).
  • VPC virtual private network
  • the control device sends the preset traffic scheduling rule and the unique path indication information of the multiple backend servers to the load balancing device.
  • the load balancing device may obtain the unique path indication information of the first type of network where the client is located from the access request, and calculate each backend server by using the preset traffic scheduling rule.
  • the load situation correspondingly selects the back-end server that can be scheduled, according to the unique path indication information of the selected back-end server, correspondingly forwards the back-end server access request to the back-end server, and the back-end server processes and responds An access request from the client and a corresponding request response message to the load balancing device.
  • the load balancing device may return the request response information to the client according to the unique path indication information of the client.
  • the load balancing device may be a load balancer, or any device responsible for scheduling an access request sent by the client to at least one backend server.
  • the load balancer sends the access request to the backend server by using the unique path indication information of the backend server delivered by the control device, because the unique path indication information of the backend server is at the client end.
  • the first type of network and the second type of network where each back-end server is located exist only. Therefore, when at least one of the first type network and the second type network is a virtual private network VPC, the gateway to the back-end server may not be needed.
  • the address conversion process avoids the access delay caused by the gateway performing address translation processing, improves the access efficiency of the client to the backend server, and also saves the processing resources of the gateway. Moreover, since there is no need to convert the address of the backend server, the consumption of the IP address of the non-VPC by the backend server is saved.
  • the embodiment of the present application does not need to perform conversion processing through the gateway, and the load balancer can obtain the real network address of the client, so that the access control can be accurately performed on the client.
  • the method may further include: instructing the load balancing device to send the unique path indication information of the load balancing device to the backend server, where the backend server according to the The unique path indication information of the load balancing device returns the request response information to the load balancing device.
  • the control device may also instruct the load balancing device to send its unique path indication information to the plurality of backend servers so that the backend server can accurately return the request response information to the load balancing device.
  • the method may further include: receiving network identification information of the first type network of the client that is submitted by the client when registering; and the network of the first type network Identification information Sending to the load balancing device, where the load balancing device saves and determines the network identifier information of the first type network acquired from the backend server access request when receiving the backend server access request of the client Whether it is within the range of the saved network identification information of the first type of network, and if not, returning the denied access information to 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 when registering.
  • the control device may send the collected network identification information of the first type of network to the load balancing device.
  • the load balancing device may save the received network identification information of the first type of network, and when receiving the backend server access request initiated by the client, may obtain the network identification information of the first type of network where the client is located from the access request. In the pre-stored network identification information, it is found whether there is network identification information of the first type of network in which the client is located. If the network identification information is not found, indicating that the client or the network where the client is located has not been registered on the control device, the access denied information may be returned to the client. If the network identification information is found, the next step of the traffic scheduling process can be continued.
  • FIG. 4 a flow chart of steps of a network interaction method embodiment of the present application is shown, which may specifically include the following steps:
  • Step 401 Send, according to the unique path indication information of the back-end server in the second type network, 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.
  • the second type of network is a virtual private network VPC.
  • the load balancer can calculate the load status of each back-end server by using a preset traffic scheduling rule, and correspondingly select a back-end server that can be scheduled, according to Selecting the unique path indication information of the backend server, forwarding the backend server access request to the backend server accordingly, processing and responding to the access request from the client by the backend server, and returning the request response information to the load balancer accordingly .
  • Step 402 Return the request response information returned by the backend server to the client's access request to the client according to the unique path indication information of the client in the first type of network, where the first type of network is a virtual private network. VPC.
  • the unique path indication information uniquely exists in the first type of network where the client is located and the second type of network in which each backend server is located.
  • the load balancer receives the request response information of the backend server in response to the access request, and may return the request response information to the client accordingly.
  • the second type of network where the client is located is a virtual private network VPC, you can follow
  • the unique path indication information of the client returns the request response information to the client accordingly.
  • step 401 may be performed, or step 401 and step 402 may be performed.
  • the load balancer sends the access request to the backend server by using the unique path indication information of the backend server delivered by the control device, and the load balancer obtains the unique path of the client by using the access request sent by the client. Indicates that the backend server returns the request response message to the client.
  • the unique path indication information of the client and the back-end server is unique in the first type of network where the client is located and the second type of network in which each back-end server is located, in the first type network and the second type network
  • at least one of the virtual private network VPCs does not need the address translation processing of the gateway to the client and the backend server, thereby avoiding the access delay caused by the gateway performing address translation processing and improving the client's access to the backend server.
  • the efficiency and return efficiency of the request response information of the backend server also saves the processing resources of the gateway. Moreover, since there is no need to convert the addresses of the client and the backend server, the consumption of the IP address of the non-VPC by the client and the backend server is saved.
  • the embodiment of the present application does not need to perform conversion processing through the gateway, and the load balancer can obtain the real network address of the client, so that the access control can be accurately performed on the client.
  • Figure 9 shows a schematic diagram of the operation of the current load balancer.
  • the client client accesses a server to obtain the service.
  • the VIP:VPORT port of the load balancer LB is accessed correspondingly.
  • the access is distributed to the plurality of backend servers RS1, RS2, RS3, or RS4 that actually provide services according to a certain traffic scheduling rule.
  • the backend server RS1, RS2, RS3 or RS4 receives the access from the client through the respective RIP1:RPORT1, RIP2:RPORT2, RIP3:RPORT3 and RIP4:RPORT4 ports, and returns the processing result to the load balancer after the corresponding processing. .
  • the load balancer returns the result of the processing to the client by accessing the CIP:CPORT port of the client.
  • the load balancer scheduling is four-layer load balancing (L4LB) according to TCP/UDP scheduling, and seven layers of load balancing (L7LB) according to the application layer (http, ftp, etc.).
  • the load balancer also has the function of checking the health of the back-end server, ignoring the back-end server that fails the health check when distributing traffic.
  • FIG. 10 shows a schematic diagram of the current working principle of using a gateway for load balancing.
  • the client is in the VXLAN type virtual private network VPC with the network identifier VNI79.
  • the IP address of the virtual private network VPC is 192.168.0.1, which is only unique in the VNI79 virtual private network VPC. Need
  • the gateway VXLAN Gateway converts the VPC address into a non-VPC address and converts it into a unique IP address 10.18.0.1 in the entire network, so that it can be accessed via the scheduling of the load balancer LB with the IP address 10.1.2.3.
  • the backend servers RS1 and RS2 in the virtual private network VPC with the network identifier VNI79 have unique address identification information 192.168.1.11 and 192.168.2.12 in their network, and the backend servers RS1 and RS2 in the virtual private network VPC of VNI1234 There are unique address identification information 172.16.100.11 and 172.16.20.21 in the network where they are located. However, the address identification information of each back-end server is unique only in the virtual private network VPC in which it resides, and it needs to be converted into IP addresses 10.16.1.11, 10.16.2.12, 10.16.3.13, and 10.16.4.14 respectively through the gateway to be able to load with the load.
  • the equalizer performs information interaction.
  • FIG. 11 and FIG. 12 are respectively schematic diagrams showing application scenarios in which a plurality of back-end servers are in a virtual private network VPC and a plurality of back-end servers are in a wide area network, when the client is in a virtual private network VPC.
  • a part of the plurality of back-end servers may be included in the WAN, and some of them are in the virtual private network VPC.
  • Figure 13 shows a schematic diagram of an application scenario in which multiple back-end servers are in a virtual private network VPC when the client is in the WAN. In practical applications, it may also be the case that at least one back-end server is in the virtual private network VPC and the remaining back-end servers are in the wide area network.
  • FIG. 11 is a schematic diagram of an application scenario 1 of a load balancing method of the present application.
  • the client client is in the virtual private network VPC with the network identifier VNI79, and the address in the virtual private network VPC of the VNI 79 is 192.168.0.1.
  • the client may obtain the unique path indication information VNI79/192.168.10.1 of the load balancer LB when registering with the control device, and access the load balancer LB according to the unique path indication information to initiate access to the backend server via the load balancer. request.
  • 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.
  • VPC virtual private network
  • VNI123 virtual private of VNI1234.
  • the backend server has unique address identification information 192.168.1.11, 192.168.2.12, 172.16.100.11, and 172.16.20.21 in the virtual private network VPC to which it belongs.
  • the load balancer can obtain unique path indication information of multiple backend servers from the control device. As seen in the figure, the load balancer can obtain the unique path indication information VNI79/192.168.1.11 and VNI79/192.168.2.12 of the backend servers RS1 and RS2 in the virtual private network VPC with the network identifier VNI79, and the virtual of the VNI1234.
  • the unique path indication information of the backend servers RS1 and RS2 in the private network VPC is VNI1234/172.16.100.11 and VNI1234/172.16.200.12.
  • client-initiated access requests can be accurately dispatched to the backend server.
  • the backend 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, the VPC address of the client and the backend server is not converted to a non-VPC address through the gateway, and the load balancer can accurately schedule the client's access to the backend server, and can accurately respond to the backend server. Return to the client accurately.
  • the client and back-end servers can also be in a virtual private network VPC built on GRE, or some of the client and back-end servers are in a virtual private network VPC created based on VXLAN, and some are based on GRE. Created in a virtual private network VPC.
  • a person skilled in the art can apply the embodiment of the present application to a virtual private network VPC constructed in multiple ways.
  • FIG. 12 is a schematic diagram of an application scenario 2 of a load balancing method of the present application.
  • the client client is in the virtual private network VPC, while the backend servers RS1 and RS2 are in the traditional wide area network.
  • the load balancer generates the unique path indication information of the client and records the learning by using 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.
  • the load balancing server schedules the client-initiated access request to the back-end servers RS1 and RS2 with IP addresses 100.12.11.11 and 100.12.1.12, and the response information of the back-end server, according to the unique path indication information of the client learned by the record. , return to the client.
  • the VPC address does not need to be converted to a non-VPC address through the gateway, and the load balancer can accurately dispatch the client's access to the backend server and return the response information to the client.
  • FIG. 13 is a schematic diagram of an application scenario 3 of a load balancing method of the present application.
  • the client is in the traditional WAN with an IP address of 10.18.0.1; while the back-end servers RS1 and RS2 are in the virtual private network VPC of the network identifier VNI79, and the IP addresses in the virtual private network VPC are respectively 192.168.1.11 and 192.168.2.12.
  • the load balancer schedules the client-initiated access request to the back-end server, it can be based on the network identifier of the back-end server VNI79 and its IP address in the virtual private network VPC.
  • 192.168.1.11 and 192.168.2.12 generate respective unique path indication information. Based on their respective unique path indication information, the load balancer can accurately schedule access requests to the backend server without having to go through the gateway to translate the VPC address of the backend server to a non-VPC address.
  • FIG. 14 is a flowchart of load balancing processing according to an embodiment of the present application.
  • the VXLAN message is first decapsulated from the access request initiated by the client, and the VNI information and the inner layer information of the message are obtained.
  • the scheduling module selects the backend server according to the obtained VNI information and the inner layer information of the packet including the client IP address, and the preset scheduling rule. If the client initially establishes a successful connection, the VTEP automatic learning module learns and records the acquired VNI information and the inner layer information of the message.
  • the VXLAN message is constructed according to the VNI information and the address information of the backend server, and is sent to the corresponding backend server. After receiving the request processing, the backend server returns the response information to the load balancer LB.
  • FIG. 15 is a structural diagram of a load balancing system according to an embodiment of the present application. As can be seen from the figure, the system includes the following key modules:
  • the control center is used to deliver scheduling rules to the load balancer. If it is a back-end server in the virtual private network VPC, the VNI information and IP address information of the back-end server need to be delivered to the load balancer.
  • the VXLAN processing module is configured to identify and receive the received VXLAN message according to the characteristics of the VXLAN protocol when receiving the access request sent by the client. When a request response is returned, a VXLAN message is encapsulated accordingly.
  • the VTEP automatic learning module is used to learn the address information of the client and record it when the client initially establishes a connection or the VTEP changes, and is used directly for returning the request response.
  • a scheduling module is configured to configure load balancing on the backend server according to an early scheduling rule.
  • the VSOCK module is used to assist in the health check of the backend server in the virtual private network VPC.
  • FIG 16 shows a flow diagram of an auxiliary health check using the VSOCK module.
  • the VSOCK module works at the bottom of the system.
  • the health check program first calls the VNI information and address information of the backend server through the system before the connection is created.
  • the subsequent VSOCK module will encapsulate or unpack the VXLAN message according to the called information and send it.
  • To the back-end server, information interaction with the back-end server can be completed without the participation of the gateway.
  • Embodiment 1 of a load balancing apparatus of a network of the present application is shown, which may specifically include the following modules:
  • the preset traffic scheduling rule receiving module 501 is configured to receive a preset traffic scheduling rule sent by the control device, and a unique path indication information of the backend server in the second type of network.
  • the information obtaining module 502 is configured to obtain the unique path indication information of the client in the first type of network from the backend server access request sent by the client.
  • the backend server access request sending module 503 is configured to send the backend server access request to at least one backend server selected according to the preset traffic scheduling rule according to the unique path indication information of the backend server. .
  • the request response information returning module 504 is configured to receive the request response information returned by the backend server, and return the request response information to the client according to the unique path indication information of the client, where the unique The path indication information is uniquely existed in the first type of network where the client is located and the second type of network in which the backend servers are located. At least one of the first type of network and the second type of network is a virtual private network (VPC).
  • VPC virtual private network
  • the load balancer sends the access request to the backend server by using the unique path indication information of the backend server delivered by the control device, and the load balancer obtains the client by using the backend server access request sent by the client.
  • the unique path indication information of the end forwards the backend server return request response information to the client.
  • the unique path indication information of the client and the back-end server is unique in the first type of network where the client is located and the second type of network in which each back-end server is located, in the first type network and the second type network
  • at least one of the virtual private network VPCs does not need the address translation processing of the gateway to the client and the backend server, thereby avoiding the access delay caused by the gateway performing address translation processing and improving the client's access to the backend server.
  • the efficiency and return efficiency of the request response information of the backend server also saves the processing resources of the gateway. Moreover, since there is no need to convert the addresses of the client and the backend server, the consumption of the IP address of the non-VPC by the client and the backend server is saved.
  • the embodiment of the present application does not need to perform conversion processing through the gateway, and the load balancer can obtain the real network address of the client, so that the access control can be accurately performed on the client.
  • the unique path indication information is generated by network identification information of a virtual private network VPC and an address identification information in the virtual private network VPC.
  • Embodiment 2 of a load balancing device of a network of the present application is shown. To include the following modules:
  • the network identifier information receiving module 601 is configured to receive and save network identifier information of the first type of network where the client is located when the plurality of clients register with the control device.
  • the preset traffic scheduling rule receiving module 602 is configured to receive a preset traffic scheduling rule sent by the control device, and a unique path indication information of the backend server in the second type network.
  • the backend server accessing module 603 is configured to access multiple backend servers according to the unique path indication information of the multiple backend application servers.
  • the operation status check module 604 is configured to perform an operation status check on the accessed back-end server, and mark the abnormality identifier on the corresponding unique path indication information for the back-end server with abnormal status; the abnormality identifier is used to indicate that the suspension is sent.
  • the backend server accesses the request to the backend server.
  • the network type identification module 605 is configured to identify a network type of the first type of network where the client is located.
  • the information obtaining module 606 is configured to obtain, from the backend server access request sent by the client, the unique path indication information of the client in the first type of network.
  • the network identifier information determining module 607 is configured to determine whether the network identifier information of the first type network acquired by the backend server access request is within the range of the saved network identifier information of the first type network, and if not, return Access to the client is denied access.
  • the backend server access request sending module 608 is configured to send the backend server access request to at least one backend server selected according to the preset traffic scheduling rule according to the unique path indication information of the backend server. .
  • the request response information returning module 609 is configured to receive the request response information returned by the backend server, and return the request response information to the client according to the unique path indication information of the client, where the unique The path indication information is uniquely existed in the first type of network where the client is located and the second type of network in which the backend servers are located. At least one of the first type of network and the second type of network is a virtual private network (VPC).
  • VPC virtual private network
  • the load balancer sends the access request to the backend server by using the unique path indication information of the backend server delivered by the control device, and the load balancer obtains the client by using the backend server access request sent by the client.
  • the unique path indication information of the end forwards the backend server return request response information to the client.
  • the unique path indication information of the client and the back-end server is unique in the first type of network where the client is located and the second type of network in which each back-end server is located, in the first type network and the second type network
  • at least one of the virtual private network VPCs does not need the address translation processing of the gateway to the client and the backend server, thereby avoiding the access delay caused by the gateway performing address translation processing and improving the client's access to the backend server.
  • effectiveness The return efficiency of the request response information with the backend server also saves the processing resources of the gateway.
  • the consumption of the IP address of the non-VPC by the client and the backend server is saved.
  • the embodiment of the present application does not need to perform conversion processing through the gateway, and the load balancer can obtain the real network address of the client, so that the access control can be accurately performed on the client.
  • the load balancer accesses the back-end server by using the unique path indication information of the back-end server delivered by the control device, because the unique path indication information of the back-end server is in the first-type network where the client is located. And the only type of network in which the back-end servers are located. Therefore, the VPC address of the back-end server can be converted without using a gateway, and the back-end server can be checked for running status by using the unique path indication information of the back-end server. The delay caused by the address translation process of the gateway is avoided, and the efficiency of the running state check is improved.
  • the information obtaining module 606 may include:
  • a backend server access request decapsulation submodule configured to, for the network type of the first type of network, unpack the network identification information of the first type of network and the client from the backend server access request The address identifies the information and generates unique path indication information of the client.
  • the request response information returning module 609 may include the following submodules:
  • a request response information encapsulating submodule configured to encapsulate the request response information for the network type of the first type of network and send the request response information to the client.
  • FIG. 7 a structural block diagram of an embodiment of a network load balancing control apparatus of the present application is shown, which may specifically include the following modules:
  • the back-end server unique path indication information obtaining module 701 is configured to obtain, from each back-end server, 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 backend server to the load balancing device, where the load balancing device is configured according to the unique path of the backend server. Instructing information, sending the client's backend server access request to at least one backend server selected according to the preset traffic scheduling rule, and according to the unique path indication information of the client in the first type of network, Returning the request response information returned by the backend server to the client, wherein the unique path indication information is uniquely present in the first type of network where the client is located and the second type of network where each backend server is located , At least one of the first type of network and the second type of network is a virtual private network VPC.
  • the load balancer sends the access request to the backend server by using the unique path indication information of the backend server delivered by the control device, because the unique path indication information of the backend server is at the client end.
  • the first type of network and the second type of network where each back-end server is located exist only. Therefore, when at least one of the first type network and the second type network is a virtual private network VPC, the gateway to the back-end server may not be needed.
  • the address conversion process avoids the access delay caused by the gateway performing address translation processing, improves the access efficiency of the client to the backend server, and also saves the processing resources of the gateway. Moreover, since there is no need to convert the address of the backend server, the consumption of the IP address of the non-VPC by the backend server is saved.
  • the embodiment of the present application does not need to perform conversion processing through the gateway, and the load balancer can obtain the real network address of the client, so that the access control can be accurately performed on the client.
  • the unique path indication information is generated by network identification information of a virtual private network VPC and an address identification information in the virtual private network VPC.
  • the apparatus may further include the following modules:
  • a sending indication module configured to send, by the load balancing device, the unique path indication information of the load balancing device to the backend server, where the backend server follows the unique path indication information of the load balancing device, Returning request response information to the load balancing device.
  • the apparatus may further include the following modules:
  • the network identifier information receiving module is configured to receive network identifier information of the first type network of the client that is submitted by the client when registering.
  • a network identifier information sending module configured to send network identifier information of the first type of network to the load balancing device, where the load balancing device saves and receives a backend server access request of the client, Determining whether the network identification information of the first type of network acquired from the backend server access request is within the range of the saved network identification information of the first type of network, and if not, returning the denied access information to the client.
  • FIG. 8 a structural block diagram of an embodiment of a network interaction apparatus of the present application is shown, which may specifically include the following modules:
  • the access request sending module 801 is configured to send the client's access request to the backend server to at least one selected according to the preset traffic scheduling rule according to the unique path indication information of the backend server in the second type of network.
  • End server, the second type of network is a virtual private network VPC;
  • And/or request response information returning module 802 for following the unique path of the client in the first type of network Instructing information, returning the request response information returned by the backend server for the client's access request to the client, the first type of network is a virtual private network VPC;
  • the unique path indication information uniquely exists in the first type of network where the client is located and the second type of network in which each backend server is located.
  • the load balancer sends the access request to the backend server by using the unique path indication information of the backend server delivered by the control device, and the load balancer obtains the client by using the backend server access request sent by the client.
  • the unique path indication information of the end forwards the backend server return request response information to the client.
  • the unique path indication information of the client and the back-end server is unique in the first type of network where the client is located and the second type of network in which each back-end server is located, in the first type network and the second type network
  • at least one of the virtual private network VPCs does not need the address translation processing of the gateway to the client and the backend server, thereby avoiding the access delay caused by the gateway performing address translation processing and improving the client's access to the backend server.
  • the efficiency and return efficiency of the request response information of the backend server also saves the processing resources of the gateway. Moreover, since there is no need to convert the addresses of the client and the backend server, the consumption of the IP address of the non-VPC by the client and the backend server is saved.
  • the embodiment of the present application does not need to perform conversion processing through the gateway, and the load balancer can obtain the real network address of the client, so that the access control can be accurately performed on the client.
  • the description is relatively simple, and the relevant parts can be referred to the description of the method embodiment.
  • embodiments of the embodiments of the present application can be provided as a method, apparatus, or computer program product. Therefore, the embodiments of the present application may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware. Moreover, embodiments of the present application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) including computer usable program code.
  • computer-usable storage media including but not limited to disk storage, CD-ROM, optical storage, etc.
  • the computer device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
  • the memory may include non-persistent memory, random access memory (RAM), and/or non-volatile memory in a computer readable medium, such as read only memory (ROM) or flash memory.
  • RAM random access memory
  • ROM read only memory
  • Memory is an example of a computer readable medium.
  • Computer readable media includes both permanent and non-permanent, removable and non-removable The media can be stored by any method or technology.
  • the information can be computer readable instructions, data structures, modules of programs, 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), other types of random access memory (RAM), read only memory. (ROM), electrically erasable programmable read only memory (EEPROM), flash memory or other memory technology, compact disk read only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, Magnetic tape cartridges, magnetic tape storage or other magnetic storage devices or any other non-transportable media can be used to store information that can be accessed by a computing device.
  • computer readable media does not include non-persistent computer readable media, such as modulated data signals and carrier waves.
  • Embodiments of the present application are described with reference to flowcharts and/or block diagrams of methods, terminal devices (systems), and computer program products according to embodiments of the present application. It will be understood that each flow and/or block of the flowchart illustrations and/or FIG.
  • These computer program instructions can be provided to a processor of a general purpose computer, special purpose computer, embedded processor or other programmable data processing terminal device to produce a machine such that instructions are executed by a processor of a computer or other programmable data processing terminal device
  • Means are provided for implementing the functions specified in one or more of the flow or in one or more blocks of the flow chart.
  • the computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing terminal device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device.
  • the instruction device implements the functions specified in one or more blocks of the flowchart or in a flow or block of the flowchart.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Computer And Data Communications (AREA)

Abstract

本申请提供了一种网络的负载均衡、控制及网络交互方法和装置。所述方法包括：接收控制设备发送的预设流量调度规则以及后端服务器在第二类网络的唯一路径指示信息；从客户端发送的后端服务器访问请求中获取客户端在第一类网络的唯一路径指示信息；将后端服务器访问请求发送到按照预设流量调度规则选择出的后端服务器；接收后端服务器返回的请求响应信息，并按照客户端的唯一路径指示信息将请求响应信息返回至客户端，唯一路径指示信息在客户端所处的第一类网络以及各后端服务器所处第二类网络中唯一存在，第一类网络和第二类网络中至少一个为虚拟私有网络VPC，采用本申请的方案可以不需要网关对客户端和后端服务器的地址转换处理。

Description

一种网络的负载均衡、控制及网络交互方法和装置
本申请要求2016年02月16日递交的申请号为201610087638.2、发明名称为“一种网络的负载均衡、控制及网络交互方法和装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及互联网技术领域，特别是涉及一种网络的负载均衡方法和一种网络的负载均衡装置，以及，一种网络的负载均衡控制方法和一种网络的负载均衡控制装置，以及一种网络交互方法和一种网络交互装置。
背景技术
随着互联网技术的发展，服务器所承担的来自客户端的访问流量越来越庞大和频繁，服务器的扩展性越发重要。为了便于客户端的访问，通常会将扩展的多台后端服务器虚拟为一个虚拟服务器，以统一对外提供服务的接口。在客户端和后端服务器之间，通常由负载均衡器(Load Balancer，LB)根据一定的算法，将访问流量调度到实际提供服务的后端服务器上(Real Server，RS)，以平衡多个后端服务器的访问流量。
对于一些基于VXLAN(Virtual eXtensible Local Area Network，虚拟可扩展局域网)建立的VPC(Virtual Private Cloud，虚拟私有云)域内的客户端，其地址仅仅在其域内唯一，无法直接访问域外的设备，因此需要经过网关的地址转换处理。在访问域外的设备时，需要经过网关将其地址转换为一个非VPC地址，才得以顺利经过负载均衡器的调度访问后端服务器。
此外，在负载均衡器对VPC域内的后端服务器进行访问流量调度时，因为其地址仅仅在其域内唯一，导致负载均衡器无法直接进行流量调度处理，也需要经过网关对服务器的地址进行非VPC地址的转换，才能实现调度处理。
由于在客户端对后端服务器访问的过程中，客户端和服务器原有的VPC地址都需要经过网关的转换处理，处理过程增加了整个访问的时延，从而造成了对后端服务器访问效率较低的问题。另外,经过网关转换处理后负载均衡器无法得知客户端真实的网络地址,就无法精确访问控制客户端。进一步地，地址转换还会消耗传统的IP地址。
发明内容
鉴于上述问题，提出了本申请实施例以便提供一种克服上述问题或者至少部分地解决上述问题的一种网络的负载均衡方法和相应的一种网络的负载均衡装置，以及，一种网络的负载均衡控制方法和相应的一种网络的负载均衡控制装置，以及一种网络交互方法和一种网络交互装置。
为了解决上述问题，本申请公开了一种网络的负载均衡方法，包括：
接收控制设备发送的预设流量调度规则，以及后端服务器在第二类网络的唯一路径指示信息；
从客户端发送的后端服务器访问请求中，获取所述客户端在第一类网络的唯一路径指示信息；
根据所述后端服务器的唯一路径指示信息，将所述后端服务器访问请求，发送到按照所述预设流量调度规则选择出的至少一个后端服务器；
接收所述后端服务器返回的请求响应信息，并按照所述客户端的唯一路径指示信息，将所述请求响应信息返回至所述客户端，其中，所述唯一路径指示信息在所述客户端所处的第一类网络以及各后端服务器所处第二类网络中唯一存在，所述第一类网络和所述第二类网络中至少一个为虚拟私有网络VPC。
可选地，所述唯一路径指示信息由所在虚拟私有网络VPC的网络标识信息以及在所述虚拟私有网络VPC中的地址标识信息生成。
可选地，还包括：
按照多个后端应用服务器的唯一路径指示信息，相应访问多个后端服务器；
对访问的后端服务器进行运行状态检查，针对状态异常的后端服务器，在对应的唯一路径指示信息上标记异常标识；所述异常标识用于指示暂停发送所述后端服务器访问请求至后端服务器。
可选地，在所述从客户端发送的后端服务器访问请求中，获取所述客户端在第一类网络的唯一路径指示信息的步骤之前，所述方法还包括：
识别所述客户端所处的第一类网络的网络类型。
可选地，所述从客户端发送的后端服务器访问请求中，获取所述客户端在第一类网络的唯一路径指示信息的步骤包括：
针对所述第一类网络的网络类型，从所述后端服务器访问请求中解封出所述第一类网络的网络标识信息和所述客户端的地址标识信息，并生成所述客户端的唯一路径指示信息。
可选地，所述将所述请求响应信息返回至所述客户端的步骤包括：
针对所述第一类网络的网络类型，封装所述请求响应信息并发送至所述客户端。
可选地，在所述从客户端发送的后端服务器访问请求中，获取所述客户端在第一类网络的唯一路径指示信息的步骤之前，所述方法还包括：
接收并保存多个客户端向所述控制设备注册时提交的所述客户端所处的第一类网络的网络标识信息；
在所述从客户端发送的后端服务器访问请求中，获取所述客户端的唯一路径指示信息的步骤之后，所述方法还包括：
判断从所述后端服务器访问请求获取的第一类网络的网络标识信息，是否在保存的第一类网络的网络标识信息的范围内，若否，则返回拒绝访问信息至所述客户端。
为了解决上述问题，本申请还公开了一种网络的负载均衡控制方法，包括：
从各后端服务器获取所述后端服务器在第二类网络的唯一路径指示信息；
将预设流量调度规则和所述后端服务器的唯一路径指示信息发送至负载均衡设备，以供所述负载均衡设备根据所述后端服务器的唯一路径指示信息，将所述客户端的后端服务器访问请求，发送到按照所述预设流量调度规则选择出的至少一个后端服务器，以及按照所述客户端在第一类网络的唯一路径指示信息，将所述后端服务器返回的请求响应信息返回至所述客户端，其中，所述唯一路径指示信息在客户端所处的第一类网络以及各后端服务器所处第二类网络中唯一存在，所述第一类网络和所述第二类网络中至少一个为虚拟私有网络VPC。
可选地，所述唯一路径指示信息由所在虚拟私有网络VPC的网络标识信息以及在所述虚拟私有网络VPC中的地址标识信息生成。
可选地，还包括：
指示所述负载均衡设备将所述负载均衡设备的唯一路径指示信息发送至所述后端服务器，以供所述后端服务器按照所述负载均衡设备的唯一路径指示信息，返回请求响应信息至所述负载均衡设备。
可选地，还包括：
接收所述客户端在注册时提交的所述客户端所在的第一类网络的网络标识信息；
将所述第一类网络的网络标识信息发送至所述负载均衡设备，以供所述负载均衡设备保存并在接收到所述客户端的后端服务器访问请求时，判断从所述后端服务器访问请求获取的第一类网络的网络标识信息，是否在保存的第一类网络的网络标识信息的范围 内，若否，则返回拒绝访问信息至所述客户端。
为了解决上述问题，本申请还公开了一种网络交互方法，包括：
根据后端服务器在第二类网络的唯一路径指示信息，将客户端对后端服务器的访问请求，发送到按照所述预设流量调度规则选择出的至少一个后端服务器，所述第二类网络为虚拟私有网络VPC；
和/或，按照所述客户端在第一类网络的唯一路径指示信息，将后端服务器针对客户端的访问请求返回的请求响应信息返回至所述客户端，所述第一类网络为虚拟私有网络VPC；
其中，所述唯一路径指示信息在所述客户端所处的第一类网络以及各后端服务器所处第二类网络中唯一存在。
为了解决上述问题，本申请还公开了一种网络的负载均衡装置，包括：
预设流量调度规则接收模块，用于接收控制设备发送的预设流量调度规则，以及后端服务器在第二类网络的唯一路径指示信息；
信息获取模块，用于从客户端发送的后端服务器访问请求中，获取所述客户端在第一类网络的唯一路径指示信息；
后端服务器访问请求发送模块，用于根据所述后端服务器的唯一路径指示信息，将所述后端服务器访问请求，发送到按照所述预设流量调度规则选择出的至少一个后端服务器；
请求响应信息返回模块，用于接收所述后端服务器返回的请求响应信息，并按照所述客户端的唯一路径指示信息，将所述请求响应信息返回至所述客户端，其中，所述唯一路径指示信息在客户端所处的第一类网络以及各后端服务器所处第二类网络中唯一存在，所述第一类网络和所述第二类网络中至少一个为虚拟私有网络VPC。
可选地，所述唯一路径指示信息由所在虚拟私有网络VPC的网络标识信息以及在所述虚拟私有网络VPC中的地址标识信息生成。
可选地，还包括：
后端服务器访问模块，用于按照多个后端应用服务器的唯一路径指示信息，相应访问多个后端服务器。
运行状态检查模块，用于对访问的后端服务器进行运行状态检查，针对状态异常的后端服务器，在对应的唯一路径指示信息上标记异常标识；所述异常标识用于指示暂停 发送所述后端服务器访问请求至后端服务器。
可选地，还包括：
网络类型识别模块，用于识别所述客户端所处的第一类网络的网络类型。
可选地，所述信息获取模块包括：
后端服务器访问请求解封子模块，用于针对所述第一类网络的网络类型，从所述后端服务器访问请求中解封出所述第一类网络的网络标识信息和所述客户端的地址标识信息，并生成所述客户端的唯一路径指示信息。
可选地，所述请求响应信息返回模块包括：
请求响应信息封装子模块，用于针对所述第一类网络的网络类型，封装所述请求响应信息并发送至所述客户端。
可选地，还包括：
网络标识信息接收模块，用于接收并保存多个客户端向所述控制设备注册时提交的所述客户端所处的第一类网络的网络标识信息；
所述装置还包括：
网络标识信息判断模块，用于判断从所述后端服务器访问请求获取的第一类网络的网络标识信息，是否在保存的第一类网络的网络标识信息的范围内，若否，则返回拒绝访问信息至所述客户端。
为了解决上述问题，本申请还公开了一种网络的负载均衡控制装置，包括：
后端服务器唯一路径指示信息获取模块，用于从各后端服务器获取所述后端服务器在第二类网络的唯一路径指示信息；
预设流量调度规则发送模块，用于将预设流量调度规则和所述后端服务器的唯一路径指示信息发送至负载均衡设备，以供所述负载均衡设备根据所述后端服务器的唯一路径指示信息，将所述客户端的后端服务器访问请求，发送到按照所述预设流量调度规则选择出的至少一个后端服务器，以及按照所述客户端在第一类网络的唯一路径指示信息，将所述后端服务器返回的请求响应信息返回至所述客户端，其中，所述唯一路径指示信息在客户端所处的第一类网络以及各后端服务器所处第二类网络中唯一存在，所述第一类网络和所述第二类网络中至少一个为虚拟私有网络VPC。
可选地，所述唯一路径指示信息由所在虚拟私有网络VPC的网络标识信息以及在所述虚拟私有网络VPC中的地址标识信息生成。
可选地，还包括：
发送指示模块，用于指示所述负载均衡设备将所述负载均衡设备的唯一路径指示信息发送至所述后端服务器，以供所述后端服务器按照所述负载均衡设备的唯一路径指示信息，返回请求响应信息至所述负载均衡设备。
可选地，还包括：
网络标识信息接收模块，用于接收所述客户端在注册时提交的所述客户端所在的第一类网络的网络标识信息；
网络标识信息发送模块，用于将所述第一类网络的网络标识信息发送至所述负载均衡设备，以供所述负载均衡设备保存并在接收到所述客户端的后端服务器访问请求时，判断从所述后端服务器访问请求获取的第一类网络的网络标识信息，是否在保存的第一类网络的网络标识信息的范围内，若否，则返回拒绝访问信息至所述客户端。
为了解决上述问题，本申请还公开了一种网络交互装置，包括：
访问请求发送模块，用于根据后端服务器在第二类网络的唯一路径指示信息，将客户端对后端服务器的访问请求，发送到按照所述预设流量调度规则选择出的至少一个后端服务器，所述第二类网络为虚拟私有网络VPC；
和/或，请求响应信息返回模块，用于按照所述客户端在第一类网络的唯一路径指示信息，将后端服务器针对客户端的访问请求返回的请求响应信息返回至所述客户端，所述第一类网络为虚拟私有网络VPC；
其中，所述唯一路径指示信息在所述客户端所处的第一类网络以及各后端服务器所处第二类网络中唯一存在。
根据本申请实施例，负载均衡器通过利用控制设备下发的后端服务器的唯一路径指示信息，将访问请求发送至后端服务器，负载均衡器通过利用客户端发送的后端服务器访问请求获取客户端的唯一路径指示信息，将后端服务器返回请求响应信息转发至客户端。由于客户端和后端服务器的唯一路径指示信息在客户端所处的第一类网络以及各后端服务器所处的第二类网络中唯一存在，因此，在第一类网络和第二类网络中至少一个为虚拟私有网络VPC时，可以不需要网关对客户端和后端服务器的地址转换处理，从而避免了网关进行地址转换处理造成的访问时延，提升了客户端对后端服务器的访问效率和后端服务器的请求响应信息的返回效率，同时也节省了网关的处理资源。而且，因为无需对客户端和后端服务器的地址进行转换处理，节省了客户端和后端服务器对非VPC的IP地址的消耗。
另外,本申请实施例不需要经过网关进行转换处理，负载均衡器可以获取到客户端 真实的网络地址,从而可以精确地对客户端进行访问控制。
附图说明
图1是本申请的一种网络的负载均衡方法实施例1的步骤流程图；
图2是本申请的一种网络的负载均衡方法实施例2的步骤流程图；
图3是本申请的一种网络的负载均衡控制方法实施例的步骤流程图；
图4是本申请的一种网络交互方法实施例的步骤流程图；
图5是本申请的一种网络的负载均衡装置实施例1的结构框图；
图6是本申请的一种网络的负载均衡装置实施例2的结构框图；
图7是本申请的一种网络的负载均衡控制装置实施例的结构框图；
图8是本申请的一种网络交互装置实施例的结构框图；
图9是目前的一种负载均衡器的工作原理示意图；
图10是目前的一种利用网关进行负载均衡的工作原理示意图；
图11是本申请的一种负载均衡方法的应用场景一的示意图；
图12是本申请的一种负载均衡方法的应用场景二的示意图；
图13是本申请的一种负载均衡方法的应用场景三的示意图；
图14是本申请实施例的负载均衡处理流程图；
图15是本申请实施例的负载均衡系统结构图；
图16是本申请实施例的利用VSOCK模块辅助健康检查的流程示意图。
具体实施方式
为使本申请的上述目的、特征和优点能够更加明显易懂，下面结合附图和具体实施方式对本申请作进一步详细的说明。
参照图1，示出了本申请的一种网络的负载均衡方法实施例1的步骤流程图，具体可以包括如下步骤：
步骤101，接收控制设备发送的预设流量调度规则，以及后端服务器在第二类网络的唯一路径指示信息。
需要说明的是，网络可以有多种类型，如常见的IP网络的广域网和虚拟私有网络VPC。IP网络是利用IP(Internet Protocol)通讯协议互连多个计算机终端、客户端、服 务端的网络，可以理解为一个公共网络。其中，每个在IP网络中的终端都具有专有的IP地址，基于IP地址识别和区分不同的终端，以便于信息的准确传递。相对于公共的IP网络，虚拟私有网络VPC使用加密协议、隧道协议和其他安全程序，在公共的IP网络中形成出一个私有和独立的虚拟网络环境，VPC用户可以在虚拟私有网络VPC中自定义其中的各个终端的IP地址范围。
本申请实施例中，上述的第二类网络可以为广域网，也可以为虚拟私有网络VPC。即后端服务器可能处于广域网中，也可能处于虚拟私有网络VPC中。
上述的后端服务器的唯一路径指示信息可以唯一对应于某一后端服务器，按照唯一路径指示信息可以与其对应的后端服务器进行通讯。
在具体的实现中，可以由控制设备可以向负载均衡器发送预设流量调度规则和多个后端服务器的唯一路径指示信息。负载均衡器接收预设流量调度规则和后端服务器的唯一路径指示信息，以便于后续的流量调度处理。此外，控制设备也可以向客户端发送负载均衡器的唯一路径指示信息。
流量调度规则可以有多种，例如WRR(Weighted Round Robin，加权循环调度算法)、RR(Round-Robin，轮询调度算法)、WLC(Weighted Least-Connection Scheduling，加权最小连接调度算法)等，本领域技术人员可以根据需要采用各种流量调度规则，本申请实施例对此不作限制。
步骤102，从客户端发送的后端服务器访问请求中，获取所述客户端在第一类网络的唯一路径指示信息。
本申请实施例中，上述的第一类网络可以为广域网，也可以为虚拟私有网络VPC。即客户端可能处于广域网中，也可能处于虚拟私有网络VPC中。上述的客户端的唯一路径指示信息可以唯一对应于某一客户端，按照唯一路径指示信息可以与其对应的客户端进行通讯。
在具体的实现中，客户端可以通过向后端服务器发送后端服务器访问请求，以获取相应的服务。在将后端服务器访问请求发送至实际处理的后端服务器之前，可以由负载均衡器接收该访问请求，以便进一步将该访问请求调度至适合的后端服务器。从客户端发送的后端服务器访问请求中，可以获取客户端的唯一路径指示信息，并记录学习该唯一路径指示信息，用于在将请求响应信息返回至客户端时指示客户端的地址。
需要说明的是，所述步骤102也可以在所述步骤101之前执行。即，可以先从后端服务器访问请求中获取客户端的唯一路径指示信息，再接收预设流量调度规则以及多个 后端服务器的唯一路径指示信息。在实际的应用中，当负载均衡器接收客户端发送的后端服务器访问请求时，表明已经与客户端初始建立连接，此时可以将客户端的唯一路径指示信息记录并学习，以便在接收到后端服务器相应返回的请求响应信息后，使用该唯一路径指示信息，将请求响应信息原路返回至客户端。
步骤103，根据所述后端服务器的唯一路径指示信息，将所述后端服务器访问请求，发送到按照所述预设流量调度规则选择出的至少一个后端服务器。
可以利用预设流量调度规则计算各个后端服务器的负载情况，并相应选择出可供调度的后端服务器，根据选择出的后端服务器的唯一路径指示信息，相应地将后端服务器访问请求转发至该后端服务器，由后端服务器处理并响应来自客户端的访问请求，并相应返回请求响应信息至负载均衡器。
步骤104，接收所述后端服务器返回的请求响应信息，并按照所述客户端的唯一路径指示信息，将所述请求响应信息返回至所述客户端，其中，所述唯一路径指示信息在客户端所处的第一类网络以及各后端服务器所处第二类网络中唯一存在，所述第一类网络和所述第二类网络中至少一个为虚拟私有网络VPC。
当接收到后端服务器响应于访问请求的请求响应信息，可以将该请求响应信息按照此前记录的客户端的唯一路径指示信息，相应返回至客户端。
由于唯一路径指示信息在第一类网络以及第二类网络中唯一存在，在步骤103中，根据后端服务器的唯一路径指示信息的指示，可以将请求响应信息发送到唯一对应的后端服务器，在步骤104中，可以根据客户端的唯一路径指示信息的指示，可以将请求响应信息发送到唯一对应的客户端。
因此，在第一类网络和第二类网络中至少一个为虚拟私有网络VPC时，可以不需要网关对客户端和后端服务器的地址转换处理，从而避免了网关进行地址转换处理造成的访问时延，提升了客户端对后端服务器的访问效率和后端服务器的请求响应信息的返回效率，同时也节省了网关的处理资源。而且，因为无需对客户端和后端服务器的地址进行转换处理，节省了客户端和后端服务器对非VPC的IP地址的消耗。
另外,本申请实施例不需要经过网关进行转换处理，负载均衡器可以获取到客户端真实的网络地址,从而可以精确地对客户端进行访问控制。
本申请实施例可以适用于客户端所处的第一类网络和后端服务器所处的第二类网络中，至少一个网络为虚拟私有网络VPC的应用场景，具体而言，可以有如下几种情况：
当客户端所处的第一类网络为广域网时，若调度的后端服务器仅有一个，该后端服 务器所处的第二类网络为虚拟私有网络VPC。若调度的后端服务器有多个，则多个后端服务器可以是全部处于虚拟私有网络VPC，或是至少一个后端服务器处于虚拟私有网络VPC而其余后端服务器处于广域网。针对多个后端服务器处于虚拟私有网络VPC的情况，可以是均处于相同的虚拟私有网络VPC，或是全部处于不同的虚拟私有网络VPC，或是部分处于相同的虚拟私有网络VPC。
当客户端所处的第一类网络为虚拟私有网络VPC时，若调度的后端服务器仅有一个，该后端服务器所处的第二类网络为虚拟私有网络VPC或广域网。若调度的后端服务器有多个，则多个后端服务器可以是全部处于虚拟私有网络VPC，或是全部处于广域网，或是部分处于广域网，部分处于虚拟私有网络VPC。针对多个后端服务器处于虚拟私有网络VPC的情况，可以是均处于相同的虚拟私有网络VPC，或是全部处于不同的虚拟私有网络VPC，或是部分处于相同的虚拟私有网络VPC。
从上述可见，本申请实施例所适用的应用场景中，第一类网络为虚拟私有网络VPC时，第二类网络可以为广域网，也可以为虚拟私有网络VPC，即第一类网络与第二类网络可以为同构也可以为异构；当第一类网络为广域网时，第二类网络可以为虚拟私有网络VPC，即第一类网络与第二类网络为异构。
作为本申请实施例的优选示例，所述唯一路径指示信息可以由所在虚拟私有网络VPC的网络标识信息以及在所述虚拟私有网络VPC中的地址标识信息生成。
具体的实现中，可以从后端服务器访问请求中获取客户端所处的第一类网络的网络标识信息，以及客户端在所处的第一类网络中的地址标识信息，相应生成客户端的唯一路径指示信息。
实际应用中，针对基于VXLAN构建的虚拟私有网络VPC中的客户端，其发送的访问请求可以为封装了的VXLAN报文，在接收到VXLAN报文后，可以对该VXLAN报文进行解封处理，从中获取客户端所在的虚拟私有网络VPC的网络标识信息VNI，以及客户端在该虚拟私有网络VPC中的作为VTEP目的地地址的IP地址信息，以此生成客户端的唯一路径指示信息。
需要说明的是，VXLAN是一种常用的构建虚拟私有网络VPC的技术，其使用MAC in UDP的方法，通过VXLAN报文访问服务器，并利用VTEP(VXLAN Tunnel End Point，VXLAN隧道终端节点)封装和解封VXLAN报文。VXLAN报文中包含有VNI(VXLAN Network Identifier，VXLAN网络标识)信息，该虚拟私有网络VPC中的作为VTEP目的地址的IP地址信息和报文内层信息。VNI信息为客户端所在的虚拟私有网络VPC的 网络标识信息，报文内层信息包含有客户端在所在的虚拟私有网络VPC中的IP地址，以及端口信息。因此，在发送的后端服务器访问请求中，可以包含有客户端所在的网络的网络标识信息，以及在第一类网络中的地址标识信息，负载均衡器可以获取该网络标识信息和地址标识信息，并生成一个客户端的唯一路径指示信息。例如，利用VXLAN报文生成的后端服务器访问请求中，包含有客户端所在的虚拟私有网络VPC的网络标识信息VNI79，以及在该虚拟私有网络VPC的地址标识信息192.168.0.1，可以相应生成客户端的唯一路径指示信息VNI79/192.168.0.1。
需要进一步说明的是，除了VXLAN构建虚拟私有网络VPC，还可以将本申请实施例的技术方案，应用于基于GRE(Generic Routing Encapsulation，通用路由封装协议)构建的虚拟私有网络VPC。GRE采用了Tunnel(隧道)技术，可以对某些网络层协议的数据报进行封装，使这些被封装的数据报能够在IPv4网络中传输。
针对基于VXLAN构建的虚拟私有网络VPC中的后端服务器，可以将包含网络标识信息VNI和地址信息的VXLAN报文发送给控制设备，由控制设备生成后端服务器的唯一路径指示信息并下发给负载均衡器，负载均衡器根据后端服务器的唯一路径指示信息并发送给后端服务器。或者，后端服务器根据自身的网络标识信息VNI和地址信息生成唯一路径指示信息，封装在VXLAN报文中经由控制设备下发给负载均衡器。
参照图2，示出了本申请的一种网络的负载均衡方法实施例2的步骤流程图，具体可以包括如下步骤：
步骤201，接收并保存多个客户端向所述控制设备注册时提交的所述客户端所处的第一类网络的网络标识信息。
在实际的应用中，客户端可以向控制设备进行注册，在注册时可以提交客户端所在的第一类网络的网络标识信息。控制设备可以将注册时接收到的第一类网络的网络标识信息发送给负载均衡器。
步骤202，接收控制设备发送的预设流量调度规则，以及后端服务器在第二类网络的唯一路径指示信息，其中，所述唯一路径指示信息在所述客户端所处的第一类网络以及各后端服务器所处第二类网络中唯一存在，所述第一类网络和所述第二类网络中至少一个为虚拟私有网络VPC。
步骤203，按照多个后端应用服务器的唯一路径指示信息，相应访问多个后端服务器。
步骤204，对访问的后端服务器进行运行状态检查，针对状态异常的后端服务器，在对应的唯一路径指示信息上标记异常标识；所述异常标识用于指示暂停发送所述后端服务器访问请求至后端服务器。
需要说明的是，负载均衡器通常在进行流量调度处理之前，先对后端服务器进行运行状态检查，对于运行状态异常的服务器，则不向其调度流量。运行状态异常可以有多种，例如服务器响应慢、服务器上的应用无法正常工作、服务器上的应用程序关联出错等。
在本申请之前的现有技术中，针对于虚拟私有网络VPC内的后端服务器进行检查时，由于后端服务器的地址仅仅在其域内唯一，负载均衡器无法直接访问虚拟私有网络VPC内的后端服务器，因此也需要通过网关与后端服务器进行信息交互。
在具体的实现中，负载均衡器可以在进行流量调度处理之前，按照后端应用服务器的唯一路径指示信息，相应访问各个后端服务器并进行运行状态的检查。对于状态异常的服务器，可以在其对应的唯一路径指示信息上标记一个异常标识，在进行流量调度时，对于携带有异常标识的服务器，则暂停向其发送访问请求，以保证由运作正常的服务器承担该访问即提供服务。由此，负载均衡器通过利用控制设备下发的后端服务器的唯一路径指示信息访问后端服务器，由于后端服务器的唯一路径指示信息在客户端所处的第一类网络以及各后端服务器所处的第二类网络中唯一存在，因此，无需网关的参与即可实现对后端服务器运行状态的检查处理。
在实际的应用中，可以在负载均衡器中设置一个运行状态检查辅助模块，该模块可以设置在系统底层，当负载均衡器通过运行状态检查程序创建与后端服务器的连接时，通过系统调用保存有的后端服务器的唯一路径指示信息，模块根据后端服务器的唯一路径指示信息封装一个VXLAN报文，并发送至相应的后端服务器。
步骤205，识别客户端所处的第一类网络的网络类型。
因为在实际的应用中，客户端可能处于基于VXLAN构建的虚拟私有网络VPC或者传统的广域网，不同的网络采用不同的网络协议，负载均衡器可以根据不同的网络协议的特点，采用适于该类型网络的数据包结构。
步骤206，针对所述第一类网络的网络类型，从所述后端服务器访问请求中解封出所述第一类网络的网络标识信息和所述客户端的地址标识信息，并生成所述客户端的唯一路径指示信息。
针对于处于第一类网络中的客户端发起的后端服务器访问请求，可以根据第一类网 络的网络类型的特点，从访问请求中解封出第一类网络的网络标识信息和客户端的地址标识信息，并相应生成客户端的唯一路径指示信息。
在实际的应用中，当负载均衡器接收客户端发送的后端服务器访问请求时，表明已经与客户端初始建立连接，此时可以将客户端的唯一路径指示信息记录并学习，后续处理中可以使用该唯一路径指示信息，将请求响应信息原路返回至客户端。
步骤207，判断从所述后端服务器访问请求获取的第一类网络的网络标识信息，是否在保存的第一类网络的网络标识信息的范围内，若否，则返回拒绝访问信息至所述客户端；若是，则执行步骤208。
在具体的实现中，还可以在预先保存有的网络标识信息中，查找是否存在有对应的从访问请求中解封的网络标识信息。若查找不到有该网络标识信息，表明该客户端或该客户端所在的网络还未在控制设备上注册，可以相应返回拒绝访问信息至客户端。若查找有该网络标识信息，则可以继续执行下一步的流量调度处理。
步骤208，根据所述后端服务器的唯一路径指示信息，将所述后端服务器访问请求，发送到按照所述预设流量调度规则选择出的至少一个后端服务器。
可以利用预设流量调度规则计算各个后端服务器的负载情况，并相应选择出可供调度的后端服务器，根据选择出的后端服务器的唯一路径指示信息，相应地将后端服务器访问请求转发至该后端服务器，由后端服务器处理并响应来自客户端的访问请求，并相应返回请求响应信息至负载均衡器。
步骤209，接收所述后端服务器返回的请求响应信息，并按照所述客户端的唯一路径指示信息，针对所述第一类网络的网络类型，封装所述请求响应信息并发送至所述客户端。
接收到后端服务器响应于访问请求的请求响应信息，可以将该请求响应信息根据之前确定的第一类网络的网络类型进行封装处理，并按照记录的客户端的唯一路径指示信息，相应返回至客户端。
实际应用中，为了使得后端服务器可以准确地返回请求响应信息至负载均衡器，可以在后端服务器部署一个VTEP自动学习模块，用于学习记录负载均衡器的VTEP地址信息。当然，后端服务器也可以从控制设备获取一个预设的返回请求响应信息规则，以便于准确地返回请求响应信息至负载均衡器。
根据本申请实施例，负载均衡器通过利用控制设备下发的后端服务器的唯一路径指示信息，将访问请求发送至后端服务器，负载均衡器通过利用客户端发送的后端服务器 访问请求获取客户端的唯一路径指示信息，将后端服务器返回请求响应信息转发至客户端。由于客户端和后端服务器的唯一路径指示信息在客户端所处的第一类网络以及各后端服务器所处的第二类网络中唯一存在，因此，在第一类网络和第二类网络中至少一个为虚拟私有网络VPC时，可以不需要网关对客户端和后端服务器的地址转换处理，从而避免了网关进行地址转换处理造成的访问时延，提升了客户端对后端服务器的访问效率和后端服务器的请求响应信息的返回效率，同时也节省了网关的处理资源。而且，因为无需对客户端和后端服务器的地址进行转换处理，节省了客户端和后端服务器对非VPC的IP地址的消耗。
另外，本申请实施例不需要经过网关进行转换处理，负载均衡器可以获取到客户端真实的网络地址,从而可以精确地对客户端进行访问控制。
最后，根据本申请实施例，负载均衡器通过利用控制设备下发的后端服务器的唯一路径指示信息访问后端服务器，由于后端服务器的唯一路径指示信息在客户端所处的第一类网络以及各后端服务器所处的第二类网络中唯一存在，因此，可以无须经由网关对后端服务器的VPC地址进行转换，而利用后端服务器的唯一路径指示信息对后端服务器进行运行状态检查，避免了网关进行地址转换处理造成的时延，提升了运行状态检查的效率。
参照图3，示出了本申请的一种网络的负载均衡控制方法实施例的步骤流程图，具体可以包括如下步骤：
步骤301，从各后端服务器获取所述后端服务器在第二类网络的唯一路径指示信息。
控制设备可以从各个后端服务器获取后端服务器的唯一路径指示信息，以用于指示信息准确地发送至后端服务器。
作为本申请实施例的优选示例，所述唯一路径指示信息可以由所在虚拟私有网络VPC的网络标识信息以及在所述虚拟私有网络VPC中的地址标识信息生成。具体地，控制设备可以从多个后端服务器获取后端服务器分别所处的各个第二类网络的网络标识信息，以及后端服务器在所处的第二类网络中的地址标识信息，相应生成各个后端服务器的唯一路径指示信息。
步骤302，将预设流量调度规则和所述后端服务器的唯一路径指示信息发送至负载均衡设备，以供所述负载均衡设备根据所述后端服务器的唯一路径指示信息，将所述客户端的后端服务器访问请求，发送到按照所述预设流量调度规则选择出的至少一个后端 服务器，以及按照所述客户端在第一类网络的唯一路径指示信息，将所述后端服务器返回的请求响应信息返回至所述客户端，其中，所述唯一路径指示信息在客户端所处的第一类网络以及各后端服务器所处第二类网络中唯一存在，所述第一类网络和所述第二类网络中至少一个为虚拟私有网络VPC。
控制设备将预设流量调度规则和多个后端服务器的唯一路径指示信息，发送给负载均衡设备。负载均衡设备在接收到客户端发起后端服务器访问请求时，可以从访问请求中获取到客户端所处的第一类网络的唯一路径指示信息，并利用预设流量调度规则计算各个后端服务器的负载情况，相应选择出可供调度的后端服务器，根据选择出的后端服务器的唯一路径指示信息，相应地将后端服务器访问请求转发至该后端服务器，由后端服务器处理并响应来自客户端的访问请求，并相应返回请求响应信息至负载均衡设备。
负载均衡设备接收到后端服务器响应于访问请求的请求响应信息后，可以根据客户端的唯一路径指示信息，将请求响应信息返回至客户端。
需要说明的是，负载均衡设备可以为负载均衡器，也可以为任意的负责将客户端发送的访问请求调度至至少一个后端服务器的设备。
根据本申请实施例，负载均衡器通过利用控制设备下发的后端服务器的唯一路径指示信息，将访问请求发送至后端服务器，由于后端服务器的唯一路径指示信息在客户端所处的第一类网络以及各后端服务器所处的第二类网络中唯一存在，因此，在第一类网络和第二类网络中至少一个为虚拟私有网络VPC时，可以不需要网关对后端服务器的地址转换处理，从而避免了网关进行地址转换处理造成的访问时延，提升了客户端对后端服务器的访问效率，同时也节省了网关的处理资源。而且，因为无需对后端服务器的地址进行转换处理，节省了后端服务器对非VPC的IP地址的消耗。
另外，本申请实施例不需要经过网关进行转换处理，负载均衡器可以获取到客户端真实的网络地址,从而可以精确地对客户端进行访问控制。
作为本申请实施例的优选示例，所述方法可以还包括：指示所述负载均衡设备将所述负载均衡设备的唯一路径指示信息发送至所述后端服务器，以供所述后端服务器按照所述负载均衡设备的唯一路径指示信息，返回请求响应信息至所述负载均衡设备。
控制设备还可以指示负载均衡设备将其唯一路径指示信息发送给多个后端服务器，以便于后端服务器可以准确地向负载均衡设备返回请求响应信息。
作为本申请实施例的优选示例，所述方法可以还包括：接收所述客户端在注册时提交的所述客户端所在的第一类网络的网络标识信息；将所述第一类网络的网络标识信息 发送至所述负载均衡设备，以供所述负载均衡设备保存并在接收到所述客户端的后端服务器访问请求时，判断从所述后端服务器访问请求获取的第一类网络的网络标识信息，是否在保存的第一类网络的网络标识信息的范围内，若否，则返回拒绝访问信息至所述客户端。
客户端可以向控制设备进行注册，在注册时可以提交客户端所在的第一类网络的网络标识信息。控制设备可以将收集到的第一类网络的网络标识信息发送给负载均衡设备。
负载均衡设备可以将接收到的第一类网络的网络标识信息保存，在接收到客户端发起的后端服务器访问请求时，可以从访问请求中获取客户端所在的第一类网络的网络标识信息，在预先保存有的网络标识信息中，查找是否存在有该客户端所处的第一类网络的网络标识信息。若并查找不到有该网络标识信息，表明该客户端或该客户端所在的网络还未在控制设备上注册，可以相应返回拒绝访问信息至客户端。若查找有该网络标识信息，则可以继续执行下一步的流量调度处理。
参照图4，示出了本申请的一种网络交互方法实施例的步骤流程图，具体可以包括如下步骤：
步骤401，根据后端服务器在第二类网络的唯一路径指示信息，将客户端对所述后端服务器的访问请求，发送到按照所述预设流量调度规则选择出的至少一个后端服务器，所述第二类网络为虚拟私有网络VPC。
当后端服务器所处的第一类网络为虚拟私有网络VPC时，负载均衡器可以利用预设流量调度规则计算各个后端服务器的负载情况，并相应选择出可供调度的后端服务器，根据选择出的后端服务器的唯一路径指示信息，相应地将后端服务器访问请求转发至该后端服务器，由后端服务器处理并响应来自客户端的访问请求，并相应返回请求响应信息至负载均衡器。
步骤402，按照所述客户端在第一类网络的唯一路径指示信息，将后端服务器针对客户端的访问请求返回的请求响应信息返回至所述客户端，所述第一类网络为虚拟私有网络VPC。
其中，所述唯一路径指示信息在所述客户端所处的第一类网络以及各后端服务器所处第二类网络中唯一存在。
负载均衡器接收到后端服务器响应于访问请求的请求响应信息，可以将该请求响应信息相应返回至客户端。当客户端所处的第二类网络为虚拟私有网络VPC时，可以按照 客户端的唯一路径指示信息，将该请求响应信息相应返回客户端。
需要说明的是，实际应用中可以执行上述的一个或多个步骤，例如可以仅执行步骤401，也可以均执行步骤401和步骤402。
根据本申请实施例，负载均衡器通过利用控制设备下发的后端服务器的唯一路径指示信息，将访问请求发送至后端服务器，负载均衡器通过利用客户端发送的访问请求获取客户端的唯一路径指示信息，将后端服务器返回请求响应信息转发至客户端。由于客户端和后端服务器的唯一路径指示信息在客户端所处的第一类网络以及各后端服务器所处的第二类网络中唯一存在，因此，在第一类网络和第二类网络中至少一个为虚拟私有网络VPC时，可以不需要网关对客户端和后端服务器的地址转换处理，从而避免了网关进行地址转换处理造成的访问时延，提升了客户端对后端服务器的访问效率和后端服务器的请求响应信息的返回效率，同时也节省了网关的处理资源。而且，因为无需对客户端和后端服务器的地址进行转换处理，节省了客户端和后端服务器对非VPC的IP地址的消耗。
另外，本申请实施例不需要经过网关进行转换处理，负载均衡器可以获取到客户端真实的网络地址,从而可以精确地对客户端进行访问控制。
为使本领域技术人员更好地理解本申请实施例，以下通过具体的示例对本申请的负载均衡以及控制方法进行说明。
图9示出了目前的负载均衡器的工作原理示意图。从图中可见，客户端Client访问某个服务器以获取服务，通过域名解析后会对应地访问负载均衡器LB的VIP：VPORT端口。访问到达负载均衡器后，会根据一定的流量调度规则，将该访问分配到后端的实际提供服务的多个后端服务器RS1、RS2、RS3或RS4。后端服务器RS1、RS2、RS3或RS4分别通过各自的RIP1：RPORT1、RIP2：RPORT2、RIP3：RPORT3和RIP4：RPORT4端口收到来自客户端的访问，相应处理后由原路返回处理结果到负载均衡器。负载均衡器将该处理结果，通过访问客户端的CIP：CPORT端口返回给客户端。负载均衡器调度根据TCP/UDP调度为四层负载均衡(L4LB)，根据应用层(http、ftp等)为七层负载均衡(L7LB)。此外，负载均衡器还具有对后端服务器健康检查的功能，分发流量时忽略健康检查失败的后端服务器。
图10示出了目前的利用网关进行负载均衡的工作原理示意图。从图中可见，客户端处于网络标识为VNI79的VXLAN类型的虚拟私有网络VPC中，在该虚拟私有网络VPC中其IP地址为192.168.0.1，该IP地址仅在VNI79的虚拟私有网络VPC中唯一，需要经 过网关VXLAN Gateway将VPC地址转换成非VPC地址，从而转换成在整个网络中具有唯一性的IP地址10.18.0.1，才可以经由IP地址为10.1.2.3的负载均衡器LB的调度，以访问同处于VNI79的虚拟私有网络VPC中的后端服务器RS1和RS2，和处于VNI1234的虚拟私有网络VPC中的后端服务器RS1和RS2。
网络标识为VNI79的虚拟私有网络VPC中的后端服务器RS1和RS2在其所在网络中具有唯一的地址标识信息192.168.1.11和192.168.2.12，VNI1234的虚拟私有网络VPC中的后端服务器RS1和RS2在其所在网络中具有唯一的地址标识信息172.16.100.11和172.16.200.12。然而各个后端服务器的地址标识信息仅在其所在的虚拟私有网络VPC中唯一，也需要经过网关分别转换成IP地址10.16.1.11、10.16.2.12、10.16.3.13和10.16.4.14，才能够与负载均衡器进行信息交互。
为了便于本领域技术人员理解本申请的负载均衡方法在不同应用场景中的实施方式，以下将结合图11、图12和图13进行说明。
需要说明的是，为了表述简便而将图例简化成2至4个后端服务器的应用场景，实际应用中可适用于任意数量的后端服务器。其中，图11和图12分别给出了客户端处于虚拟私有网络VPC的情况下，多个后端服务器均处于虚拟私有网络VPC以及多个后端服务器均处于广域网的应用场景示意图。实际应用中，还可以包括多个后端服务器中部分处于广域网，部分处于虚拟私有网络VPC的情况。
图13给出了客户端处于广域网的情况下，多个后端服务器均处于虚拟私有网络VPC的应用场景示意图。实际应用中，还可以包括至少一个后端服务器处于虚拟私有网络VPC而其余后端服务器处于广域网的情况。
本领域技术人员可以根据实际需要将本申请的负载均衡方法应用于多种适用的应用场景中。
图11示出了本申请的一种负载均衡方法的应用场景一的示意图。从图中可见，客户端Client处于网络标识为VNI79的虚拟私有网络VPC中，在VNI79的虚拟私有网络VPC中的地址为192.168.0.1。客户端可以在向控制设备注册时获取到负载均衡器LB的唯一路径指示信息VNI79/192.168.10.1，并根据该唯一路径指示信息访问负载均衡器LB，以经负载均衡器向后端服务器发起访问请求。负载均衡器利用客户端所在虚拟私有网络VPC的网络标识VNI79和在该虚拟私有网络VPC中的IP地址192.168.0.1，生成该客户端的唯一路径指示信息VNI79/192.168.0.1并记录学习。
在本应用场景中除了具有VNI79的虚拟私有网络VPC，还具有VNI1234的虚拟私 有网络VPC。在两个虚拟私有网络VPC下分别部署有2个后端服务器RS1和RS2。后端服务器在其所属的虚拟私有网络VPC中具有唯一的地址标识信息192.168.1.11、192.168.2.12、172.16.100.11和172.16.200.12。
负载均衡器可以从控制设备获取多个后端服务器的唯一路径指示信息。如图中所见，负载均衡器可以获取到网络标识为VNI79的虚拟私有网络VPC中的后端服务器RS1和RS2的唯一路径指示信息VNI79/192.168.1.11和VNI79/192.168.2.12，和VNI1234的虚拟私有网络VPC中的后端服务器RS1和RS2的唯一路径指示信息VNI1234/172.16.100.11和VNI1234/172.16.200.12。
利用后端服务器的唯一路径指示信息，可以将客户端发起的访问请求准确地调度至后端服务器。后端服务器返回响应信息时，也可以根据记录学习的客户端的唯一路径指示信息，将响应信息准确地返回至客户端。从而，不需要经过网关将客户端和后端服务器的VPC地址转换成非VPC地址，负载均衡器即可准确地将客户端的访问调度至后端服务器，还可以准确地将后端服务器的响应信息准确地返回至客户端。
实际应用中，除了VXLAN，客户端和后端服务器也可以处于基于GRE构建的虚拟私有网络VPC中，或者部分客户端和后端服务器处于基于VXLAN创建的的虚拟私有网络VPC中，部分处于基于GRE创建的虚拟私有网络VPC中。本领域技术人员可以将本申请实施例应用于多种方式构建的虚拟私有网络VPC中。
图12示出了本申请的一种负载均衡方法的应用场景二的示意图。从图中可见，客户端Client处于虚拟私有网络VPC中，而后端服务器RS1和RS2处于传统的广域网中。负载均衡器利用客户端所在虚拟私有网络VPC的网络标识VNI79和在该虚拟私有网络VPC中的IP地址192.168.0.1，生成客户端的唯一路径指示信息并记录学习。负载均衡服务器将客户端发起的访问请求调度至IP地址分别为100.12.1.11和100.12.1.12的后端服务器RS1和RS2，并将后端服务器的响应信息，根据记录学习的客户端的唯一路径指示信息，返回至客户端。从而，不需要经过网关将VPC地址转换成非VPC地址，负载均衡器即可准确地将客户端的访问调度至后端服务器并返回响应信息至客户端。
图13示出了本申请的一种负载均衡方法的应用场景三的示意图。从图中可见，客户端处于传统的广域网中，IP地址为10.18.0.1；而后端服务器RS1和RS2处于网络标识VNI79的虚拟私有网络VPC中，其在虚拟私有网络VPC中具有的IP地址分别为192.168.1.11和192.168.2.12。负载均衡器将客户端发起的访问请求调度至后端服务器时，可以根据后端服务器的网络标识VNI79以及其在虚拟私有网络VPC中的IP地址 192.168.1.11和192.168.2.12生成各自的唯一路径指示信息。根据各自的唯一路径指示信息，负载均衡器可以将访问请求准确地调度至后端服务器，而无须经过网关将后端服务器的VPC地址转换成非VPC地址。
图14示出了本申请实施例的负载均衡处理流程图。从图中可见，首先从客户端发起的访问请求中解封VXLAN报文，获取其中的VNI信息和报文内层信息。然后调度模块根据获取的VNI信息和包含有客户端IP地址的报文内层信息，以及预设的调度规则选取后端服务器。如果客户端初始建立连接成功，则通过VTEP自动学习模块学习并记录获取的VNI信息和报文内层信息。根据后端服务器的VNI信息和地址信息构造VXLAN报文，发送至相应的后端服务器。后端服务器接收到请求处理后，将响应信息返回至负载均衡器LB。
图15示出了本申请实施例的负载均衡系统结构图。从图中可见，该系统包括如下几个关键模块：
控制中心，用于下发调度规则给负载均衡器。如果是虚拟私有网络VPC内的后端服务器，则需要下发后端服务器的VNI信息和IP地址信息给负载均衡器。
VXLAN处理模块，用于在接收到客户端发送的访问请求时，根据VXLAN协议的特点识别收到的VXLAN报文并解封。在返回请求响应时，相应封装一个VXLAN报文。
VTEP自动学习模块，用于在客户端初始建立连接或VTEP发生变化时，学习客户端的地址信息并记录，供返回请求响应时直接使用。
调度模块，用于按早调度规则配置对后端服务器的负载均衡。
VSOCK模块，用于辅助对虚拟私有网络VPC内的后端服务器进行健康检查。
图16示出了利用VSOCK模块辅助健康检查的流程示意图。从图中可见，VSOCK模块工作于系统底层，健康检查程序在创建连接前先通过系统调用后端服务器的VNI信息和地址信息，后续VSOCK模块会根据调用的信息封装或解封VXLAN报文并发送至后端服务器，无需网关的参与即可完成与后端服务器的信息交互。
需要说明的是，对于方法实施例，为了简单描述，故将其都表述为一系列的动作组合，但是本领域技术人员应该知悉，本申请实施例并不受所描述的动作顺序的限制，因为依据本申请实施例，某些步骤可以采用其他顺序或者同时进行。其次，本领域技术人员也应该知悉，说明书中所描述的实施例均属于优选实施例，所涉及的动作并不一定是本申请实施例所必须的。
参照图5，示出了本申请的一种网络的负载均衡装置实施例1的结构框图，具体可以包括如下模块：
预设流量调度规则接收模块501，用于接收控制设备发送的预设流量调度规则，以及后端服务器在第二类网络的唯一路径指示信息。
信息获取模块502，用于从客户端发送的后端服务器访问请求中，获取所述客户端在第一类网络的唯一路径指示信息。
后端服务器访问请求发送模块503，用于根据所述后端服务器的唯一路径指示信息，将所述后端服务器访问请求，发送到按照所述预设流量调度规则选择出的至少一个后端服务器。
请求响应信息返回模块504，用于接收所述后端服务器返回的请求响应信息，并按照所述客户端的唯一路径指示信息，将所述请求响应信息返回至所述客户端，其中，所述唯一路径指示信息在客户端所处的第一类网络以及各后端服务器所处第二类网络中唯一存在，所述第一类网络和所述第二类网络中至少一个为虚拟私有网络VPC。
根据本申请实施例，负载均衡器通过利用控制设备下发的后端服务器的唯一路径指示信息，将访问请求发送至后端服务器，负载均衡器通过利用客户端发送的后端服务器访问请求获取客户端的唯一路径指示信息，将后端服务器返回请求响应信息转发至客户端。由于客户端和后端服务器的唯一路径指示信息在客户端所处的第一类网络以及各后端服务器所处的第二类网络中唯一存在，因此，在第一类网络和第二类网络中至少一个为虚拟私有网络VPC时，可以不需要网关对客户端和后端服务器的地址转换处理，从而避免了网关进行地址转换处理造成的访问时延，提升了客户端对后端服务器的访问效率和后端服务器的请求响应信息的返回效率，同时也节省了网关的处理资源。而且，因为无需对客户端和后端服务器的地址进行转换处理，节省了客户端和后端服务器对非VPC的IP地址的消耗。
另外，本申请实施例不需要经过网关进行转换处理，负载均衡器可以获取到客户端真实的网络地址,从而可以精确地对客户端进行访问控制。作为本申请实施例的优选示例，所述唯一路径指示信息由所在虚拟私有网络VPC的网络标识信息以及在所述虚拟私有网络VPC中的地址标识信息生成。
参照图6，示出了本申请的一种网络的负载均衡装置实施例2的结构框图，具体可 以包括如下模块：
网络标识信息接收模块601，用于接收并保存多个客户端向所述控制设备注册时提交的所述客户端所处的第一类网络的网络标识信息。
预设流量调度规则接收模块602，用于接收控制设备发送的预设流量调度规则，以及后端服务器在第二类网络的唯一路径指示信息。
后端服务器访问模块603，用于按照多个后端应用服务器的唯一路径指示信息，相应访问多个后端服务器。
运行状态检查模块604，用于对访问的后端服务器进行运行状态检查，针对状态异常的后端服务器，在对应的唯一路径指示信息上标记异常标识；所述异常标识用于指示暂停发送所述后端服务器访问请求至后端服务器。
网络类型识别模块605，用于识别客户端所处的第一类网络的网络类型。
信息获取模块606，用于从客户端发送的后端服务器访问请求中，获取所述客户端在第一类网络的唯一路径指示信息。
网络标识信息判断模块607，用于判断从所述后端服务器访问请求获取的第一类网络的网络标识信息，是否在保存的第一类网络的网络标识信息的范围内，若否，则返回拒绝访问信息至所述客户端。
后端服务器访问请求发送模块608，用于根据所述后端服务器的唯一路径指示信息，将所述后端服务器访问请求，发送到按照所述预设流量调度规则选择出的至少一个后端服务器。
请求响应信息返回模块609，用于接收所述后端服务器返回的请求响应信息，并按照所述客户端的唯一路径指示信息，将所述请求响应信息返回至所述客户端，其中，所述唯一路径指示信息在客户端所处的第一类网络以及各后端服务器所处第二类网络中唯一存在，所述第一类网络和所述第二类网络中至少一个为虚拟私有网络VPC。
根据本申请实施例，负载均衡器通过利用控制设备下发的后端服务器的唯一路径指示信息，将访问请求发送至后端服务器，负载均衡器通过利用客户端发送的后端服务器访问请求获取客户端的唯一路径指示信息，将后端服务器返回请求响应信息转发至客户端。由于客户端和后端服务器的唯一路径指示信息在客户端所处的第一类网络以及各后端服务器所处的第二类网络中唯一存在，因此，在第一类网络和第二类网络中至少一个为虚拟私有网络VPC时，可以不需要网关对客户端和后端服务器的地址转换处理，从而避免了网关进行地址转换处理造成的访问时延，提升了客户端对后端服务器的访问效率 和后端服务器的请求响应信息的返回效率，同时也节省了网关的处理资源。而且，因为无需对客户端和后端服务器的地址进行转换处理，节省了客户端和后端服务器对非VPC的IP地址的消耗。
另外，本申请实施例不需要经过网关进行转换处理，负载均衡器可以获取到客户端真实的网络地址,从而可以精确地对客户端进行访问控制。
最后，根据本申请实施例，负载均衡器通过利用控制设备下发的后端服务器的唯一路径指示信息访问后端服务器，由于后端服务器的唯一路径指示信息在客户端所处的第一类网络以及各后端服务器所处的第二类网络中唯一存在，因此，可以无须经由网关对后端服务器的VPC地址进行转换，而利用后端服务器的唯一路径指示信息对后端服务器进行运行状态检查，避免了网关进行地址转换处理造成的时延，提升了运行状态检查的效率。
作为本申请实施例的优选示例，所述信息获取模块606可以包括：
后端服务器访问请求解封子模块，用于针对所述第一类网络的网络类型，从所述后端服务器访问请求中解封出所述第一类网络的网络标识信息和所述客户端的地址标识信息，并生成所述客户端的唯一路径指示信息。
作为本申请实施例的优选示例，所述请求响应信息返回模块609可以包括以下子模块：
请求响应信息封装子模块，用于针对所述第一类网络的网络类型，封装所述请求响应信息并发送至所述客户端。
参照图7，示出了本申请的一种网络的负载均衡控制装置实施例的结构框图，具体可以包括如下模块：
后端服务器唯一路径指示信息获取模块701，用于从各后端服务器获取所述后端服务器在第二类网络的唯一路径指示信息。
预设流量调度规则发送模块702，用于将预设流量调度规则和所述后端服务器的唯一路径指示信息发送至负载均衡设备，以供所述负载均衡设备根据所述后端服务器的唯一路径指示信息，将所述客户端的后端服务器访问请求，发送到按照所述预设流量调度规则选择出的至少一个后端服务器，以及按照所述客户端在第一类网络的唯一路径指示信息，将所述后端服务器返回的请求响应信息返回至所述客户端，其中，所述唯一路径指示信息在客户端所处的第一类网络以及各后端服务器所处第二类网络中唯一存在，所 述第一类网络和所述第二类网络中至少一个为虚拟私有网络VPC。
根据本申请实施例，负载均衡器通过利用控制设备下发的后端服务器的唯一路径指示信息，将访问请求发送至后端服务器，由于后端服务器的唯一路径指示信息在客户端所处的第一类网络以及各后端服务器所处的第二类网络中唯一存在，因此，在第一类网络和第二类网络中至少一个为虚拟私有网络VPC时，可以不需要网关对后端服务器的地址转换处理，从而避免了网关进行地址转换处理造成的访问时延，提升了客户端对后端服务器的访问效率，同时也节省了网关的处理资源。而且，因为无需对后端服务器的地址进行转换处理，节省了后端服务器对非VPC的IP地址的消耗。
另外，本申请实施例不需要经过网关进行转换处理，负载均衡器可以获取到客户端真实的网络地址,从而可以精确地对客户端进行访问控制。
作为本申请实施例的优选示例，所述唯一路径指示信息由所在虚拟私有网络VPC的网络标识信息以及在所述虚拟私有网络VPC中的地址标识信息生成。
作为本申请实施例的优选示例，所述装置可以还包括以下模块：
发送指示模块，用于指示所述负载均衡设备将所述负载均衡设备的唯一路径指示信息发送至所述后端服务器，以供所述后端服务器按照所述负载均衡设备的唯一路径指示信息，返回请求响应信息至所述负载均衡设备。
作为本申请实施例的优选示例，所述装置可以还包括以下模块：
网络标识信息接收模块，用于接收所述客户端在注册时提交的所述客户端所在的第一类网络的网络标识信息。
网络标识信息发送模块，用于将所述第一类网络的网络标识信息发送至所述负载均衡设备，以供所述负载均衡设备保存并在接收到所述客户端的后端服务器访问请求时，判断从所述后端服务器访问请求获取的第一类网络的网络标识信息，是否在保存的第一类网络的网络标识信息的范围内，若否，则返回拒绝访问信息至所述客户端。
参照图8，示出了本申请的一种网络交互装置实施例的结构框图，具体可以包括如下模块：
访问请求发送模块801，用于根据后端服务器在第二类网络的唯一路径指示信息，将客户端对后端服务器的访问请求，发送到按照所述预设流量调度规则选择出的至少一个后端服务器，所述第二类网络为虚拟私有网络VPC；
和/或，请求响应信息返回模块802，用于按照所述客户端在第一类网络的唯一路径 指示信息，将后端服务器针对客户端的访问请求返回的请求响应信息返回至所述客户端，所述第一类网络为虚拟私有网络VPC；
其中，所述唯一路径指示信息在所述客户端所处的第一类网络以及各后端服务器所处第二类网络中唯一存在。
根据本申请实施例，负载均衡器通过利用控制设备下发的后端服务器的唯一路径指示信息，将访问请求发送至后端服务器，负载均衡器通过利用客户端发送的后端服务器访问请求获取客户端的唯一路径指示信息，将后端服务器返回请求响应信息转发至客户端。由于客户端和后端服务器的唯一路径指示信息在客户端所处的第一类网络以及各后端服务器所处的第二类网络中唯一存在，因此，在第一类网络和第二类网络中至少一个为虚拟私有网络VPC时，可以不需要网关对客户端和后端服务器的地址转换处理，从而避免了网关进行地址转换处理造成的访问时延，提升了客户端对后端服务器的访问效率和后端服务器的请求响应信息的返回效率，同时也节省了网关的处理资源。而且，因为无需对客户端和后端服务器的地址进行转换处理，节省了客户端和后端服务器对非VPC的IP地址的消耗。
另外，本申请实施例不需要经过网关进行转换处理，负载均衡器可以获取到客户端真实的网络地址,从而可以精确地对客户端进行访问控制。
对于装置实施例而言，由于其与方法实施例基本相似，所以描述的比较简单，相关之处参见方法实施例的部分说明即可。
本说明书中的各个实施例均采用递进的方式描述，每个实施例重点说明的都是与其他实施例的不同之处，各个实施例之间相同相似的部分互相参见即可。
本领域内的技术人员应明白，本申请实施例的实施例可提供为方法、装置、或计算机程序产品。因此，本申请实施例可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式。而且，本申请实施例可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器、CD-ROM、光学存储器等)上实施的计算机程序产品的形式。
在一个典型的配置中，所述计算机设备包括一个或多个处理器(CPU)、输入/输出接口、网络接口和内存。内存可能包括计算机可读介质中的非永久性存储器，随机存取存储器(RAM)和/或非易失性内存等形式，如只读存储器(ROM)或闪存(flash RAM)。内存是计算机可读介质的示例。计算机可读介质包括永久性和非永久性、可移动和非可移动 媒体可以由任何方法或技术来实现信息存储。信息可以是计算机可读指令、数据结构、程序的模块或其他数据。计算机的存储介质的例子包括，但不限于相变内存(PRAM)、静态随机存取存储器(SRAM)、动态随机存取存储器(DRAM)、其他类型的随机存取存储器(RAM)、只读存储器(ROM)、电可擦除可编程只读存储器(EEPROM)、快闪记忆体或其他内存技术、只读光盘只读存储器(CD-ROM)、数字多功能光盘(DVD)或其他光学存储、磁盒式磁带，磁带磁磁盘存储或其他磁性存储设备或任何其他非传输介质，可用于存储可以被计算设备访问的信息。按照本文中的界定，计算机可读介质不包括非持续性的电脑可读媒体(transitory media)，如调制的数据信号和载波。
本申请实施例是参照根据本申请实施例的方法、终端设备(系统)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理终端设备的处理器以产生一个机器，使得通过计算机或其他可编程数据处理终端设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理终端设备以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理终端设备上，使得在计算机或其他可编程终端设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程终端设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
尽管已描述了本申请实施例的优选实施例，但本领域内的技术人员一旦得知了基本创造性概念，则可对这些实施例做出另外的变更和修改。所以，所附权利要求意欲解释为包括优选实施例以及落入本申请实施例范围的所有变更和修改。
最后，还需要说明的是，在本文中，诸如第一和第二等之类的关系术语仅仅用来将一个实体或者操作与另一个实体或操作区分开来，而不一定要求或者暗示这些实体或操作之间存在任何这种实际的关系或者顺序。而且，术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、物品或者终端 设备不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、物品或者终端设备所固有的要素。在没有更多限制的情况下，由语句“包括一个……”限定的要素，并不排除在包括所述要素的过程、方法、物品或者终端设备中还存在另外的相同要素。
以上对本申请所提供的一种网络的负载均衡方法和一种网络的负载均衡装置，一种网络的负载均衡控制方法和一种网络的负载均衡控制装置，一种网络交互方法和一种网络交互装置，进行了详细介绍，本文中应用了具体个例对本申请的原理及实施方式进行了阐述，以上实施例的说明只是用于帮助理解本申请的方法及其核心思想；同时，对于本领域的一般技术人员，依据本申请的思想，在具体实施方式及应用范围上均会有改变之处，综上所述，本说明书内容不应理解为对本申请的限制。

Claims (24)

  1. 一种网络的负载均衡方法，其特征在于，包括：
    接收控制设备发送的预设流量调度规则，以及后端服务器在第二类网络的唯一路径指示信息；
    从客户端发送的后端服务器访问请求中，获取所述客户端在第一类网络的唯一路径指示信息；
    根据所述后端服务器的唯一路径指示信息，将所述后端服务器访问请求，发送到按照所述预设流量调度规则选择出的至少一个后端服务器；
    接收所述后端服务器返回的请求响应信息，并按照所述客户端的唯一路径指示信息，将所述请求响应信息返回至所述客户端，其中，所述唯一路径指示信息在所述客户端所处的第一类网络以及各后端服务器所处第二类网络中唯一存在，所述第一类网络和所述第二类网络中至少一个为虚拟私有网络VPC。
  2. 根据权利要求1所述的方法，其特征在于，所述唯一路径指示信息由所在虚拟私有网络VPC的网络标识信息以及在所述虚拟私有网络VPC中的地址标识信息生成。
  3. 根据权利要求1所述的方法，其特征在于，还包括：
    按照多个后端应用服务器的唯一路径指示信息，相应访问多个后端服务器；
    对访问的后端服务器进行运行状态检查，针对状态异常的后端服务器，在对应的唯一路径指示信息上标记异常标识；所述异常标识用于指示暂停发送所述后端服务器访问请求至后端服务器。
  4. 根据权利要求2所述的方法，其特征在于，在所述从客户端发送的后端服务器访问请求中，获取所述客户端在第一类网络的唯一路径指示信息的步骤之前，所述方法还包括：
    识别所述客户端所处的第一类网络的网络类型。
  5. 根据权利要求4所述的方法，其特征在于，所述从客户端发送的后端服务器访问请求中，获取所述客户端在第一类网络的唯一路径指示信息的步骤包括：
    针对所述第一类网络的网络类型，从所述后端服务器访问请求中解封出所述第一类网络的网络标识信息和所述客户端的地址标识信息，并生成所述客户端的唯一路径指示信息。
  6. 根据权利要求4所述的方法，其特征在于，所述将所述请求响应信息返回至所述客户端的步骤包括：
    针对所述第一类网络的网络类型，封装所述请求响应信息并发送至所述客户端。
  7. 根据权利要求1所述的方法，其特征在于，在所述从客户端发送的后端服务器访问请求中，获取所述客户端在第一类网络的唯一路径指示信息的步骤之前，所述方法还包括：
    接收并保存多个客户端向所述控制设备注册时提交的所述客户端所处的第一类网络的网络标识信息；
    在所述从客户端发送的后端服务器访问请求中，获取所述客户端的唯一路径指示信息的步骤之后，所述方法还包括：
    判断从所述后端服务器访问请求获取的第一类网络的网络标识信息，是否在保存的第一类网络的网络标识信息的范围内，若否，则返回拒绝访问信息至所述客户端。
  8. 一种网络的负载均衡控制方法，其特征在于，包括：
    从各后端服务器获取所述后端服务器在第二类网络的唯一路径指示信息；
    将预设流量调度规则和所述后端服务器的唯一路径指示信息发送至负载均衡设备，以供所述负载均衡设备根据所述后端服务器的唯一路径指示信息，将客户端的后端服务器访问请求，发送到按照所述预设流量调度规则选择出的至少一个后端服务器，以及按照所述客户端在第一类网络的唯一路径指示信息，将所述后端服务器返回的请求响应信息返回至所述客户端，其中，所述唯一路径指示信息在客户端所处的第一类网络以及各后端服务器所处第二类网络中唯一存在，所述第一类网络和所述第二类网络中至少一个为虚拟私有网络VPC。
  9. 根据权利要求8所述的方法，其特征在于，所述唯一路径指示信息由所在虚拟私有网络VPC的网络标识信息以及在所述虚拟私有网络VPC中的地址标识信息生成。
  10. 根据权利要求8所述的方法，其特征在于，还包括：
    指示所述负载均衡设备将所述负载均衡设备的唯一路径指示信息发送至所述后端服务器，以供所述后端服务器按照所述负载均衡设备的唯一路径指示信息，返回请求响应信息至所述负载均衡设备。
  11. 根据权利要求8所述的方法，其特征在于，还包括：
    接收所述客户端在注册时提交的所述客户端所在的第一类网络的网络标识信息；
    将所述第一类网络的网络标识信息发送至所述负载均衡设备，以供所述负载均衡设备保存并在接收到所述客户端的后端服务器访问请求时，判断从所述后端服务器访问请 求获取的第一类网络的网络标识信息，是否在保存的第一类网络的网络标识信息的范围内，若否，则返回拒绝访问信息至所述客户端。
  12. 一种网络交互方法，其特征在于，包括：
    根据后端服务器在第二类网络的唯一路径指示信息，将客户端对后端服务器的访问请求，发送到按照预设流量调度规则选择出的至少一个后端服务器，所述第二类网络为虚拟私有网络VPC；
    和/或，按照所述客户端在第一类网络的唯一路径指示信息，将后端服务器针对客户端的访问请求返回的请求响应信息返回至所述客户端，所述第一类网络为虚拟私有网络VPC；
    其中，所述唯一路径指示信息在所述客户端所处的第一类网络以及各后端服务器所处第二类网络中唯一存在。
  13. 一种网络的负载均衡装置，其特征在于，包括：
    预设流量调度规则接收模块，用于接收控制设备发送的预设流量调度规则，以及后端服务器在第二类网络的唯一路径指示信息；
    信息获取模块，用于从客户端发送的后端服务器访问请求中，获取所述客户端在第一类网络的唯一路径指示信息；
    后端服务器访问请求发送模块，用于根据所述后端服务器的唯一路径指示信息，将所述后端服务器访问请求，发送到按照所述预设流量调度规则选择出的至少一个后端服务器；
    请求响应信息返回模块，用于接收所述后端服务器返回的请求响应信息，并按照所述客户端的唯一路径指示信息，将所述请求响应信息返回至所述客户端，其中，所述唯一路径指示信息在客户端所处的第一类网络以及各后端服务器所处第二类网络中唯一存在，所述第一类网络和所述第二类网络中至少一个为虚拟私有网络VPC。
  14. 根据权利要求13所述的装置，其特征在于，所述唯一路径指示信息由所在虚拟私有网络VPC的网络标识信息以及在所述虚拟私有网络VPC中的地址标识信息生成。
  15. 根据权利要求13所述的装置，其特征在于，还包括：
    后端服务器访问模块，用于按照多个后端应用服务器的唯一路径指示信息，相应访 问多个后端服务器；
    运行状态检查模块，用于对访问的后端服务器进行运行状态检查，针对状态异常的后端服务器，在对应的唯一路径指示信息上标记异常标识；所述异常标识用于指示暂停发送所述后端服务器访问请求至后端服务器。
  16. 根据权利要求14所述的装置，其特征在于，还包括：
    网络类型识别模块，用于识别所述客户端所处的第一类网络的网络类型。
  17. 根据权利要求16所述的装置，其特征在于，所述信息获取模块包括：
    后端服务器访问请求解封子模块，用于针对所述第一类网络的网络类型，从所述后端服务器访问请求中解封出所述第一类网络的网络标识信息和所述客户端的地址标识信息，并生成所述客户端的唯一路径指示信息。
  18. 根据权利要求16所述的装置，其特征在于，所述请求响应信息返回模块包括：
    请求响应信息封装子模块，用于针对所述第一类网络的网络类型，封装所述请求响应信息并发送至所述客户端。
  19. 根据权利要求13所述的装置，其特征在于，还包括：
    网络标识信息接收模块，用于接收并保存多个客户端向所述控制设备注册时提交的所述客户端所处的第一类网络的网络标识信息；
    所述装置还包括：
    网络标识信息判断模块，用于判断从所述后端服务器访问请求获取的第一类网络的网络标识信息，是否在保存的第一类网络的网络标识信息的范围内，若否，则返回拒绝访问信息至所述客户端。
  20. 一种网络的负载均衡控制装置，其特征在于，所述装置包括：
    后端服务器唯一路径指示信息获取模块，用于从各后端服务器获取所述后端服务器在第二类网络的唯一路径指示信息；
    预设流量调度规则发送模块，用于将预设流量调度规则和所述后端服务器的唯一路径指示信息发送至负载均衡设备，以供所述负载均衡设备根据所述后端服务器的唯一路径指示信息，将客户端的后端服务器访问请求，发送到按照所述预设流量调度规则选择出的至少一个后端服务器，以及按照所述客户端在第一类网络的唯一路径指示信息，将所述后端服务器返回的请求响应信息返回至所述客户端，其中，所述唯一路径指示信息在客户端所处的第一类网络以及各后端服务器所处第二类网络中唯一存在，所述第一类 网络和所述第二类网络中至少一个为虚拟私有网络VPC。
  21. 根据权利要求20所述的装置，其特征在于，所述唯一路径指示信息由所在虚拟私有网络VPC的网络标识信息以及在所述虚拟私有网络VPC中的地址标识信息生成。
  22. 根据权利要求20所述的装置，其特征在于，还包括：
    发送指示模块，用于指示所述负载均衡设备将所述负载均衡设备的唯一路径指示信息发送至所述后端服务器，以供所述后端服务器按照所述负载均衡设备的唯一路径指示信息，返回请求响应信息至所述负载均衡设备。
  23. 根据权利要求20所述的装置，其特征在于，还包括：
    网络标识信息接收模块，用于接收所述客户端在注册时提交的所述客户端所在的第一类网络的网络标识信息；
    网络标识信息发送模块，用于将所述第一类网络的网络标识信息发送至所述负载均衡设备，以供所述负载均衡设备保存并在接收到所述客户端的后端服务器访问请求时，判断从所述后端服务器访问请求获取的第一类网络的网络标识信息，是否在保存的第一类网络的网络标识信息的范围内，若否，则返回拒绝访问信息至所述客户端。
  24. 一种网络交互装置，其特征在于，包括：
    访问请求发送模块，用于根据后端服务器在第二类网络的唯一路径指示信息，将客户端对后端服务器的访问请求，发送到按照预设流量调度规则选择出的至少一个后端服务器，所述第二类网络为虚拟私有网络VPC；
    和/或，请求响应信息返回模块，用于按照所述客户端在第一类网络的唯一路径指示信息，将后端服务器针对客户端的访问请求返回的请求响应信息返回至所述客户端，所述第一类网络为虚拟私有网络VPC；
    其中，所述唯一路径指示信息在所述客户端所处的第一类网络以及各后端服务器所处第二类网络中唯一存在。
PCT/CN2017/072881 2016-02-16 2017-02-04 一种网络的负载均衡、控制及网络交互方法和装置 WO2017140216A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201610087638.2 2016-02-16
CN201610087638.2A CN107086966B (zh) 2016-02-16 2016-02-16 一种网络的负载均衡、控制及网络交互方法和装置

Publications (1)

Publication Number Publication Date
WO2017140216A1 true WO2017140216A1 (zh) 2017-08-24

Family

ID=59615170

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/072881 WO2017140216A1 (zh) 2016-02-16 2017-02-04 一种网络的负载均衡、控制及网络交互方法和装置

Country Status (3)

Country Link
CN (1) CN107086966B (zh)
TW (1) TWI746506B (zh)
WO (1) WO2017140216A1 (zh)

Cited By (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112202918A (zh) * 2020-10-16 2021-01-08 深圳乐播科技有限公司 长连接通信的负载调度方法、装置、设备及存储介质
CN112769776A (zh) * 2020-12-27 2021-05-07 百果园技术(新加坡)有限公司 分布式业务响应方法、系统、装置及存储介质
CN112968976A (zh) * 2021-03-31 2021-06-15 北京奇艺世纪科技有限公司 外网访问控制系统、方法、装置、设备及存储介质
CN113746933A (zh) * 2021-09-14 2021-12-03 京东科技信息技术有限公司 显示信息的方法和装置
CN113992685A (zh) * 2021-10-26 2022-01-28 新华三信息安全技术有限公司 一种服务控制器确定方法、系统及装置
CN114785901A (zh) * 2022-03-28 2022-07-22 宁波一网信息技术有限公司 一种影像调阅方法及系统
CN115412527A (zh) * 2022-08-29 2022-11-29 北京火山引擎科技有限公司 虚拟私有网络之间单向通信的方法及通信装置
CN115952007A (zh) * 2023-03-09 2023-04-11 杭州银行股份有限公司 一种应用运行方法、计算设备及存储介质

Families Citing this family (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109831468A (zh) * 2017-11-23 2019-05-31 北京金山云网络技术有限公司 负载均衡方法、装置、电子设备及存储介质
CN108616456A (zh) * 2018-03-20 2018-10-02 北京优帆科技有限公司 一种基于vxlan的负载均衡方法及负载均衡器
CN110324391B (zh) * 2018-03-30 2022-03-25 武汉斗鱼网络科技有限公司 一种弹幕服务器连接方法、客户端及可读存储介质
CN110753072B (zh) * 2018-07-24 2022-06-03 阿里巴巴集团控股有限公司 负载均衡系统、方法、装置及设备
CN110875889B (zh) * 2018-09-03 2022-09-27 阿里巴巴集团控股有限公司 一种用于获取路径的方法及其装置
CN110928637A (zh) * 2018-09-19 2020-03-27 阿里巴巴集团控股有限公司 负载均衡方法和系统
CN109561171B (zh) * 2019-01-22 2021-11-16 北京百度网讯科技有限公司 虚拟私有云服务的配置方法和装置
CN110336730B (zh) * 2019-07-09 2022-01-18 腾讯科技（深圳）有限公司 一种网络系统及数据传输方法
CN112995247B (zh) * 2019-12-12 2024-05-31 阿里巴巴集团控股有限公司 数据发送或处理的方法、装置和系统
CN111371685B (zh) * 2020-02-28 2022-06-17 北京百度网讯科技有限公司 数据处理、IPv6挂载方法和装置
CN112261095B (zh) * 2020-10-12 2023-11-24 国电南瑞科技股份有限公司 基于两级代理的负载分流实现系统及方法
CN115604272B (zh) * 2022-11-30 2023-03-14 苏州浪潮智能科技有限公司 负载均衡方法、装置、系统及系统创建方法及设备和介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1543142A (zh) * 2003-05-01 2004-11-03 ��ʽ����Ntt����Ħ 路由器和地址标识信息管理服务器
CN1685692A (zh) * 2002-09-25 2005-10-19 西门子公司 用于透明地交换数据包的方法
CN103401800A (zh) * 2013-07-31 2013-11-20 杭州华三通信技术有限公司 一种链路负载均衡方法和设备
CN103491053A (zh) * 2012-06-08 2014-01-01 北京百度网讯科技有限公司 Udp负载均衡方法、系统及装置

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102137173B (zh) * 2010-12-27 2014-09-03 华为技术有限公司 路由信息发布方法、设备及虚拟专用网系统
US9888055B2 (en) * 2013-03-15 2018-02-06 Profitbricks Gmbh Firewall for a virtual network and related techniques

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1685692A (zh) * 2002-09-25 2005-10-19 西门子公司 用于透明地交换数据包的方法
CN1543142A (zh) * 2003-05-01 2004-11-03 ��ʽ����Ntt����Ħ 路由器和地址标识信息管理服务器
CN103491053A (zh) * 2012-06-08 2014-01-01 北京百度网讯科技有限公司 Udp负载均衡方法、系统及装置
CN103401800A (zh) * 2013-07-31 2013-11-20 杭州华三通信技术有限公司 一种链路负载均衡方法和设备

Cited By (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112202918A (zh) * 2020-10-16 2021-01-08 深圳乐播科技有限公司 长连接通信的负载调度方法、装置、设备及存储介质
CN112202918B (zh) * 2020-10-16 2023-08-08 深圳乐播科技有限公司 长连接通信的负载调度方法、装置、设备及存储介质
CN112769776A (zh) * 2020-12-27 2021-05-07 百果园技术(新加坡)有限公司 分布式业务响应方法、系统、装置及存储介质
CN112769776B (zh) * 2020-12-27 2023-04-18 百果园技术(新加坡)有限公司 分布式业务响应方法、系统、装置及存储介质
CN112968976A (zh) * 2021-03-31 2021-06-15 北京奇艺世纪科技有限公司 外网访问控制系统、方法、装置、设备及存储介质
CN112968976B (zh) * 2021-03-31 2024-02-06 北京奇艺世纪科技有限公司 外网访问控制系统、方法、装置、设备及存储介质
CN113746933A (zh) * 2021-09-14 2021-12-03 京东科技信息技术有限公司 显示信息的方法和装置
CN113992685B (zh) * 2021-10-26 2023-09-22 新华三信息安全技术有限公司 一种服务控制器确定方法、系统及装置
CN113992685A (zh) * 2021-10-26 2022-01-28 新华三信息安全技术有限公司 一种服务控制器确定方法、系统及装置
CN114785901A (zh) * 2022-03-28 2022-07-22 宁波一网信息技术有限公司 一种影像调阅方法及系统
CN114785901B (zh) * 2022-03-28 2024-06-11 宁波一网信息技术有限公司 一种影像调阅方法及系统
CN115412527A (zh) * 2022-08-29 2022-11-29 北京火山引擎科技有限公司 虚拟私有网络之间单向通信的方法及通信装置
CN115412527B (zh) * 2022-08-29 2024-03-01 北京火山引擎科技有限公司 虚拟私有网络之间单向通信的方法及通信装置
CN115952007B (zh) * 2023-03-09 2023-06-16 杭州银行股份有限公司 一种应用运行方法、计算设备及存储介质
CN115952007A (zh) * 2023-03-09 2023-04-11 杭州银行股份有限公司 一种应用运行方法、计算设备及存储介质

Also Published As

Publication number Publication date
CN107086966A (zh) 2017-08-22
TWI746506B (zh) 2021-11-21
TW201737667A (zh) 2017-10-16
CN107086966B (zh) 2021-07-27

Similar Documents

Publication Publication Date Title
WO2017140216A1 (zh) 一种网络的负载均衡、控制及网络交互方法和装置
US11528226B2 (en) Network validation with dynamic tunneling
US11765057B2 (en) Systems and methods for performing end-to-end link-layer and IP-layer health checks between a host machine and a network virtualization device
US20220206908A1 (en) Techniques for replicating state information for high availability
CN107872542B (zh) 一种数据传输的方法及网络设备
CN106464564B (zh) 用于网络分组封装和路由的方法、系统和计算机可读介质
US12015552B2 (en) Layer-2 networking information in a virtualized cloud environment
US10944836B2 (en) Dynamically addressable network services
WO2017133291A1 (zh) 一种基于服务器集群的报文生成方法和负载均衡器
US11777897B2 (en) Cloud infrastructure resources for connecting a service provider private network to a customer private network
US20190081890A1 (en) Method and apparatus for information centric networking (icn) over locator/identifier separator protocol (lisp)
CN113364660B (zh) Lvs负载均衡中的数据包处理方法及装置
US20210360040A1 (en) Systems and methods for user capability exchange across networks
US11102114B2 (en) Method, apparatus, and computer-readable storage medium for network optimization for accessing cloud service from on-premises network
WO2021012601A1 (zh) 报文处理方法、装置、设备及可读存储介质
US20230370371A1 (en) Layer-2 networking storm control in a virtualized cloud environment
CN109246016B (zh) 跨vxlan的报文处理方法和装置
US20230396579A1 (en) Cloud infrastructure resources for connecting a service provider private network to a customer private network
CN113067824A (zh) 数据调度方法、系统、虚拟主机及计算机可读存储介质
US9929951B1 (en) Techniques for using mappings to manage network traffic
US12015557B2 (en) Efficient flow management utilizing unified logging
CN110650222B (zh) 一种网络访问方法及装置
US11108735B2 (en) Mapping subnets in different virtual networks using private address space
WO2022146586A1 (en) Layer-2 networking information in a virtualized cloud environment
WO2024059805A1 (en) Console customization for virtual private label clouds

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 17752648

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 17752648

Country of ref document: EP

Kind code of ref document: A1