METHOD AND SYSTEM FOR PROCESSING REQUEST MESSAGE, AND LOAD BALANCER DEVICE

• US 20120233248A1
• Filed: 05/24/2012
• Published: 09/13/2012
• Est. Priority Date: 11/24/2009
• Status: Active Grant

• Current Assignee: Huawei Technologies Co., Ltd. (Huawei Investment & Holding Co., Ltd.)
• Original Assignee: Huawei Technologies Co., Ltd. (Huawei Investment & Holding Co., Ltd.)
• Inventors: Zou, Xianjun, Chang, Heng, Ma, Qifeng, Li, Yan, Li, Sihao
• Granted Patent: US 9,357,028 B2
• Time in Patent Office: Days
• US Class Current: 709/203
• CPC Class Codes: H04L 47/125 by balancing the load, e.g. traffic engineering
• CPC Class Codes: H04L 67/1001 for accessing one among a plurality of replicated servers
• CPC Class Codes: H04L 67/56 Provisioning of proxy services store-and-forward switching systems in data switching networks H04L12/54
• CPC Class Codes: H04L 67/564 Enhancement of application control based on intercepted application data

Abstract

A method and a system for processing a request message, and a load balancer device are provided. The load balancer obtains a service name and an operation name through simple string matching, and a large amount of computing is performed at a server side, thereby solving a session hold problem of a composition engine cluster, reducing a computing task of a load balancer, maximizing a fan-out capability of the load balancer, and increasing a throughput of the composition engine cluster to a maximum extent, therefore satisfying a demand for a large capacity of a composition engine.

Claims

1. A method for processing a request message, comprising:

receiving and parsing a request message sent by a request end, and obtaining a script name corresponding to the request message and a message type of the request message;

obtaining a target server of the request message according to a server list corresponding to the script name and the message type, and forwarding the request message to the target server; and

receiving a response message returned by the target server after the target server executes a script corresponding to the script name, and returning a response message that satisfies a return condition to the request end.

2. The method for processing a request message according to claim 1, wherein the returning the response message that satisfies the return condition to the request end comprises:

returning a response message indicating successful execution to the request end;

or

returning a last received rejection message to the request end if all the target servers return rejection messages.

3. The method for processing a request message according to claim 1, wherein the obtaining the target server of the request message according to the server list corresponding to the script name and the message type and forwarding the request message to the target server comprises one of:

selecting a server with the least load among servers that are not overloaded in an entire system as the target server if the request message is an initialization message and the server list corresponding to the script name is empty, forwarding the request message to the target server, and adding an address of the target server to the server list corresponding to the script name;

or

selecting a server that is not overloaded from servers recorded in the server list as the target server if the request message is an initialization message and the server list corresponding to the script name is not empty, and forwarding the request message to the target server;

or

selecting a server with the least load among servers that are not recorded in the server list and are not overloaded in the entire system as the target server if the request message is an initialization message, the server list corresponding to the script name is not empty, and servers recorded in the server list are all overloaded, forwarding the request message to the target server, and adding an address of the target server to the server list;

or

directly rejecting the request message if the request message is an initialization message and servers in the entire system are all overloaded;

or

selecting all servers recorded in the server list corresponding to the script name as the target servers if the request message is not an initialization message, and forwarding the request message to the target servers;

or

directly rejecting the request message if the request message is not an initialization message and the server list corresponding to the script name is empty.

4. The method for processing a request message according to claim 2, wherein the obtaining the target server of the request message according to the server list corresponding to the script name and the message type and forwarding the request message to the target server comprises one of:

selecting a server with the least load among servers that are not overloaded in an entire system as the target server if the request message is an initialization message and the server list corresponding to the script name is empty, forwarding the request message to the target server, and adding an address of the target server to the server list corresponding to the script name;

or

selecting a server that is not overloaded from servers recorded in the server list as the target server if the request message is an initialization message and the server list corresponding to the script name is not empty, and forwarding the request message to the target server;

or

selecting a server with the least load among servers that are not recorded in the server list and are not overloaded in the entire system as the target server if the request message is an initialization message, the server list corresponding to the script name is not empty, and servers recorded in the server list are all overloaded, forwarding the request message to the target server, and adding an address of the target server to the server list;

or

directly rejecting the request message if the request message is an initialization message and servers in the entire system are all overloaded;

or

selecting all servers recorded in the server list corresponding to the script name as the target servers if the request message is not an initialization message, and forwarding the request message to the target servers;

or

directly rejecting the request message if the request message is not an initialization message and the server list corresponding to the script name is empty.

5. The method for processing a request message according to claim 2, wherein the returning the response message indicating successful execution to the request end comprises one of:

directly returning the response message indicating successful execution returned by the target server after the target server executes the script corresponding to the script name to the request end if a connection length of the server list corresponding to the request message is 1;

or

returning the response message indicating successful execution among multiple response messages returned by the target servers after the target servers execute the script corresponding to the script name to the request end if the connection length of the server list corresponding to the request message is greater than 1.

6. The method for processing a request message according to claim 1, after the obtaining the target server of the request message according to the server list corresponding to the script name and the message type and forwarding the request message to the target server, further comprising:

setting a time stamp of the target server recorded in the server list to a current time.

7. The method for processing a request message according to claim 2, after the obtaining the target server of the request message according to the server list corresponding to the script name and the message type and forwarding the request message to the target server, further comprising:

setting a time stamp of the target server recorded in the server list to a current time.

8. The method for processing a request message according to claim 6, further comprising:

periodically receiving a script list that is not run reported by the target server, comparing a report time of the target server and the time stamp of the target server recorded in the server list corresponding to the script name, and deleting an address of the target server in the server list if the report time is later than the time stamp.

9. A load balancer device, comprising:

a first processing module, configured to receive and parse a request message sent by a request end, and obtain a script name corresponding to the request message and a message type of the request message;

a second processing module, configured to obtain a target server of the request message according to a server list corresponding to the script name and the message type, and forward the request message to the target server; and

a third processing module, configured to receive a response message returned by the target server after the target server executes a script corresponding to the script name, and return a response message that satisfies a return condition to the request end.

10. The load balancer device according to claim 9, wherein the third processing module comprises:

a fifth processing sub-module, configured to return a response message indicating successful execution to the request end; and

a sixth processing sub-module, configured to return a last received rejection message to the request end if all the target servers return rejection messages.

11. The load balancer device according to claim 9, wherein the second processing module comprises any one of or a combination of the following sub-modules:

a first processing sub-module, configured to select a server with the least load among servers that are not overloaded in an entire system as the target server if the request message is an initialization message and the server list corresponding to the script name is empty, forward the request message to the target server, and add an address of the target server to the server list corresponding to the script name;

a second processing sub-module, configured to select a server that is not overloaded from servers recorded in the server list as the target server if the request message is an initialization message and the server list corresponding to the script name is not empty, and forward the request message to the target server;

a third processing sub-module, configured to select a server with the least load among servers that are not recorded in the server list and are not overloaded in the entire system as the target server if the request message is an initialization message, the server list corresponding to the script name is not empty, and servers recorded in the server list are all overloaded, forward the request message to the target server, and add the address of the target server to the server list; and

a fourth processing sub-module, configured to select all servers recorded in the server list corresponding to the script name as the target servers if the request message is not an initialization message, and forward the request message to the target servers.

12. The load balancer device according to claim 10, wherein the second processing module comprises any one of or a combination of the following sub-modules:

a first processing sub-module, configured to select a server with the least load among servers that are not overloaded in an entire system as the target server if the request message is an initialization message and the server list corresponding to the script name is empty, forward the request message to the target server, and add an address of the target server to the server list corresponding to the script name;

a second processing sub-module, configured to select a server that is not overloaded from servers recorded in the server list as the target server if the request message is an initialization message and the server list corresponding to the script name is not empty, and forward the request message to the target server;

a third processing sub-module, configured to select a server with the least load among servers that are not recorded in the server list and are not overloaded in the entire system as the target server if the request message is an initialization message, the server list corresponding to the script name is not empty, and servers recorded in the server list are all overloaded, forward the request message to the target server, and add the address of the target server to the server list; and

a fourth processing sub-module, configured to select all servers recorded in the server list corresponding to the script name as the target servers if the request message is not an initialization message, and forward the request message to the target servers.

13. The load balancer device according to claim 9, further comprising:

an update module, configured to set a time stamp of the target server recorded in the server list to a current time after the request message is forwarded to the target server, periodically receive a script list that is not run reported by the target server, compare a report time and the time stamp of the target server in the server list corresponding the script name, and delete an address of the target server in the server list if the report time is later than the time stamp.

14. The load balancer device according to claim 10, further comprising:

an update module, configured to set a time stamp of the target server recorded in the server list to a current time after the request message is forwarded to the target server, periodically receive a script list that is not run reported by the target server, compare a report time and the time stamp of the target server in the server list corresponding the script name, and delete an address of the target server in the server list if the report time is later than the time stamp.

15. A system for processing a request message, comprising a request end and multiple servers, and further comprising the load balancer device according to claim 9 disposed between the request end and the multiple servers.