METHOD, DEVICE, AND SYSTEM FOR MESSAGE DISTRIBUTION

• US 20110029631A1
• Filed: 10/14/2010
• Published: 02/03/2011
• Est. Priority Date: 04/14/2008
• 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: CHEN, Shengping, LI, Yimin
• Granted Patent: US 8,856,243 B2
• Time in Patent Office: Days
• US Class Current: 709/206
• 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/1027 Persistence of sessions during load balancing
• CPC Class Codes: H04L 67/1034 Reaction to server failures by a load balancer
• CPC Class Codes: H04L 67/14 Session management for real-time applications in data packet communications networks H04L65/1066
• CPC Class Codes: H04L 67/141 Setup of application sessions admission control or resource allocation in data switching networks H04L47/70
• CPC Class Codes: H04L 69/18 Multiprotocol handlers, e.g. single devices capable of handling multiple protocols
• CPC Class Codes: H04W 88/16 Gateway arrangements

Abstract

The disclosure relates to a message distribution method, device, and system. A message distribution method includes: creating a session based on a received first type of session message and allocating a corresponding cluster node to the session; and upon receiving a second type of session message associated with the session, distributing the second type of session message to the cluster node corresponding to the session. With the technical solution according to the embodiments of the invention, both the first type of session message and the second type of session message may be processed on the same cluster node, smooth and dynamic capacity expansion may be achieved for the cluster, the system performance may be enhanced, and system maintenance may be facilitated.

Claims

1. A method for message distribution, comprising:

creating a session based on a received first type of session message, and allocating a corresponding cluster node to the session; and

upon receiving a second type of session message associated with the session, distributing the second type of session message to the corresponding cluster node to the session.

2. The method according to claim 1, wherein creating the session based on the received first type of session message comprises:

extracting a first ID from the first type of session message; and

creating the session by using the first ID as a key word, and holding the session.

3. The method according to claim 2, further comprising:

extracting a second ID from the second type of session message;

determining whether the second ID is same as the key word for creating the session; and

if the second ID is same as the key word, associating the second type of session message with the session.

4. The method according to claim 3, wherein the first ID is the Internet Protocol (IP) address of a first terminal transmitting or receiving the first type of session message and the second ID is the IP address of a second terminal transmitting or receiving the second type of session message.

5. The method according to claim 2, wherein the first ID is the number of a first terminal tr ansmitting or receiving the first type of sessio n message, the method further comprising:

extracting a third ID from the first type of session message, the third ID being the IP address of a the first terminal transmitting or receiving the first type of session message, and creating a correspondence relationship between the IP address and the terminal number;

upon receiving the second type of session message, extracting the second ID from the type of session message, the second ID being the IP address of a second terminal transmitting or receiving the second type of session message;

based on the correspondence relationship between the IP address and the terminal number, searching for a terminal number corresponding to the second ID;

determining whether the found terminal number is same as the key word for creating the session; and

if the found terminal number is same as the key word, associating the second type of session message with the session.

6. The method according to claim 1, further comprising:

detecting whether the cluster node has a fault; and

if the cluster node has a fault, creating another session based on the second type of session message and allocating another corresponding non-fault cluster node to the session.

7. The method according to claim 1, further comprising:

transmitting at least one of the first type of session message and the second type of session message to a backup node to that backs up the session information in at least one of the first type of session message and the second type of session message.

8. The method according to any one of claim 1, wherein the first type of session message is a session control message and the second type of session message is a session traffic message.

19. The method according to any one of claim 1, wherein the first type of session message is a session traffic message and the second type of session message is a session control message.

9. A load balance device, comprising:

a preprocessing unit configured to create a session based on a received first type of session message and allocate a corresponding cluster node to the session; and

a distribution unit configured to;

upon receiving a second type of session message associated with the session, distribute the second type of session message to the cluster node corresponding to the session.

10. The device according to claim 9, wherein the preprocessing unit comprises:

a first extraction module configured to extract a first ID from the first type of session message;

a creation module configured to create the session by using the first ID as a key word, and hold the session; and

an allocation module configured to allocate a corresponding cluster node to the session.

11. The device according to claim 10, wherein the distribution unit comprises:

a receiving module configured to receive a second type of session message;

a second extraction module configured to extract a second ID from the second type of session message;

a determination module configured to determine whether the second ID is same as the key word for creating the session, wherein the second type of session message is associated with the session if the second ID is same as the key word; and

a transmission module configured to distribute the second type of session message associated with the session to the cluster node corresponding to the session when the determination module determines that the second type of session message is associated with the session.

12. The device according to claim 11, wherein the first ID is the IP address of a first terminal transmitting or receiving the first type of session message and the second ID is the IP address of a second terminal transmitting or receiving the second type of session message.

13. The device according to claim 10, wherein the first ID is the number of a first terminal transmitting or receiving the first type of session message, the preprocessing unit further comprising:

a third extraction module configured to extract a third ID from the first type of session message, the third ID being the IP address of a first terminal transmitting or receiving the first type of session message; and

a relationship module configured to create a correspondence relationship between the IP address of the first terminal transmitting or receiving the first type of message and the terminal number;

the distribution unit comprising;

a receiving module configured to receive the second type of session message;

a second extraction module configured to extract the second ID from the second type of session message, the second ID being the IP address of a second terminal transmitting or receiving the second type of session message;

a searching module configured to;

based on the correspondence relationship in the relationship module, search for a terminal number corresponding to the second ID;

a determination module configured to determine whether the terminal number is same as the key word for creating the session, wherein the second type of session message being is associated with the session if the terminal number is same as the key word; and

a transmission module configured to distribute the second type of session message associated with the session to the cluster node corresponding to the session when the determination module determines that the second type of session message is associated with the session.

14. The device according to claim 9, further comprising:

a fault detection unit configured to detect whether the cluster node has a fault, and if the cluster node has a fault, trigger the preprocessing unit to create another session based on the second type of session message and allocate another corresponding non-fault cluster node to the session.

15. The device according to claim 9, further comprising:

a backup unit configured to transmit the first type of session message or the second type of session message to a backup node so as to back up the session information in the first type of sessio n message or the second type of session message.

16. The device according to any one of claim 9, wherein the first type of session message is a session control message and the second type of session message is a session traffic message.

20. The device according to any one of claim 9, wherein the first type of session message is a session traffic message and the second type of session message is a session control message.

17. A cluster node device, comprising a Wireless Application Protocol (WAP) Gateway (GW) and a corresponding User Information Database (UIDB), wherein:

the UIDB is configured to receive a control session message and store the control session information in the control session message; and

the WAP GW is configured to receive a traffic session message, search for the control session information in the UIDB based on the traffic session message, and process the traffic session message based on the session control information.

18. The device according to claim 17, where the WAP GW comprises:

a receiving unit configured to receive a traffic session message;

a local searching unit configured to transmit a search request for the control session information to the UIDB and receive control session information in a response from the UIDB;

an external searching unit configured to;

when the local searching unit fails to find the control session information, search for the control session information backed up on a backup node device outside the cluster node device; and

a processing unit configured to process the traffic session message based on the found control session information.