Method and system for managing network traffic

• US 8,539,062 B1
• Filed: 04/12/2012
• Issued: 09/17/2013
• Est. Priority Date: 12/19/2002
• Status: Active Grant

• Current Assignee: F5 Networks, Inc. (F5 Incorporated)
• Original Assignee: F5 Networks, Inc. (F5 Incorporated)
• Inventors: Masters, Richard Roderick, Hansen, David A.
• Primary Examiner(s): JACOBS, LASHONDA T
• Application Number:
  US13/445,843
• Time in Patent Office: 523 Days
• Field of Search: 709/223, 709/224, 709/203, 709/217, 709/219, 709/225, 709/229
• US Class Current: 709/223
• 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

Abstract

A system and method for directing network connections. The invention enables a network device to direct subsequent connections from a client to a server for accessing resources. A process extracts a persistence key from a received message, and employs the persistence key to identify the appropriate server. An interface is provided, enabling a user program to direct the process of extracting the persistence key. The invention also provides a way for multiple clients to persist to a common server.

Claims

1. A network device, comprising:

a memory device that stores executable instructions; and

one or more processors that executes the instructions to perform actions, including;

receiving from each of a plurality of client devices one or more packets, the one or more packets from each of the plurality of client devices includes data items about at least one other client device in the plurality of client devices;

for each respective client device in the plurality;

extracting from the one or more packets from the respective client device the data items about the at least one other client device in the plurality of client devices;

combining the data items to create a persistence key; and

when the persistence key is found in a mapping store to have a mapping, using the mapping to enable each of the client devices to communicate with each other using a persistent communications or with a common target device.

2. The network device of claim 1, wherein the one or more processors perform actions, further including:

when the persistence key is not found for a client device in the plurality of client devices, then rearranging the data items extracted from the one or more packets from the client device such that a mapping is found in the mapping store.

3. The network device of claim 1, wherein extracting, the data items further comprises buffering a number of packets that is determined based on a set of user defined instructions.

4. The network device of claim 1, wherein the one or more processors perform actions, further including:

when the persistence key is not found in the mapping store for any of the client devices, creating a mapping in the mapping store with the persistence key to enable each of the client devices to communicate with each other or the common target device.

5. The network device of claim 1, wherein the data items in the one or more packets are arranged in a defined order for each of the plurality of client devices.

6. The network device of claim 1, wherein the common target device includes one of a game, a conversation, or a multi-party event hosted on the common target device.

7. An apparatus that stores thereon computer instructions stored thereon, the computer instructions arranged to perform action, including:

receiving from each of a plurality of client devices one or more packets, the one or more packets from each of the plurality of client devices includes at least one data item about at least one other client device in the plurality of client devices;

for each respective client device in the plurality;

extracting from the one or more packets from the respective client device the data items;

combining the data items to create a persistence key; and

when the persistence key is found in a mapping store to have a mapping, using the mapping to enable at least the respective client device to communicate with the at least one other client device also having the same mapping in the mapping store using a persistent communications.

8. The apparatus of claim 7, wherein at least some of the packets are received as part of a secure communication protocol.

9. The apparatus of claim 7, wherein at least one data item is associated with a markup language header tag.

10. The apparatus of claim 7, wherein the mapping in the mapping store is associated with a timestamp useable to invalidate the mapping.

11. The apparatus of claim 7, wherein extracting the data items from the one or more packets further includes extracting at least one data item from within at least an application layer field of the one or more packets.

12. The apparatus of claim 7, wherein the computer instructions arranged to perform actions, including:

when the persistence key is not found for a client device in the plurality of client devices, then rearranging the data items extracted from the one or more packets from the client device such that a mapping is found in the mapping store.

13. The apparatus of claim 7, wherein the computer instructions arranged to perform actions, including:

when the persistence key is not found in the mapping store for any of the client devices, creating a mapping in the mapping store with the persistence key to enable each of the client devices to communicate with each other.

14. A method, comprising:

receiving from each of a plurality of client devices one or more packets, the one or more packets from each of the plurality of client devices includes data items about each of the plurality of client devices;

for each respective client device in the plurality;

extracting from the one or more packets from the respective client device the data items about each of the plurality of client devices;

combining the data items to create a persistence key; and

when the persistence key is found in a mapping store to have a mapping, using the mapping to enable each of the client devices to communicate with each other using a persistent communications or with a common target device.

15. The method of claim 14, further comprising:

when the persistence key is not found in the mapping store for any of the client devices, creating a mapping in the mapping store with the persistence key to enable each of the client devices to communicate with each other or the common target device.

16. The method of claim 14, wherein extracting the data items from the one or more packets further includes extracting at least one data item from within at least an application layer field of the one or more packets.

17. The method of claim 14, wherein extracting the data items further comprises buffering a number of packets that is determined based on a set of user defined instructions.

18. The method of claim 14, further comprising:

when the persistence key is not found for a client device in the plurality of client devices, then rearranging the data items extracted from the one or more packets from the client device such that a mapping is found in the mapping store.

19. The method of claim 14, wherein at least one packet is received using a secure communications protocol.

20. The method of claim 14, wherein the mapping in the mapping store is associated with a timestamp useable to invalidate the mapping.