# US 2025/0219929 A1 · Efficient multicast traffic distribution in an overlay network using underlay multicast distribution

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

- Number: US 2025/0219929 A1
- Document ID: US20250219929A1
- Status: Published application
- Kind: A1
- Application number: 18/608,208
- Filed: 2024-03-18
- Published: 2025-07-03
- Earliest claimed: 2023-12-28
- Assignees: Hewlett Packard Enterprise Development LP
- Applicants: Hewlett Packard Enterprise Development LP
- Inventors: Tathagata Nandy; Chethan Chavadibagilu Radhakrishnabhat; Thomas Samuel; Subramanian Muthukumar; Somnath Bhimaram Lohar
- Web page: https://patentgrep.com/patent/US20250219929A1

## CPC

- H04L 45/16: Multipoint routing
- H04L 12/4633: {Interconnection of networks using encapsulation techniques, e.g. tunneling}
- H04L 12/4641: {Virtual LANs, VLANs, e.g. virtual private networks [VPN] (LAN interconnection over a bridge based backbone H04L12/462; encapsulation techniques H04L12/4633; routing of packets H04L45/00; packet switches H04L49/00; virtual private networks for security H04L63/0272)}
- H04L 45/64: using an overlay routing layer
- H04L 45/76: Routing in software-defined topologies, e.g. routing between virtual machines
- H04L 2212/00: Encapsulation of packets
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

A network device operating as a tunnel endpoint in an overlay network is provided. During operation, the network device can receive a multicast packet destined to a first multicast group via an edge port. The edge port can be coupled to the source of the first multicast group. The network device can then map the first multicast group to a second multicast group configured in an underlying network of the overlay network by applying a mapping rule. Subsequently, the network device can encapsulate the multicast packet with a first encapsulation header with a destination address, which is a multicast address of the second multicast group. The network device can then identify a Rendezvous Point (RP) of the second multicast group and forward the encapsulated multicast packet to the RP based on the multicast address of the second multicast group.

## Claims

### Claim 1

A method, comprising:
receiving, by a network device in an overlay network, a multicast packet destined to a first multicast group via an edge port of the network device, wherein the network device operates as a tunnel endpoint in the overlay network, and wherein the edge port is coupled to a source of the first multicast group;
mapping, by the network device, the first multicast group to a second multicast group configured in an underlying network of the overlay network by applying a mapping rule;
encapsulating, by the network device, the multicast packet with a first encapsulation header with a destination address, which is a multicast address of the second multicast group;
identifying, by the network device, a Rendezvous Point (RP) of the second multicast group; and
forwarding, by the network device, the encapsulated multicast packet to the RP based on the multicast address of the second multicast group.

### Claim 2 (depends on 1)

The method of claim 1, wherein the mapping rule comprises at least one of:
a hash function producing an index for a range of predetermined multicast groups configured in the underlying network;
a sequential mapping to the range of multicast groups; and
a random mapping to the range of multicast groups.

### Claim 3 (depends on 1)

The method of claim 1, wherein the first multicast group is based on a Protocol Independent Multicast (PIM) sparse-mode (SM) protocol, and wherein the second multicast group is based on a bidirectional PIM (PIM-BIDIR) protocol.

### Claim 4 (depends on 1)

The method of claim 1, wherein identifying the RP of the second multicast group comprises:
selecting the RP from a set of RPs of a range of predetermined multicast groups configured in the underlying network; and
using the mapping rule to select the second multicast group from the range of predetermined multicast groups.

### Claim 5 (depends on 1)

The method of claim 1, wherein multicast traffic from the source of the first multicast group is forwarded via a multicast tree rooted at the RP of the second multicast group.

### Claim 6 (depends on 1)

The method of claim 1, further comprising determining, by the network device, a third multicast group configured in the underlying network, wherein the third multicast group is for carrying multicast traffic to a multicast querier of a virtual local area network (VLAN) associated with the multicast packet.

### Claim 7 (depends on 6)

The method of claim 6, further comprising:
encapsulating, by the network device, a copy of the multicast packet with a second encapsulation header, wherein a destination address of the second encapsulation header comprises a second multicast address of the third multicast group;
identifying, by the network device, a second RP of the third multicast group; and
forwarding, by the network device, the encapsulated copy of the multicast packet to the second RP based on the second multicast address.

### Claim 8 (depends on 1)

The method of claim 1, wherein the third multicast group is associated with a respective multicast group sending traffic over the VLAN.

### Claim 9

A non-transitory computer-readable storage medium storing instructions that when executed by a processor of a network device in an overlay network cause the processor to perform a method, the method comprising:
receiving a multicast packet destined to a first multicast group via an edge port of the network device, wherein the network device operates as a tunnel endpoint in the overlay network, and wherein the edge port is coupled to a source of the first multicast group;
mapping the first multicast group to a second multicast group configured in an underlying network of the overlay network by applying a mapping rule;
encapsulating, by the network device, the multicast packet with a first encapsulation header with a destination address, which is a multicast address of the second multicast group;
identifying a Rendezvous Point (RP) of the second multicast group; and
forwarding the encapsulated multicast packet to the RP based on the multicast address of the second multicast group.

### Claim 10 (depends on 9)

The non-transitory computer-readable storage medium of claim 9, wherein the mapping rule comprises at least one of:
a hash function producing an index for a range of predetermined multicast groups configured in the underlying network;
a sequential mapping to the range of multicast groups; and
a random mapping to the range of multicast groups.

### Claim 11 (depends on 9)

The non-transitory computer-readable storage medium of claim 9, wherein the first multicast group is based on a Protocol Independent Multicast (PIM) sparse-mode (SM) protocol, and wherein the second multicast group is based on a bidirectional PIM (PIM-BIDIR) protocol.

### Claim 12 (depends on 9)

The non-transitory computer-readable storage medium of claim 9, wherein identifying the RP of the second multicast group comprises:
selecting the RP from a set of RPs of a range of predetermined multicast groups configured in the underlying network; and
using the mapping rule to select the second multicast group from the range of predetermined multicast groups.

### Claim 13 (depends on 9)

The non-transitory computer-readable storage medium of claim 9, wherein multicast traffic from the source of the first multicast group is forwarded via a multicast tree rooted at the RP of the second multicast group.

### Claim 14 (depends on 9)

The non-transitory computer-readable storage medium of claim 9, wherein the method further comprises determining a third multicast group configured in the underlying network, wherein the third multicast group is for carrying multicast traffic to a multicast querier of a virtual local area network (VLAN) associated with the multicast packet.

### Claim 15 (depends on 14)

The non-transitory computer-readable storage medium of claim 14, wherein the method further comprises:
encapsulating a copy of the multicast packet with a second encapsulation header, wherein a destination address of the second encapsulation header comprises a second multicast address of the third multicast group;
identifying a second RP of the third multicast group; and
forwarding the encapsulated copy of the multicast packet to the second RP based on the second multicast address.

### Claim 16 (depends on 14)

The non-transitory computer-readable storage medium of claim 14, wherein the third multicast group is associated with a respective multicast group sending traffic over the VLAN.

### Claim 17

A method comprising:
receiving, by a network device in an overlay network, a first join request from a client device requesting multicast traffic of a first multicast group via an edge port of the network device, wherein the network device operates as a tunnel endpoint in the overlay network;
mapping, by the network device, the first multicast group to a second multicast group configured in an underlying network of the overlay network by applying a mapping rule;
generating, by the network device, a second join request requesting multicast traffic of the second multicast group;
identifying, by the network device, a Rendezvous Point (RP) of the second multicast group; and
forwarding, by the network device, the second join request to the RP based on a multicast address of the second multicast group.

### Claim 18 (depends on 17)

The method of claim 17, further comprising:
receiving, by the network device, a multicast packet encapsulated by an encapsulation header with a destination address, which is the multicast address of the second multicast group, wherein the multicast packet belongs to the first multicast group; and
forwarding, by the network device, the multicast packet via the edge port based on the first join request.

### Claim 19 (depends on 17)

The method of claim 17, wherein the mapping rule comprises at least one of:
a hash function producing an index for a range of predetermined multicast groups configured in the underlying network;
a sequential mapping to the range of multicast groups; and
a random mapping to the range of multicast groups.

### Claim 20 (depends on 17)

The method of claim 17, wherein the first multicast group is based on a Protocol Independent Multicast (PIM) sparse-mode (SM) protocol, and wherein the second multicast group is based on a bidirectional PIM (PIM-BIDIR) protocol.
