Failover/failback trigger using SIP messages in a SIP survivable configuration
First Claim
Patent Images
1. A method, comprising:
- determining that a state of a component in a communication system has changed from a first state to a second state;
generating a message comprising information related to the determined second state of the component; and
transmitting the message to a User Agent associated with the component, the User Agent internally maintaining a list of controllers, the internally maintained list of controllers including at least a first and a second controller capable of controlling the User Agent, wherein receipt of the message comprising information related to the determined second state of the component causes the User Agent to update an order of controllers in its internally maintained list of controllers, wherein the component comprises a first Session Initiation Protocol (SIP) controller for the User Agent, wherein the first state comprises an operational SIP state, wherein the second state comprises a failed SIP state, wherein the message comprises a standard SIP NOTIFY message that causes the User Agent to attempt re-registration with all controllers in its internally maintained list of controllers, and wherein the internally maintained list of controllers comprises the first SIP controller as well as a second SIP controller.
22 Assignments
0 Petitions
Accused Products
Abstract
Provided are methods, devices, and systems for maintaining a SIP survivable network. The present invention may utilize messages, such as SIP NOTIFY messages, to trigger various network components to failover and failback based on the determined status of the SIP network.
61 Citations
13 Claims
-
1. A method, comprising:
-
determining that a state of a component in a communication system has changed from a first state to a second state; generating a message comprising information related to the determined second state of the component; and transmitting the message to a User Agent associated with the component, the User Agent internally maintaining a list of controllers, the internally maintained list of controllers including at least a first and a second controller capable of controlling the User Agent, wherein receipt of the message comprising information related to the determined second state of the component causes the User Agent to update an order of controllers in its internally maintained list of controllers, wherein the component comprises a first Session Initiation Protocol (SIP) controller for the User Agent, wherein the first state comprises an operational SIP state, wherein the second state comprises a failed SIP state, wherein the message comprises a standard SIP NOTIFY message that causes the User Agent to attempt re-registration with all controllers in its internally maintained list of controllers, and wherein the internally maintained list of controllers comprises the first SIP controller as well as a second SIP controller. - View Dependent Claims (2, 3, 4, 5, 6, 7)
-
-
8. A communication device, comprising:
-
a communication interface configured to connect the communication device to a communication network; and a discovery module operable to determine that a state of a component in a communication system has changed from a first state to a second state, generate a message comprising information related to the determined second state of the component, and transmit the message, via the communication interface, to a User Agent associated with the component, the User Agent internally maintaining a list of controllers, the internally maintained list of controllers including at least a first and a second controller capable of controlling the User Agent, wherein receipt of the message comprising information related to the determined second state of the component causes the User Agent to update an order of controllers in its internally maintained list of controllers, wherein the component comprises a first Session Initiation Protocol (SIP) controller for the User Agent, wherein the first state comprises an operational SIP state, wherein the second state comprises a failed SIP state, wherein the discovery module is further operable to generate instructions for execution by the User Agent and incorporate the instructions in the message, wherein the list of controllers comprises a list of SIP controllers, wherein the instructions identify the first SIP controller such that the User Agent can reference its internally maintained list of SIP controllers to identify the first SIP controller as a SIP controller with which it is to attempt re-registration, wherein the message comprises a standard SIP NOTIFY message that causes the User Agent to attempt re-registration with at least two controllers in its internally maintained list of SIP controllers, and wherein the internally maintained list of controllers comprises the first SIP controller and a second SIP controller. - View Dependent Claims (9, 10, 11)
-
-
12. A communication system, comprising:
-
means for determining that a state of a component in a communication system has changed from a first state to a second state; means for generating a message comprising information related to the determined second state of the component; and means for transmitting the message to a User Agent associated with the component, the User Agent internally maintaining a list of Session Initiation Protocol (SIP) controllers, the internally maintained list of SIP controllers including at least a first and a second SIP controller capable of controlling the User Agent, wherein receipt of the message comprising information related to the determined second state of the component causes the User Agent to update an order of controllers in its internally maintained list of SIP controllers, wherein the component comprises the first SIP controller for the User Agent, wherein the first state comprises an operational SIP state, wherein the second state comprises a failed SIP state, wherein the message prompts the User Agent to attempt re-registration with the first SIP controller, wherein the first SIP controller comprises a primary controller of the User Agent, wherein the means for generating is further operable to generate instructions for execution by the User Agent and incorporate the instructions in the message, and wherein the instructions identify the first SIP controller such that the User Agent can reference its internally maintained list of SIP controllers to identify the first SIP controller and the second SIP controller as SIP controllers with which it is to attempt re-registration.
-
-
13. A communication system, comprising:
-
means for determining that a state of a component in a communication system has changed from a first state to a second state; means for generating a message comprising information related to the determined second state of the component; and means for transmitting the message to a User Agent associated with the component, the User Agent internally maintaining a list of Session Initiation Protocol (SIP) controllers, the internally maintained list of SIP controllers including at least a first and a second SIP controller capable of controlling the User Agent, wherein receipt of the message comprising information related to the determined second state of the component causes the User Agent to update an order of controllers in its internally maintained list of SIP controllers, wherein the component comprises the first SIP controller for the User Agent, wherein the first state comprises an operational SIP state, wherein the second state comprises a failed SIP state, wherein the message prompts the User Agent to attempt re-registration with the first SIP controller, wherein the first SIP controller comprises a primary controller of the User Agent, wherein the message comprises a standard SIP NOTIFY message that causes the User Agent to attempt re-registration with all controllers in its internally maintained list of SIP controllers, and wherein the internally maintained list of controllers comprises the first SIP controller.
-
Specification