Persistence based on server response in an IP multimedia subsystem (IMS)

• US 9,832,069 B1
• Filed: 05/29/2009
• Issued: 11/28/2017
• Est. Priority Date: 05/30/2008
• Status: Active Grant

• Current Assignee: F5 Networks, Inc. (F5 Incorporated)
• Original Assignee: F5 Networks, Inc. (F5 Incorporated)
• Inventors: Cleveland, Randall, Schrock, Mike, Glover, Donald, Thirasuttakorn, Nat
• Primary Examiner(s): Tran, Nam
• Application Number:
  US12/475,307
• Time in Patent Office: 3,105 Days
• CPC Class Codes: H04L 41/0668 by dynamic selection of recovery network elements, e.g. replacement by the most appropriate element after failure
• CPC Class Codes: H04L 67/1006 with static server selection, e.g. the same server being selected for a specific client
• CPC Class Codes: H04L 67/1027 Persistence of sessions during load balancing
• CPC Class Codes: H04L 67/1029 using data related to the state of servers by a load balancer
• CPC Class Codes: H04L 67/1034 Reaction to server failures by a load balancer

Abstract

Embodiments are directed towards managing persistence of network traffic using deep packet inspections of network response packets from an application server. In one embodiment, the network packets are associated with SIP messages. A traffic management device (TMD) interposed between client devices and a plurality of application servers receives messages from the client device and/or the application servers. The TMD performs a deep packet inspection to determine if a defined key value pair that includes a session identifier is detected. If so, and the message is from the application server, the session identifier is then mapped to an application server identifier to persistently refer each subsequent inbound packet from a client device having the same session identifier to the application server mapped to the session identifier.

Claims

1. A network device for managing communications over a network, comprising:

a memory arranged to store data and instructions;

an input interface for receiving requests and sending responses; and

a processor arranged to enable actions embodied by at least a portion of the stored instructions, the actions comprising;

receiving each outbound packet from an application server within a plurality of application servers; and

when persistence information for a pre-existing communication session between the application server and the network device is absent from a table managed by the network device, performing actions, including;

performing a deep packet inspection at a layer four or above of the OSI reference model within one or more outbound packets to identify application layer data having a session identifier that uniquely identifies the communication session, wherein the session identifier is a pre-defined string of characters that is located anywhere within application layer data;

mapping the session identifier to an identifier of the application server as persistence information in the table; and

using the mapping in the table to persistently refer each subsequent inbound packet from a client device to the corresponding application server; and

employing a failure of the application server that is detected in the communication session to update the persistent information in the table to identify another application server that transparently assumes the role of the failed application server in the communication session with the network device.

2. The network device of claim 1, wherein the deep packet inspection further comprises examining data within an application layer for a defined key value pair.

3. The network device of claim 1, wherein the outbound packet from the application server is a Session Initiation Protocol (SIP) packet.

4. The network device of claim 1, wherein the processor is arranged to perform actions, further comprising:

performing a deep packet inspection on each inbound packet;

if an inbound packet is without a session identifier within the inbound packet as determined by the deep packet inspection, selecting another application server from within the plurality of application servers using a load balancing mechanism to forward the inbound packet.

5. The network device of claim 1, wherein at least one of the inbound or outbound packets is includes Hypertext Transfer Protocol (HTTP) data.

6. A non-transitory machine-readable storage medium having machine-executable instructions stored thereon, which when executed by at least one processor for a traffic management device that is interposed between client devices and a plurality of application servers, causes the at least one processor to perform actions to manage communications over a network, the actions comprising:

receiving a message from a client device; and

when persistence information for a pre-existing communication session between the application server and the traffic management device is absent from a table managed by the traffic management device, performing actions, including;

performing a deep packet inspection at a layer four or above of the OSI reference model within one or more outbound packets to identify application layer data having a session identifier that uniquely identifies the communication session, wherein the session identifier is a pre-defined string of characters that is located anywhere within application layer data;

mapping the session identifier to an identifier of the application server as persistence information in the table; and

using the mapping in the table to persistently refer each subsequent inbound packet from a client device to the corresponding application server; and

employing a failure of the application server that is detected in the communication session, to update the persistent information in the table to identify another application server that transparently assumes the role of the failed application server in the communication session with the traffic management device.

7. The non-transitory machine-readable storage medium of claim 6, wherein the at least one processor performs one or more further actions, comprising:

if the application server mapped to the session identifier fails, revising the mapping of the session identifier to identifier associated with another application server, wherein the other application server is configured as a failover device.

8. The non-transitory machine-readable storage medium of claim 6, wherein at least one of the message or the response includes at least one of Session Initiation Protocol (SIP) data, or Hypertext Transfer Protocol (HTTP) data.

9. The non-transitory machine-readable storage medium of claim 6, wherein the at least one processor performs further actions, comprising:

receiving a message from one of the application servers wherein the message is other than a response message, and wherein the message is to be sent to a plurality of client devices;

performing a deep packet inspection a layer four or above of the OSI reference model within the message'"'"'s application layer data to identify a session identifier that uniquely identifies a communication session;

mapping the session identifier to an identifier of the sending application server; and

using the mapping to persistently refer each subsequent response from the plurality of client devices having the same session identifier within the response to the application server mapped to the session identifier.

10. The non-transitory machine-readable storage medium of claim 6, wherein the communication session is associated with a multimedia session.

11. The non-transitory machine-readable storage medium of claim 6, wherein detecting the session identifier further comprises detecting a key value pair.

12. A method executed on a traffic management device that is interposed between a plurality of client devices and a plurality of application servers, the method when executed enables the traffic management device to manage a request for a managing communications over a network, comprising:

receiving a plurality of messages, from an application server, each message being directed to a different client device within the plurality of client devices; and

when persistence information for a pre-existing communication session between the application server and the traffic management device is absent from a table managed by the traffic management device, performing actions, including;

performing a deep packet inspection at a layer four or above of the OSI reference model within one or more outbound packets to identify application layer data having a session identifier that uniquely identifies the communication session, wherein the session identifier is a pre-defined string of characters that is located anywhere within application layer data;

mapping the session identifier to an identifier of the application server as persistence information in the table; and

using the mapping in the table to persistently refer each subsequent inbound packet from a client device to the corresponding application server; and

employing a failure of the application server that is detected in the communication session to update the persistent information in the table to identify another application server that transparently assumes the role of the failed application server in the communication session with the traffic management device.

13. The method of claim 12, wherein the communication session is associated with at least one of an IP multimedia session.

14. The method of claim 12, further comprising:

receiving another message from one of the plurality of client devices;

performing an inspection of application layer data within the message to determine if a unique session identifier is present within the application layer data of the message;

when the unique identifier is undetected within the message based on the inspection, forwarding the other message to one of a plurality of application servers based on a load balancing mechanism; and

upon receiving a response from the load balanced application server, mapping another unique session identifier from within an application layer of the response such that subsequent messages from the client devices having the same unique session identifier are persistently communicated to the load balanced application server.

15. The method of claim 12, wherein performing an inspection of the application layer data further comprises searching for a predefined string of characters within any location of the application layer data.

16. The method of claim 12, wherein message is associated with a Session Initiation Protocol (SIP) message.

17. A system for managing communications over a network, comprising:

a plurality of application servers; and

a traffic management device that is interposed between the plurality of application servers and client devices, and is configured and arranged to perform actions, including;

causing each message from an application server within the plurality of application servers to be received by the traffic management device; and

when persistence information for a pre-existing communication session between the application server and the traffic management device is absent from a table managed by the traffic management device, performing actions, including;

performing a deep packet inspection at a layer four or above of the OSI reference model within one or more outbound packets to identify application layer data having a session identifier that uniquely identifies the communication session, wherein the session identifier is a pre-defined string of characters that is located anywhere within application layer data;

mapping the session identifier to an identifier of the application server as persistence information in the table; and

using the mapping in the table to persistently refer each subsequent inbound packet from a client device to the corresponding application server; and

employing a failure of the application server that is detected in the communication session to update the persistent information in the table to identify another application server that transparently assumes the role of the failed application server in the communication session with the traffic management device.

18. The system of claim 17, wherein message is associated with a Session Initiation Protocol (SIP) message.

19. The system of claim 17, wherein detecting the unique session identifier within the application layer data further comprises detecting the unique session identifier independent of a defined location of the application layer data.

20. The system of claim 17, wherein the message is associated with an HTTP message.