High availability session reconstruction

Patent metadata

Field	Value
Publication number	US-9344460-B2
Application number	US-201213570528-A
Country	US
Kind code	B2
Filing date	Aug 9, 2012
Priority date	Aug 9, 2012
Publication date	May 17, 2016
Grant date	May 17, 2016

Abstract

A first message is received at a primary container that is replicated by a secondary container. The first message is an initial message to initiate a first session. The first message is processed by an application in the primary container. At a point in time, the primary container is unavailable and the system and method detect that the primary container is unavailable. A second message is received. The second message is associated with the first session. The second message is modified by moving at least a portion of a header in the second message into a different header in the second message and adding an additional header to the second message in response to the primary container being unavailable.

First claim

What is claimed is:

1. A method comprising:
receiving, via a network, at a primary container being executed by a hardware processor, a first message, wherein the first message is an initial message to initiate a first communication session between a first communication device and a second communication device and wherein at least a portion of the primary container is replicated in a secondary container;
processing, by the hardware processor, the first message in an application of the primary container;
detecting, by a front end processor being executed by the hardware processor, that the primary container is unavailable, wherein the front end processor, is a hardware processor;
receiving, via the network and by the front end processor being executed by the hardware processor, a second message from the first communication device or second communication device, wherein the second message is associated with the first communication session; and
responsive to the primary container being unavailable, modifying, by the front end processor being executed by the hardware processor, the second message by moving at least a portion of a header in the second message into a different header in the second message and adding an additional header to the second message.

2. The method of claim 1 , wherein the first message is a first Session Initiation Protocol (SIP) message, the second message is a second SIP message, the modified second message is a modified second SIP message, and the first communication session is a first SIP communication session.

3. The method of claim 2 , wherein modifying the second message further comprises modifying a SIP To field in the second message.

4. The method of claim 3 , further comprising the steps of:
sending the modified second SIP message to a first message processor;
receiving the modified second SIP message at the first message processor;
forwarding the modified SIP message to a second message processor;
sending a response to the forwarded modified SIP message to the first message processor;
receiving the response to the forwarded modified SIP message at the first message processor;
in response to receiving the forwarded modified SIP message at the first message processor, encapsulating the modified SIP message into a new SIP INVITE message; and
sending the new SIP INVITE message to an application in the secondary container, wherein the application in the secondary container is a replicated version of the application in the primary container.

5. The method of claim 3 , further comprising the steps of:
creating a new SIP INVITE that comprises a correlation identifier which identifies the first SIP communication session in the primary container and wherein the new SIP INVITE does not have the SIP To tag;
sending the new SIP INVITE to the secondary container;
receiving the new SIP INVITE at an application in the secondary container;
restoring a state of the application in the secondary container based on the correlation identifier;
sending a 200 OK to reestablish the first SIP communication session;
changes a dialog identifier that identifies the reestablished first SIP communication session in the second message; and
sending the second message to the application in the secondary container.

6. The method of claim 5 , wherein the 200 OK is sent from the application in the secondary container.

7. The method of claim 5 , wherein the 200 OK is sent by the first communication device or the second communication device.

8. The method of claim 5 , further comprising the step of embedding the second message into the new SIP INVITE.

9. The method of claim 5 , further comprising the step of mapping the dialog identifier for any subsequent messages for the reestablished first SIP communication session.

10. The method of claim 2 , wherein the second SIP message is at least one of: an ACK request to a 2xx INVITE response, an ACK request for a 3xx-6xx INVITE response, an in-dialog INVITE request, an in-dialog non-INVITE request, a provisional response, a 2xx response to INVITE, a 3xx-6xx response to INVITE, a final response to a non-INVITE request, a final response to an in-dialog non-INVITE, a response of any kind in the failover group that is not associated with the session manager 110 that received the response, or a request of any kind that is not associated with the session manager 110 that received the response.

11. The method of claim 1 , wherein the primary container and the secondary container are JSR-289 containers.

12. A communication system comprising:
a primary container that receives a first message, via a network, wherein the first message is an initial message to initiate a first communication session between a first communication device and a second communication device and wherein at least a portion of the primary container is replicated in a secondary container;
an application in the primary container that processes the first message;
a front end-processor that detects that the primary container is unavailable, wherein the front end processor is a hardware processor, receives, via the network, a second message from the first or second communication device, wherein the second message is associated with the first communication session, modifies the second message by moving at least a portion of a header in the second message into a different header in the second message and adds an additional header to the second message in response to the primary container being unavailable.

13. The system of claim 12 , wherein the first message is a first Session Initiation Protocol (SIP) message, the second message is a second SIP message, the modified second message is a modified second SIP message, and the first communication session is a first SIP session, and wherein:
the front-end processor modifies the second message by changing a SIP To field in the second message and sends the modified second SIP message to the secondary container; and
a message processor in the secondary container receives the modified second SIP message, encapsulates the second SIP message into a new SIP INVITE message in response to receiving the modified second SIP message, and sends the new SIP INVITE message to an application in the secondary container, wherein the application in the secondary container is a replicated version of the application in the primary container.

14. The system of claim 12 , wherein the first message is a first Session Initiation Protocol (SIP) message, the second message is a second SIP message, the modified second message is a modified second SIP message, and the first communication session is a first SIP communication session, and wherein:
the front end processor creates a new SIP INVITE that comprises a correlation identifier which identifies the first SIP communication session in the primary container and wherein the new SIP INVITE does not have the SIP To tag, sends the new SIP INVITE to the secondary container, change a dialog identifier that identifies the reestablished first SIP communication session in the second message, and sends the second message to the application in the secondary container; and
an application in the secondary container that receives the new SIP INVITE, and restores a state of the application in the secondary container based on the correlation identifier.

15. The system of claim 14 , wherein the application in the secondary container sends a 200 OK.

16. The system of claim 14 , wherein a 200 OK is sent by the first communication device or the second communication device.

17. The system of claim 14 , w

Assignees

• Haserodt Kurt
• Ohrstrom-Sandgren Thorsten
• Ezell Joel
• Gillespie Don
• Avaya Inc

Inventors

• Haserodt Kurt
• Ohrstrom-Sandgren Thorsten
• Ezell Joel
• Gillespie Don

Classifications

• H04L65/1069 Primary

  Session establishment or de-establishment · CPC title

• H04L65/1006

  Electricity · mapped topic

• H04L69/40

  for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection (management of faults, events, alarms or notifications in data switching networks H04L41/06) · CPC title

• H04L65/1101

  Session protocols · CPC title

• H04L65/1104

  Session initiation protocol [SIP] · CPC title