Network based switchover to original content after ad-insertion device failure

• US 8,675,478 B2
• Filed: 04/30/2008
• Issued: 03/18/2014
• Est. Priority Date: 04/30/2008
• Status: Expired due to Fees

• Current Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Original Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Inventors: Asati, Rajiv, Shepherd, Gregory, Khalid, Mohamed
• Primary Examiner(s): Shah, Chirag
• Assistant Examiner(s): Kang, Suk Jin
• Application Number:
  US12/112,641
• Publication Number:
  US 20090274042A1
• Time in Patent Office: 2,148 Days
• Field of Search: None
• US Class Current: 370/225
• CPC Class Codes: H04L 12/185 with management of multicast group membership
• CPC Class Codes: H04L 12/1868 Measures taken after transmission, e.g. acknowledgments
• CPC Class Codes: H04L 45/00 Routing or path finding of packets in data switching networks routing or path finding in wireless networks H04W40/00
• CPC Class Codes: H04L 45/16 Multipoint routing
• CPC Class Codes: H04L 45/22 Alternate routing
• CPC Class Codes: H04L 45/28 using route fault recovery
• CPC Class Codes: H04L 45/48 Routing tree calculation
• CPC Class Codes: H04L 45/484 using multiple routing trees

Abstract

In one embodiment, a network device joins a first multicast tree to receive post-ad-inserted video content. The network device also joins a second multicast tree to receive the pre-ad-inserted video content. The content from the first multicast tree is forwarded by the network device to the receiver(s). The network device determines if it does not receive the content on the first multicast tree due to any failure, in which case, it delivers the content from the second multicast tree to the receiver(s). This enables the receiver to receive the original (pre-ad-inserted) content during the failure in first multicast tree. When the failure is resolved, the network device can go back to sending the content from the first multicast tree to the receiver(s).

Claims

1. A method comprising:

joining a first multicast tree for a first content generated at a first source, wherein the first multicast tree is identified at least by the first source;

joining a second multicast tree for a second content generated at a second source, wherein the second multicast tree is different from the first multicast tree, wherein the second multicast tree is identified at least by the second source, wherein the first source is different from the second source, and the first content includes advertising content overlaid on the second content;

adding a first outgoing interface to the first multicast tree to allow the first content to be sent to a receiver when the first content is received;

adding a second outgoing interface to the second multicast tree, wherein the second outgoing interface is non-active, such that the second content is not sent to the receiver when the second content is received;

determining a failure of receiving the first content on the first multicast tree;

switching from the first outgoing interface to the second outgoing interface such that the second content is sent to the receiver;

determining a resolution of the failure such that the first content is received on the first multicast tree; and

switching from the second outgoing interface to the first outgoing interface such that the first content is sent to the receiver.

2. The method of claim 1, further comprising:

sending one or more join messages for first and second multicast trees.

3. The method of claim 1, further comprising:

receiving a join request from the receiver specifying the first source and the second source;

determining the first and second sources using a source priority specified in the join request;

joining the first multicast tree for the first source and the second multicast tree for the second source; and

sending the content from the first multicast tree to the receiver until the failure of receiving the first content on the first multicast tree.

4. The method of claim 3, further comprising:

receiving a join request from the receiver for a multicast group without specifying source;

determining the first and second sources for the specified multicast group based on a predetermined configuration;

joining the first multicast tree for the first source and the second multicast tree for the second source; and

sending the content from the first multicast tree to the receiver until the failure of receiving the first content on the first multicast tree.

5. The method of claim 1, further comprising:

monitoring traffic for the first multicast tree;

determining if the failure occurs based on the traffic; and

performing the switching to the second outgoing interface upon the determination.

6. The method of claim 5, further comprising:

monitoring traffic for the first multicast tree;

determining if traffic received for the first multicast tree indicates the resolution in the failure; and

performing the switching to the first outgoing interface upon the determination of the resolution.

7. The method of claim 1, wherein the multicast tree is identified by either an IP route or MPLS label.

8. The method of claim 1, wherein the switching is performed without notification from the receiver to switch the multicast trees.

9. The method of claim 1, wherein the first multicast tree includes an ad that is inserted by an insertion complex that is part of the first multicast tree.

10. An apparatus comprising:

one or more processors; and

logic encoded in one or more tangible non-transitory media for execution by the one or more processors and when executed operable to;

join a first multicast tree for a first content generated at a first source, wherein the first multicast tree is identified at least by the first source;

join a second multicast tree for a second content generated at a second source, wherein the second multicast tree is different from the first multicast tree, wherein the second multicast tree is identified at least by the second source, wherein the first source is different from the second source, and the first content includes advertising content overlaid on the second content;

add a first outgoing interface to the first multicast tree to allow the first content to be sent to a receiver when the first content is received;

add a second outgoing interface to the second multicast tree, wherein the second outgoing interface is non-active, such that the second content is not sent to the receiver when the second content is received;

determine a failure of receiving the first content on the first multicast tree; and

switch from the first outgoing interface to the second outgoing interface such that the second content is sent to the receiver;

determine a resolution of the failure such that first content is received on the first multicast tree; and

switch from the second outgoing interface to the first outgoing interface such that the first content is sent to the receiver.

11. The apparatus of claim 10, wherein the logic when executed is further operable to send one or more join messages for first and second multicast trees.

12. The apparatus of claim 10, wherein the logic is further operable to:

receive a join request from the receiver specifying first source and the second source;

determine the first and second sources using a source priority specified in the join request;

join the first multicast tree for the first source and the second multicast tree for the second source; and

send the first content from the first multicast tree to the receiver until the failure of receiving the first content on the first multicast tree.

13. The apparatus of claim 10, wherein the logic when executed is further operable to:

monitor traffic for the first multicast tree;

determine if the failure occurs based on the traffic; and

perform the switching to the second outgoing interface upon the determination.

14. The apparatus of claim 13, wherein the logic when executed is further operable to:

monitor traffic for the first multicast tree;

determine if traffic received for the first multicast tree indicates the resolution in the failure; and

perform the switching to the first outgoing interface upon the determination of the resolution.

15. The apparatus of claim 10, wherein the multicast tree is identified by either an IP route or MPLS label.

16. The apparatus of claim 10, wherein the switching is performed without notification from the receiver to switching the multicast trees.

17. The apparatus of claim 10, wherein the first multicast tree includes an ad that is inserted by an insertion complex that is part of the first multicast tree.

18. An apparatus comprising:

means for joining a first multicast tree for a first content generated at a first source, wherein the first multicast tree is identified at least by the first source;

means for joining a second multicast tree for a second content generated at a second source, wherein the second multicast tree is different from the first multicast tree, wherein the second multicast tree is identified at least by the second source, wherein the first source is different from the second source, and the first content includes advertising content overlaid on the second content;

means for adding a first outgoing interface to the first multicast tree to allow the first content to be sent to a receiver when the first content is received;

means for adding to a second outgoing interface to the second multicast tree, wherein the second outgoing interface is non-active such that the second content is not sent to the receiver when the second content is received;

means for determining a failure of receiving the first content on the first multicast route;

means for switching from the first outgoing interface to the second outgoing interface such that the second content is sent to the receiver;

means for determining a resolution of the failure such that first content is received on the first multicast tree; and

means for switching to the first outgoing interface such that the first content is sent to the receiver.