# US 2009/0245248 A1 · Method and apparatus for providing resiliency in multicast networks

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2009/0245248 A1
- Document ID: US20090245248A1
- Status: Published application
- Kind: A1
- Application number: 12/060,098
- Filed: 2008-03-31
- Published: 2009-10-01
- Earliest claimed: 2008-03-31
- Assignees: Ericsson Inc.
- Inventors: Peter Arberg; Ramanathan Lakshmikanthan; Ferry Sutanto
- Web page: https://patentgrep.com/patent/US20090245248A1

## CPC

- H04L 45/16: Multipoint routing
- H04L 12/185: {with management of multicast group membership}
- H04L 12/1863: {comprising mechanisms for improved reliability, e.g. status reports (arrangements for detecting or preventing errors by carrying supervisory signal the return channel H04L1/16)}
- H04L 41/0654: using network fault recovery (ring fault isolation or reconfiguration in loop networks without recovery actions by a network management system H04L12/437)
- H04L 45/12: Shortest path evaluation
- H04L 45/28: using route fault recovery
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

Techniques for providing resilient multicast traffic processing in a network element are described herein. In one embodiment of the invention, a network element separately joins equivalent multicast traffic streams at a first and second interface respectively. During uninterrupted operation, the network element processes the packets of the multicast traffic stream it receives at the first interface and drops the packets of the equivalent multicast traffic stream it receives at the second interface. Upon an interruption of the packets of the multicast traffic stream being received at the first interface, the network element transitions to processing the packets of the equivalent multicast traffic stream it receives at the second interface. Other methods and apparatuses are also described.

## Claims

### Claim 1

A computer implemented method for a multicast edge network element guaranteeing resilient multicast traffic stream processing of only a last hop of the multicast traffic stream towards a multicast receiver, wherein the multicast edge network element is coupled with a first and second multicast core network element each capable of forwarding packets of an equivalent multicast traffic stream to the multicast edge network element and each is situated between a source of the multicast traffic stream and the multicast edge network element, comprising:
separately joining through a first and second interface of the multicast edge network element the equivalent multicast traffic streams from the first and second multicast core network element respectively;
processing packets of the multicast traffic stream received at the first interface from the first multicast core network element, and while the first interface is receiving those packets uninterrupted, dropping packets of the equivalent multicast traffic stream received at the second interface from the second multicast core network element; and
upon interruption of receipt of the packets of the multicast traffic stream at the first interface, transitioning to processing the packets of the equivalent multicast traffic stream subsequently being received at the second interface from the second multicast core network element.

### Claim 2 (depends on 1)

The computer implemented method of claim 1, wherein separately joining includes automatically selecting the first interface according to a unicast routing protocol on a first line card and a network administrator selecting the second interface to be on a second line card, wherein the second interface is coupled with the second core multicast network element creating node disjointness of the last hop of the equivalent multicast traffic streams to the multicast edge network element, and wherein the second core multicast network element uses its unicast routing protocol to determine its best route towards the source of the multicast traffic stream, wherein the paths of each of the equivalent multicast traffic streams are guaranteed to be different only for the last hop to the multicast edge network element 150.

### Claim 3 (depends on 2)

The computer implemented method of claim 2, wherein guaranteeing the resilient multicast traffic stream processing of only the last hop includes the multicast edge network element not guaranteeing multicast traffic stream processing if a pre-last hop failure affects both equivalent multicast traffic streams.

### Claim 4 (depends on 1)

The computer implemented method of claim 1, wherein transitioning to processing the packets of the equivalent multicast traffic stream being received at the second interface is performed in less than 50 milliseconds.

### Claim 5 (depends on 1)

The computer implemented method of claim 1, further comprising,
determining a best route towards the source of the multicast traffic stream, according to a unicast routing protocol, is through a third multicast core network element, wherein the third multicast core network element is able to forward equivalent packets of the multicast traffic stream to the multicast edge network element and is situated between the source of the multicast traffic stream and the multicast edge network element;
adding a third interface of the multicast edge network element to an outgoing interface list;
joining through the third interface the equivalent multicast traffic stream from the third multicast core network element;
upon receiving packets of the multicast traffic stream on the third interface from the third multicast core network element, transitioning to performing the following,
processing the packets of the multicast traffic stream received on the third interface from the third multicast core network element, and
dropping the packets of the multicast traffic stream being received at the second interface from the second multicast core network element.

### Claim 6 (depends on 5)

The computer implemented method of claim 5, further comprising removing the third interface from the outgoing interface list upon transitioning to processing the packets of the multicast traffic stream received on the third interface from the third multicast core network element.

### Claim 7 (depends on 1)

The computer implemented method of claim 1, wherein the multicast edge network element detects the interruption of the multicast traffic through use of a communication link failure notification or a drop in a rate of receipt of multicast traffic below a configured threshold.

### Claim 8 (depends on 5)

The computer implemented method of claim 5, wherein the third multicast core network element and the first multicast core network element are the same multicast core network element.

### Claim 9

A multicast edge network element to guarantee resilient multicast traffic stream processing of only a last hop of the multicast traffic stream towards a multicast receiver, comprising:
an interface manager module to automatically configure a first interface on a first line card with a best route towards a source of the multicast traffic stream as determined by a unicast routing protocol module, and to configure a second interface on a second line card as a backup interface;
a protocol independent multicast (PIM) module coupled with the first and second line card, the PIM module to cause the multicast edge network element to join the multicast traffic stream through the first interface and to separately join an equivalent multicast traffic stream through the second interface to enable the first and second line card to receive packets of the multicast traffic streams respectively;
a multicast traffic stream failure detection module coupled with the first and second line card, the multicast traffic stream failure detection module to detect one or more interruptions of the multicast traffic streams; and
a line card manager coupled with the multicast traffic stream failure detection module and the first and second line cards, the line card manager to,
cause packets of the multicast traffic stream that are to be received at the first line card to be processed and the packets of the equivalent multicast traffic stream that are to be received at the second line card to be dropped while the first line card receives those packets uninterrupted, and
cause a transition to process the packets of the equivalent multicast traffic stream that are to be received at the second line card if the multicast traffic stream failure detection module detects an interruption at the first line card of the receipt of the packets of the multicast traffic stream.

### Claim 10 (depends on 9)

The multicast edge network element of claim 9, further comprising:
a command line interface module coupled with the interface module and the PIM module, the command line interface module to accept a command from an administrator to cause the interface module to configure the second interface on the second line card, wherein the command is to further cause the PIM module to join the equivalent multicast traffic stream through the second interface.

### Claim 11 (depends on 10)

The multicast edge network element of claim 10, further comprising the interface manager to couple the first and second interface with a first and second multicast core network element respectively to create node disjointness of the last hop of the equivalent multicast traffic streams to the multicast edge network element, wherein the second core network element is to use its unicast routing protocol to determine its best route to a source of the multicast traffic stream.

### Claim 12 (depends on 11)

The multicast edge network element of claim 11, wherein the multicast edge network element is not to guarantee multicast traffic stream processing if a pre-last hop failure affects both equivalent multicast traffic streams.

### Claim 13 (depends on 9)

The multicast edge network element of claim 9, wherein the line card manager is to cause the transition in less than 50 milliseconds.

### Claim 14 (depends on 10)

The multicast edge network element of claim 10, wherein the interface manager module is to couple the first and second interfaces with a first and second multicast core network element respectively

### Claim 15 (depends on 14)

The multicast edge network element of claim 14, further comprising:
the interface manager to automatically configure a third interface with a best route towards the multicast source as determined by the unicast routing protocol module, and to add the third interface to an outgoing interface list;
the PIM module to cause to multicast edge network element to join an equivalent multicast traffic stream through the third interface; and
the line manager further to cause packets of the equivalent multicast traffic stream that are to be received at the third interface to be processed and to cause the packets of the equivalent multicast traffic stream that are to be received at the second line card to be dropped.

### Claim 16 (depends on 9)

The multicast edge network element of claim 9, wherein the multicast traffic stream failure detection module is to detect interruptions of the multicast traffic stream with use of a communication link failure notification.

### Claim 17

A machine-readable medium that provides instructions that, if executed by a processor, will cause said processor to perform operations for a multicast edge network element guaranteeing resilient multicast traffic stream processing of only a last hop of the multicast traffic stream towards a multicast receiver, wherein the multicast edge network element is coupled with a first and second multicast core network element each capable of forwarding packets of an equivalent multicast traffic stream to the multicast edge network element and each is situated between a source of the multicast traffic stream and the multicast edge network element, comprising:
separately joining through a first and second interface of the multicast edge network element the equivalent multicast traffic streams from the first and second multicast core network element respectively;
processing packets of the multicast traffic stream received at the first interface from the first multicast core network element, and while the first interface is receiving those packets uninterrupted, dropping packets of the equivalent multicast traffic stream received at the second interface from the second multicast core network element; and
upon interruption of receipt of the packets of the multicast traffic stream at the first interface, transitioning to processing the packets of the equivalent multicast traffic stream subsequently being received at the second interface from the second multicast core network element.

### Claim 18 (depends on 17)

The machine-readable medium of claim 17, wherein separately joining includes automatically selecting the first interface according to a unicast routing protocol on a first line card and a network administrator selecting the second interface to be on a second line card, wherein the second interface is coupled with the second core multicast network element creating node disjointness of the last hop of the equivalent multicast traffic streams to the multicast edge network element, and wherein the second core multicast network element uses its unicast routing protocol to determine its best route towards the source of the multicast traffic stream, wherein the paths of each of the equivalent multicast traffic streams are guaranteed to be different only for the last hop to the multicast edge network element 150.

### Claim 19 (depends on 18)

The machine-readable medium of claim 18, wherein guaranteeing the resilient multicast traffic stream processing of only the last hop includes the multicast edge network element not guaranteeing multicast traffic stream processing if a pre-last hop failure affects both equivalent multicast traffic streams.

### Claim 20 (depends on 17)

The machine-readable medium of claim 17, wherein transitioning to processing the packets of the equivalent multicast traffic stream being received at the second interface is performed in less than 50 milliseconds.

### Claim 21 (depends on 17)

The machine-readable medium of claim 17, further comprising,
determining a best route towards the source of the multicast traffic stream, according to a unicast routing protocol, is through a third multicast core network element, wherein the third multicast core network element is able to forward equivalent packets of the multicast traffic stream to the multicast edge network element and is situated between the source of the multicast traffic stream and the multicast edge network element;
adding a third interface of the multicast edge network element to an outgoing interface list;
joining through the third interface the equivalent multicast traffic stream from the third multicast core network element;
upon receiving packets of the multicast traffic stream on the third interface from the third multicast core network element, transitioning to performing the following,
processing the packets of the multicast traffic stream received on the third interface from the third multicast core network element, and
dropping the packets of the multicast traffic stream being received at the second interface from the second multicast core network element.

### Claim 22 (depends on 21)

The machine-readable medium of claim 21, further comprising removing the third interface from the outgoing interface list upon transitioning to processing the packets of the multicast traffic stream received on the third interface from the third multicast core network element.

### Claim 23 (depends on 17)

The machine-readable medium of claim 17, wherein the multicast edge network element detects the interruption of the multicast traffic through use of a communication link failure notification or a drop in a rate of receipt of multicast traffic below a configured threshold.

### Claim 24 (depends on 21)

The machine-readable medium of claim 21, wherein the third multicast core network element and the first multicast core network element are the same multicast core network element.
