IP Library Granted Patent US 8,009,555
Granted Patent B2
US 8,009,555 · App. 12/392,904 · Granted Aug 30, 2011

Mechanism for transparent real-time media server fail-over with idle-state nodes

Assignee: Red Hat, Inc.
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 8,009,555
App. No.
12/392,904
Granted
Aug 30, 2011
Kind
B2
Abstract

In one embodiment, a mechanism for transparent real-time media server fail-over with idle-state nodes is disclosed. In one embodiment, a method includes replicating a start time of a request related to a bidirectional stream of media sent to an original master media server, receiving notification of selection as a new master media server after failure of the original master media server, determining an offset time by subtracting the replicated request start time from a current time, and resuming playback of the request at the offset time within the request.

Claims (40)

1. A computer-implemented method performed by a new master media server, comprising:

replicating a start time of a request related to a bidirectional stream of media sent to an original master media server, wherein the original master media server performs playback of the request at the start time;

receiving notification of selection as the new master media server after failure of the original master media server;

remaining idle until both of the failure of the original master media server and the selection as the new master media server;

determining an offset time by subtracting the replicated request start time from a current time; and

resuming playback of the request at the offset time within the request.

2. The method of claim 1 , wherein the request includes at least one of playback of a file, a scheduled task, and generation of a dual tone multi-frequency (DTMF) sequence signal.

3. The method of claim 1 , wherein the original master media server and the new master media server are developed on a JAVA platform.

4. The method of claim 3 , wherein the original master media server and the new master media server utilize a JAVA Management Extension (JMX) Application Programming Interface (API) and a Service Logic Execution Environment (SLEE) container.

5. The method of claim 1 , wherein the original master media server and the new master media server are controlled by a JBoss™ Communications Platform (JBCP) application server.

6. The method of claim 1 , wherein the original master media server receives the bidirectional stream of media from a media gateway.

7. A system, comprising:

a media server controller;

a master media server controlled by the media server controller to receive a bidirectional stream of media from a caller; and

a backup media server coupled to the master media server and controlled by the media server controller, the backup media server operable to:

replicate a start time of a request related to the bidirectional stream of media, wherein the master media server performs playback of the request at the start time;

receive notification from the controller of selection as a new master media server after failure of the master media server;

remain idle until both of the failure of the master media server and the selection as the new master media server;

determine an offset time by subtracting the replicated request start time from a current time; and

resume playback of the request at the offset time within the request.

8. The system of claim 7 , wherein the request includes at least one of playback of a file, a scheduled task, and generation of a dual tone multi-frequency (DTMF) sequence signal.

9. The system of claim 7 , wherein the master media server and the new master media server are developed on a JAVA platform.

10. The system of claim 9 , wherein the master media server and the new master media server utilize a JAVA Management Extension (JMX) Application Programming Interface (API) and a Service Logic Execution Environment (SLEE) container.

11. The system of claim 7 , wherein the controller is a JBoss™ Communications Platform (JBCP) application server.

12. The system of claim 7 , wherein the master media server receives the bidirectional stream of media from a media gateway communicably coupled to the master media server and the backup media server.

13. An article of manufacture comprising a non-transitory machine-readable storage medium including data that, when accessed by a machine, cause the machine to perform operations comprising:

replicating a start time of a request related to a bidirectional stream of media sent to an original master media server, wherein the original master media server to perform playback of the request;

receiving notification of selection as a new master media server after failure of the original master media server;

remaining idle until both of the failure of the original master media server and the selection as the new master media server;

determining an offset time by subtracting the replicated request start time from a current time; and

resuming playback of the request at the offset time within the request.

14. The article of manufacture of claim 13 , wherein the request includes at least one of playback of a file, a scheduled task, and generation of a dual tone multi-frequency (DTMF) sequence signal.

15. The article of manufacture of claim 13 , wherein the original master media server and the new master media server are developed on a JAVA platform.

16. The article of manufacture of claim 15 , wherein the original master media server and the new master media server utilize a JAVA Management Extension (JMX) Application Programming Interface (API) and a Service Logic Execution Environment (SLEE) container.

17. The article of manufacture of claim 13 , wherein the original master media server and the new master media server are controlled by a JBoss™ Communications Platform (JBCP) application server.

18. The method of claim 1 , wherein the request start time is replicated by the new master media server, wherein the notification of selection as the new master media server is received by the new master media server, wherein the offset time is determined by the new master media server, and wherein the playback is resumed by the new master media server.

19. The method of claim 1 , wherein the new master media server does not execute all of the requests received by the original master media server and does not replicate the state of the original master media server.

20. The system of claim 7 , wherein the backup media server does not execute all of the requests received by the master media server and does not replicate the state of the master media server.

21. The article of manufacture of claim 13 , wherein the request start time is replicated by the new master media server, wherein the notification of selection as the new master media server is received by the new master media server, wherein the offset time is determined by the new master media server, and wherein the playback is resumed by the new master media server.

22. The article of manufacture of claim 13 , wherein the new master media server does not execute all of the requests received by the original master media server and does not replicate the state of the original master media server.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 25, 2009
From: RALEV, VLADIMIR ANGELOV
To: RED HAT, INC.
Reel/Frame 022312/0979 →
Continuity (1)
Related Publication 20100214908A1 · Aug 26, 2010