SYSTEM AND METHOD FOR PROVIDING TIMER AFFINITY THROUGH NOTIFICATIONS WITHIN A SESSION-BASED SERVER DEPLOYMENT
First Claim
1. A telecommunication system that provides timer affinity through notifications, said telecommunication system comprising:
- one or more engine nodes that process incoming communications, each communication being associated with a session between multiple participants; and
one or more timer objects associated with the session and accessible by the engine nodes, said timer objects being maintained remotely with respect to the engine nodes, wherein said timer objects, once initiated, gradually reduce a specified time period until the timer objects fire;
wherein once a particular timer object fires, a notification is transmitted to an engine node that processed the last communication for the session associated with said particular timer object; and
wherein said engine node that processed said last communication is assigned the particular timer object for processing.
1 Assignment
0 Petitions
Accused Products
Abstract
The session-based server deployment can be comprised of an engine tier that is designed for high throughput processing of communications and a state tier that maintains state information for access by the engine tier. The engine tier can include a plurality of engine nodes that process incoming messages. The state nodes can contain call state, including various timers. When processing a call, an engine can set various timers in the state tier. Upon expiration of a timer, the state node can transmit a notification assigning the timer to the corresponding engine node which handled previous communications for the call. This affinity between the timer and its respective engine can provide numerous benefits, such as reduced latency and more localized data access.
130 Citations
20 Claims
-
1. A telecommunication system that provides timer affinity through notifications, said telecommunication system comprising:
-
one or more engine nodes that process incoming communications, each communication being associated with a session between multiple participants; and one or more timer objects associated with the session and accessible by the engine nodes, said timer objects being maintained remotely with respect to the engine nodes, wherein said timer objects, once initiated, gradually reduce a specified time period until the timer objects fire; wherein once a particular timer object fires, a notification is transmitted to an engine node that processed the last communication for the session associated with said particular timer object; and wherein said engine node that processed said last communication is assigned the particular timer object for processing. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10)
-
-
11. A method for providing timer affinity within a session-based server deployment, said method comprising:
-
processing incoming communications by one or more engine nodes, each communication being associated with a session between multiple participants; initiating at least one timer object that is accessible by the engine nodes, said timer object being maintained remotely with respect to the engine nodes, wherein the timer object is associated with a particular session; continuously reducing a time period specified by said timer object until said time period expires; transmitting a notification to an engine node that processed the last communication for the particular session associated with said timer object; and executing the timer object by the engine node that processed the last communication for the particular session. - View Dependent Claims (12, 13, 14, 15, 16, 17, 18, 19)
-
-
20. A computer-readable medium carrying one or more sequences of instructions for providing timer affinity in a session-based server deployment, which instructions, when executed by one or more processors, cause the one or more processors to carry out the steps of:
-
processing incoming communications by one or more engine nodes, each communication being associated with a session between multiple participants; initiating at least one timer object that is accessible by the engine nodes, said timer object being maintained remotely with respect to the engine nodes, wherein the timer object is associated with a particular session; continuously reducing a time period specified by said timer object until said time period expires; transmitting a notification to an engine node that processed the last communication for the particular session associated with said timer object; and executing the timer object by the engine node that processed the last communication for the particular session.
-
Specification