# US 2012/0250685 A1 · Forwarding groups of multicast flows

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

- Number: US 2012/0250685 A1
- Document ID: US20120250685A1
- Status: Published application
- Kind: A1
- Application number: 13/495,711
- Filed: 2012-06-13
- Published: 2012-10-04
- Earliest claimed: 2006-07-28
- Assignees: Internatonal Business Machines Corporation
- Inventors: CHATSCHIK BISDIKIAN
- Web page: https://patentgrep.com/patent/US20120250685A1

## CPC

- H04L 45/00: Routing or path finding of packets in data switching networks (routing or path finding in wireless networks H04W40/00)
- H04L 12/1854: {with non-centralised forwarding system, e.g. chaincast}
- H04L 45/16: Multipoint routing
- H04L 45/306: {Route determination based on the nature of the carried application}
- H04L 45/54: {Organization of routing tables}
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

A routing element and method for forwarding multicast traffic in a network includes grouping a collection of path-related multicast information flows from a source and associating each information flow of the collection with a multicast address from a set of multicast addresses. Forwarding information is placed in routers within the network between the sources and destinations wherein the forwarding information includes a single entry in a forwarding table using an identifier, e.g., a representative address, for the collection.

## Claims

### Claim 1

A routing element for a communications network, comprising:
a forwarding table having a collection of distinct lists of outgoing router interfaces used by one or more of a plurality of multicast groups transmitting through the routing element, the forwarding table including grouping information employed to combine two or more of the distinct lists to concurrently provide a multicast flow to the outgoing router interfaces on the two or more of the distinct lists; and
a replication element configured to map the multicast flow in accordance with the grouping information.

### Claim 2 (depends on 1)

The routing element as recited in claim 1, further comprising a reverse path forwarding (RPF) module to check incoming packets.

### Claim 3 (depends on 1)

The routing element as recited in claim 1, further comprising a control module configured to combine two or more of the distinct lists to provide a multicast flow to the outgoing router interfaces on the two or more of the distinct lists.

### Claim 4 (depends on 3)

The routing element as recited in claim 3, wherein the two or more of the distinct lists are combined in accordance with criteria externally supplied to the control module.

### Claim 5 (depends on 1)

The routing element as recited in claim 1, wherein the two or more of the distinct lists which are grouped are identified by a single identifier.

### Claim 6 (depends on 1)

The routing element as recited in claim 1, wherein the two or more of the distinct lists are grouped based upon a content-based property.

### Claim 7 (depends on 1)

The routing element as recited in claim 1, further comprising a replication pattern identifier field in the forwarding table wherein the two or more of the distinct lists are linked using a same replication pattern identifier indicated in the field.

### Claim 8 (depends on 7)

The routing element as recited in claim 7, further comprising a pass-through identifier placed in the replication pattern identifier field to indicate that a multicast group is not linked to other distinct lists.

### Claim 9 (depends on 1)

The routing element as recited in claim 1, wherein the multicast flows includes multicast transmissions.

### Claim 10 (depends on 1)

The routing element as recited in claim 1, further comprising a multicast control protocol configured to communicate thematic linkage information to a control module which combines the two or more distinct lists.

### Claim 11 (depends on 10)

The routing element as recited in claim 10, wherein the multicast control protocols propagate multicast distribution tree management information (join, prune) for all the multicast groups that are thematically linked.
